aboutsummaryrefslogtreecommitdiffstats
path: root/include/feedutils.php
Commit message (Collapse)AuthorAgeFilesLines
* process activity deletes from OStatus which for whatever reason do not use ↵zotlabs2017-09-271-37/+58
| | | | the industry standard tombstone mechanism
* ostatus - support likes of commentszotlabs2017-09-241-11/+19
|
* pubcrawl: make a good faith effort to handle multi-media contentzotlabs2017-09-181-1/+1
|
* provide rel=alternate link if no reshare content in postzotlabs2017-09-181-0/+5
|
* include the mastodon summary in the postzotlabs2017-08-101-2/+2
|
* ostatus feed was missing commentszotlabs2017-08-061-1/+1
|
* provide a better "is_commentable" default for OStatus conversations that ↵zotlabs2017-07-301-1/+12
| | | | were fetched on the fly
* issue with OStatus comments being propagated downstreamzotlabs2017-07-261-0/+15
|
* remove activitypub components from corezotlabs2017-07-261-182/+0
|
* begin the tedious process of mapping activities between AS1, zot, and AS2zotlabs2017-07-201-0/+49
|
* implement update_feed_itemzotlabs2017-07-191-3/+12
|
* provide optional salmon signatures for AP entitieszotlabs2017-07-181-0/+8
|
* some corrections to AS encoding based on the current spec (some of this work ↵zotlabs2017-07-171-7/+22
| | | | was completed long before the spec settled).
* activitypub, cont.zotlabs2017-07-171-14/+26
|
* activitystreams converters updated to recent speczotlabs2017-07-171-12/+14
|
* mis-attributed profile photo when Mastodon comment author has no profile photozotlabs2017-07-161-0/+11
|
* deal with mastodon privacy scopes - mark private and block commenting since ↵zotlabs2017-07-151-1/+20
| | | | we refuse to send private activities through the public OStatus connector.
* fix typoszotlabs2017-07-121-6/+8
|
* make websub/PuSH and salmon both use consume_feed() for item storage as ↵zotlabs2017-07-121-13/+43
| | | | there is a lot of duplication of effort and patches applied to one that haven't been applied to the other. This will require an update of addons as well or follow activities may be duplicated
* even more logging of conversation parent discoveryzotlabs2017-07-111-0/+1
|
* find_parent for feeds needs more debug logging. Something is still falling ↵zotlabs2017-07-091-0/+4
| | | | through the cracks and it isn't obvious why
* some sites use the old style ostatus:conversation xml field, check for it.zotlabs2017-07-041-2/+9
|
* duplicated posts after conversation fetchzotlabs2017-06-301-0/+11
|
* use "Full Name (username)" for ostatus commenter xchanszotlabs2017-06-291-2/+28
|
* forgot to return true from the conversation_fetch routine - which triggers ↵zotlabs2017-06-291-0/+2
| | | | the rescan for potential parent posts
* log the conversation so we can debug this easierzotlabs2017-06-281-0/+1
|
* conversation fetching is partially working - but it isn't always glueing the ↵zotlabs2017-06-281-7/+20
| | | | conversation pieces together.
* pretend it's a real feed even though it isn'tzotlabs2017-06-281-2/+12
|
* add loggingzotlabs2017-06-281-0/+3
|
* more refetch testingzotlabs2017-06-281-1/+1
|
* refetch testingzotlabs2017-06-281-1/+1
|
* translate 'favorite' verb to 'like' if it's an ostatus feedzotlabs2017-06-271-6/+15
|
* log conversation fetches (also a missed / char in the string replace)zotlabs2017-06-271-1/+3
|
* (untested currently) fetch conversation for GNU-Social and Mastodon when ↵zotlabs2017-06-271-1/+47
| | | | provided a comment with no local copy of the parent.
* support linked media (audio/video) elements in feeds as well as imageszotlabs2017-06-261-4/+17
|
* in gnu-social reshare objects are activities, not posts or commentszotlabs2017-06-261-1/+1
|
* add ostatus attached photos (inline to the post body) even if there's a link ↵zotlabs2017-06-261-1/+1
| | | | to the photo in the post but it isn't wrapped in an img tag.
* mastodon reshares can be either posts or comments; silence warning from ↵zotlabs2017-06-251-1/+1
| | | | guess_image_type when handed a URL to a non-existent resource.
* testing mastodon boosts/reshareszotlabs2017-06-191-14/+35
|
* remove some duplicated codezotlabs2017-06-151-13/+13
|
* always transmit a valid urizotlabs2017-06-151-0/+4
|
* use parent_midzotlabs2017-06-151-2/+2
|
* sigh... x-zot prefix slipped in againMario Vavti2017-06-151-1/+1
|
* typoMario Vavti2017-06-151-1/+1
|
* re-add type since the actual culprit was the X-ZOT prefixMario Vavti2017-06-141-1/+1
|
* thr:in-reply-to seems to must not have a type set. there is no mention of ↵Mario Vavti2017-06-141-1/+1
| | | | this in the spec and replies will be shown as replies in mastodon this way.
* support mastodon content warnings by converting into n-s-f-w tagzotlabs2017-06-141-0/+8
|
* attempt to group gnu-social and mastodon conversations by ↵zotlabs2017-06-141-10/+25
| | | | ostatus:conversation in addition to falling back on thr:in_reply_to
* preserve the ostatus:conversation pointer alsozotlabs2017-06-141-1/+8
|
* ostatus is almost unrecognisable these days from its former self. In this ↵zotlabs2017-06-141-3/+15
| | | | case thr:in-reply-to has almost no meaning since it almost never refers to a top level post; which makes it quite difficult to preserve conversations