Post

Bailey Townsend 🦀
@pds.dad

Would be nice if there was a way to find new PDSs to move to wouldn't there be? Working on a new page to expose that along with trust signals to known PDSs. I will be porting over the trusted PDSs from PDS MOOver to verified on this page. Reach out if you'd like yours hidden or details changed.

Bailey Townsend 🦀
@pds.dad

Nice! Hoping to have mine up later this week still reviewing and testing. Mine is mostly just to expose them as for what can be migrated to. It finds them automatically from walking the relay and populates data from that. Not going quite be curated, but more so..

Bailey Townsend 🦀
@pds.dad

"I know that this pds is most likely not Malicious." I have a lot of fear of copy cat PDSs showing up to harvest credentials so got things in there to hide from lists or show warnings.

Joe Basser
@joebasser.com

Yeah good point. Mine is setup to filter out based on some signals that make it likely to be a ‘public’ PDS vs. someone’s personal one. (Which they can still choose to list if they want) but you’re right I should definitely look out for those kind of copycat scenarios

Joe Basser
@joebasser.com

Awesome! That’s exactly what mine does too - more so for users to find a place to create an account if they don’t have one yet!

Bailey Townsend 🦀
@pds.dad

I def like yours and think it fills an important niche we need in exposing these communities/pds better. Mine is mostly just to help people when moving to a pds with a typeahead, and give some surface level info if needed. W social is a good example, I have it set as hidden and a warning because..

Joe Basser
@joebasser.com

Yeah I was thinking a bidirectional declaration between a PDS and its operator's account. Most of the machinery is necessary when the host domain is separate from the public-facing account. E.g bsky.app vs bsky.social. What do you think? Would establish 'this account represents this PDS's operator'