Replies (45)

bc21's avatar
bc21 7 months ago
We can. Stay humble and stack zaps ⚡️
What about this note would keep it private? { "sig" : "9b677cbe21cadd93a091bdfd40003b0ab9152891d69e1213c2204f7d1594af1c58623487d516f81688d4deda517e1ec24b96f1deca0e40b2b166152b376d6f83", "id" : "08a0568d69f0d4e6dacfc694c164181cf757b96b5a630728e09a061272100566", "tags" : [ ], "content" : "Hopefully no one can read this note.", "kind" : 1, "pubkey" : "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d", "created_at" : 1746239889 }
If anyone reposts it (not quote posts it, but actually reposts it), then it is sent in the "content" fields to other relays.
Presumably fiatjaf tried to delete the note. Obviously, if anyone has reposted it in the meanwhile it has been sent to other relays. Clients that see reposts won't even have to fetch the original note at all, since it's already included in the "content" field of the repost event.
It was supposed to be kept private by the relay, but Jumble was refusing to AUTH (@Cody I don't know why this happened but it did, it generally works but sometimes Jumble just decides to not perform AUTH after getting an `auth-required:` error?) so I kept retrying and eventually I must have forgotten to click on the "send only to this relay" checkbox (@Cody maybe the checkbox state should be persistent?).