The anti-leech technology of the bittorrent protocol remains effective. Those ranting about this just haven't bothered to read... This client (despite the unfortunate name) is just smarter about how to use upload bandwidth, in an async world.
In fact, I would say this is an IMPROVEMENT in some ways over bittorrent's default behavior, as it will dedicate more of your outgoing bandwidth to higher-speed peers. They, presumably, can then serve up more data to others than a low-speed peer reasonably could.
Instead of being the end of bittorrent, this could really improve the health of the P2P network, increasing speeds and decreasing download times for everyone (not only those using this program).
All batteries contain heavy metals and as such are potentially toxic if not properly disposed of;
Yes. However, the materials in question are in a pure enough form, and enough of it is in one place, that they are inherently valuable even when used-up. This means you'll rarely if ever see them dumped. If they are, anyone who may see it will take the opportunity to cash it in, therefore recycling it, themselves.
Chemical fuels, however, are generally more hazardous, and much harder to contain as they do not stay together, on top of the ground, when dumped. Not to mention the numerous other hazardous materials, including some heavy metals, used in engines.
It still eliminates the vast majority of the moving parts, while allowing you to use liquid fuel.
It reduces complexity, but you're still stuck with terribly inefficient conversion from chemical to electricity. Without a 10MW power plant on your bumper, there's no way you're going to overcome that inherent limit.
Flywheels will never work because of the gyroscopic effect and the simple need for them to be massive.
Gyroscopic effects can be countered easily.
Flywheels are so promising because of the fact they do not need to be massive. Higher speeds have the potential for significantly more power storage than higher mass.
You can make a flywheel that will shred itself into something like cotton candy if the bearings fail - it's been done already, in fact
You can, but you don't need to. Numerous, smaller flywheels can be used, instead of a single massive one.
you really need to couple them as a generator
What made you think I was suggesting otherwise?
so you still end up dealing with an electric power system so they are silly.
No, they are highly efficient batteries. What is silly about that?
Supercapacitors are a good idea, but when will they be affordable?
I wasn't mentioning them as an immediate option.
a 30-second fill-up turns into a 15-minute fill-up just by the nature of batteries.
True, but easily manageable. There's no reason fueling stations need to be a separate stop. Make the fueling station part of a shopping mall, with numerous fast food restaurants, and refueling becomes faster, since fueling-up no longer becomes another stop.
Besides, the vast majority of fill-ups are going to be in your garage, at home, in the middle of the night, where it's infinitely more convenient, and time hardly matters.
I'm not opposed to serial hybrids in the short-term, though... Throw a compact electrical generator into an otherwise fully electric vehicle, and RIGHT NOW you've got the worlds most fuel efficient car, with the range of a standard vehicle.
I like the idea of electric, air, and other-powered cars for short trips,
It's rather unworkable to force that kind of dichotomy onto individuals.
if you're lighting and heating a house then surely any kind of lightbulb is 100% efficient...
Nope.
First, electric heating is much more expensive and much less effecient than natural gas, heating oil, etc.
Second, CFs use brutally cheap switching power supplies with a low power factor, which means much less effecient (higher line losses) than with fully resistive loads with a perfect power factor.
Most people don't object to privately operated security cameras.
As long as the cameras (and personally identifiable data in general) are hard enough to access that they will only be used to prosecute major crimes, most people would be perfectly happy. After all, since the beginning of time, officials could interview other witnesses and find out who was doing what, and when.
The privacy concerns really come into play when the cameras are online, and easily accessible. Then it's a force multiplier for the authorities, allowing them to track hundreds and hundreds of people with only trivial effort, as well as prosecuting every trivial violation of the law the cameras see.
In other words, it's not the cameras, it's the databases.
it is possible to play flash video files in mplayer under amd64.
Flash support in MPlayer is quite primitive. Only videos encoded with just the right options work. Things like compressed headers and the like can't even be opened.
There's a significant number of videos that simply won't work.
It doesn't matter that the tradeoff for that speed is flexibility, security, and portability. They want things to be fast for some undefined quantity of fast.
I've got to call you on the "portability" crap.
Java is about as portable as Flash... Sure, the major platforms are supported, but that's it. 3rd parties spent a lot of time trying to impliment java, but never did get everything 100%. Licensing issues, above all else, made it a real hassle to get Java on platforms like FreeBSD.
Meanwhile, C and C++ compiler are installed in the base system by default.
The only "portability" advantage Java has is perhaps in GUI apps, and that's at the expense of a program that doesn't look or work remotely similar to any other app on the system...
There are a great many reasons people don't use java. Performance is only a minor one.
Why dont people just use the quicktime package format,
Because Quicktime is despised just slightly less than Ogg.
Off the top of my head:
Significant overhead. Metadata at the end of files (like AVI). This precluding good playback of partial files, and causes really terrible problems with partially damaged MOV files. Unbelivably large number of different ways to do anything. An unbelivably huge and complex standard that probably nobody on earth understands entirely. 14 different versions of the standard, and a field in the MOV header to dictate which version of the standard the player should use to read the file. And finally: patents
If quicktime wasn't so horrible, you certainly wouldn't have ever seen formats like Ogg or MKV.
many of the same people who were telling potential new users that all these things were easy on Linux suddenly switch and say that Linux users are locked out.
Not at all. Linux users can play WMV video and audio. As of a few months ago, you don't even need the binary codec DLLs or an x86 system for the large majority of WMV video and audio formats.
The reason that's not openly supported by organizations, of course, is the patent licensing fees, which prevent most distros from including programs like MPlayer to begin with. Since the EU is repeatedly trying to get software patents into law, it would be rather hypocritical for them to suggest programs like MPlayer, wouldn't it?
Linux isn't the issue, it's just the reason it was posted on/.
The issue is a government that requires you to use commercial software to play. One that uses secret, undocumented file formats (even Real video would be a bad choice, in this regard). etc.
Quicktime, at least sticks with open and standard video/audio codecs, and MP4 container, despite the patent issues.
And if they put a little bit of effort into it, they could use patent-free formats as well.
Definately. If an interested party would pick-up Snow, finalize the bitstream, and start adding some performance optimizations for encoding and high-def playback, it could beat-out every other video codec out there. The quality/bitrate is easily better than even h.264, and can scale down to ridiculously low bitrates while being completely watchable.
Can these be inserted into the ogg bitstream without too much pain?
Nope. SnoPenguin nailed it. Ogg is terribly codec-specific.
MKV is gaining in popularity, partly because it can handle just about any audio or video format, including Vorbis, as well as subtitles, menus, chapters, etc.
Theora isn't ready to go, it's not even remotely ready.
Really? Why?
There's a reason why it's still an alpha whereas Vorbis is a full release.
And that reason is???
It's much better to admit there's nothing that works out there that's OSS than to recommend a poor OSS solution.
That wouldn't be true, of course.
The patents on MPEG-1 have long ago expired. It has pretty good quality (better than Theora/VP3) when encoded with a recent implimentation (ie. libavcodec for video, twolame for audio). And more than that, it is by far the most widely compatible format around, supported by just about every video player made in the past several years, on just about every single platform around.
I've no doubt in time Theroa will be its match,
I, however, do. The VP3 codec is hated by just about everyone who knows anything about video.
It has really poor video quality, compared to even much older video codecs.
It is very CPU-intensive to encode.
It's playback performance is horrible. Once you reach resolutions where a full frame can't fit in your CPU cache, you get performance worse than codecs like h.264.
In some 4 years of Theora's development, Xiph hasn't removed any of VP3's limitations, nor added any advantages over the original VP3 codec. Since they've frozen the bitstream, even the potential for them to do any of that has passed...
I was somewhat active in the Theora development process some time ago, but I've long since given it up for dead.
You should pay more attention before you "correct" other people...
The source was linked in the Doom9 thread the/. story linked to. I have the zipfile on my hard drive to prove it, and a large number of the comments in that thread revolve around a review of the source.
Please explain exactly how the CPU will know what priority the scheduler has assigned to a given process.
I don't specifically know "how". What I do know is that it's a fact, and quite easy to demonstrate.
Start a long-running CPU-intensive program (my preference is mencoder) at a low priority, and monitor the CPU tempurature. After you've given it plenty of time to cool down (a day or more if you like) start the program at the default or higher priority, and you'll see the tempurature is significantly higher.
A well-positioned amp-meter with remote sensing could tell you if the CPU suddenly needed more power.
Somehow I don't think that would meet the standard for evidence...
You need to measure tiny variations in current caused by one device, mixed in with the haystack of all the other electric devices in your house... Most of which can vary significantly from moment to moment.
So, if I have this running on a machine that also uses Tor then the "create extra CPU load" method would fail.
Not necessarily.
If you have your CPU-intensive app running at a low priority, and TOR running at a higher priority, then your CPU will become slightly hotter when TOR is doing heavy processing.
It may make it much harder to detect than it already is, but there you go.
there is a reason that after several breakups that they just coming back together.
Because they can?
It's not like market forces broke-up AT&T. It was the federal government. Now, it's the federal government giving them a pass, and allowing unlimited mergers.
If GM could buy-up Ford and Chrysler, you can bet they'd jump at the chance... Not because there's any good reason for a monopoly, but because getting rid of your competitors is always profitable.
It's no big deal for me to ZIP or tar-gzip my desktop data, and transfer it someplace. Pulling down data from some of these web apps in a standard format is less straightforward.
GMail is pretty simple. They provide POP3 access, so you can download it directly with your program of choice (check the box to keep it on the server, obviously).
UPLOADING it to Gmail in the event of a crash would be decidedly more difficult, though. That's good enough for me, though.
Slashdot Mirror
Name just one way in which Bittorrent breaks this rule...
I'll wait.
The anti-leech technology of the bittorrent protocol remains effective. Those ranting about this just haven't bothered to read... This client (despite the unfortunate name) is just smarter about how to use upload bandwidth, in an async world.
In fact, I would say this is an IMPROVEMENT in some ways over bittorrent's default behavior, as it will dedicate more of your outgoing bandwidth to higher-speed peers. They, presumably, can then serve up more data to others than a low-speed peer reasonably could.
Instead of being the end of bittorrent, this could really improve the health of the P2P network, increasing speeds and decreasing download times for everyone (not only those using this program).
Yes. However, the materials in question are in a pure enough form, and enough of it is in one place, that they are inherently valuable even when used-up. This means you'll rarely if ever see them dumped. If they are, anyone who may see it will take the opportunity to cash it in, therefore recycling it, themselves.
Chemical fuels, however, are generally more hazardous, and much harder to contain as they do not stay together, on top of the ground, when dumped. Not to mention the numerous other hazardous materials, including some heavy metals, used in engines.
It reduces complexity, but you're still stuck with terribly inefficient conversion from chemical to electricity. Without a 10MW power plant on your bumper, there's no way you're going to overcome that inherent limit.
Gyroscopic effects can be countered easily.
Flywheels are so promising because of the fact they do not need to be massive. Higher speeds have the potential for significantly more power storage than higher mass.
You can, but you don't need to. Numerous, smaller flywheels can be used, instead of a single massive one.
What made you think I was suggesting otherwise?
No, they are highly efficient batteries. What is silly about that?
I wasn't mentioning them as an immediate option.
True, but easily manageable. There's no reason fueling stations need to be a separate stop. Make the fueling station part of a shopping mall, with numerous fast food restaurants, and refueling becomes faster, since fueling-up no longer becomes another stop.
Besides, the vast majority of fill-ups are going to be in your garage, at home, in the middle of the night, where it's infinitely more convenient, and time hardly matters.
I'm not opposed to serial hybrids in the short-term, though... Throw a compact electrical generator into an otherwise fully electric vehicle, and RIGHT NOW you've got the worlds most fuel efficient car, with the range of a standard vehicle.
It's rather unworkable to force that kind of dichotomy onto individuals.
No. You've thoroughly demonstrated that you have absolutely no idea what Power Factor is...
Please educate yourself before making further claims.
Nope.
First, electric heating is much more expensive and much less effecient than natural gas, heating oil, etc.
Second, CFs use brutally cheap switching power supplies with a low power factor, which means much less effecient (higher line losses) than with fully resistive loads with a perfect power factor.
But the vast majority of these millions of actions are decided by a handful of people at the very top.
And those local decisions are usually based on general policies set by the top as well.
Most people don't object to privately operated security cameras.
As long as the cameras (and personally identifiable data in general) are hard enough to access that they will only be used to prosecute major crimes, most people would be perfectly happy. After all, since the beginning of time, officials could interview other witnesses and find out who was doing what, and when.
The privacy concerns really come into play when the cameras are online, and easily accessible. Then it's a force multiplier for the authorities, allowing them to track hundreds and hundreds of people with only trivial effort, as well as prosecuting every trivial violation of the law the cameras see.
In other words, it's not the cameras, it's the databases.
Flash support in MPlayer is quite primitive. Only videos encoded with just the right options work. Things like compressed headers and the like can't even be opened.
There's a significant number of videos that simply won't work.
I've got to call you on the "portability" crap.
Java is about as portable as Flash... Sure, the major platforms are supported, but that's it. 3rd parties spent a lot of time trying to impliment java, but never did get everything 100%. Licensing issues, above all else, made it a real hassle to get Java on platforms like FreeBSD.
Meanwhile, C and C++ compiler are installed in the base system by default.
The only "portability" advantage Java has is perhaps in GUI apps, and that's at the expense of a program that doesn't look or work remotely similar to any other app on the system...
There are a great many reasons people don't use java. Performance is only a minor one.
It's hard to believe a moderator was stupid enough to give you points for this crap.
A quick glance at TFA would instantly show you how stupid you sound.
Because Quicktime is despised just slightly less than Ogg.
Off the top of my head:
Significant overhead.
Metadata at the end of files (like AVI).
This precluding good playback of partial files, and causes really terrible problems with partially damaged MOV files.
Unbelivably large number of different ways to do anything.
An unbelivably huge and complex standard that probably nobody on earth understands entirely.
14 different versions of the standard, and a field in the MOV header to dictate which version of the standard the player should use to read the file.
And finally: patents
If quicktime wasn't so horrible, you certainly wouldn't have ever seen formats like Ogg or MKV.
I can't believe it either...
Windows users have toxoplasma gondii parasite?
As if it's known symptoms weren't bad enough, this clever bug wears down it's host's defenses by compelling them to use Microsoft software...
Not at all. Linux users can play WMV video and audio. As of a few months ago, you don't even need the binary codec DLLs or an x86 system for the large majority of WMV video and audio formats.
The reason that's not openly supported by organizations, of course, is the patent licensing fees, which prevent most distros from including programs like MPlayer to begin with. Since the EU is repeatedly trying to get software patents into law, it would be rather hypocritical for them to suggest programs like MPlayer, wouldn't it?
Linux isn't the issue, it's just the reason it was posted on
The issue is a government that requires you to use commercial software to play. One that uses secret, undocumented file formats (even Real video would be a bad choice, in this regard). etc.
Quicktime, at least sticks with open and standard video/audio codecs, and MP4 container, despite the patent issues.
And if they put a little bit of effort into it, they could use patent-free formats as well.
With appologies to "CryoPenguin" (not "SnoPenguin").
Definately. If an interested party would pick-up Snow, finalize the bitstream, and start adding some performance optimizations for encoding and high-def playback, it could beat-out every other video codec out there. The quality/bitrate is easily better than even h.264, and can scale down to ridiculously low bitrates while being completely watchable.
Nope. SnoPenguin nailed it. Ogg is terribly codec-specific.
MKV is gaining in popularity, partly because it can handle just about any audio or video format, including Vorbis, as well as subtitles, menus, chapters, etc.
Really? Why?
And that reason is???
That wouldn't be true, of course.
The patents on MPEG-1 have long ago expired. It has pretty good quality (better than Theora/VP3) when encoded with a recent implimentation (ie. libavcodec for video, twolame for audio). And more than that, it is by far the most widely compatible format around, supported by just about every video player made in the past several years, on just about every single platform around.
I, however, do. The VP3 codec is hated by just about everyone who knows anything about video.
It has really poor video quality, compared to even much older video codecs.
It is very CPU-intensive to encode.
It's playback performance is horrible. Once you reach resolutions where a full frame can't fit in your CPU cache, you get performance worse than codecs like h.264.
In some 4 years of Theora's development, Xiph hasn't removed any of VP3's limitations, nor added any advantages over the original VP3 codec. Since they've frozen the bitstream, even the potential for them to do any of that has passed...
I was somewhat active in the Theora development process some time ago, but I've long since given it up for dead.
You should pay more attention before you "correct" other people...
The source was linked in the Doom9 thread the
Not a laptop, nor a desktop with CnQ/SpeedStep...
In fact it is a 4 year-old Athlon XP, in a motherboard that doesn't even support S2K.
GNU: Large African antelopes. Also called wildebeest.
RMS: Root Mean Square.
GPL: Game Programming Library
Thank you and goodnight!
I don't specifically know "how". What I do know is that it's a fact, and quite easy to demonstrate.
Start a long-running CPU-intensive program (my preference is mencoder) at a low priority, and monitor the CPU tempurature. After you've given it plenty of time to cool down (a day or more if you like) start the program at the default or higher priority, and you'll see the tempurature is significantly higher.
Somehow I don't think that would meet the standard for evidence...
You need to measure tiny variations in current caused by one device, mixed in with the haystack of all the other electric devices in your house... Most of which can vary significantly from moment to moment.
Not necessarily.
If you have your CPU-intensive app running at a low priority, and TOR running at a higher priority, then your CPU will become slightly hotter when TOR is doing heavy processing.
It may make it much harder to detect than it already is, but there you go.
Because they can?
It's not like market forces broke-up AT&T. It was the federal government. Now, it's the federal government giving them a pass, and allowing unlimited mergers.
If GM could buy-up Ford and Chrysler, you can bet they'd jump at the chance... Not because there's any good reason for a monopoly, but because getting rid of your competitors is always profitable.
GMail is pretty simple. They provide POP3 access, so you can download it directly with your program of choice (check the box to keep it on the server, obviously).
UPLOADING it to Gmail in the event of a crash would be decidedly more difficult, though. That's good enough for me, though.