aboutsummaryrefslogtreecommitdiffstats
path: root/include/zot.php
Commit message (Collapse)AuthorAgeFilesLines
* undo self-deliver checkredmatrix2015-09-301-5/+6
|
* process_delivery: ignore selfredmatrix2015-09-281-0/+6
|
* well there's one problem...redmatrix2015-09-271-4/+4
|
* add some safety checks on the sending side of syncredmatrix2015-09-271-6/+20
|
* don't send sync packets to deleted hubloc locationsredmatrix2015-09-221-2/+4
|
* inverted logic syncing deleted hublocsredmatrix2015-09-221-1/+1
|
* add names to delivery report for sync deliveryredmatrix2015-09-221-1/+3
|
* report the channel syncredmatrix2015-09-221-1/+11
|
* backport item syncredmatrix2015-09-221-0/+85
|
* new delivery report formatredmatrix2015-09-201-13/+33
|
* improve on the last attemptredmatrix2015-09-201-4/+4
|
* catch the timestamp alsoredmatrix2015-09-201-1/+1
|
* remove system flags from channel import packetredmatrix2015-09-201-5/+9
|
* we need the xchan record alsoredmatrix2015-09-201-1/+1
|
* clone new connection requestsredmatrix2015-09-191-18/+19
|
* include site identitfier on redmatrix delivery reports alsoredmatrix2015-09-181-0/+2
|
* log the remote message if there was oneredmatrix2015-09-111-1/+4
|
* another tactic to deal with orphan hublocs from re-installs, or at least ↵redmatrix2015-09-111-18/+34
| | | | allow the descendant channel to survive
* zot_refresh: always try the hubloc pointed to by xchan_addr firstredmatrix2015-09-101-3/+12
|
* protect from sql injectionredmatrix2015-09-021-1/+1
|
* really fix post filteringzottel2015-09-021-2/+2
|
* issues with abook sync between hubzilla and redredmatrix2015-08-231-2/+1
|
* Properly fix which perms get checked for comments, Mike's solutionAlexandre Hannud Abdo2015-08-141-14/+3
|
* revert 36b5f6acredmatrix2015-08-121-12/+14
|
* Require comment perms only for own posts, allow senders to deliver comments ↵Alexandre Hannud Abdo2015-08-101-1/+11
| | | | using stream perms.
* patch to allow theme based widgetsredmatrix2015-07-231-1/+2
|
* fix for empty recip array resulting from a mangled xchanredmatrix2015-07-151-5/+8
|
* clone sync fixes across red/hzredmatrix2015-07-151-2/+7
|
* coverup and ignore the illegal string offset message that some sites have ↵redmatrix2015-07-141-1/+3
| | | | been reporting. This does not fix it. A fix would be to examine the data that has been received and find out why it is mangled and trace this back to where it was mangled.
* a few clone sync fixes as well as some work on hubzilla clone sync back to ↵redmatrix2015-07-021-0/+22
| | | | redmatrix
* no this isn't it. well ok, it's part of it, but not the important part. it's ↵redmatrix2015-06-281-14/+31
| | | | still pretty cool.
* some work on issue #329redmatrix2015-05-251-3/+4
|
* cloning abook entries was broken in several ways if the target xchan wasn't ↵redmatrix2015-05-201-16/+5
| | | | available on the clone site. This should make it less broken.
* Some documentation and whitespaces at line endings.Klaus Weidenbach2015-04-101-223/+325
|
* Correcting reported Doxygen syntax warnings.Klaus Weidenbach2015-03-291-413/+380
| | | | | | | Fixed wrong Doxygen syntax and add some of the available FIXME to Doxygen documentation. Updated Doxygen configuration to add also all capital letter tags. Adding some more Doxygen documentation.
* 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
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 15:48:44 +0000