X11 has effectively already been deprecated for years, seeing little to no development on it. No one should be surprised.

X11 is complete.

Wayland is incomplete, and is missing essential features like accessibility and automation (ydotool will never have half the features xdotool has).

Mozilla, for example, would sign Firefox’s flatpak with a PGP key that they would disclose on their website. You verify the signature using the RSA algorithm (or any other algorithm for digital signatures. There are a bunch.) Or, you could just trust that your connection wasn’t tampered the first time, then you would have the public key, and it would verify each time that the package came from that same person. Currently, you have to trust every time that your connection isn’t tampered.

Major flatpak providers (Flathub at the very least) would include their PGP public key in the flatpak software repo, and operating system vendors would distribute that key in the flatpak infrastructure for their operating system, which itself is signed by the operating system’s key.

Article doesn’t mention my biggest problem with flatpaks, that the packages are not digitally signed. All major Linux distros sign their packages, and flathub should too. I would prefer to see digital signatures from both flathub and the package’s maintainer. I don’t believe flathub has either one currently.

This survey doesn’t distinguish between levels of cloud service provider, so I was a little confused.

Virtual private servers, cloud virtual servers (like AWS), cloud-based software where you provide code or a program and the cloud system runs it on a server of its choosing, and cloud-based systems where someone else provides the software (like Google Docs).

I like git add because then you can do git diff --staged

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.