@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
Top-level
@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 16 comments
@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 @dansup So you could help not to make the process go from informal to formal, but from high entropy to low entropy. 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. @humanetech @gert @dansup 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 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. It was in this post in April: https://socialhub.activitypub.rocks/t/social-cg-issue-trackers/1648/2 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. @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? @weex @gert @dansup @cj @pukkamustard Some time ago I edited all the FEDERATION.md I could find in: https://socialhub.activitypub.rocks/t/guide-for-new-activitypub-implementers/479 @weex A small list of things that needs FEPs: https://socialhub.activitypub.rocks/t/come-help-list-of-feps-needed/1097 @weex There was also an idea to host the FEPs at https://library.activitypub.dev/ but I never updated the library's code. @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. @humanetech @gert @dansup Just tried again and I was able to login... FEPs are alive again! |
@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".
https://en.wikipedia.org/wiki/Robustness_principle#Criticism
@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".