client forks are the new plugins, instead of adding a little extra, you can just take over the whole thing
maybe it is, I thought it was official lol. works really well..
oh. right, isn't this the official mullvad?
mullvad accepts LN
nostr is the dream of any developer and it is also the dream social interaction model for humans. it takes everything good we learned from the open source development of bitcoin and lightning and applies it to the missing piece, a simple system that is very unreliable by nature, it is the opposite of a blockchain, information is expected to maybe be incomplete, and that freedom to fail is where creativity is allowed to flourish. it will also introduce normal people to cryptography because of it's simple nsec/npub model. I'd say most bitcoiners are very affraid of messing with their coins so they don't touch it much, and because of that, they don't actually learn experience by doing. nostr will make interacting with keys familiar for everyone without the fear of loosing money.
if you have a bitcoin node, doesn't that automatically verifies that the bitcoin is real bitcoin and comes from the right network?
i'd say branle launch, damus launch, anigma launch were significant in generating new adoption that then went on to create the subsequent waves that lead to nostrnovember
Someone was asking for this some days ago (#[0] do you remember who?), so I added it to the NIPs repo README: https://github.com/nostr-protocol/nips#standardized-tags
A list of standardized tags in use. Please send fixes and additions.
awesome. this is a well needed addition.
yo, happy bday 0xtr! :)
you search for the same content on other platforms where you have accounts with
it is a way for clients to authenticate with relays, right now, relays have basic permissions that are hardcoded and they're relative to the events they receive. i.e. they only accept events from certain pubkeys (not who sent them), or can block connections per IP, but they don't really know who they're talking to... with AUTH, the relay knows who it is talking to because the client signs a unique challenge, so they have a signed proof that the clients is X pubkey. with this, they can for example refuse to serve kind-4 notes or other things it decides should be reserved to only authenticated pubkeys..
a kind conference about notes and other stuff transmitted by relays
yes, they can require anything they want. users can leave but they might be left without features those services provided out-of-protocol. there's no way you prevent someone to use their identity somewhere else. you can loose content if those services used private relays for it and you don't have a copy yourself, if you have copies and they adhere to NIP01, then you can repost them to other relays.
I think this is the writing that better translates my pronunciation to english