Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @hongminhee@hollo.social
洪 民憙 (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.
---Reply---
洪 民憙 (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. 😩
Reply
---Replies---
silverpill@silverpill@mitra.social (2026-04-25 01:52:47)
@hongminhee
Why don't you fix your software instead?
It sounds like you're referring to this issue:
https://github.com/pixelfed/pixelfed/issues/6588
But in Fediverse, attachment is not supposed to be an object, it's an array.
I don't think you should expect people to comply with your vision of ActivityPub.