Reminder: AS/AP-based suffers from #BallOfMud based ad-hoc expansion unless we find common practices and stick to them.
-
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.
-
M [email protected] shared this topic
-
Justin Thomasreplied to small circle 🕊 in calmness last edited by
@smallcircles it's possible that standards can be an emergent characteristic of building and experimentation.
My approach to building policy and standards (something I do a lot in my day job) - particularly for unproven or new technologies - is to start by building a proof-of-concept. Figure out what works. Then engage the community to refine and standardize.
We're in that PoC stage with a lot of things right now. Premature standardization could put us in a much worse position than allowing for the organic development of the ecosystem.
-
small circle 🕊 in calmnessreplied to Justin Thomas last edited by
@jdt I agree, and am also deeply interested in emergence and how to facilitate that reliably so it turns into healthy evolution and adaptability to changing needs over time.
Interesting discussions are on matrix chat and social coding forum, looking at ideas and vision for a next-gen fedi, kicked off by @helge
Premature standardization as the name says is an anti-pattern, but so too is post-facto documentation of what has become de-facto standard in the fediverse installed base.
-
small circle 🕊 in calmnessreplied to small circle 🕊 in calmness last edited by
So it is a balancing act.. unless the system is primed to not find a natural balance, which imho is the case in current ASAP fedi.
I semi-jokingly referred to it as the "as soon as possible" fedi, an intermediary stage I suppose to the next-gen fedi that is still not tapped into well enough, and we risk squandering potential and opportunity and giving ample time for corporate web to catch up and make things bland and exploited, let alone very unsafe for diverse fedizen groups.
-
small circle 🕊 in calmnessreplied to small circle 🕊 in calmness last edited by
-
naturzukunftreplied to small circle 🕊 in calmness last edited by
@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. -
small circle 🕊 in calmnessreplied to naturzukunft last edited by
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.
-
small circle 🕊 in calmnessreplied to small circle 🕊 in calmness last edited by
See also the 5 forces I see that determine interop on the ASAP "as soon as possible" fedi and tooted something about:
