nostr clients that don’t support bech32 links 👎🏻
This is kinda wild? 
I hit this all the time and it pisses me off.
I have none.
I think the mobile clients on both platforms (ios and android) need better UX.
I’m mostly sticking with desktop for now.
Easy fix: just go IPv6 only 🧠
I started getting a taste of this a month or two ago.
topaz runs almost everything through LMDB and I think it’s one of the best investments you can make in UX as a client.
You’re not wasting your time.
Ah Amethyst, that would explain it, for sure lmfao. 🤣
In all seriousness, it’s a problem with a lot of clients.
And some relay operators (such as damus) still have binaries that produce unexpected results with filters too. I don’t think relay devs were on the same page about this initially, but also, bugs were shipped into prod as well.
The ecosystem is young and mostly what you are experiencing is a result of that, for mixed reasons.
We will continue to build, and things will refine 🤝🏻 things have already come so far just in this year alone.
Only here for the good protocols 🤝🏻 nostr:note15vmd70phadek58asua2zrhc2uak43xlm9txn0yxev7lpynrkvjsq663fyt
https://advancednostrsearch.vercel.app
This service is awesome.
A few folks in the strfry telegram have acknowledged a bug in how dates were handled in filters. Doug acknowledged on May 3 that the bug had been fixed (screenshot attached).
Also, see this note from fiatjaf, who was doing some tests and seemed to find damus was running a version with the bug. At least, this is what they later claimed in the telegram thread.
nostr:note146yjpuqexrxmu4lzcvztzvtysv5d8vft76uuyd6puke7zjrmmayqn5lw6x
I personally find the Damus relay to have odd behavior (sometimes, at odd times) with the events it returns. I’m not in a position to provide reproducible examples, but knowledge of the bug is real.
Cc: nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s you should update your strfry binary, I think you are running a version with screwy logic on filters.
Ya saw this. Clever work around and certainly not out of the question that we build some remote capabilities in the future.
Unrelated but also something I’m keeping my eye on: technology like nsecBunker. I could see us supporting things like this down the road too.
Eh not entirely, you can hardly even zap with Damus any more. :(
We’ll be taking a very conservative approach out of the gate, since we are launching apple only initially, but our roadmap is much bigger.
there will be a Linux (+windows and MacOS) desktop version (based on the same code) that will launch early next year exploring more progressive and integrates ways of doing payments with content and chat and stuff.
Honest to god this project has taken fucking forever but we are very excited to share
That’s where the alphas were built but the repo is back in private hands as we prep to launch. I’ll be deleting that code soon after launching.
Most of the significant code for the topaz project now lives here in this general purpose library I built:
We will ship on iOS. Mark my words. #soon nostr:note1askv74hs3pgjdqd3z5v9wwk8e58fgczwhwt5nkqcf6ucj4d5atssxqhda4
nostr-kit got NIP-04 today ✅