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
Why can't we all just agree on a single field instead of polluting everybody's kind0, increasing bandwidth usage of everybody and making the logic of every client much more complex? The only point of having a standard is not having to support every different bizarre implementation people come up with. nostr:nevent1qqsdhveyzt5e4ssss2fgvtxp03ax7yhnpdyqqu6f6kku49fsy56p72gpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtcpzpmhxue69uhk2tnwdaejumr0dshsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uq3uamnwvaz7tmxv4jkguewdehhxarj9e3xzmny9acx7ur4d3shyqtxwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tmwwp6kyvtpxdc8vam9xfcrxa3hd4hx573kdpkx2d3nwgmrywrhdsuhwdfkxashwdm4xgekv7n3wvcrvvnkx4m8zcm3w96nxum8dqen7cnjdaskgcmpwd6r6arjw4jszrnhwden5te0dehhxtnvdakz7qguwaehxw309ahx7um5wgkhqatz9eek2mtfwdhkctnyv4mz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qyg8wumn8ghj7mn0wd68ytnddakj7qg3waehxw309ahx7um5wgh8w6twv5hszynhwden5te0dehhxarjxgcjucm0d5hszxnhwden5te0wp6hyctkd9jxztnwdaehgu3wd3skuep0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgkwaehxw309aex2mrp0yhx6mmnw3ezuur4vghsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshszgthwden5te0wfjkccte9ehx7um5wghxyctwvshhyetnw3exjcm5v4jqz8nhwden5te0wfjkccte9ehx7um5wghxyctwvshhgun4wd6x2eqpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhszxrhwden5te0wfjkccte9ecxcetzwd68ytnrdakj79yusvu
Vitor Pamplona @Vitor Pamplona - 1y
The truth is that in Nostr you have to support what everyone else does otherwise the UX is just terrible. This is just one of the 1000s of little things we need to do to support interoperabilty in the protocol.
But, more importantly, we can't have a protocol where people can do "whatever they want" without running into these little issues.
NIP here: https://github.com/nostr-protocol/nips/pull/794
Derek Ross @Derek Ross - 1y
Agree. Has no one read the XKCD on this?
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.
PABLOF7z @PABLOF7z - 1y
public-shaming driven development nothing wrong with that
Русский бот @mikedilger - 1y
I must confess I haven't looked at anybody else's code yet. I'm too busy for that.
2d5b6 - 1y
nostr:nevent1qqs9pt0ghyzzq7p6pqajnlvjgr7n9tyhy0vhpuyhgvdrd6y5r50n90cp9emhxue69uhkummnw3ezuamfdejjcamnwvaz7tmjv4kxz7fwdehhxarj9emkjun9v3hx2apwdfcqe8eq5t
fiatjaf 他の人のクライアントを自分のコードで修正しようとするのはやめてほしい。それはプロトコルの肥大化と死への道だ。ユーザーにとって0.001%でも良いUXを得るために、Nostrのシンプルさを犠牲にしないでください。 もし、あるクライアントが何か間違ったことをしているのを見かけたら、そのクライアントと話し合うか、Nostr上でそれを提起してみてください。 nostr:nevent1qqsf8ugj8luqy4ecfeth3e5lsu5thaxzu08lu6kvz8e5en2t8lvc5vcpr4mhxue69uhhyetvv9ujumn0wd68ytnhd9ex2erwv46zu6nsyp389y
nostr:nevent1qqsvj0zwxlns7xeh6zff6rneyh4s7au53swzj739n28zelsn3evtfqspr4mhxue69uhhyetvv9ujumn0wd68ytnhd9ex2erwv46zu6ns6l9zux
Yes. https://this.how/standards/ https://fiatjaf.com/27598e6f.html
