When I worked on OpenStack for a few years, 80% of the bugs I fixed were type errors that could have been prevented by Python being staticly typed.

Jellyfin depends on proprietary Microsoft .NET, even on Linux.

It’s still better than Plex and Emby, which are fully proprietary, and have no source code. But I will stick with sshfs with kodi, and nginx plus mpv for now.

One time I was getting estimates for server software for an embedded device I had made. In a teleconference, I told one company that our prototype server ran on nginx. They emailed us an estimate saying we had to switch our embedded system to Windows 10 IoT Enterprise, and put the server on Microsoft’s cloud, because “Engine X is not an enterprise web server.”

I think that wormhole.app page is different software from magic wormhole (and warp). It just has a similar name. wormhole.app does appear to be proprietary.

Thanks. I think I found its homepage, is it the same as this? That looks like part of Gnome, so should be open source too. (It’s maybe available in your operating system without needing a flatpak, if you would prefer it that way)

I’m not familiar with warp, and couldn’t find it with a search. But I did find magic wormhole, and it appears to be MIT licensed, so it is open source. I also searched packages.debian.org and found it, so definitely open source.

As for firewalls: it might only block incoming connections, or has an exception for LAN hosts. I’d have to see the configuration to say more.

No. Check my previous comment – this is about hosting on your home ISP, and turning that on or off directly affected the blocking. There is no way to host a webserver through any commercial VPN service.

It seems crazy to me too, but I tested it numerous times. Closing port 80 and 443 stopped the blocks, and re-opening them started the blocks again.

From several years of experiencing it in person. Datadome was the worst and most consistent. It stopped the moment I switched my webserver onto an exotic port number (above 10,000).

Datadome sent me captchas at every domain they firewalled. After correctly solving, I would always be completely blocked:

(not my screenshot)

Here is a page listing some system requirements for Peertube. It says 4 cores and 4GB RAM for 1000 viewers, which some Raspberry Pi systems have.

Yes. However, hosting things from your home connection will make it difficult for you to visit many websites. Blocklists such as Datadome, Cloudflare, and F5 will give you endless captchas if they detect port 80 or port 443 open.

C when I cast a char * * to a char * * const: ok

C when I cast a char * * to a char * const *: ok

C when I cast a char * * to a char const * *: WTF

C when I cast a char * * to a char const * const *: ok

I love that these have borders around the buttons. I wish more interfaces would do that. It used to be standard.

Try going to http://000.000.000.000:8080/ in your web browser (replacing the 0’s with your public IP address), on your home connection. If it doesn’t work, it means that your port forwarding is probably not working. If the page loads correctly, it means your port forwarding is working correctly, and the problem is probably your ISP doing port blocking.

In my system, the raid arrays seem to do periodic data scrubbing automatically. Maybe it’s something that’s part of Debian, or maybe it’s just a default kernel setting. I don’t think it helps much with data integrity – I think it helps more just by ensuring the continued functionality of the drives.

When it’s running, you can type cat /proc/mdstat to see the progress.

That command will also show you if there is a failing drive, so that you can replace it.

Sure. First you set up a RAID5/6 array in mdadm. This is a purely software thing, which is built into the Linux kernel. It doesn’t require any hardware RAID system. If you have 3-4 drives, RAID5 is probably best, and if you have 5+ drives RAID6 is probably best.

If your 3 blank drives are sdb1, sdc1, and sdd1, run this:

mdadm --create --verbose /dev/md0 --level=5 -n 3 /dev/sdb1 /dev/sdc1 /dev/sdd1

This will create a block device called /dev/md0 that you can use as if it were a single large hard drive.

mkfs.btrfs /dev/md0

That will make the filesystem on the block device.

mkdir /mnt/bigraid
mount /dev/md0 /mnt/bigraid

This creates a mount point and mounts the filesystem.

To get it to mount every time you boot, add an entry for this filesystem in /etc/fstab

The man page at https://btrfs.readthedocs.io/en/latest/mkfs.btrfs.html says:

RAID5/6 has known problems and should not be used in production.

So those profiles have unknown, unspecified problems.

But btrfs is safe on top of md-based raid1/5/6. It also has the advantage that you only need to encrypt one volume.

The easiest way to disable unnecessary services is to uninstall them with aptitude, or whichever package manager you like. Try terminating services one by one, and see if anything bad happens. If nothing bad happens, you can probably uninstall it. On the other hand, if the system does get wonky a reboot should fix it. Or, you can research the services by name and decide whether to uninstall them. (avahi-daemon for example is a good idea to uninstall.)

To make the GUI not run, uninstall your display manager (gdm, xdm, nodm, or whatever) and uninstall your xorg server or wayland server. There may be GUI programs remaining after that, but they will only be consuming disk space, not RAM or CPU.

If the battery is old and holds little charge, you may save a few watts by removing it and throwing it away, instead of letting the system keep it topped off.

Get a power meter, such as a Kill-a-watt device. Then, experiment with different settings. If it’s consuming less than 30 watts, you’re probably fine. If you live in the US, one watt-year is about one US dollar (or a little more), so for every watt it consumes, that’s about how much you will pay per year for its electricity.

draw .io is closed source.

I agree that the repository should only contain source files, not the output of the build process. However, in some cases (like icon images) the source files may be binary. I think small binaries that are required to build and/or run the software, and that are not an output of any build process, do make sense to put in the repository.