I have no issue with corporate funding. I have an issue when a company gets to make all the decisions. Lot of good software has gone to hell when the shareholders need profit now instead of seeing a long term vision.
We’ll see, but I’ve been around this rodeo enough to just avoid it from the start and take some pain now instead of putting in effort that’s going to be wasted later.
2023, I remember the announcement last year. Not sure where you’re getting 2014 from, that was even before NC split off.
What puts me off of Owncloud is the new ownership. I couldn’t care less if it’s written in the blood of Christ, if I have to worry about the rug getting pulled out from under me for self-hosting, it’s a no-go for me, Joe.
Nextcloud works well for me and has for years. The people that don’t like it can go use this, and we’ll see you back in a couple of years when it goes open-core or worse.
Probably depends on the ISP, but I just have 2 nics in each server, and eth1 on both is on a switch to the cable modem. If one goes down, the other comes up fine. Can’t recall if I spoofed the same MAC on the OPNsense VMs.
VMs under KVM are pretty much bare metal and Proxmox doesn’t use much for resources itself, it’s basically a headless Debian with a webserver interface to do all the KVM stuff.
Proxmox, especially if you use ZFS for the VM datastore, makes a home lab so much easier to revert, backup and deploy/clone VMs and LXCs. I highly recommend it if you’re just starting out. Once you wrap your head around it, it gets out of the way and lets you just tinker with your projects, and not have to manually do everything in VirtManager or at the command line.
Combined with Proxmox Backup Server, it’s a production ready hypervisor for anything you decide to keep. Also, the HA features work well enough that I had my main routing OPNsense VM jump between nodes when the primary node lost a drive, and I didn’t notice for a week, it was that seamless.
If you want to lose most of your tooling and community support, Podman is a great way to go.
Your Overton Window has fell off the side of the building and broken on the pavement.
As to why distro maintainers go along, if you had to vet every time the network stack updated and make sure it doesn’t break your custom solution to predictable naming, you’d probably just go along with it and let anyone that needed it devise and maintain their own solution. 99% of users won’t worry about it.
Use a firewall like OPNsense and you’ll be fine. There’s a Crowdsec plugin to help against malicious actors, and for the most part, nothing you’re doing is worth the trouble to them.
Governments are not anyone’s issue other than other governments. If your threat model is state actors, you’re SOL either way.
Making it harder for everyone else is the goal, and to do that you need a swiss cheese model. Hopefully all the holes don’t line up between the layers to make it that much harder to get through. You aren’t plugging all the holes, but every layer you put on makes it a little bit harder.
And NAT is not just simple to set up, it’s the intuitive base for the last 30 years of firewalls. I don’t see where you get a cost from it. As I said, separating network spaces with it comes naturally at this point. Maybe that’ll change, but I remember using routable IPV4 when it was it the norm, and moving to NAT made that all feel way more natural.
Obfuscation is not security
Yes, of course. But saying trite things like that doesn’t get around the idea that giving out a map of the internal network by default isn’t the best policy.
NAT still has its place in obfuscating the internal network. Also, it’s easier to think about firewall/routing when you segregate a network behind a router on its own subnet, IMO.
I left IT about a decade ago to farm 3000 acres and 300 cows.
It is very much not retirement living.
I used to be a network engineer and I found farming bloody complicated. You might be very surprised at the breadth of knowledge it takes to successfully farm today.
My god, that was 15 years ago.
Yah, but the UK has been an Orwellian nightmare since Maggie’s day. Everyone expects laws that completely negate privacy there and just roll over for it.
IDK, I’ve found Gnome unusable for a long time. I tried to make up for it with extensions for a while, but every release would unapologetically break something I found essential and the extension devs would give up trying to keep them going.
I understand that eventually they got better about dropping breaking changes without warning, because extension devs were leaving in droves, but at that point KDE got good again with Plasma, and I’ve never looked back.
Gnome has their vision to be a completely hands off, dumbed-down, unbreakable DE for the lowest common denominator. I guess judged by that light, it’s a success. It’s the default in a lot of distros because it’s low maintenance for packaging and support. Frankly, I think it’s a major reason for the slow speed of Linux desktop uptake, but what do I know.
Gnome devs judge release success by the amount of features they managed to remove since last release and make it easier to maintain.
Eventually it’ll be one button in the middle of the screen that turns it on and off.
Lucas anything.
Jellyfin is basically a storage/streaming server. You still have to get the files, which is where Sonarr/Radarr/QBT come in.