this post was submitted on 06 Jan 2025
372 points (92.7% liked)

Greentext

4770 readers
1164 users here now

This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.

Be warned:

If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.

founded 1 year ago
MODERATORS
 
all 32 comments
sorted by: hot top controversial new old
[–] [email protected] 178 points 1 week ago (4 children)

Actually pretty common as most people would subconsciously hit the same areas each time.

[–] [email protected] 32 points 1 week ago

Yeah I was gonna say I'll do the same thing and I usually just end up hitting only hte home row keys, and usually my left hand hits keys before the right hand.

[–] [email protected] 24 points 1 week ago* (last edited 1 week ago) (1 children)

This is similar to why "random" numbers or passwords you come up with yourself aren't really that random

[–] [email protected] 13 points 1 week ago (1 children)

1234 is as random as 1111 🧐

[–] [email protected] 6 points 1 week ago

And as random as 3282, assuming you're using a random number generator.

[–] [email protected] 15 points 1 week ago

Yeah the filename is fsdfsdf like always

[–] [email protected] 3 points 1 week ago
[–] davidgro 43 points 1 week ago (1 children)

There's also the birthday paradox to consider - each new file increases the number of potential matches for all files that follow, and also is a potential match for all files that precede it. The total number of ways to match is something close to the square of the number of files.

[–] [email protected] 58 points 1 week ago (1 children)

Also smashing the keyboard is very poor randomisation, you naturally place your hands the same and probably even start hitting the keys the same way.

[–] davidgro 6 points 1 week ago

Yup, very much so.

[–] someguy3 30 points 1 week ago

You're probably hitting the same area of your keyboard and roughly the same number (length).

[–] Tarquinn2049 26 points 1 week ago (4 children)

So, I have seen people do this, and I gotta ask... what is the plan?

Like you are saving the file, implying that you plan on using it again... why make it so hard to figure out which one it was? Especially in this case, where he has done it to enough files all in the same place that he eventually hit the same combo again.... like, are there hundreds or thousands of randomly named files in that same folder? Why save them if they will be impossible to find again anyway?

[–] davidgro 16 points 1 week ago* (last edited 1 week ago) (1 children)

My guess is since they are images the thumbnail is more important as an identifier than the name would be.

[–] [email protected] 5 points 1 week ago (2 children)

Then why change it? Most apps give a default name, so you literally just need to click "save" or press "Enter."

[–] davidgro 4 points 1 week ago* (last edited 1 week ago) (1 children)

No idea, best I got is that maybe the default name is always the same from whatever source they are using, so they would get 'replace it?' dialog anyway.

[–] [email protected] 3 points 1 week ago (1 children)

Really? Pretty much everything I've used adds a (1) or something to always give a unique name.

[–] davidgro 3 points 1 week ago

Yeah, I agree, usually it does

[–] 9point6 8 points 1 week ago (1 children)

I don't do specifically what OP did, but often I remember things by when better than by name.

Sorting a folder by last modified/created in descending order generally gets me what I'm looking for pretty quickly

[–] [email protected] 2 points 1 week ago

I tend to save things with the name embedded, so "--_" and use the date that's relevant for the file, not necessarily when it was created (e.g. due date for homework, tax return due date, etc). If I don't care (e.g. a downloaded image), I just accept whatever the default is.

[–] [email protected] 4 points 1 week ago (2 children)
[–] [email protected] 6 points 1 week ago (1 children)

"doc1", "doc2", "doc3frogstudy", "doc4"

hmm, the doc is redundant. the number is also redundant, it has date to sort by. 1, 2, and 4 can be whatever.

[–] Tarquinn2049 2 points 1 week ago (1 children)

I can see an argument for how it can still be possible to work with that... filing system, but I still don't get what the upside is, just that it doesn't have as many downsides as it seems like it should.

[–] [email protected] 2 points 1 week ago

I personally have too many random trash notes and files to name them. Maybe it takes 30 seconds, whatever, I'm closing the thing right now. It's not important anyways, but I'm not gonna purge it all to make anyone else happy with how clean and dead my harddrive is.

[–] [email protected] 2 points 1 week ago (1 children)

Isn't it more lazy to just accept whatever the default is?

[–] [email protected] 2 points 1 week ago

I guess so, I used to type gibberish because I wasn't sure what to name it, but didn't like it saying "untitled" or "image3.jpg". "ehixvakg.jpg" has more personality.

[–] affiliate 1 points 1 week ago

some websites will save the file name when you upload a file. it could be done for privacy reasons if you don’t want a website to know how you got a file. this is the best reason i can think of for randomizing file names, but i don’t actually do this in practice. sometimes i’ll just rename the file before uploading if im worried about it. file names are just too useful.

[–] [email protected] 21 points 1 week ago

Muscle memory

[–] [email protected] 17 points 1 week ago (1 children)

Pretty common actuality. Across all people hence smashing a keyboard for a random password is a bad idea

[–] [email protected] 2 points 1 week ago (1 children)

Iirc there was a dictionary for randomly smashed keys, I've seen it but now I can't find it.

[–] [email protected] 2 points 1 week ago

Most of em are in the 10mil most common password list

[–] [email protected] 6 points 1 week ago

This is why you have:

ieudjsjau.jpeg
ieudjsjau2.jpeg
ieudjsjau22.jpeg
ieudjsjau222.jpeg
ieudjsjau222b.jpeg
ieudjsjau222d.jpeg
ieudjsjau3.jpeg