More along the lines of a “pizza finder” service that scours different menus and shows the pizza options at a bunch of places, whether those places exclusively offer pizza, specialize in pizza with some other options, or just offer pizza as one of several options. It would be perfectly reasonable for such a service to only return results related to pizza, without any implicit suggestion that each place it returns only has pizza available.

Financial analysts were sounding the alarm in October. On October 7, Bloomberg ran an influential article about the circular deals:

https://www.bloomberg.com/news/features/2025-10-07/openai-s-nvidia-amd-deals-boost-1-trillion-ai-boom-with-circular-deals

That built on earlier reporting where they described the deals as circular, as the deals were being announced. Each of these reports notes the financial analysts at different investment firms sounding the alarm.

From there, a robust discussion happened all over the financial press about whether these circular deals were truly unstable. By the time Gamers Nexus ran that video the financial press was already kinda getting sick of the story.

Whatever the hell these trading algorithms were doing on November 20, they definitely weren’t ahead of the curve on investor knowledge and belief.

it’s like AI companies went from buying 10 memories as usual to 1000000,

I mean, they basically did. OpenAI announced a few months ago that they reached deals to buy 900,000 wafers of DRAM per month, representing 40% of global production capacity. For a single company. There are several other companies competing at those scales, too.

End to End Encryption protects the messages *between the ends". If an “end” is compromised the best E2EE technology isn’t going to protect confidentiality.

Just ask Pete Hegseth, who invited a journalist into an E2EE signal chat. The journalist was an authorized “end” and could therefore read the conversation.

This change is about employers who already have full access to the “end” of the Android phone itself when that phone is in an enterprise managed state. Perfect encryption between that phone and other parties doesn’t change anything because the employer has full access to the phone itself.

but I don’t think most are designed to control people’s opinions

Yeah I’m on team chaos theory. People can plan and design shit all they want, but the complexity will lead to unexpected behavior, always. How harmful that unwanted behavior is, or how easy it is to control or contain, is often unknown in advance, but invented things tend to develop far, far outside the initial vision of the creators.

Being able to point a camera at something and have AI tell me “that’s a red bicycle” is a cool novelty the first few times, but I already knew that information just by looking at it.

Visual search is already useful. People go through the effort of posting requests to social media or forums asking “what is this thing” or “help me ID these shoes and where I can buy them” or “what kind of spider is this” all the time. They’re not searching for red bicycles, they’re taking pictures of a specific Bianchi model and asking what year it was manufactured. Automating the process and improving the reliability/accuracy of that search will improve day to day life.

And I have strong reservations about the fundamental issues of inference engines being used to generate things (LLMs and diffusers and things like that), but image recognition, speech to text, and translation are areas where these tools excel today.

The eyebrow raiser in the Slate’s base configuration is that it doesn’t come with any audio systems: no radio antenna/tuner, no speakers. It remains to be seen how upgradeable the base configuration is for audio, how involved of a task it will be to install speakers in the dash or doors, installing antennas (especially for AM, which are tricky for interference from EV systems), etc.

I’d imagine that most people would choose to spend few thousand on that audio upgrade up to the bare minimum expectations one would have for a new vehicle, so that cuts into the affordability of the package.

The analog dials were an illusion. That information has been processed digitally for at least the last 25 years.

What I’m saying is if YouTube is sharing $10 million of revenue with channel owners in a month that has 1,000,000,000 total views across YouTube, that’s a penny per view.

Then, if the next month the reconfigure the view counts to exclude certain bots or views under a particular number, you might see the overall view count drop from 1,000,000,000 to 500,000,000, while still hitting the same overall revenue. At that point, it’s $0.02 per view, so a channel that sees their view count drop in half may still see the same revenue despite the drop in view count.

If it’s a methodology change across all of YouTube, a channel that stays equally popular as a percentage of all views will see the revenue stay the same, even if the view counts drop (because every other channel is seeing their view counts drop, too).

Isn’t that the formula? They take all of the revenue, set aside the percentage they’ve set for revenue share, and then divide that among all channels based on viewer counts. Dropping viewership for all channels proportionally means that the same amount of revenue will still be distributed to the channels in the previous ratios.

Most 4k streams are 8-20 Mbps. A UHD runs at 128 Mbps.

Bitrate is only one variable in overall perceived quality. There are all sorts of tricks that can significantly reduce file size (and thus bitrate of a stream) without a perceptible loss of quality. And somewhat counterintuitively, the compression tricks work a lot better on higher resolution source video, which is why each quadrupling in pixels (doubling height and width) doesn’t quadruple file size.

The codec matters (h.264 vs h.265/HEVC vs VP9 vs AV1), and so do the settings actually used to encode. Netflix famously is willing to spend a lot more computational power on encoding, because they have a relatively small number of videos and many, many users watching the same videos. In contrast, YouTube and Facebook don’t even bother re-encoding into a more efficient codec like AV1 until a video gets enough views that they think they can make up the cost of additional processing with the savings of lower bandwidth.

Video encoding is a very complex topic, and simple bitrate comparisons only barely scratch the surface in perceived quality.

Article is paywalled for me.

Does it describe the methodology of how they use the transmitter and receiver?

What specifically are they transmitting? Is it actually wifi signals within the 802.11 protocols, or is “wifi” just shorthand for emitting radio waves in the same spectrum bands as wifi?

Yeah I’m with you.

“Using this technological advancement to improve health care is good”

“Not in countries where health care is publicly run”

“What” is the correct response here.

“The only difference between the two emails was the link,” the memo said. “ActBlue delivered. WinRed got flagged. That is not a coincidence.”

It could also be that winred is more often associated with spam because emails with winred links use a style more associated with other actual spam. Like if spammers use words like Trump a lot to try to scam victims, and a lot of those emails get flagged as spam, then the word Trump itself becomes more highly correlated with spam. And since the word Trump is highly associated with winred links, maybe winred gets caught up in the rule set/heuristics that associate Trump fundraisers with spam.

How does being a dick to users get back at site admins you don’t like?

That’s another round trip, and you still have to use JS to identify þe browser.

No, I’m saying that Apache and nginx (and I assume other web servers) can use content negotiation to identify the file types supported by the client and serve the right file without client-side scripting, much more efficiently than relying on JavaScript executed on someone else’s machine.

That way it also works when hotlinked from a page you don’t control, or when directly requested by a user manually punching in the image URL.

Javascript for this seems like the wrong tool. The http server itself can usually be configured to serve alternative images (including different formats) to supporting browsers, where it serves JXL if supported, falls back to webp if not, and falls back to JPEG if webp isn’t supported.

And the increased server side adoption for JXL can run up the stats to encourage the Chromium team to resume support for JXL, and encourage the Firefox team to move support out from nightly behind a flag, especially because one of the most popular competing browsers (Safari on Apple devices) does already support JXL.

It’s not too late.

The current standard on the web is JPEG for photographic images. Everyone agrees that it’s an inefficient standard in terms of quality for file size, and that its 8-bit RGB support isn’t enough for higher dynamic range or transparency. So the different stakeholders have been exploring new modern formats for different things:

WEBP is open source and royalty free, and has wide support, especially by Google (who controls a major image search engine and the dominant web browser), and is more efficient than JPEG and PNG in lossy and lossless compression. It’s 15 years old and is showing its age as we move towards cameras that capture better dynamic range than the 8-bit limits of webp (or JPEG for that matter). It’s still being updated, so things like transparency have been added (but aren’t supported by all webp software).

AVIF supports HDR and has even better file size efficiency than webp. It’s also open source and royalty free, and is maintained by the Linux Foundation (for those who prefer a format controlled by a nonprofit). It supports transparency and animation out of the box, so it doesn’t encounter the same partial support issues as webp. One drawback is that the AVIF format requires a bit more computational power to encode or decode.

HEIC is more efficient than JPEG, supports high bit depth and transparency, but is encumbered by patents so that support requires royalty payments. The only reason why it’s in the conversation is because it has extensive hardware acceleration support by virtue of its reliance on the HEVC/h.265 codec, and because it’s Apple’s default image format for new pictures taken by its iPhone/iPad cameras.

JPEG XL has the best of all possible worlds. It supports higher bit depths, transparency, animation, lossless compression. It’s open source and royalty free. And most importantly, it has a dedicated compression path for taking existing JPEG images and losslessly shrinking the file size. That’s really important for the vast majority of digitally stored images, because people tend to only have the compressed JPEG version. The actual encoding and decoding is less computationally intensive than webp or avif. It’s a robust enough standard for not just web images, but raw camera captures (potentially replacing DNG and similar formats), raw document scans and other captured imagery (replacing TIFF), and large scale printing (where TIFF is still often in the workflow).

So even as webp and avif and heic show up in more and more places, the constant push forward still allows JXL to compete on its own merits. If nothing else, JXL is the only drop in replacement where web servers can silently serve the JXL version of a file when supported, even if the “original” image uploaded to the site was in JPEG format, with basically zero drawbacks. But even on everything else, the technical advantages might support processing and workflows in JXL, from capture to processing to printing.

You were talking about $1.34 in damages, which doesn’t sound like downtime or disruption.

you will get prison for DDoS in USA

Who said anything about DDoS? I’m using ad blockers and saving/caching/archiving websites with a single computer, and not causing damage. I’m just using the website in a way the owner doesn’t like. That’s not a crime, nor should it be.