Latest Posts (20 found)

2026-11-18 22:11: Last few weeks we've seen PHP2Shell, Brotli, Java4Shell, Nginx, and another PHP critical vuln imminent....

Last few weeks we've seen PHP2Shell, Brotli, Java4Shell, Nginx, and another PHP critical vuln imminent. AI is really gonna fuck things up. This shit needs regulating. Fast. Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️ You can reply to this post by email , or leave a comment .

0 views
Unsung Today

“The download numbers of the mod broke all records at our site.”

Grand Theft Auto: San Andreas followed in the footsteps of 2002’s GTA: Vice City, and was released in 2004. (Subsequent versions were IV from 2008, V from 2013, and VI, launching right now .) Here’s a 2012 story at Eurogamer , written by Simon Parkin, about the infamous Hot Coffee minigame , unlocked in San Andreas by a third-party mod. It all started with a last-minute decision to remove some sex scenes that were originally meant to be published in the game: The question now was how to extract the explicit material without breaking the wider game’s functionality so close to release. An emergency meeting was called so that the senior managers could discuss a solution. During the meeting Houser explained: “You can’t always take a thing out of a game.” He had an alternative solution: rather than remove the content, the team could ‘wrap’ the sexual scenes so that while the relevant code would still be present on the game disc, it would be impossible for the player to access from within the game. As he put it in an internal email sent at a later date: “We locked it away because there was no other way to get the game done on time – safely. The code is very interwoven in [GTA] and everything reacts to everything else. The impact of yanking something late is too scary.” The decision was made. The sex would remain, but the sex would remain hidden. The idea was perhaps to unlock the scenes later via an official patch, but we all know what happens to content hidden in game’s code – inevitably, a curious nerd will find it and then talk to other nerds about it: The video showed that the content wasn’t a hidden cut-scene but a pair of playable mini-games. In one, dubbed the “spanking game” by Wildenborg, players were invited to smack CJ’s girlfriend on the backside, rhythmically tapping a button to raise an “excitement” bar. In the “shagging game”, players moved the analogue stick in time with the characters’ bodies to increase excitement. Both characters remained fully clothed and there were no genital shots. But this was still the most explicit sexual content Wildenborg had seen in a video game. “It was at this point I decided to release the patch to the public,” he says. “I tossed the name «Hot Coffee» on the file, based on the fact that the girlfriends would ask CJ in for some «coffee» as a euphemism for sex. Hot Coffee was the first modification for San Andreas.” Despite not owning a copy of the game himself, with two days still to go before the game’s European release, Wildenborg had spilled Hot Coffee. Then everything blew up. I’ll let you read the rest . It’s an interesting story that contains some good observations – “Houser understood the great contradiction at the heart of Western culture: tolerance towards violence versus intolerance towards sex” – although I am somewhat doubtful that the game creators were interested in pushing the public debate as much as they were in generating marketing-friendly controversy. If you agree with that correction, it becomes an even more interesting story in that it doesn’t portray anyone involved in a particularly positive light.

0 views
Unsung Today

“It was awful, it was too sim-y.”

The original Grand Theft Auto – known in early production as Race ’n’ Chase – had a problem: it just wasn’t too fun to play. The driving was there, the buildings were there, the missions were there, but the joy wasn’t. What injected the right amount of joy was… an unexpected bug. When the player earned a “wanted” status, the game dispatched some cop cars to chase them. As they do, the cop cars had a particular pathfinding algorithm where they meant to converge on a player. But within that algorithm, there was a mistake, as described by one of the game’s creators : […] the other thing that was a problem was the handling – the car handling was appalling. There was a point in it where you used to have a button for opening the doors and it was just rubbish. I can’t remember if this is true because we used to joke about it that you even had to start the engine. It was awful, it was too sim-y. And there was a whole living city thing that crept into it. That kind of inspires people to be more realistic and simulate more often. That steers you in a certain direction. But there were people on the team constantly trying to get that fixed. So the core of playing was fundamentally broke. There were steps being taken to fix that, but it wasn’t really gelling together. The police behaved really badly, the way they originally worked was just rubbish. Then one day, I think it was a bug, the police suddenly became mental and aggressive. It was because they were trying to drive through you. Their route finding was screwed I think and that was an awesome moment because suddenly the real drama where, “Oh my God, the police are psycho – they’re trying to ram me off the road.” That was awesome, so that stayed in. It was tweaked a little bit, but that stayed in because that was great fun. Suddenly the game got more dramatic and it’s no longer boring – the police trying to pull you over. They’re after you, they’re trying to ram you off the fucking road. Everybody suddenly went, “Hey, this is actually pretty cool. There’s something in this, this is working.” It was less about the mission stuff, which we always thought was another mess, and more about just general play – just being able to piss around. I don’t think we’ve ever seen the code or the bug in question. I found the story interesting, not only because it teaches us that you can’t really work your way around bad mechanics (this can be as true for serious apps as it is for videogames), but also because it highlights the interesting push and pull between realism and fun. The game was eventually released in 1997 and spawned a best-selling series.

0 views
Unsung Today

Le Monde’s interesting cookie pop-up

Cookie banners and pop-ups are bad not just because they are a nuisance , but also because so many try to trick you into choosing the setting that benefits the advertisers and reduces your privacy: the default option is the one bad for you, and the non-default one makes you jump through the hoops, mainfested as confusing dialogs with subpar, multi-clicks interfaces, with plausible deniability of “well, we’re giving the user control.” But I just went to the website of the French newspaper Le Monde , and saw something really interesting: = 2x) and (width >= 700px)" srcset="https://unsung.aresluna.org/_media/le-mondes-interesting-cookie-pop-up/1.2096w.avif" type="image/avif"> = 3x) or (width >= 700px)" srcset="https://unsung.aresluna.org/_media/le-mondes-interesting-cookie-pop-up/1.1600w.avif" type="image/avif"> The “Reject all cookies” was there where you usually expect a close box to be, which felt… strangely thoughtful? I wanted to click that anyway, and that ended up benefitting me. I’m expected to be proven wrong here – but this felt like an unexpected positive UI decision, given all this context, and an unexpected understanding of motor memory.

0 views

Data Contracts

Data contracts are a way to describe the contents and guarantees of datasets. Simon Harrer and Arif Wider describe in detail what they are and how to use them. They apply practices from API design to data by treating them as data-providing services - such as data products - whose interfaces we want to define as clearly as possible. This approach significantly increases the robustness of large-scale data landscapes, and gives both people and AI agents the explicit, trustworthy metadata they need to work with data autonomously, which is why more and more enterprises are adopting them.

0 views

Nvidia Earnings; Office Convergence; OS Wars, AI Edition

Nvidia's earnings were boring, and also a statement as to why Jensen Huang probably isn't coming back; then, Microsoft and Anthropic ship dueling operating system updates.

0 views

curl on OSS-Scanner

OSS Scanner is a service by Anthropic to scan critical open-source repositories for security vulnerabilities curl maintainer Max Dymond submitted pull-request 1191 to OSS-Scanner in the end of October and we were swiftly enrolled into the program. The idea for this service is inspired by OSS-Fuzz : Anthropic scans the participating open source projects for security problems on their machines at some interval with their magic applied and they let us know if they find anything. I don’t think they officially say exactly which model they use for this nor how often they rescan. Early in the morning of November 5 we received our first sign of life from them since they merged the PR. An automated mail: Forty-five security vulnerabilities in a single shot is a lot . But sure, we did ask them to do this. Of course, had we not asked them, chances are someone else would instead have figured these ones out and reported to us separately. There are many people with capable harnesses and AI models out there. The Anthropic email with all the findings described that the analysis considers one of the flaws to be severity MEDIUM and the remaining 44 at severity LOW. In addition, they also found 23 ordinary bugs that are also included in the report. The ordinary bugs they reported have not yet been analyzed. This blog post focuses on the 45 reported claimed vulnerabilities. In this large tarball we got individual markdown reports for each finding, together with their associated reproducers and in many cases also their suggested patches for mitigation. With a little scripting and lots of manual fiddling, I submitted all these reports as individual issues on GitHub following our new policy . I paced myself and did this over a period of several days to soften the impact this had on the team. Each report starts in ASSESS mode and once it has been given proper attention we move it to a suitable severity level or we set it to NONE if there is no vulnerability at all there. You can view all the issues yourself . In the curl project we have decided to gradually raise the requirements for severity LOW vulnerabilities. Issues that seem too ridiculous or unlikely we now set to NONE to a larger extent than we have in the past. As just a bug as we like to call them. With this in mind, curl maintainers worked fiercely on the reports of the coming days until we had reached an initial verdict for all the 45 reports – and in the mean time we also received a few additional reports submitted by other reporters. The severity MEDIUM finding we consider to be a LOW and we also agreed with an additional four findings, thus landing on five (11.1%) confirmed. 36 of the 45 findings we consider just bug s, three of them were not even bugs while one of the findings was completely wrong . The wrong one insisted the issue in the complete opposite way and claimed we should patch away our proper way to instead do it the AI’s suggested inferior way – which would introduce the vulnerability it warned for. Vulnerability rate The 11% vulnerability confirm rate is lower than the average in vulnerability reports we have seen in 2026 but the 80% just a bug share is a much higher rate than ordinary reports. The average share of vulnerability reports that report “just a bug” has been at about 43% earlier during this year. Combined, a conclusion must land on that these reports have high quality, but are way too eager to call them vulnerabilities. This should also be seen with the understanding that we as a project have shifted slightly and have higher requirements now. One of the most annoying things with AI generated reports in general is the length of the reports and these ones are no exceptions. It feels like an unwritten law that they must produce very long texts and it feels like the reports are always excessively long no matter the complexity of the issue it reports. In that regard, human reports still easily outperform the AIs’. Several of these findings contain proposed patches for the identified issues. In some instances they have been almost exactly what were necessary, but more commonly the fixing took human effort to analyze the (too) long report and write up the fix for it. Since 41 out of the 45 findings identified problems, we got our hands full. At the time of this writing, eleven of the reported bugs are still not addressed. When an AI finds a bug, they tend to identify problems that no user ever ran into. Users typically report problems when they do something and curl then does something unexpected or it somehow doesn’t satisfy the user’s wishes. In these findings, the reported problems are more theoretical . In many cases this makes the reports less important, and sometimes unlikely to cause problems in real world use cases. We willingly joined this effort as getting flaws and bugs reported helps us improve curl. However, since the severity levels of the findings are of this, shall we say trivial , kind, it feels reasonable to reconsider our participation if this keeps up. Part of the idea of making more vulnerability reports public early is to make it possible for everyone to join in and help. Provide your comments and views on reports still in ASSESS. Submit your proposed changes as pull-requests, or help review changes proposed by others. Help review the advisories for confirmed vulnerabilities to make sure the descriptions make sense and are accurate and that we figure out exactly when they were introduced etc.

0 views

Re: Dying Indies

Cassidy wrote a post titled “Why are all the indie-friendly products dying at the same time?” that it’s worth reading if you’re interested in this kind of topic. I’m not gonna TLDR her post, but I wanna add one extra consideration: a lot of startups are good products, but terrible businesses. And the problem with VC-powered projects is that you can trick yourself into thinking you have a good business when in reality you have a good product, with no real business attached to it. And what end up surviving are good businesses with solid products. Services that started charging a fair and reasonable amount of money from the get-go, delivering a quality service in return. Services that are more like traditional businesses, in a way. And that’s honestly good in my view. Thank you for using and believing in RSS. You're awesome. Send me an email :: Sign my guestbook :: Become a supporter

0 views

Attackers Used Optimizely to A/B Test Malware on Top Websites

At least 178 top web destinations unwittingly served a variety of malware exploits against visitors over the past 24 hours thanks to a security vulnerability involving Optimizely , a company that helps websites customize user experiences and test out new features. Experts say the incident, which saw data-stealing malicious software silently injected into sites like the BBC , CNN ,  Equifax , Ledger and Zoom , was exacerbated by the reality that few popular websites enforce strict rules on the sources of third-party content. The Zoom.com homepage loading the malicious JavaScript file from Optimizely. Image: blog.report-uri.com. Click to enlarge. According to a blog post from the security firm Report URI , on November 16 malicious JavaScript code was served to visitors of 178 organizations through Optimizely’s platform. Report URI researcher Scott Helme wrote that the payload delivered by the malicious Javascript was rebuilt 26 times during the day, dropping a multi-purpose malware kit that could steal payment card data, cookies and screenshots, and swap any cryptocurrency payment addresses for the attacker’s. Helme noted the affected websites also served exploit code custom made to attack known vulnerabilities in older Apple iPhone and iPad devices. Known by such names as “ DarkSword ” and “ Coruna ,” these are zero-click exploit kits that chain together a half-dozen security holes to seize complete control over outdated devices and extract data. “The important lesson here is that trusted JavaScript doesn’t always remain trustworthy,” Helme wrote . “A website can be compromised through a third-party dependency without its own code or infrastructure ever being breached.” Contacted for comment, Optimizely said that on November 16, 2026 it “identified a security incident in which an unauthorized party exploited a vulnerability in the Optimizely Experimentation to add malicious JavaScript to some customer projects.” “We acted swiftly to contain the incident and have fully remediated the identified vulnerability,” reads a written statement shared by Optimizely. “These measures included blocking access to the vulnerable path, deploying a fix, removing the injected code from affected projects, ending active sessions, revoking tokens, and resetting access for affected user accounts. We have also implemented additional protections to prevent malicious code from being delivered in Cloudflare. While the incident has been fully remediated, we are working with third-party experts on a comprehensive investigation.” Many top web properties no longer fully display content unless visitors agree to let often dozens of third parties serve JavaScript, a powerful web scripting language that enables interactive content. JavaScript code is run on the user’s device, and it can read information displayed in the user’s browser and even modify a website’s appearance or content. One reason JavaScript is so heavily used is that it enables fairly precise browser fingerprinting and other ways of tracking visitors and clicks. According to the 2025 Web Almanac by HTTP Archive, the median homepage loads at least 22 JavaScript files. But as the incident with Optimizely shows, a compromise at a third-party vendor’s website can quickly snowball into a supply chain attack against downstream websites that end up serving visitors tampered and malicious JavaScript files. Zach Edwards is a researcher at Infoblox and the co-founder of the ad-tracking service DecryptAds . Edwards said Optimizely is a vendor which often collects data outside of consent flows, with their JavaScript snippets being embedded as close to the top of the page as possible to ensure that it’s one of the first things to render, which is important since the product is primarily built for A/B testing. “So to make the product work as expected, this code is setup to fire immediately on-page load, and not restrict rendering behind a consent dialog box,” he said. “This means that this supply chain attack didn’t require any clicking or consent to trigger — most of the impacted clients would immediately serve up the payload as soon as someone loaded the page, further increasing risks from this type of JavaScript snippet being compromised.” Websites can minimize the chances that a breach at a third-party content provider spirals into a supply chain attack by taking full advantage of “ Content Security Policies ” or CSPs, which specify the domain names that are allowed to serve third-party content. But Edwards said most websites — apart from perhaps the largest e-commerce, social media and financial platforms — don’t even bother with CSPs, or else tend to leave them overly permissive for marketing reasons. “With literally all websites which embed 3rd party JavaScript resources, if you don’t have a content security policy then if any of those partners get compromised, new domains can be injected into your website via JavaScript which won’t be stopped,” he said. “We’re in the age of JavaScript supply chain attacks and yet almost no one is talking about why content security policies were invented and how this is largely the solution for operators, even though it’s not always simple to get it initially deployed.” How broadly deployed were CSPs at the websites impacted by the Optimizely attack? According to Report URI, 68 of the sites had no CSP at all, while 50 of them had a CSP that still allowed the malware payload and the data theft. The company found only 24 of the affected sites (15 percent) had CSPs that fully blocked the malicious payload. Image: blog.report-uri.com. The overall deployment of CSPs across the Web’s busiest sites is somewhat lower — about 10 percent — according to Helme’s site crawler.ninja , which scans the top million websites daily for security issues. Helme said he hopes this incident will encourage more sites to adopt effective CSPs, noting that it could have been far worse: By Report URI’s estimates, the purveyors of this malware attack managed to steal only around $7,500 worth of virtual currency from affected users, as well as an unknown number of payment card records. Helme said he often compares the current widespread lack of CSPs to the Wild West. “Organizations are running all this code, but they don’t know what it’s doing,” Helme said in an interview with KrebsOnSecurity. “This is why we keep seeing such large scale breaches in places [where] there are no checks and rules in place on the code we’re running, so this was kind of inevitable. Once an attacker gets to the point of running code on your site, the question is what do they want to do with that and can they write the script to do it. Now with AI that’s not a problem anymore.” Internet users can control the JavaScript elements allowed to run on webpages by using simple script-blocking plugins like NoScript. But these tools have always only been effective for diehard security and privacy nerds who are willing to put up with sifting through dozens of JavaScript requests on each new website. Happily, modern ad blocking software can handily block most third-party JavaScript requests. Ten years ago, the standard security advice for end users was to install antivirus and enable a firewall. These days, your ad/script blocker is your firewall. We explored several options and approaches to blocking ads in our August 2026 story, Who’s Tracking You?

0 views
Unsung Yesterday

“I’ve spent years on it. Years. On a box.”

Designer Pablo Stanley created a really fun interactive exploration of what it takes to create a seemingly simple “composer” (industry’s jargon for a more sophisticated input field or things like it): = 2x) and (width >= 700px)" srcset="https://unsung.aresluna.org/_media/ive-spent-years-on-it-years-on-a-box/1.2096w.avif" type="image/avif"> = 3x) or (width >= 700px)" srcset="https://unsung.aresluna.org/_media/ive-spent-years-on-it-years-on-a-box/1.1600w.avif" type="image/avif"> It’s a bit outside of Unsung’s purview since a lot of it is very “sung.” The case study focuses on visual presentation, and doesn’t cover systems design or consistency with other things; I even worried at times it could perpetuate an image of a UX designer being a “lone genius,” overindexing on visuals and tactile experiences over more important things, of which there is a ton in the AI neck of the industry woods. At the same time, there are also mentions of flow, and a general drive toward reducing complexity that feel worthwhile. Plus, the theme of details that seem minuscule on the surface, but will all ladder up to a lot of friction in repeated use, is something we cover a lot . Also, I am burying the lede: it’s a really enjoyable and well-crafted experience – don’t miss the sound and music! – and this unique way of talking about interface details could be inspiring in and of itself. You can also watch the entire thing as a video with Stanley narrating, but I personally liked the interactive version more:

0 views
Xe Iaso Yesterday

"No way to prevent this" say users of only language where this regularly happens

In the hours following the release of CVE-2026-123633 and CVE-2026-123007 for the project NGINX , site reliability workers and systems administrators scrambled to desperately rebuild and patch all their systems to fix an HTTP/2 connection use-after-free during reverse-proxy processing when connection slots run low, alongside an HTTP/2 flow-control integer underflow that leads to an out-of-bounds memory copy over TLS, both of which can allow unauthenticated remote code execution on affected servers with HTTP/2 enabled. This is due to the affected components being written in C, the only programming language where these vulnerabilities regularly happen. "This was a terrible tragedy, but sometimes these things just happen and there's nothing anyone can do to stop them," said programmer Dr. Deontae Rempel, echoing statements expressed by hundreds of thousands of programmers who use the only language where 90% of the world's memory safety vulnerabilities have occurred in the last 50 years, and whose projects are 20 times more likely to have security vulnerabilities. "It's a shame, but what can we do? There really isn't anything we can do to prevent memory safety vulnerabilities from happening if the programmer doesn't want to write their code in a robust manner." At press time, users of the only programming language in the world where these vulnerabilities happen continuously were referring to themselves and their situation as "helpless."

0 views

The curl 30 years gource

In association with curl’s 30 year anniversary, I made another gource video visualizing its development. Unfortunately it doesn’t cover the full 30 years since we only have records from late 1999 until today; but it is still decent. Instead I added a little bonus: I’m doing a voice over comment track, explaining and highlighting some facts and details.

0 views
Unsung Yesterday

“No one knows what ⍼ is meant to represent or where it originated from.”

A fun Masto post from abadidea, written some time in between the Microsoft outage, the grounding of all the flights, and the banking problems: My discord has an emoji named “tech debt” - which is just the angzarr, ⍼, the symbol famous for having no known use or agreed-upon meaning but somehow appearing in unicode and now it’s just a part of unicode forever. With so many enormous tech debt bills coming due recently, perhaps you, too, would like to take a moment to appreciate the tasteful angles of the angzarr. This is angzarr as rendered by your computer – ⍼ – and this is it blown up… = 2x) and (width >= 700px)" srcset="https://unsung.aresluna.org/_media/no-one-knows-what-angzarr-is-meant-to-represent-or-where-it-originated-from/1.2096w.avif" type="image/avif"> = 3x) or (width >= 700px)" srcset="https://unsung.aresluna.org/_media/no-one-knows-what-angzarr-is-meant-to-represent-or-where-it-originated-from/1.1600w.avif" type="image/avif"> …and it is true we actually do not know what it is all about. In between 2022 and 2024, computer science student Jonathan Chan ventured out to figure out the purpose of the mysterious character. In a so-far-four-part piece – part 1 , part 2 , part 3 , and part 4 – he compiled the timelines, found old docs and even one physical font block, and talked the a few people. Spoiler alert: The journey must be the reward because the story remains unresolved, and might forever be. There is a lesson I learned when researching keyboards. The answer to the question of “why is a certain key in this place?” most often ends up being “because it was there on the keyboard before this one.” There is natural inertia in not touching something that is already out there, and real cost associated both with understanding something old, and with change management necessary to change or get rid of it. You might assume there is not much damage of angzarr still existing in Unicode – out of sight, out of mind! – but it’s not as simple as that. Complexity will find its way to get to you. Here’s me searching for “right arrow” in macOS’s default character picker, and you can see what should be an easy process is muddled by having to deal with all of Unicode’s character space: = 2x) and (width >= 700px)" srcset="https://unsung.aresluna.org/_media/no-one-knows-what-angzarr-is-meant-to-represent-or-where-it-originated-from/2.2096w.avif" type="image/avif"> = 3x) or (width >= 700px)" srcset="https://unsung.aresluna.org/_media/no-one-knows-what-angzarr-is-meant-to-represent-or-where-it-originated-from/2.1600w.avif" type="image/avif"> A lot of these things might be angzarr-adjacent, used by pretty much no one, yet clouding the results. The thing I want is… well, actually it doesn’t even exist here! I need to search for “rightwards arrow”: = 2x) and (width >= 700px)" srcset="https://unsung.aresluna.org/_media/no-one-knows-what-angzarr-is-meant-to-represent-or-where-it-originated-from/3.2096w.avif" type="image/avif"> = 3x) or (width >= 700px)" srcset="https://unsung.aresluna.org/_media/no-one-knows-what-angzarr-is-meant-to-represent-or-where-it-originated-from/3.1600w.avif" type="image/avif"> Here’s another classic example. Check out the Edit menu in Photoshop – what is one menu item here that feels very much out of place? = 3x)" srcset="https://unsung.aresluna.org/_media/no-one-knows-what-angzarr-is-meant-to-represent-or-where-it-originated-from/4.1600w.avif" type="image/avif"> In between stalwarts like Cut/​Copy/Paste, and so many other universal and technical menu items, there’s one extremely specific and strange entry: Sky Replacement. I’m sure, just like with angzarr, there was once a reason. I’d even say in contrast with the mysterious character, Sky Replacement probably sees use today – perhaps even significant use. But it is such an oddball that its very presence here tells me something went awry in the design process, and no system was in place to correctly understand its added, treacherous weight , and adjust the whole information architecture to accommodate it. But also, it’s easy to point fingers at bloat elsewhere. I think a more fruitful question for anyone reading it would be: what is an angzarr in your app, and what are the hidden costs associated with it being there? I also think the original post also points to a pretty delicious irony. Usually, removing even an extremely obsolete and niche thing is hard because every feature finds its power user, who will shout at you the moment you even approach it. But for angzarr, there was a moment in time – perhaps even many years – where deleting (or demoting) it was perfectly safe. But now, the original poster’s team is using it just because it was there , and now any removal is once again a more complicated proposition.

0 views

Running the full server-side Datasette Python app in the browser with service workers and Pyodide

Datasette Lite is my port of the Datasette Python application to run directly in the browser using WebAssembly and Pyodide . I've released a complete rewrite of Datasette Lite using service workers, and it's now almost indistinguishable from the real server-side application. You can now do all of the following, using a carefully crafted URL to lite.datasette.io : The ability to load specific Datasette references, plugins, and SQLite versions makes this a fantastic tool for linking to demos of work-in-progress features or bug reproductions, without needing to spin up a full web server to serve that demo. As an example, consider the following URL: https://lite.datasette.io/?install=datasette-maplibre&url=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/demo.db&metadata=https://gist.githubusercontent.com/simonw/39fa5d399465766039549912e2b3d291/raw/f6dfba99a75cbb8b5d9386223220eb52272767ee/metadata.yml#/demo/capitals_and_countries%23map=0/4.2/180&color=continent Follow that link and, after a short loading screen, you'll find yourself on a page that looks like this: That's Datasette running the new datasette-maplibre plugin, loading up a database of GeoJSON shapes of countries and displaying both a combined map and individual boundary maps in a table. Let's break down that URL to see what it's doing: The installs that additional plugin from PyPI. You can pass as many times as you like to load more plugins. loads that SQLite database from the provided URL. These URLs need to have open CORS headers - I host files like this in Gists , because they provide an easy way to get open CORS headers on a web-hosted file. loads this metadata.yml file . The metadata file adds HTML descriptions to various tables, and to the Datasette homepage. Visit that homepage here for a guided tour of the other features of that plugin, all defined in the metadata file. is a fragment hash that turns into a location within Datasette - here it's loading the SQL view, then appending another fragment hash to it ( is a URL-encoded ) which tells the map plugin to zoom to a certain location and to set the color of the shapes on the map based on the column in the data. That URL is doing a lot of work! I wrote more about this trick for building URL-addressable software in URL-addressable Pyodide Python environments last year. The full set of supported URL arguments is described in the Datasette Lite README . I've already started using Datasette Lite as part of the Datasette development process. Here's a recent issue describing a pagination bug - I posted a comment there demonstrating the old, broken behavior and the new fix using links to Datasette Lite: Demo of the bug: https://lite.datasette.io/?ref=1.0a42&sql=https://gist.github.com/simonw/75ececf61d50e6e8d50f0c150150ee81#/data/scores?_size=2&_sort=score - click next and the second page is empty. Here's that same page with the bug fixed (running on 1.0a43): https://lite.datasette.io/?ref=1.0a43&sql=https://gist.github.com/simonw/75ececf61d50e6e8d50f0c150150ee81#/data/scores?_size=2&_sort=score Datasette Lite is not a new project. I launched the first version back in 2022 , originally as a bit of a joke (running server-side apps in the browser is pretty funny) but one that quickly started proving its value. The problem with that initial version is that it was a hack . It worked by running Datasette in a Pyodide web worker, simulating requests through that stack, then injecting the resulting HTML back into the top level page using . This worked for basic Datasette, but meant that any feature that used JavaScript failed to work, because script tags in don't execute, and the web worker tricks it used failed to load additional JavaScript or CSS files. The new version takes a completely different approach based on Service Workers . These allow JavaScript to intercept HTTP requests for new pages and resources and serve them from client-side code instead. Datasette Lite registers a service worker for the entire domain. The parent page then creates an iframe that sends requests for Datasette pages to URLs that look like this: Those are regular Datasette URLs, but with a prefix. What's that about? The prefix is necessary because of multiple tabs. Consider the URL above, which loads the demo instance with the plugin. That URL defines a full, custom Datasette instance. You might have that one running in a tab, then one of my other demo links running in another. The service worker for is shared between all of those tabs. If it routed to a single instance of Datasette then every tab would share that underlying instance, no matter what plugins or other settings their URL attempted to configure. Instead, the parent page generates a random session ID and uses it as a prefix for all of the subsequent hidden asset and page loads. The service worker can then use that session ID to route those requests back through the parent page to a web worker running a dedicated Datasette instance for that particular session. (We still need a web worker because Pyodide in a service worker would not be able to maintain state beyond around 30 seconds, depending on the browser. There are a lot of moving parts here!) I had Claude Fable 5.2 generate several SVG diagrams to help explain this. Here's my favorite of those, now embedded in the Datasette Lite README: This system started life back in May as an AI research spike generated using Claude Opus 4.8. It wasn't until November (and Claude Fable 5.2) that I felt familiar enough with how it all works to confidently ship it to production! I added this feature last night as an off-shoot of investigating a potential bug in SQLite . Datasette is meant to work against any released version of SQLite since 3.25 (released in September 2018). There have been 87 further releases since then. Being able to fire up Datasette against a specific version of SQLite is really useful for demonstrating new SQLite features and debugging weird issues. In the past I've used various tricks to get different SQLite versions running with Python on my Mac, but it's not a trivial process. WebAssembly is perfect for this. I can load up a custom SQLite build entirely in my browser, test it there, then discard it when I close my tab. datasette/pysqlite3-wasm-wheels is my new repository which contains WebAssembly compiled Python wheels for pysqlite3 for 163 different SQLite versions. Each version gets a file with a name like this: That's for SQLite 3.54.1, the most recent version. Datasette Lite now takes a special URL parameter, which will accept a version number like , resolve the path to the corresponding wheel file, then fetch that wheel and install it into the Pyodide environment and configure Datasette to use it. Once I'd built the wheels, I decided to have Claude Fable 5.2 build me [this bonus tool]( https://datasette.github.io/pysqlite3-wasm-wheels/?versions=3.54.1,3.54.0&sql=select+json_object(%27a%27%2C+(select+json_array(1%29%29%29) for comparing a SQL query across any selected versions of SQLite. Here's an example showing how differs between SQLite 3.54.0 and 3.54.1: Nothing about how Datasette Lite works is unique to Datasette. Almost any Python application should be able to pull the same trick - running entirely in the browser using WebAssembly and Pyodide, as a cheap way to provide preview environments, demonstrate features, and recreate bugs. C and Rust extensions used to be a blocker for this kind of thing, but any good coding agent can compile those to Pyodide-compatible WebAssembly now. You can even publish them to PyPI as of PEP 783 in April 2026. One catch is databases. SQLite is no problem at all, but running PostgreSQL or MySQL in WebAssembly, while possible, is still a path less trodden. I'd love to see WebAssembly preview environments like these become a common pattern across the Python ecosystem. For Hacker News: Full server-side Datasette Python app in the browser with service workers You are only seeing the long-form articles from my blog. Subscribe to /atom/everything/ to get all of my posts, or take a look at my other subscription options . Load client-side Datasette to browse any SQLite database, JSON file, CSV file or SQL script Select a released version of Datasette to load from PyPI Load a specific commit, tag, or branch name from the Datasette GitHub repository Pick from over 100 versions of SQLite to use with Datasette Install additional Datasette plugins from PyPI or URLs to wheel files, including JavaScript visualization tools

0 views
Unsung Yesterday

“Everything in the digital universe was going to have to get patched.”

Computers spend an enormous amount of time pretending numbers can be other things, and internet infrastructure does the same, constantly working hard to translate impenetrable IP addresses such as into friendly strings like . The details of the infrastructure are above my pay grade, but in principle it works like this: You ask your browser to visit a URL on a domain it hasn’t seen before, so it doesn’t know its IP address yet. Your computer asks a DNS server for that IP address, and the server sends it over. Now, your browser knows where to go, and fires the request directly to the website using its just-learned address. Since you don’t want to bother the DNS server with too many questions, your operating system remembers the answer in its cache for a while, so next time you visit the same server, it can retrieve the IP address from memory. The DNS server in its response even handily provides a few parent addresses to cache too (e.g. ), to further save on future network traffic. Now, I glossed over one part we gloss over every day just to say sane. “The server responds” is its own complex challenge. The Internet’s series of tubes are not those rubber hoses where one opening ends up next to someone’s mouth, and another next to the other person’s ear. No, on the internet, things are divvied up in packets that all travel together side by side, squeezed like packages on an Amazon truck, and they are only dispatched to the right precise destination at the end of their journey. Even though the DNS logic was created during an early era of the internet where computers trusted each other more, the creators recognized the risk of someone else impersonating the DNS server, and sending their own invalid response to your “translate this domain into the IP address, pls” query. So, a simple authentication system was built. When asking the server, you’d include a number only you knew – in effect, a simple password. Then, when the DNS responded, it included the same number. If you saw your number and the domain you asked about, you could have a pretty high confidence that who was responding was the server you originally asked. A wrong number? Means a mangled transmission or an impersonator, so just throw the whole thing away. This seems like a primitive system, but this sort of security by unguessability happens all the time. When you start a new Medium post, you will see this in its URL bar: = 2x) and (width >= 700px)" srcset="https://unsung.aresluna.org/_media/everything-in-the-digital-universe-was-going-to-have-to-get-patched/1.2096w.avif" type="image/avif"> = 3x) or (width >= 700px)" srcset="https://unsung.aresluna.org/_media/everything-in-the-digital-universe-was-going-to-have-to-get-patched/1.1600w.avif" type="image/avif"> The part is just a number. That number is the entire security. There’s nothing preventing you from guessing that number to get to my draft, or methodically start testing each number one by one – except the space extended by 12 hexadecimal digits, at over 281 trillion numbers, is basically astronomical, and you are not. If you checked one URL per second, it would take you 9 million years. If you checked a hundred a second, it would be 60 millennia. 10,000 per second? Still over 600 years of work. This is effectively a monkeys with typewriters scenario, let alone that at some point during those 600 years Medium would also recognize what you’re trying to do, and their systems would stop responding to your efforts and perhaps send an appropriate three-letter agency your way. This system works because the number space is incredibly vast. But for the DNS query we talked about it was only 65,536 numbers. Enter Dan Kaminsky, a security researcher with a reputation for tackling the unfun, pedestrian issues no one else cared about. In 2008, Kaminsky found himself poking at the fringes of DNS, trying to find problems and vulnerabilities. He was specifically interested in helper DNS servers. See, the caching I mentioned doesn’t just happen on your computer. DNS servers are arranged in a small hierarchy and also have a bunch of helper servers (called “public resolvers”), popular for their speed. If a helper server doesn’t know something, it asks a server closer to the truth, starting with one of the supreme court of few “root servers” at the core of the whole system, and then down the chain, sometimes a few more times. Then, after receiving the answer, it sends it over to whomever asked – but it then caches the answer for a while, too, to prevent all this effort in case the same computer or another one asks about it again, too. This means that if you could convince that helper server to cache a wrong answer, you could trick a potentially significant swath of the internet to go to a wrong IP address – sending, say, all traffic your way, and then stealing people’s passwords and credit card numbers. But you’d still have to know the one right magic number out of 65,536. This is where Kaminsky tried something different. 65K numbers is a lot for a person, but not for a computer. What if you could, indeed, monkey-and-typewriter this whole situation? What if you did it by brute force ? Say, you ask a DNS server for an uncommon version of a common URL (e.g. ) so you know it won’t have it cached. No cache means that server has to ask a server closer to the core, which takes a bit of time. But before that happens, you fake an answer from that parent server to the server you just asked. No, scratch that, you fake 65,536 answers. Now, you know the domain you asked about, so that part will match for sure. You don’t know what secret number the server communicated to its parent server, but you know that out of all the answers you generate, one will have to match. Now, you just need some luck of timing. If your answer will arrive before the official answer, it will be treated as the official one and cached – and the official one coming after yours will be rejected. (Here’s a pretty horrible real-life example: Imagine someone wanting to hijack you as you land at the airport. They know where you land, but they don’t know your name – so instead of trying to guess, they just deploy a few dozen limo drivers, each one holding a card with a different popular first name. If they time it well, you will see the fake limo driver before your limo driver – and that’s the driver you will follow to your doom.) And… the real server wouldn’t just respond with an IP address . It would also, as was customary, thoughtfully include an IP address for the entire domain while you’re at it, just to help you in the future. If your fake answer included that too, you could theoretically insert yourself in front of Amazon’s traffic. Kaminsky tried it… and saw it succeed. The consequences were huge. He later recalled: Once I saw it work, my stomach dropped. I thought, “What the heck am I going to do about this? This affects everything.” An article by Erica Naone written around that time adds: Kaminsky’s technique could be used to direct Web surfers to any Web page an attacker chose. The most obvious use is to send people to phishing sites (websites designed to trick people into entering banking passwords and other personal information, allowing an attacker to steal their identities) or other fake versions of Web pages. But the danger is even worse: protocols such as those used to deliver e-mail or for secure communications over the Internet ultimately rely on DNS. A creative attacker could use Kaminsky’s technique to intercept sensitive e-mail, or to create forged versions of the certificates that ensure secure transactions between users and banking websites. “Every day I find another domino,” ­Kaminsky says. “Another thing falls over if DNS is bad… I mean, literally, you look around and see anything that’s using a network–anything that’s using a network–and it’s probably using DNS.” And here’s Wired with its typical, exaggerated take: The problem had been coded into Internet architecture in 1983. It was 2008. Somebody must have fixed it by now. He typed a quick series of commands and pressed enter. When he tried to access the Fortune 500 company’s Web site, he was redirected to an address he himself had specified. “Oh shit,” he mumbled. “I just broke the Internet.” Kaminsky asked his friend and DNS expert Paul Vixie, who grasped the severity of the situation : I realized we were looking down the gun barrel of history. It meant everything in the digital universe was going to have to get patched. Together with Vixie, they alerted Department of Homeland Security, and then execs at networking companies. The plan was hatched: he’d work with biggest DNS vendors to quietly patch the system, and only a month after that, once everything was already corked up, he’d release the details of the finding to the public. The patch was deployed on July 8, 2008. It was as cheap as possible, basically vastly increasing the number space from 65,536 to billions (Vixie compared it to dogshit, but there wasn’t time for anything else), and Kaminsky planned to announce the details on August 6. But there was an unexpected last-minute kink in the plan, which was… someone’s curiosity. Apparently, one security expert saw the patch, and from pondering that patch figured out the problem, and exposed it prematurely on July 21. Luckily, by then things were already relatively patched up, and no one could nefariously use the original flaw. This cache poisoning problem was a nightmare some compared to Y2K, and likewise avoided – but this one without any of the limelight. Kaminsky was inducted to an Internet Hall of Fame for detecting the problem and eventual successful effort in containing it. Unfortunately, this happened only a few months after his untimely death at 42 , in early 2021.

0 views
Kev Quirk Yesterday

2026-11-17 15:52: Thinking about trying #LittleFedi but I'm not sure how it would fare on a larger...

Thinking about trying #LittleFedi but I'm not sure how it would fare on a larger fedi account. I have ~13k followers - has anyone with an account of a similar size been using it? Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️ You can reply to this post by email , or leave a comment .

0 views

The NVIDIA Bubble

If you liked this piece, you should subscribe to my premium newsletter, and you can subscribe on the following links: $70 a year , $18 a quarter , or $7 a month . In return, you get a weekly premium newsletter that dives deep into the finances of the AI bubble. Over the past few months, I’ve published a two part guide to the world of AI debt, an analysis of the (dubious) impact of generative AI on the global economy , deep analyses of the biggest players in the AI infrastructure space like NVIDIA (part one and two ) and Oracle (part one and two ), and the role private credit is playing in funding AI data centers , and how private equity, reeling from years of successive failed software acquisitions, is doubling down on the AI bubble .  Last week’s piece was a 13,000-word deep dive into Megaspeed — the shady firm at the heart of Jensen’s downfall, which somehow bought billions of GPUs despite being, just a few years ago, an unsuccessful developer of free-to-play mobile games. It’s all very weird, and I spent a lot of time making sense of it all.  On Friday, I’m going to share how we fix the tech industry, and how we stop the next bubble before it even starts.   If you want to get in touch — and especially if you have any juicy information about Anthropic, OpenAI, or any other companies in the AI bubble — hit me up on Signal at ezitron.76. I’m also on IB on your Bloomberg Terminal.  This weekend, thousands of horrible little men cried out for the return of their pervert emperor, demanding that NVIDIA restore disgraced CEO Jensen Huang, who resigned after it leaked that he’d had multiple affairs , one of which (as described in my free newsletter last week) was with a woman called Alice Huang who may or may not have been a Chinese spy, but was most certainly selling restricted AI chips to Chinese companies through a company called Megaspeed ( covered in depth in my premium last week ).  Within the space of a week, illegal chip sales routed through Alice Huang’s empire went from $4.8 billion to “at least” $7.5 billion , to $12 billion between March 2024 and June 2025 according to the Wall Street Journal.  The Information also reported that companies connected to Alice Huang invested in DeepSeek, the famed Chinese AI lab that spooked the world back in Q1 2025 for, ironically, suggesting that we didn’t need to buy as many NVIDIA GPUs. Let’s be clear about something: Jensen Huang resigned and is not coming back. To paraphrase Semafor’s Rohan Goswami , NVIDIA’s board was packed with allies , deliberated at length about what to do (and didn’t really want to do it) , and has both let him walk and done nothing to retain him, I’d personally guess because the probe the board is running already has some idea of wrongdoing such as, I dunno, the giant illegal smuggling ring that has been covered at length by basically every media outlet. NVIDIA has also said it was not considering bringing him back . Even now, a week into this bizarre crisis, few are truly reconciling with the allegations raised in May 2026 by Culper Research’s short report , namely that 20% or more ($43bn+) of NVIDIA’s FY 2026 sales came from selling through China. Even two profiles of Culper in the New York Times and Wall Street Journal fail to substantively discuss the material of the guy they’re god damn profiling. That’s because, to paraphrase Culper’s own work, Megaspeed is just the tip of the iceberg. As I covered last week , Culper directly connects Megaspeed to popular AI server manufacturer Supermicro , whose co-founder and board member Wally Liaw was arrested with several co-conspirators back in March for trying to sell over $2.5 billion in chips to a Chinese passthrough entity Culper believes is a Megaspeed affiliate. Liaw had previously resigned in 2018 due to an accounting scandal ( per short seller Hindenburg ), only to be rehired in 2021 as a consultant and reinstated to the board in 2023. Let me spell it out for you: a co-founder and member of the board of one of the largest manufacturers of AI servers was arrested for selling chips to China, specifically to a company affiliated with the very same smuggling operation that Alice Huang ran.  Supermicro is a huge, publicly-listed company with a history of accounting scandals. 70% or more of its revenues come from selling AI servers powered by NVIDIA GPUs, and back in August 2024 — months into Megaspeed’s $12 billion purchases of eventually-smuggled GPUs — Supermicro was NVIDIA’s third-largest customer, around that it was facing allegations of accounting manipulation and sanction evasion by Hindenburg that never went anywhere because our markets are broken and our SEC is trash. Anyway, my point is that this story is just getting started, and that those in the Copium dens are trying to reframe this as a “guy who made a mistake” rather than a philanderer that appears to have overseen the GPU equivalent of Iran Contra. Whatever rumors you may have read about a potential Jensen comeback appear to be peddled by the most desperate of AI boosters who, based on reports on CNBC , do not appear to be aligned with what Huang himself has said.  And really, why do they want Jensen back so bad?  It’s simple: Jensen Huang’s value has nothing to do with GPUs or AI, and everything to do with keeping the AI bubble inflated. Perhaps it’s more appropriate to call it the NVIDIA Bubble , because without it, the AI industry doesn’t really make much sense.  As I’ll make clear later in this piece, NVIDIA played an active role in keeping the wheels of the AI bubble turning — funding model labs, buying startups, and backstopping compute for Neoclouds, thereby allowing them to raise debt. Its interventions didn’t merely sustain the industry-wide spending spree, but amplified it. In the process, NVIDIA transformed the AI bubble to something that attached itself to the personal wealth of ordinary people — often without them realizing it.   As the stock prices of NVIDIA (and the rest of the Magnificent Seven) became engorged on AI-related hysteria, the exposure of ordinary (and unwitting) savers to the AI bubble grew. Investors who followed the mantra of “don’t buy individual stocks, just buy index funds” ended up in a position where, due to the top-heavy nature of the S&P 500 , and the predominance of mega-cap tech stocks, a significant chunk of their wealth is gambled on the question of whether AI is a bubble or not. And that’s without mentioning other factors — like how insurers and pension funds are exposed to the AI bubble (and, in particular, the AI infrastructure buildout), either directly or indirectly through their investments in private credit.  Or, put succinctly, if NVIDIA sneezes, the retirement savings and personal investments of ordinary retail investors will catch a cold. And if NVIDIA catches the flu, we’ll see the wealth of retail investors contract the fiscal equivalent of pneumonic plague — the type that Soviet scientists cooked up in a Siberian lab during the Cold War, and that gives Annie Jacobsen nightmares .  Despite many saying “NVIDIA isn’t NVIDIA without Jensen,” in truth it’s still selling the same chips, has the same fab space and supplier agreements, and outside of his horrible personality (and cult of personality ) seems virtually identical. Back in August, NVIDIA said that it expected 70% year-over-year growth in Fiscal Year 2028 (starting February 2027) , which suggests — unless something has materially changed! — that NVIDIA had clear expectations and agreements to hit those targets. CEO Colette Kress should, if you believe everything that’s been said over the last few years about “insatiable demand,” have absolutely no problem selling just as many GPUs at just as fast a rate… …unless, of course, there’s another reason that “NVIDIA isn’t NVIDIA without Jensen.” The truth is that what people actually mean is that “NVIDIA isn’t NVIDIA without Jensen using its balance sheet to grow at a high pace involving constant, quasi-legal-to-illegal dealmaking involving channel stuffing and illegal smuggling.” The Wall Street Journal reports that Jensen Huang had told his finance team ( in August, the very same month it raised guidance) that the company was facing a glut of GPUs and had over-ordered capacity at TSMC and with memory manufacturers, necessitating further circular financing: I dunno man, I’m no securities lawyer, but I feel like worrying that you have an oversupply of chips and then telling investors that you actually expect to sell more chips than ever feels like some sort of stock manipulation, and it wouldn’t be the first time NVIDIA’s done it in the last year. Back in September 2025 , it announced it would invest $100 billion in OpenAI to build 10GW of data center capacity, with Jensen Huang saying live on CNBC that there had “never been an engineering project of this complexity and this scale ever,” referring to a deal that he would dismiss as “ never a commitment ” five months later, because it was only ever a “ letter of intent .” The truth is that Jensen Huang lied. You can dress it up in terms of “memoranda of understanding” or “letters of intent” not actually meaning “a contract has been signed,” but Jensen Huang went on CNBC and did everything he could to convince you that NVIDIA was investing $100 billion in OpenAI to build 10GW of data centers, much like he went on CNBC a few months ago to convince you that (and I quote the headline) “NVIDIA [had lined] up $500 billion in financing” despite these being A) memoranda of understanding and B) no money ever changing hands or being raised by anybody to do anything and, to quote Bloomberg , said $500 billion figure having “no obvious provenance.” There is no other way to interpret this other than intentional manipulation of the markets perpetuated by the mainstream business and technology press, all because nobody would ever push back on Jensen Huang.  And that’s because everybody knows, deep down, that we’re all living in an NVIDIA Bubble — a financial mania manufactured, maintained and sustained using NVIDIA’s credit rating and cash to brute-force the markets and the media into believing in anything. While the AI bubble is relatively young, the NVIDIA bubble has been inflating for over a decade. I don’t even mean that derisively! Jensen Huang and NVIDIA were formative to the entire AI bubble, both in creating the infrastructure, demand, and even the underlying research that eventually led to the LLM boom.  Way back in August 2016, Jensen Huang delivered “the world’s first AI supercomputer” — the DGX-1 — to a small AI lab called OpenAI that had recently raised money from yCombinator’s Sam Altman and Tesla/SpaceX’s Elon Musk . Three months later, OpenAI announced it was moving to Microsoft Azure , training on NVIDIA Pascal GPUs in the earliest days of AI compute. A few years later, NVIDIA found itself in flux, with a beat on earnings in February 2019 clouded by a decline in both hyperscale and cloud sales , but Jensen Huang was already working on an acquisition that would change everything, agreeing to buy Israeli high-speed networking firm Mellanox that March for $6.9 billion in cash , outbidding both Microsoft ( which was already using its tech at Azure ) and Intel for the InfiniBand technology that would eventually allow NVIDIA to network together clusters of AI servers.  Four months later in July 2019 , Microsoft would invest a billion dollars into OpenAI “...to build “new Azure AI supercomputing technologies.” Four months later in November 2019 , NVIDIA and Microsoft would announce that Azure would now offer a “a new kind of GPU-accelerated supercomputer in the cloud on Microsoft Azure,” networking together up to 800 NVIDIA V100 GPUs using Mellanox’s InfiniBand tech, and the first time I can find where you could rent out massive clusters of AI GPUs. Microsoft and NVIDIA engineers even trained their own conversational AI model called BERT . The deal itself wouldn’t close until April 2020 , and a month later in May, Microsoft and OpenAI would announce that they had built a 10,000 GPU “supercomputer” together, with sources telling The Register that it was likely made up of AMD CPUs and NVIDIA V100 GPUs.  The same month, NVIDIA would release its A100 GPUs , which remain somewhat of a workhorse for AI Compute, and were a huge commercial success. Another significant milestone came two months later in July 2020 , when NVIDIA would publish a blog about how OpenAI researchers had released a paper describing how they’d trained GPT-3 using its Volta-era V100 GPUs ( released in 2017 ).  In August 2020 , NVIDIA’s data center revenue would outpace its gaming revenue for the first time in the company’s history, “aided largely by the Mellanox acquisition” per Holger Mueller of Constellation Research.  In other words, Jensen Huang and NVIDIA were far more foundational to the AI bubble than Sam Altman or Elon Musk, quite literally buying and building the company and the infrastructure necessary to build large language models.  While June 2017’s Attention Is All You Need paper absolutely kicked off the transformer-based model boom, NVIDIA and Baidu’s late 2017 research into mixed precision training that allowed model developers to use nearly half as much memory during training without losing accuracy, and also train faster on NVIDIA’s newer chips, a technique that became the standard in the early days of LLMs, shouldn’t be overlooked. In August 2021, OpenAI would launch Triton , a Python-esque coding language specifically built to make it easy to write code that ran on GPUs that would become foundational to the entire AI boom. Three months later, Microsoft announced that OpenAI’s GPT-3 was now available on an invite-only basis to customers via its new Azure OpenAI Service . Then came 2022 — a rough year for everybody, per my second Hater’s Guide To NVIDIA :  NVIDIA’s Q3 FY23 (November 2022) earnings were rough , missing on analyst expectations , though not as rough as Q2 FY23, when it had to pre-announce that it had missed on guidance by a little under $2 billion .  While NVIDIA had started shipping its H100 GPUs with data center sales eclipsing its gaming revenue by about $2.2 billion, it had yet to fill the hole caused by the post-pandemic dropoff of PC and graphics card sales or, more aptly, the hole left by the collapse of cryptocurrency mining.  And then a mere two weeks later, Sam Altman announced the launch of ChatGPT , creating the greatest sense of FOMO in the tech industry’s history. Per the New York Times , “...the entire agenda of [Google] had changed” as a result of ChatGPT, and Satya Nadella was “gleefully” ordering billions of dollars of NVIDIA GPUs.  By March 2023, every major hyperscaler was now offering NVIDIA H100 chips , and a month later in April 2023, NVIDIA would invest in the Series B round of CoreWeave , a former Ethereum miner backed by Magnetar Capital, which was famous for backing dodgy CDOs during the Great Financial Crisis .  Somewhere in early 2023, CoreWeave got a new customer — NVIDIA itself, according to The Information . This deal was part of a wider strategy dubbed “Project Osprey,” wherein NVIDIA would spend $1.3 billion over four years to rent back its own GPUs for whatever reason, making it the second largest customer behind Microsoft, who was renting capacity for OpenAI. That Microsoft deal would eventually lead to the creation, per The Information , of the first GPU-backed financing led by private equity firm Blackstone, emphasis mine: This deal would, as The Information notes, become the template for basically all data center financing, rationalizing the notion of lending unprofitable, debt-filled neoclouds like CoreWeave billions of dollars to build data centers as long as some sort of other counterparty agreed to rent capacity in the future. And when lenders needed further justification — by which I mean proof of cashflows — they’d happily tick the box because NVIDIA had agreed to pay its customers to rent back the GPUs that all that debt was being raised to buy. In September 2023, Bernstein analyst and alleged professional Stacy Rasgon attacked “Twitter randos” for suggesting, and I quote , that it was a conspiracy theory to believe the following: Three years later, Rasgon has now downgraded NVIDIA , and worries about the following: Stacy was, of course, talking about Jack Gamble (AKA JG_Nuke) who had repeatedly critiqued CoreWeave as a pump and dump inflated by NVIDIA in its earliest days in 2023.  I mention this because I believe analysts and the mainstream media have been critical to inflating the NVIDIA Bubble, and in laundering the reputations and rationalizing the inherent lunacy of the AI bubble. As long as NVIDIA “beat and raised” — as in beat analyst expectations and raised guidance — everybody was happy and looked away from the many, many things wrong with this picture. And 2023 was the year that NVIDIA’s circular financing took off, with the company investing in Cohere , Synthesia , Runway , Hugging Face (which it would eventually acquire), Perplexity , Together (an inference company that also buys GPUs), and Mistral . At this point, NVIDIA’s bubble had begun to inflate, with a landgrab to invest in anything AI related and to buy as many GPUs as possible, per me in Part 2 of my Hater’s Guide To NVIDIA: What was missing, of course, were revenues. But none of that mattered! A captured media ecosystem and a brainless market credited AI with basically any related revenue growth for anybody who bought NVIDIA GPUs.  Behind the scenes, Jensen was doing everything he could to keep growth going, making sure CoreWeave was able to raise more than $10 billion in debt from a handful of very specific bankers that he’d conned into believing the idea that building endless AI data centers would create infinite cash.  By February 2024, the sudden influx of demand led to Jensen ruefully discussing the “fairest” way to decide who gets its GPUs , and a month later he’d announce Blackwell , the next-generation NVIDIA GPUs that cost tens of thousands of dollars more depending on the configuration , specialist cooling and entirely new racks, massively increasing the cost of data centers and, in turn, increasing NVIDIA’s revenues.  In June 2024 , Jensen would claim that “the more you buy, the more you save” under what he called “CEO Math,” but I would call “complete bullshit”, per Business Insider: That, by the way, is about as much “skepticism” as you’ll find in this era, and why the bubble was allowed to inflate. At no point can I find any substantive conversation about the actual benefits of buying NVIDIA GPUs , or any of the financial returns , or really anything other than…well…fluff.  You see, everybody loved the AI bubble. Liking AI allowed you to talk about something new and exciting , and nobody would argue with you if you said you thought it was going to make everybody a bazillion dollars. They would, however, attack you viciously if you dared to suggest anything was wrong — something they still do to this day! — because, as Jensen realized, AI had become load-bearing for the entire stock market, even though the only people making money on AI were NVIDIA and other semiconductor companies. And somewhere between 2023 and 2024, Jensen met Alice Huang (no relation) , and between March 2024 and June 2025, per the Wall Street Journal , Megaspeed would buy “nearly $12 billion worth of top-of-the-line NVIDIA chips” and send them to Chinese firms, including Blackwell chips that it claimed had demand that was “well above supply” in August 2024 and by October 2024 was “ sold out for the next 12 months ,” partially as a result of Jensen Huang creating that demand via CoreWeave and in his dealings with Megaspeed. In 2024 alone, NVIDIA would invest in data center firm Applied Digital (CoreWeave’s landlord), as well as neocloud Nebius and Stargate Abilene data center builder Crusoe . In 2025, it would anchor CoreWeave’s IPO ( which couldn’t have proceeded without NVIDIA’s help ), agree to pay neocloud Lambda $1.3 billion over four years to rent back its GPUs , invested twice in British neocloud Nscale, invested in Crusoe again , and extended its deal with CoreWeave to pay it $6.3 billion . In August 2025 , CFO Colette Kress would sing the praises of “extraordinary” and “soaring global demand,” and in October 2025, Jensen would claim ( and Reuters would report ) that there were “$500 billion in bookings for its AI chips.” What did that mean? Who knows. Nobody asked. Nobody dared harsh the flow. Would NVIDIA make $500 billion in that period? No. Huang would claim in NVIDIA’s Q3 Fiscal Year 2026 earnings ( November 2025 ) that “compute demand keeps accelerating and compounding across training and inference — each growing exponentially.”  All of this was part of the kabuki theater of NVIDIA — claims that there was “astonishing demand” for AI GPUs at a time when it was doing everything it could to inflate that demand by funding companies explicitly to raise debt and buy GPUs. The first sign of desperation began in September 2025, when Jensen Huang would go on CNBC and announce that non-existent deal with OpenAI . Per the Wall Street Journal , talks never progressed past their earliest stages. This did not stop anyone from reporting the deal as done for literally months — its intention was entirely to create the imaginary sense of “demand” that would mean you have to do whatever Jensen needs to get his GPUs.  And, of course, to continue fooling the media into believing that there was “incredible demand for AI.” In a December 2025 piece, TIME would mention that Jensen Huang was “unhappy,” because NVIDIA “had to publicly declare that its China revenue had shrunk to $0,” leading to him lobbying the Trump administration to change chip export rules that NVIDIA was at the time vigorously violating. By the end of 2025, NVIDIA had also agreed to around $27 billion worth of cloud compute agreements in total — literally agreeing to rent back its GPUs from its customers — and as of its last earnings report, these agreements had grown to a remarkable $36 billion. Not once during these three years did we ever learn what revenues Microsoft, Google, Amazon, or Meta made from renting out NVIDIA GPUs, but we didn’t need to, because the media was all too happy to claim that Microsoft and Google’s bets on AI had paid off as early as 2024. It didn’t matter that OpenAI or Anthropic lost billions, it didn’t matter that CoreWeave was a time bomb , it didn’t matter that NVIDIA was literally paying its customers to buy its GPUs , it didn’t matter that NVIDIA was effectively stepping in whenever anyone had any doubts about the AI bubble , as long as hyperscalers — and most importantly NVIDIA — kept beating on estimates and raising guidance. Even though, as I’ve mentioned, the actual revenues from AI are nowhere to be seen. Thanks to Bloomberg , we eventually found out that Microsoft’s Fiscal Year 2026 AI revenues were around $34 billion, with $24.1 billion coming from OpenAI, meaning that $265 billion in capital expenditures since 2022 (at the time) had bought Microsoft a single-digit AI business outside of feeding itself money by investing in OpenAI. As we can see in hindsight, it’s clear that there never was “insatiable demand” for AI chips outside of Jensen Huang’s pressure tactics, some of which involved claiming there was “limited availability” of chips that he himself made sure were in limited supply, mostly by making sure that NVIDIA-incubated customers bought them using either NVIDIA’s investment or debt raised using that investment, like when NVIDIA put in at least a billion dollars into an SPV that raised money for Elon Musk to buy NVIDIA GPUs in January 2026 . And the most-damning proof we’ve had of there being no real “demand shortage” is that NVIDIA has been forcing customers like Amazon to take billions of dollars of GPUs months in advance of when they’d need them as part of an “early rack receipt program,” with Business Insider revealing one crucial piece of information: In other words, Jensen Huang said that if you don’t buy the chips now — even though you have “no clear forecasted path” to install them — you won’t get them when you “need” them. As I’ve said recently, based on analyses of earnings statements and documents viewed by this publication, I believe there are over $200 billion worth of NVIDIA GPUs that are sitting in warehouses waiting to be installed as a result of artificial demand pressures created by Jensen Huang and NVIDIA.  This is how NVIDIA has beaten expectations and raised guidance basically every fucking quarter for the past two years — circular financing, illegal chip smuggling and channel-stuffing.  The most important rule of living in the NVIDIA Bubble was that everybody kept in line, saying there was always more demand for GPUs, always more demand for AI, and that everybody was making lots of money… even though none of that was actually true. Back in August, I used analyst notes to prove that the vast majority of AI demand — 70%+ of revenue and 80%+ of compute demand — was from Anthropic and OpenAI buying compute, and the sheer power of the NVIDIA Bubble was such that people simply ignored it because it was uncomfortable to think about. Last week, Sam Altman said the quiet part out loud at a Samsung conference , emphasis mine: One particularly-childish view that I’ve heard is that if NVIDIA falters, AMD or Broadcom could potentially “pick up the slack” and “capture the demand,” as if said demand was not entirely a result of Huang’s dealmaking and his aggressive use of NVIDIA’s balance sheet. Your open source model company fails to close a financing round? NVIDIA will pay $6 billion to “license” its tech and take some of its employees . A shitty AI search company that nevertheless buys hundreds of millions of dollars’ worth of compute starts running out of money? No problem, NVIDIA’s got billions to make sure Perplexity keeps chugging . CoreWeave’s landlords get worried about it not making its lease payments? No problem, NVIDIA has backstopped the leases . Anthropic needs another $10 billion to make prepayments on its compute? No problem, NVIDIA is kicking $10 billion into its IPO .  There’re also very few other companies out there like NVIDIA, which had twelve-month trailing free cash flows of $127 billion through its latest quarter, second only to Apple, which had $136 billion.  As of its latest quarter, NVIDIA also had about $99.4 billion in total liquidity — more than AMD ($15.8 billion) and Broadcom ($24 billion) combined, with better credit (AA versus A and A- respectively), lower net debt, and an interest coverage ratio (IE: how many times it could pay its interest expenses with its operating income) of 435x compared to Broadcom’s 17x and AMD’s 65x. Additionally, NVIDIA has significantly more capacity booked with TSMC and the memory cartel, largely as a result of being able to afford it and justify it with upcoming revenues, even if said revenues were artificially inflated with circular deals. In other words, NVIDIA has more cash, better credit, a better balance sheet, and spent three fucking years building hype, FOMO and funding its own customers so that by 2025 there were entire companies that existed functionally to either buy or rent NVIDIA GPUs.  This is a plan that took years — or a decade, depending on how you think about it — to execute, and its collapse was inevitable, because it’s clear that despite his bravado and confidence, Jensen Huang was desperate and would do literally anything to keep the beat-and-raise machine alive.  The Chinese smuggling was and is one of the single-most brazen acts I’ve seen in the history of capitalism — a flagrant, well-documented campaign of export control violations perpetuated at times in broad daylight, ignored by much of the press, to this day referred to by some as a “conspiracy theory” despite GamersNexus’ smuggling report from August 2025 , the New York Times reporting in October 2025 , Bloomberg’s reporting in December 2025 , Wally Liaw of Supermicro’s arrest in March 2026 , and Culper’s massive short report in May 2026 proving in vast detail that NVIDIA is absolutely involved in illegal smuggling of GPUs to China. Yet the most-damning part of all of this is how willing everybody was to ignore the circular financing, and no, I’m afraid that all the grab-bag articles saying “wow, NVIDIA sure has invested in a lot of its partners!” don’t count.  The media rubber-stamped every single circular deal throughout the AI bubble because there were hundreds of millions or billions of dollars attached — even if they weren’t real! — from NVIDIA or one of NVIDIA’s customers, all without any consideration or discussion of how unstable it was or, more importantly, how NVIDIA was inflating its revenues by creating these circular relationships. While the cries to restore Jensen Huang have fallen on deaf ears, even if he were to return, it’s clear that the circular financing era was coming to an end regardless of who was wearing the leather jacket.  And it’s important to measure how incredibly large a loss that is. Per The Wall Street Journal : That means 27% of all venture capital funding in 2026 flowed from NVIDIA, and those that didn’t lock down their funding are incredibly worried, including Nscale, which, per the FT , needs more money to complete its massive contract with Anthropic: Bloomberg also reports that NVIDIA invested $2 billion in Nscale in September — a billion more than we knew — but apparently said billions weren’t sufficient, and it’s unclear what’ll happen next, much like it’s unclear what happened to NVIDIA’s supposed offer to buy Reflection AI, per the WSJ, or its investment in Thinking Machines: Huh, that’s weird. Why would NVIDIA invest in or buy AI labs?  Ohhh. Right. The NVIDIA Bubble might get pricked if anyone buying AI compute — even those who quite literally can’t afford it! — blinks for even a second about the prospect of buying more.  And that’s been the core of the Jensen Huang hustle — NVIDIA invests, NVIDIA rents, NVIDIA backstops, or NVIDIA introduces you to Microsoft, Anthropic, OpenAI, or Meta, one of whom is a customer of basically every single AI lab, which should tell you about how much demand for AI there really is. The Journal’s piece ends with a gutpunch that tells the entire story of the AI bubble:  Without Jensen, there is no AI bubble, because if anybody else acted like Jensen they’d look like a fucking lunatic, mostly because the NVIDIA Bubble’s purpose was to rationalize the irrational and provide justifications for basically anything. If you worried that your customer couldn’t pay you, Jensen would invest. If you worried that you couldn’t pay your vendors, Jensen would backstop your leases.  And despite the constant threat of demand outstripping supply, Jensen could always get you more GPUs — and, per Elon Musk , many of his deals were “a handshake” rather than a “written contract,” with a “purchase order coming together at some point later.” One has to wonder how many of the “deals” announced by NVIDIA in the last few months — or any of that egregious forward guidance — was based on Jensen’s “handshakes,” or his ability to mobilize suppliers and vendors and financing under the banner of “insatiable demand for AI.” Except…it’s very clear that era is over. Per the WSJ , Jensen was warning as much at a conference in October, emphasis mine: This is three very specific warnings baked into one: While the third point is obviously bollocks, the first two suggest both tightening financing conditions and NVIDIA’s unwillingness to bankroll its own bubble, and a suggestion that with or without Huang, the end was already approaching at high speed. And without Jensen — and the central bank of AI — there’s very little keeping this entire thing afloat. While hyperscalers might have been afraid of pissing off Jensen and getting put in Jensen Jail , I don’t see Amy Hood (CFO of Microsoft) being intimidated by the meager presence of Colette Kress demanding that she (and other hyperscalers) take billions of GPUs in advance.  Without Jensen, NVIDIA loses its don (credit to Michael Burry for that one) and its ability to use mob-like tactics to push around its customers or constantly provide, per the New York Times , questionable deals that nevertheless made bankers billions of fees: Huang’s cachet was so significant that he was able to bully the CEOs of effectively every major private equity firm into lying on television about a non-existent $500 billion deal to fund data centers, emphasis mine: Jensen’s presence was not just finding the deals , but calling up the right bankers at the right time and giving them explicit or implicit guarantees that NVIDIA’s balance sheet would hold up the other end of the deal. And without Jensen, the NVIDIA Bubble bursts, leaving behind an industry that must reconcile with the consequences of its destructive mania. Whatever value you may or may not think AI has, it is not paying for itself. It is a continual drain on the debt markets and the venture capital industry.  Anthropic has $141 billion in cash, wants to raise another $70 to $90 billion, and will not be cash-flow positive before 2030 according to underwriter Goldman Sachs . It also has $895 billion in compute commitments, which is the real reason NVIDIA is investing $10 billion at its IPO — Jensen doesn’t care if the chips ever get rented, he cares that somebody has a reason to buy them, or issue debt to the company doing so. In reality, the “demand” for AI GPUs was manufactured by Jensen Huang and the hype cycle he created through exploiting the desperation of a flailing tech industry. The industry’s lead cheerleader and House Whip was also its central bank, an evil Michael Clayton figure that loved profiting off of bullying, monopolization, and legal cons that only made sense because he was going to do anything he could to keep you from not paying for AI, which required keeping as many companies alive as possible.  Anyone else doing this in literally any context would be considered a lunatic. Perhaps Jensen was one too.  In any case, nobody else has the balance sheet, credit rating, assets, cashflow and psychopathy to do the same. Jensen spent 33 years inflating the NVIDIA Bubble, and it took less than a week for it to collapse.  I want you to think deeply about why you think there’s “demand” for AI, and how much of that belief is built upon a fantasy concocted by Jensen Huang: Even Anthropic’s demand appears to be slowing, with growth ( per Ramp ) trending to around 15% to 25% quarter-over-quarter in Q4 2026, down from 47% in the quarter before and over 140% in the quarter before that.  One has to wonder how Anthropic — or OpenAI’s — customers will be able to afford those tokens if there’s a generalized sense that the money has run out. Remember: it’s not just that Jensen invested , but that everybody ultimately relied on the idea that Jensen would always be there if somebody else couldn’t invest. There was always the sense that NVIDIA had everybody’s back, mostly because, well, NVIDIA has, up until recently, had everybody’s backs as part of a giant, quasi-legal circular financing operation that the media applauded right up until it sputtered. As I’ve explained for years, the entire tech industry has become obsessed with growth-at-all-costs thinking — or what I call The Rot Economy — which inevitably dragged it into an era that was defined not by delivered value but by speculation on what might happen if we all put another few trillion dollars into something.  In reality, buying NVIDIA’s GPUs was always a shitty deal, though nowhere near as bad a deal as renting them. Hyperscalers won’t share their AI revenues because their AI revenues suck, and they’ve spent $1.4 trillion or more on what appears to be less than $100 billion worth of revenues, with the future theoretical hundreds of billions contingent on hyperscalers spending hundreds of billions more. OpenAI made up 11% of Microsoft’s total revenues in Q1 Fiscal Year 2026 , which suggests that Microsoft’s overall revenues are in decline and that its AI revenues aren’t filling the gap outside of an AI lab that lost $10.9 billion in Q3 2026 and raised only $11 billion of the $30 billion it wanted in its latest funding round at $1.25 trillion , which was also lower than expected. CoreWeave, Nebius, IREN, and every neocloud is woefully unprofitable, with the justification being that if they just stopped raising money and finished all of these data centers they might one day have positive margins, somehow. Braindead analysts are now suggesting that “customer prepayments will help instead of debt,” which is contingent on companies that rent AI compute making prepayments, most of whom are unprofitable.  While hyperscalers could fill the gap, hyperscalers are already in an overbuild situation, mostly driven by Jensen Huang’s pressure campaign.  Demand for AI services has never, ever made sense, with Anthropic and OpenAI making up 89% of all AI startup revenues and both of them being both unprofitable and agreeing to spend over $1.3 trillion in the next seven years , most of which is contingent on continual funding and debt. We do not know the revenues of effectively any other AI startup, only annualized run rates that tell us very little about the actual financial conditions of the company and the occasional reporting that tell us a dog like Cognition would burn $800 million in 2026 alone .  Even with the best possible read of those annualized run rates, these startups raise hundreds of millions or billions of dollars’ worth of funding to make tens or hundreds of millions of dollars in revenue, and need to do so every few months due to the remarkable cost of renting NVIDIA GPUs, which despite being multiple generations in do not seem to be getting more efficient for the end customer. In many ways Jensen Huang created the perfected form of Jack Welch’s GE Capital , manipulating the markets, the media and the banking system into affirming his every decision by making sure that everybody had somebody else to pay or get paid by, even if the entire system was terrifyingly brittle.  And the worst part is that Jensen never really cared about whether there was demand for AI outside of its ability to justify further debt or cash for buying AI GPUs. The majority of the backstops that NVIDIA has provided — like its leases for Oracle, Anthropic, and OpenAI — require the data center capacity to be built before NVIDIA pays a dime, punting any theoretical time at which he or his heir would have to “backstop” anything into a time so far in the future that it doesn’t really matter.  Every CoreWeave or neocloud debt deal follows the same path — a customer agrees to buy unbuilt capacity, the debt is raised, the GPUs are bought, and then nothing happens until the data center is actually finished, which may take years, but none of that matters as long as NVIDIA got paid. Who knows what happens in NVIDIA’s earnings today. Perhaps they beat and raise again, with Colette Kress coasting off of the previous three months’ worth of circular financing deals that kept the machine alive.  Then again, the amount of stories in the past week that have said something to the effect of “Colette Kress and NVIDIA do not want to do circular financing anymore” suggest that the company may be getting ahead of something — such as pulling or lowering revenue guidance, perhaps blaming everything on the “challenging transition” rather than “the collapse of the circular financing economy.” In any case, the NVIDIA Bubble has popped. Jensen Huang is done. NVIDIA is no longer the circular financing titan, and anybody depending on its theoretical backing for future financing or funding is shit out of luck. There is no longer a well-funded boob-signing billionaire playboy left to beguile the press, con financiers, and pump the most wretched of bags in an endless conga-line of dodgy deals with goal of goosing NVIDIA’s revenues by any means necessary, even if the eventual data centers never actually get bought. The NVIDIA Bubble inflated at the perfect time, with Jensen capitalizing on the industry-wide knowledge ( as I wrote back in the Rot-Com Bubble ) that tech was flat out of hypergrowth ideas. NVIDIA offered hyperscalers and their brainless executives a panacea — a magical chip that allowed them to monopolize both the software layer and the infrastructure underpinning it, if only they’d just buy enough GPUs and build enough data centers to house them. All that mattered to Jensen was keeping them believing in the dream. Unfortunately, the vast majority of people do not want to pay for AI, and the vast majority of those who pay for AI compute can’t afford to do so. Those buying NVIDIA GPUs refuse to explain how much money they’re making from renting them out, or what it costs to do so. We do not know how many active AI GPUs there are in the world, and hyperscalers like Microsoft have taken great pains to mislead us into believing they have gigawatts more in capacity than they actually have .  There’s a reason that NVIDIA has $36 billion in compute commitments — because the actual demand for AI compute is much, much smaller than the demand he created for his GPUs. None of this mattered because Jensen Huang always made sure that nobody thought about it too much. The moment NVIDIA’s growth slows, it’ll be all that anybody can think about.  If you liked this piece, you should subscribe to my premium newsletter, and you can subscribe on the following links: $70 a year , $18 a quarter , or $7 a month . If you want to get in touch — and especially if you have any juicy information about Anthropic, OpenAI, or any other companies in the AI bubble — hit me up on Signal at ezitron.76. I’m also on IB on your Bloomberg Terminal.  You’re gonna need customer prepayments to buy GPUs, which will require cash up front from your customers, who are for the most part functionally in default. You’re not going to be able to raise debt without being able to do so, if at all. Bring me cash or I’m not going to guarantee I can sell your GPUs, which are in tight supply, honest. There’s massive demand for AI GPUs . Is there? Jensen Huang pushed customers to take billions of dollars’ worth of chips months in advance, with $200 billion or more of them sitting in warehouses thanks to a lack of capacity or power to install them. That “demand” appears to be a result of channel-stuffing, and if it’s not, why the fuck did they have to pay for the chips and take them earlier than they need them? There’s massive demand for AI compute . Is there? The vast majority of AI compute is sold to either Anthropic or OpenAI. The vast majority of Microsoft, Google, Oracle, CoreWeave, Nscale, Lambda, Amazon and Firmus’ backlogs come from OpenAI, Anthropic, Meta, or a hyperscaler buying capacity for OpenAI and Anthropic. There’s massive demand for AI tokens. Is there? 80% of Anthropic and OpenAI’s revenues come from 1% of their customers, the vast majority of which are unprofitable AI startups , with the largest purchasers of these tokens — like Perplexity, Cursor, and Reflection AI — all funded by NVIDIA.

0 views
Kev Quirk Yesterday

The Butcher's Masquerade

Author: Matt Dinniman Genre: Fantasy Released: 28 February 2022 Rating: ★★★★☆ Attention. Attention. The gates are down. The hunters are loose. Run, Run, Run. A lush jungle teeming with danger. Savage dinosaurs seeking blood. A fallen princess intent on vengeance. A mysterious, end-of-floor celebration for the top crawlers, dubbed “The Butcher’s Masquerade.” But that’s not all. Just when Coast Guard vet Carl and his ex-girlfriend’s cat, Princess Donut, think they’ve seen it all as they compete to survive in the galaxy’s most popular game show, the latest dungeon level introduces a terrible new threat. The sixth floor. The Hunting Grounds. As the remaining crawlers battle for their lives, outside tourists are finally allowed to enter the game, and they are ready to hunt. Among them is Vrah, a famed and veteran hunter, intent on collecting the biggest trophy of her career. But her prey is far from harmless, and this season they are fighting back. Welcome, crawlers. Welcome to the sixth floor of the dungeon. Learn more on Goodreads ➡ After reading the last book I said: I've been reading these books back to back; there's other books I want to read, so I think I'm going to take a break from reading these books and will switch to something else. I did stop reading these books - instead I went with Audible and listened to the audiobook. Lots of people have recommended how good Jeff Hays' voices are in the audiobooks, and they were right. I really enjoyed this and it didn't feel stagnant. At first it was weird as I had voices in my head of what I thought the various characters sounded like, but I soon adjusted. I'm going to continue with the series via audiobook - it's a lot of fun and I can listen while walking the dogs, or commuting to work. Highly recommended. Thanks for reading this post via RSS. RSS is ace, and so are you. ❤️ You can reply to this post by email , or leave a comment .

0 views

Neat stats are neat

Adam has officially released NeatStats , and I have to say, it looks, well, kinda neat! I’m not a big stats person; I do think knowing too much about your personal site is not all that healthy and can push you into weird directions, but for people who do want to get at least some basic information about the traffic they get, this looks promising. I also quite like the terminal view on the landing page; it reminds me of the default Goaccess view. It’s interesting how for years there was pretty much no action in the “analytics for websites” space, but now—and I suspect this was partly because of GDPR—we have loads of them: from Plausible , to Fathom , to Umami , to Simple Analytics , to Pirsch , to Tinylytics , and the list goes on and on and on. All that said, I’ll stick with parsing my logs with Goaccess those rare times when I want to see what’s happening on my site, and I’ll also keep assuming that nobody reads these posts, other than AI scrapers. Thank you for using and believing in RSS. You're awesome. Send me an email :: Sign my guestbook :: Become a supporter

0 views