#ActivityPub specs are basis for spec compliance.
General Discussion
5
Posts
3
Posters
22
Views
-
#ActivityPub specs are basis for spec compliance.
Current fediverse is a mixture of flavors. Mastodon is a flavor. The #FEP is a recipe cookbook for particularly flavored meals.
The fedi as it is today will never offer a home to anything that does not in some way represent a timeline with flowing texts, even if masquerading in more creative UI's. Every specialist (not really, just different-than-microblogging) domain auto-excludes itself to live in the fringes of fedi. Just by being different.
-
#ActivityPub specs are basis for spec compliance.
Current fediverse is a mixture of flavors. Mastodon is a flavor. The #FEP is a recipe cookbook for particularly flavored meals.
The fedi as it is today will never offer a home to anything that does not in some way represent a timeline with flowing texts, even if masquerading in more creative UI's. Every specialist (not really, just different-than-microblogging) domain auto-excludes itself to live in the fringes of fedi. Just by being different.
@smallcircles "today"? Are you imagining additional fediversal protocols that aren't organized by time? Space (maps), topic (wikis, library catalogs), semantics (glossaries, dictionaries), ontologies (laws, scriptures)?
-
@smallcircles "today"? Are you imagining additional fediversal protocols that aren't organized by time? Space (maps), topic (wikis, library catalogs), semantics (glossaries, dictionaries), ontologies (laws, scriptures)?
More like an extension based off of the specs that is less likely to only lead to protocol decay and whack-a-mole development. On the basis that the current specs are too flexible. #ActivityPub is de facto a protocol framework. An extension can be the protocol with more rigor, and help ease solution development on top of that with yet more composable extensions.
W3C specs give us conceptually 'addressible actors that exchange activities with object payload'. That's powerful.
-
#ActivityPub specs are basis for spec compliance.
Current fediverse is a mixture of flavors. Mastodon is a flavor. The #FEP is a recipe cookbook for particularly flavored meals.
The fedi as it is today will never offer a home to anything that does not in some way represent a timeline with flowing texts, even if masquerading in more creative UI's. Every specialist (not really, just different-than-microblogging) domain auto-excludes itself to live in the fringes of fedi. Just by being different.
@smallcircles this is absolutely untrue.
ActivityPub, out of the box, can handle literally any CRUD applications. That's a huge swath of possible apps.
All apps exist in time, and many apps like games or office utilities have an activity stream. That doesn't mean they're microblogging apps.
-
More like an extension based off of the specs that is less likely to only lead to protocol decay and whack-a-mole development. On the basis that the current specs are too flexible. #ActivityPub is de facto a protocol framework. An extension can be the protocol with more rigor, and help ease solution development on top of that with yet more composable extensions.
W3C specs give us conceptually 'addressible actors that exchange activities with object payload'. That's powerful.
@smallcircles @evanwolf it's very powerful.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@naturzukunft2026 many such cases, sadly
-
@eyeinthesky @evan @trwnh the charter has the correct scope. I believe Evan was responding to discussion about the Fediverse and trying to point out the venn diagram overlap of Fediverse and WG charter. As such, indieweb stuff didn't factor in to that conversation. Or at least that was my read -- I raised an eyebrow when I read the email too!
-
@trwnh @evan @darius So maybe the narrow WG focus is aspirational (or participant-specific) rather than official. I've read that Indieweb leaders like Tantek will be involved so that sounds like there's interest from them too. Maybe there will be somewhat independent subgroups working on different subsets of specs?
-
@eyeinthesky @evan @darius a lot of this is probably in https://github.com/swicg/meetings but you'll have to find it first -- it's not in one piece
-
@eyeinthesky @evan @darius i believe the rechartering process led up to people landing on more or less the following:
- the primary reason for rechartering is that AP people want to work on updating AP/AS2
- however, there are other specs which also need updates, but don't want to recharter separately
- the w3c liaisons advised making the charter broader rather than narrower, to avoid potentially needing to amend the charter
- the work will be driven primarily by availability of editorsiirc?
-
On the W3C SocialCG mailing list, I saw that @evan wrote "The WG ... is focused on a narrow core: Activity Streams and ActivityPub." The WG charter describes a much broader scope. What am I missing?
-
Mastodon is a black hole. ActivityPub Academy receives my notes, Mastodon accepts them and ignores them. That's a bit annoying. In the meantime, I've remembered the mention speciality, which I'll probably never understand. You can only federate if you adapt to the peculiarities of Mastodon. The spec is ActivityPub, but federation is unfortunately Mastodon.
#activitypub #mastodon
-
The new W3C #ActivityPub Working Group is not that. Or not just that. It's a "Social Web" Working Group and includes maintenance of ActivityPub, WebSub, Activity Streams, Activity Vocabulary, MicroPub, Linked Data Notifications, Webmention, and LOLA specifications. Maintaining all these disparate specs in one WG seems like it will lead to similar results as the first time this was tried (not great). What's that saying about doing the same thing repeatedly and expecting different results? 🙃
