Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: Microsoft Dirty Tricks Compendium

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

____/ Linonut on Saturday 24 May 2008 15:26 : \____

>    http://www.grokdoc.net/index.php/Dirty_Tricks_history
> 
> Contents
> 
>     * 1 A History of MS' Standards 'Dirty Tricks'
>           o 1.1 Standards Bodies and Windows APIs
>           o 1.2 Standards covered
>     * 2 MS OfficeOpenXML
>           o 2.1 Licensing
>           o 2.2 (In-)Compatibility with other standards
>           o 2.3 Office2007 implementation
>           o 2.4 Alternative Implementations
>           o 2.5 Summary and epilogue
>     * 3 MPEG
>     * 4 OpenDoc
>     * 5 HTML and WWW
>     * 6 Kerberos standard with proprietary extension
>     * 7 The Sender ID flap
>     * 8 Ecmascript
>     * 9 RTF
>     * 10 LDAP
>     * 11 CIFS
>     * 12 OpenGL
>     * 13 C#/CLI
>     * 14 .NET
>     * 15 Java
>     * 16 ODBC API
>     * 17 ActiveX standardization
>     * 18 NTP, the Network Time Protocol
>     * 19 RIFF (WAV)
>     * 20 VFAT
>     * 21 C++
>     * 22 RC4 encryption
>     * 23 Rdesktop
>     * 24 Boot sector pain
>     * 25 PNG
> 
> Not sure if it is truly comprehensive, though.  For instance, I see nothing
> in the above list about
> 
>    *  Violating non-disclosure agreements
>    *  Buying out the competition and killing them
>    *  Using brain-drain on the competition
>    *  Slinging mud, astroturfing, channel-stuffing, stove-piping, and
>       legal threats (direct, via press release, and by proxy)
>    *  Strong-arming vendors
>    *  Cooking their accounting numbers (pretty standard for all business,
>       I suppose)
> 
> But, I suppose Grok's list is a technical list.  So here's another:
> 
>    http://www.groklaw.net/staticpages/index.php?page=2005010107100653
> 
>    Microsoft Litigation.
> 
> Teach me Billy!  Teach me!

How can Microsoft defend itself? Oh, well... say that "everyone's doing it."

Accused Microsoft of AstroTurfing. Microsoft's response? Diversion. Accuse
someone, spread more libel.

I'm glad the resources above show so well what 'company' we're dealing with.
It's a serial killer. At the moment I'm compiling a list of OOXML corruptions.
So far today I've covered nations from A to C (still over 20 letters to go). I
got about 200 links for just 3 letters! Microsoft left quite a trail of
corruption, with OOXML /alone/. It left us with another world-wide treasure
trove of corruption -- of ammunition against its behaviour.

- -- 
                ~~ Best of wishes

Roy S. Schestowitz      | Othello for Win32/Linux: http://othellomaster.com
http://Schestowitz.com  | Free as in Free Beer |  PGP-Key: 0x74572E8E
Cpu(s): 24.4%us,  3.6%sy,  1.0%ni, 66.5%id,  4.1%wa,  0.3%hi,  0.1%si,  0.0%st
      http://iuron.com - semantic engine to gather information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIOGoWU4xAY3RXLo4RAgNFAJ4kdmwZl1+r5gX+EKJDBKSv8rUDuQCfTk9L
GJmjk8hLV+aLJ/H7i5kq0vY=
=VbKg
-----END PGP SIGNATURE-----

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index