My understanding is that because of the type of protien that it encodes for, the immunity imparted by the vaccine decreases over time (because of complex immune system reasons). Never to 0%, but lower. The annual booster not only prepares you better for oncoming strains (in theory, when the vaccine research, development, and approval systems work as expected), but re-ups your immunity to existing strains.

The theory as I understand it is that because viruses like COVID-19 pass through populations in waves, your body is developing a very strong short-term immunity to neutralize any immediate “rebound” waves (imagine a wave bouncing off the side of a pool, yes, viruses move through populations like that). It then maintains a weaker, long-term response. By fooling your immune system into thinking you have COVID-19 right now, the vaccine bumps your body ino “short-term” response mode, so your best possible immune response is at the ready if the real thing shows up.

I am not an epidimeologist, but I read a lot of their work from 2020-2023. I might have details wrong, but if it’s been >6mo since you’ve had a booster, you would probably benefit from getting another one.

For those who don’t know, Bluesky isn’t really federated. The only way to host a non-Bluesky instance required 1TB of storage in July 2024, and 5 TB of storage in Nov 2024. Could be way more than that now.

You basically have to be a company to federate into the ATProto (Bluesky) ecosystem. You can’t just “stand up an instance”.

Lots of detail: https://dustycloud.org/blog/how-decentralized-is-bluesky/

(I know you’ve already realized that you were conflating Mastodon with Bluesky, I’m putting this here for others who come along so they can get the facts).

I don’t frequent that world much these days, but I personally preferred the agent/pull model when I did. I can’t really articulate why, I think I feel comfortable knowing that the agent will run with the last known config on the machine, potentially correcting any misconfiguration even if the central host is down.

The big debate back in the day was Puppet vs. Chef (before Ansible/SaltStack). Puppet was more declarative, Chef more imperative.

I also admit, I don’t like YAML, other than for simple, mostly flat config and serializing.

I further admit that Ansible just has a bigger community these days, and that’s worth something. When I need to do a bit of CM these days, I use Ansible.

So wait… Did Puppet have a license change as well recently? Is this just preemptive because it looks like Perforce is starting to change things?

Which documents, you say?

What happened?

Shredded, you say?

How badly?

To bits, you say? Oh my my…

Ahh, the comment I was looking for

I would have also accepted: “Haskell did it first.”

X2go is the successor to NX and works well IMO, though I’ve never tried Rustdesk to compare.

This is interesting because I’ve been thinking about switching from Debian to Arch. I’m already running Nix inside of my Debian installation to get more recent apps (I don’t like how snap interacts with the rest of the system, so I avoid it if I can).

Is there anything else on a more base OS level (like apt v pacman) that you’ve noticed is different, if you’re willing to share?