And the solution to that is to scrub the metadata and introduce some light content fuzzing (to avoid variable keyword/phrasing inclusion traps that can be used for narrowing down leak investigations).

Like, yeah, there are hazards to doing an exfil dump like that, but if you know what you’re doing and understand the threat vectors that are likely going to be employed against you, you can cover your bases reasonably thoroughly - especially if you have a homelab with local ML/LLM capabilities that you can use (and, well, know how to use) to obscure/modify the precise phrasing of things such that it becomes way harder to attribute the leak source.

And, I’m not saying “chuck it into your local model and cross your fingers” - it would be an element of the sanitization pipeline. If you are so inclined to do this sort of thing, you should absolutely do as much manual and deterministic verification and sanitizing that you can.

It goes without saying that this is all at your own risk. But if you think it’s worth it, there are ways it can be done.

Install local ai on your hardware. Feed your data to it. Ask it what metadata can be extracted to identify chain of custody. Strip it off, ask it the same. Keep iterating until it cannot pull any useful meta.

Then leak it from a fresh system using a connection that is not directly connected to you.

Easier said than done, but still possible. There are actual crimes committed that people get away with all the time, they just never end up in the news. Unsolvable crime is still a thing, so untraceable leaks can be too.