>fix your stupid 1337 h4x0r file extension by renaming it to txt Posted on May 23, 2023 by Anonymous >fix your stupid 1337 h4x0r file extension by renaming it to txt
congratulations on discovering the magic of plaintext, fucktard
This! OP is a homosexual as always.
Look how knowledgeable you are... Go fuck yourself you little bitch.
Guys don't fight, we're all friends here!
No. We are frens. That's different.
Fuck you. I hate this freetard zoo and I only come here to spread misery and anger. Shitting on neets in their manchild desktop threads distro wars is my favourite pass time.
That's just sad, man
Ikr? How can anyone argue for literal years about their electronic funko pops, or distros as they call it?
I'm going to put a single 0x0 at the end of the file so you can't open it up in a text editor.
kek, does this really work?
nope, the 0x0 is just displayed as mojibake
Why are you opening ascii files as utf16.
I've never understood why they do this shit
From the days of .info files, but with 8.3 file names the "i" just got removed.
This goes back to the era of the 80s and BBS
Why is .info file a thing? It's literally just a txt file. I don't get it.
Because its a txt file with the info about the stuff, whatever it may be.
Anon, quit getting so hung up about file extensions. It was not uncommon back in the day to do the Unix way of thing. No file extensions and treat everything as a text file unless it's MIME type was detected otherwise.
>But then why .info to begin with?
Reasonable question. A big problem with doing everything with MIME types is that the user does not have the ability to tell what type of a file something is at a glance, so people started to append things like .info to make it more visable.
This is all legacy shit going back like 60 years. Is it dumb? Yeah, kind of. But there is a reason why these things all ended up that way. Its not a straight line.
So file extensions weren't common back then? I think the file's type is determined by the magic byte? Like CAFEBABE for Java or something.
>So file extensions weren't common back then?
Depends on the OS. For UNIX, file extensions were not used implicitly, but many people would just add them to some file names for the sake of readability when looking though your stuff, but the OS it self just ignored them.
Strictly speaking, its how it works to this day with Linux.
Then there are some hardware sets like the PDP series of computers where some of the OSs used them, and some didn't.
None of this shit was standardized between computers and OSs till CP/M, which was the first (popular) OS that was on multiple hardware sets that recognized and enforced extensions on file names.
MS-DOS in many ways is just a CP/M clone (even drive names like A: C:, etc is from CP/M)
And then Windows just adopted for compatibility what DOS was doing.
Happy to give some insight.
If you want a weird read, look up the classic Macintosh OSs.
System OS 1 though 9
They didn't use file extentions, but they also didn't use magic byte at the begining of the file either.
Those OSs used a god awful series of file system that actually had two byte steams for every file, a byte steam for most of the bulk of the actual file it self and a second one with the file's binary and a bunch of meta data regarding the file including something to identify what type of file it was. Hence why you needed special software back in the day to copy a file from Mac<->DOS/Win, since you had to sew the two data streams back together to get the full file when attempting to write to a FAT filesystem, and then split them apart when writing to a Mac.
Apple had a lot of insane ill-conceived ideas in motion during that era that just made things harder for their own engineers.
Depending on the extension is a Windows thing. For everyone else, it's just metadata. Basically, a
poor-man's tagging system.
>extension explains the file type
Doesn't seem stupid to me anon
Reverse Hungarian notation? Cool.
it's deadly accurate. apple's operating systems back then were a comical farce and i hated working on these systems.
>Apple had a lot of insane ill-conceived ideas in motion during that era that just made things harder for their own engineers.
corporation has always been run by morons that barely understand the technology they're trying to sell. this is why they're now at 7% market share.
nobody cares about what they feel or want, never will. they are quite happy to suck on the mutilated israeli cocks of corporations.
kill yourself, thanks. men are speaking.
>men are speaking
Your cue to remain silent, kiddo
kill yourself, thanks. white men are speaking.
finally admitting that YWNBAW, eh?
what did the child molesting communist mean by this? stick to what you're best at: raping minors.
Projecting hard, I see. Come on do the 42% already.
You're a .nagger
>It's literally just a txt file
So are .f, .c, .cpp, .yaml, .json, .html, .xml, .js, etc. The changed extension clearly shows the purpose of the text file.
But all these get interpretedcompiled. What happens to .nfo file? You read it just like a .txt? Cool, I guess
>astronaut shooting astronaut looking at earth
its all text files, always has been
Thank God I've never seen a .todo file.
>he doesn't .plan
winbabby fucktard detected
I don't plan, I just do.
>not using msinfo32 to read warez info files
Back in the DOS days, extension was just a hint. There were no file associations.
For instance, README files were often called "README.1ST" or "README.DOC" (nothing to do with word tho).
Zoomies can't into ANSI art
I don't want to scroll through a page of trash letter art to look at the instructions, I literally delete everything irrelevant from every readme I open.
You’re so fucking cool. I want to be like you when I grow up
>fix your stupid file explorer by configuring it to open nfo files with your text editor
They aren’t “just” text files you absolute philistines
There. That’s probably one of the most feature full nfo viewers. Now you too can have a proper viewer to enjoy cool ascii art
found the amiga user