🫧 socialcoding.. @smallcircles@social.coop
Public

@virtualpierogi @sriSriram "sri" Ramkrishna - 😼 @jsalvadorJuanjo Salvador @benBen Werdmuller @nlnet

It needs concerted effort, as argued in my blog post, to set all of this up. Things can start small and pragmatic, and then gradually evolve and mature, but we should take care it evolves in the proper direction.

There are trade-offs to consider every step of the way. If there'd more capabilities to introspect the functionality that an actor offers, it would diminish the need for an upfront design-by-consensus process, but it would increase the complexity of the specifications.

I drew this in a diagram a couple years ago, and transferred it to our social coding forum at: discuss.coding.social/t/wiki-g

Here you see the fediverse devolve into non-interoperable app-by-app whack-a-mole development, keeping track of all the moving-target projects one took a dependency on. Versus the that tries to hammer out full-blown specs upfront, which became a huge package to deal with, with high complexity to implement.

Wiki: Grassroots standardization processes

This topic is a starting point to consider best-practices for the design and evolution of open standards by the commons and tailored to the grassroots environment’s social dynamics. Inspiration for this topic is the standardization surrounding the ActivityPub family of protocols. While in January 2018 W3C ActivityPub v1.0 became a W3C Recommendation there was no good process in place to responsibly evolve the specifications. Since then a large amount of protocol decay has stifled innovation and...

discuss.coding.social · Discuss Social Coding

🫧 socialcoding.. @smallcircles@social.coop
Public

@virtualpierogi @sriSriram "sri" Ramkrishna - 😼 @jsalvadorJuanjo Salvador @benBen Werdmuller

Unfortunately there's a new threat, and it was addressed in the keynote speech by @michielMichiel Leenaars of @nlnet .. and that is the mad dash to incorporate into everything and vibe-code stuff together in a heartbeat.

I think this is particular bad for the fediverse still lacking its robust foundations. The 's will have no problem figuring out how to mix'n mash the existing protocol decay and tech debt into new applications that are rushed into production. Finally non-protocol-experts are enable on the ecosystem and can onboard themselves without involving themselves in endless plumbing of the most low-level technical implemention details of devs.

But the ecosystem will rot and decay as a result of it. Furthermore if a slew of AI-generated fedi apps are launched in quick succession and some of them find good uptake (until they break in unexpected ways), it will serve to attract unwanted corporate attention I'm afraid.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116097028148422269 on your instance and quote it. (Note that quoting is not supported in Mastodon.)