• 4 Posts
  • 20 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.



  • Yeah, loading any external resources - I would think fonts even more so than images - is potentially risky. In addition, there is somewhat realistic possibility for browser fingerprinting if you use some style that makes browser viewport size atypical.

    I can’t think of any actual security issues other than those. Otherwise the worst that a style could do is crash the browser, to make it utterly unusable or make it super slow. But those are all recoverable by simply trashing userChrome.css and restarting Firefox.










  • Has the thing you are doing ever worked? I mean, if you were to use actual inline svg document then I think it would just work, but I doubt you are doing that. But if you just use an svg image using say, list-style-image or background-image, then I don’t think currentcolor inside the svg has ever worked.

    The way colors are forwarded from the embedding document (in gecko) to the svg is bit of a hack. The svg icon needs to have certain attribute value in its definition: example: ... AND the element using this svg icon needs to declare that such forwarding is needed using css .thing { -moz-context-properties: fill, fill-opacity } AND then setting the fill color like .thing { fill: currentColor }.

    And you need to set svg.context-properties.content.enabled if the svg file you are using is not loaded using chrome:// or resource:// uri.

    If you do that setup then you can totally make them use currentColor from the embedding document. This hackery might not be required anymore when/if css link params is implemented.