Semisol on Nostr: This appears to be some sort of metrics functionality. Don’t think there is any bad ...
This appears to be some sort of metrics functionality. Don’t think there is any bad faith.
I’d recommend
primal (npub12vk…pugg) fix this.
The public key seems to be used for certain personalization, so it makes sense they might store that for debugging, but still a privacy risk.
They could rework their debugging system to integrate tracing and logging to identify specific issues, without storing search queries or pubkeys. And limit retention to a few days, and only when necessary (query error or high latency).
TIL Primal stores every advanced search you make, associated with your public key.
Published at
2025-05-01 01:49:00Event JSON
{
"id": "152ef6361793098269ce0d785995158e8eeb1a42694826b4890550c0b0fc07e9",
"pubkey": "52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd",
"created_at": 1746064140,
"kind": 1,
"tags": [
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd"
],
[
"p",
"532d830dffe09c13e75e8b145c825718fc12b0003f61d61e9077721c7fff93cb"
]
],
"content": "This appears to be some sort of metrics functionality. Don’t think there is any bad faith.\n\nI’d recommend nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg fix this.\n\nThe public key seems to be used for certain personalization, so it makes sense they might store that for debugging, but still a privacy risk.\n\nThey could rework their debugging system to integrate tracing and logging to identify specific issues, without storing search queries or pubkeys. And limit retention to a few days, and only when necessary (query error or high latency).\n\nnostr:note1g6lpr8p6jjmw8q7gj4336prk49efqk8htuwh00s43hsffy2kf2vsj390w5",
"sig": "15ba6affbcbbb590533d21d867f565f4d5231769e3cc6d5d7b70da1a36ba28a01dc6ad3b6a74c725cd26ada929d7a21838d2f3b1e3058c1514759a884fb215d9"
}
