qubit
Overclocked quantum bit
- Joined
- Dec 6, 2007
- Messages
- 17,865 (2.99/day)
- Location
- Quantum Well UK
| System Name | Quantumville™ |
|---|---|
| Processor | Intel Core i7-2700K @ 4GHz |
| Motherboard | Asus P8Z68-V PRO/GEN3 |
| Cooling | Noctua NH-D14 |
| Memory | 16GB (2 x 8GB Corsair Vengeance Black DDR3 PC3-12800 C9 1600MHz) |
| Video Card(s) | MSI RTX 2080 SUPER Gaming X Trio |
| Storage | Samsung 850 Pro 256GB | WD Black 4TB | WD Blue 6TB |
| Display(s) | ASUS ROG Strix XG27UQR (4K, 144Hz, G-SYNC compatible) | Asus MG28UQ (4K, 60Hz, FreeSync compatible) |
| Case | Cooler Master HAF 922 |
| Audio Device(s) | Creative Sound Blaster X-Fi Fatal1ty PCIe |
| Power Supply | Corsair AX1600i |
| Mouse | Microsoft Intellimouse Pro - Black Shadow |
| Keyboard | Yes |
| Software | Windows 10 Pro 64-bit |
This is a Very Bad Thing. Welcome to the broken internet.
TechDirt explains why:
For years now, we've discussed the various problems with the push (led by the MPAA, but with some help from Netflix) to officially add DRM to the HTML 5 standard. Now, some will quibble with even that description, as supporters of this proposal insist that it's not actually adding DRM, but rather this "Encrypted Media Extensions" (EME) is merely just a system by which DRM might be implemented, but that's a bunch of semantic hogwash. EME is bringing DRM directly into HTML and killing the dream of a truly open internet. Instead, we get a functionally broken internet. Despite widespread protests and concerns about this, W3C boss (and inventor of the Web), Tim Berners-Lee, has signed off on the proposal. Of course, given the years of criticism over this, that signoff has come with a long and detailed defense of the decision... along with a tiny opening to stop it.
There are many issues underlying this decision, but there are two key ones that we want to discuss here: whether EME is necessary at all and whether or not the W3C should have included a special protection for security researchers.
Read the rest: https://www.techdirt.com/articles/2...s-creation-officially-supports-drm-html.shtml
TechDirt explains why:
For years now, we've discussed the various problems with the push (led by the MPAA, but with some help from Netflix) to officially add DRM to the HTML 5 standard. Now, some will quibble with even that description, as supporters of this proposal insist that it's not actually adding DRM, but rather this "Encrypted Media Extensions" (EME) is merely just a system by which DRM might be implemented, but that's a bunch of semantic hogwash. EME is bringing DRM directly into HTML and killing the dream of a truly open internet. Instead, we get a functionally broken internet. Despite widespread protests and concerns about this, W3C boss (and inventor of the Web), Tim Berners-Lee, has signed off on the proposal. Of course, given the years of criticism over this, that signoff has come with a long and detailed defense of the decision... along with a tiny opening to stop it.
There are many issues underlying this decision, but there are two key ones that we want to discuss here: whether EME is necessary at all and whether or not the W3C should have included a special protection for security researchers.
Read the rest: https://www.techdirt.com/articles/2...s-creation-officially-supports-drm-html.shtml
