It's ugly but very practical. But they should decouple the frontend from the backend, and give users direct access to their private keys like nsecs or as 12 word seed phrases. Otherwise the different instances aren't interoperable with each other. Also, without decoupling the client and server, you are forced to keep using their web implementation, which is not ideal for most privacy conscious people. Another thing is, they aren't very pro-bitcoin, so the paid instances only accept traditional fiat payments which is terrible for privacy.
Another thing is it's a product, not a protocol. So creating another compatible implementation is not going to be very easy, and forking the mostly JavaScript code is not going to be easy either
basantagoswami / Basanta Goswami
npub1gm…tdaz2
2025-03-03 07:26:09
in reply to nevent1q…8z6k
Author Public Key
npub1gmm2ehusvs35zgh6pq84m8hkj4ea0ygy3c9j2e3slzhjjce3kmns5tdaz2Published at
2025-03-03 07:26:09Event JSON
{
"id": "99256a13fda6facd89761df93fd36f41807bddc0c9aaa6fbdee3c2aa717352eb",
"pubkey": "46f6acdf9064234122fa080f5d9ef69573d791048e0b256630f8af296331b6e7",
"created_at": 1740986769,
"kind": 1,
"tags": [
[
"e",
"f63d4d725125a2909ba8aa222a9bc3dafb44f1012218eb6d19e3a2938ef1eaa4",
"wss://nostr.bitcoiner.social",
"root"
],
[
"p",
"6867d899ce6b677b89052602cfe04a165f26bb6a1a6390355f497f9ee5cb0796"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://nostr.wine/",
"read"
],
[
"r",
"wss://relay.snort.social/"
],
[
"r",
"wss://relay.mostr.pub/"
]
],
"content": "It's ugly but very practical. But they should decouple the frontend from the backend, and give users direct access to their private keys like nsecs or as 12 word seed phrases. Otherwise the different instances aren't interoperable with each other. Also, without decoupling the client and server, you are forced to keep using their web implementation, which is not ideal for most privacy conscious people. Another thing is, they aren't very pro-bitcoin, so the paid instances only accept traditional fiat payments which is terrible for privacy.\n\nAnother thing is it's a product, not a protocol. So creating another compatible implementation is not going to be very easy, and forking the mostly JavaScript code is not going to be easy either",
"sig": "e88d675163da90356c8bf84c876bd0aa3d93dea88f64a17265d3da0577b26077449f311e688bc4cd32764ca1d5b8b4c0125df34f5b9ccb333d12fd4ec92a8802"
}