MGSV had realistic graphics (one of the first games with PBR) and handled it well. One of the devs had a GDC talk about their lighting approach, too.
In the game light/shadow (in addition to what outfit you're wearing, surface you're on, if you've showered recently and other factors) has an effect on your camouflage index. Unlike prior Metal Gear Solid games this is never shown as a value on-screen but instead communicated by clues from enemy reactions and sound cues, where eg. their animation will change to show they've noticed something suspicious from a distance.
There's evidence various third-party models (including Deepseek) used distilling in training, based on models from those leading services. So they have more flexibility with pricing.
The point was that distilling based on others' models for training means they're not spending the same amount on R&D and/or training, giving them headroom in other ways (responding to the parent's point). It wasn't a comment reflecting on copyright/fair use.
I like the wide layout of the site but just on a readability front on a widescreen monitor after the opening more narrow paragraphs it changes to full width text layout and those could benefit from a `columns: 2` in CSS to split them since reading long width paragraphs is a bit difficult.
While a couple months back an article[1] discussed how Google was keeping the water requirements a secret from locals who wanted transparency, claiming it was proprietary knowledge.
So they sued and discovered it will use 2-8 million gallons of drinking water per day[2], seemingly near the limit of their capacity to handle, judging by comments from officials.
> 'That water supply that otherwise would not be required until 2060 or the 2060s, suddenly becomes something that we need to be worried about during the 2030s.’
> If it exceeds that demand, they’re going to have to start looking for a new water source.
So I'm not sure how this fits with the claims of the article from the OP. I suppose if anything it disproportionately affects certain places not as well equipped for it?
It seems the reason they're inlined in the page at all is to measure things briefly like bounding boxes (not sure the full extent as it didn't cover that), before subsequent removal. I'm not familiar with Scratch and its use of user-submitted SVGs but I'd be curious to read more about what they're doing that required it be inlined specifically.
(This isn't a comment on the challenges in proper sanitization fwiw, as I've needed to do various of the same things myself)
They want to run getBBox [1] which requires the SVG to be in the DOM somewhere - otherwise it throws an error. They need to do this because SVGs tend to have very inaccurate viewboxes, especially when working with SVGs made in old versions of Scratch. getBBox is the easiest way to get a more accurate understanding of how big the stuff in the SVG is.
> Disabling JavaScript actually greatly increases your fingerprint as not many users turn it off, so that instantly puts you in a much smaller bucket that you need to be unique in.
I've heard a handful of people say this but are there examples of what I would imagine would have to be server-side fingerprinting and the granularity? Since most fingerprinting I'm aware of is client-side, running via JS. While I expect server-side checks to be limited to things like which resources haven't be loaded by a particular user and anything else normally available via server logs either way, which could limit the pool but I wonder how effective in terms of tracking uniqueness across sites.
In addition to server-side bits like IP address, request headers and TLS/TCP fingerprints, there are some client-side things you can do such as with media queries, either via CSS styles or elements that support them directly like <picture>. You can get things like the installed fonts, screen size/type or platform/browser-specific identifiers.
> It'll be like (lack of) privacy on the internet caused by the ad industrial complex, but much worse and much more invasive.
The concerning aspect is how others' content being scanned into systems don't have any knowledge or consent. Having private PII/files/code/emails/etc being read and/or accidentally shared by the agent online.
Matches the name of episode 152[1] the Wikipedia article cites for the info. Seems the classification of seasons and even the season's episode order on Wikipedia differs from the one in the Youtube title.
reply