Email or username:

Password:

Forgot your password?
Top-level
Gert V

@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.

18 comments
smallcircles (Humane Tech Now)

@gert @dansup

> 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.

Gert V

@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: en.wikipedia.org/wiki/Jon_Post

smallcircles (Humane Tech Now)

@gert @dansup

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".

en.wikipedia.org/wiki/Robustne

@gert @dansup

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".

Gert V

@humanetech @dansup What he did was write up a lot of RFCs in order to avoid widespread confusion..

smallcircles (Humane Tech Now)

@gert @dansup

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.

socialhub.activitypub.rocks/t/

Gert V

@humanetech @dansup So you could help not to make the process go from informal to formal, but from high entropy to low entropy.

smallcircles (Humane Tech Now)

@gert @dansup

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.

David Sterry

@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.

smallcircles (Humane Tech Now)

@weex @gert @dansup

I have proposed on SocialHub to transfer it to codeberg.org/fediverse but there was no follow-up to that.

David Sterry

@humanetech @gert @dansup Well if you know anyone who can get an access code, please do. I'll definitely make it part of my daily or at least weekly rounds.

smallcircles (Humane Tech Now)

@weex @gert @dansup

It was in this post in April: socialhub.activitypub.rocks/t/

I also proposed some changes to the FEP process.

Both @cj and @pukkamustard did a ton of work in setting things up, and its their call if they feel positive for a move to codeberg.

David Sterry

@humanetech @gert @dansup @cj @pukkamustard

That's amazing. I found this stuff about federation.md in many projects which is very interesting. Are all of those listed somewhere along with things like the FEPs and AP spec?

cj πŸ‡ΊπŸ‡ΈπŸ‡¨πŸ‡­

@humanetech I am fine with a move to codeberg. I think most of the FEP things are documented in the git repository, not in the issues specific to git.activitypub.dev. It would be good to get explicit opinion from @pukkamustard and @lain as well though.

@weex @gert @dansup

David Sterry

@humanetech @gert @dansup Just tried again and I was able to login... FEPs are alive again!

Go Up