LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "Lars Noodén" <lars.nooden@gmx.com>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Wikipedia extolled as an aide for getting history correct
Date: Sat, 18 Jun 2022 10:12:55 +0300	[thread overview]
Message-ID: <7eca45c2-1036-cbf7-01ea-c84fc882355f@gmx.com> (raw)
In-Reply-To: <2022.06.17.0637.05182@afu.wta.att.ne.jp>

On 6/17/22 00:46, Akira Urushibata wrote:
[snip]
> Has anybody been monitoring the Wikipedia article on the "Linux"
> operating system?  As stated above I notice that it is constantly
> evolving.  I see the need to examine the article and the "GNU/Linux"
> naming ordeal from an objective perspective.

Back in the day, I and others at the now defunct OpenDocument Fellowship
did try to follow the various Wikipedia articles on Open Standards and
in particular the OpenDocument Format¹ and even related, non-standard
formats like OOXML².

I haven't looked at those particular pages for very many years but when
I last did there was still an ongoing fight between those trying to keep
the articles concise and filled with accurate information and those
working to delete them or obfuscate the information.  I presume the
latter were paid at least indirectly by Microsoft since they were so
active and persistent.

The tactics they used consistently at that time were:

1. saturate the open standards articles with excessive verbiage
2. diffuse the concepts and reword concepts as vaguely as possible
3. split the then long article into multiple pages
4. remove key concepts and information from the original article
5. confuse the material in the subarticles
6. shrink the subarticles to almost nothing for "precision"
7. call for deletion of the subsequently short subarticles

In that way they were able to remove, delete, or obfuscate a lot of key
information about the format and about open standards in general.

Remember, if open file formats³ are so well supported that programs can
be used interchangeably, then that aspect of vendor lock-in would
completely go away, along with most non-political barriers to FOSS
applications and operating systems on the desktop.

tldr; I would expect that these days you would have to look out for the
abuse of similar tactics, but perhaps more refined and subtle, in
regards to the relevant Wikipedia articles on software and operating
systems.

/Lars

¹ Standardized as ISO/IEC 26300
	https://www.oasis-open.org/committees/office/
	https://www.iso.org/standard/66363.html
	https://www.loc.gov/preservation/digital/formats/fdd/fdd000247.shtml

² Which, to this day, no programs actually use.  None.

³ One that is:
	1. maintained by an independent non-profit
	2. published and available free-of-charge
	3. usable royalty-free
	4. has no constraints on re-use

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  parent reply	other threads:[~2022-06-18 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 21:46 Wikipedia extolled as an aide for getting history correct Akira Urushibata
2022-06-17 22:36 ` Greg Farough
2022-06-18  1:17   ` Davis Remmel via libreplanet-discuss
2022-06-18  6:06 ` J Leslie Turriff
2022-07-18  6:44   ` Ade Malsasa Akbar
2022-06-18  7:12 ` Lars Noodén [this message]
2022-06-21  2:57 ` Alexandre Oliva
2022-06-21 23:07   ` J.B. Nicholson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7eca45c2-1036-cbf7-01ea-c84fc882355f@gmx.com \
    --to=lars.nooden@gmx.com \
    --cc=libreplanet-discuss@libreplanet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).