Cringely On Microsoft Settlement
sandalwood writes: "Robert X Cringley has a new article about the proposed settlement in the Microsoft antitrust case. He includes information on where to write to make your views known (the 'proposed Final Judgement' accepts comments from the public for a period of 60 days after it's been published)."
A darned good idea (imho) would be to force Microsoft to publish their APIs, and restrict them from anti-competitive practices. IBM was doing this 20 years ago in the mainframe world and the European Union slapped them down hard for it.
It's mentioned in this article on gnu.org, but one of the links to the settlement details (the most important part) is broken, the new location for ibm1984ec.html is here.
o/~ Join us now and share the software
Posting AC due to paranoia 8S
/.'ers comment to the DoJ (read, take action and not just wish you could) about this it will crash and burn like a corrupt copy of Windows 95. Read the Article, it does have some instructions at on where to go from here for the commonfolk. Also, a non-partisan board is a Good Thing(tm) in this whole mess.
MSFT is lobbying HARD on this to get this settlement through cause they know they will come out smelling like roses in the end, but with the growing awareness of the language of the settlement, it seems highly unlikely that it will breeze through. If enough people like
Then again, I am just preaching to the choir on this, right?
Is this legal FUD practiced by both sides of this case?
My solution? Require Microsoft to develop its own technology without outside help for 5 years. They can't acquire technology, buy companies or lease patents. See how long they last...
Strange women lying in ponds distributing swords is no basis for a system of government.
Up until the last paragraph, this was a very intelligent comment. Then all of a sudden you start promoting virii and DDOS attacks??? This makes you sound like an immature teenager.
How about instead of breaking the law, and making Open Source hackers look like thugs in the process, we design our own micropayment system, BSD license it, and offer it up as a vastly more secure and powerful solution that passport? Or would that me to "non-31337" for you?
A red flag should go off when a Slashdot poster, or comment acceptor chooses a text with a link identical to one in an earlier story within a certain time period. Sort of a "Warning: Are you sure this hasn't been posted before? Check the story below to be sure this isn't a duplicate." message.
Yes, even the kings of slashdot could benefit from idiot-proof software.
Remember "Bring 'em on"? *sigh
Wonderful idea there. (cough). How about we offer up something as good or better ? Private corporations dominating a space through de facto standards happen because nobody else has stepped up with a Free (as in speech) solution that's better. Some cases to take into consideration:
- 16-bit ISA took off because anyone could build to the IBM PC published spec (essentially free-as-in-beer).
- Then Microchannel flubbed it (must license from IBM).
(Unfortunate footnote -- for 32-bit slots, VESA came along, and was destroyed by Intel's PCI when they slaughtered their competition in the PC chipset market.)So instead of proposing that people DDoS Passport sites, maybe we need to make ubiquitous a better solution that's published and freely implementable. Microsoft did lose out on the browser encryption fight (shttp vs https) and SSLeay / OpenSSL provided free reference implementations that let people use encryption without having to play with the big monopolies (um, except for Verisign). We can come up with a system that delivers Passport / .NET's functionality too.
o/~ Join us now and share the software