Ir para o conteúdo

loo.blue

@loo.blue did:plc:seiwji66yyjpzs2konzwe77d

loo.blue

No Bluesky desde

Seguidores
10
Seguindo
0
Posts
40
Dias nos rankings
0

Resumo

loo.blue (@loo.blue) é um usuário do Bluesky desde 2 janeiro 2026. Tem 10 seguidores, segue 0 contas e publicou 40 posts.

Aparições nos rankings

Os melhores dias em que posts desta conta entraram na lista diária do Debya.

Esta conta ainda não apareceu em um ranking diário.

Posts curtidos recentemente

Curtidas públicas da rede Bluesky.

  • fry69@fry69.dev

    This sounds like the correct way to resolve a handle. A handle with did:web (found via DNS or HTTP) means that the authoritative DID document is at a web URL, which must be used and all other sources are not to be trusted.

    Ver post
  • fry69@fry69.dev

    It works now 🎉 My point was that I (did:web) should not be a special case and bsky should not be the default entity to ask/resolve handles. That sounds concerning to me.

    Ver post
  • fry69@fry69.dev

    I still think there is some not quite right with your login logic if you ask bsky by default. There is of course still a record in bsky for my did:plc account, which is impossible to delete, as e.g. chat messages rely on the bsky AppView. But that should play no role for resolving atproto handles

    Ver post
  • fry69@fry69.dev

    Tried a second time and @fry69.dev repeatedly resolves to @fry69.altq.net through your login system.

    Ver post
  • fry69@fry69.dev

    Now the login works, kinda. When I logged in with my @fry69.dev account (did:web), it used my old (did:plc) account @fry69.altq.net somehow.

    Ver post

Entre para ver mais

Contas que bloqueia

No Bluesky, bloqueios são registros públicos.

Esta conta não bloqueia ninguém.