[bug] Custom emoji objects aren't valid JSON-LD #848
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#848
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
What were you trying to do?
with #815 being merged, payloads containing custom emoji objects are no longer JSON-LD compliant. See #815 (comment) for details.
What did you expect to happen?
Payloads can be passed through JSON-LD expansion
What actually happened?
An error is thrown due to an invalid
@id
objectSeverity
I cannot use the software
Since this is a spec conflict and likely a mistake in the AP specification, I've opened an issue with the W3C: https://github.com/w3c/activitypub/issues/476
From the discussion in the GH thread, the best way to solve this issue on the akkoma side would be to send out
Emoji
objects without anid
property, instead of setting them to null.This is now also causing federation issues between akkoma and iceshrimp.net as of 3.13.3, since any bio with any emoji inside of them will fail to parse on iceshrimp.net's side, due to the JSON-LD submodule not recognising
"id": null
confirmed: This is now also preventing ALL posts that has any emoji inside of it to be processed by iceshrimp.net
#850 fixes this