The World Wide Web Consortium’s decision to keep votes about DRM secret and that it censured the EFF for...

The World Wide Web Consortium’s decision to keep votes about DRM secret and that it censured the EFF for “disclosing even vague sense of a vote” raises concerns.

By Brian Faggioli Bryan Lunduke

Other urls found in this thread:

en.wikipedia.org/wiki/Tim_berners-lee
archive.is/yRmty
opisafagg.ot/
web.archive.org/web/20170919093345/https://boingboing.net/2017/07/07/eschatology-watch.html
web.archive.org/web/20170919093345/
boingboing.net/2017/07/07/eschatology-watch.html
archive.is/2017.09.19-134541/https://8ch.net/tech/res/795293.html
twitter.com/NSFWRedditImage

The EFF disagrees with W3C claims

Update: W3C press conference, Monday, Sept. 18, 9 a.m. EST

Is there anything we can do to stop these motherfuckers?

More confirmation that the web is cancer.

Tim Berners-Lee is a fuckhole, too. He's a pseudo-intellectual dimwit who lucked into a position of authority by virtue of the fact that his implementation of hypertext (he didn't come up with the idea itself, it was decades old when he implemented HTTP) came about at the right time to catch on.

I have to give him credit for managing to turn his bit of dumb luck into an entire career, though. He has more honors and awards than he can probably count at this point:

en.wikipedia.org/wiki/Tim_berners-lee

Stop using the modern web, and start creating and promoting alternatives.

Preety much this . Why are you telling us this n-s-yayyy kun? Do you want a open web? Why not keep DRM a secret?

Can't we just make our own DOM.

Does this DRM aids effect older HTML standars (say, HTML 3.2, and 4.0)? If not, can't we make our own doctype and serve it over P2P?

It's not about the doctype. This technology is going to be included in every major browser. You're going to have basically 4 options:

1. Run a pre-DRM browser that's no longer receiving updates and is full of known security holes.
2. Run a non-mainstream browser like lynx or links.
3. Stop using browsers altogether.
4. Bend over and take the W3C's DRM in your cornhole.

Why not make a new browser then? Wasn't half chan doing that?

Firefox has EME implemented already, but it lets you disable it. I expect other mainstream browsers let you disable it too. What's wrong with that option?
The situation is fucked because it's going to normalize using EME on websites, but keeping it out of your own personal browser isn't that hard, as long as you don't rely on the EME.

that falls under (2)

Did his wallet find it especially important? Fucking fraud.

An open letter to the W3C Director, CEO, team and membership

(1/2)

>Effective today, EFF is resigning from the W3C.


https:// www.eff.org/deeplinks/2017/09/open-letter-w3c-director-ceo-team-and-membership

...

IPFS

This is a problem with the browser, not the transport.

Any self-respecting FOSS browser would probably have a way to disable the DRM, with a notice that "some websites may break" or whatever.

Oh they will ignore it and then cry about it. Just like Holla Forums when it found out the internet is basically cloudflare.

The browser is probably the most easily fixed of all the issues this is going to cause. Tinfoils will also happily use something with less features while a proper replacement is being forked and/or built.

Although the W3C decision is influenced by (((corporate interests))), who/what's cucked in this case?


Retard you can apply Google cache before archiving.
archive.is/yRmty

You all know this is a fucking problem that isn't solved by opting out. You think Netflix is bad? Fucking everything is going to use DRM now that this shit is standardized.
They're conditioning the normies to be cucks, and you're going to be a pariah for not following suit.

As always, the users.

>archive.is/yRmty
Please don't post shortened-links user.

That's an archive link you moron.

It's still shortened. He might be annoyed that he can't see what he's actually visiting.

Web standards were a mistake

at least with closed gardens you have no delusion of what's going on

...

No shit Sherlock.
Here's some knowledge.
You when you post this
>archive.is/yRmty
This is called a shortened link.
It's shortened because the real link behind it should normally be like this opisafagg.ot/
This kind of link is not obfuscated like archive.is or archive.fo
Here's an example of an archive link that isn't shortened.
web.archive.org/web/20170919093345/https://boingboing.net/2017/07/07/eschatology-watch.html
Has you can see you have two links in it:
-The archive:
web.archive.org/web/20170919093345/
-And the original source:
boingboing.net/2017/07/07/eschatology-watch.html
The advantage of such links is that besides being archived is that you know the original website you are supposed to go on.
Imagine that a shortened link redirects you to a website that isn't the good one, how would you know that it's not the one good one ?
But be reassured archive.is and archive.fo can give you non shortened links, just select "share" in archive.is.fo and it will give you multiple links notably the one that isn't shortened.


Basically this.
There's more to it tho.

Archive.is is not a shortlink for archive.org.

The Firefox feature cycle is as follows.
EME is at stage two of this cycle.

You're a dense motherfucker aren't you ?
If you understood that in the last post then I can't do anything for you.
I have no power that can regenerate brain cells.

I don't think you get it.

archive.is/2017.09.19-134541/https://8ch.net/tech/res/795293.html

Pretty sure he's right. You know life is a lot better if you can own up to your mistakes.

At least put it on IPFS or something.

Yes. Form the CIIIW which is a clone of W3C, gut the DRM, and get the FOSS browsers to follow CIIIW and not W3C. Then as W3C makes changes, don't carry them to the CIIIW, and be sure to make CIIIW changes that W3C will refuse to port. The way you break the W3C is to make them irrelevant to the internet.

That's not IceCat's fault, that's Netflux's fault for not providing an open internet solution for you to use. Cancel Netflux and start torrenting your shows.

Sure, he was explaining it to you in a condescenting way, but you don't get credit for using fallacy of extension on his explanation. +1 XP for admitting you were wrong.

Bumping because this is legit important even if you faggots would rather just argue about browsers.