So apparently NodeBB includes a valid nodeinfo and even lists 'activitypub' in the protocols section, even for forums that don't federate

Shoutout to @silverpill for creating a new Nodeinfo FEP to handle this

Introducing the newly redesigned Fediverse Onboarding feature 🥳

Now this is something we can share and use to help people find their way in this federated community

https://fedidb.com/welcome

Feedback + boosts greatly appreciated, I spent a lot of time on this, for the benefit of everyone ️

@renchap Pixelfed supports double blind sigs, I will update our logic to support the RFC9421 version!

I'll be in touch this week regarding our progress.

(P.S - I'm almost done follower collection sync too)

@jaz @julian @liaizon Yes, we just need to check the nodeinfo protocols, though I assumed they all supported ActivityPub as this is what nodeinfo was created for.

I've never seen a nodeinfo with an empty protocols array, that kind of defeats the purpose IMO.

I will fix this though.

@liaizon @jaz @julian we discover servers by crawling pixelfed peers api, so they federated at some point. We do remove servers without a reachable node info or one that blocks crawlers

@liaizon @jaz @nodebb not right how? We just go by the nodeinfo numbers

Special thanks to @jaz for opening up so many issues in the new FediDB repo!

I was able to ship fixes for many of them

https://github.com/fedidb/fedidb-nuxt/issues?q=is%3Aissue%20state%3Aclosed%20author%3Ajmking-iftas

#fediDB