Oddbean new post about login | logout @greenart7c3's Amber Signer is now an official NIP. It was just merged. 🚀 Devs working on Android apps (Native or PWAs) should not allow nsecs in their apps anymore. Amethyst will start to deprecate our nsec-based logins in the upcoming versions. https://github.com/nostr-protocol/nips/blob/master/100.md
Does this mean you will have to use a nip100 signer to use Amethyst on Android? Do you have plans to add nip46 support?
Good thanks
I’m working on something to help with onboarding new users to nostr. How do you see new Users coming in to Amethyst?
They usually come on word of mouth (a friend inviting them to join) and usually drop into our chat to say hello and get the initial tips.
Ok. What about a random coming from Xitter because they don’t want to KYC over there? They download Amethyst and then what? They’re gonna go to a key signer app and then come back to Amethyst and then get started?
Humm.. yeah I havent thought about this with Amber. We gotta figure it out. Usually they just create a new user on amethyst. Random people coming from Twitter because of KYC has always been minimum. Every new user wave has been triggered by either influencers or word of mouth (what's app style).
Xitter is introducing KYC for monetised users (ie bluechecks) from July 1. People over there aren’t happy and it’s getting worse in future with Gov regs across the West. I’m creating something to help direct onboarding because per your point, if we can even get a handful of influencoors with big followings to join up we’ll see waves joining in short order when they encourage signups. I think ideally new users create keypairs in client and move to key signers later when they want to connect with other nostr services. Do you think there’s a more frictionless onboarding flow?
nostr:nevent1qqs8whhpavu787jrud73l35u6nsj8kmqt7ekjq6wnlkk2aw8992w7ucpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qygzxpsj7dqha57pjk5k37gkn6g4nzakewtmqmnwryyhd3jfwlpgxtspsgqqqqqqszcwl98
2 apps at once or integrated? 🤔 hmm nostr:nevent1qqs8whhpavu787jrud73l35u6nsj8kmqt7ekjq6wnlkk2aw8992w7ucpz3mhxue69uhkummnw3ezummcw3ezuer9wcpzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqvzqqqqqqyeuspaa
> Devs working on Android apps (Native or PWAs) should not allow nsecs in their apps anymore. Sounds exaggerating. nostr:nevent1qqs8whhpavu787jrud73l35u6nsj8kmqt7ekjq6wnlkk2aw8992w7ucpr9mhxue69uhkymmnw3ezumr9vd682unfveujumn9wspzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqvzqqqqqqymn0u9q
Heck yes! Finally. Been using Amber for a couple months now and was finding it hard to believe how inputting nsecs was still a standard. A necessary step for nostr but good riddance.
Huge. This will drastically improve security for users overall. We shouldn't be inputting our private keys into applications unless it's a key signing application or extension or similar. nostr:nevent1qqs8whhpavu787jrud73l35u6nsj8kmqt7ekjq6wnlkk2aw8992w7ucpz9mhxue69uhkummnw3ezuamfdejj7q3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqqqqzdujxjj
This is fantastic. The nsec will be as valuable as seed words soon. It should be protected. nostr:nevent1qqs8whhpavu787jrud73l35u6nsj8kmqt7ekjq6wnlkk2aw8992w7ucpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqzyprqcf0xst760qet2tglytfay2e3wmvh9asdehpjztkceyh0s5r9cqcyqqqqqqgag75u2
How is it different from nip46?
It communicates via Androids inter-app messaging systems instead of via websockets.