Latest posts tagged with #NodeInfo on Bluesky
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 […]
https://mstdn.feddit.social/nodeinfo/2.0
https://mstdn.feddit.social/nodeinfo/2.0
#nodeinfo #mastodon #fediverse
yeaaaah i implemented #nodeinfo in #flohmarkt. now how the hell does one add a server to #fedidb in the year 2025? :D
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 […]
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?
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 ⁂!
![{
"links": [
{
"rel": "http://nodeinfo.diaspora.software/ns/schema/2.2",
"href": "http://localhost:8080/-/nodeinfo/2.2"
},
{
"rel": "http://nodeinfo.diaspora.software/ns/schema/2.1",
"href": "http://localhost:8080/-/nodeinfo/2.1"
},
{
"rel": "http://nodeinfo.diaspora.software/ns/schema/2.0",
"href": "http://localhost:8080/-/nodeinfo/2.0"
},
{
"rel": "http://nodeinfo.diaspora.software/ns/schema/1.1",
"href": "http://localhost:8080/-/nodeinfo/1.1"
},
{
"rel": "http://nodeinfo.diaspora.software/ns/schema/1.0",
"href": "http://localhost:8080/-/nodeinfo/1.0"
}
]
}](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:rmxxsmssvtgzfwp7qzyedyll/bafkreielyzccncsp3f7j7plw33vi6fi2esc3offtvy3gftgszp2qzfjbi4)
{ "links": [ { "rel": "http://nodeinfo.diaspora.software/ns/schema/2.2", "href": "http://localhost:8080/-/nodeinfo/2.2" }, { "rel": "http://nodeinfo.diaspora.software/ns/schema/2.1", "href": "http://localhost:8080/-/nodeinfo/2.1" }, { "rel": "http://nodeinfo.diaspora.software/ns/schema/2.0", "href": "http://localhost:8080/-/nodeinfo/2.0" }, { "rel": "http://nodeinfo.diaspora.software/ns/schema/1.1", "href": "http://localhost:8080/-/nodeinfo/1.1" }, { "rel": "http://nodeinfo.diaspora.software/ns/schema/1.0", "href": "http://localhost:8080/-/nodeinfo/1.0" } ] }
[microdon]
Added basic nodeinfo support to microdon.
It uses its own stlyle of path for each nodeinfo file. But also supports Akkoma, Firefish, Pixelfed, and Mastodon style paths, too.
#microdon #nodeinfo
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
#Fediverse #NodeInfo
