The app uses traditional login but automatically generates keys for the user which are used to sign events in the comm rooms. at this point no relay - the posts are public but encrypted unless viewing from the app itself. we also use a private db for some info. Keys are kept saved in encrypted form in said private DB. I tried to basically circumnavigate the annoying UX parts for the user by doing these things but also as a way to suppport and get more people to use nostr in a n(n private way eg introduce them to it easy. Many of them will be noobs to privacy and BTC but we will bring them to the "light side" slowly but surely. Later Ill add login for nostr natives as well to avpod the whole email thing - fake emails are allowed though if people want to use an alias email to secure their ID further and even suggested at sign up!

Replies (1)

I don’t know how data protection and id verification laws are shaping up in your country, but in Australia, Europe, and USA they are hitting hardest on social apps with “traditional” custodial handling of user accounts and data. Big social is 💯 behind this, as it hurts the competition more than the establishment. You might consider deeper Nostr integration if you want your app to survive the next few years.