Modifying a piece of data stored locally on your server will be a very limited way to annoy Freenet. Firstly, it won't be up to you what data
is stored on your server, so if you have a specific agenda it will only be through extreme luck that you can progress it through modifying
data on Freenet.
Couldn't I just request the data a whole lot from a server located on a machine under my control? As I understand it the data will migrate towards the greatest desire for it, would this eventually cause it to show up on the machine I'm targetting?
Further, unless the data is really unpopular (and therefore really rare) any modifications you do make to a local copy will
be a drop in the ocean.
How much redundancy are you planning on building in? Too much and nobody will have enough storage space. Also, it seems to me that although the initial modification would, as you say, be a "drop in the ocean", it has the potential to grow exponentially as each retrieval of the flawed copy will result in another request for the same key in the hopes of getting a good copy. This demand would cause the spread of data associated with that key, be it the original or modified copy. Voila, you decrease people's ability to get the original data by:
- obscuring the actual data
- creating a large load on the freenet system.
Encryption sounds like the way to do things (digitally sign each copy), but good crypto is always trickier to implement than it appears, and it would probably sacrifice some of the anonymity.
Not trying to be a downer, I sure hope this succeeds, but this is something one would probably want to get this right on the first try.
[ Parent ]