They way you are executing it just straight up absurd.

1. Why storing draft in relays, not in local? Sure for sync but atleast give option to store locally. Even it's encrypted, Privacy please. spies will know how many dozens of notes we are drafting and we are tired removing each of them at every single relays.

2. When you automatically draft, Why don't you tell user that it was automatically drafted by giving a toast "Saved as draft"

Reply to this note

Please Login to reply.

Discussion

A local relay would help here or a configuration option for which relays can save drafts. I don't think spies would care how many encrypted drafts you have.

The problem was there's no built in local relay in amethyst like nostrmo did.

I'd like to see that added. It follows the nostrdb model of Damus.

Nah, the goal is to never add a local DB directly into Amethyst. It's too centralizing. We will be using other apps that can do the local db part.

> Why storing draft in relays, not in local?

Iteroperability and Decentralization. Everything will be stored on relays in time. One goal of Amethyst is to not have a local database. There is no need to be a relay and a client at the same time. This is the decentralization Nostr gives us. If the goal is to keep things local, why even use Nostr? Just build a regular app.

> Why not the popup?

I added, but since it saves all the time, it became a very annoying popup. Maybe we can do some other form of UI hint for this.

I will say that I didn't know if my note was saved in drafts and had to go looking for it. I also knew it was there. I don't want an annoying pop-up every single time, but maybe for usability, show an indicator the very first time and then never show it again.

You may add the confirmation popup like the following:

Draft Note?

[Save] [Cancel] [Discard]