Friday, February 23, 2007

Web 3.0 Concept: Software Anti-Piracy

Though I'm not a anti-piracy fan-boy, this idea came to me recently. This might sound extremely meaningless, but it has much insight in our piracy battles and state of software: "It is difficult to steal something that is no there." Everything boils down to the physical. In fact, digital is not only an analogy to physical, but also uses it as a backbone (current/voltage represent 0's and 1's) and therefore, digital interaction requires physical presence and connection. In traditional program-cracking and media-pirating, a physical medium is required, replicated usually in a static/semi-static form.

The phenomenon of the internet is that the physical is displaced to that of the servers.
Obviously, the software mantra, "nothing cannot be broken," applies as seen in the full scale server pirating of the online computer game Lineage; however, paired with anti-piracy techniques, it may prove impracticable to pirate. The solution:
- Stream in chunks, given arbitrarily (have multiple versions of each data section which cannot be paired together)
- Make the program so big that it is near impossible to obtain all the data sections and ridiculously impractical to download.
- Make physical form impossible. (create sections larger than common media)
- Decentralize products. Instead of one big product for a large amount of money, create smaller products with proportionate price. Keep product streams separate, have incompatible data chunks in saved form (data chunks from two products deliberately take same virtual memory locations causing data to be overwritten upon running other product).

This probably sounds counter-intuitive, but implemented correctly this is the golden ticket for software applications (which may realistically become Web 3.0 Applications). Seeing traditional desktop products going online [Image Editing, Office Suites, Word Processing] and online products go desktop [Adobe Apollo], this technique could be leveraged to decrease software piracy.

No comments: