Cheat Engine

[Jorg hi]

I thought of a very smart way to send p2p files! My idea would be to convert it into my new format INET. It would just scan each byte of the file, and see if it can find it on the internet using a search engine. For example if you were to send this text file

"I like PI3298748923"

It would search for "I like PI3298748923", and see if its on google. If it gets no searches it will keep dropping the length of the string until it finds an exact search. Then it will reference the HTML URL, and the char position and length.

Then it will rename the file as .INET, in this format
"www.website1.com/file.html [0,10]
www.website2.com/file.html [734,17]
www.website3.com/file.html [91,56]
<??Time Stamp??>
"

And the person would just convert that back into a file using the INET tool.
My idea, is that because it uses online websites to create the file, that if EVEN 1 piece of website data changes, the entire file would be corrupt. This would stop many simple programmers/hackers. But someone with more skill would just try to find a Cache of the webpage or authorize one by legal law(some how...) and then fix the missing ByteCodes inside the exebutal/(Guess whats missing, it would be harder for a pure text one though)...

Does anyone have a much greater imaginative idea?
WAIT... maybe I could make the program find file name similarities of each computer to use as a data/char table??(Of course there would be a hook disabling file deletion/modifications)...

I'm just trying to find a new way to send files, without actually sending the file. I would use a method similar to a torrent... but that is easily tracked now, and you can get in big trouble for having the torrent's data on your server.

[atom0s]

Some problems:

1. INET is an already used name/acronym for a lot of things.

2. Your generated file will be huge, way bigger then the original file due to 1 byte turning into a full sentence for reference. Kind of defeating the purpose of p2p all together when you are downloading gigs of reference data to even get the main download.

3. As you said 1 byte change on a page kills the entire file / misaligned it, corrupts it etc. Kind of also defeating the purpose if someone is using your tool for themselves and their data just corrupts if it is needed later on.


Overall your idea is fairly flawed, not bashing you but the idea isn't something I'd use or even think of using after knowing how it works. Reconstruction of the file would take days depending on the speed of someones internet as well as the website (if its even up). You are going to have to find something better. What is the point of creating a new p2p method if the current ones work fine as is anyway?

[Slugsnack]

If you want to develop your own P2P system, it's definitely worth it to look into existing systems. Worthy examples of note are:
- Napster
- Gnutella
- Pastry
- Freenet
- BitTorrent
- JXTA