The concern isn’t around public keys needing to be private or even anonymous - it’s more targeted toward publishing lots of event kinds by default (without opt-in, or even not being obvious is client UX, including new ones), when all I actually want to publish are kind 0,1,3,7,42,1984,etc (profile, notes, contact list, reactions, channel messages, spam reports, etc).
Pubkeys may be cheap, however I’m not going to create 100 just to segment or try obfuscate my data. Pubkeys if stored correctly, shouldn’t be throw away use for people - unless that’s their intention.
I have no issue with 1,000 NIPs that may content private/sensitive information being drafted - that’s 100% fine - the issue is that data being published by default by client apps - and not opt-in and clear in UX.
wakoinc / Blake
npub1kt…rmrvj
2023-02-26 10:37:27
in reply to nevent1q…ug5g
Author Public Key
npub1ktw5qzt7f5ztrft0kwm9lsw34tef9xknplvy936ddzuepp6yf9dsjrmrvjPublished at
2023-02-26 10:37:27Event JSON
{
"id": "6f6940dc54937132bce7c9e664afde7f9d2ab4c76acddb6c4b487f84e98b0004",
"pubkey": "b2dd40097e4d04b1a56fb3b65fc1d1aaf2929ad30fd842c74d68b9908744495b",
"created_at": 1677407847,
"kind": 1,
"tags": [
[
"e",
"4eb3673ef5b1b77d83902e55a0ca409a3134f0eb53c2d482d7782d731d873521"
],
[
"e",
"c20a2e806d7901446d1217798f2c35b5d1331a9b1f2de9ca239fcf2773f27def"
],
[
"p",
"7560e065bdfe91872a336b4b15dacd2445257f429364c10efc38e6e7d8ffc1ff"
]
],
"content": "The concern isn’t around public keys needing to be private or even anonymous - it’s more targeted toward publishing lots of event kinds by default (without opt-in, or even not being obvious is client UX, including new ones), when all I actually want to publish are kind 0,1,3,7,42,1984,etc (profile, notes, contact list, reactions, channel messages, spam reports, etc). \n\nPubkeys may be cheap, however I’m not going to create 100 just to segment or try obfuscate my data. Pubkeys if stored correctly, shouldn’t be throw away use for people - unless that’s their intention. \n\nI have no issue with 1,000 NIPs that may content private/sensitive information being drafted - that’s 100% fine - the issue is that data being published by default by client apps - and not opt-in and clear in UX.",
"sig": "25f4a10965ce25f4027d9eee98deff53d68fed8609870f82750277f1d8a24c606cc4800ea3236618f1264dcf60ff6f535defcc1e4e71028c1a34930f9c2de181"
}