Looks to be affecting our pipelines that rely on Playwright as they download images from Azure e.g. https://playwright.azureedge.net/builds/chromium/1124/chromi... which aren't currently resolving.

No tip

Suggestion that the admin is vibe governing: https://bsky.app/profile/amyhoy.bsky.social/post/3lluo7jmsss...

Confirmed here: https://www.cloudflarestatus.com/incidents/gshczn1wxh74

Slightly more info here: https://github.com/npm/cli/issues/8203

> I've now switched my primary HN link from the home page to /active, where, thankfully, flagged posts still show up.

Great tip, thanks!

Yea, the difference between home and /active has never been starker. I feel like HN's well-intentioned user-flagging system assumed good faith, and was not built to handle the obvious partisan brigading that we've been seeing.

> system assumed good faith

Ironically also the reason that many checks and balances in the US government seem to be failing.

> Why isn't it front-page news on HN rather than being flagged? Is it just because Musk's "DOGE" is in the title?

Essentially yes. Certain users are flagging because they don't want any discussion related to DOGE on HN. See for example https://news.ycombinator.com/item?id=43036254.

LOL... wow! I thought the "national cyberattack" and the root override/hijacking was far more relevant than the connection with the organization which shall not be named which is nominally led by he who shall not be named.

If you snoop around the network requests you'll see API calls made for fetching data. Could pull from those endpoints instead.

It's not a hypothetical, it's here in Node 23: https://nodejs.org/docs/latest/api/typescript.html#typescrip....

Speaking about the specification, it's a proposal. Yes, some run ahead and implement proposals under experimental flags, doesn't make it any more/less hypothetical as the proposal can still be rejected rather than progressing.

Come on, now.

> maybe in the future JS runtimes might be able to strip away types for you without a build-step.

You can't backpedal from that to "speaking about the specification". It's not future JS runtimes. It's a thing you can take advantage of right now.

I'm not very familiar with Nuxt or SvelteKit but this is exactly what React and NextJS provide with server components. Any JS related to server components isn't shipped, only client components which effectively represent the islands. The only real difference is you're not mixing technologies, it's all React.

Thanks. I wasn't aware Next had already shipped RSC support.

Yeah I also don’t think this is correct for SvelteKit.

SvelteKit doesn't support islands. It does full page hydration.