I encourage everybody to adopt the following pattern, when talking about ActivtyPub:
General Discussion
6
Posts
3
Posters
14
Views
-
I encourage everybody to adopt the following pattern, when talking about ActivtyPub:
- Use W3C ActivityPub, when referring to The Specification and its consequences
- Use ActivityPub for referring to what is actually implemented in the Fediverse
If it's important what you mean by ActivityPub, use more clarifications, e.g. Mastodon-ActivityPub.
-
I encourage everybody to adopt the following pattern, when talking about ActivtyPub:
- Use W3C ActivityPub, when referring to The Specification and its consequences
- Use ActivityPub for referring to what is actually implemented in the Fediverse
If it's important what you mean by ActivityPub, use more clarifications, e.g. Mastodon-ActivityPub.
@helge for what is actually implemented in the fediverse i would use the term "fediverse", or with clarification "mastodon protocol". i don't think it serves well to muddy the waters between following the spec vs following what others have done (which are generally not the same).
-
@helge for what is actually implemented in the fediverse i would use the term "fediverse", or with clarification "mastodon protocol". i don't think it serves well to muddy the waters between following the spec vs following what others have done (which are generally not the same).
Bad idea. The Fediverse is already ambiguous enough. Suggesting using it to also mean a protocol just creates a mess.
-
Bad idea. The Fediverse is already ambiguous enough. Suggesting using it to also mean a protocol just creates a mess.
@helge there is no singular fediverse protocol and there cannot be. "fediverse" is a collective/umbrella term. the protocols are "mastodon protocol", "lemmy protocol", "funkwhale protocol", etc, and they partially overlap.
-
I encourage everybody to adopt the following pattern, when talking about ActivtyPub:
- Use W3C ActivityPub, when referring to The Specification and its consequences
- Use ActivityPub for referring to what is actually implemented in the Fediverse
If it's important what you mean by ActivityPub, use more clarifications, e.g. Mastodon-ActivityPub.
@helge I support this
-
@helge there is no singular fediverse protocol and there cannot be. "fediverse" is a collective/umbrella term. the protocols are "mastodon protocol", "lemmy protocol", "funkwhale protocol", etc, and they partially overlap.
test refederation
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@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.
-
@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.
-
@tennoseremel And if it had used JSON instead of JSON-LD? ;)
-
@tennoseremel@gts.skobk.in fwiw if ActivityPub were XML instead of JSON I would not have integrated it.
-
@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.
-
@tennoseremel activities need an extensible markup language for mentions, tags, quotes, media, and a lot more.
