Yes, and thank you for your interest in helping. Appreciated! After an update, I will eventually reboot. When doing so, the options in the gear at the Gnome login will be

• Gnome
• Gnome Classic

Both of these options are X11. I verify this with $ echo $XDG_SESSION_TYPE and see X11. When Wayland is working, the Gnome login will show four session types:

• Gnome
• Gnome Classic
• Gnome on X.org
• Gnome Classic on X.org

I haven't been able to locate a log file where something looks relevant to the decision made at boot for XDG, Wayland, or X11 that chooses one over the other. It's just as though Wayland stops being an option. 3 or 4 updates later, I'll have Wayland back again - but no idea why it comes and goes. My caveman intuition tells me it happens around nvidia updates, but I haven't kept strict notes on that.

I did try Bazzite after this post - defaults to Nvidia 560 driver, which is still not the stable. Also installs extra things that I had to turn off - ended up re-wiping and going back to Fedora 40. I may retry in the future, though - but in general, I'm less interested in immutable at this point.

Thank you for the suggestions!

I disagree! They can be great options, inexpensive and reliable. My current home server is a Dell r620 with xeon CPUs, 64gbs of RAM, and 2 terabytes storage in raid 5. It serves several vms, a mix of Windows and Linux. More than enough for many home set ups. Boots the os off a 16gb flash card. Cost me $185. Thing has been a tank.

I bought two short L brackets from home Depot, and have it hanging flat against the wall. It's been fabulous.

Well now I have a new book (series?) to read, this looks super awesome, thank you

Nice!

Always love these kinds of questions, and love how you are working to build this community.

I work for a government agency as a deputy ciso, and I'm putting together a decision package for legislature to request new staff. I'm looking for five new members of my team, which would slightly double our size. It's a very long process, which involves a lot of capacity planning, reading strategic plans and tying it to things other people have talked about, demonstrating work bottlenecks through metrics from our soc, and leveraging relationships and capital Goodwill that I've built over the last couple years.

Cross your fingers for me.

This happens to a lot of bands

This is excellent, very useful for continuing to make images accessible on the fediverse

This was great! Love bikini kill, nice to see a Ska cover :)

If it's #2, I tend to scoop (with a plastic dog bag, I don't use one of those ) pretty much right away, tie it off & put it in the trash. I'm with @[email protected], changing to wood cut down on smell quite a bit. I change it out once a week now.

There's wood pellets in there now :) Big fan of wood pellets since 2020!

Ayy, nice work getting started down the selfhosting route! Start by remembering that security is a maturity process. To find out if you're doing the right things at the right time, ask yourself:

• Do I know it needs to be done
• Have I done enough (this day, week, etc)
• Do I have it to give

If you're just one person and it's a self-hosted home setup, remember you can't patch all the things all at once. Asking yourself regularly if you maturing your environment over time is essential. Do a little work each week and you'll make good progress.

When I think of security, I think of a few things

Authentication & Access - each system should have just enough accounts with just enough permissions to get work done. Change default passwords. Make them long and unique. Use MFA whenever possible (often impractical for self-hosted; cut yourself slack when this is the case!). A note on logging - if you can, while you're doing this homework, check how long it saves logs. Shoot for keeping logs longer if possible; I like 30 days, but you might want more. Also make sure you have a time server, or at least that you're getting accurate time stamps. If something weird happens and you're investigating, having timestamps on logs that line up and make sense helps you recreate what happened, so you can decide if you need to wipe something and reload it.

Patching - automated scanning of your stuff for vulns would be fantastic if you're interested in going that route, but a Saturday morning checklist to run updates on everything works too.

Attack Surface Management - if you're not sure you're exposed, scanning externally can be a big help. I have a Racknerd server ($40/yr, it's amazing) in San Diego and I periodically run scans of my home network to see what's forwarded. This is using nmap, although I could also use a free version of Nessus Essentials on there. This gives me an idea of what I look like from outside my network.

Inventory - do you know what you have, and what's it doing? Even a pencil drawing of your network, IP addresses, and services they have can come in super handy. While big orgs have an index of critical data and where it's stored, just knowing what containers are running on which VM or physical box can help if stuff goes sideways. I redraw mine periodically, yes it's hand drawn because it's fast and does the job lol. Do what works for you, though, to keep an inventory of your stuff. You need to know what you have, what it does, and where it's supposed to be going.