aboutsummaryrefslogtreecommitdiffstats
path: root/include/notifier.php
Commit message (Collapse)AuthorAgeFilesLines
* issue with dead hub detectionredmatrix2015-11-151-1/+1
|
* improve /locs page with some field notes and the ability to do a forced syncredmatrix2015-11-011-1/+1
|
* new feature: delayed postingredmatrix2015-10-251-1/+1
|
* fix typo in include/notifier.phpMario Vavti2015-10-191-1/+1
|
* separate permission_update notification into permission_create and ↵redmatrix2015-10-181-2/+7
| | | | permission_update, since some networks send out a notification for duplicate share requests even if connected.
* mail sync/migrate continued; also abstract delivery loop to make it ↵redmatrix2015-10-151-59/+43
| | | | re-usable, change refresh_all to use delivery loop.
* need full path to deliver_hooks.phpredmatrix2015-10-021-1/+1
|
* more work on the notifierredmatrix2015-09-291-1/+6
|
* remove redundant coderedmatrix2015-09-241-7/+1
|
* delivery optimisationsredmatrix2015-09-241-8/+25
|
* heavy lifting for delivery reportsredmatrix2015-09-221-0/+12
|
* don't deliver to dead hubsredmatrix2015-09-141-25/+18
|
* remove xchan_instance_url - it needs to be an abook field, not an xchan fieldredmatrix2015-09-141-14/+0
|
* begin moving diaspora to pluginredmatrix2015-08-021-18/+8
|
* Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-06-291-1/+10
|\ | | | | | | | | | | Conflicts: view/nl/messages.po view/nl/strings.php
| * some prep workredmatrix2015-06-291-1/+10
| |
* | convert the abook fieldsredmatrix2015-06-141-2/+1
| |
* | Merge branch 'master' of https://github.com/redmatrix/redmatrixredmatrix2015-05-271-0/+2
|\| | | | | | | | | Conflicts: mod/impel.php
| * fix for forked thread on diasporaredmatrix2015-05-271-11/+0
| |
| * revert for nowredmatrix2015-05-271-5/+5
| |
| * Comments need to have some kind of routing instructions.redmatrix2015-05-261-0/+13
| |
* | fix some merge errorsredmatrix2015-05-181-1/+1
| |
* | Merge branch 'master' into tresfriendica2015-04-291-7/+15
|\| | | | | | | | | Conflicts: include/notifier.php
| * disconnectfriendica2015-04-231-7/+15
| |
* | Merge branch 'master' into tresfriendica2015-04-231-9/+45
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Contact.php include/ItemObject.php include/api.php include/attach.php include/diaspora.php include/dir_fns.php include/enotify.php include/event.php include/expire.php include/items.php include/notifier.php include/notify.php include/photos.php include/taxonomy.php include/text.php include/widgets.php include/zot.php mod/admin.php mod/channel.php mod/dirsearch.php mod/display.php mod/editwebpage.php mod/events.php mod/home.php mod/item.php mod/manage.php mod/mood.php mod/network.php mod/page.php mod/photos.php mod/ping.php mod/post.php mod/thing.php mod/viewsrc.php view/css/mod_events.css
| * more work on queue optimisationsfriendica2015-03-091-3/+18
| |
| * Fix a couple of places where we weren't checking for dead hublocs. Add a ↵friendica2015-02-271-5/+14
| | | | | | | | function to mark a hubloc dead.
| * syntax - missing argfriendica2015-02-251-1/+1
| |
| * this may actually fix the deliver loop when deleting existing items. It's ↵friendica2015-02-251-1/+8
| | | | | | | | hackish but I don't see any other way out.
| * Found the cause of the delete looping, and I can prevent it going forward. ↵friendica2015-02-251-2/+7
| | | | | | | | 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.
| * don't send deleted items upstream - only downstream.friendica2015-02-241-3/+6
| |
* | Merge branch 'master' into tresfriendica2015-02-051-14/+0
|\| | | | | | | | | | | Conflicts: view/css/mod_events.css view/theme/redbasic/css/style.css
| * send rating information to directoriesfriendica2015-02-021-14/+0
| |
* | Merge branch 'master' into tresfriendica2015-01-311-0/+10
|\| | | | | | | | | Conflicts: include/zot.php
| * updates to put rating info into the local xlink before sending it to known ↵friendica2015-01-281-0/+10
| | | | | | | | directory servers
* | more message restrict conversionsfriendica2015-01-291-3/+6
| |
* | start on item_restrict conversionfriendica2015-01-221-4/+3
| |
* | heavy lifting converting item flag bitsfriendica2015-01-221-5/+4
| |
* | slow progress removing bitfields on item tablefriendica2015-01-211-2/+1
| |
* | that should take care of the bitfields in hublocfriendica2015-01-201-1/+1
| |
* | first cut at unpacking bitfields in hubloc, fixed hubloc_error and ↵friendica2015-01-201-5/+2
|/ | | | hubloc_deleted
* include channel clones in PM deliveries (also some whitespace edits)friendica2015-01-081-0/+1
|
* make unique hub filter more robust and straight-forward so it's easier to ↵friendica2014-12-171-7/+25
| | | | understand and debug since it's such a critical piece of the delivery chain
* critical notifier fix to make diaspora delivery work reliably again. If ↵friendica2014-12-171-18/+11
| | | | everything breaks revert or debug.
* PostgreSQL support initial commitHabeas Codice2014-11-131-7/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were 11 main types of changes: - UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just copied from Friendica. All of these instances, the LIMIT 1 was simply removed. - Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice to boot). Proper explicit boolean conversions were added. New queries should use proper conventions. - MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_ func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There were no true toggles (XOR). New queries should refrain from using XOR when not necessary. - There are several fields which the schema has marked as NOT NULL, but the inserts don't specify them. The reason this works is because mysql totally ignores the constraint and adds an empty text default automatically. Again, non-compliant, obviously. In these cases a default of empty text was added. - Several statements rely on a non-standard MySQL feature (http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run a zillion times faster, even on MySQL. - A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG, UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_ - INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes around the value -- assist functions added in the dba_ - NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are handled in Zot/item packets automagically by quoting all dates with dbescdate(). - char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype for all text fields in the postgres schema. varchar was used in a couple of places where it actually seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code actually validates data, new bugs might come out from under the rug. - postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted. bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function was added to handle this transparently. - postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax. Statements were updated to be standard. These changes require corresponding changes in the coding standards. Please review those before adding any code going forward. Still on my TODO list: - remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting - Rewrite search queries for better results (both MySQL and Postgres)
* disable request message response until we work through thisfriendica2014-11-011-1/+0
|
* What this checkin does is catch the case where a comment arrived and there's ↵friendica2014-10-301-0/+35
| | | | a missing top-level post to match it with. So we'll send a request back to the sender that you've never seen this thread and please send a fresh copy of the entire conversation to date. We could soon have posts in the matrix from different platforms from days gone by, which have been migrated into the modern world. We'll be polite and not deliver these to everybody. However, if someone comments on one of these antique threads we wouldn't be able to see it in our own matrix because we won't have a copy of the parent post. So this rectifies that situation. Be aware that item deletion may need to change to keep "hard deleted" items indefinitely so that they don't keep coming back. We'll have to null out the important data of the former item to accomplish the deletion aspect.
* d* PM cont.friendica2014-09-231-1/+1
|
* found the suckerfriendica2014-09-221-0/+2
|
* we don't always set HUBLOC_FLAGS_DELETED but we often set hubloc_status = ↵friendica2014-09-211-2/+3
| | | | HUBLOC_OFFLINE instead. Filter this as well from deliveries.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-02 04:59:16 +0000