Acabo de descubrir esta herramienta:
https://github.com/jeremyd/nostr-contacts
Por si os interesa para hacer puntualmente backup de los follows.
🫂
PoW and the energy spent are what make sats real.
🫂
Be careful, efficiency usually implies centralisation.
Nostr URL scheme is "nostr:", not "nostr://".
Following the rules is not vandalism.
If the event's recategorized maybe a new 1984 could replace the previous one?
That's actually what the Fediverse is doing.
And it's not going well, imo.
Nope.
NIP-05 is just setting a DNS alias for a pubkey.
It's not user verification.
An export to file option is maybe too much for Amethyst.
But an option to push your historical events to a private relay (i.e. #[2] ) may be a good idea.
I think Nostros client has recently implemented.
You can always use disposable keypairs to test new apps.
You can change the mempool size in your own bitcoin node.
That's what they call the "halving"?
/s
What's your idea? Are you going to use a pubkeys whitelist?
Or authentication via NIP-42?
Normal relays don't guarantee how long they are going to keep the events.
A 'backup' relay could guarantee certain amount of time.
No.
It depends on the node who build the mined blocks and its own mempool size.
The queue is still smaller than what it was just last November:
There's no One Mempool.
Each node has its own mempool with its limits, it's pending transactions, etc.
Kind 10002 is also part of the user profile (relays list metadata).
You could also consider following it's evolution, imo.
🫂