aboutsummaryrefslogtreecommitdiffstats
path: root/boot.php
Commit message (Collapse)AuthorAgeFilesLines
* add aid to notifiy table which we may need to supress duplicate notify ↵friendica2013-11-201-1/+1
| | | | | | emails across your channels also try to handle the wretched mess of broken and duplicated hublocs that fred.cepheus.uberspace.de typically reports
* Protocol: now set data['alg'] on all encapsulated encrypted packets, so that ↵friendica2013-11-201-7/+3
| | | | we can more easily retire 'aes256cbc' once it is no longer viable.
* remove the challenge table as wellfriendica2013-11-181-1/+1
|
* drop the queue table which we no longer usefriendica2013-11-181-1/+1
|
* pull in some posts when we first connect with a new channel (if allowed to) ↵friendica2013-11-171-1/+1
| | | | - if not allowed to, do it if that condition changes
* document extra featuresfriendica2013-11-171-2/+4
|
* removeme sort of works for a single channel - lots of loose ends to deal ↵friendica2013-11-121-2/+4
| | | | with but it's a start
* provide zid in js so we can use it from clientfriendica2013-11-101-1/+2
|
* DB - allow private messages to expirefriendica2013-11-061-1/+1
|
* add shameless plug if they've not got zot, and add photo favicon to photos pagesfriendica2013-11-051-1/+7
|
* make the storage permissions tweakable for hosted environments where they ↵friendica2013-11-041-0/+15
| | | | may require tweaking.
* allow mailsent update locking to unlock after 24 hours. Also don't even try ↵friendica2013-10-301-3/+10
| | | | to do a DB update if the build number is 0. Something else will likely fail and likely in some horrible way, but we shouldn't try and update the DB - something is clearly wrong with it.
* if registration is disabled, send the site register link to pubsitesfriendica2013-10-301-8/+6
|
* allow zot public providers to list their location, as a non US-based server ↵friendica2013-10-301-1/+1
| | | | could be a strong selling point.
* Schema change - add channel_dirdate so we can ping a directory server once a ↵friendica2013-10-271-1/+1
| | | | 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-1/+1
| | | | uplink back to them without any ambiguity.
* Don't send a quintillion emails every time mysql restarts.Thomas Willingham2013-10-101-0/+6
|
* post signaturesfriendica2013-10-021-1/+2
|
* Add possibility to use a block a channel menu (set channel_menublock to the ↵zottel2013-10-011-0/+5
| | | | | | lowercase title of the block without special chars) Fix comanche_block() SQL
* implement republish permission for use in sourced channelsfriendica2013-09-301-18/+18
|
* directory sync - this will either work, or it won't work, or it will ↵friendica2013-09-301-2/+9
| | | | | | | | | 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-1/+1
|
* suppress creating the directory update record for profile updates which are ↵friendica2013-09-251-1/+1
| | | | part of the normal import_xchan sequence - otherwise we get two for every change. Create it normally if we are called with a profile_update message and don't go through the whole import_xchan thing.
* reduce susceptibility to bleichenberger attackfriendica2013-09-241-0/+1
|
* adult channel settingfriendica2013-09-221-7/+3
|
* add a flag field to xtags so that we can filter tags based on whether or not ↵friendica2013-09-191-1/+1
| | | | 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.
* provide a "safe search" backend and allow for self-censorship using nsfw or ↵friendica2013-09-191-1/+1
| | | | adult profile keywords. Eventually the directories will be forced to mark adult profiles and sync this knowledge between them. At the moment there's no way to do an unsafe search, but we really just need a checkbox and pass the value through directory to dirsearch on the back end, and some will want this as a pconfig.
* Merge branch 'zpull'friendica2013-09-191-0/+1
|\ | | | | | | | | | | | | Conflicts: boot.php install/database.sql install/update.php
| * set default charset of email_header_encode, add ud_flags to indicate which ↵friendica2013-09-181-1/+1
| | | | | | | | updates have been processed in some way.
* | sync item_search with yesterday's network fix for collections. Add ud_addr ↵friendica2013-09-191-1/+1
| | | | | | | | 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/+1
|/ | | | (directory sync) updates have been processed in some way.
* add "tiered" access policy, add tagcloud to directory pagesfriendica2013-09-181-1/+1
|
* site sellpage linksfriendica2013-09-171-1/+1
|
* Pieces we'll need to tie together chanman and account/channel deletion and ↵friendica2013-09-171-0/+1
| | | | | | | | directory sync. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. OK? Understood?
* bumped the capslockfriendica2013-09-171-1/+1
|
* SEO: add keywords to appropriate channel pagesfriendica2013-09-171-0/+7
|
* more remote error reporting for zotfriendica2013-09-121-0/+1
|
* extends DB in hubloc to maintain hubloc connectivityMichael Meer2013-09-101-5/+1
|
* site rename issuefriendica2013-09-091-1/+2
|
* Merge https://github.com/friendica/red into zpullfriendica2013-09-091-0/+11
|\
| * Preparation to maintain HubLocs from adminpanel. This should act as basis ↵Michael Meer2013-09-091-0/+11
| | | | | | | | for a kind of traffic light to get an overview.
* | change primary key on updates tablefriendica2013-09-091-1/+1
|/
* fix the sitename alsofriendica2013-09-081-1/+1
|
* fix the recipient and subject localisation of failed update emailsfriendica2013-09-081-3/+3
|
* public site list (will take a few days to populate, assuming folks have ↵friendica2013-09-051-1/+1
| | | | updated their site access policy which old sites do not have)
* update photo timestamp on site renamefriendica2013-09-051-1/+2
|
* security fix and ability to change layout on webpage edit formfriendica2013-09-031-3/+13
|
* testing Comanchefriendica2013-09-031-3/+2
|
* Merge pull request #108 from cvogeley/masterfriendica2013-09-021-11/+17
|\ | | | | More mobile theme fixes
| * More mobile theme fixesChristian Vogeley2013-08-311-11/+17
| | | | | | | | | | | | If user is logged in personal settings are used else use admin settings. Only show toggle link if there is something to switch between.