shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

261
active users

#protocoldecay

0 posts0 participants0 posts today
just small circles 🕊<p><span class="h-card" translate="no"><a href="https://mastodon.social/@frankstrater" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frankstrater</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@dansup" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dansup</span></a></span> <span class="h-card" translate="no"><a href="https://framapiaf.org/@peertube" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>peertube</span></a></span></p><p>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 <a href="https://social.coop/tags/W3C" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>W3C</span></a> <a href="https://social.coop/tags/ActivityStreams" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ActivityStreams</span></a> and <a href="https://social.coop/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ActivityPub</span></a> open standards.</p><p>At serious cost: Ever increasing <a href="https://social.coop/tags/ProtocolDecay" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProtocolDecay</span></a> and subsequent <a href="https://social.coop/tags/WhackaMoleAdoption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WhackaMoleAdoption</span></a> i.e. retaining app-by-app interop pipes against moving release targets.</p><p>When is Video domain getting standardized? That's my question.</p>
just small circles 🕊<p>Reminder: AS/AP-based suffers from <a href="https://social.coop/tags/BallOfMud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BallOfMud</span></a> 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 <a href="https://social.coop/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ActivityPub</span></a> protocol extension is contributing to <a href="https://social.coop/tags/ProtocolDecay" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProtocolDecay</span></a> and increasing complexity to facilitate broad <a href="https://social.coop/tags/interoperability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>interoperability</span></a>. </p><p>The <a href="https://social.coop/tags/FEP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FEP</span></a> process and <a href="https://social.coop/tags/SocialCG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SocialCG</span></a> are where collective effort and proactive participation can improve <a href="https://social.coop/tags/fedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedi</span></a> for all. We need a bottom up standardization process.</p>