without standards, interoperability between clients falls away. client maintenance to support all the "nonstandard" things creates friction in the development process. there are definitely at least a few highly recommended if not standardized NIPs that need to be adhered to. there's a reason the browser wars have started to end in browsers working together to standardize. 

nostr:nevent1qqszsypl99cq3yuke4lhtve7x9jyqk8l694sx32h2l2uqmwvgd4qu7spz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jqvzqqqqqqymea045 

 it was always headed this way, which is why a lot of devs abandoned it and focused on its market place usage, the most interesting stuff getting built rn is on llms and L402 

here’s a post on sn back in february
https://stacker.news/items/131593/r/Car

sometimes you got to let grassroots stuff grow organically and not throw so much gasoline on it

live and learn 
🤙 

 💯 still better than twitter tho 

 yeah I mean I'm all for letting people go buck wild and do what they want. my only issue is that some standardization is required to define what nostr is. otherwise we are all just building random web apps that may or may not break other web apps. we've definitely made too many nips. there's only a handful that relevant to everyone.  

 i think back in dec 22 jack at the time did the right thing, literally elon was well on pace to get his wechat app, done this way, technically some apps could just focus on privacy side