No one stops you from making a new feature. As long as you want, you can make Amethyst into an omnipotent kaleidoscope-like super App. But please don't ignore the life and death of the Nostr protocol and change the protocol to meet your kaleidoscope function. Nostr is not meant to be a kaleidoscope that can do everything.
It's just a simple censorship-resistant social network protocol. Nostr needs to be kept simple yet efficient.
No, that's just a high-sounding excuse. What's really true is that you ignored everyone's advice and fatally sabotaged Nostr. We discussed this issue extensively several months ago. But it's useless for you. You can be the emperor of Amethyst, but please don't be the emperor of Nostr. Fortunately #[4] has been managing Nostr, if it were managed by you, you would just kill Nostr. You can fork Nostr to make your own Amethyst Emperor.
I disagree with the statement above. I don't believe in personal attacks when we argue.
It's interesting that nostr:nprofile1qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsz8mhwden5te0dehhxarj94ex2mrp0yhxummtda6xzun09e3k7mf0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgw3tmmj , nostr:nprofile1qyvhwumn8ghj76r0v3kxymmy9ehx7um5wgcjucm0d5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgsq29me0 and nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hszrnhwden5te0dehhxtnvdakz7qpqlunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqmkg28z were all working on their own decentralized/censorship-resistant apps before they decided to move to Nostr.
Nostr makes decentralization simple and efficient, thank you for your contribution #[2] 🫂💜
And #[2] , I'm building 🤙💪
Please do not destroy and kill Nostr. If #[0] wants to have its own centralized platform, you can fork a protocol of your own.
nostr:note188jh9ft9eddjgxk06gdruq9ggue5692spk0sy0ae8seet9ex4xps7jen53
🫂
Good morning ☀️🌸 #Nostr
Everything is changing, and we are here to make it better.
Fragile balance, which is a sign of upside.🚀🚀🚀
We have previously studied the presentation of Twitter's long-threaded topic posts, and the implementation of technical solutions is particularly complex. Need to modify the display logic of all historical posts. You also need algorithmic support. It takes a lot of energy and time for the small team we have now. This is not the most important development in our current priority, and will be placed on the future development path.
OK, thank you. I checked and found out that our client has not yet implemented NIP-42. This needs to be put on the development plan list.
I haven't tested it. However, you can add this relay, which has a broadcast function. wss://relay.nostr.band
