Bei der Lufthansa dürfen Powerbanks mit bis zu 100 Watt im Handgepäck transportiert werden.

Was für ein konfuser Artikel. Über die Leistung der Powerbanks wird in den Regeln überhaupt nichts gesagt. Was begrenzt wird, ist die erlaubte Kapazität. Dort sind 100 Wh das erlaubte Maximum.

If you plan on running the laptop all the time on wall power, make sure to limit the battery charge to 80 % or less, otherwise the battery will die pretty quickly.

The worst part is that Nextcloud isn’t even really in competition with Google. Setting up a Nextcloud server isn’t hard, but it’s not a trivial task. Sharing it outside your local network also requires a bit of skill, especially if done securely. That is to say, Nextcloud users probably tend to be more tech-savvy.

That’s only true for those who self-host this. There are lots of companies offering Nextcloud hosting. That’s probably why Google doesn’t like Nextcloud. I’m not saying Google is right. Actually what Google is doing here is quite pathetic.

Yes, using uuidgen should work fine.

Thanks for pointing this out. I thought this had to be an actual UUID. Generating a unique string of arbitrary format manually is certainly much easier to do manually without additional tools.

This is not quite true. As I mentioned in my other comment already, each feed entry needs its own unique UUID. You have to generate such a UUID for every entry.

How do people subscribe to them?

Subscribing to an RSS feed really is nothing more than telling your RSS client about the URL to that RSS XML file. The RSS client then regularily checks the URL for changes.

If your site is hand-made as you say, you would have to manually create and update the RSS file also. This is quite a nuisance, not only because it is XML, but also because every feed entry needs its own unique UUID, which you need to create. Perhaps you could create a script that does it for you. Static site generators are usually able to automatically create an RSS feed for you.

Correct, you summarized that well.

The easiest way to do it is by running a Kiwix server and hosting a copy of Wikipedia with that.

I am not sure which CPUs exactly the article is refering to with those early i586 CPUs, but I do remember those Cyrix 6x86/6x86MX CPUs. When it comes to Linux, they were always treated as 486-class CPUs because they were missing some instructions required to be considered 586-class. On the other hand their architecture was actually quite modern, like a 686 CPU with out-of-order execution. The 6x86MX also supported the CMOV instruction which is usually associated with 686-class CPU. Quite strange CPUs from today’s perspective.

VIA also had some CPUs (certain VIA C3 CPUs) that the Linux kernel always treated as 486-class CPUs due to some missing 586 instructions.

AMD’s Am5x86 CPUs were rebranded 486 CPUs, while AMD’s K5 was an early 586 CPU that might fall into that early 586 category due to missing instructions. AMD’s later K6 CPUs should support all Pentium instructions afaik (but not CMOV like the Cyrix CPUs did).

I’ve subscribed to their RSS feed, but their server is so unreliable, my feed reader complains all the time that it is unreachable. When I manually retry it mostly works, only to fail again later. I’m wondering what’s going on there. I never have this problem with any other feed…

That is awesome!

oldschool computer processor

Are Russian military flights forced to detour over the Baltic Sea between Kaliningrad and St. Petersburg?

Not only their military flights, all Russian aircraft are forbidden from entering that airspace. Just have a look at any of the ADS-B websites. There is this very narrow flight corridor where they are allowed to fly.

A stock Amiga 1200 wouldn’t allow you to run Linux, because the CPU doesn’t have an MMU (memory management unit). With a turbo card installed with at least a 68030 and enough RAM you could run Linux on a 1200 though.

Any electronic component (or sub-circuit) running at a high frequency can cause voltage fluctuations on the supply voltage rail. Ideally the Arduino itself has decoupling capacitors close by so those fluctuations are absorbed by those caps and never reach the RTC module. The RTC module itelf can similarily cause such fluctuations, so again, a suitable decoupling capacitor close to the component should be present. It really goes both way though. Those capacitors both reduce the influence a component has on the supply voltage, but also protects the component from fluctuations coming from the supply rail.

To better understand this, maybe it helps to consider that real circuits are never perfect. As such, PCB traces have resistance and so does the power supply. That in turn means that when the load on the power supply changes, the voltage also changes due to those resistances. With capacitors with low internal resistance near those components, those capacitors can quickly supply current when needed. This is also why you typically design PCBs with high currents with power traces in a star toplogy, so the influence between components is minimized.

Using electrolytic capacitors for decoupling isn’t ideal. This is due to their rather high ESR (and also their rather high inductance). This means that they don’t do much decoupling for frequencies higher than perhaps a couple of kHz. So for reducing mains frequency ripple, electrolytic capacitors are fine, but reducing voltages spikes caused by high frequency electronics they don’t do much.

Same with GrapheneOS.

I liked the original Deus Ex. If it is still available, I’d be interested!

Oops, you are correct of course, 6A is what I meant, plain 6 should work fine also most of the time, but there is pretty much no point going for that, unless you have that deployed already.