Entwickelt Open Source in der Freizeit, hat zu viele Fahrräder und ist Fan des HSVH (Das erste “H” steht für “Handball”) und von islieb, Franzbrötchen und guter Schokolade. Wunschliste: alles unter https://www.rausch.de/schokolade/

Wer Amazon mag: https://www.amazon.de/hz/wishlist/ls/3VWK0ZL3MN3ZT

Liberapay: https://liberapay.com/heluecht/donate
BTC: 1AtJ9JVysdhWjSs5qQvp7Xt9xFdjMKSSA7
BCH: qpjg2gwgr35fgz3dxy6lcpw3lt4szrfgev90uk3tfv

  • 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


















  • @loki @dawnerd Well, since the accounts are now moved to their specific hosts, you can use these hostnames instead of the generic one when using their protocol. The only action where you currently still need the generic bluesky host name (bsky.app) is during some account related activities.

    The different hosts already talk to each other using the same protocol that is already in use for third parties who interact with bluesky (like alternate clients or custom feeds). The only thing that currently prevents “real” decentralization is the user registry.

    From the outside it appears as if it all was some monolithic block. But this is only the case since the default usernames are using the bsky.social hostname. But in fact you can already use your own hostnames for your account, since the account is not locked to any hostname but to some unique hash. (Which is one of the advantages of their protocol and which we really should implement in the Fediverse as well to perform real account portability)