Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "David Bray, PhD" <david.a.bray@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] The growing challenges of discerning authentic vs. inauthentic information and identity
Date: Tue, 9 Jan 2024 15:59:14 -0700	[thread overview]
Message-ID: <CA+aeVP_=7vUiUdZTa=JPoT_=a3sm_NWsdX+7Ac=j3SfBztRY+g@mail.gmail.com> (raw)
In-Reply-To: <8c29e360-7cbc-4b67-a669-640fdc6e6fa6@3kitty.org>

[-- Attachment #1: Type: text/plain, Size: 4807 bytes --]

Also on history let’s consider the 1890’s and how both Pulitzer and Hearst
made their money with sensationalist headlines that may not have matched
the actual facts of the scenario. The U.S. ended up going to war with Spain
over a disinformation event - Remember the Maine!

The Congress was also slightly more polarized at the time than it is now.
What if we’re seeing a Second Gilded Age?


On Tue, Jan 9, 2024 at 13:00 Jack Haverty via Nnagain <
nnagain@lists.bufferbloat.net> wrote:

> IMHO, similar issues of judgement and trust have come up in the past, and
> it might be worth researching the history.
>
> In the context of the Web, during the 90s there was a similar concern
> about categorizing content available on the Internet.   The issue at the
> time was providing mechanisms to protect children from pornography.  But
> today's issues of truth and misinformation are very similar -- e.g., you
> might categorize an inaccurate news post as "pornographic".
>
> I suggest looking at some work from the 90s.  At the time, I was working
> at Oracle as "Internet Architect", and served as corporate representative
> to W3C (see https://www.w3.org/ ).  Thw W3C group, led by Tim
> Berners-Lee, was intensely involved in setting technical standards for the
> Web.
>
> A project was formed call PICS - Platform for Internet Content Selection.
> Essentially it created mechanisms to add metadata to existing content on
> the Web, and use it to filter content for end users.
>
> See https://www.w3.org/PICS/ for the history.  PICS is now obsolete and
> was replaced by something called POWDER - see
> https://www.w3.org/2007/powder/
>
> I wasn't involved in POWDER, which occurred after my involvement with W3C
> ended.  But I was very involved in the creation of PICS.
>
> The main idea of PICS was to enable the creation of "rating schemes" to
> categorize content.  Since the focus was on pornography, one likely rating
> scheme was the classical G/R/X ratings popular at the time for
> characterizing movies.   But anyone, or any group, could define a rating
> scheme to suit their views.
>
> Having selected a rating scheme they liked, any group, or individual,
> could assign ratings to specific content.  Perhaps you think that movie is
> "R", but I think it's "X".   As a judge once noted - "I can't define it,
> but I know it when I see it".   Opinions can of course differ.
>
> Ratings were to be kept in one or more databases, accessible on the
> Internet to anyone.  Content could be identified by a URL, or perhaps a
> unique cryptographic "hash" of the content itself, in case it was moved.
> Each record would contain 4 items - the identity of the content, the
> identity of the rating scheme used, the identity of the person or group
> making the rating, and the rating which they assigned.  Such technology was
> easily within the capabilities of databases even then.
>
> On the "consumer" side, applications (e.g., browsers) would have settings
> that could be applied to indicate which rating system was to be used, which
> groups or persons making ratings were to be trusted, and what ratings of
> content would be actually viewable by the human end user.
>
> The idea was that various groups (content creators, reviewers, religious
> groups, community activists, etc.) would define their preferred rating
> scheme and then assign ratings, at least to content they deemed
> objectionable.
>
> End users, e.g., parents, could then set up their children's web browsers
> to use the rating scheme of whichever group(s) they trusted to make
> "correct" ratings, and set their children's browsers appropriately to
> restrict the content they could see.   A content consumer simply selects
> the rating service they trust.
>
> It seems straightforward how a similar mechanism might be applied to
> instead rate accuracy of Internet content, and allow consumers to choose
> which, if any, ratings are applied to filter the information they see,
> based on who they trust to make such judgements.
>
> PICS was actually implemented in popular browser software.   But, as far
> as I know, no group ever designed their preferred rating scheme, or
> actually assigned ratings to any content then available on the Internet.
> The mechanisms were there.   But apparently no one used them.   The loud
> voices of "Something has to be done!" didn't actually themselves do
> anything.
>
> Even if PICS/POWDER isn't appropriate for handling misinformation, an
> analysis of why it failed to be used might be revealing.
>
>
> Jack Haverty
>
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>

[-- Attachment #2: Type: text/html, Size: 6228 bytes --]

      parent reply	other threads:[~2024-01-09 22:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+aeVP__FcBG6noaozL7anGYWQ4TR4tvr1jn2sJa8DnzRZNzag@mail.gmail.com>
2024-01-03 14:32 ` David Bray, PhD
2024-01-05  0:18   ` rjmcmahon
2024-01-05  0:42     ` Spencer Sevilla
2024-01-08 20:17   ` Dave Taht
2024-01-08 22:08     ` David Lang
2024-01-09  0:16       ` David Bray, PhD
2024-01-09  2:30         ` David Lang
2024-01-09  2:52           ` David Bray, PhD
2024-01-09  3:12             ` David Lang
2024-01-09 18:23               ` David Bray, PhD
2024-01-09 20:00                 ` Jack Haverty
2024-01-09 20:11                   ` Dick Roy
2024-01-09 22:59                   ` David Bray, PhD [this message]

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.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CA+aeVP_=7vUiUdZTa=JPoT_=a3sm_NWsdX+7Ac=j3SfBztRY+g@mail.gmail.com' \
    --to=david.a.bray@gmail.com \
    --cc=nnagain@lists.bufferbloat.net \
    /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