Those sealed censored deleted Documents on Epstein and Maxwell? ... they are not really deleted...Can be Un-Redacted when Copying to Txt Notepad??

POSTED BY: JAYNEZTOWN
UPDATED: Wednesday, December 24, 2025 23:54
VIEWED: 3097
PAGE 2 of 2

PREV PAGE 1 2

SIGNYM

Tuesday, August 4, 2020 3:00 AM

Quote:
Originally posted by JEWELSTAITEFAN:
Seeing this headline brought beck memories.

I used to use Notepad or Wordpad all the time to de-clutter M$ crap all the time. My boss at the time would spend hours trying to decode and reformat some M$ garbage to get the text out of it and transcribe to our documents. I would just change to Notepad to get rid of the useless M$ formatting, and then put in the simple formatting we needed - took a few minutes. I even showed him how easy it was, but it took him a while before he became frustrated enough to do it this easy way.

M$ still has a habit of making their software retain a copy of the original version of the document (file) within the saved file. This used to be handy with photos, when somebody posted some edited or cropped photo, you could unformat it and find the original, where they were nekkid or flashing boobage.

I recall that whenever I am required to mess with useless M$ crap, there are hoops you need to go through to get rid of that original version. Like I had to convert to Notepad, then save as Notepad text, then delete the file from active display, then shut down the Word app, then change the name of the file (like by one character), then open it fresh in Word. Miss a step and the little pecker would retain the original version.

I have no doubt that some Libtard who doesn't know how to use a computer (like Apple users) posted this in a form that can be decoded as described.

True, that. You can even get M$ to show all of the previous edits and comments. I can imagine that M$ "redaction" applies a formatting-type action before and after the redacted portion instead of replacing the actual text with black block, so - again- I can imagine that all you need to do is xfer the file to some app that doesn't support the "redact" function to recover the original.

Still, while it's reasonable to claim that Notepad unredacts the document (if it was released in .doc format and not .pdf) it may not be true.

-----------
Pity would be no more,
If we did not MAKE men poor - William Blake

#WEARAMASK

JAYNEZTOWN

Monday, July 21, 2025 5:13 AM

and now Pelsoi is defending Trump

Epstein Filthy Rich 2020 doc

6IXSTRINGJACK

Monday, July 21, 2025 6:41 AM

Quote:
Originally posted by SIGNYM:
Quote:
Originally posted by JEWELSTAITEFAN:
Seeing this headline brought beck memories.

I used to use Notepad or Wordpad all the time to de-clutter M$ crap all the time. My boss at the time would spend hours trying to decode and reformat some M$ garbage to get the text out of it and transcribe to our documents. I would just change to Notepad to get rid of the useless M$ formatting, and then put in the simple formatting we needed - took a few minutes. I even showed him how easy it was, but it took him a while before he became frustrated enough to do it this easy way.

M$ still has a habit of making their software retain a copy of the original version of the document (file) within the saved file. This used to be handy with photos, when somebody posted some edited or cropped photo, you could unformat it and find the original, where they were nekkid or flashing boobage.

I recall that whenever I am required to mess with useless M$ crap, there are hoops you need to go through to get rid of that original version. Like I had to convert to Notepad, then save as Notepad text, then delete the file from active display, then shut down the Word app, then change the name of the file (like by one character), then open it fresh in Word. Miss a step and the little pecker would retain the original version.

I have no doubt that some Libtard who doesn't know how to use a computer (like Apple users) posted this in a form that can be decoded as described.

True, that. You can even get M$ to show all of the previous edits and comments. I can imagine that M$ "redaction" applies a formatting-type action before and after the redacted portion instead of replacing the actual text with black block, so - again- I can imagine that all you need to do is xfer the file to some app that doesn't support the "redact" function to recover the original.

Still, while it's reasonable to claim that Notepad unredacts the document (if it was released in .doc format and not .pdf) it may not be true.

-----------
Pity would be no more,
If we did not MAKE men poor - William Blake

#WEARAMASK

Even saving things in Notepad isn't good enough, depending on what it is you're looking to do.

Now that I'm doing cross-platform work, I've discovered that there are quite a few annoyances with M$ formatting (at least when looking through a lens of trying to get away from M$ and move over to Linux... I would have argued the other way a few years ago).

The first off is, M$ and command prompt hate, hate, HATE any characters that you don't see on your keyboard. Since I'm still primarily writing my scripts in M$, I'm constantly having to go back and fix things manually that shouldn't need fixing because the file names or text inside a file has a little line over an "o".

Worse yet are the invisible characters. Hard returns in M$ Notepad are different than hard returns that Linux uses and recognizes. One day I was banging my head up against a wall trying to figure out why somewhere in the area of 90 data arrays that I was working with just fine in M$ simply did not work when they were ported over to Linux.

It turns out that in this one particular instance, for that one particular use, Linux did not want to recognize those hard returns from M$ Notepad, even though it's been fine with them anywhere else that I had them so far.

I was able to fix this in a program called Notepad++, but not before finding out how to manipulate that program to replace my M$ hard returns with Linux friendly hard returns.

And by that point, it was simply easier to just walk over to the other computer and bulk edit them directly in Linux rather than work on them remotely.

Honestly, I think at some point this is just the programmers being contrarian dicks. There's no reason why a hard return can't be a hard return can't be a hard return no matter where you're using them, unless somebody is b

SIGNYM

Monday, July 21, 2025 8:00 AM

A hard return should be "carriage return" "line feed", both of which are absolutely in original ASCII.

I can't imagine why anyone would change that, except to be dicks.

-----------
"It may be dangerous to be America's enemy, but to be America's friend is fatal."- Henry Kissinger

"Constant monitoring of behavior, emotion, and identity breeds conformity, judgment, and fear."

6IXSTRINGJACK

Monday, July 21, 2025 10:02 AM

Quote:
Originally posted by SIGNYM:
A hard return should be "carriage return" "line feed", both of which are absolutely in original ASCII.

I can't imagine why anyone would change that, except to be dicks.

Outside of just being a dick to be a dick, I have only one idea...

Somebody painted themselves into a corner when putting together the original code and decided it wasn't worth trying to fix because of all the other changes they'd have to make to fix it. At that point, I could see a little "dickish" behavior come into play where the person writing the code they were going give away as a free alternative to M$ might say "screw it. They shouldn't have been using M$ in the first place.".

I've had to do a few strange things to manipulate data for the end user here or there because of the constraints of the program(s) and metadata and the limitations of some programs with this data already. A ton of forethought and planning and changing while working on and abusing it all and I thought I'd had it all ironed out and future-proofed. Turned out, there was something I hadn't thought about and I ended up having to make a pretty huge change one night that backed out a few of those decisions, changed them to make room for the necessary change I originally overlooked, added that in as well, the then dealt with the ripple effect that created... which lead to more wasted time doing a good deal of testing to make sure nothing else broke in the process.

There were "Shortcuts" I could have taken and just gotten it all done right away without worrying about things breaking or needing to test anything, but every one of them other than rebuilding part of this from scratch and dealing with the consequences now would have ultimately become somebody else's problem one day. Most likely, a problem that they aren't capable of fixing and/or would never put the time or effort into learning/fixing it themselves. It would end up being a small annoyance to a small group of people who noticed it. The type which I find that others have left for me to clean up when possible and annoy me to no end when I find them. Hell... The only reason I had to do everything I'm mentioning in the last 2 paragraphs in the first place is exactly because somebody did something stupid and/or lazy deeper into the code than I'm willing to travel and I've got to do workarounds that make sense for the end user while still working as intended too.

I could see "thinking about current M$ users" as a low-level priority, and then a reluctant coder not caring about M$ users having to suffer rather than undoing and redoing a ton of work being the culprit here. Still dickish, but a little more understandable than straight up defiance to the previously set standard.

Then again, who knows? Maybe that was all part of what they had to do to avoid being copyright claimed and ruined by the Evil Thief Bill Gates.

--------------------------------------------------

"I don't find this stuff amusing anymore." ~Paul Simon

JAYNEZTOWN

Wednesday, December 24, 2025 11:54 PM

hacker Anons got the names again!

the list is full of pedophiles from both parties

PREV PAGE 1 2