Reply have worked before. I have also made an issue report in github but no one has reacted to it. Suddenly I see more people finding issues when replying. The deeper the thread you reply to more will happen where it is posted (level) in the thread
Folks, if you have ever used Anigma, there is an LNURL field in your Nostr profile pointing to their integrated LNBits wallet.
People might be sending sats to you there, depending on the client implementation of which wallet to choose (LNURL or the Lightning Address).
If you are like me that already lost that wallet, make sure to delete the information in that field to avoid losing more sats.
Amethyst 0.14.1 has an LNURL edit field to help you do that: https://github.com/vitorpamplona/amethyst/releases/download/v0.14.1/app-release-v0.14.1.apk
Thank for the update. Hope you solve also the reply on thread ussue. I made a issue report on github about it. https://github.com/vitorpamplona/amethyst/issues/102 . It is really simple: Replying on a thread levelep more or equal than 4 than this reply will be post on a higher level of the thread which is very inconvient for both parties. Anyway. I am happy to install this new version. 👍
Hi #[0]
Post in
Results in wrong thread level
Know bug?
After posting the relays again when they are screwed the bug seems not to occur anymore. So very low priority suddenly. Keep up the good work.
Hi #[0]
Maybe this is already a known bug of Amethyst but I still want to report it just to be sure.
The bug becomes more visible when you have a different set of relays then the default when starting from scratch and limit the number of relays to let say 10 or so.
The bug occurs when put Amethyst in the background by pressing the Android home screen button for example.
Now you make Amethyst active again and wait till the relays become active you will notice a whole new number relays are added to your relays list. More irritating is the ones you have added become inactive. I hope you see what I mean.
This will definitly be my next step. 100%. Amethyst has a bug which replies in the wrong thread for some reason. Very annoying. #[6]
Easier said than done😛. Umbrel is running on my raspberry pi... I need a lot of ☕☕☕☕ now and then give it a try. To be continued. Much appreciate your input btw sir #[3] 👍🙏👍
I try now to host iris over umbrel. Maybe that does the trick!
I don't know what you try to say with that. I use a browser extension Alby but when using the Amethyst Android app you totally omit the browser. I also tried it with tailscale extension which in in turn should eliminate the https issue but the the same result. I had expected on my local network it should work fine first. But if internally apps like iris.to communicate with https that might be a reason for not working on non https local indeed. I am surprised so many people got it working without to many tricks. Many only on Damus (again) it works out of the box...
All web nostr clients require relays prefixed by wss. Unfortunately umbrel relays requires the ws prefix. Only Damus seems to accept other than wss prefix. Hope I am wrong. I have already tried snort.social, iris.to, Amethyst Android app but all change the ws:// prefix in wss:// prefix which should not be done by the app. Any suggestions?
Sorry ignore this post. I tried to remove it but it didn't.
It's awesome. Running on Dex. No desktop for me anymore
27 running iris.to on Tab S8 Ultra. No complains about speed. A free relais.
False. Run my own node and I love it. With lnbits you can have your own lightning address. Please dig into it. In my profile you see I have walletofsatoshi but payments and tipping I do via lnbits through my own lightning node. Alby extension needed for payments on browser but that is not a problem imho