1641
Chrome not proceeding with Web Integrity API deemed by many to be DRM (9to5google.com)
submitted 2 years ago by to c/technology@lemmy.world
240 comments fedilink hide all child comments
 

The Chrome team says they're not going to pursue Web Integrity but...

it is piloting a new Android WebView Media Integrity API that’s “narrowly scoped, and only targets WebViews embedded in apps.”

They say its because the team "heard your feedback." I'm sure that's true, and I can wildly speculate that all the current anti-trust attention was a factor too.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 years ago (1 child)

you had to purchase TCP/IP for it from third parties back then.

LOL WAT?!! The precursor to the WinRAR subscription, huh...

And one of the first websites I visited was "the original one" on Tim Barners-Lee's NEXT cube in CERN.

Wow, this is kinda like witnessing the moon landing live, right? That's amazing!

And guess what - there was a network way before the Web. We had chat, "social media" before it was called that, and played online multiplayer games. All without any spam or advertising.

Interesting... Which chat server was this? And what year approximately?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 2 years ago

    Well, the TCP/IP stack we had was not at all like WinRar. You bought a box with a bunch of disks (5.25in) and some thick paperback manuals. The price was about 150$, and installation was tricky. It only worked with a certain set of network cards. But it did work together with the other network stack back then: Novell Netware, which did the majority of work in corporate networks back then.

    The chat had a bit different structure back then. Messages went from client to client, and the "TALK" server only did coordination. There was a system, IIRC it was called NICKSERV or something where you globally registered your nickname.

    I was not only watching things back then. I wrote a number of tools that made the rounds back then, a client for such a multiplayer online game that worked both in a text terminal and with a GUI, and a non-interactive NNTP (USENET) client that allowed access to our equivalent of the fediverse remotely. And I even wrote our companies first SMTP (email) gateway to the internet back then. Not "installed" or "configured" - wrote.

  • permalink
  • fedilink
  • source
  • parent