From gwbush's website: "I am a reformer with results. Of the major candidates, the only one who does not have a DC zip code. I come from outside the system with a record of reform and a record of results."
The second sentence doesn't even have a VERB. The first sentence and the second half third say almost EXACTLY the same thing.
Actually, the first query is to split the load across multiple servers.
Linking servers is an interesting issue that can't be handled by the IRC protocol: you have thousands of people logging in and out, each providing a list of files with attributes, and you want to be able to search across all of the files available? Not a chance, unless you have some *really fast* indexing capability, and you manage to transfer *lots* of data between your servers.
Don't assume napster is just like IRC, just because the linux client looks like IRC. There are a lot of other issues.
Evan, realizing he may sound unfriendly but isn't intending to.
"I'd write a decentralised Mp3 trading program (that, instead of a central server or two has a decentralised network. sort of like IRC, only with less coordination). I don't have the bandwidth to test such a thing, or the time to implement it but I think it'd be a viable project."
That's exactly what the ads are paying for: not only the time/effort to write such a server, but the exorbitant bandwidth required for such a project.
I have already written a GNOME Napster client, without any help from the author of Napster. The downloading interface is a bit sketchy right now (GtkClist can't pack widgets, even though the docs say they can!@#), but it works, kinda.
There are two issues: 1) If my client doesn't display ads, then Napster, Inc doesn't get any money, which will eventually make the server go down. If I release the source, it would be trivial for someone to "remove" the ads code. There is also the issue of "free software" when it has ADVERTISEMENTS in it.
2) If I release the source, everyone will know the Napster protocol, opening lots of security holes.
Slashdot Mirror
From gwbush's website:
"I am a reformer with results. Of the major candidates, the only one who does not have a DC zip code. I come from outside the system with a record of reform and a record of results."
The second sentence doesn't even have a VERB.
The first sentence and the second half third say almost EXACTLY the same thing.
IDIOTS.
Actually, the first query is to split the load across multiple servers.
Linking servers is an interesting issue that can't be handled by the IRC protocol: you have thousands of people logging in and out, each providing a list of files with attributes, and you want to be able to search across all of the files available? Not a chance, unless you have some *really fast* indexing capability, and you manage to transfer *lots* of data between your servers.
Don't assume napster is just like IRC, just because the linux client looks like IRC. There are a lot of other issues.
Evan,
realizing he may sound unfriendly but isn't intending to.
There's a LUG here, I think. The link to their website is broken on the UW pages, though. :P
That's exactly what the ads are paying for: not only the time/effort to write such a server, but the exorbitant bandwidth required for such a project.
I have already written a GNOME Napster client, without any help from the author of Napster. The downloading interface is a bit sketchy right now (GtkClist can't pack widgets, even though the docs say they can!@#), but it works, kinda.
There are two issues:
1) If my client doesn't display ads, then Napster, Inc doesn't get any money, which will eventually make the server go down. If I release the source, it would be trivial for someone to "remove" the ads code. There is also the issue of "free software" when it has ADVERTISEMENTS in it.
2) If I release the source, everyone will know the Napster protocol, opening lots of security holes.
Can anyone propose a solution to these problems?
Evan