nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z is this a setting that can be changed? You use on device google translate don't you?
It only does it on the Play version. F-droid doesn't allow the Google model we use to translate in device.
Not in the plan, right now. But since Kotlin runs on desktop as well, somebody out there could make a desktop app using our code base. Put a bounty. Let's see if we can attract more devs.
Usually 1GB. But with the way many profile images go for 10-50MB, it can easily go up.
Ouch, 2GB? I recommend buying a new phone :(
### #Amethyst v0.70.1: Quick Fix for F-Droid users
- Restructures the spacing in the first and second rows of a post
- Fixes Wake-Lock permission line that crashes on the F-droid version
Download:
- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.70.1/amethyst-googleplay-universal-v0.70.1.apk)
- [F-Droid Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.70.1/amethyst-fdroid-universal-v0.70.1.apk)
Well, I only make this particular app for Android. People can of course install others. I'd just would like to avoid the extra work if Android solves it for us :)
See if this version fixes it: https://github.com/vitorpamplona/amethyst/releases/tag/v0.70.1
I signed up for this tidal thing, free plan for starters. Chose favorite artists. Tried to listen to my Welcome mix. I get
"There was an unexpected error. Try again later. (S6001)"
Uncaught (in promise) TypeError: can't access property "mediaProduct", n is undefined
nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m
They should store everything on Nostr. We have better infrastructure. 😃
Just go back to the previous version.
I am not sure what's crashing for you, but there is a bug fix coming up in a few minutes as well.
Which android phone do you use again? Is it a memory issue ? If so it gets slow before crashing.
Isn't that automated for Android APKs? The phone doesn't install the app if it doesn't match the previous version's signing keys.
### #Amethyst v0.70.0: Background Video Playback (alpha)
Now you can "pin" streams and videos to the background and keep using the app/the phone while watching/listening to it.

Keep an eye out for bugs, this is a massive restructuring of how the video playback system used to work
- Moves Video/Audio player to a foreground service.
- Migrates Feed, Stories, and Live Stream screens to use that service
- Blocks screen from going to sleep if a video is playing.
- Blocks WIFI from going to sleep if an online video is playing.
- Allows the app to pause while listening to media and continue playing
- Manages cache for up to 30 videos in parallel for each of the 3 categories: local, streaming, progressive content
- Activates the use of popups with artwork that points to the screen with the video
- Creates a button to allow any video to play while browsing the app/phone
- Moves app to SingleTop mode.
- Keeps viewed position cached for up to 100 videos.
- Restructures the starting screen from App Navigation
Download:
- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.70.0/amethyst-googleplay-universal-v0.70.0.apk)
- [F-Droid Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.70.0/amethyst-fdroid-universal-v0.70.0.apk)
We could use another update from the user to identify that the stream is still live so that zap.stream doesn't need to keep updating the event to sustain its status.
This could help in the updates to the LiveStream as well.
Hmm was my understanding nostr:npub1exv22uulqnmlluszc4yk92jhs2e5ajcs6mu3t00a6avzjcalj9csm7d828 didn’t know the destination user at all? Not very similar?
To the best of my understanding, that is only true if you use a different IP for each contact of yours. Otherwise, the server can easily bundle your queues and map out who you are. They call re-using IP an "opt-it" security issue. Even though most people are reusing the same IP for everything.
Same issue. The metadata is always somewhere. On Signal, the servers at the company know the destination user and the time of the message. They claim to not be saving it, but who knows... For SimpleX, it's similar, but on their relays instead.
Clients generally filter by date, so you might not see some messages if you do this today.
Governments establishing a stronger evidence based on a time collusion of separate evidences.