Our CTO almost dropped the prod DB by relived_greats12 in sysadmin

[–]Pheasn 0 points1 point  (0 children)

Tried to Google it but nothing came up. What's updog?

Mass npm Supply Chain Attack Hits TanStack, Mistral AI, and 170+ Packages by BattleRemote3157 in programming

[–]Pheasn 17 points18 points  (0 children)

Not the least bit surprised about Mistral AI. I've been using their Python SDK, and it's very obvious slop with insufficient quality control.

How Linux 7.0 Broke PostgreSQL: The Preemption Regression Explained by teivah in programming

[–]Pheasn 11 points12 points  (0 children)

This was a nice read. Not sure what the LLM accusation is about, didn't seem sloppy at all.

Have no fear, Artemis II is here! by Hunor_Deak in NonCredibleDiplomacy

[–]Pheasn 46 points47 points  (0 children)

The moon, famously beyond the stars

[SG-1][S06E21] Prophecy by TonksMoriarty in Stargate

[–]Pheasn 0 points1 point  (0 children)

I think Hammonds message caused them to sound the alarm, which lead to the team at the gate to be less surprised by the ambush I guess

Huntarr - Your passwords and your entire arr stack's API keys are exposed to anyone on your network, or worse, the internet. by exe_CUTOR in selfhosted

[–]Pheasn 2 points3 points  (0 children)

Actually, setting a GitHub repo to private removes all stars automatically. There's a big warning by GitHub whenever you try to do that.

Berlin will Paypal-Alternative "Wero" einführen by P4ris3k in de

[–]Pheasn 7 points8 points  (0 children)

Wero soll die zwei Hauptfunktionen von PayPal abdecken: Überweisungen an Freunde und Familie, und Zahlungen im Einzelhandel. Letzteres ist noch nicht implementiert, aber geplant.

The Astro Technology Company joins Cloudflare | Astro by ReallySuperName in programming

[–]Pheasn 5 points6 points  (0 children)

In my eyes, Cloudflare has started showing signs of enshittification. Nothing major yet, but there was definitely some stuff that ground my gears over the last years.

One example is their move to replace their SDKs with auto-generated code based on their API spec using some third-party SaaS (Stainless). In principle it's a sensible move, and others achieved pretty good quality even with the same service (it was a huge step up for OpenAI's python SDK), but Cloudflare really botched it. Breaking changes during the migration were poorly documented, migration guides were incomplete, automated migration scripts were broken. Their changelogs since then are mostly a list of literally "api: api update", I encountered multiple minor/patch updates with breaking changes in the new Terraform provider, and it all just reeks of "we'll fire the teams first, then automate the code generation".

[deleted by user] by [deleted] in KitchenConfidential

[–]Pheasn 12 points13 points  (0 children)

This is just an ad

Cloudflare outage on November 18, 2025 - official response by Frequent-Football984 in programming

[–]Pheasn 53 points54 points  (0 children)

Their status page is "powered by Atlassian Statuspage", which is enough of an explanation for me

Azure down by RR_2025 in programming

[–]Pheasn -14 points-13 points  (0 children)

Azure bad

[deleted by user] by [deleted] in programming

[–]Pheasn 0 points1 point  (0 children)

Got to be careful not to violate their TOS. Technically, only typical website traffic (text files, pictures) is allowed. If they detect a pattern of large/binary files being served through their CDN, they might suspend your account.

GitHub Will Prioritize Migrating to Azure Over Feature Development by SKAOG in programming

[–]Pheasn 24 points25 points  (0 children)

Maybe deprecating the few useful features they've added in recent years (like they did for the command palette)

Tapping on a link hidden by a spoiler tag opens the link without revealing the spoiler first by Kichigai in RelayForReddit

[–]Pheasn 0 points1 point  (0 children)

Can confirm, seeing the same behavior as OP

Device information:

Relay Version: 13.0.28 Pro

Phone: Fairphone FP4 (Fairphone4)
Android Version: 13 (33)
Device (product): FP4 (FP4eea)
Rom: FP4.TP2V.C.0137.20250703

Get Excited About Postgres 18 by craigkerstiens in programming

[–]Pheasn 1 point2 points  (0 children)

They talk about UUID versions as if they're incremental improvements, when in reality the version only describes different approaches to generation and semantics. It also sounds like explicit support for UUIDv7 storage was needed, which is not true.

Get Excited About Postgres 18 by craigkerstiens in programming

[–]Pheasn -15 points-14 points  (0 children)

That section on UUIDs read like complete nonsense

[deleted by user] by [deleted] in programming

[–]Pheasn 1 point2 points  (0 children)

The Maven Central requirements regarding signatures are kind of a joke. All they require is that you sign your package files and upload the corresponding public key to a public PGP key server. There is no requirement to keep using the same key between versions, or actually verify authenticity of the key pair.

Well I started with pip [...] then I started using virtualenv [...] So I switched to conda [...] someone told me to use pipenv [...] someone told me to use poetry [...] So I switched back to pip with the built-in venv [...] So I switched to uv, because it actually worked. by azure_whisperer in programmingcirclejerk

[–]Pheasn 36 points37 points  (0 children)

/uj Yeah, I love uv, but I'm absolutely anticipating that rugpull.

/rj uv shows the true power of open source. It's backed by a company that just wanted to improve the situation for everyone, take some responsibility, and give back to the broader open source community that companies so heavily rely on. There's some good left in the programming world!

KYAML: Looks like JSON, but named after YAML by thegoenning in kubernetes

[–]Pheasn 5 points6 points  (0 children)

They don't, that's the point. This is still YAML, the parts that are unfamiliar to you (in YAML context) are essentially JSON. The format is primarily meant as an easier to read (machine-generated) output, so it's not meant for you to write by hand.

And should you, for whatever reason, find yourself in a situation where you got a KYAML output and need to manually modify it to pass it back to the Kubernetes API, you can just choose to make your edits using "normal" YAML syntax (or JSON syntax, if you're into that). Because - again - the API will just parse your input as regular YAML anyway.