-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Lemmy instances on 0.19.4 are no longer included #184
Comments
This is easily circumventable, as most software supporting the nodeinfo schema also supports the |
Just realised: there's already a PR at #183 for this. |
Sorry about this, I've been away for a little while. :) Let me get on top of this :D |
Merged the PR. Gotta deploy it our to the crawler infra, which is currently performing a backup, will probably take another hour. :) |
Hmm, it's scanned the backlog again but not making a huge dent in the un-scannable instances. |
Ok, it's ripping through them now, should be good shortly :D |
And yeah it's pretty obvious 0.19.4 has broken it :D |
OK, I'm goign to close this. They have started rolling in, though may take another ~12 hours before they all flow through :) |
Possible cause:
From what I can understand of this crawler's code, it looks for "http://nodeinfo.diaspora.software/ns/schema/2.0" in the response to /.well-known/nodeinfo
Lemmy 0.19.4 included a change to only provide "http://nodeinfo.diaspora.software/ns/schema/2.1".
Usually, fediverse platforms that provide 2.1 also provide 2.0, so it wouldn't be a problem, but they've apparently decided to make problems (including for themselves) by not doing so.
The text was updated successfully, but these errors were encountered: