Crashing and burning (in a non-production environment) is an excellent motivator to develop necessary skills; being unafraid to break things and fix them when they inevitably break helps you get a deeper understanding of how the systems work, for what it’s worth.

This appears to be a variation of the “standwich.” Please see the attached for an example.

Running an RKE cluster as VMs on my ceph+proxmox cluster. Using Rook and external ceph as my storage backend and loving it. I haven’t fully migrated all of my services, but thus far it’s working well enough for me!

Good bot

I don’t know how I feel about this personally. On the one hand, I feel like this is a privacy win for those who want it: no watch history means no algorithmic recommendations and (presumably) less data collection for those users. On the other hand, I personally really enjoy the recommendations that YouTube makes for me. Maybe it is the wide variety of content that I watch, but I’m honestly very pleased with the recommendations that YouTube provides. That being said, I feel like the opt-in to algorithmic recommendations is a good thing overall, however I am personally going to leave my watch history enabled.

Back when COVID was in its prime, I was contributing CPU/GPU cycles to Folding@Home for protein folding simulations and working on a vaccine. Since then, I’ve reimaged my desktop twice. I should probably reinstall the BOINC client to contribute again…

Thanks for the info. That seems quite heavy handed.

I’m out of the loop, what is France trying to do with regard to DNS?

Here’s the link to the study: https://doi.org/10.3390/s23136205

A modern classic IMO 🤣

Hello fellow domain hoarder 🤣

Hello from onlylans.io

I’ve used the PWA, Jerboa, Liftoff, and Connect.

Jerboa is probably my favorite of the bunch. I prefer how compact everything is and the 0.0.33 version was working well. I upgraded to 0.0.36 and performance took a bit of a hit so I figured I would explore alternatives. Also when I looked at other options 2FA support had not been added (it’s working as of this post)

The PWA is more than functional,and I like it quite a bit. Don’t like that backing out of a post navigates to the top of the page though.

Connect is good too, just personally not a fan of the larger interface, even in list/compact mode.

Currently using liftoff. Performance is good, 2FA support is available, and in list/compact mode it’s tolerable. I still do prefer the compactness of Jerboa though.

Very frustrating to hear. I’ve been slowly migrating away from RHEL-based distros after they shifted CentOS to be upstream from RHEL. This is another nail in the coffin in my books.

I’m posting currently from the PWA after I enabled 2FA on my account (not currently working with Jerboa). It’s nice and works well, but I prefer the more compact list view present in Jerboa. Other than that, no complaints!

Oof

I have Lemmy running on my homelab behind Cloudflare, though I’m using a reverse proxy setup. I made some minor modifications to the provided docker-compose.yml to get everything working with my existing reverse proxy setup.

As for backups, I want to say so long as you back up the postgres database and import the backup on your new server you should be good. I believe there’s a section in the Lemmy docs on how exactly to do that process.

Cloudflare tunnels are great but OP may not want to have to authenticate each user to their services.