#nodeinfo — Public Fediverse posts

@elgg We've got a MR to add #Elgg to fediverse.party;

https://codeberg.org/fediverse/fediparty/pulls/288

Our usual process is to set up some test accounts to check federation is working, and we usually wait until a project has at least 1 independent instance, to confirm that it's practical to self-host.

I can't find any Elgg instances on FediDB or the-federation.info, and only a demo server on fediverse.observer. Maybe that the plugin isn't publishing #NodeInfo data in a way these instance mapping sites can ingest?

Just so you know, the dominance of Mastodon as a server software choice for the fediverse has at times been overstated, and may still be overstated;

"The Mastodon API endpoint is Mastodon specific but platforms which have also implemented the Mastodon API (to make use of Mastodon mobile clients) look like Mastodon servers to apps reading information about the servers."

@jaywink, 2019

https://talk.feneas.org/t/serviceinfo-specification-for-service-metadata/99

(1/2)

#fediverse #StatsCollection #NodeInfo

Edit: Done! https://madeincanada.social/#servers

Instead of manually adding servers to https://MadeInCanada.social, I'll leverage my FediDB.com service with a new API 🔥

#ActivityPub #NodeInfo #Fediverse #MadeInCanada

https://mstdn.feddit.social/nodeinfo/2.0

#nodeinfo #mastodon #fediverse

• Tanukey (you've listed it elsewhere)
• Neko
• Catodon
• Hajkey
• Metaskey
• Backspacekey

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

I added the "Implementations" section and a reference to FEP-844e:

https://codeberg.org/fediverse/fep/pulls/741

There are 3 independent implementations now. Since this is a "2025 edition", and 2025 is about to end, I think the FEP should be finalized.

If you have any suggestions, please comment here, on SocialHub, or create an issue.

#fep #fep_0151 #activitypub #nodeinfo

I finally got around to setting up #nodeinfo properly on #Enigmatick as an effort to be a more compliant #ActivityPub participant. Coincidentally (and unexpectedly), my connected instances have jumped substantially (>15% in 24 hours):

enigmatick=> SELECT                                                                                                          CASE                                                                                                                       WHEN created_at > NOW() - INTERVAL '1 day' THEN 'last 24h'                                                               WHEN created_at > NOW() - INTERVAL '2 days' THEN '24-48h ago'                                                            WHEN created_at > NOW() - INTERVAL '3 days' THEN '48-72h ago'                                                          END as period,                                                                                                           COUNT(*)                                                                                                               FROM instances                                                                                                           WHERE created_at > NOW() - INTERVAL '3 days'                                                                             GROUP BY period                                                                                                          ORDER BY period;
   period   | count
------------+-------
 24-48h ago |     1
 48-72h ago |     3
 last 24h   |   164
(3 rows)

Maybe it's not directly related - I also fixed some direct object and tags link references to provide proper ActivityPub representations.

Loops now supports NodeInfo ✨

https://fedidb.com/software/loops

#loops #nodeInfo #activityPub

We'd like to recognize the valuable contributions from two developers who participated in Korea's #OSSCA (Open Source Contribution Academy) program. Both contributors identified important gaps in #Fedify's functionality and documentation, providing thoughtful solutions that benefit the broader #ActivityPub ecosystem.

@gaebalgom contributed PR #365, addressing issue #353 regarding NodeInfo parser compatibility, originally reported by @andypiper. The issue arose when Fedify incorrectly rejected #NodeInfo documents from snac instances due to overly strict version string parsing that required semantic versioning compliance. Their solution improves the fallback behavior in the parseSoftware() function to handle non-SemVer version strings by parsing dot-separated numbers and defaulting to zero for missing components. The implementation includes thorough test coverage for various edge cases, including single numbers (3), two-part versions (2.81), and malformed version strings. This fix provides immediate compatibility improvements across the fediverse while maintaining backward compatibility, and will be included in Fedify 1.9. The contribution serves as an interim solution, with a more comprehensive fix planned for Fedify 2.0 (issue #366), where the NodeInfo software.version field will be changed from the SemVer type to a plain string to fully comply with the NodeInfo specification.

@z9mb1 contributed PR #364, resolving issue #337 by adding practical examples for Fedify's custom collection dispatchers feature. Custom collections were introduced in Fedify 1.8 but lacked clear documentation for developers seeking to implement them. Their contribution provides a comprehensive example demonstrating how to set up custom collections for tagged posts, including proper routing patterns, pagination handling, and counter functionality. The example includes mock data structures, shows how to configure collection dispatchers with URL patterns like /users/{userId}/tags/{tag}, and demonstrates the complete request/response cycle using federation.fetch(). This work provides developers with a clear, runnable reference that reduces the complexity of implementing custom collections in ActivityPub applications.

We appreciate these meaningful contributions that help make Fedify more accessible and robust for the entire ActivityPub community.

#opensource #fedidev #fediverse

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

About the whole #nodeinfo #GTS brouhaha, I want to point out that an #API is meant to be machine-readable. What's the point of providing a machine-readable endpoint and then blocking machines via robots.txt?

@mastodonmigration @bob 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 #WordPress - #WebsiteBuilder app. Somehow, I kept getting difficulties from the iPhone app to connect #Mastodon and #BlueSky. 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.

#Jetpack #ActivityPub #WebFinger #NodeInfo #WebMention #URLshortener #PlugIn #Fediverse #Marketing #Sharing #SocialMedia #MarketingIntegrations #OnlineEngagement #AudienceEngagement

this work by @graue to add #NodeInfo "feature flag" support to @phanpy is amazing!
https://github.com/cheeaun/phanpy/pull/817

this really helps makes the fediverse stronger ⁂!

#ShowerThoughts: Could we use Murmurations to replace NodeInfo in fediverse servers, for sharing server stats and public details? Or make NodeInfo compatible with Murmurations aggregators?

Some preliminary musings on potential interop between the verse and Murmurations on SocialHub;

https://socialhub.activitypub.rocks/search?q=murmurations

Some of which probably answer that question, and I'll have a dig through.

#AskFedi #NodeInfo #Murmurations #SocialHub

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.

https://github.com/jhass/nodeinfo/blob/main/PROTOCOL.md

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.

#Fediverse #NodeInfo

#Hollo now gives you accurate usage statistics from #NodeInfo.

@LaurensHof
> When the Mastodon pilot launched in September 2023, Mastodon had around 1.7M monthly active users, a number that has dropped a year later to around 1.1M

Are we talking about just Mastodon or the fediverse as a whole (a big chunk of which is Mastodon for now, but ...).

But this is a great example of why there's an urgent need to update or replace the NodeInfo protocol (originally part of Diaspora) that's used for collecting fediverse stats.

https://socialhub.activitypub.rocks/t/is-there-an-fep-for-nodeinfo-yet/4538/4

#NodeInfo

Fedify is an #ActivityPub server framework in #TypeScript & #JavaScript. 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)
• #WebFinger client and server
• HTTP Signatures & Linked Data Signatures & Object Integrity Proofs
• Middleware for handling webhooks
• #NodeInfo protocol
• #Node.js, #Deno, and #Bun support
• CLI toolchain for testing and debugging

If you're curious, take a look at the #Fedify website! There's comprehensive docs, a demo, a tutorial, example code, and more:

https://fedify.dev/

Main #Threads differences to date with other #Fediverse platforms (focusing on non debatable issues):
1 - They are not #opensource
2 - They do not publish a #nodeinfo
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.

@dansup do you support alternate ways to add header images and meta informations, besides`/api/v1/instance`?

https://fedidb.org/network/instance/mastodon.social

Firefish seems to add a lot of extra stuff to the NodeInfo Metas: https://firefish.social/nodeinfo/2.1

#fedidb #api #nodeinfo