We need a nostr client with no fucking images. Like this shit is such a waist of mental space and energy.
#nostr
#unix-principles
Is it just me or is all the pieces in place to do Knowledge Management of #nostr.
What am I missing?
Mutually exclusive write access to a chunk of memory
Goddamit I’m fell for the twitter shit. Troll af 🤦
Sorry it’s not twitter. It’s not instagram
Can someone explain to me wtf is #threads. It’s not Twitter. It’s instagram. What have we done.
#nostr is our only hope. 🤦♂️🥹
You think doing email over nostr is possible? Or do we have to rethink the concept of email usage
#nostr #email
The power of nostr and bitcoin is the fact that anyone can own copies of your data, that means they have read permission, but only you have write permission.
If I post my nostr note, signed, on Twitter. Twitter owns a copy. That’s it. If they delete my account, that’s fine, cause other relays and myself still owns the same copy.
Ledger, the company, does not own my Bitcoin. Though they have read permission.
Furthermore, if someone takes my note and changes it, then signs it, then the signature will differ. And anyone will able to verify that it was tweaked.
You can only post through your account on Twitter if you are logged into your account. That is too say: The twitter API call authenticated you via some Security Service. That is how they know it’s your note. Cause it was posted via your credentials.
However, in nostr your credentials are embedded into the note itself via the “sign” field in NIP-01. This allows someone, anyone, to verify my note simple by looking at my note. They do not need to trust the authentication of any account.
If I post my signed nostr note on Twitter, then twitter will “act” as a relay in this instance. Twitter will own a copy of my note. But anyone can verify that note was signed by me without depending on Twitter API at all. In the real world though, using Twitter as a relay is useless.
Then according to you, what is the purpose or a relay? A relay stores a copy of a note. And allow the distribution of that not to any client that REQ it. Hence, a relay relays events. Technically a relay does not even have to store the events in a DB, it can simple relay them to connect clients. What am I missing?
As a bitcoin analogy: Does every node that has a copy of the ledger own your coins? No. Obviously not. Even though it’s literally a public ledger. You own your coins, cause you own your keys. You have write permission. Everyone else (or everything else) only has read permission.
A Bitcoin node exists to validate TXs. A Relay exists to propagate copies. The more copies the higher the probably of your SIGNed event to be observed (read).
Your events are signed by you and you only. Relays are only a “view model”. You need copies of your events. A relay owns a copy. You own the data. If someone reads an event that was not signed by me nsec, then they are not reading my event by definition. You’re confusing the concept of digital copies with that of cryptographic ownership.
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 what is your take on microservices?
Is the #nostr community responsible for the websocket package in Go standard? 🧐
Got it. Had to properly escape my content. God dammit.
testing
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
My event serialization is correct. Do I need to have tags populated with pubkey?
WTF is wrong with my ID. I get this response from relay.damus.io:
```
["OK","4f0df82388813961c05a22534685af7b759ab14e362659f6aa5d2e60ee54b9e0",false,"invalid: bad event id"]
```
#damus
#nostr