god on Nostr: I believe cookies are stored on the client. So the reason for the intrusive cookies ...
I believe cookies are stored on the client. So the reason for the intrusive cookies confirmation banners is that the site is asking permission to store those cookies on your device. I don’t think a signature from your nsec would match this use case. But maybe you could use your nsec to add in your own client’s “policy” so that you don’t need to be asked about it. I guess cookies are dumb and they’ll be done away with. But businesses do like to have some sort of analytics on their site visitors. Fine with that, just looking to automate that policy and place control with the client. And do it in a way that’s not retarded like the current way (cookies prompts).
Published at
2025-01-28 01:50:36Event JSON
{
"id": "6097a2b9163675faa3c0ef19b523e3f2b175aa59a355746e842a1b4aff2eec29",
"pubkey": "b0803f9ce4cf9c051c9263c46869fe6edb1b67af71d80048a6ee26aaaa1e2dfb",
"created_at": 1738029036,
"kind": 1,
"tags": [
[
"e",
"a2c1fd254efb565b18a1193c648075b422dad9fb7d9838612c4ae7b9dd473cb5",
"wss://relay.wellorder.net",
"root",
"b0803f9ce4cf9c051c9263c46869fe6edb1b67af71d80048a6ee26aaaa1e2dfb"
],
[
"e",
"2314b99042fe7dc2d8316ef30b38bda53b8d8184ce127109e21009feb9c1b3f9",
"wss://nostr.bitcoiner.social",
"reply"
],
[
"p",
"34b1051e56a2503c30133b9c2536ae9fe2b5624924655c2d05145073b53d63b7"
]
],
"content": "I believe cookies are stored on the client. So the reason for the intrusive cookies confirmation banners is that the site is asking permission to store those cookies on your device. I don’t think a signature from your nsec would match this use case. But maybe you could use your nsec to add in your own client’s “policy” so that you don’t need to be asked about it. I guess cookies are dumb and they’ll be done away with. But businesses do like to have some sort of analytics on their site visitors. Fine with that, just looking to automate that policy and place control with the client. And do it in a way that’s not retarded like the current way (cookies prompts).",
"sig": "bf36ecf33faf4b3af82e2fe408eb0bc0a98ed853d8f4babe3e6a3fc7618bdac5e23517bfbf18bee0d74be8f9daea530c6502ad77128b9a053b867d30945658c1"
}