Message to all other nostr devs, Amethyst now replies all kind 1s with NIP-22 comments instead of NIP-10. Most clients already display them correctly so there is no change to any of you. We are starting the migration process of the writing side. The point is to keep kind 1 for root posts as much as possible and minimize wasting mobile data when assembling the home feed.

Replies (29)

1.12.6 is fluctuating between unusably slow and usably slow so that is what I am on. The 1.13+ is just straight up unusable for me at this point. I wonder what happened to my account that made it this way, I suspect its me being so active on concord generating a ton of events.
22 concord communities, and they have even more channels. Been enjoying that protocol a lot. So 1.13+ is having to process a lot of data and seems slow even if I disable everything in the DM tab. I thought I could spare myself that by staying on 1.12 but this morning it was equally unusable, although now that seems to have cleared up again a bit thankfully.
ALso worth mentioning, I was victim during a spam attack that also flooded my DM's with spam messages during the past weeks. So while I blocked those accounts and they are blocked on amethyst it may or may not have to process hundreds of additional DM events.
Interesting.. well, 1.14 does have some performance improvemetns for both concord and NIP-17 for those exact problems. Have you tried? It's supposed to load faster. I have been using Corcord just with the SoapBox cchannels, so not as heavy, but I can try to join more to see what happens.
I did because I read that. Unfortunately no fix, so I then downgraded to 1.12 again and noticed it was so laggy but now it seems more caught up again. Amethyst in general has always been the most laggy app currently on my phone but its also a great future rich client so I accepted that. Would be nice if it had the speed of the other nostr apps though since on my OnePlus 3T on the latest versions but even this morning on 1.12 the loading account screen takes minutes and then stays laggy for a while after. Battery wise ill let the stats speak for itself. image I think on battery you'd notice it the easiest with a newer phone.
As I wrote that I reset the amethyst app and now its minutes again before the UI is usable. Its always that initial load that lags it so much, if I leave it open for a few minutes its usable again. The initial load does make android ask me if i'd rather close the app.
Hum.. I wonder what it is... If you create a new account on a new version of Amethyst and follow all your follows (you can import follows form another account when setting up), would that be fast enough on 1.14? If it is, then we still need to work on the concord/nip17 DMs performance. If not, there there is something else going on. ๐Ÿค”
Gave it a try, instant lag fest right after importing them. So maybe its simply pulling to many messages? But does mean my lag is from the act of following them all alone. And I bet the concord stuff on top of that is not helping.
I wish there was an easy way for you to emulate my CPU speed on the phone since your phone could be to new for you to notice. If its android 9 compatible I should probably try it in a VM. For full transparency I exclusively use the fdroid-universal version.
Gave that a try, also laggy during load and thats on a 6800U ryzen core. image It bringing my phone down to its knees i'd expect, it also bringing the VM down to its knees means it should be reproducable.
โ†‘