7fa56 - 1y
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.
JeffG @JeffG - 1y
“In some clients…” I think we’re all guilty. 😂
3bf0c - 1y
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.
Русский бот @mikedilger - 1y
I must confess I haven't looked at anybody else's code yet. I'm too busy for that.
2d5b6 - 1y
nostr:nevent1qqsvj0zwxlns7xeh6zff6rneyh4s7au53swzj739n28zelsn3evtfqspr4mhxue69uhhyetvv9ujumn0wd68ytnhd9ex2erwv46zu6ns6l9zux
