Lingolol

0 posts0 participants0 posts today

silverpillStarted writing a new FEP:<a href="https://codeberg.org/silverpill/feps/src/branch/main/0151/fep-0151.md" rel="nofollow noopener noreferrer" target="_blank">FEP-0151: NodeInfo in Fediverse Software (2025 edition)</a>Mentioned some best practices. What else should be added there?<a class="hashtag" href="https://mitra.social/collections/tags/fep" rel="nofollow noopener noreferrer" target="_blank">#FEP</a> <a class="hashtag" href="https://mitra.social/collections/tags/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">#NodeInfo</a>

David Zappelli<a href="https://mastodon.online/@mastodonmigration" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mastodonmigration</a> <a href="https://beamship.mpaq.org/@bob" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bob</a> So, I looked at your instructions, but I realized that they need an update. First, the desktop editor is not the same as the iPhone <a href="https://sfba.social/tags/WordPress" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WordPress</a> - <a href="https://sfba.social/tags/WebsiteBuilder" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebsiteBuilder</a> app. Somehow, I kept getting difficulties from the iPhone app to connect <a href="https://sfba.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> and <a href="https://sfba.social/tags/BlueSky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlueSky</a>. So, I instead went back to my laptop and did it there. This is now done by going into the editor, and selecting TOOLS >MARKETING; and then see the CONNECTIONS button on the page (right of the menu). Or HOSTING >CONNECTIONS, depending on how you’re logged in.Then hit the CONNECT button, sign into the Mastodon Account handle, approve the connection to WordPress by "authorizing" it. You may get a pop-up window in the process. <a href="https://sfba.social/tags/Jetpack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Jetpack</a> <a href="https://sfba.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://sfba.social/tags/WebFinger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebFinger</a> <a href="https://sfba.social/tags/NodeInfo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NodeInfo</a> <a href="https://sfba.social/tags/WebMention" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebMention</a> <a href="https://sfba.social/tags/URLshortener" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#URLshortener</a> <a href="https://sfba.social/tags/PlugIn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PlugIn</a> <a href="https://sfba.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a href="https://sfba.social/tags/Marketing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Marketing</a> <a href="https://sfba.social/tags/Sharing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sharing</a> <a href="https://sfba.social/tags/SocialMedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SocialMedia</a> <a href="https://sfba.social/tags/MarketingIntegrations" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MarketingIntegrations</a> <a href="https://sfba.social/tags/OnlineEngagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OnlineEngagement</a> <a href="https://sfba.social/tags/AudienceEngagement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AudienceEngagement</a>

wakest ⁂this work by <a href="https://social.coop/@graue" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@graue</a> to add <a href="https://social.wake.st/tags/NodeInfo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NodeInfo</a> "feature flag" support to <a href="https://hachyderm.io/@phanpy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@phanpy</a> is amazing! <a href="https://github.com/cheeaun/phanpy/pull/817" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/cheeaun/phanpy/pull/817</a>this really helps makes the fediverse stronger ⁂!

@reiver ⊼ (Charles) :batman:AcitivityPub isn't the only protocol used by the Fediverse.NodeInfo is another protocol that makes up the suite of protocols that the Fediverse is based on.<a href="https://github.com/jhass/nodeinfo/blob/main/PROTOCOL.md" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/jhass/nodeinfo/blob/main/PROTOCOL.md</a>NodeInfo is used to discover various information about the server node.Such as:• the software it is running (ex: Mastodon, PIxelfed, etc) • the server node's total number of users, • the number of posts on the server node, • the number of active users, • etc.<a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a href="https://mastodon.social/tags/NodeInfo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NodeInfo</a>

Hollo :hollo:<a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Hollo" target="_blank">#Hollo</a> now gives you accurate usage statistics from <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/NodeInfo" target="_blank">#NodeInfo</a>.

Fedify: an ActivityPub server framework<a href="https://fedify.dev/" rel="nofollow noopener noreferrer" target="_blank">Fedify</a> is an <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> server framework in <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/TypeScript" target="_blank">#TypeScript</a> & <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/JavaScript" target="_blank">#JavaScript</a>. It aims to eliminate the complexity and redundant boilerplate code when building a federated server app, so that you can focus on your business logic and user experience. The key features it provides currently are: <ul> <li>Type-safe objects for Activity Vocabulary (including some vendor-specific extensions)</li> <li><a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/WebFinger" target="_blank">#WebFinger</a> client and server</li> <li><a href="https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures-12" rel="nofollow noopener noreferrer" target="_blank">HTTP Signatures</a> & <a href="https://web.archive.org/web/20170923124140/https://w3c-dvcg.github.io/ld-signatures/" rel="nofollow noopener noreferrer" target="_blank">Linked Data Signatures</a> & <a href="https://w3id.org/fep/8b32" rel="nofollow noopener noreferrer" target="_blank">Object Integrity Proofs</a></li> <li>Middleware for handling webhooks</li> <li><a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/NodeInfo" target="_blank">#NodeInfo</a> protocol</li> <li><a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Node" target="_blank">#Node</a>.js, <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Deno" target="_blank">#Deno</a>, and <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Bun" target="_blank">#Bun</a> support</li> <li>CLI toolchain for testing and debugging</li> </ul> If you're curious, take a look at the <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a> website! There's comprehensive docs, a demo, a tutorial, example code, and more: <a href="https://fedify.dev/" rel="nofollow noopener noreferrer" target="_blank">https://fedify.dev/</a>

Jupiter Rowland@<a href="https://stefanbohacek.online/@stefan" rel="nofollow noopener noreferrer" target="_blank">Stefan Bohacek</a> To add to your table: <a href="https://framagit.org/hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> supports nodeinfo 2.0 and 2.1. Examples from a stable release, just to show that they can differ, depending on how a hub is configured: <a href="https://hub.netzgemeinde.eu/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://hub.netzgemeinde.eu/.well-known/nodeinfo</a> <a href="https://im.allmendenetz.de/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://im.allmendenetz.de/.well-known/nodeinfo</a> <a href="https://klacker.org/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://klacker.org/.well-known/nodeinfo</a> <a href="https://hubzilla.monster/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://hubzilla.monster/.well-known/nodeinfo</a> Example from a development release: <a href="https://zotum.net/.well-known/nodeinfo" rel="nofollow noopener noreferrer" target="_blank">https://zotum.net/.well-known/nodeinfo</a> However, it looks like nodeinfo can be turned off entirely by the hubmin. At least hubzilla.org has a blank nodeinfo page. <a href="https://codeberg.org/streams" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> always has a blank nodeinfo page. Most nodeinfo code has intentionally been removed. It understands nodeinfo, but it seems to send something else instead which it only understands itself, which is limited in what information it offers, and which isn't parsed by Fediverse stats/instance-listing websites. By the way: Both Hubzilla and (streams) support both OAuth and OAuth2 both as a client and as a server. However, Hubzilla's documentation is painfully outdated in this regard; parts of it still refer to Red, so they were last touched before the name change to Red Matrix. And (streams) doesn't have any documentation. Also, Hubzilla and (streams) are the only Fediverse server applications with full, i.e. both server-side and client-side support for OpenWebAuth single sign-on. CC: @<a href="https://infosec.exchange/@kpwn" rel="nofollow noopener noreferrer" target="_blank">Konstantin :C_H:</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OAuth" rel="nofollow noopener noreferrer" target="_blank">OAuth</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OAuth2" rel="nofollow noopener noreferrer" target="_blank">OAuth2</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Nodeinfo" rel="nofollow noopener noreferrer" target="_blank">Nodeinfo</a>

洪民憙 (Hong Minhee) 🤏🏼<a href="https://todon.eu/tags/Fedify" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fedify</a> is an <a href="https://todon.eu/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> server framework in <a href="https://todon.eu/tags/TypeScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TypeScript</a> & <a href="https://todon.eu/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JavaScript</a>. It aims to eliminate the complexity and redundant boilerplate code when building a federated server app, so that you can focus on your business logic and user experience.The key features it provides currently are:• Type-safe objects for Activity Vocabulary (including some vendor-specific extensions) • <a href="https://todon.eu/tags/WebFinger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebFinger</a> client and server • HTTP Signatures • Middleware for handling webhooks • <a href="https://todon.eu/tags/NodeInfo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NodeInfo</a> protocol • <a href="https://todon.eu/tags/Node" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Node</a>.js, <a href="https://todon.eu/tags/Deno" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Deno</a>, and <a href="https://todon.eu/tags/Bun" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bun</a> support • CLI toolchain for testing and debuggingIf you're curious, take a look at the Fedify website! There's comprehensive docs, a demo, a tutorial, example code, and more:<a href="https://fedify.dev/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://fedify.dev/</a><a href="https://todon.eu/tags/fedidev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedidev</a>

Éric FreyssinetMain <a href="https://mastodon.social/tags/Threads" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Threads</a> differences to date with other <a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> platforms (focusing on non debatable issues): 1 - They are not <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> 2 - They do not publish a <a href="https://mastodon.social/tags/nodeinfo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nodeinfo</a> 3 - To date, they are only very partially federated: some accounts and only to be read from outside Threads EDIT: 4 - Threads accounts are based on Instagram and when one joins they are offered to follow their IG friends, even those without a Threads account yet Will update.

Matthias Pfefferle<a href="https://mastodon.social/@dansup" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dansup</a> do you support alternate ways to add header images and meta informations, besides`/api/v1/instance`?<a href="https://fedidb.org/network/instance/mastodon.social" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://fedidb.org/network/instance/mastodon.social</a>Firefish seems to add a lot of extra stuff to the NodeInfo Metas: <a href="https://firefish.social/nodeinfo/2.1" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://firefish.social/nodeinfo/2.1</a><a href="https://mastodon.social/tags/fedidb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedidb</a> <a href="https://mastodon.social/tags/api" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#api</a> <a href="https://mastodon.social/tags/nodeinfo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nodeinfo</a>

Fedilab AppsExtra-features (disabled by default) is somewhat confusing in <a href="https://toot.fedilab.app/tags/Fedilab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fedilab</a>. This option allows to enable features that <a href="https://toot.fedilab.app/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> doesn't support (quotes, reactions, submit messages in a specific format, etc.) But softwares like <a href="https://toot.fedilab.app/tags/Pleroma" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pleroma</a>, <a href="https://toot.fedilab.app/tags/Akkoma" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Akkoma</a>, <a href="https://toot.fedilab.app/tags/GlitchSocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlitchSocial</a>, <a href="https://toot.fedilab.app/tags/FireFish" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FireFish</a> don't support (currently) same features.We plan to use <a href="https://toot.fedilab.app/tags/NodeInfo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NodeInfo</a> to automatically enable features depending on the user's instance (ie: software).

Recent searches

Search options

Administered by:

Server stats:

#nodeinfo