<![CDATA[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.]]>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.

]]>https://board.circlewithadot.net/topic/7293c156-b222-4229-ba47-dd0ea9b603c3/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.RSS for NodeFri, 15 May 2026 10:24:03 GMTFri, 24 Apr 2026 12:59:46 GMT60<![CDATA[Reply to 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. on Fri, 24 Apr 2026 21:24:52 GMT]]>@evan @mariusor @silverpill @hongminhee I can't wait for us to finally drop jsonld in a living standard

]]>https://board.circlewithadot.net/post/https://mastodon.xyz/users/Profpatsch/statuses/116461790307632786https://board.circlewithadot.net/post/https://mastodon.xyz/users/Profpatsch/statuses/116461790307632786Fri, 24 Apr 2026 21:24:52 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 21:24:02 GMT]]>@silverpill @hongminhee why do we need this kind of complication? What's wrong with just always expecting an array and simplifying the standard instead?

]]>https://board.circlewithadot.net/post/https://mastodon.xyz/users/Profpatsch/statuses/116461787071463535https://board.circlewithadot.net/post/https://mastodon.xyz/users/Profpatsch/statuses/116461787071463535Fri, 24 Apr 2026 21:24:02 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 21:23:27 GMT]]>@hongminhee @jamie why do we need this kind of complication? What's wrong with just always expecting an array and simplifying the standard instead?

]]>https://board.circlewithadot.net/post/https://mastodon.xyz/users/Profpatsch/statuses/116461784782945734https://board.circlewithadot.net/post/https://mastodon.xyz/users/Profpatsch/statuses/116461784782945734Fri, 24 Apr 2026 21:23:27 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 20:29:39 GMT]]>@hongminhee It's subtly more messed up than that. AP didn't explicitly allow all 3, but it calls out in a non-normative note that implementers may produce non-canonical serializations.

Right now, as:Public is canonical. Public would be canonical if properties like to/cc/audience were vocab-relative, but they aren't (and shouldn't be). Undefining the as: prefix results in the full URI being canonical.

I think introducing a vocab relative term for visibility could make sense, using Public.

]]>https://board.circlewithadot.net/post/https://mastodon.social/users/trwnh/statuses/116461573180546609https://board.circlewithadot.net/post/https://mastodon.social/users/trwnh/statuses/116461573180546609Fri, 24 Apr 2026 20:29:39 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 19:31:53 GMT]]>@evan @hongminhee yes I think we should!

]]>https://board.circlewithadot.net/post/https://friend.camp/users/darius/statuses/116461346081638797https://board.circlewithadot.net/post/https://friend.camp/users/darius/statuses/116461346081638797Fri, 24 Apr 2026 19:31:53 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 19:16:03 GMT]]>@silverpill @mariusor @hongminhee

]]>https://board.circlewithadot.net/post/https://social.coop/users/django/statuses/116461283775146505https://board.circlewithadot.net/post/https://social.coop/users/django/statuses/116461283775146505Fri, 24 Apr 2026 19:16:03 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:35:35 GMT]]>@silverpill I do not bow to the Mastodon imperialism.

@hongminhee

]]>https://board.circlewithadot.net/post/https://metalhead.club/users/mariusor/statuses/116461124656733814https://board.circlewithadot.net/post/https://metalhead.club/users/mariusor/statuses/116461124656733814Fri, 24 Apr 2026 18:35:35 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:32:19 GMT]]>@rra @hongminhee @cwebber

Link Preview Image
GitHub - w3c-social/activipy: ActivityStreams 2.0 python implementation and validation lib

ActivityStreams 2.0 python implementation and validation lib - w3c-social/activipy

favicon

GitHub (github.com)

]]>https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461111823710780https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461111823710780Fri, 24 Apr 2026 18:32:19 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:28:33 GMT]]>@evan @hongminhee @cwebber could you share a link to that Python one?

]]>https://board.circlewithadot.net/post/https://post.lurk.org/users/rra/statuses/116461097013856436https://board.circlewithadot.net/post/https://post.lurk.org/users/rra/statuses/116461097013856436Fri, 24 Apr 2026 18:28:33 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:28:13 GMT]]>@mariusor @hongminhee I bet the software you're using right now always sends an array

]]>https://board.circlewithadot.net/post/https://mitra.social/objects/019dc0bf-e003-7c53-b4b9-f792cd7efe4ehttps://board.circlewithadot.net/post/https://mitra.social/objects/019dc0bf-e003-7c53-b4b9-f792cd7efe4eFri, 24 Apr 2026 18:28:13 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:24:33 GMT]]>@hongminhee the activitystrea.ms library does a pretty good job of parsing and generating AS2, in a uniform way. It pushes you into better habits, which I appreciate.

My book does bare-JSON parsing in all the major examples; I should probably change it in the next version.

Should we start a page for JSON-LD-based AS2 libraries? I think @cwebber did a good Python one, and there may be others.

]]>https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461081299959770https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461081299959770Fri, 24 Apr 2026 18:24:33 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:22:20 GMT]]>@mariusor @hongminhee I didn't infer that from the spec, it's how Fediverse works.

]]>https://board.circlewithadot.net/post/https://mitra.social/objects/019dc0ba-7f1e-7a50-9121-efc57b286730https://board.circlewithadot.net/post/https://mitra.social/objects/019dc0ba-7f1e-7a50-9121-efc57b286730Fri, 24 Apr 2026 18:22:20 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:13:17 GMT]]>@hongminhee So, I really appreciate that you are doing this work. I know it's hard, and it feels unrewarding, but it really matters, and it really helps the ecosystem.

Please let me know if I can help out in these efforts.

I hope that all of us in the ActivityPub community take these requests seriously when they come in.

]]>https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461037020352441https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461037020352441Fri, 24 Apr 2026 18:13:17 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:09:41 GMT]]>@mariusor @silverpill @hongminhee yeah, that's definitely not what the spec says.

"The serialized JSON form of an Activity Streams 2.0 document MUST be consistent with what would be produced by the standard JSON-LD 1.0 Processing Algorithms and API [JSON-LD-API] Compaction Algorithm"

]]>https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461022833482226https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461022833482226Fri, 24 Apr 2026 18:09:41 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:08:57 GMT]]>@evan@cosocial.ca Can't agree more.

I think having good libraries can make the JSON-LD easier.

Yeah, that's one of reasons why I started Fedify; it was started from building a type-safe Activity Vocabulary library for TypeScript which lets me free from dealing with all complicated things about JSON-LD and keeping it standard-compliant at a time!

]]>https://board.circlewithadot.net/post/https://hollo.social/@hongminhee/019dc0ae-3b3a-7c80-865f-4ba7668a4e31https://board.circlewithadot.net/post/https://hollo.social/@hongminhee/019dc0ae-3b3a-7c80-865f-4ba7668a4e31Fri, 24 Apr 2026 18:08:57 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:06:59 GMT]]>@silverpill @hongminhee single element arrays in JSON-LD go to the element itself, not an array.

]]>https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461012231748211https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461012231748211Fri, 24 Apr 2026 18:06:59 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 18:05:30 GMT]]>@hongminhee so, I've been dealing with this problem a lot with tags.pub.

I have found that many projects are open to issues and patches. Even if I have to downgrade what I'm sending over the wire to the least common denominator, I have some hope that the next people who build to the spec will get better interoperability.

I think having good libraries can make the JSON-LD easier.

]]>https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461006419863551https://board.circlewithadot.net/post/https://cosocial.ca/users/evan/statuses/116461006419863551Fri, 24 Apr 2026 18:05:30 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 17:54:22 GMT]]>> 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

]]>https://board.circlewithadot.net/post/https://metalhead.club/users/mariusor/statuses/116460962580863194https://board.circlewithadot.net/post/https://metalhead.club/users/mariusor/statuses/116460962580863194Fri, 24 Apr 2026 17:54:22 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 17:51:34 GMT]]>@hongminhee Thank you

(my server can handle an object, but you do a favor to all who are only beginning to develop their fedi projects)

]]>https://board.circlewithadot.net/post/https://mitra.social/objects/019dc09e-5320-7c63-9484-ec5c1f863447https://board.circlewithadot.net/post/https://mitra.social/objects/019dc09e-5320-7c63-9484-ec5c1f863447Fri, 24 Apr 2026 17:51:34 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 17:38:34 GMT]]>@silverpill@mitra.social Well, I fixed my software too:

https://github.com/fedify-dev/fedify/pull/721

]]>https://board.circlewithadot.net/post/https://hollo.social/@hongminhee/019dc092-612e-701d-bfe7-7a526244b6dfhttps://board.circlewithadot.net/post/https://hollo.social/@hongminhee/019dc092-612e-701d-bfe7-7a526244b6dfFri, 24 Apr 2026 17:38:34 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 16:52:47 GMT]]>@hongminhee

Why don't you fix your software instead?

It sounds like you're referring to this issue:

Link Preview Image
[Federation]: `Create(Note)` with a single attachment is dropped because `Helpers::verifyAttachments` still assumes `attachment` is an array (follow-up to #6427) · Issue #6588 · pixelfed/pixelfed

Description PR #6427 made handleCreateActivity accept the JSON-LD 1.1 compact form of to/cc (single value instead of a one-element array). The same compaction rule applies to every set-valued property in Activity Streams 2.0, and one of ...

favicon

GitHub (github.com)

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.

]]>https://board.circlewithadot.net/post/https://mitra.social/objects/019dc068-807e-7a33-8f51-5b939a720affhttps://board.circlewithadot.net/post/https://mitra.social/objects/019dc068-807e-7a33-8f51-5b939a720affFri, 24 Apr 2026 16:52:47 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 13:55:39 GMT]]>@jamie@zomglol.wtf Yeah, exactly such kind of thing!

]]>https://board.circlewithadot.net/post/https://hollo.social/@hongminhee/019dbfc6-56d3-72c0-a998-55ec5607e8e4https://board.circlewithadot.net/post/https://hollo.social/@hongminhee/019dbfc6-56d3-72c0-a998-55ec5607e8e4Fri, 24 Apr 2026 13:55:39 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 13:44:18 GMT]]>@hongminhee I ran into things like this with Mastodon. I send valid AP activities but if I don’t encode them in a specific way, Mastodon silently ignores them. Like how it assumes the object of a Create activity must be inline and not a reference, but the actor must be a reference and not inline.

]]>https://board.circlewithadot.net/post/https://zomglol.wtf/users/jamie/statuses/116459979302316597https://board.circlewithadot.net/post/https://zomglol.wtf/users/jamie/statuses/116459979302316597Fri, 24 Apr 2026 13:44:18 GMT<![CDATA[Reply to 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. on Fri, 24 Apr 2026 13:08:46 GMT]]>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. 😩

]]>https://board.circlewithadot.net/post/https://hollo.social/@hongminhee/019dbf9b-6a99-70a3-bab2-1b9269bf2834https://board.circlewithadot.net/post/https://hollo.social/@hongminhee/019dbf9b-6a99-70a3-bab2-1b9269bf2834Fri, 24 Apr 2026 13:08:46 GMT