I mostly agree with this. Specifically why I dislike nip46's ability to use public relays, relay auth can't be trusted for client-side security.
I think remote signers (nip07 for desktop) are the only way we should be interacting with web clients. Which is the purpose of my app nvault. I will eventually add direct connection only-nip46 support with nip44 encryption only.
For me there is also the UX of opening a new app and having to accept 100000 message decryption requests, then add 200ms of latency per request. This is the main reason I stopped using coracle. I can't stand declining all the auth prompts.
The final issue, is most client's can't correctly handle exceptions thrown during nip07 requests and most of them lock up after I decline 2 or 3 in a row: Coracle, Primal, Nostter, ChaChai,
I just want to choose when to load my chat, not every social client need's to handle DMs, I can go to another client for that. Most clients are only good at 1 thing anyway and most of us just hop between clients to do multiple things because theyre all broken in some way anyway.
ChipTuner
npub1qd…3fqm7
2024-11-26 16:42:38
in reply to nevent1q…pg7e
Author Public Key
npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7Published at
2024-11-26 16:42:38Event JSON
{
"id": "5af8c127a9c42daad87beff871447adb82ef08f7c25b8c958cd01f4e9802e1ce",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1732639358,
"kind": 1,
"tags": [
[
"e",
"6de9af705677b9bd3b75ccdf33448512934319de9c0ce756eaf59d375fcbdca9",
"",
"root"
],
[
"e",
"cdb6ac8c614b2dbb82f70d7080459e30ca3e758b57f07395fed0e6a549844276",
"",
"reply"
],
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb",
"",
"mention"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"",
"mention"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5",
"",
"mention"
]
],
"content": "I mostly agree with this. Specifically why I dislike nip46's ability to use public relays, relay auth can't be trusted for client-side security. \n\nI think remote signers (nip07 for desktop) are the only way we should be interacting with web clients. Which is the purpose of my app nvault. I will eventually add direct connection only-nip46 support with nip44 encryption only. \n\nFor me there is also the UX of opening a new app and having to accept 100000 message decryption requests, then add 200ms of latency per request. This is the main reason I stopped using coracle. I can't stand declining all the auth prompts. \n\nThe final issue, is most client's can't correctly handle exceptions thrown during nip07 requests and most of them lock up after I decline 2 or 3 in a row: Coracle, Primal, Nostter, ChaChai, \n\nI just want to choose when to load my chat, not every social client need's to handle DMs, I can go to another client for that. Most clients are only good at 1 thing anyway and most of us just hop between clients to do multiple things because theyre all broken in some way anyway. ",
"sig": "6714e5a0bf1c782b6417159fa250fc4c3d206803edbcc4838294d1ac7d44c59105649e27e9038db1999c061d76bc62a6ac71a88557493ebefb3ec0093605778c"
}