If you have seen Amethyst crashing after loading a specific npub, this should fix it.
Discussion
Everything is running like before again, only even better. Thank you 🤙
Do I zap nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj703s8dt or the list of devs for their efforts?
The list of devs is better.
Looking good.
Can I feature request here? Is there a way to initiate ephemeral chats on Amethyst, or is one coming?
Not yet. I just don't know where to put the button. :)
It could be an option on the "new note" button.
Like *click* "new note?" "New chat?"
It would also be nice if the chat itself (not necessarily the messages) could stay in the messages list once you click the join button. That way you can easily resurrect old chats. Add it is that disappear from view, and return when there is activity.
It doesn't work for me, so I've switched to Primal for now. With the latest Amethyst, it's almost as though I'm in a bubble of my own. Lost almost all follows and followers. No notifications....
Hum.. strange, I can see your feed just fine with your npub. 🤔 It doesn't load any post?
It loads some if them, but my feed is quite different from that on Primal, and I'm not getting notifications.
Ok, I've added a broadcast relay as suggested by nostr:nprofile1qqsda2memtapc2lykjnd8t9px4ake2stw39lg6k49xj6u3jz3pteu6qpz9mhxue69uhkummnw3ezuamfdejj7qg3waehxw309ahx7um5wghxcctwvshszxmhwden5te0wahhgtnydamku6tndah8g6r9w4czucmp9uwezsfz. It seems to be working now.
Thank you!
Interesting. You didn't change any other list, just the broadcast?
Sorry yes, I added a local "Citrine" relay as well.
Weird. I will do some testing on this
Update..... Amethyst still doing weird things for me. My feed is almost empty when compared with my Primal feed. Relays not working.
How many relays does it connect to?
It was connecting to at least a dozen, but I've uninstalled the update now, and gone back to v 0.94.3 that behaves as expected.
There was a major change to how relays work. Might need to adjust some things.
> crashing after loading a specific noun
Not validating input ... nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9uq3wamnwvaz7tmkd96x7u3wdehhxarjxyhxxmmd9ukfdvuv understands coding as much as he understands money.
I was validating. The tag is a valid uri. But it is still crashes not only the app, but the low-level socket at the OS level. It kills java itself without any exception reported.
The Android JVM/OS has a bug there???
I don't know. I didn't investigate further. But the exception wasn't in the app. So much that the app would be killed without any sign of a catch by the JVM. So, my hunch is that is not even in java. It's lower. Likely either one of their native libs or a lib in the OS itself.
The tag uri has over 1000 chars. So, it could be as simple as an overflow in C code.
Oof