Essentially forcing folks who use amethyst, to use a whole new client to partake?
As time goes on, the less I'm able to do with these kinds of changes happening to everything...🤷
I do not want to use another client or app just to use nests, badges, etc.
Then don't use another client. You'll be able to use Amethyst to listen and text chat just fine.
I mean I understand it's me, and folks don't want me to participate in their nests anyways.... but come on...what about the other people? What about new people?
You basically said it yourself that amethyst users would not be able to actually use nests other than to type or listen....
Amethyst users are Nostr users. They don't need to create Nostr keys. They already are on Nostr. This would be for someone visiting the website.
So I won't need to use nip07 to create a nest?
Im finding Nip07 excludes many mobile only users from using nostr things. There's an app for everything. We don't wanna use another one just to fully use all nostr features/ services. Always a big hurdle when teaching new folks....
"Ugh, I've already just installed 2.... another just to manage my badges I recieve? 😑"
"Well you could just always use Kiwi..."
"I don't like it"
"Yeah, me either."
🤷
At first you will have to use a web browser that supports NIP-07 or sign in with nsecBunker to create a Nest. Listening and text chat is different and will work without extra work. Eventually, I'd like to have clients use the Nest API to create them, but that's not launching just yet.
I can relate to this, clients are closing options to join in and only allowing some login abstraction and disregarding the basic protocol. It's starting to look like classical websites. A client should always give an option to insert nsec imo. The same goes for zaps, some clients only allow NWC zapping which means having something like Alby, to zap you would only need any LN wallet.
Never enter your NSEC into a web client. Always use NIP-07 extension.
Let users choose, you can put a warning, Coracle it uses nip07 by default, otherwise nsec. Nip07 you have to trust the extension, you can also trust a specific web client, i can be using a burner nsec. Also if you open the web client in mobile there aren't many signers for mobile, what will clients require next for safety reasons, 2FA? I don't think we should treat users like children and decide what we think it's best for them, let them know the options and risks and decide.
Imagine bitcoin mobile wallets not allowing you to insert a private key, you could only receive or broadcast a previously signed tx by an hardware wallet.
