aboutsummaryrefslogtreecommitdiffstats
path: root/include/zot.php
Commit message (Collapse)AuthorAgeFilesLines
* don't store update records if we're not a directory server of some kindfriendica2013-11-041-0/+5
|
* allow zot public providers to list their location, as a non US-based server ↵friendica2013-10-301-3/+7
| | | | could be a strong selling point.
* access policy and directory mode were crossed on site table creationfriendica2013-10-301-1/+1
|
* send rpost requests from remote sites back to yours.friendica2013-10-291-2/+2
|
* rpost bbcode tagfriendica2013-10-291-0/+11
|
* create update record for accounts on directory server itself during profile ↵friendica2013-10-241-5/+8
| | | | changes, re-queue failed directory sync packets, fix account_id index in queue creation, be more selective about updating hubloc_connected (only when we're talking to the associated site). But we still need a way to flag dead accounts and these mechanisms won't cut it, because it isn't a requirement that channels communicate with anybody, except for contacting the directory when the account is created. I think we need to make every channel ping the directory once a month. Then we can find those that have not done so (after syncing with other directories). We can't have the directory just flag dead accounts as this would create a way for an anti-social attacker to become a directory server and mark all the accounts dead.
* update even if no changefriendica2013-10-141-0/+8
|
* sql wrong number of argsfriendica2013-10-141-0/+1
|
* bring back photo shadows (via theme settings)friendica2013-10-021-1/+2
|
* post signaturesfriendica2013-10-021-0/+8
|
* that would've messed it upfriendica2013-10-021-1/+1
|
* block forgeriesfriendica2013-10-021-3/+18
|
* in probe diagnostic - note https failure as diagnostic info - this also ↵friendica2013-10-011-3/+3
| | | | changes zot_finger so you can tell it not to fallback. This could be useful in corporate environments that are off the grid or other high security situations (as much as anything could be considered high security which relies on SSL).
* directory sync - this will either work, or it won't work, or it will ↵friendica2013-09-301-7/+15
| | | | | | | | | 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.
* ret_secret is not usedOlaf Conradi2013-09-301-5/+0
|
* structure for channel unionsfriendica2013-09-261-1/+2
|
* suppress creating the directory update record for profile updates which are ↵friendica2013-09-251-4/+4
| | | | 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.
* populate the new fields in the directory updates tablefriendica2013-09-241-9/+17
|
* adult channel settingfriendica2013-09-221-0/+7
|
* is_commentable() had some major issues when applied to the atrocity known as ↵friendica2013-09-201-1/+4
| | | | | | ConversationObject, hopefully this won't destabilise the network as it's a somewhat major permission tweak related to comments; also add any local clones to allowed_public_recips() as they should always be allowed recipients. Not sure what to do about host permissions in the event of clones. They have more than one host, and it isn't spelled out in the sent message. All of this stuff will make your head hurt.
* missing hashfriendica2013-09-191-1/+2
|
* provide a "safe search" backend and allow for self-censorship using nsfw or ↵friendica2013-09-191-0/+10
| | | | 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.
* trim commas from keywordsfriendica2013-09-191-0/+1
|
* add "tiered" access policy, add tagcloud to directory pagesfriendica2013-09-181-0/+2
|
* site sellpage linksfriendica2013-09-171-4/+8
|
* Pieces we'll need to tie together chanman and account/channel deletion and ↵friendica2013-09-171-0/+10
| | | | | | | | 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?
* found itfriendica2013-09-151-3/+3
|
* more loggingfriendica2013-09-151-0/+3
|
* don't create a directory sync notification (entry in the updates table) if ↵friendica2013-09-151-17/+30
| | | | the site record was updated - without checking first to see if anything changed. This is causing lots of sync entries when nothing changed to warrant it.
* implement what I hope will now be the server side of directory sync, add ↵friendica2013-09-151-5/+12
| | | | viewsrc to item_photo_menu, and log what changed in import_xchan update objects so we can find out why there are so many updates when nothing _obvious_ has changed that should trigger it.
* some fixes to directory keyword searchesfriendica2013-09-141-1/+1
|
* import_xchan - check every known hubloc/location field and create a new ↵friendica2013-09-141-4/+8
| | | | hubloc if anything at all changed anywhere.
* need to figure out what's causing thisfriendica2013-09-121-0/+6
|
* so public_recips and allowed_public_recips is working so much better than ↵friendica2013-09-121-4/+12
| | | | before, but was still not quite right. We seem to be getting all the right results for top-level posts now, but comments aren't getting through on channels for which we've allowed them to send us their stream, but not comment on our posts. The reason is we were seeing if they could comment - and we only need to do that if we own the post. If they own the post, we only need to check if they can send us their stream.
* Merge pull request #129 from MicMee/masterfriendica2013-09-121-1/+2
|\ | | | | to flag failed auth attempts in db table hubloc as hubloc_receive_error
| * delete logger line; was the wrong place.Michael Meer2013-09-111-1/+0
| |
| * flag failed auth attempts in DB table hublocMichael Meer2013-09-111-1/+3
| |
* | assuming this doesn't blow up the internet like the last fix - this is a ↵friendica2013-09-111-1/+1
|/ | | | very old bug that's been reported time and time again and nobody every bothered to debug or even report it somewhere where we could monitor it. It's buried somewhere in my stream, but basically is "things don't work right if you've got 'everybody in my address book' permissions" on "can send me their channel stream and posts". I think this is Michelle's problem and anybody else who has en empty matrix after making lots of connections.
* well that really stuffed things up...friendica2013-09-101-2/+2
|
* provide detailed error to remote site for the myriad of things that can go ↵friendica2013-09-101-4/+8
| | | | wrong inside item_store(), !! this changes the return of item_store !!
* just a typoMichael Meer2013-09-091-1/+1
|
* some alteration to the way directory sync was originally supposed to work. ↵friendica2013-09-091-25/+14
| | | | I'm making this up as I go and not exactly certain where to go next but it makes more sense now and I think the basic idea will actually work. I'll just have to keep making it up until it does work.
* make sure new contacts who are not yet in the address book are sync'd across ↵friendica2013-09-081-0/+14
| | | | clone instances
* public site list (will take a few days to populate, assuming folks have ↵friendica2013-09-051-3/+16
| | | | updated their site access policy which old sites do not have)
* update hubloc_timestampsfriendica2013-08-271-5/+14
|
* clone sync was trying to update xchan info in the abook loop.friendica2013-08-261-1/+1
|
* more cleanup from the mess yesterday - you might have a look for xchan_addr ↵friendica2013-08-261-0/+3
| | | | and hubloc_addr with slashes in them and fix them - especially getting rid of ip addresses and the /channel/xyz in the addr fields
* try to fix bad addresses that got into the networkfriendica2013-08-251-0/+3
|
* Try to ensure full paths don't leak into xchan_addr and hubloc_addrfriendica2013-08-251-1/+1
|
* possible fix for mention tags not posting to mentioned forum (when send ↵friendica2013-08-221-3/+25
| | | | stream permission is blocked)
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 16:52:46 +0000