Did you guys start using this new nostr app?
White Noise - https://www.whitenoise.chat
Download links:
- https://www.whitenoise.chat/download
- or from zapstore.dev app
Now you can sign in using Amber. I use it for testing now, is still developing phase, but is a working app.
What conncern me is that is draining the battery quite a lot.
Any feedback?
Amazing combination of MLS and nostr. Im using daily and I faced some issues with key lost on group or individual chat. When the person uninstalled or renewed their keys your chat with them are lost in time and you have to start another one. On groups if a Adm lost their keys the group fall in a limbo.
Anyway this works very well and waiting for the security audit.
unfortunately iOS test build down and I can’t test anymore.
I have it and tested it with @ek a few months back. Haven't touched it since tho. It was mostly solo-vibe-coded last time I looked at it, and I didn't feel like doing a deep review of too many lines of code.
After the latest version, once I update, all chats and groups were wiped because you are forced to sign with a new key, or something like that.
But OK, I understand that, not a big deal. I feel it faster now, but this battery thing makes me think twice before I open it. Also on a grapheneOS, idk why, after a while is starting itself even that I killed the task.
I would prefer this app for nostr DMs than any other nostr client.
Yes. I would prefer this app at least in concept. Implementation, will have to see.
I used v0.2.0 with a test key for a 1 on 1 chat and it worked smoothly. I didn't run it enough to notice battery drain though.
I tried it a while back with @ek. I think you gave it a look too, and @optimism was checking out the code. I haven't tried it again.
Indeed, long time ago #688923 still are early days
I like seeing more messaging tools being built on Nostr instead of relying on centralized platforms. The fact that it works with Amber is a good sign for ecosystem integration.
Regarding battery drain — it could be due to constant relay connections or background syncing. Messaging apps over decentralized networks might keep persistent connections open, which can affect battery life, especially in early development stages.
It would be interesting to know:
How many relays does it connect to by default?
Is there a background sync interval setting?
Does it use push notifications or continuous polling?
Overall, experimentation like this is important for the future of decentralized communication. Performance optimization usually comes later in development.
Thanks for sharing — I’ll keep an eye on it.