Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
We're being trolled.
Someone already asked Notch and he said it was just the Minecraft 1.0 files. But the .7z file is about 70mb in size while the minecraft.jar is only a few megabytes in size, so it can't just be the minecraft.jar files. If the secret file really is the minecraft code then it's most likely that Notch just included the resources folder which is about 90mb. The best way to find out would be to do a 7z of the current .minecraft and see if the size of the archive is the same.
Only quad core? I think cloud computing is the way to go for a server.
Hallo, I asked him and got that reply
I have been trying to battle this for a while, at the moment I am going on the basis of:
The average secure password is 14 chars long.
The password is typed using chars between the ASCII Chars of 32 to 126.
Currently my computer (6 Cores) is generating 14^94 possible combinations if the script don't crash out (Virtual boxing so can pause whenever needed).
After the database is generated I plan to make it use a distributed computing method where somehow people can run a program to test it, more = quicker, plan is that it will work on Linux, Windows & (I can't test) Mac OSx to allow pretty much anyone run the program.
Or I may look at using the GPU TO process data, this is seen a lot in bitcoin mining as a GPU is LOTS Quicker compared to a CPU now.
Or, it could be just the minecraft.jars, since when an archive program compresses a file, it "deflates" the file of about 20-60% in size. If the file is 70 MB, and the minecraft code is 90 MB, then the compression took about 22% out of the file. That is a reasonable number, so it could be.
The only problem is that the jar which contains the code is about 2.5mb. Which leaves us with the same problem as before of a large archive with a small code.
Ohman95 may be correct about the idea of multiple versions. Since most code is updated with many small changes such as bukkit updates with many developpement versions, it may be possible. If the code is not a jar file and decompiled, they probably made differential backups. It may help if someone able to download MCP for Minecraft 1.0 and MC Nostalgia to find the exact size of the source.
Honestly, I think the password consists of random letters and numbers.Never mind, didn't know how old this thread was.
"Just remember that when you are falling, turn it into a dive." ~Wookiefoot
"Why isn’t my life like a situation comedy? Why don’t I have a bunch of friends with nothing better to do but drop by and instigate wacky adventures? Why aren’t my conversations peppered with spontaneous witticisms? Why don’t my friends demonstrate heartfelt concern for my well-being when I have problems?… I gotta get my life some writers." ~Calvin, Calvin and Hobbes
Look up Minecraft 8 million Notch secret Message
I don't think so, the code was already solved... mostly.
I'm going to convert the .7z file to a .rar file just to see what happens.
My Github ด้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้дด็็็็็้้้้้็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้
I just tried all of those, It did not work.
My Github ด้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้дด็็็็็้้้้้็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้
http://boinc.berkeley.edu/
We could start a project there running through passwords.
(I'd like to confirm this is supposed to be cracked)
- Steve Martin
I have been trying some Swedish passwords. I'm sure Smiba Will crack the password before I ever will.
And I had a HUGE derp moment... You can't convert a password protected file... I feel so stupid right now
I just had an Idea, If it could take 1 computer approx. 70 years to crack the password... What if we got multiple computer Working together trying to crack the password? With the combined computing power, wouldn't it be possible to crack it alot faster?
My Github ด้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้дด็็็็็้้้้้็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้
Objection!
https://twitter.com/smiba1
My Github ด้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้дด็็็็็้้้้้็็็็้้้้้็็็็็้้้้้็็็็็้้้้้็็็็็้้้้้