Recent searches
Search options
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.
@smallcircles the only question is what we do with the existing applications that are based on mastodon.
with #rdfpub i'm at the very beginning of federation and have been surprised countless times.
i'm very excited to see what else i come across.
If the commons accepts its open standards based, as requirement to assure its openness, and people building apps and services for that commons claim to adhere to these standards, then they should be willing to participate and accomodate, sometimes make concessions for the greater good.
Now any FOSS project is entitled to go anywhere it wants. They are autonomous. But the commons should not hang their head and go into unsustainable direction because of a post-facto interop leader.
in calmness @smallcircles@social.coopSee also the 5 forces I see that determine interop on the ASAP "as soon as possible" fedi and tooted something about: