aboutsummaryrefslogtreecommitdiffstats
path: root/boot.php
Commit message (Collapse)AuthorAgeFilesLines
* allow objects to have permissionsfriendica2013-12-281-1/+1
|
* db update for directory profiles - and fix broken database.sql from the ↵friendica2013-12-251-1/+1
| | | | sys_perms addition a couple days back
* add account_level, is_foreigner and is_member functions; convert all e2ee ↵friendica2013-12-231-1/+1
| | | | user input and prompts to hex to avoid javascipt's lame handling of quotes. !!This breaks all prior encrypted posts.!!
* remove a couple of mysql reserved words from being used as table or row ↵friendica2013-12-221-1/+1
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* Some sys chan stuffThomas Willingham2013-12-221-6/+6
|
* remove the .wgl (widget list) file processing for ordering widgets on a ↵friendica2013-12-181-37/+1
| | | | page. This preceded Comanche and was never used and is now obsolete.
* Add App::poi to store the "person of interest" for a given page. This is so ↵friendica2013-12-181-5/+6
| | | | we can comanchificate the vcard_from_xchan widget -- it will pick up the target xchan from the page environment.
* bloody hell... php version incompatibility with openssl - openssl no longer ↵friendica2013-12-151-1/+8
| | | | accepts a string as an algorithm. Earlier versions didn't recognise sha256. So we'll look to see if the algorithm constant for sha256 is defined and if so we'll use that instead of the string.
* Provide a fallback channel to probe for magic-auth when we have no prior ↵friendica2013-12-151-1/+5
| | | | | | | | communications with a site. This will be a system channel if one exists, otherwise any channel will do. We'll try to use the first valid channel on the site because that was probably created when the site was installed and is the closest thing to a system channel we've got.
* add construct_page hookfriendica2013-12-131-0/+4
|
* The affinity tool is not a "traditional" widget. But it is nevertheless a ↵friendica2013-12-111-1/+2
| | | | widget. It just makes fewer page layout decisions which are hard-coded. If you want to shrink it down and put it on the sidebar in your theme, go for it.
* mod channel is now Comanchifiedfriendica2013-12-101-1/+0
|
* look for comanche module pages using theme_include()friendica2013-12-101-2/+2
|
* matrix/network page under Comanche cont.friendica2013-12-101-0/+2
|
* mod_network is now running under Comanche. Yay.friendica2013-12-101-1/+4
|
* reorganise a few included functions - notably identity related functionsfriendica2013-12-031-642/+2
|
* deprecate a->get_curl_code() and $a->get_curl_headers()friendica2013-12-011-20/+0
|
* allow themes to mess with the navbar contents without a custom template. ↵friendica2013-11-281-1/+2
| | | | | | | | | | | | It's done as a callback using a transient plugin hook. For instance to get rid of the notifications link: insert_hook('nav','strip_notify'); function strip_notify($a,&$b) { unset($b['nav']['notifications']); }
* replaced rhash icontuscanhobbit2013-11-231-1/+1
|
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 14:41:54 +0000