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’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…

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.

Same with GrapheneOS.

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.

Can anyone explain to me if a headless chrome browser is dangerous the way a regular chrome browser is?

Almost. You want to make sure to keep it as up-to-date as you would a regular Chrome browser. It does almost everything a regular Chrome does, including running arbitrary scripts on websites.

Anyone have experience converting from 1G LAN to 2.5 or even 10?

Going from 1 G to 2.5 G is fairly cheap these days. You can almost certainly use the same cabling, even when you’ve got only Cat.5e cabling. While you can do 10 G over copper, I wouldn’t suggest doing that, since it consumes quite a lot of power compared to both 1 G and 2.5 G. You’d need Cat.6E for reliable 10 G over copper.

Sure, I’m not saying this never happens, but I’d argue this is the exception not the rule. Especially when it comes to DDR5 which is still quite new, so there should not be that many laptops with dead batteries with such memory around yet. It would be a different story with DDR4, not that I would suggest that they use DDR4. And the SSD form factor they used isn’t very common, so it is probably even less likely that people have such SSDs lying around. I still appreciate that they allow me to buy the machine without memory/storage.

The point of the DIY edition is that you could just reuse some old RAM or SSDs.

In theory, yes. I don’t think it is very likely that people have DDR5 SO-DIMM modules lying around, let alone 2230 SSDs. I don’t understand why they weren’t able to go for the way more common 2280 form factor for the SSD at least.

I don’t know your exact setup, but you should add the IP that Jellyfin sees when the reverse proxy makes a request. That probably comes from the IP of your Traefik docker container.

Thanks for pointing this out! I probably would have missed this, since I didn’t expect such a change for a patch release.

Their documentation mentions:

For jellyfin to know which reverse proxy is trusted, the IP, Hostname or Subnet has to be set in the Known Proxies (under Admin Dashboard -> Networking) setting.

Does this really mean, that the only way to configure this is through the web UI? This is kind of a problem when deploying it, since without the reverse proxy I can’t reach the Jellyfin server. Is there no way of doing this outside the web UI, via a config file or something?

Edit: Apparently the configuration for the proxies is stored in Jellyfin’s network.xml config file. So it should be possible to do this without manually configuring it via the web UI.

Another edit: It works. Adding <KnownProxies>[proxy ip or hostname]</KnownProxies> in place of the empty <KnownProxies/> key to that config file does the trick.

I’m not sure why you think manufactuers of SoCs (or entire phones) - which aren’t used by Google directly (as in: used by Google in their own products or sold by Google as their own product) - provide drivers to Google. They don’t, because there is no point in doing that. This is not how the Android eco-system works or the business of selling those SoCs for that matter.

SoC manufactuers sell their SoCs to companies who want to build Android phones (or they build their own like Samsung). With those SoCs they provide a BSP (board support package) that includes all the bits needed to bring up a system running on that partricular SoC. Google has pretty much nothing to do with this, except that Google recommends a certain Linux kernel version (with a bunch of Android-specific patches) for a given Android version, which SoC makers often (but not always) use as the base for their customized kernels.

It is not like Google provides the operating system including all device specific drivers to the device manufacturers. They don’t care about that at all. They provide AOSP (which is open source, so anyone can get that) as well as their proprietary stuff like Google Play etc. That’s pretty much it.

There is a lot not to like about many Android phones (or rather smartphones in general), when it comes to their openness in regards to software. And it is perfectly fine to criticize those involved, but you should direct your criticism at the correct parties. Google isn’t the bad guy in this instance.