Chrome not proceeding with Web Integrity API deemed by many to be DRM - eviltoast

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.

  • Treczoks@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year 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.