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: