aboutsummaryrefslogtreecommitdiffstats
path: root/include/zot.php
Commit message (Collapse)AuthorAgeFilesLines
* tweaks to directory registrations which don't seem to be happening, also ↵friendica2015-03-191-0/+14
| | | | downgrade any directory that claims to be a primary directory for RED_GLOBAL.
* add missing %d for abook_closenessMichael Johnston2015-03-111-1/+1
|
* diaspora's spammy permission model seems to have leaked through our ↵friendica2015-03-101-2/+5
| | | | firehose. Don't let it.
* change default affinity (abook_closeness) to 80 for all new connections ↵friendica2015-03-081-1/+7
| | | | going forward (was 99). This way it can be adjusted down later without requiring you to change all your existing connections upward (since your existing connections are likely all sitting at 99 at the moment). The default setting is also configurable with a pconfig system.new_abook_closeness
* I'm going to use the site_update timestamp to indicate whenever we ↵friendica2015-03-031-0/+15
| | | | successfully connect with a site. This way we can mark hubs dead on non-directory servers; but we have to wait before implementing this until we have a history of site_update being updated.
* don't let a zot-finger bring a dead hub back to life unless it's the site ↵friendica2015-03-031-5/+7
| | | | we're currently talking to.
* make public delivery to contacts or any connections work againzottel2015-03-021-3/+2
| | | | $hash wasn't defined in this case
* Merge https://github.com/friendica/red into pending_mergefriendica2015-02-261-0/+3
|\
| * more fake null shenanigansHabeas Codice2015-02-261-0/+3
| |
| * Revert "more fake null shenanigans"Habeas Codice2015-02-261-23/+94
| | | | | | | | This reverts commit b57010e3da6c0521121a622c27013c8af7678132.
| * more fake null shenanigansHabeas Codice2015-02-261-94/+23
| |
* | loop breakerfriendica2015-02-261-0/+16
|/
* Found the cause of the delete looping, and I can prevent it going forward. ↵friendica2015-02-251-12/+37
| | | | The issue remains what to do about comments which are already in the DB and have ITEM_ORIGIN incorrectly set. We can't exactly reset them because the "original" context has been lost. (Sorry but couldn't resist an insider pun that none of you will be able to follow anyway). Read the comments.
* call post_local hooks prior to storing a post that is going to be sourced. ↵friendica2015-02-251-0/+7
| | | | There are some fields in the actual stored item that may change when we start the second delivery chain so a few plugins may not deal with these items correctly. Since we only source public items these effects will be slight.
* solve some (hopefully most) missing delivery issuesfriendica2015-02-251-13/+55
|
* public_recips cleanupfriendica2015-02-231-18/+30
|
* catch negative agesHabeas Codice2015-02-201-6/+7
| | | | nix extra var
* fix parens mismatch from last commitzottel2015-02-181-2/+2
|
* also deliver public posts to channels with channel_w_stream = PERMS_AUTHEDzottel2015-02-181-2/+2
|
* Merge branch 'master' of https://github.com/friendica/redHabeas Codice2015-02-161-1/+1
|\
| * force site_url to be lowercase when stored. Otherwise rating hubs on ↵friendica2015-02-151-1/+1
| | | | | | | | postgres could get real messy.
* | normalize age dataHabeas Codice2015-02-161-2/+7
|/ | | | | | | | mysql has type tinyint(3) which probably turns into a 24-bit value, but postgres uses 3-digit decimal as its constraint (probably what the mysql schema was intended to do). either that or mysql silently truncates while postgres respects the constraint. Either way, bad data gets in unchecked, now it's checked.
* missing paramfriendica2015-02-131-1/+1
|
* well that was certainly fun. And the reason why likes and other acitivity ↵friendica2015-02-111-3/+4
| | | | deletions weren't propagating. Hopefully this is the last reason and there aren't more lurking further down the chain.
* more efficient processing of response activities, plus a proof of concept ↵friendica2015-02-111-17/+44
| | | | fix for the problem of receiving a delete notification before we actually get the item which we're supposed to delete.
* Merge branch 'master' of https://github.com/friendica/redHabeas Codice2015-02-051-10/+34
|\
| * Merge branch 'master' into pocoratefriendica2015-02-031-0/+5
| |\
| | * garbage in garbage outfriendica2015-02-031-0/+5
| | |
| * | send rating information to directoriesfriendica2015-02-021-10/+29
| |/
* / escape datesHabeas Codice2015-02-051-1/+1
|/
* sync_locations() toggle DB flag functions were broken - result of postgres ↵friendica2015-01-301-4/+22
| | | | changes. Split these into seperate set and reset blocks.
* let zot_refresh continue without a primary hub if one cannot be found. also ↵friendica2015-01-301-5/+14
| | | | weekly doc updates
* local_user => local_channelfriendica2015-01-281-1/+1
|
* add yet another firehose checkfriendica2015-01-281-1/+1
|
* more minor tweaks to the route mismatch algorithm after watching it all day.friendica2015-01-281-2/+5
|
* ignore route mismatches on firehose posts to the sys channel. Use whatever ↵friendica2015-01-271-1/+1
| | | | parent route we have. By definition we aren't going to have permission issues with these things.
* we need to actually ask for the id from the DB if we want to use it.friendica2015-01-271-1/+1
|
* improved route mismatch detection. We will be less strict about the absolute ↵friendica2015-01-271-2/+22
| | | | route matching and only look at the last hop before it got to us - which is ultimately all we should care about (since that sender controls the thread permissions). Route mismatches seem to occur somewhat frequently from yamkote (for unknown reasons), and the logging has been improved a bit so it should provide some slightly more useful debugging info in case it still happens going forward. Oh, also we'll set the parent on comments when we store the initial post (item_store()) and only go back and set the parent for top-level posts. This should reduce the number of comments with missing parents on shared hosts, but may increase the number of missing threads. Probably worthwhile to do a query occasionally for parent = 0 and see how we're doing and how many have shared host related delivery issues.
* handle an incoming directory rating messagefriendica2015-01-261-2/+45
|
* remove superfluous group byHabeas Codice2015-01-241-1/+1
| | | | | this gets called from a zot post_post dealing with a specific messageid and hubloc_hash combination. grouping by site doesn't make sense here and it gets grouped when pulled back out elsewhere anyway
* zot_finger second arg is optional but function declaration didn't specify ↵friendica2015-01-211-1/+1
| | | | this - causes issue with check_upstream_directory
* connection clone issuesfriendica2015-01-101-0/+3
|
* don't update locally deleted itemsfriendica2015-01-061-3/+8
|
* don't import to sys channel from self-censored authorsfriendica2014-12-121-1/+11
|
* can't reset public to false because it may have been passed in as true and ↵friendica2014-12-011-5/+5
| | | | this would be wrong and cause even more subtle bugs. Reset to whatever value was passed in.
* Somewhat subtle process_delivery() bug - $public was not being reset if a sysThomas Willingham2014-12-011-0/+1
| | | | channel is reached but then the loop iterated over another channel.
* change logging of some troublesome or noisy bits so we can figure out what ↵friendica2014-11-191-2/+2
| | | | is really going on
* couple of fixes:friendica2014-11-191-0/+5
| | | | | - significantly increase the content availability on the discover channel - fix the button group on the blog/list mode which made the border on a single comment button a bit wonky
* there's still a permission issue delivering a public post directly to the ↵friendica2014-11-191-0/+2
| | | | sys channel (on the local system), but this puts the local sys channel in the public delivery chain and fixes an issue with unseen counts showing on the discover page (where you can't do anything about it).
* add sys channel to public recips if scope publicfriendica2014-11-181-0/+12
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-21 03:25:08 +0000