0 Followers
0 Following
2 Posts

GitHub Platform availability dips to 87.25%, averages 1.04 incidents/day

https://awful.systems/post/8119327

GitHub Platform availability dips to 87.25%, averages 1.04 incidents/day - awful.systems

Hi folks, I’m making another tech-stack recommendation. Previously, on Awful [https://awful.systems/comment/11010908], I noted that below 87.5% availability, whether a service is up is effectively random chance. We’ve reached that point for GitHub’s Platform, which includes components like Actions, Copilot, Pages, and the core API of issues and PRs. I do not have confidence in GitHub’s owners or operators to remedy this situation, so I cannot recommend it professionally nor to neighbors. As a bit of nuance, note that Pages seems to have relatively decent availability and is often up even when the rest of GitHub is down, so static content hosted on Pages can be deprioritized for migration. The thread is open on Lemmy. I’m interested in your thoughts, particularly around alternative forges, alternative paradigms for forges, community-driven plans for migration, strategies for migrating, and tools that ease the burden of maintaining many git repositories.

A Cryptography Engineer’s Perspective on Quantum Computing Timelines

https://awful.systems/post/7860428

A Cryptography Engineer’s Perspective on Quantum Computing Timelines - awful.systems

I’m not gonna dig up the links since I’m sure y’all’re already tired of talking about quantum computing. I am going to insist that, while I professionally disagree with Filippo about plenty of things, I do not see any mistakes in their analysis here. Please start thinking about post-quantum cryptographic tooling today.

Activating Two Trap Cards at Once, or: A Gentle Response to the Popularity of Vibecoding

https://awful.systems/post/7783165

Activating Two Trap Cards at Once, or: A Gentle Response to the Popularity of Vibecoding - awful.systems

Welcome to the carnival! We’ve got fun and games. I asked vibecoders to complete three tasks. When folks complained about that, I offered up five more tasks. I did half of these and got average scores. How well did the community do? Scroll to the end to find out!

Vibecoding Challenge 2: The Five Feathers (Spring 2026)

https://awful.systems/post/7478543

Vibecoding Challenge 2: The Five Feathers (Spring 2026) - awful.systems

Okay, previously, on Awful [https://awful.systems/post/7079104], we established that vibecoding can’t produce working compilers. Let’s try some other side projects of mine. I have important stuff [https://lobste.rs/s/tqttgj/forwardly_evaluated_build_systems#c_kfijc0] to work on and a deadline, so I’m not matching these projects with my own submissions. Instead, I’ve laid out a psuedo-objective rubric and I’m going to say that par is 10/10 points.

Palantir Sues Swiss Magazine For Accurately Reporting That The Swiss Government Didn’t Want Palantir

https://awful.systems/post/7470005

Palantir Sues Swiss Magazine For Accurately Reporting That The Swiss Government Didn’t Want Palantir - awful.systems

Lemmy

This response video has put Siliconversations onto my radar. They were only mentioned briefly as one of the multiple people claiming that AGI is possible, and this response was so bad that it caused me to go digging for a few minutes into their backers.

Control AI, stylized as “CONTROL/AI” or “control”, is now interesting as well. They appear to have funded at least some of these videos, was definitely credited in one Hank Green video, and got a footbath from Siliconversations in the linked video. We also already know some stuff about Future of Life Institute, who funded Siliconversations’ prior doomer video and is run by ethnonationalist Max Tegmark. @[email protected] might know more about how the money is moving.

InternetOfBugs Is Lying About SciShow Lying About AI

YouTube

I’ve finished grading all of the entries so far. I don’t think that we’ll get any more, so here’s a preview of the upcoming blog post.

The tier listings are as follows:

  • B tier: Corbin S. (Task 1), Corbin S. (Task 2), Corbin S. (Task 3)
  • C tier: Piper M. (Task 1)

Admittedly, we didn’t get a whole lot of players, but that’s it. That’s the entire tier listing. I had three things I wanted to do in my spare time. I did them and got an average ranking based on my average predictions of the future; I met expectations. Piper also placed and I greatly appreciate her sportsmanship here.

My solutions are available as notes and source code. For Task 1, I have three main commits: one, two, three, and a bugfix. For Task 2, the commits are internal to my homelab, but I do have notes and source code. Finally, for Task 3, I put the entire repository into a flat gist including notes, source code, and Nix flake.

bf: Initial thoughts on pointer propagation. · rpypkgs/rpypkgs@ec6d074

Jan 27, 22:30: Not breaking ground quite yet, just crystallizing some thoughts. We have some contestants and I need to have my solution ready before I can take a look at their offerings. The commut...

GitHub

It occurs to me that this audience might not immediately understand how hard the chosen tasks are. I was fairly adversarial with my task selection.

Two of them are in RPython, an old dialect of Python 2.7 that chatbots will have trouble emitting because they’re trained on the incompatible Python 3.x lineage. The odd task out asks for the bot to read Raku, which is as tough as its legendary predecessor Perl 5, and to write low-level code that is very prone to crashing. All three tasks must be done relative to a Nix flake, which is easy for folks who are used to it but not typical for bots. The third task is an open-ended optimization problem where a top score will require full-stack knowledge and a strong sense of performance heuristics; I gave two examples of how to do it, but by construction neither example can result in an S-tier score if literally copied.

This test is meant to shame and embarrass those who attempt it. It also happens to be a slice of the stuff that I do in my spare time.

Lobsters Vibecoding Challenge (Winter 2025-2026)

https://awful.systems/post/7079104

Lobsters Vibecoding Challenge (Winter 2025-2026) - awful.systems

I’m tired of hearing about vibecoding on Lobsters, so I’ve written up three of my side tasks for coding agents. Talk is cheap; show us the code.

A Nix flake for detecting and removing fascist software

https://awful.systems/post/6731398

A Nix flake for detecting and removing fascist software - awful.systems

Happy Holiday and merry winter solstice! I’m sharing a Nix flake that I’ve been slowly growing in my homelab for the past few months. It incorporates this systemd feature [https://github.com/systemd/systemd/pull/39285], switches from CppNix to Lix, and disables a handful of packages. That PR inspired me, and I’m releasing this in turn to inspire you. Paying it forward and all that. Should you use this? As-is, probably not. It will rebuild systemd at a minimum and you probably don’t have enough RAM for that; building from this flake crashed my development laptop and I had to build it on a workstation instead. Also, if you have good taste in packages then this will be a no-op aside from systemd and Lix, and you can do both of those on your own. Isn’t this merely virtue-signalling? I think that the original systemd PR was definitely signalling, since it’s unlikely to ever get deployed on the systems of our friends. However, I really do sleep better at night knowing that it’s unlikely that jart or suckless have any code running on my machines. Why not make a proper repository and organization? Mostly the possibility that GitHub might actually take down a repository named nixpkgs-antifa. If there’s any interest then I could set up a Codeberg repo. However, up to this point, I’ve only used it internally and my homelab has its own internal git service. Mods: You’ve indicated that you don’t like it when people write code to approach our social problems. That’s fine; I’m not publishing an application or service and certainly not starting a social movement, just sharing some of my internal code.