As well as with the original article. First thing - you can't really say "few flaws have been fixed" when the original article (and the post blurb) specifically say that no fixed flaws where actually found in the testing sample.
On the other hand, the statistics used by Rob Weir are shoddy according to my local statistics semi-expert (my girlfriend who finished 2nd year BA stats A. with a perfect 100 score). Specifically his sample is incredibly small: 25 random pages out of a random selection of 200 pages out of 5220 pages of the original standard document, out of 6045 pages actually in the original document (not the amended document), of which he doesn't know how many defects where actually reported against each page (we know how many were reported totally, but we don't know what is their percentage in the first sampling or subsequent sampling), and as Rob Weir found new defects that were not reported to Microsoft in time for the BRM, he has no idea what is the actual density of (pre-BRM) reported defects in the total "defect population" (defects discovered before BRM, after BRM and defects that are yet undiscovered).
As such a confidence interval of 1.5% +-3% (i.e. at worst 4.5%, which is not what the post reports) seems highly suspect. To clarify for non-statistics students, a confidence interval of 1.5% +-3% in a result of 0 hits out of a random sample, means that Rob Weir is at worst 95.5% confident and at best 100% confident that there were no defects addressed by Microsoft.
This is awfully presumptuous, even if its Microsoft that we are talking about.
Finally, the theme. Well, he's got me there, Fedora does win in that respect. I don't mind the Ubuntu brown, but they aren't doing something nice enough with it so far.
The fedora 8 Nudoka (or however they call it) is the ugliest piece of visual cr@p I've seen as default on a desktop OS in the last 5 years. The Ubuntu Human is boring, low-contrast, jarring on most applications and even conflicts with the Human icon theme's strong colors - but it is tons better then the Fedora default theme which looks like it was drawn by a 10 years old. The first thing I did after installing Fedora 8 is to go back to clearlooks which was brilliant when it was created and time has not made it worse. The theme is not the only problem - a common complaint I get is about the default wallpapers which looks like somebody tried to do something nice and gave up in the middle of it. Even the icons suck - it looks like it supposed to be a default Tango theme, but it has so many missing icons that are drawn instead using the stock GNOME icons which haven't been updated in several years.
I like Fedora - its the default desktop on all Linux stations at my office, and mostly because I've put it there. But I'm using it despite its visual appearance and not because of it. The main reason why Fedora is still a better desktop OS for me any many other users is that Ubuntu can't handle a corporate environment - it doesn't do remote authentication or authorization, doesn't have kerberised services, has no support for central management facilities and even the minimal SMB browsing it can do fails on a corporate network. If you are deploying Linux desktops in a corporate environment, you mostly have two options - Fedora (and don't get me started on RHEL) or SuSE. Ubuntu is hype and all, but can't play nicely with other computers and 8.04 doesn't look like its going to solve it.
My favorite non bloatware software is the Amarok media player. Yes - it is 32MB (installed) and has everything but the kitchen sink, but all of its features are useful (I think I've used every single one of them including wikipedia support)
Have you used the Microsoft ODF converter ?
I have it installed at work on a number of systems and its a fscking pain in the !@#$. Its rather complex to install (you need to download and install 3 dependencies, and then customize word's toolbar by hand to include the functionality), integrates badly (doesn't assign ODT file extension to word, and doesn't offer ODT support from word's standard file open/save - you need to choose a different menu option for "export" and "import"), does a very bad job of preserving styles even for very simple things like point size and alignment, and you already noted its biggest problem - its hard to discover that it even exists. I also got the ODF converter to only work for Word with ODT - can't get it to handle spreadsheets or presentations
Sun's plugin, while notably also supports only ODT properly at this time, solves most of these problems: it is a single download, uses the standard open/save dialogs and supposedly (haven't tried it yet) works very well by skipping the part where ODF files are being filtered through the inferior OOXML format in Microsoft's ODF-converter.
From reading the article, its clear that the summary above is quite misleading - Microsoft will not "support" ODF in the sense that they will offer a version of their office productivity suite which allows for opening or saving ODF files.
Microsoft will "support" ODF in the sense that they will not contest the standardization of ODF as an ISO/IEC/ANSI standard if ISO/IEC also accepts OOXML as an international standard. Nobody at any point said anything about Microsoft releasing software that understands ODF.
According to Mordechai Vanunu, the Israeli nuclear whistle blower - as quoted by the Sunday Times - Israel had laser enrichment technology, in actual production use, at the early 1980s. http://en.wikipedia.org/wiki/Mordechai_Vanunu
He is running a linux livecd under QEmu for the screen saver (and hardcoding the iso image file name in the binary). Running coLinux would be tons neater.
Not sure if we are seeing the same site. The site, though ugly and features incredibly poor color choice and CSS effects, contains a several screens full of George Harrison biography, and less then a couple of dozens links, almost all of which point to other pages on the site and appear to be very George Harrison related. {It also has an funny geo-ip feature which knows my location. neat, but fails to take account the fact that most countries don't have internal states}
All in all, not my first idea of how to build a spamming web site, unless by spamming you mean "Inform the whole world on the life of one whose name was George Harrison".
Also, while the site is currently no. 10 (last on the first page) of the google search you did, his location there is probably not thanks to his "beatles-beatles" posting in slashdot (unless Google magically "knows" that George Harrison is a member of the Beatles, which I doubt).
Given that all of the "beatles-beatles" links are to that George Harrison web site, except for one which is for an SEO site - I think that this guy is just a George Harrison fan trying to promote his web site using his slashdot posting.
Given the fact that I couldn't locate his site in the first 10 pages of a google search for "beatles", I'd say he does a botch-up job of that and we can safely ignore him.
This is a storm in a teapot (or how ever you say that).
I'm going to pull out the crossover office argument again: for the sake of the argument, lets assume that someone comes and ports kdelibs to a different architecture - ahmm.. lets say to native Win32 (instead of the current kdelibs-win32 effort which depends on the qt-win32 port, because its easier).
So now I can write a software that links against kdelibs, which might link against either a GPLed version of Qt, a commercial Qt or the Win32 API - and its done in run time so I can be sure.
Stallman would say that my software would have to be GPLed, but he'll say that anyway, regardless of what I use - so lets disregard him. Most law abiding people (and lawyers- IANAL, but I consulted with one) would say that the only license you have to respect is kdelibs which is LGPL.
I can't know for sure what kdelibs links to and I don't much care - its not my problem. When it uses Win32 or a commercial Qt (which BTW - I can't distinguish between that and a GPLed Qt), I don't have any additional license requirements other then kdelibs'. So saying that since its possible that my software (which I distribute only in binary form) will sometimes be linked with a GPLed software, then I must GPL it - is utter bullshit. Its like saying that Microsoft needs to GPL MS-Office because it might link with wine which is GPLed.
I'm just taking it a bit further - I don't need to have a competing "non-encumbered" backend implementation for that to happen (though I already have it: the commercial Qt library) - as long as I can't tell for sure what I link against (even in the future), then I need only satisfy what licenses I can tell for sure are involved, which is just the LGPL in this case.
P.S.
Copyright law (which has nothing to do with any of this, BTW) IS all about interfaces and nothing at all about dynamic/static/whatever linking.
We are not arguing here about copyright law, but about the GPL license which has nothing to do with copyright law. In effect, the GPL and copyright law are mutually exclusive - you can either be covered under the GPL, in which case you can obey the GPL and copy interfaces and code; or you can be covered under copyright law, in which case you are not allowed to copy anything.
Right, Qt is GPL/QPL so to develop against Qt you must license as GPL or buy a TrollTech license.
But! kdelibs are LGPL! So if you are only using KDE interfaces, you may license as anything you want!
I don't know for sure, but I think this is intentional - if you want to develop cross platform apps, then you buy a Qt license from TrollTech (Although I would argue that neither Qt nor GTK+ is right for the job - instead choose FLTK or Wx). If you want to strengthen the Linux desktop (specifically the KDE part of it), then you can license it however you like w/o paying anyone anything.
For example which would you think is faster. A) Sending a Bitmap of a desktop at 1600x1200 or B) Sending a compressed XAML based representation with both Vector and Raster information about a 1600x1200 desktop.
Here is a hint, one is 1.3mb at minimum compressed, the other could be anywhere from 30kb to 1mb at the max.
Probably (A). You go and make the extra effort to compress the XML, why don't you compress the image ? Under most conditions (this is desktop, not live pictures - most of the screen is blue:-) ), even lossless compression of the bitmap would make it on the order of several dozens of KBs.
Your XAML OTOH would need to have some really funky encoding where most stuff is cut into raster bits that get encoded in an XML friendly way (i.e. very bloated) and some stuff which can be presented in vectors (what exactly ? I can't find anything on my desktop which was originally vector, especially if I exclude the content of application windows which are self drawn) which are still big as they are XML encoded. I would hazard an educated guess that apples to apples, your uncompressed XAML data is 2 to 3 times bigger then the uncompressed original image (after compression they might be on the same order of size) and takes between 5 to 10 times more processing power to parse and understand.
Like I said, completely useless except as hype pressure points ("we're better then linux because our display code is XML powered!").
You actually said "simple and efficient" and "XML" in the same sentence. I would have shot myself after doing that.
The current trend of "Its XML so its better" is really annoying. Specifically, everything which is changed to and XML based protocol becomes bloated and takes a lot more bandwidth to transmit and more processing power to read and use. It makes sense in some areas, such as certain internet protocols, but its makes no sense whatsoever in high-bandwidth/high-speed applications such as drawing to the screen.
So, as to your questions, Microsoft is evil and Apple's Quartz is tons better.
Not really. The GSM gateway discussed is not a GSM cell - its just another GSM client.
You can of course call it and be connected to your local PBX - but you'd do so using some GSM operator's cells, which is hardly what the post asked.
You seem to be confusing GSM with peer-to-peer radio. I know peer-to-peer is all the rage now, but please, do get a clue.
Can you be any more stupid ? * Mandriva has a lively market share. They even got Wallmart to sell PCs pre-installed with their OS - had RedHat managed to do this? * Winix is an old (and dumb) rumor which has never had any sort of credability - so stop being an ass. * Project Marklar is Apple's (!!) x86 OS.
And make up your mind already ? either Microsoft will dump NT for BSD or for Linux , they can't have both dogs by the tail as your dumb add post suggests.
kde-cygwin site lists all of their releases as "beta" which in my book translates to: "not production quality".
In addition I tested KDE for Win32, it crashed often. This might or might not be related to the quality of the Qt port but definetly does not reflect well on the KDE on Cygwin project (not that I blame them - its a hell of a lot of work and not many people to do it)
It doesn't matter whether they allow Qt to run GPLed on windows or not - by releasing a GPLed version of Qt they are specifically allowing it to be modified and redistributed under the terms of the GPL.
One possible modification is porting Qt to run on MS-Windows. so I can get Qt/X11, port it to Win32 (as the kde-cygwin project on sf.net do) and release it under the GPL. Other people can now use this version to develop and distribute Qt based application on Win32 - but again only using the GPL. So even given that case (and Qt from kde-cygwin is nowhere near production quality) I can still not distribute commercial non-GPLed software for Win32. I can however make in-house, not for distribution Win32 software based on Qt - something that wasn't available earlier.
The problem is that doing the Qt/X11 to Win32 port is hard time consuming work which has to be done (to some extent) for each new release of Qt - so its not much of a threat to Trolltech buisness model. Still its a welcome change and might facilitate faster adoption of Qt in the MS-Windows world, which is a "Good Thing"(tm)
This survey surveyed only residents of the USA, right ? so they can't really say "Internet Useres" when they only questioned users from one country. Last time I checked, the Internet was this kind of global network thingy that people from all over the world could use.
The survey results should say: 80% of Americans are dumb. well - gee, its a HUGE surprise, I never would have guessed! thanks for letting us know.
Now can we please get on with our peaceful lives, outside of the US of A, where people actually have a clue..
What's important is that DomainKeys signs the content of the email itself, so you know not only that this email came from an approved sender, but also it wasn't tampered with on the way.
As a result remailers that add content (such as mailing lists) will have to re-sign the messages passing through or remove the DomainKeys headers at all, which is quite a headache.
While software patents are indeed evil, the situation would have been worse has Yahoo not take out a patent on the algorithm.
Being a highly visible algorithm, its quite likely that has it not been patented already, someone (for example, a large software corporation, hint hint) would just go ahead and patent Yahoo's DomainKeys instead - or maybe just something similar enough that will be called, maybe, "Authenticated Sender Identification". US Patent office officials, being dumb enough or greesed well enough will just pass it w/o due examination and then said corporation can just go ahead and sue everyone deploying a mail server with Domain Keys!
Now, of course the best solution would be to have software algorithms not patented (in the US and elsewhere), but that being no more then wishful thinking the next best thing is exactly what Yahoo has done.
And look - its down. Got a bit of slashdotting and IIS presents a funny little 403.9 error (dot 9 ? dont remember seeing that in RFC2616) about "too many users". boo-hoo.
Slashdot Mirror
As well as with the original article. First thing - you can't really say "few flaws have been fixed" when the original article (and the post blurb) specifically say that no fixed flaws where actually found in the testing sample.
On the other hand, the statistics used by Rob Weir are shoddy according to my local statistics semi-expert (my girlfriend who finished 2nd year BA stats A. with a perfect 100 score). Specifically his sample is incredibly small: 25 random pages out of a random selection of 200 pages out of 5220 pages of the original standard document, out of 6045 pages actually in the original document (not the amended document), of which he doesn't know how many defects where actually reported against each page (we know how many were reported totally, but we don't know what is their percentage in the first sampling or subsequent sampling), and as Rob Weir found new defects that were not reported to Microsoft in time for the BRM, he has no idea what is the actual density of (pre-BRM) reported defects in the total "defect population" (defects discovered before BRM, after BRM and defects that are yet undiscovered).
As such a confidence interval of 1.5% +-3% (i.e. at worst 4.5%, which is not what the post reports) seems highly suspect. To clarify for non-statistics students, a confidence interval of 1.5% +-3% in a result of 0 hits out of a random sample, means that Rob Weir is at worst 95.5% confident and at best 100% confident that there were no defects addressed by Microsoft.
This is awfully presumptuous, even if its Microsoft that we are talking about.
The fedora 8 Nudoka (or however they call it) is the ugliest piece of visual cr@p I've seen as default on a desktop OS in the last 5 years. The Ubuntu Human is boring, low-contrast, jarring on most applications and even conflicts with the Human icon theme's strong colors - but it is tons better then the Fedora default theme which looks like it was drawn by a 10 years old. The first thing I did after installing Fedora 8 is to go back to clearlooks which was brilliant when it was created and time has not made it worse. The theme is not the only problem - a common complaint I get is about the default wallpapers which looks like somebody tried to do something nice and gave up in the middle of it. Even the icons suck - it looks like it supposed to be a default Tango theme, but it has so many missing icons that are drawn instead using the stock GNOME icons which haven't been updated in several years.
I like Fedora - its the default desktop on all Linux stations at my office, and mostly because I've put it there. But I'm using it despite its visual appearance and not because of it. The main reason why Fedora is still a better desktop OS for me any many other users is that Ubuntu can't handle a corporate environment - it doesn't do remote authentication or authorization, doesn't have kerberised services, has no support for central management facilities and even the minimal SMB browsing it can do fails on a corporate network. If you are deploying Linux desktops in a corporate environment, you mostly have two options - Fedora (and don't get me started on RHEL) or SuSE. Ubuntu is hype and all, but can't play nicely with other computers and 8.04 doesn't look like its going to solve it.
My favorite non bloatware software is the Amarok media player. Yes - it is 32MB (installed) and has everything but the kitchen sink, but all of its features are useful (I think I've used every single one of them including wikipedia support)
You seem to confuse "spooky action" with time travel. Why is that ?
So, if for example IE7 on Vista takes 10 seconds to do some test, so Opera is 100% faster - taking 0 seconds to do the same test ?!??!
Have you used the Microsoft ODF converter ? I have it installed at work on a number of systems and its a fscking pain in the !@#$. Its rather complex to install (you need to download and install 3 dependencies, and then customize word's toolbar by hand to include the functionality), integrates badly (doesn't assign ODT file extension to word, and doesn't offer ODT support from word's standard file open/save - you need to choose a different menu option for "export" and "import"), does a very bad job of preserving styles even for very simple things like point size and alignment, and you already noted its biggest problem - its hard to discover that it even exists. I also got the ODF converter to only work for Word with ODT - can't get it to handle spreadsheets or presentations Sun's plugin, while notably also supports only ODT properly at this time, solves most of these problems: it is a single download, uses the standard open/save dialogs and supposedly (haven't tried it yet) works very well by skipping the part where ODF files are being filtered through the inferior OOXML format in Microsoft's ODF-converter.
From reading the article, its clear that the summary above is quite misleading - Microsoft will not "support" ODF in the sense that they will offer a version of their office productivity suite which allows for opening or saving ODF files.
Microsoft will "support" ODF in the sense that they will not contest the standardization of ODF as an ISO/IEC/ANSI standard if ISO/IEC also accepts OOXML as an international standard. Nobody at any point said anything about Microsoft releasing software that understands ODF.
According to Mordechai Vanunu, the Israeli nuclear whistle blower - as quoted by the Sunday Times - Israel had laser enrichment technology, in actual production use, at the early 1980s.
http://en.wikipedia.org/wiki/Mordechai_Vanunu
So - nothing new here, move along, move along.
He is running a linux livecd under QEmu for the screen saver (and hardcoding the iso image file name in the binary).
Running coLinux would be tons neater.
Not sure if we are seeing the same site. The site, though ugly and features incredibly poor color choice and CSS effects, contains a several screens full of George Harrison biography, and less then a couple of dozens links, almost all of which point to other pages on the site and appear to be very George Harrison related.
{It also has an funny geo-ip feature which knows my location. neat, but fails to take account the fact that most countries don't have internal states}
All in all, not my first idea of how to build a spamming web site, unless by spamming you mean "Inform the whole world on the life of one whose name was George Harrison".
Also, while the site is currently no. 10 (last on the first page) of the google search you did, his location there is probably not thanks to his "beatles-beatles" posting in slashdot (unless Google magically "knows" that George Harrison is a member of the Beatles, which I doubt).
Given that all of the "beatles-beatles" links are to that George Harrison web site, except for one which is for an SEO site - I think that this guy is just a George Harrison fan trying to promote his web site using his slashdot posting.
Given the fact that I couldn't locate his site in the first 10 pages of a google search for "beatles", I'd say he does a botch-up job of that and we can safely ignore him.
This is a storm in a teapot (or how ever you say that).
I'm going to pull out the crossover office argument again: for the sake of the argument, lets assume that someone comes and ports kdelibs to a different architecture - ahmm.. lets say to native Win32 (instead of the current kdelibs-win32 effort which depends on the qt-win32 port, because its easier). So now I can write a software that links against kdelibs, which might link against either a GPLed version of Qt, a commercial Qt or the Win32 API - and its done in run time so I can be sure. Stallman would say that my software would have to be GPLed, but he'll say that anyway, regardless of what I use - so lets disregard him. Most law abiding people (and lawyers- IANAL, but I consulted with one) would say that the only license you have to respect is kdelibs which is LGPL. I can't know for sure what kdelibs links to and I don't much care - its not my problem. When it uses Win32 or a commercial Qt (which BTW - I can't distinguish between that and a GPLed Qt), I don't have any additional license requirements other then kdelibs'. So saying that since its possible that my software (which I distribute only in binary form) will sometimes be linked with a GPLed software, then I must GPL it - is utter bullshit. Its like saying that Microsoft needs to GPL MS-Office because it might link with wine which is GPLed. I'm just taking it a bit further - I don't need to have a competing "non-encumbered" backend implementation for that to happen (though I already have it: the commercial Qt library) - as long as I can't tell for sure what I link against (even in the future), then I need only satisfy what licenses I can tell for sure are involved, which is just the LGPL in this case. P.S. Copyright law (which has nothing to do with any of this, BTW) IS all about interfaces and nothing at all about dynamic/static/whatever linking. We are not arguing here about copyright law, but about the GPL license which has nothing to do with copyright law. In effect, the GPL and copyright law are mutually exclusive - you can either be covered under the GPL, in which case you can obey the GPL and copy interfaces and code; or you can be covered under copyright law, in which case you are not allowed to copy anything.
Right, Qt is GPL/QPL so to develop against Qt you must license as GPL or buy a TrollTech license.
But! kdelibs are LGPL!
So if you are only using KDE interfaces, you may license as anything you want!
I don't know for sure, but I think this is intentional - if you want to develop cross platform apps, then you buy a Qt license from TrollTech (Although I would argue that neither Qt nor GTK+ is right for the job - instead choose FLTK or Wx). If you want to strengthen the Linux desktop (specifically the KDE part of it), then you can license it however you like w/o paying anyone anything.
Here is a hint, one is 1.3mb at minimum compressed, the other could be anywhere from 30kb to 1mb at the max.
Probably (A). You go and make the extra effort to compress the XML, why don't you compress the image ? Under most conditions (this is desktop, not live pictures - most of the screen is blue :-) ), even lossless compression of the bitmap would make it on the order of several dozens of KBs.
Your XAML OTOH would need to have some really funky encoding where most stuff is cut into raster bits that get encoded in an XML friendly way (i.e. very bloated) and some stuff which can be presented in vectors (what exactly ? I can't find anything on my desktop which was originally vector, especially if I exclude the content of application windows which are self drawn) which are still big as they are XML encoded. I would hazard an educated guess that apples to apples, your uncompressed XAML data is 2 to 3 times bigger then the uncompressed original image (after compression they might be on the same order of size) and takes between 5 to 10 times more processing power to parse and understand.
Like I said, completely useless except as hype pressure points ("we're better then linux because our display code is XML powered!").
You actually said "simple and efficient" and "XML" in the same sentence. I would have shot myself after doing that. The current trend of "Its XML so its better" is really annoying. Specifically, everything which is changed to and XML based protocol becomes bloated and takes a lot more bandwidth to transmit and more processing power to read and use. It makes sense in some areas, such as certain internet protocols, but its makes no sense whatsoever in high-bandwidth/high-speed applications such as drawing to the screen. So, as to your questions, Microsoft is evil and Apple's Quartz is tons better.
Well, the fact is that KDE has a larger user base then GNOME. I wonder why ? maybe because GNOME ("we-what-preferences-you-want") just sucks ?
Not really. The GSM gateway discussed is not a GSM cell - its just another GSM client. You can of course call it and be connected to your local PBX - but you'd do so using some GSM operator's cells, which is hardly what the post asked. You seem to be confusing GSM with peer-to-peer radio. I know peer-to-peer is all the rage now, but please, do get a clue.
Or you could use playfair/hymn/whatever-its-called-now on the itunes download.
Can you be any more stupid ?
* Mandriva has a lively market share. They even got Wallmart to sell PCs pre-installed with their OS - had RedHat managed to do this?
* Winix is an old (and dumb) rumor which has never had any sort of credability - so stop being an ass.
* Project Marklar is Apple's (!!) x86 OS.
And make up your mind already ? either Microsoft will dump NT for BSD or for Linux , they can't have both dogs by the tail as your dumb add post suggests.
kde-cygwin site lists all of their releases as "beta" which in my book translates to: "not production quality". In addition I tested KDE for Win32, it crashed often. This might or might not be related to the quality of the Qt port but definetly does not reflect well on the KDE on Cygwin project (not that I blame them - its a hell of a lot of work and not many people to do it)
It doesn't matter whether they allow Qt to run GPLed on windows or not - by releasing a GPLed version of Qt they are specifically allowing it to be modified and redistributed under the terms of the GPL. One possible modification is porting Qt to run on MS-Windows. so I can get Qt/X11, port it to Win32 (as the kde-cygwin project on sf.net do) and release it under the GPL. Other people can now use this version to develop and distribute Qt based application on Win32 - but again only using the GPL. So even given that case (and Qt from kde-cygwin is nowhere near production quality) I can still not distribute commercial non-GPLed software for Win32. I can however make in-house, not for distribution Win32 software based on Qt - something that wasn't available earlier. The problem is that doing the Qt/X11 to Win32 port is hard time consuming work which has to be done (to some extent) for each new release of Qt - so its not much of a threat to Trolltech buisness model. Still its a welcome change and might facilitate faster adoption of Qt in the MS-Windows world, which is a "Good Thing"(tm)
This survey surveyed only residents of the USA, right ? so they can't really say "Internet Useres" when they only questioned users from one country. Last time I checked, the Internet was this kind of global network thingy that people from all over the world could use. The survey results should say: 80% of Americans are dumb. well - gee, its a HUGE surprise, I never would have guessed! thanks for letting us know. Now can we please get on with our peaceful lives, outside of the US of A, where people actually have a clue..
What's important is that DomainKeys signs the content of the email itself, so you know not only that this email came from an approved sender, but also it wasn't tampered with on the way. As a result remailers that add content (such as mailing lists) will have to re-sign the messages passing through or remove the DomainKeys headers at all, which is quite a headache.
While software patents are indeed evil, the situation would have been worse has Yahoo not take out a patent on the algorithm.
Being a highly visible algorithm, its quite likely that has it not been patented already, someone (for example, a large software corporation, hint hint) would just go ahead and patent Yahoo's DomainKeys instead - or maybe just something similar enough that will be called, maybe, "Authenticated Sender Identification". US Patent office officials, being dumb enough or greesed well enough will just pass it w/o due examination and then said corporation can just go ahead and sue everyone deploying a mail server with Domain Keys!
Now, of course the best solution would be to have software algorithms not patented (in the US and elsewhere), but that being no more then wishful thinking the next best thing is exactly what Yahoo has done.
I myself thank them for that.
And look - its down. Got a bit of slashdotting and IIS presents a funny little 403.9 error (dot 9 ? dont remember seeing that in RFC2616) about "too many users". boo-hoo.