[flagged]
Recreating Epstein PDFs from raw encoded attachments
111–120 of 224 posts
Re: Recreating Epstein PDFs from raw encoded attachments
#112Earlier quoted context omitted.
So it was a public event attended by 450 people: https://www.mountsinai.org/about/newsroom/2012/dubin-breast-... https://www.businessinsider.com/dubin-breast-center-benefit-... Even names match up, but oddly the date is different.
looks like we have it. in the end it's pretty mundane...
Which begs the question why was it censored?
Re: Recreating Epstein PDFs from raw encoded attachments
#113Earlier quoted context omitted.
I mean, the internet is finding all her mistakes for her. She is actually doing alright with this. Crowdsource everything, fix the mistakes. lol.
I wonder if this could be intentional. If the datasets are contaminated with CSAM, anybody with a copy is liable to be arrested for possession. More likely it's just an oversight, but it could also be CYA for dragging their feet, like "you rushed us, and look at these victims you've retraumatized". There are software solutions to find nudity and they're quite effective.
Or it's distraction. Leave nudity in to use up attention that should be turning to analysis of what's been redacted.
There's redaction to protect victims and there's redaction to protect specific co-conspirators in Epstein's spy ring
Re: Recreating Epstein PDFs from raw encoded attachments
#114My non political take about this gift that keeps on giving is that: PDF might seem great for the end user that is just expected to read or print the file they are given, but the technology actually sucks.
PDF is basically a prettify layer on top of the older PS that brings an all lot of baggage. The moment you start trying to do what should be simple stuff like editing lines, merging pages, change resolution of the images, it starts giving you a lot of headaches.
I used to have a few scripts around to fight some of its quirks from when I was writing my thesis and had to work daily with it. But well, it was still an improvement over Word.
Re: Recreating Epstein PDFs from raw encoded attachments
#115Re: Recreating Epstein PDFs from raw encoded attachments
#116Re: Recreating Epstein PDFs from raw encoded attachments
#117[flagged]
it's really all about the blackmail
Re: Recreating Epstein PDFs from raw encoded attachments
#118Earlier quoted context omitted.
I mean, the internet is finding all her mistakes for her. She is actually doing alright with this. Crowdsource everything, fix the mistakes. lol.
This would be funnier if it wasn’t child porn being unredacted by our government
Weren’t. Subjunctive mood.
Re: Recreating Epstein PDFs from raw encoded attachments
#119Earlier quoted context omitted.
I doubt the PDF would be very interesting. There are enough clues in the human-readable parts: it's an invite to a benefit event in New York (filename calls it DBC12) that's scheduled on December 10, 2012, 8pm... Good old-fashioned searching could probably uncover what DBC12 was, although maybe not, it probably wasn't a public event. The recipient is also named in there...
There's 70 results that come out when searching for "application/pdf" on the doj website
OK, but if the solution is to brute-force them, there's probably a need to choose which files to focus on.
Of course there are other content-types, e.g. searching for "Content-Type: image/jpeg" gets hits as well. But only a few of them actually have the base64 data, mostly there are just the MIME headers.. Looking for "/9j/" (which is Base64 for FF D8 FF, which is the header for JPEG files), the Trumpian justice.gov website ignores "/" and shows results case-insensitively, but there are 4 or 5 base64'ed JPEG images in there.
I also saw that the page is vulnerable to code injection, somehow garbage in one search result preview was OCREd as "", and the rest of the search results were striken-through because "" is the HTML to do that.
Re: Recreating Epstein PDFs from raw encoded attachments
#120Given how much of a hot mess PDFs are in general, it seems like it would behoove the government to just develop a new, actually safe format to standardize around for government releases and make it open source. Unlike every other PDF format that has been attempted, the federal government doesn't have to worry about adoption.
I give any new document format 3 to 5 years until it ends up with similar mess. And that is if it starts well designed and limited.