-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
What are the criteria for a PDS to be listed in the repo's README? #4
Comments
Hi @kjarex , I just noticed your issue here! It's based on plc.directory related services, and these are targets right now. atproto-pds-search/lib/atproto_pds_crawler.dart Lines 9 to 12 in f9e89e1
|
Thanks. Do you have any idea why Just again for clarification: my intention is not to get it on the list (as the pds is not really used currently anyway), but just to rule out any technical misbehaviour of the pds 😀The same reason why it gets skipped here, might as well create issues with federation later. |
The crawler started indexing on July 29 according to the GitHub Actions workflow (see the I think DIDs which were registered before the June 29 are not crawled. FYI @myConsciousness |
I'm seeing a whole lot more PDS instances than what this repo seems to suggest I don't think the scraper is actually working, like, at all. It doesn't even list the US West-based PDS instances that Bluesky now has ( |
I'm just wondering, by which criteria a PDS is listed in the README?
I'm asking because I'm missing
schnitzel-mit-pommes.de
in the list, while atscan.net mentions it.It's not that I need it to be listed, I'm more interested if this PDS might not deliver/ respond with some required data or misbehaves in any other way!?
Should it indeed misbehave/ lack any necessary information, I would be interested in the details.
Thanks!
The text was updated successfully, but these errors were encountered: