Re: @dansup on another thread:
> I think the reason most core devs don't engage in the socialhub forum is because we communicate more directly (dms, discord, etc) as conversations typically move fast
But a "move fast and do not share things" approach means missing out on a win-win and hampers/slows #Fediverse evolution.
An improved standards process + active project participation is much needed.
A problem is that this process hardly exists and no one really reserves the time to make it work.
There's a sort of chicken egg problem in improving the situation.
With no efficient process devs don't find it worthwhile to participate, and no one is available to improve things.
Maybe monetary incentives, salary, bounties for doing community work is needed to stimulate people to help do all the work - and there is a lot to be done - should be considered.
A more formal organization..
A federated protocol where everyone creates ad-hoc extensions for their own projects means we'll soon have a spaghetti-code #Fediverse that no one fully understands and gets harder and harder to interoperate with and less attractive to build new apps for.
The tech debt is already very large, and most documentation is lacking. The "Tragedy of the Commons" of fedi is that it is not a project in and of itself, so nobody maintains it, only uses it as a dependency in their own project.
@humanetech @dansup @cj If only open source projects could become a community effort and not just a never ending toy developers just abandon at will multiple times. Like, I'd love to see Activity Pub become a very solidly maintained protocol that's built on. Take RSS, for example. But the internet at large is trying to kill RSS, so... how did email become so maintained?
In "The Fediverse Challenge" I quoted Moxie's reason for not making Signal decentralized:
"We got to the first production version of IP, and have been trying for the past 20 years to switch to a second production version of IP with limited success. We got to HTTP version 1.1 in 1997, and have been stuck there until now. Likewise, SMTP, IRC, DNS, XMPP, are all similarly frozen in time circa the late 1990s"
(Not saying that is a valid reason)
@blindscribe EMail only exists because there is literally nothing else to communicate without beeing forces to use someones platform.
For the same reason matrix was just pushed to be used by the german health care system*.
The problem for the fediverse is… that it's a toy, nothing companies need to interoperate.
Humane Tech Now, I prefer to actually do stuff instead of spending years and years being ignored or talking and not agreeing on anything at all because the number of potential use cases grows indefinitely. I did my best to try and make use of this process, but it clearly didn't work.
I needed a mechanism to append things to someone else's collections and I made one, and I published a FEP, and other developers said that the thing I made is good. I don't like all this theoretical talk because it doesn't move the world forward in any meaningful way. Building a concrete implementation, and then proposing a standard along with a demonstration that it actually works and achieves what it needs to achieve, works much better.
@grishka sure, and can't blame you in the slightest. It does not really matter how the process is set up, and if things are documented before or after the fact. You participate in discussions, and FEP process, which is more than many others do.
Also the fedi specs work best if ones use cases are already well represented, and just need some tweaks and extension here and there. But if widespread, rich interop is where your app starts off and thrives, its a much more risky bet to 'just start'.
@humanetech @dansup There are more precedents of #slowTech, the internet took from 1970 to 1990 to develop, with the unwritten rule of raw consensus and working code. They used RFCs to write evolving standards. But these were mostly academics who were allowed to spend some of their time on creating the internet. There are examples where fundraising helps (temporarily), e.g. Mobilizon. A more formal organization is asking for tragedy.
> A more formal organization is asking for tragedy
Yea, it is a bit of a conundrum here. A spaghetti-code fediverse is also doomed to become a tragedy, or maybe in slowtech terms it will continue to exist like bulletin boards and usenet. But it will be missed opportunity because there's potential to offer so much more. Truly social humane tech that serves people, fosters collaboration, and offering a refreshing alternative.
Growth in numbers is unimportant, but grow in quality.
Yea Postel's law, but also see this criticism:
> "A flaw can become entrenched as a de facto standard. Any implementation of the protocol is required to replicate the aberrant behavior, or it is not interoperable. This is both a consequence of applying the robustness principle, and a product of a natural reluctance to avoid fatal error conditions. Ensuring interoperability in this environment is often referred to as aiming to be "bug for bug compatible".
Well, if we did that for the #Fediverse it would be a great step forwards. We have a Fediverse Enhancement Proposals (FEP) process, but after bootstrapping it, it immediately stalled.
Well, I am not advocating to make the process more formal. Better defined, maybe, easier accessible.
But to have a more formal organization core as a foundation below the SocialHub community, on which it stands. Maybe being able to collect funding and deal it out via bounties in a democratic community-involved process, idk.
There's a ton of work and all dull chores.
Volunteering like now, trying to herd cats, is a recipe for burnout and in fact happened to many others already.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!