More context, this is Apple’s requirement (thanks for sharing #[3] )

https://developer.apple.com/support/offering-account-deletion-in-your-app/

How should Damus meet Apple’s requirement on “account deletion”? The current implementation doesn’t actually meet the requirement and seems to be confusing for users. Some context: #[0]

Any thoughts about this? #[1]

*UX issue (and much more)

Actually, Apple‘a requirement is not actually met, it is just “simulated to be met”.

It says: “People expect that all data associated with their account will be deleted when the account is deleted. This includes user-generated content that’s shared with others, such as photos, video, text posts, and reviews.”

Difficult if not impossible to solve in the context of Nostr. 🤔

More thoughts about this UC issue: #[3]

Maybe it would help to add in the app description, that Damus is ONLY a frontend to the decentral Nostr network. Nostr is not even mentioned, the App description conveys that Damus is a network of its own. Maybe that’s the problem?

I suspect that the Apple requirement is targeted at central services and require that your account on the central server is deleted, which does not make sense in the context of Nostr.

Apple does not require that deleting an account in some email app deletes your hotmail/whatever account - nor that your account is banned.

I think this is a weird interpretation of apples requirement. The current “delete” feature does not delete anything, quite contrary it stores your npub and bans it, nothing I would expect from the word “delete”! I think we should put our heads together and find a better way to fulfill Apple’s requirement!

Actually, I’d expect that ONLY the key is deleted from the device. There are no “accounts” in Nostr.

Yes, I think too that most clients try to do it that way, with more or less success. But that means that you may not see every reply. But you will not see spam as well.

I expect that sooner or later all clients will try to find all relays where followers are posting to and not just reading only those relays configured. It does not make sense otherwise. You choose what relays to write to and everybody who follows you will have to read from one of those to get your message. It is inevitable to have a decentralized relay structure and miss comments, that's the way Nostr works. This can only be circumvented, if everybody reads from the same relays, which would not be dezentralized.

Ja, genau! 🇦🇹

Hallo & beste Grüße in die Niederlanden!

Let me know on which paid relays you miss your messages, we might help you to find the cause!

You may have experimented with too many relays, Damus shows you use 32 (!) relays, this might create too much traffic and Damus (or your network provider) might drop some connections. Try it with ~7-10 relays, this should be enough. Maybe 3-4 paid relays and 3-4 free ones.

Only email no npub when registering for the call… 🤫

Wen nostr??? 🤙

Self-custodial (mobile) Lightning wallets work great, you don’t need anything else… If there weren’t LNURL & Zaps! 🥲

Agree, finding contacts is an issue.

My experience is that people don’t like too many new things, so any new term should be introduced with caution. But keypairs or pub/sec-key is an important one.

The creation of a new keypair (aka account) is only 1 click in most apps, how could it be further improved?

Btw, do you think it is a good idea to call it “account” if it is not centrally managed?

A zap is public and attached to a Nostr npub, a lightning tip is private and mostly anonymous.