Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

洪 民憙 (Hong Minhee) :nonbinary:@hongminhee@hollo.social (2026-04-24 21:59:46)
I hope more #ActivityPub implementations start properly handling JSON-LD documents in various forms, rather than using ad-hoc approaches like only allowing specific fields to accept both arrays and scalar values.
---Reply---
洪 民憙 (Hong Minhee) :nonbinary:@hongminhee@hollo.social (2026-04-24 22:02:44)
Or, just use a proper JSON-LD processor altogether. Of course, there would be a performance penalty. The #ActivityPub spec explicitly allows as:Public or bare Public for public addressing in to/cc, etc., but surprisingly many implementations don't handle this. All of this would actually be solved by using a JSON-LD processor.

---Replies---

洪 民憙 (Hong Minhee) :nonbinary:@hongminhee@hollo.social (2026-04-24 22:08:46)
Honestly, I don't really care what strategy other #ActivityPub implementations follow to comply with the spec. (I solved it in #Fedify by just using a proper JSON-LD processor.) It's just a bit annoying that I always send valid JSON-LD documents, but whenever I encounter an interoperability bug where the other side can't process them, I'm the one who has to send them a patch to fix it. 😩