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: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---
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.
Reply
---Replies---
洪 民憙 (Hong Minhee) :nonbinary:@hongminhee@hollo.social (2026-04-25 02:38:34)
@silverpill Well, I fixed my software too:
https://github.com/fedify-dev/fedify/pull/721
marius@mariusor@metalhead.club (2026-04-25 02:54:22)
> attachment is not supposed to be an object, it's an array.
@silverpill I don't understand how you infer that from this spec: https://www.w3.org/TR/activitystreams-vocabulary/#dfn-attachment
@hongminhee
Beady Belle Fanchannel@Profpatsch@mastodon.xyz (2026-04-25 06:24:02)
@silverpill @hongminhee why do we need this kind of complication? What's wrong with just always expecting an array and simplifying the standard instead?