Thread - Nostr Hypermedia

corndalorian corndalorian@primal.net 0 months ago

Nostr interoperability FAIL. I have an old Android phone. I installed Amethyst and Dark Wisp. I don’t want to type my nsec anywhere on that phone. I have Clave and Primal’s built in remote signer on my iPhone, but Amethyst and Dark Wisp don’t seem to support either of those methods. I assume they use Amber, but I’m not going to put my nsec in yet another app. FAIL

Replies (5)

Vitor Pamplona _@vitorpamplona.com 0 months ago

Even if we supported, just the 400 relay AUTH requests we do to load your feed on average, would completely overflow your Clave. We tried.

1 replies ↓

Vitor Pamplona _@vitorpamplona.com 0 months ago

It's not a fail. It's an impossibility. We can't send a network request for every auth, every decryption, every draft save the app does. Amethyst more likely will NEVER work with remote signers over http/websockets. It's just too expensive. Data plans will go bust just on the back and forth.

1 replies ↓

Vitor Pamplona _@vitorpamplona.com 0 months ago

Lol.. failure is having to use remote signers because iOS doesn't allow devs to write any more efficient ways of having a signer there. Don't put an idiotic iOS limitation on us.

2 replies ↓

Vitor Pamplona _@vitorpamplona.com 0 months ago

But he wants to use an iOS signer with Android apps.. how many people you know have an iPhone and an Android phone in their pocket to make this usecase worth implementing? It's like saying that I cannot use my flathead screwdriver in my hex screws. It's idiotic.

2 replies ↓

Vitor Pamplona _@vitorpamplona.com 0 months ago

You can keep insisting that every tool needs to work with every other tool as much as you want. It will never be the case. Nostr or not.

2 replies ↓