Conversation

Notices

1. Embed this notice
   Daniël Klabbers (luceos@fosstodon.org)'s status on Saturday, 23-Mar-2024 04:45:32 JST Daniël Klabbers

   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

   • Tim Chambers and Evan Prodromou repeated this.
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Saturday, 23-Mar-2024 04:45:32 JST silverpill

     in reply to

     @luceos I think the most important part of this proposal is "Requirements" section that says:

     >Fediverse software SHOULD implement NodeInfo [NodeInfoRepository].

     The reference leads to NodeInfo repository.

     It is badly formatted, but otherwise seems to be correct.

   • Embed this notice
     smallcircles (Humanity Now 🕊) (smallcircles@social.coop)'s status on Saturday, 23-Mar-2024 08:38:07 JST smallcircles (Humanity Now 🕊)

     in reply to

     @luceos

     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.