FEP-0151: NodeInfo in Fediverse Software (2025 edition)
General Discussion
3
Posts
2
Posters
7
Views
-
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-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.
💕 I'm so thankful for all the work to the #FEP process you have 🎁 gifted this entire year. You are one of those who help the #fediverse shine, aggregating building blocks, paving pathways with grassroots #ActivityPub tiles, where only raw substrate of ✨ possibilities existed before.
This "2026 edition" I hope we can walk, all like you, in unison on a singular cause. Towards sunnier #SocialWeb futures. Grow strong to face a gloomy #SocialNetworking landscape of offline society.
-
💕 I'm so thankful for all the work to the #FEP process you have 🎁 gifted this entire year. You are one of those who help the #fediverse shine, aggregating building blocks, paving pathways with grassroots #ActivityPub tiles, where only raw substrate of ✨ possibilities existed before.
This "2026 edition" I hope we can walk, all like you, in unison on a singular cause. Towards sunnier #SocialWeb futures. Grow strong to face a gloomy #SocialNetworking landscape of offline society.
And thank you for your work too @smallcircles !
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Right, which ActivityPub.Space follows and auto categorizes, which ends up as a way for microblog content to make its way into the threadiverse. @strypey@mastodon.nzoss.nz
@silverpill@mitra.social sorry for interjecting 😁
-
-
> @strypey@mastodon.nzoss.nz said:
>
> We could instead try to agree on a separate place for all discussions about fediverse coordination (would it rub anyone up the wrong way if I described this as fediverse governance?). But it does makes sense to discuss a federated network in a federated network, rather than a separate, centralised forum.I keep harping on this one point because it just makes so much sense that it'd be silly not to. The new blood (new software devs implementing AP) always appear on fedi, not some third-party site, first.
To your main point, fedi on Mastodon is all just everybody talking in the same room. Certainly that's why it seems like there's so much meta-discussion about AP.
This isn't the case on the threadiverse, where discussions are segregated/categorized by community.
-
@mariusor awesome! ♥️
-
@pfefferle I added a PKCE task to my todo list:
-
@pfefferle if I'd come up with a scheme for them they would be related to pairs of activityType:objectType entries (instead of a global write), or maybe just the activityType
Ie, Create:Note, Create:Image, Undo, Delete.
-
@mariusor yea, I think the scopes and the PKCE part was the issue!
but finally... 😊
-
@pfefferle love it! 💗
GoActivityPub doesn't really do "scopes" because I couldn't think of a way store the permissions on the server side in a way that doesn't require custom logic to interact with vanilla ActivityPub objects.
