ActivityPub would have been better if it used XML instead of JSON.
General Discussion
12
Posts
6
Posters
10
Views
-
ActivityPub would have been better if it used XML instead of JSON.
/duck
-
ActivityPub would have been better if it used XML instead of JSON.
/duck
-
ActivityPub would have been better if it used XML instead of JSON.
/duck
@tennoseremel activities need an extensible markup language for mentions, tags, quotes, media, and a lot more.
-
@tennoseremel activities need an extensible markup language for mentions, tags, quotes, media, and a lot more.
@tennoseremel we often end up with html-in-jsonld, but worry not: as json is inherently human-readable, and html (by the sole virtue of not being xml) is too, everything is great and the web developers feel all modern and trendy.
-
ActivityPub would have been better if it used XML instead of JSON.
/duck
@tennoseremel@gts.skobk.in fwiw if ActivityPub were XML instead of JSON I would not have integrated it.
-
ActivityPub would have been better if it used XML instead of JSON.
/duck
@tennoseremel And if it had used JSON instead of JSON-LD? ;)
-
@tennoseremel And if it had used JSON instead of JSON-LD? ;)
@fentiger@mastodon.social then there would be property conflicts!
But far fewer than expected and everyone would just adjust and defer to prior art... and most importantly nobody would use JSON-LD compliance as a cudgel.
Sounds nice actually.
-
@julian The ability to make up brand new, guaranteed-unique identifiers on the fly is probably the thing I like most about JSON-LD.
As you imply, though, it's not really a problem in practice, because devs are used to JSON, and know what happens when you add extensions to standards.
-
@julian The ability to make up brand new, guaranteed-unique identifiers on the fly is probably the thing I like most about JSON-LD.
As you imply, though, it's not really a problem in practice, because devs are used to JSON, and know what happens when you add extensions to standards.
@fentiger@mastodon.social the purportedly world-ending effects of property collisions are overblown, imho.
-
@julian The ability to make up brand new, guaranteed-unique identifiers on the fly is probably the thing I like most about JSON-LD.
As you imply, though, it's not really a problem in practice, because devs are used to JSON, and know what happens when you add extensions to standards.
>The ability to make up brand new, guaranteed-unique identifiers on the fly is probably the thing I like most about JSON-LD.
But it is not a JSON-LD thing, right?
A JSON document can have property names that are URIs, or reverse-DNS strings, or UUIDs, or longNamesThatIncludeSoftwareNameAndVersion. All of those can be globally unique.
-
Here's the first recorded collision in the history of Fediverse: https://github.com/bookwyrm-social/bookwyrm/issues/3731
-
>The ability to make up brand new, guaranteed-unique identifiers on the fly is probably the thing I like most about JSON-LD.
But it is not a JSON-LD thing, right?
A JSON document can have property names that are URIs, or reverse-DNS strings, or UUIDs, or longNamesThatIncludeSoftwareNameAndVersion. All of those can be globally unique.
@silverpill @julian Fair point.
I suppose I was thinking of the ability to assign it to a shortened name in the @'context - but this is probably relatively unimportant once it's been gzipped.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Right, which ActivityPub.Space follows and auto categorizes, which ends up as a way for microblog content to make its way into the threadiverse. @strypey@mastodon.nzoss.nz
@silverpill@mitra.social sorry for interjecting 😁
-
-
> @strypey@mastodon.nzoss.nz said:
>
> We could instead try to agree on a separate place for all discussions about fediverse coordination (would it rub anyone up the wrong way if I described this as fediverse governance?). But it does makes sense to discuss a federated network in a federated network, rather than a separate, centralised forum.I keep harping on this one point because it just makes so much sense that it'd be silly not to. The new blood (new software devs implementing AP) always appear on fedi, not some third-party site, first.
To your main point, fedi on Mastodon is all just everybody talking in the same room. Certainly that's why it seems like there's so much meta-discussion about AP.
This isn't the case on the threadiverse, where discussions are segregated/categorized by community.
-
@mariusor awesome! ♥️
-
@pfefferle I added a PKCE task to my todo list:
-
@pfefferle if I'd come up with a scheme for them they would be related to pairs of activityType:objectType entries (instead of a global write), or maybe just the activityType
Ie, Create:Note, Create:Image, Undo, Delete.
-
@mariusor yea, I think the scopes and the PKCE part was the issue!
but finally... 😊
-
@pfefferle love it! 💗
GoActivityPub doesn't really do "scopes" because I couldn't think of a way store the permissions on the server side in a way that doesn't require custom logic to interact with vanilla ActivityPub objects.
