Skip Navigation

Posts
0
Comments
197
Joined
2 yr. ago

  • However, if they do implement it, which I imagine they would if this API actually becomes widespread,

    The problem is, is not really possible to implement it in a truly open-source browser, since anyone compiling it themselves (including distro maintainers) would fail the check unless they perfectly match a build approved by the attestor. If it differs from the approved version, that's specifically what WEI is intended to prevent.

  • Google's proposal also has sites serve content to clients without the attestation, or at least so they claim in the repo (thus the proposal to make the check deliberately fail sometimes, so websites won't rely on it. Of course, there is no guarantee it will stay that way, Google could change that policy whenever they want.

    The main difference is really in Google's dominance on the web. Sites can't start requiring Safari, but they can start requiring Chrome or Safari.

  • You've got 402 after 404

  • From another perspective, you have a new version every few days, with the date as the version

  • No, and not even all keyboards and mice. It will only work for ones which can do PS/2 signaling over the USB port.

  • That section isn't about ad-blockers, it's about botnet ad fraud; using bots to inflate ad view counts to make advertisers pay more.

  • And there is OpenSUSE: 10 11 12 13 42 15

  • It would have been, but they dropped the major version, since they no longer wanted the version number to be tied to the GTK version

  • Yes, there are some limitations to be aware of, with how it interacts with certain features. But EXT4 doesn't have any of those features at all. It doesn't have CoW, or balance, or multi-device, or snapshots.

    If the filesystem, is single-device, and you have the swapfile on it's own nocow subvolume, preallocate the swapfile, and don't try to take snapshots of it, it should be fine.

  • It doesn't seem to be targeting ad-blockers in particular (or other page customizing extensions), although that may result eventually. What it does do is let webpages restrict what web browsers and operating systems you are allowed to use, just like how SafetyNet on Android lets apps restrict you to using an OS signed by Google. That could end up with web pages forcing you to use a web browser and OS the big players like Google, Microsoft and Apple, blocking any less restrictive or less used competors like Firefox and Linux, thus creating a cryptographically enforced oligopoly. And even if they signed e.g. Firefox, it would only be certain builds of it. That would make it impossible to make a truly open-source browser that can access pages using this API. Quite concerning.

  • Mozilla suite was the predecessor, containing a web browser, e-mail client, web page editor, and IRC client. It was discontinued 17 years ago in favor of Firefox and Thunderbird, but continued by the community in the form of SeaMonkey.

  • Though really the Starfleet ship is more like a rowboat next to the Borg ship.

  • You mean HTML 5?

  • What sucks is that Outlook for some unfathomable reason inserts CSS that sets the paragraph spacing to 0 into all e-mail. So when you reply to someone who uses Outlook, you have to do that crap.

  • That doesn't even make any sense, since it's not an absolute scale

  • Apple side-steps the problem by, at least when you’re listening to Apple Music, simply sending the AAC stream as-is to the headphones and has them decode the audio.

    Do they actually though? Everything I can find says that's just a myth. If it can play multiple things at the same time, they can't possibly do that.