aboutsummaryrefslogtreecommitdiffstats
path: root/install/database.sql
Commit message (Collapse)AuthorAgeFilesLines
* add aid to notifiy table which we may need to supress duplicate notify ↵friendica2013-11-201-1/+3
| | | | | | emails across your channels also try to handle the wretched mess of broken and duplicated hublocs that fred.cepheus.uberspace.de typically reports
* remove the challenge table as wellfriendica2013-11-181-10/+0
|
* drop the queue table which we no longer usefriendica2013-11-181-16/+0
|
* DB - allow private messages to expirefriendica2013-11-061-18/+19
|
* Fix missing parenthesis in database.sqlAntoine G2013-11-011-1/+1
| | | This was blocking database creation process
* allow zot public providers to list their location, as a non US-based server ↵friendica2013-10-301-0/+1
| | | | could be a strong selling point.
* Schema change - add channel_dirdate so we can ping a directory server once a ↵friendica2013-10-271-0/+2
| | | | month which means we can find dead channels - because they won't be pinging the directory server once a month.
* preserve the source owner when creating a delivery fork so that we can ↵friendica2013-10-131-0/+1
| | | | uplink back to them without any ambiguity.
* post signaturesfriendica2013-10-021-1/+1
|
* implement republish permission for use in sourced channelsfriendica2013-09-301-0/+2
|
* directory sync - this will either work, or it won't work, or it will ↵friendica2013-09-301-1/+4
| | | | | | | | | possibly recurse and blow up the matrix. Hard to say. Do you feel lucky? Well do ya' ... punk? Rule #1 - don't mess with anything unless it's blowing up the matrix. If it doesn't blow up the matrix, but doesn't work, just let it go and let's figure out what it is doing and what it isn't doing. The flow is as follows: Once a day go out to all the directory servers besides yourself and grab a list of updates. This happens in the poller. If we've never seen them before add them to the updates table. The poller also looks to see if we're a directory server and have updates that haven't yet been processed. It calls onedirsync.php to process each one. If we contact the channel to update and don't find anything (we're just doing a basic zot_finger), set a ud_last timestamp. If this is set we will only try once a day for seven days. Then we stop trying to update. This will probably cause a spike the first time through because you haven't seen any updates before, but we spread out the load over your delivery interval.
* structure for channel unionsfriendica2013-09-261-0/+12
|
* add a flag field to xtags so that we can filter tags based on whether or not ↵friendica2013-09-191-1/+3
| | | | the parent xchan is safe or not. Otherwise we'll have tags that lead to nowhere because the directory entry is hidden but the tag isn't. A successful porn site in the matrix could also swamp the directory with x-rated tags, even if the site was playing nice and did everything right to self-censor. Accomplishing this with joins would be horrendously inefficient, though it will take a bit of code re-org to get this flag where it needs to be when it's time to set keywords.
* sync item_search with yesterday's network fix for collections. Add ud_addr ↵friendica2013-09-191-1/+3
| | | | to update table to store the target address since it's possible the mirroring directory won't yet have an xchan or hubloc they can link the ud_hash to and therefore mayn't know how to contact them.
* set default charset of email_header_encode, add ud_flags to indicate which ↵friendica2013-09-181-1/+3
| | | | (directory sync) updates have been processed in some way.
* site sellpage linksfriendica2013-09-171-1/+3
|
* Fixed error in SQL Statementndurchx2013-09-121-1/+1
|
* extends DB in hubloc to maintain hubloc connectivityMichael Meer2013-09-101-0/+2
|
* change primary key on updates tablefriendica2013-09-091-1/+3
|
* public site list (will take a few days to populate, assuming folks have ↵friendica2013-09-051-0/+2
| | | | updated their site access policy which old sites do not have)
* This isn't optimal, but on the short term we'll clone the page editor to use ↵friendica2013-09-011-2/+2
| | | | as a block editor, and probably a layout editor as well. Eventually, these should all probably just be switches onto a single editor instance. Decided to put the layout_mid into the item table directory rather than re-use resource_id, so that we can still have pages attached to different resources like photos and events and stuff. The block editor is far from finished, at this point I've only cloned it and changed the name and type of item it looks for.
* add a guid to directory update table to avoid recursionfriendica2013-08-311-0/+2
|
* basic structure for premium channel implementationfriendica2013-08-211-0/+4
|
* poll stufffriendica2013-08-211-1/+26
|
* network-wide poll voting structurefriendica2013-08-201-18/+28
|
* email attachments (and fix email photos)friendica2013-08-191-0/+1
|
* check these in so I can go back and find out why the stylsheet is horkedfriendica2013-08-111-1/+5
|
* basic *account* removal, but the channel removal which it calls still needs ↵friendica2013-08-041-22/+0
| | | | (lots of) work. Oh and the intro table is no longer used and won't be - so it's gone.
* add "xchan_instance_url" for communicating with services that lack nomadic ↵friendica2013-08-011-0/+2
| | | | identity. This will be set to the url of the Red site that they are connected with. Only the nomadic identity clone at that site can communicate directly with them. Other instances will need to relay through that site - and if it goes down, that connection is stuffed.
* better mail obscuringfriendica2013-07-311-1/+1
|
* fix bug #84, make imported messages from your clones show up on your wallfriendica2013-07-291-1/+1
|
* add chandesc field to profiles to provide some arbitrary text in the ↵friendica2013-07-241-0/+1
| | | | directory - such as to inform people what this channel is about before they connect. This will work best with a "channel detail" popup in the directory to provide more info than is available in the micro-profiles (when hovered, or clicked or something). And of course, the first thing is to enable this data to be stored in the directory.
* update friends/followers API so Friendica Android client won't chokefriendica2013-07-171-1/+0
|
* block duplicate channelsfriendica2013-07-171-0/+1
|
* photo_flags - for adding taxonomy photos and other stuff.friendica2013-07-161-0/+2
|
* fix xtagfriendica2013-07-141-8/+8
|
* Add self to recipient lists. Sure we already have a copy but it's possible ↵friendica2013-07-141-1/+3
| | | | our nomadic channel clones don't.
* any questions regarding this checkin will be ignoredfriendica2013-07-031-0/+17
|
* add age to directory profile - requires updating on each birthday and that ↵friendica2013-06-301-0/+2
| | | | part is still missing
* Basic ability to create "things"friendica2013-06-271-2/+4
|
* Add site registration policy to site record. This is not yet used or stored, ↵friendica2013-06-201-1/+3
| | | | but potentially can be exchanged through directory mirrors to automatically create "open site" lists.
* infrastructure for future stufffriendica2013-06-191-1/+3
|
* We will need a per item comment policy to be able to determine in advance if ↵friendica2013-06-161-0/+2
| | | | we have permission to comment on something , and we'll need to send it out with all communications. The current check is not only flawed but also a huge performance hit. Also provide the ability for an item to disable commenting completely - such as for a webpage or wherever you want to prevent comments on one item, without requiring a change to your entire permission scheme. All of this is only partially implemented at the moment but we need the structures in place on several sites in order to finish it without breaking everything.
* DB: add timestamps to hubloc table so we can eventually expire dead entries.friendica2013-06-041-2/+6
|
* add driver param to output queue so we know what protocol to use when faced ↵friendica2013-05-061-0/+1
| | | | with multiple choice
* minor fixes related to postgres developmentfriendica2013-05-051-2/+2
|
* missed channel_default_group key nrenamefriendica2013-04-031-1/+1
|
* add new connections to default group (if any)friendica2013-03-271-1/+1
|
* update manage table and some documentationfriendica2013-03-271-2/+2
|
* rename 'uri' (and parent_uri) to 'mid' (and parent_mid) since these no ↵friendica2013-03-211-10/+10
| | | | longer remotely resemble uri's and are actually message_id's. This change is potentially destabilising because it touches a lot of code and structure. But it has to get done and there's no better time than the present.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 17:06:22 +0000