Post
#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.
@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.
@smallcircles @evanwolf it's very powerful.
A space for Bonfire maintainers and contributors to communicate
