I'm pretty sure the ATproto answer to that is "don't bother users with that decision", i.e. just point new users to somewhere (be it bsky.social or some other P

I'm pretty sure the ATproto answer to that is "don't bother users with that decision", i.e. just point new users to somewhere (be it bsky.social or some other PDS provider) and call it a day. This "works" from a decentralized/federated point of view because ATproto supports migrating accounts/identities between PDSes even if the old PDS is offline or adversarial, and because account/identity hosting (i.e. the PDS) is decoupled from the app itself (i.e. the appview) - so even if you signed up as @foo.example.app instead of @foo.bsky.social, you can still log into Bluesky as @foo.example.app (and likewise, @bar.bsky.social can still log into Example App), and if Example App (or Bluesky, for that matter) ever kicks the bucket you can migrate your account (and its followers, and very likely its public content, and possibly its private content if that was backed up somewhere) to someplace else.