That would be a very satisfying ticket closure

“Only Happy When it Rains” automatically begins playing in head

Tubesync is pretty great

Bat bat bo-at

Bonbaten-fana fo-fat

Fee-fi-fo-fat

Bat!

Not if you’re serving content to a device that can do the decoding, like a Shield. My Jellyfin server runs in a Proxmox VM with no GPU passed though, and transcoding disabled for all accounts.

Gitlab is pretty great!

I wonder how many fucking numbers and letters they will keep adding over the fucking years.

Numbers and letters over the years:

“You shall love your neighbor as yourself”

Galations 5:14

“Be genial, sweet and kind towards your companions.”

Mino-ī-Kherad, II.7

“For my people are foolish; they know me not; they are stupid children; they have no understanding. They are ‘wise’—in doing evil! But how to do good they know not.”

Jeremiah 4:22

You may want to give it another shot. They’ve been working pretty hard to move away from config files - much more is done via the GUI these days to make things more user-friendly.

The devs have also really been focusing on voice this year as well - it’s been really interesting to see what they come up with. A few releases back, they released an update that allows you to give voice commands to HA via a landline phone hooked up to a $30 VoIP box. There is also support now for Espressif’s new “S3-Box” devices, which have small screens, a speaker and a few microphones for under $50 - this does require messing with yaml files at this point, but I should be able to finally ditch my Echos soon!

You can easily have a smart home without any data leaving your home network.

You need three things:

• Home Assistant software (free and open source)
• ZigBee (also free and open source) smart devices made by companies that comply with the ZigBee protocol
• Most importantly, a ZigBee controller.

There are several options available (Deconz Conbee II, etc), and this device gets plugged into the same machine Home Assistant is on, and it allows HA to control your ZigBee devices directly. No “hub” sending your data to a cloud server, everything is done on your local network. If the devices comply with the protocol, you don’t need their hub, even if they say it’s required.

I use Hue bulbs, but have no Hue hub. I use many Aqara devices, but don’t have an Aqara hub. It’s pretty great and works very well!

crushed by a herd of elephants

OG Hannibal style

A Hitler scenario would be damn terrifying.

Fun fact: This guy is from Coeur d’Alene Idaho, which was famously the home of the Aryan Nations group. Probably not a coincidence.

Who have been subjected to targeted information warfare/propaganda for years.

If you’re rural, check out B4RN.

Unfortunately not, it applies to all clusters. A quorum requires at least 2 votes, which means 2 nodes. But if one node goes down, you only have 1 vote, and the cluster will go into read-only mode, which means you’ll lose the GUI and the ability to manage your nodes:

When your cluster is non-quorate (so at least half of all nodes are dead), the remaining nodes will change the PVE management into read-only mode. Because of that you will no longer be able to change and manage your VMs and containers and will also not be able to log into the GUI. This is done to avoid cluster split-brain problems in which they run into inconsistent states. (Source)

But if you have a device that will supply a vote in the event that one of the two votes is unavailable, the cluster will continue to function with a single node, which will allow you to use the normal Proxmox tools and interfaces to diagnose the problem, while also keeping any VMs on the single remaining node up and running (available).

Here is a Proxmox employee explaining it a bit more clearly than the official documentation:

… a cluster needs to be always quorate to work properly, not just for HA. High availability just means that the cluster will try to keep your HA-enabled VMs and containers always available, i.e. if a cluster node fails the HA-manager will launch HA-managed guests on another cluster node.

While a 2 node cluster should work with 2 active nodes, if one of your nodes goes down your cluster will automatically be non-quorate and will no longer work as expected. To have quorum in your cluster, you need a setup of at least 3 nodes, though you do not need 3 full Proxmox installations … you can setup something like a Raspberry Pi as a QDevice for external vote support.

(Source)

You may have trouble keeping a quorum with a proxmox cluster of 2. You should really have 3, or set up a q-device. (Source)

Each node in a cluster has a “vote” in a healthy cluster. If one of your devices goes (or is taken) down, you’ll lose quorum, and the GUI and some other stuff. You need 3 votes for things to work reliably. I have an old RPi set up as a q-device and it works fine.

He’s using a pretty standard tactic for a right wing politician down in the polls: throw increasing amounts of crazy against the wall until something sticks and the polls improve.

His consultants will call this “calibrating”, to find the right level of insane to match voter expectations and grab media attention for a few cycles along the way.