Friday, March 05
Daily News Stuff 5 March 2021
No Through Road Beyond Zebra Edition
No Through Road Beyond Zebra Edition
Tech News
- Bring your own client. (Geoffrey Litt)
I'm in favour of this idea. The API for the new site was completed around Christmas; it's the UI that's holding things up.
- eBay has banned sales of the six blacklisted Dr Seuss books. (WSJ)
These are sales of children's books between private individuals.
Banned.
- HTTPWTF. (HTTPToolkit)
For example, theCache-Control: no-cacheheader tells the browser to cache your content, even if it is not normally cacheable.
- I for one welcome our new, incredibly stupid, robot overlords.
- Google wants to give your browser cancer. (EFF)
FLoC is a replacement for third-party tracking cookies. They don't plan to stop tracking you; they plan to have your own browser track everything they do and report back to them.
The EFF is stepping into the shoes the ACLU pooped in. Um. The EFF threw out the ACLU's shoes because they smelled of poop, bought some new shoes, and stepped into those.
- How well do dual RTX 3090s in SLI work? (Serve the Home)
For some computation and rendering tasks it works very well. For games, on the other hand, this is Serve the Home, they didn't benchmark any games.
- Kiara got her shadowban lifted, finally.
YouTube deleted the last two months of her videos instead.
Yes, this is the same retarded crap that they pulled with Hardware Unboxed.
Epic Rant Video of the Day
Disclaimer: When On Beyond Zebras are outlawed, only outlaws will have On Beyond Zebras.
Posted by: Pixy Misa at
10:58 PM
| Comments (3)
| Add Comment
| Trackbacks (Suck)
Post contains 255 words, total size 3 kb.
1
From the HTTPWTF article: "This totally works, it's widely used and quick & easy to implement, which is all great, but it's wild that every websocket connection in the world relies on one magic UUID."
Not as rare as you would think. Raymond Chen had an example of this years ago. DirectX is at least partially a capability-based system; it asks cards a bunch of "do you support X feature?" questions, where 'X feature' is signified by a particular UUID. They found one card was responding to every feature request with a yes, whether or not it actually did, so they generated a UUID[1] and added that to the list of feature requests, only there was no feature tied to it. That meant that any card that claimed to support that feature was buggy or lying, and they switched to some kind of fallback.
[1] I think this was one of the cases where they actually generated an old-style v1 GUID from a NIC and then "smashed the NIC to guarantee no other GUID could ever be generated that matched that one."
Not as rare as you would think. Raymond Chen had an example of this years ago. DirectX is at least partially a capability-based system; it asks cards a bunch of "do you support X feature?" questions, where 'X feature' is signified by a particular UUID. They found one card was responding to every feature request with a yes, whether or not it actually did, so they generated a UUID[1] and added that to the list of feature requests, only there was no feature tied to it. That meant that any card that claimed to support that feature was buggy or lying, and they switched to some kind of fallback.
[1] I think this was one of the cases where they actually generated an old-style v1 GUID from a NIC and then "smashed the NIC to guarantee no other GUID could ever be generated that matched that one."
Posted by: Rick C at Saturday, March 06 2021 02:35 AM (eqaFC)
2
"We implore Google to abandon FLoC and redirect its effort towards building a truly user-friendly Web."
Well, nice idea, but they're probably ten years too late. Google backing down any amount on the issue of tracking is Google saying "we want to be a much smaller company", what with them being the biggest ad/tracking company.
Well, nice idea, but they're probably ten years too late. Google backing down any amount on the issue of tracking is Google saying "we want to be a much smaller company", what with them being the biggest ad/tracking company.
Posted by: Rick C at Saturday, March 06 2021 02:42 AM (eqaFC)
3
Browser fingerprinting: I had a thought about this yesterday. One of the things they fingerprint is the list of fonts the browser has access to. I wondered if this is dynamically generated or set on browser startup. If it's not set on browser startup, it might be entertaining to right (say) a Windows service[1] that generates randomly-named fonts. Imagine that it registers and unregisters with Windows, 5-15 different fonts every few seconds. You'd probably need to do something that was an actual readable font file but since this isn't a font you'd actually use, something that consisted of a minimal set of glyphs would probably be sufficient to keep Windows from barfing. The idea is like the Star Trek anti-Borg shield rotation frequency: change your fingerprint constantly, rather than hiding it. FWIW, the browser I'm using at the moment says it has 3.5 bits of entropy (1 in 11.8 browsers) on the EFF cover your tracks site. No idea if this would be useful and there are sure to be some drawbacks.
[1] or a Unix daemon; the idea being that it's not part of the browser at all.
[1] or a Unix daemon; the idea being that it's not part of the browser at all.
Posted by: Rick C at Saturday, March 06 2021 02:55 AM (eqaFC)
52kb generated in CPU 0.014, elapsed 0.1351 seconds.
58 queries taking 0.1247 seconds, 342 records returned.
Powered by Minx 1.1.6c-pink.
58 queries taking 0.1247 seconds, 342 records returned.
Powered by Minx 1.1.6c-pink.
