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 an id property, instead of setting them to null.
I've opened an issue with the W3C: https://github.com/w3c/activitypub/issues/476
Bringing this up with the W3C sounds like the right move. Do you feel like doing this? I can do it if not, but I think you have more experience than me in wording these things.
Btw, how did…
Just verified, this is also mentioned in JSON-LD 1.0:
7.4.3) If expanded property is @id and value is not a string, an invalid @id value error has been detected and processing is aborted.…
From the JSON-LD spec:
If expanded property is @id: If value is not a string, an invalid @id value error has been detected and processing is aborted. When the frameExpansion flag is set,…
I'm not sure, but all JSON-LD implementations I'm aware of can't parse it, including the official JSON-LD playground
The issue is that null and undefined (no id/@id key) are handled differently in JSON-LD. The latter is valid (and how anonymous objects are supposed to work), the former is not, and throws…
The specific error is Invalid JSON-LD syntax; "@id" value must a string., verifiable at https://transform.tools/jsonld-to-expanded
Context: We've received reports of federation issues with akko.wtf, and I verified that the affected users both have this in their actor objects:
"tag": [
{
"id": null
}
]
I think this change is making emoji attachments federate as "id": null, which causes JSON-LD expansion errors. 😬
@Oneric & @puckipedia: thank you. Fixed in 333611f65e
This issue is currently preventing implementations running full json-ld (iceshrimp.net, takahe, ...) from federating with akkoma. The compaction step at the end of JSON-LD processing replaces…