Kudos to nostr:npub1qlk0nqupxmlyxravg0aqscxmcc4q4tq898z6x003rykwwh3npj0syvyayc for implementing the feature.
Did you tell them Nostr is permissionless?
This already happens with paid relays. It’s different from Twitter because you don’t have a choice over there, but you do over here in regards to which relays you want to use. What he’s suggesting is adding extra information so that clients and relays are smarter and don’t waste resources attempting to connect.
I’m sure it will! I haven’t looked at code from Amethyst yet but will let you know! My colleagues at nostr:npub1cashappn03s3cl2ljsdntv0v28e2um5lgx4vjctqjt23pcwzjhsqmtdg5l also open sourced a work-in-progress Kotlin SDK called Nostrino, which I was planning to look at as well.
First time developing in Android / Jetpack Compose! nostr:npub1c0nfstrlj0jy8kvl953v84hudwnpgad0zx709z0ey7nmjp0llegslzg243
Then… the mother must also be a Nostrich.
BREAKING news, Bitcoin.Review gripping list of bitcoin software updates. Thanks @Mandrik @Bumi for joining me! BR040; Alby, Zeus, Nunchuk, Damus, Munity, SATSCARD, App store censorship and more!
https://bitcoin.review/podcast/episode-40/
BUT, Nothing is happening in bitcoin
Nice! (Typo? Mutiny*)
That will be possible once my calendar event NIP gets merged.
Requesting feedback for NIP-91: Bech32 URL Query. We can enable Nostr web client share links to not force users to exit their current client to view them. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr
She even pronounced Damus correctly!
In what condition and how did you manage to get it at that price? That’s pretty good! I just ordered a used but decent condition Pixel 6a for $200 USD to do Android development and compare cross-platform Nostr interoperability.
Caption this.
“How could Tim Apple hate zaps?” nostr:note1tpdrchnr42sa4h4kqnlrdn5cul7mzsh7g7m7ejyq9vccxdxn3kxsymqw5x
Repping a t-shirt that nostr:npub1vtavk0dkfjd86j6799p09td3p7t82dfgr6jd9g8njhahcgsemhtsfpkjyp gave me as I go to the office today while she’s visiting Kyiv.
Мова. Слава Україні! 🇺🇦 
Repping a t-shirt that nostr:npub1vtavk0dkfjd86j6799p09td3p7t82dfgr6jd9g8njhahcgsemhtsfpkjyp gave me as I go to the office today while she’s visiting Kyiv.
Мова. Слава Україні! 🇺🇦
It would be pretty hard to do since there’s infinitely so many clients and different ways in how they approach constructing the URL. Should there be a NIP that specifies that shared Nostr web links should attach a query parameter so that 1) other clients know how to parse and navigate to the URL, 2) doesn’t mess with the path routing in the original web client if in the browser, and 3) works universally for links shared by any Nostr web client?
For example, https://snort.social/p/npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf?nostr=npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf (or whatever NIP-19 identifier)
^ nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn would y’all have appetite for a NIP that proposes query parameter hints on share links for maximum cross-client compatibility?