actor
on non-Activity objects
Merged upstream in MR 4105 https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4105 and commit e944b1529862a2a40158803da5fe04a024f7aa4f https://git.pleroma.social/pleroma/pleroma/-/commit/e…
actor
on non-Activity objects
Intuitively i’d expect other implementations to just ignore the extra actor field. Does this cause issues with JSON-LD normalisation or other kinds of issues?
It causes problems for…
actor
on non-Activity objects
as above: replace this sort with a second filter that only runs if no tags have a rel=quote
is this a valid assumption? should any Link with a correct mediaType be considered a quote? should you only consider the first object link, or should you maybe consider object links that are at the end of content
?
type
may not be always Link
. it may be an extension or subclass of Link
. a Link is just a node that has href
(and optionally rel
, mediaType
, name
, hreflang
, height
, width,
preview`)
i'd instead do toArray(tags).filter(hasRel)
because the link relation is what is doing all the semantic heavy-lifting
a user on another instance cannot request to be followed, and instead can only request to follow someone. Is that correct?
that seems correct, yes. Follow is an explicit action by one actor…
worth noting that you could probably remove the id
for the inlined object
entirely and it would still be valid. if provided, it should be the original remote ID
associated misskey issue:…