aboutsummaryrefslogtreecommitdiffstats
path: root/include/zot.php
Commit message (Collapse)AuthorAgeFilesLines
* improvement in source route checking when handling complex *upstream* ↵friendica2014-10-101-6/+19
| | | | delivery chains, which were not adequately accounted for in the earlier checkin.
* allow (our own) ajax urls to pass through bbcode intact.friendica2014-10-091-1/+2
|
* OK this is important. So read it carefully.friendica2014-10-091-3/+33
| | | | | | | | This checkin implements route matching of comments so that they are only accepted from the same route as the top-level post they are attached to. This way there should be no mis-match of permissions between any posts in the thread. It may not be completely compatible with comments posted in the past (though I've tried to be, there may be some minor issues). In addition it seems that relaying was invoked more often than necessary - especially when a duplicate post arrived which was not processed because the edited time hadn't changed - it still invoked relaying. This fix should improve site performance considerably for comments cross-posted to forums; which got bounced around a bit and delivered redundantly for no reason. Roll this back *only* if it causes a meltdown or comment loss is "serious" (as in OMG people are dying, make it stop!). If we can get past 24 hours without serious issue we need to get everybody onto this code. There may be some minor comment loss (mostly affecting new comments to older posts or likes of older comments) until the majority of sites have moved to the new code. It may be difficult or impossible to deliver comments to posts that pre-date the addition of source routes (April 1, 2014) to anybody but the top-level post author at his/her primary hub. We may wish to close comments on these posts, but let's see how we go before doing that.
* ability to pre-populate connections for new channels. e.g. "MySpace Tom"friendica2014-10-011-2/+0
|
* found the suckerfriendica2014-09-221-2/+2
|
* just mark dead hubloc deleted - don't remove them. This could cause ↵friendica2014-09-161-2/+4
| | | | problems. Also clean up fetch_url/post_url header option
* honour service class restrictions for total_identities, total_channels ↵friendica2014-09-151-4/+36
| | | | ("friends") and total_feeds both when importing channels and subsequently when syncing clones. Limits are based on the local system - additional entries are silently dropped.
* provide a way to sync locations and get rid of bogus hublocs, now implementedfriendica2014-09-141-2/+8
|
* pull the plug on the old location sync section of import_xchan - this has ↵friendica2014-09-141-168/+12
| | | | | | now been split off into its own function. Cross fingers because this is core functionality which was tried and true, well tested; and now it's a bit different. Please revert this if the matrix breaks in the next few hours.
* more heavy lifting on the hubloc management and revocation infrastructure; ↵friendica2014-09-141-10/+51
| | | | don't rush me. This is going to become a fundamental part of zot. It deserves careful consideration.
* some backend work for the remaining missing bits of mod_hubman - this is ↵friendica2014-09-131-2/+200
| | | | still a fair ways from being complete and is not ready for prime time. Basically we'll let a channel send out a public message saying "these are my currently approved locations" and anything that isn't in the list will be marked deleted. We'll send out this message when locations change somehow - either through direct personal involvement (hub revoke, change primary, channel import) or during a system rename or "find bad/obsolete hublocs" activity. This way we won't have clones sending back location info we just got rid of and re-importing the bad entries.
* don't allow an xchan to be imported with an empty name. To avoid translation ↵friendica2014-09-111-2/+2
| | | | issues we'll just make it '-'.
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-1/+1
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* realm detection logic reversedfriendica2014-09-041-1/+1
|
* sql error in profile_activityfriendica2014-08-311-4/+2
|
* lots of little Diaspora issuesfriendica2014-08-281-6/+7
|
* works one way sort of - now to go the other way - which will require fixing ↵friendica2014-08-261-1/+4
| | | | a whole slew of FIXMEs
* sort out some anomaliesfriendica2014-08-251-1/+12
|
* We really can't do this without a hubloc. I was hoping we could, but ↵friendica2014-08-221-2/+3
| | | | notifier is setup to take hublocs, not xchans.
* provide the site blacklist everywhere it is neededfriendica2014-08-211-0/+16
|
* some more work on realmsfriendica2014-08-171-3/+4
|
* add collections widget to connections page - and some more work on realmsfriendica2014-08-171-1/+15
|
* provide backend storage and declaration of directory realmfriendica2014-08-161-2/+5
|
* don't block "public" messages with authenticated scopezottel2014-08-151-1/+1
|
* zot logging to figure out why we occasionally don't have an address on ↵friendica2014-08-121-0/+4
| | | | xchan_import - I suspect we don't have anything useful at all.
* got the logic reversed on that onefriendica2014-08-071-1/+1
|
* over-ride the private flag if we received a post that isn't completely ↵friendica2014-08-071-1/+13
| | | | public, but they didn't set the private flag.
* public scope delivery issuesfriendica2014-08-061-3/+11
|
* clone sync of "unfriend" actionsfriendica2014-08-051-0/+15
|
* add an encoding type to formatted zot communication structures so that we ↵friendica2014-07-241-5/+1
| | | | can later add alternate encodings.
* ensure that we don't have permission settings issues due to version skew ↵friendica2014-07-171-1/+1
| | | | across sites.
* collection sync issuefriendica2014-07-171-0/+25
|
* collection syncfriendica2014-07-161-0/+114
|
* limit fields to what we requirefriendica2014-07-141-1/+1
|
* index collection sync info by hash rather than idfriendica2014-07-141-1/+1
|
* clean up more code duplicationfriendica2014-07-141-6/+20
|
* the sending side of clone syncing of collection/privacy_group information. ↵friendica2014-07-141-1/+15
| | | | The receiving side is not yet implemented.
* much better fix to problem yesterday of updates with the wrong ud_addr ↵friendica2014-06-301-23/+16
| | | | | | getting updated. Now we'll pass in the update table row to import_xchan so we know exactly which ud_addr applies. We still need ud_flags passed in separately.
* control chars crept in.friendica2014-06-301-1/+1
|
* ensure we have a unique guid for each address if one is generated.friendica2014-06-301-1/+1
|
* update the update records for all addresses attached to this channel, not ↵friendica2014-06-301-7/+19
| | | | just the primary.
* Implements a new permission level PERMS_PENDINGAlexandre Hannud Abdo2014-06-191-11/+15
| | | | | | | | | | | | | | | | With this a user can allow some action to any user which connects to them, even before they've connected back. Ref. https://mobiliza.org.br/display/478d9e71eaf55748dc646d3990651d6d34cfb7db5c38360538ec730ca3ccf908@zothub.com Also some code cleanup and an alternative logic for handling notifications of permission changes in zot.php. This assumes that private posts are still restricted to people in your addressbook. Regardless of your global permissions, a pending channel won't get private posts, even if the post only has a deny clause not matching the pending channel.
* note work still remainingfriendica2014-06-171-0/+1
|
* sync profiles to nomadic clonesfriendica2014-06-171-0/+39
|
* send new connection notification even if auto-perms are setfriendica2014-06-121-1/+1
|
* duplicate birthday events showing upfriendica2014-06-041-0/+7
|
* bring back birthdaysfriendica2014-06-021-2/+11
|
* Merge branch 'master' into neweventfriendica2014-05-291-1/+21
|\ | | | | | | | | Conflicts: include/zot.php
| * cleanup dead directory entries. This was a real b#tch, so keep your eye out ↵friendica2014-05-281-0/+18
| | | | | | | | for issues - which you shouldn't see until next weekend when this is scheduled to run. We're only setting flags, so if anything goes wrong we should be able to recover without too much pain.
| * add activity_received hookfriendica2014-05-131-0/+3
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 16:44:52 +0000