tal

If that's actually their problem, they could easily just play a small amount of silence before a video's content. They don't need to be constantly tying up an audio stream.

Funnily enough, Microsoft built WSL so developers could use Linux without leaving Windows. Instead, it turned a growing number of Windows PCs into functional Linux development machines, with Windows serving as little more than the launcher.

I mean, I get using Windows if you're actually doing Windows development work, but if not, I'd just put Linux proper on the thing.

The appeal for developers is that even if their employer issues a Windows laptop, and even when their development stack expects Linux, WSL removes the need to dual-boot.

With WSL, they don’t have to fight their employer’s hardware policy to get it.

Any employer that is employing someone to do Linux development work and takes issue with them having a Linux box to do dev work isn't a place that I'd want to bother to work.

only thing

Cygwin?

There are a few Firefox plugins that exclude Shorts from YouTube search results.

Web search engines that provide a video search may have a duration filter. Both Kagi and DuckDuckGo can do this, in a quick check.

They could let users register a PGP pubkey and encrypt their emails, which would also avoid third parties harvesting data from them.

CloudFlare having that outage a while back was bigger, I'd say. GitHub is only used by a small percentage of people out there.

If you want to go by "percentage of the Internet taken down", the biggest outage ever has probably been the Morris Worm, since a lot of major insitutions quarantined themselves by closing down their network links to other sites until they could identify the problem, purge it, and secure their systems against reinfection.

https://en.wikipedia.org/wiki/Morris_worm

The Morris worm or Internet worm of November 2, 1988, was a malicious self-replicating computer program that affected VAX computers and SUN-3 workstations running the 4.2 and 4.3 Berkeley UNIX code.[1] It is one of the oldest computer worms distributed via the Internet, and the first to gain significant mainstream media attention.

The Internet was partitioned for several days, as regional networks disconnected from the NSFNet backbone and from each other to prevent recontamination while cleaning their own networks.

The Morris worm has sometimes been referred to as the "Great Worm", named after the devastating "Great Worms" of Tolkien. The Morris worm had a devastating effect on the Internet at that time, both in overall system downtime and in psychological impact on the perception of security and reliability of the Internet.[17]

It looks like it supports bridging to GitHub and a number of other issue trackers, so while the project is using GitHub's issue tracker, I'd bet that the devs are using their own system to interface with it.

Use archive.org's Wayback Wachine.

https://web.archive.org/

I mean, internal CI and version control systems go down too. Like, if GitHub has substantially worse downtime than an whatever internal system one runs, fair enough.

Git's distributed, so downtime isn't usually a huge deal compared to a non-distributed version control system.

I think that the largest issue is actually that GitHub provides a centralized commit review system (and, to be fair, so are many internal systems) that one uses to review pull requests. Like, a CI run being deferred usually isn't a huge deal. Version control is probably distributed these days. But code review is something that you'd like to keep going.

If you do code review in email or something, it's distributed. You can keep working. If your email server goes down, it might prevent new messages from reaching other users, but all of the review requests you have can be worked on and any review you've already received can be read. But if people are using some centralized Web-based code review system, and that goes down, then that kinda halts a lot of stuff.

Same centralized problem for issue tracking.

EDIT: I've never used a distributed issue tracker, but apparently they are indeed out there:

https://github.com/git-bug/git-bug

EDIT2: A lot of issue trackers involve people attaching large files to issues, so there might be some fundamental scalability issues in that regard for distributed operation; might need to centralize that part. That being said, I'd rather temporarily lose access to just a large-file-hosting server than to that and all of the other issue data.

Note that this is specific to Germany (or, probably, the EU, but they're using Germany as a benchmark). German DDR5 prices had started coming back down slightly earlier in the year

I remember articles earlier in the year commenting on that. According to this article, they're now drifting back up again, albeit slowly.

I don't know if "explode" is really the right term. The price changes since the initial increase around late 2025 and early 2026 haven't really been dramatic.

https://www.generationamiga.com/2026/01/18/apollo-a6000-review-the-ultimate-68k-amiga-rebuilt-for-the-modern-age/

Apollo A6000 review: the ultimate 68K Amiga, rebuilt for the modern age

The Apollo A6000 ships with 2 GB of Fast RAM

It succeeds where emulation cannot, delivering the tactile, hardware‑level experience of owning a new Amiga‑class machine in 2025/2026.

https://www.apollo-computer.com/a6000.php

:-)

I think that he means just put 2-3 days of food out.

If the cat eats wet food, that'd have spoiling problems, but I suppose that it'd probably be okay with dry kibble.