You need to use UDP in order to do the transfers through firewalls. NATs & firewalls allow solicited UDP (necessary for most all UDP-based transfers to work), but disallow TCP. A reliable UDP layer is of course going to have the "did you get it? yes/no"-ism of TCP, because that's the whole purpose of it.
Take a look at the links in the article. The link is to the GPL'd LimeWire code for a reliable UDP layer. The link to the p2p hackers discussion is also from a bunch of people about how to do a reliable UDP transfer.
If there is an algorithm that can detect whether or not a photograph is forged, wouldn't it be possible to have another 'competing' algorithm that randomly altered bits and used the detection-algorithm as its success scale? (The better it becomes at not being detected, the better the genetic algorithm is doing.) Seems that that'd work fairly well, and would apply to lots of other technologies that require seamless photograph overlays.
Descarte was one of the first philosphers to discuss the quandry about a "thinking machine", mentioning the problem in viewing a machine dressed up in a hat -- can we consider it human?
The Elegant Universe is a brilliant read on string theory, which is just an utterly amazing concept (down to the quantum theory level).
Orality & Literacy describes how a cultures that have a written language will evolve differently than those who only speak. It examines how an oral society will not consider an "oak" tree to be anything similiar to a "pine" tree, because the concept of a "tree" doesn't exist. Literacy brings about abstractions.
Terrible may have been an extreme (although not entirely incorrect) choice of words, after looking for a source. The exact quote is:
--- The third and newest of the methods is the Bit Torrent support that has been added to the newest of the Shareaza betas. Bram Cohen the creator of BitTorrent told Slyck that in his view Shareaza's implementation was not perfect. Based on comments he had read he said that "the shareaza author doesn't understand BitTorrent's tit-for-tat algorithms at all" and therefore "the client is unlikely to be able to offer as good performance as the official one." He also slammed Shareaza for not speaking to him saying no one ever told him anything about Shareaza's support. ---
SWT is definitely an option, the problem is that LimeWire would sacrifice the "run anywhere" beauty. There's LimeWire users on Windows, Linux, OSX, Mac Classic, OS/2, SunOS, etc.... Until SWT is ported to every platform, LimeWire's going to continue using Swing.
Another option is an abstraction layer between Swing & SWT -- there's some projects (SwingWT, to name one) that are doing that, but it's incomplete and LimeWire won't compile right now with it.
Swing is pushed to its limits (and sometimes beyond) right now with LimeWire, painting progress bars & icons on tabs, user-configurable change-at-runtime themes, tooltips & rowstripes for tables & lists, real-time statistics graphs, etc... a port to SWT (or an abstraction layer of SWT) would be a massive project.
You can do 100% of what Shareaza tries to do with LimeWire -- that is, search for and download files. The network it runs on is implementation details. You can in fact say that Shareaza is bloated for adding support for multiple networks instead of making one network work as good as it possibly can.
Bram Cohen has complained that Shareaza's BitTorrent implementation is terrible. Gnutella developers have complained that Shareaza's Gnutella implementation is outdated & that it wrongly sends tons of "Gnutella2" packets to clients that don't want them.
Would you prefer a client that picks a goal and makes it work amazingly well, or a client that tries to do lots of things so-so?
Open source clients & protocols, like LimeWire (on Gnutella) have made huge advances in the level of file-sharing, forcing other proprietary apps to play catch-up (and, in this case, probably playing a big part in making Shareaza go open source).
The same logic behind wanting voting machines & encryption schemes to be open source applies to wanting p2p networks & clients as open source.
Just one more horror story
on
Stealth Inflation
·
· Score: 4, Interesting
It's sad that when people tell horror stories, others reply, "Yeah, that's about normal." We should not sit idly by while companies continue to 'mistakenly' swindle consumers out of money. I have personally spent countless hours fighting with RCN (a cable/phone/internet) company to refund $182.91 that they owe me. The full story is available at my RCN sucks page. I've had to resort to telling my credit card company to refuse payment, because RCN still refuses to return the money they owe me.
Tons and tons of Panther users have found Java to be broken after upgrading. Apparently Panther incorrectly installed Java. Typing 'java -version' reports back "HotSpot at incorrect virtual address. Sharing disabled." Some reported that if they explicitly tried to use the 1.3 JVM that it all-out-crashed on them. Others just reported not being to start Java 1.4 apps.
I guess that fits also. I tend to use that particular argument by Descartes as the philosophical basis for quantum physics. Basically, you can't know anything exists until you've interacted with it (hence superposition, ala Schrodinger's cat)...
i'm not really too sure what you mean. limewire ues java's swing implementation to do the drawing. if java does funky redraws, then so will limewire. either way, you can download the code yourself -- just look at the 'gui' project from www.limewire.org.
and yes, improving java *will* improve acquisition, because acquisition literally runs limewire's java core and then provides a native interface for it. so if limewire's core is running faster (which it might, because it'll be using java 1.4), then the interface is updated faster and the program as a whole is faster.
i can assure you there's no code that "messed with the window server". the warping you're probably referring to is java being slow and not allowing time for the Swing Event Thread to completely process all the redrawing. but, the code tries to make sure that swing is given as much time as possible to keep things updated.
I bought myself an Archos Jukebox, and then returned it to get an iPod. To be honest, the Archos kinda sucked.
There's no 'hold' on it to prevent you from accidentally turning it off -- the hold is like a 'soft hold' of sorts that works only for not changing the song that's playing. You can still turn it off or change the volume while it's on hold. And, the hold is set/unset by just pressing and holding the 'on' button, which can easily happen accidentally.
The controls for it are not very well-thought out... I like listening to my music on random (so I can eventually hear everything rather than focusing on a few albums over and over).Sometimes when I hear a song I want to restart that particular song to hear the beginning again -- but when the Archos is set to shuffle, hitting 'back' will move to a new song, and then hitting 'forward' will move to a completely new song -- there's no consistency in the shuffle algorithm.
The manual for the Archos is awful -- it doesn't explain what anything on the screen means. While charging it, I had absolutely no clue what the random XX:YY numbers were while charging -- were they hours:minutes, or minutes:seconds, or just random numbers? And why would it sometimes say 'Batteries Fully Charged' and then 5 minutes later go back to charging for another hour or two.
It would turn off occasionally, too. And it would skip on songs that play fine on my computer, or randomly get stuck on songs and repeat them forever.
In all, the Archos just seemed to be a very flaky mp3 player. Luckily, Circuit City let me return it for the full price 33 days after I bought it.
I don't have my iPod yet (it should be arriving in the next few days), but I am very much looking forward to it. Everything I've read, and everyone I know who has one absolutely loves it.
A small collection of rather interesting quotes, taken from the RIAA's press release & the Register article...
---.. the U.S. Secret Service, assisted by a team of investigators from the Recording Industry Association of America (RIAA), on Monday morning raided a major music piracy operation in New York City, leading to the capture [...] of 421 CD-R burners [...].
"There were only 156 actual burners, but some run at very high speeds: some as high as 40x. This is well above the average speed," was the official line yesterday.
The Secret Service, we naively presumed, was employed to protect high-ranking elected officials.
"Perhaps the truth is less interesting than the facts?" asked Amy Weiss, the RIAA's Senior VP of Communications.
Programming languages are just going through the normal stage of evolution. Early oral cultures had little to no abstraction because the 'language' didn't support it. Then the invention of writing offered a quantum leap in understanding, letting people realize that both an oak and pine were 'trees' (a previously meaningless word).
Programming languages, while not following exactly the same paradigm, are definitely following the same thread. The more advanced they become, the more advanced people who use them become... allowing things to be done in multiple ways and bringing in a new wave of thinking about programming.
Slashdot Mirror
You need to use UDP in order to do the transfers through firewalls. NATs & firewalls allow solicited UDP (necessary for most all UDP-based transfers to work), but disallow TCP. A reliable UDP layer is of course going to have the "did you get it? yes/no"-ism of TCP, because that's the whole purpose of it.
Take a look at the links in the article. The link is to the GPL'd LimeWire code for a reliable UDP layer. The link to the p2p hackers discussion is also from a bunch of people about how to do a reliable UDP transfer.
LimeWire doesn't have any spyware, at all. In fact, it has absolutely zero bundled software. Even with the free version.
If there is an algorithm that can detect whether or not a photograph is forged, wouldn't it be possible to have another 'competing' algorithm that randomly altered bits and used the detection-algorithm as its success scale? (The better it becomes at not being detected, the better the genetic algorithm is doing.) Seems that that'd work fairly well, and would apply to lots of other technologies that require seamless photograph overlays.
Philosphy: Meditations (Descarte)
Science: The Elegant Universe (Green)
Language: Orality & Literacy (Ong)
Descarte was one of the first philosphers to discuss the quandry about a "thinking machine", mentioning the problem in viewing a machine dressed up in a hat -- can we consider it human?
The Elegant Universe is a brilliant read on string theory, which is just an utterly amazing concept (down to the quantum theory level).
Orality & Literacy describes how a cultures that have a written language will evolve differently than those who only speak. It examines how an oral society will not consider an "oak" tree to be anything similiar to a "pine" tree, because the concept of a "tree" doesn't exist. Literacy brings about abstractions.
I also recommend that you look at an older slashdot article Books on Programming Theory for more books.
Terrible may have been an extreme (although not entirely incorrect) choice of words, after looking for a source. The exact quote is:
---
The third and newest of the methods is the Bit Torrent support that has been added to the newest of the Shareaza betas. Bram Cohen the creator of BitTorrent told Slyck that in his view Shareaza's implementation was not perfect. Based on comments he had read he said that "the shareaza author doesn't understand BitTorrent's tit-for-tat algorithms at all" and therefore "the client is unlikely to be able to offer as good performance as the official one." He also slammed Shareaza for not speaking to him saying no one ever told him anything about Shareaza's support.
---
from mp3newswire.
SWT is definitely an option, the problem is that LimeWire would sacrifice the "run anywhere" beauty. There's LimeWire users on Windows, Linux, OSX, Mac Classic, OS/2, SunOS, etc.... Until SWT is ported to every platform, LimeWire's going to continue using Swing.
Another option is an abstraction layer between Swing & SWT -- there's some projects (SwingWT, to name one) that are doing that, but it's incomplete and LimeWire won't compile right now with it.
Swing is pushed to its limits (and sometimes beyond) right now with LimeWire, painting progress bars & icons on tabs, user-configurable change-at-runtime themes, tooltips & rowstripes for tables & lists, real-time statistics graphs, etc... a port to SWT (or an abstraction layer of SWT) would be a massive project.
You can do 100% of what Shareaza tries to do with LimeWire -- that is, search for and download files. The network it runs on is implementation details. You can in fact say that Shareaza is bloated for adding support for multiple networks instead of making one network work as good as it possibly can.
Bram Cohen has complained that Shareaza's BitTorrent implementation is terrible. Gnutella developers have complained that Shareaza's Gnutella implementation is outdated & that it wrongly sends tons of "Gnutella2" packets to clients that don't want them.
Would you prefer a client that picks a goal and makes it work amazingly well, or a client that tries to do lots of things so-so?
LimeWire is (and has been for the past 4 years) open source -- GPL'd and all.
Don't even bother. You've already got a free, open-source p2p app for all the platforms you could ever want, using LimeWire (written in Java).
You'd prefer security through obscurity?
Open source clients & protocols, like LimeWire (on Gnutella) have made huge advances in the level of file-sharing, forcing other proprietary apps to play catch-up (and, in this case, probably playing a big part in making Shareaza go open source).
The same logic behind wanting voting machines & encryption schemes to be open source applies to wanting p2p networks & clients as open source.
It's sad that when people tell horror stories, others reply, "Yeah, that's about normal." We should not sit idly by while companies continue to 'mistakenly' swindle consumers out of money. I have personally spent countless hours fighting with RCN (a cable/phone/internet) company to refund $182.91 that they owe me. The full story is available at my RCN sucks page. I've had to resort to telling my credit card company to refuse payment, because RCN still refuses to return the money they owe me.
Tons and tons of Panther users have found Java to be broken after upgrading. Apparently Panther incorrectly installed Java. Typing 'java -version' reports back "HotSpot at incorrect virtual address. Sharing disabled." Some reported that if they explicitly tried to use the 1.3 JVM that it all-out-crashed on them. Others just reported not being to start Java 1.4 apps.
FYI,
You can download America's Army from multiple sources very quickly at magnetmix.com. It'll download off of everyone who has downloaded it on Gnutella.
You can always use the LimeWire core and build something ontop of it that automates exactly what you want it to do.
Check out:
limewire.org and the javadocs.
And what happens if these mice & the mice bred by Harvard (that are incredibly susceptible to cancer) mate? Do they implode?
I guess that fits also. I tend to use that particular argument by Descartes as the philosophical basis for quantum physics. Basically, you can't know anything exists until you've interacted with it (hence superposition, ala Schrodinger's cat)...
Uh, it's not unique -- atleast the idea isn't. Ever read Plato? It's in The Republic -- The Allegory of the Cave.
That's the Matrix preloaded.
limewire is free software, if you want it to be. it's open-source. download and see for yourself. or here's the javadocs, if you're so inclined.
i'm not really too sure what you mean. limewire ues java's swing implementation to do the drawing. if java does funky redraws, then so will limewire. either way, you can download the code yourself -- just look at the 'gui' project from www.limewire.org .
and yes, improving java *will* improve acquisition, because acquisition literally runs limewire's java core and then provides a native interface for it. so if limewire's core is running faster (which it might, because it'll be using java 1.4), then the interface is updated faster and the program as a whole is faster.
i can assure you there's no code that "messed with the window server". the warping you're probably referring to is java being slow and not allowing time for the Swing Event Thread to completely process all the redrawing. but, the code tries to make sure that swing is given as much time as possible to keep things updated.
I bought myself an Archos Jukebox, and then returned it to get an iPod. To be honest, the Archos kinda sucked.
... I like listening to my music on random (so I can eventually hear everything rather than focusing on a few albums over and over).Sometimes when I hear a song I want to restart that particular song to hear the beginning again -- but when the Archos is set to shuffle, hitting 'back' will move to a new song, and then hitting 'forward' will move to a completely new song -- there's no consistency in the shuffle algorithm.
There's no 'hold' on it to prevent you from accidentally turning it off -- the hold is like a 'soft hold' of sorts that works only for not changing the song that's playing. You can still turn it off or change the volume while it's on hold. And, the hold is set/unset by just pressing and holding the 'on' button, which can easily happen accidentally.
The controls for it are not very well-thought out
The manual for the Archos is awful -- it doesn't explain what anything on the screen means. While charging it, I had absolutely no clue what the random XX:YY numbers were while charging -- were they hours:minutes, or minutes:seconds, or just random numbers? And why would it sometimes say 'Batteries Fully Charged' and then 5 minutes later go back to charging for another hour or two.
It would turn off occasionally, too. And it would skip on songs that play fine on my computer, or randomly get stuck on songs and repeat them forever.
In all, the Archos just seemed to be a very flaky mp3 player. Luckily, Circuit City let me return it for the full price 33 days after I bought it.
I don't have my iPod yet (it should be arriving in the next few days), but I am very much looking forward to it. Everything I've read, and everyone I know who has one absolutely loves it.
Bush should just watch Buffy. After all, he's trying to kill 'The First'.
(Did Buffy's speech at the end of last week's episode remind anyone of Bush?)
A small collection of rather interesting quotes, taken from the RIAA's press release & the Register article...
.. the U.S. Secret Service, assisted by a team of investigators from the Recording Industry Association of America (RIAA), on Monday morning raided a major music piracy operation in New York City, leading to the capture [...] of 421 CD-R burners [...].
---
"There were only 156 actual burners, but some run at very high speeds: some as high as 40x. This is well above the average speed," was the official line yesterday.
The Secret Service, we naively presumed, was employed to protect high-ranking elected officials.
"Perhaps the truth is less interesting than the facts?" asked Amy Weiss, the RIAA's Senior VP of Communications.
Just ask google's history page.
Programming languages are just going through the normal stage of evolution. Early oral cultures had little to no abstraction because the 'language' didn't support it. Then the invention of writing offered a quantum leap in understanding, letting people realize that both an oak and pine were 'trees' (a previously meaningless word).
Programming languages, while not following exactly the same paradigm, are definitely following the same thread. The more advanced they become, the more advanced people who use them become... allowing things to be done in multiple ways and bringing in a new wave of thinking about programming.