aboutsummaryrefslogtreecommitdiffstats
path: root/include/notifier.php
Commit message (Collapse)AuthorAgeFilesLines
* tag anyonefriendica2014-04-151-17/+3
|
* make sure we can find that functionfriendica2014-04-111-0/+1
|
* we also need a loop breakerfriendica2014-04-111-0/+6
|
* this should improve queue performance dramatically.friendica2014-03-241-2/+4
|
* we don't allow forgeries to be received - save some bandwidth by not ↵friendica2014-03-211-0/+5
| | | | allowing them to be sent. We do have to figure out how some secondary delivery chains are ending up with posts belonging to the original owner instead of the chain owner, but that's for another day.
* try to reduce the number of simulaneous deliveries of the same post when ↵friendica2014-01-221-2/+22
| | | | dealing with owner relays that have more than one channel instance. If things melt down in the next few hours and I'm not available please revert this. I've reviewed a few times and think it's OK, but this part of the delivery code is traditionally touchy.
* this is necessary for any possibility of a federated future.friendica2013-11-211-1/+16
|
* add aid to notifiy table which we may need to supress duplicate notify ↵friendica2013-11-201-4/+8
| | | | | | emails across your channels also try to handle the wretched mess of broken and duplicated hublocs that fred.cepheus.uberspace.de typically reports
* create update record for accounts on directory server itself during profile ↵friendica2013-10-241-1/+1
| | | | 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.
* preserve the source owner when creating a delivery fork so that we can ↵friendica2013-10-131-2/+3
| | | | uplink back to them without any ambiguity.
* Pieces we'll need to tie together chanman and account/channel deletion and ↵friendica2013-09-171-5/+30
| | | | | | | | 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?
* doc update, put more telemetry on notifier and try to ensure that private ↵friendica2013-09-131-0/+4
| | | | posts have recipients.
* perform a refresh_all when an import has completed so that all your ↵friendica2013-09-081-3/+2
| | | | connections get a fresh update.
* Add Comanche layouts to the things that don't go offsite.friendica2013-09-011-0/+4
|
* most of expire is now ported from friendica, but the protocol bits to push ↵friendica2013-08-141-4/+15
| | | | out the delete notifications for the entire batch to all recipients of the original post are not complete and will take quite a bit more work. As a consequence, expire has been completely disabled until it is fully implmented since it could result in completely un-removable posts reminiscent of the infamous "Bonnie Nadri" incident at Diaspora which we do not wish to re-live.
* block content-type (called ITEM_BUILDBLOCK to avoid confusion with content ↵friendica2013-08-121-0/+5
| | | | that is blocked)
* yhis should fix the privacy leak - as well as non-private replies to private ↵friendica2013-08-011-1/+4
| | | | posts
* privacy leakagefriendica2013-07-311-1/+1
|
* improvements in delivery loggingfriendica2013-07-211-8/+25
|
* fix profile update propagationfriendica2013-06-181-3/+3
|
* don't federate webpages ;-)friendica2013-06-151-0/+6
|
* push refresh messages, performance work on conversations and configs, doc ↵friendica2013-06-141-12/+51
| | | | updates
* zidify img links, delay notifier until actually published for time ↵friendica2013-05-271-0/+4
| | | | travelling posts
* workarounds for people that re-install and end up polluting everybody's ↵friendica2013-05-161-2/+2
| | | | databases with stale entries
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* delete item should now mostly workfriendica2013-01-281-1/+5
|
* uncomplicate item deletion and fixup all the other linked tablesfriendica2013-01-241-3/+4
|
* this should make tag delivery (e.g. forums) work - but not yet fully testedfriendica2013-01-131-3/+18
|
* never enough documentationfriendica2013-01-041-3/+14
|
* This should fix the errant relaying...friendica2013-01-041-2/+6
|
* fix typo - commited to wrong treefriendica2013-01-041-1/+7
|
* break delivery loopfriendica2013-01-041-1/+5
|
* verify table needs auto_increment flagfriendica2013-01-021-2/+2
|
* cleanup more obsolete stufffriendica2012-12-181-2/+2
|
* y'all got mailfriendica2012-12-051-51/+75
|
* Now if you follow somebody it will create an abook entry on the other site ↵friendica2012-11-291-1/+3
| | | | with blocked,ignored, and pending set. No "friend notifications" yet.
* got comments going back and forth - we really need local_deliver now since ↵friendica2012-11-271-10/+10
| | | | even local deliveries are going through zot and that isn't necessary or desirable in the long term
* tracking through commentsfriendica2012-11-271-3/+9
|
* DATABASE: outq additions, delivery now getting the notify across to the ↵friendica2012-11-191-2/+5
| | | | other side
* For private messages, use hush-hush ultra top-secret mode by defaultfriendica2012-11-181-7/+7
|
* Now we are able to get a zot notification packet and the resulting json ↵friendica2012-11-181-535/+50
| | | | encoded message into the queue, it's still a hard slog, but there's light at the end of the tunnel - "a message is ready and waiting to be delivered".
* little stufffriendica2012-11-161-4/+19
|
* more progress on notifier cleanup and encoding items for transit.friendica2012-11-151-10/+77
|
* starting the big notifier cleanupfriendica2012-11-141-62/+64
|
* got zotfriendica2012-11-121-17/+50
|
* likes are quasi working again - at least an activity item is stored and it ↵friendica2012-11-051-2/+2
| | | | mostly has correct data, but displaying it needs improvement.
* "profile url" e.g. the wall/stream is now "channel url". "Profile URL" goes ↵friendica2012-10-291-1/+1
| | | | to the profile details.
* more cleanupMike Macgirvin2012-10-231-49/+0
|
* updatesfriendica2012-09-091-4/+4
|
* more DB cleanupfriendica2012-08-301-6/+6
|