Post

nate
@zzstoatzz.io

i think so! just checking that this is not sufficient already? bc im thinking that accepting a PDS domain as a filter (whether or not the handles for the accounts hosted on that PDS have the pds as the top level domain) might be interesting now that you say that

B. Prendergast
@renderg.host

Thanks for looking! I don't think this works for me. My case is an app for one specific community on its own PDS (say `acme.com`, <10k users). (Also example you show wouldn't work for users with custom domains on that PDS.)

B. Prendergast
@renderg.host

For an `acme.com` member, searching `bob` returns top 50 bobs across the network of 40m, and none are on `acme.com`. Filtering results client-side shows nothing, and `bob.acme.com` stays invisible. Bob shows up once the prefix rules out everyone more popular, or when typed in full.

0 reposts0 likes

B. Prendergast
@renderg.host

10k accounts is 0.025% of 40M, so they probably rank well below the cut. If `pds=acme.com`, matched on the PDS the users lives on—so custom domains work too—then 'bob' competes with ~10k accounts, not 40M. Make sense?

nate
@zzstoatzz.io

yes! i think i worded my reply confusingly, but that were on the same page. i’ll add a param to let you scope down matches to accounts hosted on a PDS domain like acme.com, if provided. sound good?