Oddbean new post about | logout
▲ ▼
verbiricha | 1 years ago (raw) | export | reply | flag +44 
 i don't know who needs to hear this right now but read and respect the NIPs, don't blindly copy other people's code. all nostr clients need to be interoperable and the spec we agreed upon is on the NIPs. there are mistakes, bugs and leftovers from experimentation in some clients.
▲ ▼
Auxmos | 1 years ago (raw) | root | parent | reply | flag 
 🤝
▲ ▼
elomelo8382747958d863 | 1 years ago (raw) | root | parent | reply | flag 
 agree with u
▲ ▼
nickionbtc | 1 years ago (raw) | root | parent | reply | flag 
 nostr:nevent1qqsddvk67ahsfe7was6t5lhshurrk3nuvd50tmn37ttnuw36vy7d8fcpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqnnv3mga3szzkwgxke9zf3qmg08kd8x2h3gpwsygya9w0qrrlqspqvzqqqqqqyh33jfv
▲ ▼
hodlbod | 1 years ago (raw) | root | parent | reply | flag +1 
 Agreed, and for anyone trying to do something non-standard, NIP 78 is your friend. You can often experiment there with your own custom namespace, then upgrade user data to a standard version when it exists.
▲ ▼
TheGrinder | 1 years ago (raw) | root | parent | reply | flag +3 
 nostr:note1ey7yudl8pudn05yjn588jf0tpamefrqu99aztx5w9nlp8rjckjpq4hj45g
https://m.primal.net/HLjO.png
#nostrdesign #nostr #plebchain
▲ ▼
JeffG | 1 years ago (raw) | root | parent | reply | flag +1 
 “In some clients…” 

I think we’re all guilty. 😂
▲ ▼
Mike Dilger | 1 years ago (raw) | root | parent | reply | flag 
 I must confess I haven't looked at anybody else's code yet. I'm too busy for that.
▲ ▼
N | 1 years ago (raw) | root | parent | reply | flag 
 nostr:nevent1qqsvj0zwxlns7xeh6zff6rneyh4s7au53swzj739n28zelsn3evtfqspr4mhxue69uhhyetvv9ujumn0wd68ytnhd9ex2erwv46zu6ns6l9zux
▲ ▼
3328fc6c | 1 years ago (raw) | root | parent | reply | flag 
 Respec muh authority!

Bro tell that to Damus or Amethyst. Loads of things they do contrary to existing NIPs, then their thing becomes the new standard cause other clients implement it as well to be compatible with the big boys.
▲ ▼
fiatjaf | 1 years ago (raw) | root | parent | reply | flag 
 nostr:nevent1qqsvj0zwxlns7xeh6zff6rneyh4s7au53swzj739n28zelsn3evtfqsppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszyrhwden5te0dehhxarj9ekk7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9thwden5te0wfjkccte9ehx7um5wghxyee06g4903

I'll add to this: stop trying to fix other people's clients on your code. That is the road to protocol bloat and death. Don't trade away the simplicity of Nostr in order to get 0.001% better UX for your users or we will all lose in the end.

If you see that some client is doing something wrong, try talking to them, or bring it up on Nostr, that benefits everybody.
▲ ▼
Joe | 1 years ago (raw) | root | parent | reply | flag 
 How often are client devs all meeting together to work on Nostr? Do you all meet like one a month on Nostr Nests or anything like that?
▲ ▼
0xDEADC0DE | 1 years ago (raw) | root | parent | reply | flag 
 Is there a place to meet? I need it