klangcola

Not a problem when self-hosting on own hardware. Especially in winter. Overly complicated spaceheater goes brrrr

AntennaPod. Free, open source and just works perfectly, fast and snappy, unobtrusive. This is the way.

Another alternative is PodVerse. Also free and open source. More features, but more sluggish

Today I Learned, thanks for sharing.

From your linked thread it seems potentially still acceptable, being fully local , open source, and with an international contributor team. But yeah no such ties with LibreOffice.

You should there is also OnlyOffice, which has better compatibility with Microsoft file formats (and uses Microsoft formats by default). Its also generally good, and open source.

I use both OnlyOffice and LibreOffice on different computers. Both are good.

I'll start: The Guardian (UK) is self-owned (owned by an organization whose purpose is the long term economic viability and editorial independence of the Guardian).

Hard to say without knowing which method you used to install HomeAssistant.

But I never found mdns .local addresses to be very reliable. They work 80-90% of the time, but the remaining 10-20% are a hassle.

Instead I'd recommend you install PiHole (in a docker container is easiest). PiHole is a DNS server intended for network-level ad-blocking. But it also have a handy feature of defining local DNS entries, so you can have HomeAssistant.myhome or HomeAssistant.whatever (.local should not be used with PiHole local DNS because .local is meant for mdns)

Not Op, but I was in a very similar situation (decent pay, old house, old car, not many fancy purchases). While many people here will borrow a lot and pay the minimum on their mortgage, I paid down my mortgage completely. (and otherwise spent money on travel).

Ironically, this is bad financial advice. The last 15-20 years interest have been very low, and house prices have soared. It would make much more financial sense to borrow more and buy a nicer house. But I value the freedom I get from not having a mortgage. And I never borrowed to buy a car, as cars depreciate like rocks

Next time I buy a plane it will definitely be an Airbus and not a Boeing.

Checks out. But also Military Industrial Complex.

The telegraph article is very thorough, and doesn't mince word. Give it a read

Some key points regarding Proxmox:

• Even if you only want to run two services, you still want to keep them isolated. This can save you much pain and frustration in the future when they require upgrades
• Proxmox let's you easily manage VM and LXC containers. So you can easily manage backups, or spinning up a separate test instance of your service. Which again, can save you pain and frustration when it comes to future updates of your services.
• Backups are even better if you can deploy the separate Proxmox Backup Server
• Should you ever want to add another service in the future, you can test it out in a new VM or container without it affecting your existing services at all
• ZFS is indeed quite memory hungry, but AFAIK it's mainly used for the read cache, and can be tuned to use less RAM at the cost of performance
• ZFS is mentioned a lot because it's good, but Proxmox also supports a range of other storage technologies: LVM, mdraid, EXT4, CEPH
• Proxmox is just standard Debian and KVM/QEMU virtual machines under the hood. Which means you can use standard tooling and workflow should you need it for some edgecase.
• You mentioned Jellyfin in a container: My understanding is that Jellyfin in Docker has some extra limitations or complexities when it comes to hardware encoding.
  • Jellyfin also has official documentation for how to deploy in LXC container and get HW transcoding working (Less complex than in Docker).
  • LXC containers are not like Docker containers. While a Docker container is meant to be an immutable image of a (single) application, LXC is more like a full fledged VM, but without the overhead of virtualization. LXC containers are full systems, and you install software via the usual apt, dnf etc
  • The "correct" way to run Docker in Proxmox is to run Docker in a Virtual machine. Installing Docker inside a LXC container is also possible, with some caveats. Installing Docker directly on the Proxmox host is not recommended

For reference, my oldest Proxmox server is a 2013 AMD dualcore 16GB DDR2 ram with VMs on LVMthin on a single SSD, with legacy VM doing mdraid of 3 HDDs using hardware passthrough. Performance is still OK, the overhead from Proxmox is negligible compared to strain from the actual workloads

"QR & Barcode scanner" is Free an Open Source, and supports what you want (if i understood you correctly) https://github.com/wewewe718/QrAndBarcodeScanner

Looks like it's not been updated in a while, but it works just fine. Available on F-Droid and on Google Play