preview
A chatbot user passive-aggressively tries to get their vibecoded Web browser into Debian and Arch.
A chatbot user passive-aggressively tries to get their vibecoded Web browser into Debian and Arch.
@corbin@awful.systems
A chatbot user passive-aggressively tries to get their vibecoded Web browser into Debian and Arch.
A chatbot user passive-aggressively tries to get their vibecoded Web browser into Debian and Arch.
Hi folks, I’m making another tech-stack recommendation. Previously, on Awful, 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.
Hi folks, I’m making another tech-stack recommendation. Previously, on Awful, 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.
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.
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.
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!
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!
Okay, previously, on Awful, we established that vibecoding can’t produce working compilers. Let’s try some other side projects of mine. I have important stuff 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.
Okay, previously, on Awful, we established that vibecoding can’t produce working compilers. Let’s try some other side projects of mine. I have important stuff 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.
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.
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.
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, 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.
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, 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.
Cross-posting a good overview of how propaganda and public relations intersect with social media. Thanks @Soatok@pawb.social for writing this up!
Cross-posting a good overview of how propaganda and public relations intersect with social media. Thanks @Soatok@pawb.social for writing this up!
Tired of going to Scott “Other” Aaronson’s blog to find out what’s currently known about the busy beaver game? I maintain a community website that has summaries for the known numbers in Busy Beaver research, the Busy Beaver Gauge.
I started this site last year because I was worried that Other Scott was excluding some research and not doing a great job of sharing links and history. For example, when it comes to Turing machines implementing the Goldbach conjecture, Other Scott gives O’Rear’s 2016 result but not the other two confirmed improvements in the same year, nor the recent 2024 work by Leng.
Concretely, here’s what I offer that Other Scott doesn’t:
I accept PRs, although most folks ping me on IRC (korvo on Libera Chat, try #esolangs) and I’m fairly decent at keeping up on the news once it escapes Discord. Also, you (yes, you!) can probably learn how to write programs that attempt to solve these problems, and I’ll credit you if your attempt is short or novel.
Tired of going to Scott “Other” Aaronson’s blog to find out what’s currently known about the busy beaver game? I maintain a community website that has summaries for the known numbers in Busy Beaver research, the Busy Beaver Gauge.
I started this site last year because I was worried that Other Scott was excluding some research and not doing a great job of sharing links and history. For example, when it comes to Turing machines implementing the Goldbach conjecture, Other Scott gives O’Rear’s 2016 result but not the other two confirmed improvements in the same year, nor the recent 2024 work by Leng.
Concretely, here’s what I offer that Other Scott doesn’t:
I accept PRs, although most folks ping me on IRC (korvo on Libera Chat, try #esolangs) and I’m fairly decent at keeping up on the news once it escapes Discord. Also, you (yes, you!) can probably learn how to write programs that attempt to solve these problems, and I’ll credit you if your attempt is short or novel.