• 1 Post
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle




  • That’s not necessarily a good solution either, because a service could figure out that the source of random fingerprint data likely comes from the same user. Especially if your ip is not changing. It might perhaps be effective if a substantial amount of people were doing it though.

    But to generate such random fingerprint is difficult because it consists of many parts and services don’t all build fingerprints the aame way. You could easily randomize e.g. canvas data, but the issue is that if you only randomize one data point then that one random data point pretty uniquely identifies you if your other datapoints are stable. So to be effective you would really need to randomize several different datapoints and that may not be such an easy task since websites could build them in all sorts of ways.




  • Indeed. I mean, I’m blocking ads as much the next guy and that’s not going to change in any foreseeable future, but I cannot see how introduction of privacy preserving advertising platform could possibly be seen as anything other than an improvement over the current, completely perverse, situation. It would be better for people who don’t block ads, so if this acquisition would advance uses of privacy-respecting advertising systems and simultaneously get some revenue to Mozilla then this sounds quite like a win-win to me.










  • I mean, there are options. It could mute/unmute, close the stream, copy one of various track information such as track name or playback position, send the video to different screen etc. But I can’t think of anything that makes much sense, although mute/unmute is at least somewhat sensible.

    But, yeah, it’s one of those interactions that has just always worked like that, long before browsers could play video even. It’s similar to how Ctrl+C copies stuff, Ctrl+Z undoes previous operation, right-click opens a context menu etc.; they don’t have to do those things, but users have learned to expect it, so it would be pretty dumb to change that with no reason.




  • Right, and that’s fine. The one good thing about these “collections” is when they describe what the pref does (I mean, so does official source typically). But that matters only as long as the audience actually reads those descriptions. But then if you just pick the ones you actually care about (which you should totally do) it becomes irrelevant from which “collection” you found about it from.


  • None.

    I don’t think it’s a good idea to take some huge collection of prefs and just apply them blindly.

    Instead, make the changes that you actually want to do, so that you actually know what changes you are causing. If you want to put those into your user.js file then feel free, but in my opinion it’s just better to change them in about:config directly - that is, unless you need to apply the exact same set of changes to multiple profiles.