How does this work.. The FEP-f1d5 talks about a node info endpoint, but the FEP states no obligatory endpoint. References lead to an old library that recommends /.well-known/x-nodeinfo2 (for that v2 library). How did a FEP become final without this crucial piece of information or am I simply missing that information in the finalised FEP? #ActivityPub#Fediverse
Currently the #FEP process serves as an instrument for the open ecosystem that allows people to draw attention to what they want to or have built. For reasons of collecting feedback, providing help or in hopes of others adopting their practices so as to increase general interop in some way or other.
The process is informal, lightweight, and its facilitators assume no authority. Anyone can submit FEP's on whatever they want. Authors are in charge, ecosystem decides to adopt or not.
Of course there are numerous ways in which the #FEP process can be improved and further expanded to make it a stronger force towards a broadly interoperable Fediverse. I am a fan of bottom up standards process in 3 stages, where FEP's play a role besides other hives of activity and ultimately evolve open standards, like #ActivityPub.
@luceos Like others have said, the FEP process is very loose. FEP-f1d5 looks to me to be an informational document about history and caveats of NodeInfo in “Fediverse” software. I believe it should not have a requirements section or the SHOULD statement (NodeInfo is not typically, if ever, required for AP-related federation). I also don’t see any rationale to support that position. That said, these are just my personal opinions and observations. YMMV.
/cc @smallcircles@silverpill
Add comment