News for hackers. Stuff that matters.
Re:Payment Request API by swiley on Sunday September 17, 2017 @09:14PM (#15272704)
The w3c seems to be run by people who make money on the web, not people who use the web.
Re:Payment Request API by throwaway284534 on Sunday September 17, 2017 @09:26PM (#15272737)
The W3C is run by the same peers who frequent this and other tech forums. You can help by contributing to the organization, or you could hope for some internet points with snarky remarks. Which do you want to be remembered for?
Re:Payment Request API by jancsika on Sunday September 17, 2017 @10:56PM (#15273073)
For certain decisions that seems like a false choice.

For example, no amount of contribution would have stopped Netflix et al from pushing through EME as a web standard.

Re:Payment Request API by colejohnson66 on Monday September 18, 2017 @02:11AM (#15273707)
As bad as DRM is, EME is a good step towards killing Flash. And because of that, Netflix needs a replacement, and the studios aren’t just going to remove DRM requirements because Netflix says they won’t support DRM. I’m almost certain that if Netflix tried to remove DRM, the studios would balk and pull their content.
Re:Payment Request API by gsnedders on Monday September 18, 2017 @03:23AM (#15273969)
Or Netflix could take the route they took on iOS and just make native apps for everything.

Or, perhaps more likely, browser vendors would continue to not kill Flash until 2020 (at the earliest) when Adobe ends support, and then browsers would drop support for the insecure plugin and then Netflix would go the native apps route.

Re:Payment Request API by jancsika on Monday September 18, 2017 @12:52PM (#15277471)
That goes against what throwaway284534 was implying.

If everyone is a "peer" and an enormous number of those peers make a succinct, persuasive argument that EME is incompatible with W3C's mission statement of "Web for All" and "Web for Rich Interaction"[1], one would think that would make a difference in the direction the W3C takes.

Instead I'm eating popcorn watching players with deep pockets choose tactics in their battle to control an industry. And that battle is what shapes this web API.

So the claim of, "your peers are listening and they value your feedback," is about as convincing as a hold message from Comcast.

[1] https://www.w3.org/Consortium/mission

Re:Payment Request API by KyeRussell on Monday September 18, 2017 @04:19AM (#15274182)
It's called pragmatism.
Re:Payment Request API by ben_jones on Sunday September 17, 2017 @09:32PM (#15272751)
While he could've worded it better he did provide valid criticism. I'm sure he is not the only person here who has profiteering concerns for the various bodies who govern the internet.
Re:Payment Request API by swiley on Sunday September 17, 2017 @09:40PM (#15272786)
Alright "run" wasn't the right word, "heavily influenced by" is probably better.

They just seem to continuously standardize things that are very user hostile and only serve content distributors.

Re:Payment Request API by detaro on Sunday September 17, 2017 @10:28PM (#15272943)
> continuously standardize things that are very user hostile and only serve content distributors.

Example Nr 1 you are going to quote is the DRM stuff (understandably, it's the most controversial for good reasons, both inside and outside W3C). What other very user hostile examples are there?

Re:Payment Request API by swiley on Monday September 18, 2017 @10:58AM (#15276478)
Web workers are pretty bad if you're looking for another one.
Re:Payment Request API by RandomInteger4 on Sunday September 17, 2017 @09:47PM (#15272813)
If people want to make money of the content they produce and other people are happy to pay them, then what's the problem?
Re:Payment Request API by orf on Monday September 18, 2017 @04:20AM (#15274184)
Why not both?
Re:Payment Request API by objclxt on Sunday September 17, 2017 @11:20PM (#15273158)
> The w3c seems to be run by people who make money on the web, not people who use the web.

Not really. Anyone can join the W3C, and anyone can participate in a working group / contribute to a standard.

However, most people would agree that the balance of power effectively lies with the browser vendors. You can propose a standard all you like, but if you can't get a browser to adopt it then it's not going to get any traction. And although it's true that some browser vendors make their money off the web (Google) others very much don't (Apple).

Re:Payment Request API by gsnedders on Monday September 18, 2017 @03:28AM (#15273984)
> However, most people would agree that the balance of power effectively lies with the browser vendors

It lies with two groups: the implementers (as nothing can become a standard without implementations, though there's plenty of precedent for using obscure ones!) and the W3C Members (i.e., the paying organisations who pay to get a seat; not those who contribute on mailing lists/GitHub/whatever, not those who are officially on the working groups as "invited experts") who ultimately vote on the proposed standard (and there Google has as much say as the BBC and Boeing and the University of Edinburgh.

Re:Payment Request API by dmitriid on Monday September 18, 2017 @03:44AM (#15274046)
> Anyone can join the W3C, and anyone can participate in a working group / contribute to a standard.

Starting at ~10 000 USD per year, sure

Re:Payment Request API by gsnedders on Monday September 18, 2017 @09:03AM (#15275446)
It's worth noting that while it costs money to join the W3C, W3C membership isn't a requirement to participate in most (maybe even all now?) WGs where you can simply join the mailing list or subscribe to the GitHub repo and contribute.
Re:Payment Request API by dmitriid on Tuesday September 19, 2017 @07:02AM (#15283452)
However, if you want anything done (especially your way), you'd better be paying A LOT. See recent EME snafu