It’s not; if enough clients implement a very basic feature all clients need to implement it or their users will think the client is broken.
If a few big clients implement HTML rendering on kind:1s then a client that doesn’t will show raw HTML and people will think it’s sucks and move on.
Protecting from complexity at this level is important if we don’t want to end up with a handful (or less) apps in nostr.
You are making a case for why edits are bad and become de-facto mandatory if they get enough traction.
And nostr only works if it’s simple and the barrier to entry to create something new is low.
The issue is centralization; a protocol is the definition of restrictions, constrains that enable interoperability. All protocols work like this, TCP, ICMP, IMAP and driving on a highway.
The more complex a protocol is the harder it becomes to implement it, thus the harder it becomes to remain interoperable and decentralized.
NIP-69 🔁 merged ✅
P2P markets NIP by @negrunch@Mostro and Robosats’ liquidity getting merged; hopefully the first two of many p2p markets becoming interoperable.
I’m going for a BlueWallet-inspired design for Honeypot.
Multiple wallets, multiple currencies.
I added a few charts to understand the allocation of your funds across mints and a level of view of the size of your UTXOs (1000x 1 sat proofs or 1x 1000 sats proof?)
The first chart in the view will be an evolution of your balance in that wallet across time, much like the one @craigraw has in Sparrow.
#nutsack
https://m.primal.net/Lofh.mov
La casa de La Crypta… AMAZING!!! 🔥🔥🔥
If you ever visit Buenos Aires definitely have a visit, the work these guys are doing is very very cool.
Well done, @redgorila 👌
📢 NDK 2.10.4 has been shipped.
This release fixes a few very annoying bugs related on subscription lifetime, ghost EOSEs (happy halloween btw), smarter filter compilation.
Also implements the changes needed to use NIP-46 with FROST.
If you are using NDK >= 2.8 highly recommend upgrading to this release.
we should be able to get that with NIP-66 and the stuff @sandwich built:
nak req -k 30166 -t N=50 relay.nostr.watch -a 9bbbb845e5b6c831c29789900769843ab43bb5047abe697870cb50b6fc9bf923 should get it, but I see it's returning non-NIP-50 relays 🤔
kind:30166 with "#N": ["50"] should get that info 😀
@Fabian where does Nostur get the key I’m signing as? I made this pubkey months ago and no matter what I do it always signs with this nsec; I even removed all the accounts, it still signs with it when I’m signed in as my main pubkey 😓
nostr:note1n28drew24jshmkdndv3w7f68hw05cuvx34dpzlwcf009d0tq2ckqu3u405
I had a look and, like you guessed, my pubkey in the keychain had a wrong nsec -- so at some point that bug got triggered and I could never write again with Nostur -- I'd think if I logout that Nostur would wipe the keychain entry?
Oddbean new post about login | logout
Notes by PABLOF7z | export