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
I can well understand this, esp. since #SocialHub is not efficient in pushing #ActivityPub et al.
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.
@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.
@humanetech @dansup Evolution is basically a process of trial and error. If you want to help it, please have a look how that has been done before: https://en.wikipedia.org/wiki/Jon_Postel
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".
https://en.wikipedia.org/wiki/Robustness_principle#Criticism
@humanetech @dansup What he did was write up a lot of RFCs in order to avoid widespread confusion..
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.
https://socialhub.activitypub.rocks/t/fep-a4ed-the-fediverse-enhancement-proposal-process/1171
@humanetech @gert @dansup
Practically speaking, I've been trying to regain access to git.activitypub.dev for weeks but haven't had any luck. I feel like its home repo needs to be on a more reliable host.
If FEP really failed, then let's do another one based on a proven process like RFC or even BIP.
I have proposed on SocialHub to transfer it to https://codeberg.org/fediverse but there was no follow-up to that.
@humanetech @gert @dansup Just tried again and I was able to login... FEPs are alive again!
