aboutsummaryrefslogtreecommitdiffstats
path: root/boot.php
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* | This isn't optimal, but on the short term we'll clone the page editor to use ↵friendica2013-09-011-1/+1
|/ | | | 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-1/+1
|
* I've got a pretty good idea of how to bootstrap, parse and render Comanche ↵friendica2013-08-291-1/+16
| | | | now. This does not mean it's close to being presentable - far from it.
* block attempts to set the baseurl to an ip address if it was previously a ↵friendica2013-08-291-2/+14
| | | | dns name
* some basic mappings between comanche pages and normal pages so normal pages ↵friendica2013-08-281-5/+32
| | | | will still work
* right - here's how we're going to link comanche with webpagesfriendica2013-08-281-1/+1
|
* bring back mail list and cleanup some issues which popped out with full PHP ↵friendica2013-08-271-1/+3
| | | | warnings
* get rid of ssl_policy - it's implicit in the site urlfriendica2013-08-271-5/+5
|
* clone sync was trying to update xchan info in the abook loop.friendica2013-08-261-2/+3
|
* found the buggerfriendica2013-08-261-1/+5
|
* regex patchfriendica2013-08-261-0/+1
|
* Try to ensure full paths don't leak into xchan_addr and hubloc_addrfriendica2013-08-251-0/+5
|
* always use system provided baseurl if configuredfriendica2013-08-251-0/+22
|
* start timestamping hubloc connections so we can eventually remove dead onesfriendica2013-08-241-2/+5
|
* another issue with site renamefriendica2013-08-241-2/+2
|
* fix xchans more completely after a URL changefriendica2013-08-241-4/+13
|
* premium/restricted channel connections implemented, configure at ↵friendica2013-08-211-5/+12
| | | | yoursite/channel/nickname - this basically redirects "follow" requests to a premium channel's sell page if it has one configured. You can still click through and create a connection request (introduction), but this provides a means for the channel owner to state their terms. If you don't abide by the terms, you will likely be blocked or the channel deleted. This facility is extensible in a number of ways.
* progress on generic sellpage - is not yet linked from existing connect ↵friendica2013-08-211-5/+7
| | | | buttons and editing has not been completed
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 09:26:31 +0000