The article is dated October 2025, but I don't recall ever hearing about this before, and it doesn't look like anything has ever been posted on HN.
The separation of storage and compute is new for Heroku, though they are not the first to do so. So far it seems like there's still only fixed combinations of vCPU and RAM, and that the price of each "no storage included" instance is more than the equivalent storage-included "Classic" instance size.
AI-related definitions aside, if it's a strictly subtractive/destructive tool that only removes light, it's hard to characterise as "generative" and arguably not much different to filtering frequencies!
You're absolutely correct and it's me who has mis-read that part. The point of the oddly relaxed wording on sexual images and behaviour still stands though!
> Unacceptable behaviors include but are not limited to: offensive comments, insults, jokes or ridicule; gratuitous or off-topic sexual images or behavior in spaces where they are nor other unappropriately aggressive behaviors; threats of violence or deliberate intimidation; creating additional online accounts in order to harass another person or circumvent a ban; harassment of any form.
I can't help but wonder who decided that, in an electronics forum of all places, *any* form of joke should be unacceptable, but sexual images are only a problem if they are gratuitous or off-topic!
Our site is fine, including files served by Cloudflare's CDN and Cloudflare Workers, but the Cloudflare dashboard is definitely down.
The Cloudflare status page says that it's the dashboard and Cloudflare APIs that are down. I wonder if the problem is focused on larger sites because they are more dependent on / integrated with Cloudflare APIs. Or perhaps it's only an Enterprise tier feature that's broken.
If it's not everything that is down, I guess things are slightly more resilient than last time?
> A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal. Posted 3 minutes ago. Nov 18, 2025 - 14:42 UTC
Seems like they think they've fixed it fully this time!
> Investigating - Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available.
Things are back up (a second time) for me.
Cloudflare have updated their status page now to reflect the problems now. It doesn’t sound like they are confident the problem is fully fixed yet.
Salesforce Service Cloud is affected by the issue too, so if they are dogfooding their own customer service software there's a good chance their support team are locked out of accessing support cases too :/
It's worth noting that including Critical CSS in every page load isn't the only way to use it.
A lot of unnecessary bloat can be avoided by only including it when it looks like a user is visiting for the first time (and likely hasn't got the CSS files cached already) or only using the Critical CSS technique for pages that commonly come at the start of a session.
Given there seem to be few other Critical CSS tools out there, its utility in driving web performance, and the fact Google's web.dev recommended tool (https://github.com/addyosmani/critical) uses penthouse under the hood, I'm surprised there isn't more effort and/or sponsorship going into helping maintain it.
Yep, Mike Hansen was on the live stream launching the new device. He also notably created Rhasspy [1], which is open-source voice assistant software for Raspberry Pi (when connected to a microphone and speaker).
I've picked up an Echo Dot a few years ago when Amazon were practically giving them away, thinking that surely someone would have jailbroken it by now to allow it to be used with Home Assistant.
It was only after researching later that I discovered that this wasn't currently possible and recommended approach was to buy some replacement internals that cost more than the device itself (and if I recall correctly, more than the new Home Assistant Voice Preview Edition).
The article is dated October 2025, but I don't recall ever hearing about this before, and it doesn't look like anything has ever been posted on HN.
The separation of storage and compute is new for Heroku, though they are not the first to do so. So far it seems like there's still only fixed combinations of vCPU and RAM, and that the price of each "no storage included" instance is more than the equivalent storage-included "Classic" instance size.