I understand that the HN crowd is composed of many different people with radically different interests and opinions, so an "average HN opinion" would be mostly meaningless, but still...
I find it mildly amusing that HN both loudly complains about bots scraping their websites AND is very interested in user privacy.
The conflicting part is that user privacy automatically means that you cede any control over how exactly does the user accesses your resource. Whether they use a web browser or an automated scraper. Any attempt to analyze requests to tie different requests made by the same actor together automatically means privacy violation.
I don't have a good answer to this dilemma yet, I just thought that this is a curious observation and wanted to share.
see f.e. "Highlight" (Resolved value of the Highlight system colour keyword, as RRGGBB), which has bajillion different values for android - and I can't find the most common ones for linux
I wonder if this took into account GPU render-time fingerprinting? The minute timing differences in how you render an image are still used to identify you.
Recently did a WebGPU project and noticed Firefox polls GPU status on a 100ms timer, so you can't really use it for such as far as I can tell.
That said, Claude figured out that while Canvas copying of a loaded JPEG was out due to fingerprint resistance, it could copy it via WebGPU, so yeah...
10 comments:
Oh, damn. I thought this was about the uniqueness of human fingerprints or similar.
I understand that the HN crowd is composed of many different people with radically different interests and opinions, so an "average HN opinion" would be mostly meaningless, but still...
I find it mildly amusing that HN both loudly complains about bots scraping their websites AND is very interested in user privacy.
The conflicting part is that user privacy automatically means that you cede any control over how exactly does the user accesses your resource. Whether they use a web browser or an automated scraper. Any attempt to analyze requests to tie different requests made by the same actor together automatically means privacy violation.
I don't have a good answer to this dilemma yet, I just thought that this is a curious observation and wanted to share.
funny how enabling letterboxing causes me to be in "under 100 samples" category
btw, is pixelRatio controllable somehow? how do I set it to 1, most common value?
wtf is "Maximum touch points" ?
> The digitiser's touch-point count, uncollapsed.
my laptop does not have touch screen, why am I not at 0?
interesting how Windows and Mac are almost at 100% of DRM enabled, meanwhile linux is only at 33%
anyone knows why is that?
I wish I could select what OS to sort values for
see f.e. "Highlight" (Resolved value of the Highlight system colour keyword, as RRGGBB), which has bajillion different values for android - and I can't find the most common ones for linux
I read they're not releasing the details - that seems good (for the public). Hopefully they're releasing it to privacy-friendly browser makers.
I wonder if this took into account GPU render-time fingerprinting? The minute timing differences in how you render an image are still used to identify you.
If you can run compute shader code, the fingerprinting and side channel possibilities become very rich. [1] is one paper among many on this topic.
[1]: https://dl.acm.org/doi/10.1145/3634737.3656283
Recently did a WebGPU project and noticed Firefox polls GPU status on a 100ms timer, so you can't really use it for such as far as I can tell.
That said, Claude figured out that while Canvas copying of a loaded JPEG was out due to fingerprint resistance, it could copy it via WebGPU, so yeah...