clacke@libranet.de is my main [fds]

@notclacke@fedia.social
51 Followers
164 Following
1.2K Posts
Trying out IceShrimp!

My main is on Friendica at
libranet.de/~clacke

This account is a liaison account and mainly intended for reposts, but if I did write any original posts, you'll find them at
justmytoots.com/notclacke@fedia.social .
mainlibranet.de/~clacke
there's another important point here. i found this correctness issue because i was figuring out ways to cache more computation. caching is not something you can do unless you have codified correctness in a sufficiently abstract way. the idea that caching and correctness are at odds has never made sense to me because i would never implement a caching behavior that's not provably correct, and conversely any nontrivial correctness inference can be used to cache. this is literally how compiler optimizations work
the reason this wasn't a security bug is because the software isolates things extremely well already (there is no way an error like this could have produced that). the reason it didn't generate an obviously broken flamegraph was because the software effectively decouples candidate selection from preference ranking from backtracking. i think i found a great example of @norootcause's principle of robust systems where the robustness mechanics produced an extremely difficult to debug error

So...
Russia put a hit on the leader of the Russian Volunteer Corps, which works for Ukraine to resist Putin.

So, Ukraine somehow put out evidence of them completing the hit, and intercepted/diverted/collected half a million dollars, after using the global media to spread the story... And then Budanov held an event, where they miraculously resurrected the commander!

"Welcome back to life!"

Russian milbloggers not amused.
https://kyivindependent.com/ukraines-hur-faked-death-of-top-anti-putin-russian-commander-claimed-kremlin-bounty-money/

"my computer isn't mine"

Last 4 words from:

'for every new worthless AI gadget Microsoft crams into it and for every time the OS inexplicably boots to a white screen and implores me to "finish setting up" my PC with an Office 365 subscription, the real problem is a feeling that my computer isn't mine"

Source: https://www.pcgamer.com/software/linux/im-brave-enough-to-say-it-linux-is-good-now-and-if-you-want-to-feel-like-you-actually-own-your-pc-make-2026-the-year-of-linux-on-your-desktop/

#TakeBackYourComputer

I'm brave enough to say it: Linux is good now, and if you want to feel like you actually own your PC, make 2026 the year of Linux on (your) desktop

Now if you don't mind I'm going to delete the root folder and see what happens.

PC Gamer

Looking at the trajectories of interstellar objects we have created, past trajectories of interstellar objects that have visited or are visiting us, and the trajectories of the Sun and nearby stars, what are their past and future interactions?

The Overview Effekt: "Where is Voyager Headed? ↤ ↦ Where did 3I/Atlas Come From?"

farside.link/invidious/watch?v…

youtube.com/watch?v=RuTfNWU4XW…

there better not be any situations or events in 2026
one thing that i mean very genuinely but is weird to say is that i find python kind of annoying to write and that makes it much easier to focus on practical things rather than aesthetics
what i'm more interested in doing at the moment is minimizing the amount of cpu cycles, wall clock time, and gigabytes of disk space taken up by the process of development. the requirements for local dev tooling are way, WAY different than ephemeral CI—but i'm not sure the solutions are different

The standard file format for metadata (including in wheels and installed projects) is based on the format of email headers. However, email formats have been revised several times, and exactly which email RFC applies to packaging metadata is not specified.

it never fucking ends https://packaging.python.org/en/latest/specifications/core-metadata/

Interpreting old metadata: In PEP 566, the version specifier field format specification was relaxed to accept the syntax used by popular publishing tools (namely to remove the requirement that version specifiers must be surrounded by parentheses). Metadata consumers may want to use the more relaxed formatting rules even for metadata files that are nominally less than version 2.1.

Core metadata specifications - Python Packaging User Guide

Hey, friends. It's evening time in North America. Whatever you do tonight, please don't drink and drive. And stay off the road if you can. You're important and the Fediverse needs you safe.