What phone are you using? I logged in with your NPUB but it does not crash. I think it's something unique to your setup.
Hum... We didn't change that part I think.
How long does it take to happen?
How long does it take? Does it get slower close to the crash?
My #amethyst keeps crashing and closing out of a sudden. How can I provide logs for a possible fix? The version is 0.68.4 fdroid, OS is MIUI 13 stock delbloated. Is there anything I could do nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z?
If you have them, please do. You can get from android studio.
Obtainium. É só usa o aplicativo e ele baixa automático do APK.
### #Amethyst v0.68.4: Performance Improvements
- Renames NIP-05 to Nostr Address for nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424
- Moves UserProfile NewThreads, Conversations, Reports, and App Recommendations to be additive filters
- Moves the synchronized Zap allocation block to run only when needed
- Moves badges out of the User class
- Keeping media feed active from the start of the app.
- Only logging pruning and printing stack traces when it matters
- Adds EOSE limits to the Video tab
- Adds EOSE limits to the Discovery tab.
- Only triggers the mutable state of connection if the connection actually changes.
- Reduces profile feed size to 200 and zaps, reports, and followers to 400
- Puts the Wifi signal processing on an IO Thread
Download:
- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.68.4/amethyst-googleplay-universal-v0.68.4.apk)
- [F-Droid Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.68.4/amethyst-fdroid-universal-v0.68.4.apk)
Nah... don't fight the developer instinct. Fork everything. Let's see what they got.
Boom! The Nostr address nomenclature goes mainstream thanks to Damus adding support, joining Snort, Plebstr, and Current. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z you better merge my PR quick or we'll fall behind on Amethyst 😂
I think it's too generic, but sure
https://github.com/vitorpamplona/amethyst/commit/64a5071345065c690e1b9e46f3539e519ecffc4c
Add more relays to your relay list.
The difference on a galaxy S20 in fluidity is quite staggering. Don't get me wrong, I love amethyst and admire the incredible feature rate that nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z is bombarding us with. But would love to have such fluidity on amethyst. Will check source code of both clients to better understand where lies the difference. Is it just amount of rendering components, the amount of data, or maybe more agressive caching...??
Yep, these older phones are hard. Amethyst will use over 1GB of ram just for the caching system and up to 200 threads for the multiple observers in the UI. I think these older phones weren't ready for such a massive use of ram+cpu. But maybe it's just that the Jetpack Compose isnt optimized by older processors.
I've been thinking about that reminder bot we talked a few days ago with nostr:npub1nftkhktqglvcsj5n4wetkpzxpy4e5x78wwj9y9p70ar9u5u8wh6qsxmzqs.
I've read again the NIP-01 and some discussions regarding the `created_at` property of events.
I'm wondering how providing a note for future display, e.g: in 1 week, would be handled by current clients (c.c nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z) and what should be the recommendations around that.
What i would have in mind is to have a bot that when requested, would remind a note to the requester in the timeframe made by the requester.
By allowing the notes events to provide future dates, it could allow to avoid the bot on maintaining a database on its own an only publish a note with a future date in the `created_at` field. However that would mean the clients do not display the note until datetime is past nor the associated notification.
e.g:
1. Alice asks the bot to remind some note in 1 week as an answer to the same note
2. the reminder bot publishes instantly a note with a `created_at` corresponding to the future time requested
And that's pretty much all.
I'm wondering, would that be a stupid idea to do it this way nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6?
Just "like" the note with the ⏰ emoji when the time comes. All clients will display that as a notification.
Press the square, in the bottom corner for full screen and save it. It's just an issue when the video is on the media screen and that square button gets behind the new post button.
Seems like I asked this before, but I can't remember what the answer was... Is there an easy way to save videos from nostr notes?
Saving pics is easy with Amethyst, but unless I'm missing something there doesn't seem to be a similarly direct way to save videos. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
Saving as a file or just bookmarking the video?
The app should be quite smooth in newer phones, from 2021+. The older ones and some Samsung variants that I have yet to crack. Freezing generally means the phone is using too much memory for the phone.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z why can't amethyst be as fluid (no freezing or jumping because of rendering stuff we don't know the size yet) as primal.
The bigger the feature set, the harder it is to be performant.
These look like laptop covers... just saying...
