Fabian on Nostr: > I also see the value of having certain types of mutes public Yes public mute is ...
> I also see the value of having certain types of mutes public
Yes public mute is useful, especially to remove some possible taint from one's WoT, but maybe it's better to use public reports for that so the mutes can stay private. At the moment Nostur doesn't do anything with reports yet, aside from being able publish them.
> You mentioned that "last seen" metadata is still leaked, even in encrypted lists. I am not familiar with that means.
With the Last Seen I mean this:
When you update something that you expect to be private, it will still reveal in the metadata that you did something and when using relays as storage it happens all the time, this is what updates the "Last Seen".
> We're talking about storing a long-standing standard event kind
Compared to the mute list the follow list is even more long-standing/defined but last week I saw 2 more people get their list nuked, its just not solved (only in theory but not in practice). Nostur is used a lot to recover follow lists, I would probably have to implement similar mechanisms for mute lists.
> How do you plan to handle the encrypted data in the kind 10000 at the time of import, if there is any? Decrypt it and store it locally and on iCloud unencrypted?
Yes decrypt and store, and on iCloud can also be encrypted.
> is there a way to make sure that Nostur only adds the local mutes to the new list, without removing entries
Yes but this is basically the same problem as with the follow lists, maybe even harder because there are some tricks that can be applied to prevent follow list nuking that probably won't work for mute lists.
Published at
2025-06-09 21:48:20Event JSON
{
"id": "fc22fda200a676bcfca8c3d6931077c7dab0cf3cf37d3e1d84684dea9f85a477",
"pubkey": "9be0be0e64d38a29a9cec9a5c8ef5d873c2bfa5362a4b558da5ff69bc3cbb81e",
"created_at": 1749505700,
"kind": 1,
"tags": [
[
"e",
"db966a63e465c506117db7521626d65cab808a1e6beec0d3d11c597c01fd7413",
"",
"root"
],
[
"e",
"82386d2965f7c15482a418a102485f18cfc301526f299d3e0c2cb4e95663cb3b",
"",
"reply"
],
[
"imeta",
"url https://media.utxo.nl/wp-content/uploads/2025/06/last-seen_.webp",
"dim 1284x1721",
"blurhash LCAJi?%gS~X9~ANabvX8~AR*X8bH"
],
[
"p",
"06b7819d7f1c7f5472118266ed7bca8785dceae09e36ea3a4af665c6d1d8327c"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb"
],
[
"p",
"9be0be0e64d38a29a9cec9a5c8ef5d873c2bfa5362a4b558da5ff69bc3cbb81e"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"645681b9d067b1a362c4bee8ddff987d2466d49905c26cb8fec5e6fb73af5c84"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "\u003e I also see the value of having certain types of mutes public\n\u2028Yes public mute is useful, especially to remove some possible taint from one's WoT, but maybe it's better to use public reports for that so the mutes can stay private. At the moment Nostur doesn't do anything with reports yet, aside from being able publish them.\n\n\u003e You mentioned that \"last seen\" metadata is still leaked, even in encrypted lists. I am not familiar with that means. \n\nWith the Last Seen I mean this:\n\nhttps://media.utxo.nl/wp-content/uploads/2025/06/last-seen_.webp\n\nWhen you update something that you expect to be private, it will still reveal in the metadata that you did something and when using relays as storage it happens all the time, this is what updates the \"Last Seen\". \n\n\n\u003e We're talking about storing a long-standing standard event kind\n\nCompared to the mute list the follow list is even more long-standing/defined but last week I saw 2 more people get their list nuked, its just not solved (only in theory but not in practice). Nostur is used a lot to recover follow lists, I would probably have to implement similar mechanisms for mute lists.\n\n\u003e How do you plan to handle the encrypted data in the kind 10000 at the time of import, if there is any? Decrypt it and store it locally and on iCloud unencrypted? \n\nYes decrypt and store, and on iCloud can also be encrypted. \u2028\n\u003e is there a way to make sure that Nostur only adds the local mutes to the new list, without removing entries\n\nYes but this is basically the same problem as with the follow lists, maybe even harder because there are some tricks that can be applied to prevent follow list nuking that probably won't work for mute lists.\u2028\u2028",
"sig": "e540c339639782174dcdaf1da289160f957ff6b851560e42badfdb19345feb07a2bded527dcf2d030595e426e29b996b1a0a37a843f4346db6aad692723a0c16"
}
