the NOSTR protocol relies heavily on HTTPS client server connections.
a problem that I am beginning to see with NOSTR, public and private keys are a way out of the control that Google, Microsoft and various companies have over the identity that users around the world have through emails.
instead of teaching and showing the advantages of keys and relays, developers are only adding the option to start section with Google making the option to create keys or signers meaningless, because you will want to touch those options when you only have to use the usual?
right now adding Google tools seems easy, but what would happen if in a few years Google or those in charge of web maintenance start adding things that would make just eliminating Google options difficult?
a few weeks ago an update occurred in the way the https protocol connects to servers to recover files
ipfs gateways are the ones that were affected in that, IPFS could be an option to the bloossom servers used in NOSTR, but now clients can no longer recover media files from the gateways because they are now marked as insecure.
with NOSTR, attacks, instead of coming with legal threats, could come with simple web protocol updates in which clients would simply no longer be able to connect to relays and servers that anyone could run simply because they were marked as insecure, causing few to be able to run relays and servers because only they will be able to comply with the things required by https connection protocols
The_Crin
npub1v4…ec9al
2026-10-05 21:33:29 GMT
in reply to naddr1qq…wx84
Author Public Key
npub1v4qqsdtwt2ezzmhax339t82k7t9t85w38f7ksv3vhtrzkya6z0hq4ec9alPublished at
2026-10-05 21:33:29 GMTEvent JSON
{
"id": "59c9d887e7da1242cfbc9503ec5950ab745639788acb678765ac88f5d5d59bdd",
"pubkey": "654008356e5ab2216efd3462559d56f2cab3d1d13a7d68322cbac62b13ba13ee",
"created_at": 1791236009,
"kind": 1111,
"tags": [
[
"A",
"30023:54609048284d2a151c8df625f40c389d423ed057fcef927db88956d28e22ba03:1582621",
"wss://relay.ditto.pub/"
],
[
"P",
"54609048284d2a151c8df625f40c389d423ed057fcef927db88956d28e22ba03"
],
[
"K",
"30023"
],
[
"a",
"30023:54609048284d2a151c8df625f40c389d423ed057fcef927db88956d28e22ba03:1582621",
"wss://relay.ditto.pub/"
],
[
"p",
"54609048284d2a151c8df625f40c389d423ed057fcef927db88956d28e22ba03"
],
[
"k",
"30023"
]
],
"content": "the NOSTR protocol relies heavily on HTTPS client server connections.\n\n\na problem that I am beginning to see with NOSTR, public and private keys are a way out of the control that Google, Microsoft and various companies have over the identity that users around the world have through emails.\n\ninstead of teaching and showing the advantages of keys and relays, developers are only adding the option to start section with Google making the option to create keys or signers meaningless, because you will want to touch those options when you only have to use the usual?\n\nright now adding Google tools seems easy, but what would happen if in a few years Google or those in charge of web maintenance start adding things that would make just eliminating Google options difficult?\n\na few weeks ago an update occurred in the way the https protocol connects to servers to recover files\nipfs gateways are the ones that were affected in that, IPFS could be an option to the bloossom servers used in NOSTR, but now clients can no longer recover media files from the gateways because they are now marked as insecure.\n\nwith NOSTR, attacks, instead of coming with legal threats, could come with simple web protocol updates in which clients would simply no longer be able to connect to relays and servers that anyone could run simply because they were marked as insecure, causing few to be able to run relays and servers because only they will be able to comply with the things required by https connection protocols",
"sig": "af343c36b62acc13d83985db66d209ff196a612fe01a1d3048466347fbc729d072a0d3ce019044aa553c7921189d52ab709ecc6a463198f566c4e961930f3801"
}