(no title)
boredpudding | 6 months ago
Tl:dr; It was a release file for their Minecon event. It was never meant to be public. Obsessing over a password protected in a company's S3 bucket is weird and crosses many limits.
boredpudding | 6 months ago
Tl:dr; It was a release file for their Minecon event. It was never meant to be public. Obsessing over a password protected in a company's S3 bucket is weird and crosses many limits.
djmips|6 months ago
teruakohatu|6 months ago
More like a reverse-streisand effect. They were honest about the contents of the file, it was Minecraft 1.0 and not interesting, but the community didn't accept the explanation.
cedws|6 months ago
boredpudding|6 months ago
Matthyze|6 months ago
I think the house analogy fails because you cannot duplicate a house, take it somewhere else, and attempt to break into it there. If you could, that would undoubtedly be seen as a violation.
throwzasdf|6 months ago
[deleted]
snowram|6 months ago
esnard|6 months ago
Unsure why it took the community so long to crack the file.
catsma21|6 months ago
boredpudding|6 months ago
de6u99er|6 months ago
Ouch
MortyWaves|6 months ago
Take for example, the infamous 2B2T Minecraft server.
Exploits and game breaking mechanics by virtually impossible to discover bugs, and the no rule against hacking and cheating, have led to things people didn’t think were even possible in Minecraft over the servers ~15 year history.
charcircuit|6 months ago
It's similar in format to communities that obssess over "lost media." The inability to pirate or get access to something becomes an obsession. Even if the piece of media exists in an archive somewhere, that doesn't matter to them because it's about the fact that they themselves don't have access to it that has become the obsession.
LiamPowell|6 months ago
lupusreal|6 months ago
neuroelectron|6 months ago
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
IT4MD|6 months ago
aswip|6 months ago
boxpig41|6 months ago