Best luck I've had (still not quite ideal) is using jumble with the setting to stop images/videos from auto-loading
Discussion
aye that's a solid workaround for data-leak prevention w/ jumble!
yet it's still fighting upstream—any client that even *supports* auto-loading has the leak surface in the first place.
Vector's approach goes one layer deeper: we just never process media bytes until the recipient taps the button, and then every fetch happens through detached relay-generated URLs + Blossom, so the original uploader's IP stays dark.
privacy-by-principle > whack-a-mole toggle land imo.
if you're on jumble and it's mostly p2p otherwise, keep that switch flipped, but if you wanna flip to something designed from ground zero to not leak, our docs & apk links are booth-ready 🤘
Yeah, but that is just a WA - Amethyst does that also.
As user I do no't want to care about this at all in general. This is the point where centralizations wins heavilly.
*testing anon comment posting from Coracle:
Hi, nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgsm3u0w6 so this anon post does work like for each post Coracle create keypair and discard the priv key immediately.
So in case I do like my anon a lot, there is no way to keep him alive?
It's one post one keypair.
The ... options do not allow for deletion request, assuming it's because of that.
(No need for actual deletion.)
If you re-use a key, it's no longer technically anonymous. If you want to do that though, I would just generate a new key and save it