Conversation

Notices

1. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Sunday, 11-May-2025 04:39:12 JST silverpill

   Started writing a new FEP:

   FEP-0151: NodeInfo in Fediverse Software (2025 edition)

   Mentioned some best practices. What else should be added there?

   #FEP #NodeInfo

   • Embed this notice
     @reiver ⊼ (Charles) :batman: (reiver@mastodon.social)'s status on Sunday, 11-May-2025 06:39:41 JST @reiver ⊼ (Charles) :batman:

     in reply to

     @silverpill

     Regarding:

     "In order to hide the usage statistics, the values of properties in the usage object could be set to 0."

     What do you think about setting it to 'null' rather than '0'?

     I suppose if some software wasn't written robustly, it might "panic" on getting a non-number.

     But, to me 'null' seems more appropriate.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Sunday, 11-May-2025 06:39:41 JST silverpill

     in reply to

     • @reiver ⊼ (Charles) :batman:

     @reiver NodeInfo schema 2.1 requires these values to be integer [0;∞]

     http://nodeinfo.diaspora.software/schema.html

     The properties in usage object are optional, though, so simply omitting them is fine too. That might be a better solution than setting values to 0.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Sunday, 11-May-2025 08:08:27 JST silverpill

     in reply to

     • FenTiger

     @fentiger

     >"Servers SHOULD implement NodeInfo..." seems a bit strong, especially considering that some people are quite strongly opposed to it. Is this really a SHOULD?

     I want to encourage people to implement NodeInfo (because end-users expect it to be implemented) but discourage certain practices, so SHOULD feels appropriate there.

     RECOMMENDED would work too

     >Would it be worth recommending that implementers provide a config option to allow NodeInfo to be switched on and off by the instance admin?

     Yes

     >Should there be a recommendation that "Consumers SHOULD NOT assume that any given Fediverse site will implement NodeInfo"?

     +1

     >I've seen code out there that uses a NodeInfo hit to decide which auth protocol to use for cross-instance login. I personally don't like this approach and would prefer not to encourage people to use designs like this.

     I also don't like it.

     There are even FEPs that recommend using NodeInfo to signal capabilities: https://codeberg.org/fediverse/fep/src/branch/main/fep/9fde/fep-9fde.md
     I mentioned that NodeInfo shouldn't be used in that way in the "When to use NodeInfo" section.

   • Embed this notice
     FenTiger (fentiger@zotum.net)'s status on Sunday, 11-May-2025 08:08:29 JST FenTiger

     in reply to
     "Servers SHOULD implement NodeInfo..." seems a bit strong, especially considering that some people are quite strongly opposed to it. Is this really a SHOULD? Or would it be better to write a paragraph or two about the pros and cons, and let implementers decide for themselves?
     
     Would it be worth recommending that implementers provide a config option to allow NodeInfo to be switched on and off by the instance admin?
     
     Should there be a recommendation that "Consumers SHOULD NOT assume that any given Fediverse site will implement NodeInfo"?
     
     I've seen code out there that uses a NodeInfo hit to decide which auth protocol to use for cross-instance login. I personally don't like this approach and would prefer not to encourage people to use designs like this.
   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Monday, 12-May-2025 04:22:55 JST silverpill

     in reply to

     • @reiver ⊼ (Charles) :batman:

     @reiver I changed the recommendation to "omit properties"

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Monday, 12-May-2025 04:24:38 JST silverpill

     in reply to

     • FenTiger

     @fentiger Added "Privacy and security considerations" section which explains why people might want to disable NodeInfo:

     https://codeberg.org/silverpill/feps/src/commit/451193095d8330e42f7400541c9f751a9e28c7d2/0151/fep-0151.md#privacy-and-security-considerations