Dran

I run ubuntu’ server base headless install with a self-curated minimal set of gui packages on top of that (X11, awesome, pulse, thunar) but there’s no reason you couldn’t install kde with wayland. Building the system yourself gets you really far in the anti-bloatware dept, and the breadth of wiki/google/gpt based around Debian/Ubuntu means you can figure just about any issues out. I do this on a ~$200 eBay random old Dell + a 3050 6gb (slot power only).

For lighter gaming I’ll use the Ubuntu PC directly, but for anything heavier I have a win11 PC in the basement that has no other task than to pipe steam over sunshine/moonlight

It is the best of both worlds.

Are you maybe thinking of https://distr1.org/ made by the i3 guy?

I think the vision was what Motorola delivered briefly a decade ago with webtop. The original version of it was a chrooted lubuntu with full access to apt, and custom applications that let you render your phone, or phone apps as an application. It was powerful enough to get me through my first 3 years of a computer science program in college with a lapdock as my primary “computer”. (Think a brainless laptop, that you dock your phone into)

https://arstechnica.com/gadgets/2011/03/motorola-atrix-the-ubuntu-powered-webtop-experience/

When they moved from android 2.3 to 4.0, they dropped the lubuntu webtop in favor of Android’s tablet mode, which was a huge bummer, and what made me get an actual laptop. Outside of gaming, if that were the average computer paradigm today I’d be a happy camper. Why buy two computers when you can buy one instead?

Generally the lifecycle with this sort of thing is old_thing becomes an alias to new_thing, and eventually old_thing gets dropped as an alias down the line.

It’s still decent advice to learn dnf native calls and to update scripts using yum to those native calls.

I’m a big fan of tiling window managers like i3 or awesome (awesome wm). Awesome is the one I use. It’s tiling and the entire interface is built from scripts that they encourage you to modify. Steep learning curve but once you get it how you like, there’s nothing like it.

buy it from somewhere that has a 14 or 30 day “no questions asked” return policy. A competent retailer will have that baked into their margins so don’t feel bad doing it. I think that’s your best bet.

Then pay for them or learn to bypass them, you ungrateful pissant.

I find it hard to respect opinions of those who do not seem to respect developers. Lemmy is a very niche product, third-party clients are an even more niche subproduct. We are lucky to get something as polished as sync and if the guy values his own time at $20/user for the good experience with this few paying users, it seems very ungrateful to complain about it without suggesting an alternative to keep the guy fed. There cannot be a very large market for premium lemmy apps. Compound that with designing his app in a way that dns adblocking doesn’t break the app. I dns adblock, have never seen an ad on sync, and I still paid for the ad-free version anyway just to support the project.

If you make more money at the top, leave it at the top. If you make more at the bottom, put it at the bottom.

How much poop in the soup is too much poop before $20 becomes reasonable? Just deal with it, switch apps, ad block, or pay the man. There’s an option in there for everyone

especially true for when manufacturers stop supporting the console you invested into, stops making replacement parts, issuing security patches, etc. Having the ability to make, repair and use copies of the games you purchase is critical to digital preservation.

I certainly wasn’t just born good at this. Unironically if you want to learn how something works, try to automate it. By the time it’s automated you’ll understand basically every part of it at at least a basic high-level.

I have condensed almost all of my workflows into pure bash scripts that will run on anything from bare metal to a vm to a docker container (to set up and/or run an environment). My dockerfiles mostly just run bash scripts to set up environments, and then run functions within the same bash scripts to do whatever things they need to do. That process is automated by the bash scripts that built my main host. For the very few workflows I have that aren’t quite as appropriate for straight docker (wireguard for example) I use libvirt to automate building and running virtual machines as if they were ephemeral containers. Once the abstraction between container and vm is standardized in bash, the automation doesn’t really need to care which is which, it just calls start/stop functions that change based on what the underlying tech is. Because of that, I can have the canary system build and run containers/vms in a sandbox, run unit tests, and return whether or not they passed. It does that via cron once a week and then supplants all the running containers with the canary versions once unit tests pass.

Basically I got sick of reinventing the wheel every time a new technology came out and eventually boiled everything down into bash so that it’ll run on anything it needs to. Maybe podman in userland becomes the new hotness next year, or maybe I run a full fat k8s like I do at work. Pure bash lets me have control over everything, see how everything goes together, and make minor modifications to accommodate anything I need it to.

It sounds more complicated than it really is, It took me like a week of evenings to write and it’s worked flawlessly for almost a year now. I also really really really hate clicking things by hand lol, so I automate anything I can. Since switching off proxmox, this is the first environment that I have entirely automated from bare-metal to fully running in a single command.

I’m incredibly lazy; it’s one of my best qualities.

Virtual machines also exist. I once got bit by a proxmox upgrade, so I built a proxmox vm on that proxmox host, mirroring my physical setup, that ran a debian vm inside of the paravirtualized proxmox instance. They were set to canary upgrade a day before my bare-metal host. If the canary debian vm didn’t ping back to my update script, the script would exit and email me letting me know that something was about to break in the real upgrade process. Since then, even though I’m no longer using proxmox, basically all my infrastructure mirrors the same philosophy. All of my containers/pods/workflows canary build and test themselves before upgrading the real ones I use in my homelab “production”. You don’t always need a second physical copy of hardware to have an appropriate testing/canary system.

I can’t say I’ve ever seen that, but it wouldn’t be hard for an iptables rule at the egress to just block outgoing traffic to 8.8.8.8. it’s not a great workaround for content providers. Especially because there’s definitely a universe where Google kills their DNS offering and a bad actor sets up a DNS server on the same static IP. Not that this isn’t an issue for domains too, it’s just another immutable and this one costs more than a subdomain to maintain.

Dns resolution is integral to load balancing and regional content delivery. There is no universe where a single server, even a specially designed asic, could handle proxy routing if there was a DNS outage and every iPhone or android device or whatever failed to a single IP. Thank God the Internet works this way tbh, dns-based content blocking will probably be the only thing we can do eventually

Are… hygienists famously known for not being smart? I don’t think that’s a thing lmao

Generally end-user applications like Firefox would be the latest/same version, but system libraries might be a few versions different. Generally security patches are written for a few major versions of libraries/daemons at the same time. So features might be different but it’s all the same security for the most part.

That’s the major draw between one distro to another, they will have different philosophies on what to include, and what major version to use. Debian for example is much more reluctant to upgrade something unless there’s a large demand for a new feature. The theory is it is more stable and consistent to use that way.

Ubuntu on the other hand features much more modern versions of libraries because they want to be more hip and modern, expecting users to learn new things more often because they think the new features are worth it and they want to support all the things.

Yes but they use different repositories with different maintainers. Think of a package manager like steam, epic, etc, except instead of games it’s everything. Some package managers get different applications, some have different versions of the same applications. In the case of Debian/Ubuntu it’s more like steam in China vs steam in the rest of the world. Same steam, different games, different maintainers of who decides what games get to go in which steam.

This still doesn’t solve the issue with underlying kernel feature and function compatibility. 99% of the time when I have an issue getting something to work, it’s because of something like my LTS kernel doesn’t support floc(), etc.

This only solves competence issues, it does nothing to resolve the difficult compatibility problems.