Federate emoji as anonymous objects #815
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#815
Loading…
Reference in a new issue
No description provided.
Delete branch "Oneric/akkoma:emoji-id"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Similarly small change as those in #814, but may warrant some more attention wrt possibly federation effects.
Federation with other *omas and with *keys (+IceShrimp) should work; not sure how Mastodon and its forks handle null ids. (e.g. fedibird and chuckya support emoji reactions)
Usually an id should point to another AP object
and the image file isn’t an AP object. We currently
do not provide standalone AP objects for emoji and
don't keep track of remote emoji at all.
Thus just federate them as anonymous objects,
i.e. objects only existing within a parent context
and using an explicit null id.
IceShrimp.NET previously adopted anonymous objects
for remote emoji without any apparent issues. See:
333611f65e
Fixes: #694
I was now able to confirm this works fine in practice with:
However issues arose with GtS 0.16.0; emoji got stripped with only the shortcode text remaining. I brought it up with GtS upstream
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.