I'd recommend Strike or River, send them to nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8 sooner rather than later, and recommend Coldcard/Sparrow to a cold wallet storage/interface.

If you can start understanding UTXO management early you will be way ahead of the game.

They're sending Bitcoin to each other via nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 while we're at lunch. My son uses it more than my daughter, so he asked her if she knew how to create an invoice for a specific amount. She figured it out! The only thing they had a problem with was spelling their lightning addresses. "Citadel" isn't an everyday word they use 😂 I think a contact list via Nostr or address book would be very beneficial here.

The,n somehow we got to talking about the prices of things. They both started talking about money printing and inflation. 🥹🥹🥹

Your children are little sponges and will listen to everything you say and watch everything you do. 💜💜💜

https://github.com/nostr-protocol/nips/blob/master/02.md

Here is where our contact lists are stored! KIND-3.

{

"kind": 3,

"tags": [

["p", "91cf9..4e5ca", "wss://alicerelay.com/", "alice"],

["p", "14aeb..8dad4", "wss://bobrelay.com/nostr", "bob"],

["p", "612ae..e610f", "ws://carolrelay.com/ws", "carol"]

],

"content": "",

...other fields

}

Most of the clients use this as "following". They search among all relays, find the latest Kind-3 event signed by your npub.

When you click follow on someone's profile page, the client generate a new event, add that name to tags and publish a new event.

Relay should delete the previous contact list once they recieved new one, which, not always happen.

## Why do we suffer from contact list disaster?

Client fails to find the latest contact list event and adds the new following at the end of the lates previous event they can find, and add the current timestamp to it. This is why we feel our following list being wiped.

## Why is follower number never unstable?

Followers are calculated from querying everyone's latest kind-3 event. Based on different client implementation, "everyone" is an unstable set, also, as we mentioned above, "latest event", may be stored in a relay we didnt know.

Thank you for reading. I hope this will help you know a little bit more about some weird client behaviours and enjoy the design behind nostr.

idea cr: nostr:npub1t3ggcd843pnwcu6p4tcsesd02t5jx2aelpvusypu5hk0925nhauqjjl5g4

https://void.cat/d/CGtxRrrjhMaBUe5X3hps4m.webp

Is anyone who sees this in on the 0.80 beta of nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5?

I noticedvit's been in beta for quite a long time andbwas wondering how it's going. Did it start out as a tire fire? Is it getting better over time? Do you think it's close to being stable enough to become an actual release?

Tell me your opinions. I want to know the good, the bad, and the ugly!