bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Server stats:

253
active users

#protocoldecay

0 posts0 participants0 posts today
Replied in thread

@frankstrater @dansup @peertube

Other than that.. I started calling current AS/AP fedi the "as soon as possible" fediverse, where necessarily early app implementations served as the de-facto reference implementations for the #W3C #ActivityStreams and #ActivityPub open standards.

At serious cost: Ever increasing #ProtocolDecay and subsequent #WhackaMoleAdoption i.e. retaining app-by-app interop pipes against moving release targets.

When is Video domain getting standardized? That's my question.

Reminder: AS/AP-based suffers from #BallOfMud based ad-hoc expansion unless we find common practices and stick to them. Collaboration across a commons is essential here. Just coding your app with custom #ActivityPub protocol extension is contributing to #ProtocolDecay and increasing complexity to facilitate broad #interoperability.

The #FEP process and #SocialCG are where collective effort and proactive participation can improve #fedi for all. We need a bottom up standardization process.

"Show don't tell" of federate #FOSS code & apps doesn't work well in environment where we need "Show don't tell" of #OpenStandard specs to make progress. Especially if the specs are so vague that each code implementation thrown in the cauldron of #ActivityPub #fediverse installed base is known to only add #ProtocolDecay and #TechDebt.

In #Commons #CommonSense makes #CommonsSense: Don't introduce the opposite of #interoperabily when in pursuit of seamless interop.

We need both forms of showing.