There is a list of hardcoded relays, but it tries to use the relays from the user's NIP-07 extension if they exist.
Yes, please, let's do the same spec so everything is compatible. Let me know what you think.
Roy Harper
I think what clients are doing is parsing "#whatever" from the content and adding these as "t" tags in the event.
Hey Nostr community, great to see Nostr grow and take shape!
Do you want to give feedback on our game and be part of our ⚡10k sats draw?
We have created a new game called 'Cowdle' to see how gaming could be part of the Nostr fun. It's a competitive word guessing game played with your friends.
Try the game with your followers by posting a fresh new note (Not in a reply to this thread):
'@cowdle #game'
Ohh, and you can win ⚡ by playing too!
We would 🧡 to hear your feedback and suggestions, maybe you even have ideas for types of games that could work on Nostr?
We will draw the 10k reward amongst all those that have played and given feedback by Sunday the 12th 21:00 CET. Provide your feedback as replies to this thread. And follow us to stay up to date! We will for sure follow you back.
Read more about Cowdle here: https://cowdle.gg
Thank you! 🐮⚡🐮
#[0] I guess we need hashtag support on https://github.com/mikedilger/gossip so I can play this.
I sent the screenshot so I wouldn't have to decide.
https://nostr.watch/ has statistics now, and data, historical and present, that comes from the server instead of from your own browser.
It's actually super hard and a giant pain in the ass.
I just did it.
There’s a bunch of impersonation being done with NIP-05 because it currently just verifies to the domain name. This makes folks using directory services like nostr.directory, nostrplebs.com, and things like cash.app for verification difficult. Because I could be verified by those accounts and set my petname to jack or some brand name.
We’ve written up a updated proposal to add optional names that are verified at the service as part of the NIP-05 and a link back to the information that the verification service has about this nostr user.
Clients don’t need to implement this but it solves a lot of issues we’re seeing when people are using third party domains for verification.
https://github.com/erikwestra/nips/compare/master...nip-05-security-proposal
A simpler solution would be for clients to drop the misleading "verified" badges entirely.
For example, this is what I see on Gossip: 
Simple and straight to the point.
It's probably related to your client not following relay hints and that note not being in any relay from the static set of relays you're connected to.
It should be at least on wss://relay.realsearch.cc, according to the event tags of my response.
Uncle Bob uses Lightning: #[0]
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/.
I imagine that losing follows and whatnot won't be an issue for people that only use one client, right? And then once you're using multiple clients you should also be open to using a dedicated client just for managing your contacts and so on.
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/.
Why not keep a history locally? You could do the prompting or not -- but even then instead of overwriting you still keep the previous versions.
I do like that Gossip keeps a local copy and only overwrites -- or merges upon an explicit button click: 
A prototype writer client is live at https://write.nostr.com/, by #[0].
A reader client should be happening soon.
How is Gossip working for you?
I am familiar with these things, but I don't see the benefit of pulling a giant spec from other people into Nostr and make it into a bloated dependency. I don't see any benefits, only malefits.
Why hasn't any other language adopted Rust's model of borrowing pointers?
