Saltar al contenido

loo.blue

@loo.blue did:plc:seiwji66yyjpzs2konzwe77d

loo.blue

En Bluesky desde el

Seguidores
10
Siguiendo
0
Posts
40
Días en rankings
0

Resumen

loo.blue (@loo.blue) es un usuario de Bluesky que se unió el 2 enero 2026. Tiene 10 seguidores, sigue a 0 cuentas y ha publicado 40 posts.

Apariciones en rankings

Los mejores días en que los posts de esta cuenta entraron en la lista diaria de Debya.

Esta cuenta aún no ha aparecido en un ranking diario.

Posts que le gustaron recientemente

Me gusta públicos de la red 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

Inicia sesión para ver más

Cuentas que bloquea

En Bluesky los bloqueos son registros públicos.

Esta cuenta no bloquea a nadie.