If you are using Amber, yes. Its already part of the next release.

One balance per browser, unfortunately no way to move or synch ecash yet

Yes, as long as you dont force close the app it should work

3¢ per search is not trivial

Double tap the zap button

Dear Vitor

As a nostr newbie i need more explanations...

What are nip04 scammers?

How is the detection with dm-reporter working practically?

Gracias

Can we have a Citrine-like app that simply stores all of your pictures, images, music, videos sent to Nostr (NIP-96 Media Servers + Blossom) locally and offer those files to any Nostr client that has the hash via Android inter-app APIs?

Maybe it even syncs with other servers, like Blossom can do?

The goal is to avoid duplicating disk usage between multiple Nostr apps, removing the need for app-centric local caches where the same files are downloaded and stored in every installed Client's local database (like profile pictures).

Hi Mum

I’m in the newspaper but I don’t know what it says

**Security Update**

I've got some bad news for you guys. This morning, as I was adding error handling to flotilla, I discovered that Coracle has been sending user session objects to bugsnag when reporting errors.

Who is affected: Users who triggered an error in Coracle while signed in with their private key, since December 5th 2023.

What I've done:

- I immediately released a new version of Coracle, both to web and to zap.store

- I have deleted the affected apks from my releases

- I have deleted all my error data from bugsnag

- I have deleted my bugsnag project and rotated my api key, so lingering error reports will be dropped

- I have audited my code for use of the session object to ensure nothing else like this is happening

What you should do:

- If you're logged in with your private key, log out

- Hard refresh the page to ensure you have the latest version of Coracle

The bottom line is that if you signed in to Coracle with your private key, it has been shared with me and with bugsnag. In practical terms, your keys should still be secure, since they were sent over TLS, and have been deleted. But there is no guarantee I can offer that they are in fact gone.

I take my users' privacy seriously. My error reporting implementation doesn't record user IPs, it redacts identifying data, and it allows users to opt-out. I also warn the user when they attempt to enter an nsec into a text field. In this case, I simply screwed up, and I sincerely apologize. Reply to this note if you have any questions.

The group state does change with each add/remove but those are handled via commit messages that only make delta changes and don't require the full group state to be sent around.

Yes, once you in the group, you only need to publish a single event that all members of the group can then decrypt and view.

The largest event is actually the welcome/invite event because it has the whole tree/group state included in it. It doesn't start to become an issue until the group is ~150 (based on the max size of nostr events) but there are a few ways I've thought about to get around that so it's not that concerning.

I agree with that, but wouldn't it be better to have both?

Would users be too annoyed if Amethyst removed the "Create Account"/"Log in with nsec" and added a button to download Amber instead?