RIAA, yada yada yada, bad business model, yada yada, needs to shift their business paradigm, yada yada yada, metallica sucks, yada yada, hot grits, yada yada.
And still these "eevul corporations plot against mp3!!!!!!11" type articles pull in almost 300 posts every time. Sigh.
Please, don't say "X-Windows", "XWindows" or such. It's not the correct name for the windowing system that XFree86 is compatible to. The proper name for it is either X11, X, X Window System, X Version 11 or X Window System, Version 11. See the man page (man X) if you don't believe me.
Speaking of it as "X-Windows" is like calling the linux kernel "linux32.dll".
There are plenty of codecs that are better than mp3, but mp3 has taken such a hold (mindshare) it'll probably take a whole shift in the digital-audio format to remove it.
BZZZZT, wrong, but thank you for playing. MPEG Audio layer 3 (MP3) is a format, not a codec. LAME is an encoder. mpg123 (and others) are decoders. Put an encoder and a decoder together, and you have a codec.
(This is not a flame. More like a gentle correction.)
They're just forgetting about glibc2. If everyone compiles their evil binary-only crud for glibc2, then modern linux installations can run the aforementioned binaries.
Your carefully laid out, exceptionally civilized points have convinced me of the Holy Truth of the American Way and that the Commies who Rule China (and most of Europe and Australia, too!) must be nuked, along with the Stinking Democrats who want to ban our Guns!!!!!!!!111!!!
Like a wise person (whose name I have forgotten) once said somewhere, "The only intuitive interface is the nipple. Everything else is learned."
Seriously, the problem that wind'ohs users who decide to install linux (or any other "alternative" OS, for that matter) have is that they expect it to be exactly like the (piece of shit, IMO) OS that they used before. No, they don't want to learn yet another user interface or read any documents without shiny 32-bit images or fluffy suitspeak, since they already know this computer stuff, roight? They simply don't want to wrap their tiny little brains around the fact that linux is not windows. And never will be, if I can help it.
I wonder, was the injunction for DeCSS, specifically, or also for code derived from the algorithm presented in the source of DeCSS? I mean the css-auth package by the LiVID developers...
As far as I know, porting DirectoryOpus 4 would be quite a task - perhaps difficult enough to just give up and put the effort into improving gentoo, a DOpus 4 workalike in GTK. (sorry, no link.) Amiga software (especially in cases like this) tends to rely heavily on the system; some programs even use the doubly linked lists provided by the exec.library instead of having their own implementation...
Anyway, DirectoryOpus 4 used to be a commercial product, so I wouldn't expect much of the source:-)
Umm.... couldn't everyone just lie about their name to the browser that they're using? Although some systems might take the name information from somewhere else, at least GNU and BSD users should be pretty safe.
Is it still as brittle as an eggshell? The last I tried BeOS (on a friend's machine, a few years back) it crashed at the slightest software malfunction. Not that there were many in the GNU tools that we tried, but it was still a bitch to reboot the system every 2 hours.
Which kind of reminds me of the AmigaOS; a great system, but a major problem for software development was that the system bit dirt every single time that one dereferenced a NULL pointer...
There's a difference between symmetric key length and asymmetric key length. For example, 64 bits in RC5 seems pretty damn uncrackable, but 64 bits in an asymmetric cipher (ElGamal, or RSA) is near useless.
By the way, is there already a public cipher algorithm that uses keys longer than 256 bits (twofish and some others)? Not counting RC4, which has basically infinite maximum key length, with restrictions IIRC.
Well, I guess that we'll just have to implement a known codec in a country that doesn't have a patent office as stupid as the merkin one.
It's been done before. There's LAME and there's BladeEnc; both would be patent licensing violations in the US, but since they are mostly distributed in non-US and non-Germany countries, there's little that FhG can do except sending bark letters.
RIAA, yada yada yada, bad business model, yada yada, needs to shift their business paradigm, yada yada yada, metallica sucks, yada yada, hot grits, yada yada.
And still these "eevul corporations plot against mp3!!!!!!11" type articles pull in almost 300 posts every time. Sigh.
Psst... OpenNAP. The canonical luse32 client won't support unofficial servers, but that's not my problem.
Oh, so you don't need to check the capability bits (or what have you) for multitexturing et cetera before using said feature of D3D, eh?
Get out. Get out and grow up.
Please, don't say "X-Windows", "XWindows" or such. It's not the correct name for the windowing system that XFree86 is compatible to. The proper name for it is either X11, X, X Window System, X Version 11 or X Window System, Version 11. See the man page (man X) if you don't believe me.
Speaking of it as "X-Windows" is like calling the linux kernel "linux32.dll".
And to keep slaves, and tread down on people who weren't born into the middle or upper class.
Bugger off, trollboy.
BZZZZT, wrong, but thank you for playing.
MPEG Audio layer 3 (MP3) is a format, not a codec. LAME is an encoder. mpg123 (and others) are decoders. Put an encoder and a decoder together, and you have a codec.
(This is not a flame. More like a gentle correction.)
Yet another iteration of "It'll be back, and it'll blow your socks off, you stupid PC l00zurz!!!!!", eh? No thanks.
As if there weren't enough noise on comp.sys.amiga.advocacy already :-)
They're just forgetting about glibc2. If everyone compiles their evil binary-only crud for glibc2, then modern linux installations can run the aforementioned binaries.
How typical of ZDNet.
Oh yeah, as if news programs (on TV, I mean) didn't do that either.
One controversial (i.e. completely clueless) link, and we have about 400 comments. That's the real slashdot effect...
Death of UNIX predicted! Film at 11.
Your carefully laid out, exceptionally civilized points have convinced me of the Holy Truth of the American Way and that the Commies who Rule China (and most of Europe and Australia, too!) must be nuked, along with the Stinking Democrats who want to ban our Guns!!!!!!!!111!!!
Congratulations.
Like a wise person (whose name I have forgotten) once said somewhere, "The only intuitive interface is the nipple. Everything else is learned."
Seriously, the problem that wind'ohs users who decide to install linux (or any other "alternative" OS, for that matter) have is that they expect it to be exactly like the (piece of shit, IMO) OS that they used before. No, they don't want to learn yet another user interface or read any documents without shiny 32-bit images or fluffy suitspeak, since they already know this computer stuff, roight? They simply don't want to wrap their tiny little brains around the fact that linux is not windows. And never will be, if I can help it.
Only if they've got PPC-compatible CPUs :-)
Where are the Debian packages?
Not what I'd expect from Sterling. Still, the idea of shooting lawyers on sight sounds kind of neat :-)
ObFilthyAmerikaners: The writer really needs to look up "communis[mt]" in the dictionary.
Death of USENET predicted! Film at 11.
Also, go take a look at Sluggy freelance. Bun-bun also has some information on what to do abo^Wto telemarketers.
I wonder, was the injunction for DeCSS, specifically, or also for code derived from the algorithm presented in the source of DeCSS? I mean the css-auth package by the LiVID developers...
As far as I know, porting DirectoryOpus 4 would be quite a task - perhaps difficult enough to just give up and put the effort into improving gentoo, a DOpus 4 workalike in GTK. (sorry, no link.) Amiga software (especially in cases like this) tends to rely heavily on the system; some programs even use the doubly linked lists provided by the exec.library instead of having their own implementation...
Anyway, DirectoryOpus 4 used to be a commercial product, so I wouldn't expect much of the source :-)
Umm.... couldn't everyone just lie about their name to the browser that they're using? Although some systems might take the name information from somewhere else, at least GNU and BSD users should be pretty safe.
See also this document for some FSF propaganda on the subject.
Is it still as brittle as an eggshell? The last I tried BeOS (on a friend's machine, a few years back) it crashed at the slightest software malfunction. Not that there were many in the GNU tools that we tried, but it was still a bitch to reboot the system every 2 hours.
Which kind of reminds me of the AmigaOS; a great system, but a major problem for software development was that the system bit dirt every single time that one dereferenced a NULL pointer...
There's a difference between symmetric key length and asymmetric key length. For example, 64 bits in RC5 seems pretty damn uncrackable, but 64 bits in an asymmetric cipher (ElGamal, or RSA) is near useless.
By the way, is there already a public cipher algorithm that uses keys longer than 256 bits (twofish and some others)? Not counting RC4, which has basically infinite maximum key length, with restrictions IIRC.
Well, I guess that we'll just have to implement a known codec in a country that doesn't have a patent office as stupid as the merkin one.
It's been done before. There's LAME and there's BladeEnc; both would be patent licensing violations in the US, but since they are mostly distributed in non-US and non-Germany countries, there's little that FhG can do except sending bark letters.