Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)VI
Posts
0
Comments
47
Joined
2 yr. ago

  • There are people profiting from this either by owning the investment firms e.g. through stocks or by working in them in highly paid positions. In a democracy, the majority might be for such a law, but certainly not everyone.

  • You can file web compatibility bugs on bugzilla.mozilla.org or webcompat.com

    There are different ways how bugs are fixed. But someone might reach out to the page itself, find and fix a bug in Firefox or change the web specification if the incompatibility arises from ambiguity around the feature definition.

    Firefox can also ship an intervention, basically injecting code into certain websites to fix broken ones.

    Some incompatibilities can arise from missing features in Firefox, the web constantly evolves and the Devs sometimes don't catch up. But bugs might still help, as high compatibility-risk features might be implemented more quickly.

  • I think lots of people also don't know how easy it is to migrate all user data between browsers. Also, the added work of changing your phone app is probably too much for the average, comfortable consumer.

  • Though misandry and mysogny often occur together and mirror each other. So it's valid to cry about both when someone talks about "woman and children" are grouped together as especially vulnerable groups that need additional protection.

  • During last year, I watched two series (only murders, Andor) and one movie. Disney+ is convenient and I can share the account with some friends. But at some point, it's literally cheaper to buy the things I watch directly and then also own them. Set up a Plex instance and it's also easier to share with friends.

  • Not only is telemetry easy to disable. In about:telemetry, you can see what's being send and many of these things are important to improve the user experience, make Firefox faster and also monitor privacy/security problems.

    Without telemetry (use counter), how to decide whether a deprecated feature can be removed? Removing them is necessary to decrease maintenance work, be able to innovate and remove features that are less secure.

  • Maybe they're greedy, maybe more are using adblockers, maybe companies aren't willing to spend as much per ad due to the economy, maybe they are profitable but the margin is too low to be worth the effort and risk associated with running a platform. We probably won't know.

  • I don't think filling Google repositories with complaints and well-intentioned, but garbage issues/pull requests. At best they'll just delete them occasionally and at worst work less in the open, changing permissions on repositories, doing discussions more in internal tools.

    What you can do is support alternative browsers, get other people to use them too and notify news as well as your local politicians about such problems. Maybe join organizations on protecting privacy or computer clubs (in Germany, support e.g. Netzpolitik.org and CCC).

    Maybe acknowledge what the in-principle good things about WEI would be and support alternative means of achieving them. This proposal uses good things like less reliance on captchas and tracking, a simple to use API to enable a huge potential for abuse and power grab. Alternatives might be a privacy pass, as mentioned by WebKit https://github.com/WebKit/standards-positions/issues/234

  • I guess this is much less about captcha V2, i.e. the ones everyone sees but more about V3 that works in the background or other such scripts using fingerprinting, collecting lots of data about the user to determine their validity.