Slashdot Mirror
Ian Clarke on Peer-to-Peer
Simone of O'Reilly writes "On Freenet, the more popular information gets, the more copies it
generates--and the easier it is to find and download. That's just one
significant feature of this promising peer-to-peer network. Freenet
inventor Ian Clarke may not be talking about his new company, Uprizer,
but he has a lot to say about how decentralized architectures can fix
what ails the Internet. Here's the interview." We've heard from Clarke before, but this is an interesting piece.
That's why fnnews was created. It hasn't been updated for Freenet 0.3 (I'm very busy and some other people who are thinking of reimplementing it such as Brandon Wiley haven't gotten around to doing so). What it is a Usenet-like enumeration-based newsgroup system. Individual posts are static content, but fnnews newsgroups behave like dynamic content (of course, you have to have a client which supports it - and fnclient hasn't been updated for Freenet 0.3.x). Once fnnews is updated, then Freenet can really have discussion over it. There also is fnindex, IIRC may have been updated by Brandon. It is an index system similar to fnnews except that it is designed for in-Freenet key indices rather than discussion.
Actually, very little content is stored directly under a named key. What happens is you store the data under a key whose name is a hash of the contents. Then in a seperate key with a real name you include a redirect to the hash key. So you would only have one copy of, say, the GPL, even if it has a dozen names. MP3s might have a lot more "duplicates", but none exact (ie, you'd have one at 128 bps, one at 112, another at 128 that wasn't quite ripped as well, etc). Nothing can be done about that (well, not easily).
Visit me on #weirdness on the Galaxynet.
--
I'm now on a cable modem, and we're not permitted to run servers by the AUP. Nor do I have a choice, because DSL is unlikely to become available any time soon, because I'm too far from my CE. Based on the probability of increased legal pressure by parties like RIAA, MPAA, etc, who want publication to remain a 'big-shop' capability, I expect the no-server trend to continue and increase. From the ISP's point of view, it's a way to control liability. (Common-carrier status is far from assured, erosion has occurred already.) From Joe Sixpak's point of view, no big deal. Small-time hobby-oriented web space at the ISP and places like GeoCities serve just fine.
Give it less than 5 years, and the ability to 'Peer' may well be a big-budget item, past the range of the small-timer.
The living have better things to do than to continue hating the dead.
Yes, I am sure something like slashdot could be built within freenet - but the end user experience would be radically different. I could not respond to your response as quickly as I am today - heck, I might not even see your response. It just would not be the same.
Look at Usenet, it is distributed, and some people have attempted to build status and moderating systems into it all using smart clients (as another respondent suggested) but it still produces nothing like the experience of the real slashdot or other discusssion based web sites.
There are some services that a distributed system with the current communication limitations of the internet cannot provide.
-josh
"Instead of clicking on a reply link, you write a counter-argument or suppliment to a piece by another author and upload it. If its well-written and informative, then it will presumably be passed around by lots of people and spread through Freenet. Which would also (in theory) create interest in other pieces on the same subject...."
Wow! You've just reinvented fidonet!!
on a more serious note, I really don't want to go back to something that takes that long to proliferate, if that is indeed what would be required for this to work. Slashdot's strength is in its real time and its relatively small downtime. If I have to wait days, hell, even hours to post and reply in discussions then I'll just not bother. This may sound a little bit conceited, but I believe that there is such thing as sacrificing _some_ security in favour of speed, assuming that actual gains outweigh the failings. Since Slashdot is very fast updating, and is fairly easy to make anonymous, I'll stay with it. Freenet is a good idea, but I don't know enough about its logistics to know if it even can be done on the scale that currently is used, let alone the speed...
"Titanic was 3hr and 17min long. They could have lost 3hr and 17min from that."
IBM had PL/1, with syntax worse than JOSS,
And everywhere the language went, it was a total loss...
On Freenet's conceptual forebears: "The intention of the original Arpanet was
Wasn't it proven that it is a myth that part of the design of the internet was to withstand a nuclear war. I remember hearing a quote that even the military isn't stupid enough to build a system that will be around even when there wouldn't be anyone left to use it.
Yes, there are some kludges using subspaces, but fundamentally each document stored is a static document.
Suppose I don't care about storing versions of my web site? Suppose I change prices on my products on a daily basis and I cannot afford to have a single straggling copy of a web page with the wrong price on it? Suppose I have to absolutely positively guarantee that every portion of my web site is viewable to every user who visits?
There are just some things freenet will never do well.
That said, when is someone going to come up with some good solutions for mirroring and distributing dynamic content?
-josh
I attribute this fault to Freenet's coarse-grained object model (which I in turn blame on Unix, but that's an entirely different story). It's built having in mind heavy-weight "documents", not light-weight, generalised, abstractly-modeled "objects". A proper implementation of the Freenet concept would be like a mega-Slashdot (or more appropriately, a mega-Everything2 or somesuch): a gigantic distributed object database. Better, instead of having a predetermined interface, the software could have transparent bindings for all popular languages; it also support easy object format change; et cetera, et al...
But of course, that's "awfully hard" to understand and implement... especially when you're dealing with stupid, static languages... sigh
To the editors: your English is as bad as your Perl. Please go back to grade school.
IIRC, If you know the key for the official copy of the data, then that's what you're getting. Freenet's architecture includes checksum-based keys -- meaning that if you know the key (which includes the checksum), your client can verify that the file is correct.
That, and you can just use public-key authentication for verification of authenticity.
I can imagine it now. You're using Freenet, and you see this banner ad that says, "Warning: Your freenet content may not be permanent! Click here to subscribe to our service, which guarantees to request your content 10,000 times a day." It would be a kind of popularity inflation effect. Everybody who didn't abuse the system would get their content labeled "unpopular."
--
Find free books.
It's not all that bad.
If you want your node to store your information, you can force your node to retain that information. OTHER nodes may not store it if nobody else requests it, but that's fine -- nobody'll mirror a big web page that nobody wants to read, nor should they be forced to.
Anyhow, once enough people run nodes, information will need to be quite unpopular to be completely dropped off the network. Only marginally unpopular stuff may become rare enough to take longer to retrieve (not mirrored close to you) but that's a big difference from entirely unavailable.
IIRC, VC has been discussed on the Freenet mailing list -- indeed, I think proposals exist for implementing it.
Ahh I remember those days.. the free Unix BBS systems... Free Nets! Societies of computer people.. who knew how to use unix. Are people getting dumber? Because it seems that now people can't use Unix or even Windows anymore.. yet ages ago they could! Hrmm what's going on here?
The great thing about the Internet now is that I, as an individual, can publish pretty much anything. I can write music and put it out, I can write fiction and put it out where people can come by and access it. Until the early 90s this was just not possible. If my stuff is not enormously popular - so what - people who enjoy that kind of thing can still get it. I can publish to my heart's content and the few hundred readers can read it. Similarly, I can go and get obscure stuff myself - something that wasn't possible before the internet showed up in its current form due to publishing barriers.
But Freenet will just drop this stuff because it's not popular - and this seems like a retrograde step to me. It re-erects those old barriers to publishing that the Internet is destroying - and eventually, Freenet just holds what the Sheeple want. We end up with a network that's no better than TV or the print press - containing only what's popular. We end up with masses of Britney Spears or Blink 182, but you can't find something like the Bottom Feeders or Bradley N. Litwin.
So to summarize: Automatic for the Sheeple.
Oolite: Elite-like game. For Mac, Linux and Windows
--
--
--
--
Note: For those of you too lazy to read the whole thing, the part I am talking about is on the second page of the aforementioned article.
Free Hans!
On a time scale, this works wonderfully for daily updates where a slightly popular piece of content is pretty sure to be mirrored nearby. But for slashdot, it would probably generate just as much traffic (or more, depending on the overhead of requesting updates to the latest second). For dynamically generated content using what-have-you, it would just not work at all. All my slashdot pages say "Pink Daisy" on them somewhere... I'm sure no one else would desire to cache those. I could find my computer at work cacheing a copy of slashdot for each of my coworkers, who skips over it for the latest version. Also, and I'm not entirely sure about this, I thought that old content becoming less popular and being removed was one of the serious difficulties with Freenet.
If you are modding me down because you disagree with me, use the "Flamebait" category, not the "Troll" one.
Peer to Peer is not just about file sharing, it's about colaboration and communication at a higher level. For the ISP's to stifle it will be about as dificult as taxing email, simply put it ain't gonna happen.
Bandwidth is just getting faster, the p2p technology is getting more more fancy. To block any kind of 'incomming call' from any source on the internet to dsl/broadband customers is basically television.
I can understand your fear, but rest assured.. your prophesy of a non-contributing internet nation is not reality.
This was not meant to be a flame. Cheers
--------------------
This really isn't a problem. If somebody wants to set up a server farm with 10,000 machines, each requesting a certain document, then you are free to do that... even if you distribute them across the world.
With Freenet, it isn't a problem because you are then saying that all the nodes have a specified piece of information, and it is all done on your dime anyway, so who is hurting? All that really happens is if I decide to access that data as well along the line, the likelyhood of finding a node with the data is going to be pretty high. Indeed, in such a scheme it still wouldn't be a problem even to the people running Freenet, because you've just added 10,000 nodes to Freenet and at least some of the server space will still be available on those nodes to store stuff that belongs to other Freenet users. It would be a win-win situation.
As far as making a bot to keep requesting a piece of information, all that it would affect is your local node, so it would at least allow others to grab it off of your node if it somehow became a piece of "popular" data. That sounds like a very good piece of software you should write... so please submit it!
According to the K5 article, Stirling advocated the implementation of laws requiring that ID-tags be affixed to data transversing the Freenet.
"I propose a law requiring a transparent tag showing origin and history on any file on any server, and that the file be immediately accessible on request. The authorities should develop and send out a "sniffer" intelligent agent program to detect files not meeting these criteria. Immediately shut down any server/node that doesn't reply properly. With really... severe... penalties for anyone owning hardware harboring pirate files. Sufficient to make them take elaborate precautions not to do so."
Furthermore,
Stirling claims that he talked to the FBI, who told him that they have the ability to penetrate Freenet's anonymity. I suspect that either they were (a) blowing happy smoke Stirling's way, or (b) they were thinking of Carnivore catching the evil copyright violator's insertion at the ISP, before it actually enters the Freenet.
To some extent, I can empathize with Stirling's fears as an author -- I wouldn't necessarily want someone to reproduce my copyrighted works with impunity and scatter to texts to the winds. However, I find Stirling's "draconian" (to use his own words) reaction unsettling.
I'm wondering about the possibility of Stirling's proposed restrictions to Freenet. Are such measures feasible (legally and technologically)?
Sincerely,
Vergil
Insects and Grafitti Photos
- The issue of goodwill: Freenet can be subverted. Because anyone can run a Freenet node, it would be trivial for a black-hat to claim to have any information which is to be censored, and either return something else or look to see who is submitting the requests.
- The issue of spoofing. Merely faking the metadata on documents could really mess up the system.
- The issue of request propagation. A document which is widely distributed will be returned quickly, but a document which is present in only one place potentially requires the request to visit every Freenet node. Suppose that someone generates a bunch of bogus requests for documents which do not exist? Each request goes to every Freenet node, flooding the system.
I know next to nothing about these issues, but I was still able to formulate the questions. Why don't we have answers? If Freenet is supposed to be able to function even in a very hostile environment, shouldn't it be proof or at least resistant to these attacks? And we know it will be attacked, by bored script kiddies if no one else.--
Time is Nature's way of keeping everything from happening at once... the bitch.
Thoughts regarding P2P: What are the implications for security in the P2P world? Seems like it would be very easy for someone to crack into the local client S/W and figure out to breach security on a Peer's machine by sending scripts/etc. If this is possible, the implications could be profound as a cracker could gain access to hundreds of machines as the crack propagated itself around the P2P network. Infected clients could update S/W from a site other than the one intended by the end-user (and thus infect more computers, etc). The possibilites for security violations are endless...how do we prevent/reduce the chances of such harm for P2P networks? I.e. besides using regular security measures, open source, etc. what else would work? Redesign P2P clients to use more client/server architecture for S/W updates/patches (but maintain P2P connections for data - still issues of passing cracks disguised as data remain)? What else?
In Mojo Nation we deal with the same problems of herding cats, in this case it is a problem of how you can cache content effeiciently and effectively without knowing what is really going on. Markets are one such distribution system that has a very long history of people tweaking (and trying to cheat, therefore building up its protections against most types of fraud) and it actually does solve some of the problems you address. We are not as gung-ho on the whole "information must be free" bit as Ian, but we do know that these sorts of P2P systems are the ideal infrastructure for the next step in internet content distribution.
jim
The next step for these systems are to pass around the code to turn the database of objects (which P2P systems like Mojo Nation and Freenet are good at distributing) into something dynamic and structured on the local client. Imagine giving the user a chunk of the /. database for an article along with code to explain how everything should be formatted, etc. The presentation and organization is local (along with any dynamic effects) while the data is just a selection from the pool of possible objects. This would also mean that when you download the articles you can pre-load the higher ranked articles or use collaborative filters to trim out the bits you are not interested in and avoid having to download these in the first place.
Freenet has some good cacheing mechanisms in there but there is a balance which needs to be maintained between de-centralization (which provides the censorship resistant features of systems like Mojo Nation and Freenet) and dynamic information features that require a trusted codebase for execution. If Java had lived up to some of its hype perhaps we could be passing around dynamic objects that contained information and presentation all in one bundle and we would run these in our browsers without fear, but it just didn't turn out that way...
So freenet can't do everything. Big deal; it's not intended to. HTTP sucks at doing "real" dynamic content, too; that's why chat rooms, "news tickers" and suchlike are done as Java applets.
:-)
While you can't do full database lookup things, you could do versioning fairly easily by adding an "update key" to stuff that could be updated. This would be the owner's public key and a string encrypted with the owner's private key. When a message with the appropriate tag comes in to the local server, it supercedes the old information. It might simply add a "superceded by" pointer to the old version; there are good reasons for keeping old versions around, not the least of which is to guard against post-facto censorship. To get an old version, you simply add the version number to your request.
As to something like Slashdot, note that it is not really "dynamic" information. It is a sequence of static submissions. Submissions could simply be Freenet messages. The only thing that is really dynamic is the moderation scores. These could either live on a normal website or go out as frequently updated messages (see above) from the main site. Should be fairly easy to do a Java applet that pulls it all together. (It'll be a while before browsers unserstand "freenet://" URLs
BTW, I'm not familiar with the exact architecture of Freenet, but I would assume that when you put a message into the system, your local system tags it as the "definitive" version. It is then outside of the LRU cache scheme. It may take a while to get it from elsewhere in the network, but it's there.
The big problem that I see with Freenet is that 95% (at least) of the data will be pr0n and warez. The pr0n and wares kiddies are collecters and love to play "minez bigger than yourz" games. If one of them has, say, 100 pirated versions of Microsoft Office, he'll happily pump them all into Freenet just for bragging rights. Other kiddies will check them out, and like as not, relabel and retransmit them.
There's no way that I can see to stop them; basically, it's a built-in denial of service attack.
--
Welcome to the Turing Tarpit, where everything is possible but nothing interesting is easy.
--
Another thing that worries me is that one of the characteristics of censorship is that it's mysterious: you don't know what you're missing due to censorship. This sounds a lot like what happens when your speech mysteriously disappears from Freenet, presumably due to low popularity. How do you know that it was really due to low popularity, and not to someone cracking Freenet? To me, the issue isn't really permanence, since dead tree format is the only format that's really permanenet on time scales of more than 30 years. It's the issue of not knowing how long your information is supposed to last. I'd rather know that my information will be there until I stop paying the bill to my webhost.
Finally, it seems that a lot of the agenda behind proposals like the .porn TLD is to make it
easier to recognize unpopular speech so that it can be censored. Doesn't it seem like running
a Freenet node is the ultimate red flag being waved at the censors, saying, "Secret police, here
I am"? Maybe the information is already out there and
free, but your own wetware is now in a smelly jail cell...
--
Find free books.
--
The author looks at the terrible p2p implementations in napster and nutella and concludes that the p2p community in general understands the nature of the net so poorly as to make the same mistakes. If you look in the archvies for the decrentralization list on egroups you'll see that some people have addressed and are addressing the very issues he says will be a stubling block. Just because the author can't think his way through the problems of bandwidth, infrastrure, and reliability doesn't mean that people with better minds than him can't.
--
You get Mojo when you actually provide service for someone else (i.e. you let someone download a block from you, accept a block from someone, return search results, or relay messages for others). Tokens are given directly to the counterparty (though they exchange them for fresh ones right away so you can't spend the Mojo behind their back).
Nope. Both of them are utter pipe dreams. The "transparent tag showing origin and history" already exists today, except it has a much shorter name and a much more spotty record. They're called "watermarks", and they're pretty much a joke. Just look at SDMI, which has had some brilliant minds tackling the watermark problem and, even after millions of dollars in research, they still haven't managed to come up with a way to stop a really determined 15-year-old.
Translated into modern idiom,
- I propose a law requiring watermarks on every file on every server, and that the files be immediately accessible on request.
Problem number one: watermarks don't work.Problem number two: if the law is going to require that every file on every server be immediately accessible on request, that's going to play hob with e-commerce. Do you really want to place that order for Naked Amazon Women In Bondage from Amazon.com, knowing that anyone can send an email to Amazon saying, "Hi! Pursuant to the new Federal laws, I want to investigate your site to make sure you're not using any of my IP. Please send me all of your customer purchase records."
The alternative to this, which Stirling probably means, is that the watermark be kept available, although the file may not necessarily be. That defeats the purpose of a good watermark; one of the principles of good watermarks is they can't be removed.
- The authorities should develop and send out a `sniffer' intelligent agent program to detect files not meeting these criteria.
Stirling, meet the First Amendment. If I don't want to include watermarks in my original works, neither you nor the government get to say whoopty-doo about it.On a technological note, I've got some experience with smart agents. At the present time, they're really not very smart. Remember that there exist such things as countermeasures; once people figure out what ruleset the expert system behind the agent is using, they'll figure out ways to avoid triggering the agent.
- Immediately shut down any server/node that doesn't reply properly
Violates due process of law. Shutting down a server does Nasty Stuff to online businesses, and would require that a court hearing be held. Remember, nobody can be deprived of life, liberty or property without the due process of law.This is the only proposal which is feasible technologically, BTW. After all, to take down a server all you need is a fire axe and strong arms.
- With really severe penalties for anyone owning hardware harboring pirate files
Violates the legal principle of mens rea, which basically means--"if you had no criminal intent, then you didn't commit a crime". If I'm an ISP and someone is running warez off their shell account, I'm not liable until I'm notified of the illegal copying and I have time to verify the allegations myself.Technologically unfeasible, too, given that many systems will be harbored in foreign countries which are not signatory to any such ludicrous treaty as Stirling is suggesting. To penalize the owners of those servers would require... well, a small Special Forces team could probably convey the US's displeasure, but that seems like overkill, doesn't it?
- Stirling claims that he talked to the FBI, who told him that they have the ability to penetrate Freenet's anonymity
Maybe true, maybe false. Sounds more like happy smoke to me. Think about this: if the FBI does have this capability, why in God's name would they tell anyone about it?Stirling needs to talk to his dealer about the purity of his rock.
This is not erecting new barriers to publishing, it is lowering them and letting anyone get in on the action. Nothing is for free, but if people work together we can make the cost so close to free that no one will really care. In the end, you need to have at least some cost for publication or else you are just shifting the problem from one of publishing to one of filtering out all of the crap that everyone else is publishing (which turns into its own set of messy problems.)
jim
(I believe this is in our faq.)
Freenet is a work in progress, and it isn't even half done at the moment. Ways to update data on the network have been on the table for almost half a year. It's not an easy thing to achieve, but we believe that it can be done, and I think we are 90% agreed on the method (I wrote up a detailed proposal a few months ago, which should be somewhere on the webpage). Don't hold your breaths, but I would certainly like to get started on it in the somewhat near future.
That said, there are of course things that cannot be done on Freenet the way they are done on the web. Obviously you can't allow limited lookups against a database for example, but more often than not it will be a question of thinking different (let Freenet be the database...)
/ Oskar Sandberg
Check out the new 0.920 version, just released yesterday! A much better install, faster and a lot less buggy as well. The centralization issue is being worked on (there is a single bank, although peers use micro-credit between any two counterparties so bank failure != system failure) and we are pushing things out to the edges as quickly as we can.
Part of the advantage we think we have with a market-based structure is that it is easy for us to be flexible about control decisions and letting local choices provide emergent behavior. For now, some stuff is centralized just because it was easier for us to do it that way and move on to the important bits that needed to get coded -- we are paying the price of this and going back to replace certain centralized features with most distributed solutions, but in the end it is simple for anyone to build a better mousetrap to solve a problem within Mojo Nation and replace an existing market actor by offering the other agents a better deal. :)
jim
Here was something I didn't understand from the explanation of this decentralized, caching system. If I want to post an encrypted document that only I know about for later retrieval (say in 5 years) how does the system prevent it from getting deleted from all nodes for unpopularity? If there is no central authority, doesn't that imply that either: 1. documents can be lost or 2. each peer has to be able to talk to all other peers to preserve unique but unpopular files? DOS sounds a problem with this also.
Anybody remembers util-linux with a backdoor on a server in Holland?
I'm not going to rely on any data from untrusted sources. :-)
I don't mean slashdot
Last month I had to prepare a presentation about the perspectives of P2P networks and the CNET article The P2P Myth was one of the most usefu
l sources of both ideas and links for further reading.
Look around. How much of your web-surfing time is spent reading totally static documents?
Don't you spend far more time on sites with some form of interactivity, or at the very least, which are updated from hour to hour?
Incidentally, I think the terminal client to terminal client approach is technologically backward. It may have some advantages in preventing censorship (though I'm willing to bet that it would be pretty easy to spoof freenet, one way or another, to lower it's signal-to-noise ratio below slashdot in flat mode, ignoring moderation scores), but it would make far more sense with a true "web" structure than with the internet which is closer in many ways to a free tree. Caching on machines that are only connected to each other through a backbone makes much less sense than caching on the backbone.
--------
As a Freenet developer, I feel compelled to correct some of the inaccuracies being presented by commentors as fact.
"Freenet is an attempt to replace the web." - This is more true than saying that Freenet is a replacement for Napster, but it's still not true. Freenet is better than the web in a couple of ways, mainly anonymity and decentralization. If you don't need these features, then by all means use the web.
"You can't create Slashdot on Freenet because Freenet doesn't have dynamic content." - Sure you can. A web forum was already created, but is currently being overhauled. We already have a web frontend and newsgroups, mail, and hyperlinked documents in Freenet. A web forum is just an HTML frontend to a newsgroup with some bells and whistles. The reason that they use dynamically generated pages is because they use RDMS backends so that the servers can handle the load. Since the load in Freenet is distributed, this isn't necessary. Sometimes you really do need dynamically generated content, but in the case of web forums it's mostly just a performance enhancement.
"Popular == worthless. Freenet will be filled with worthless stuff." - Popularity is local, not global. If you connect to your friends instead of random strangers then the local network will be filled with items of shared interest.
"The problem with Freenet is that unpopular items are dropped." - Popularity is local, not global. You want items that no one in your local network is requesting to disappear. Files go to where they are wanted and disappear from where they are not wanted.
"I can't trust the information that I get out of Freenet." - We have tamper-proof keys that rely on digital signatures and content hashes. If you are worried about authenticity, then use those.
"Freenet must track what people request because it knows what is popular. That leaves an audit trail that compromises anonymity." - Popularity is local, not global. Your node discards items that have not been requested in a while. There is no global rating or tracking of any kind.
"Freenet requires a high-speed connection" - No, but it would certainly be nice.
Sorry, I pressed "Submit" too early:
The P2P Myth
Oh, wait... we're talkin' 'bout 'puter stuff here, aren't we? Damn... I was hoping to pollute the world's water supplies with LSD.
The colors, the colors... I can see the music!
Hi! This is the Sig, blatantly attached to the end of this comment.
Mojo Nation deserves a plug.
It has an ingenious solution to the freeloader problem, namely an
internal currency system, which may make the system more scaleable
than Freenet. Advogato also
runs some good discussions of these issues.
It seems to me like freenet also needs to track data to a certain extent because it caches the most popular content on other sites. That means there is an audit trail, even more than me setting up an ftp server on the different IP addresses I get with a dialup account, and just send an encrypted email to my friends to upload/download the content that is illegal from there. I would think there is less chance of me getting caught, even though I have to more actively do something considered illegal. Also, keep in mind that I realize freenet is not only going to be used for illegal stuff. But, it is the illegal (illegal is not always immoral, but often unpopular to the powers that be) content that is going to need the most protection and need to be cached the most. Stuff like deCSS mirrors are one example. We might be able to build on the peer to peer model some, but we still need there to be a strong structure based on a server passing clients to each other, or something. The only problem is that we know they won't allow this easily. Just look at napster, who does not distribute mp3's, but is getting in trouble for users doing it.
Anyone else have any better ideas?
Mas vale cholo, que mal acompañado.
Ian wants to basically replace the web with freenet and has said as much. But what he doesn't get is that he is not going to replace the web as we know it with static documents (which is all freenet serves up).
Come on, how could a web site like slashdot possibily exist in freenet? It couldn't. It is simply too dynamic, too frequently updated, and reliant on a coherent and consistent database of comments and articles that simply cannot exist in a distributed network.
Freenet will be a boon for the archival of static and infrequently updated content and web sites, but for anything more dynamic, freenet fails to offer a solution - and as such will nicely complement, but never replace the web.
-josh
--