3.14
En cierta manera, sí.
No hay una lista escrita de tus seguidores en ningún lado.
Hay listas de a quién sigue cada usuario. Y son los clientes los que en base a consultar la listas de miles de usuarios, se quedan con las personas que te siguen para construir la lista de tus seguidores.
Por eso es tan variable, porque depende de la información de miles de usuarios disponible en los relays a los que se está en ese momento conectado.
* three months ago, sorry.
Not at all. At least not now.
Bitcoin has gone through much bigger queues due to utxos consolidations, traders transactions between exchanges, etc.
Two months ago was bigger than today, for example:
Still not as big as just two months ago:
When I said 'user metadata ' I was referring not just to the kind-0 event but also to the contact-list on kind-3 events, relay-list or similar.
Nope.
They're completely different cases.
- Follows list exists as part of your own user metadata. The wiping problem happens when a client update the metadata with a blank list because it has not get previously the correct list.
- Followers list doesn't exist as a list per-se. The client builds it up from reading every follows-list from other users metadata, and getting the ones that has your pubkey. That's why it varies quite a lot depending from which relays those users are read.
He's talking about follows, not followers.
Which client?
Today some people have reported that same problem with the latest version of Amethyst (by #[2] ).
Dunno if it's resolved, or if it's happening with other clients too.
Amethyst checkmarks also mean that you follow the user, nothing related with NIP-05 aliases or 'verification'.
👍
More cases of user confusion regarding NIP-05 alias and checkmarks:
nostr:note15w5atktl2r2q7kewwkep0zf3p276gc8y3krlwnamk552xy28ylysgjug9x
Amethyst also allows to Hide (Mute) and/or Report user.
Someone should also just host a metadata archiver relay that stores all versions of everybody's metadata (by just querying other relays) and then offer a metadata recovery service. Maybe #[0] from https://erdaltoprak.github.io/nostrid/.
#[9] already keeps metadata history and allows to check it on https://nostr.band .
Maybe it could add also the Contact Lists?
Please, check that the relay is added with the prefix "ws://" and not with "wss://'.
Not something that I require myself right now, tbh. I don't use kind4 very often.
But I think it could provide a nice extra privacy feature for kind4, yes.
Now that clients have started playing with using different relays for different functions, it's becoming easier to send kind4 events just to relays that requires authentication.
Do you require authentication (NIP-42) to access kind4 events?
Oh yes, please #[17] !!
🙏
PS: that is much longer than the majority of blog posts!
How's the relay access controlled?
- Pubkeys whitelist?
- Auth NIP-42?
- Or just assuming local network as private and secure?