Self-hoster/FOSS Pronouns: He/Him
Treat the response like you would of an LLM, it needs to make sense to you, you need to make sure they aren’t messing with you or have given you a fix that only works in their case. Usually the best fixes are the simple ones. And it seems like even with the longer ones you’re able to figure out your simple fixes which is awesome!
But states rights? What happened to states rights?
You can also host it yourself.
Depends on the level of block lists you add. The defaults are pretty sane and it doesn’t need any configuration, you configure your router to use it
Pihole, homeassistant, a music server using moodeaudio
There’s also Zed. And helix.
Amongst all the other great alts here
Also neovim is really dope! Just have to throw that there
And enjoyer
When you really wanna pursue slack
Slackware!
And I use Slackware fwiw
While I agree with your point I don’t think a lot of people will be open to that cause they may not be aware of base distros and all that and in the end it would seem like you’re not listening to them.
OP literally said they want to avoid mint due to bad experiences.
I get that but at this point shouldn’t we get more people on this side. Like I think redhad and canonical are infinitely better than microsoft. Lesser of 2 evils and all. Who knows one day they may start using arch (btw)
Also uwuntu is a derivative of Ubuntu.
While I agree with the sentiment, fedora is fairly independent to their RHEL in terms of operations right?
The fork that takes off will be the one where the Firefox devs move to. Which isn’t predictable. We could make our own foundation, without the blackjack and hookers (cause based on how mozilla was doing things it sure seems like all they did), and make it more as a means for the devs to get paid for their work.
Well goodbye mozilla it wasn’t great knowing you. Hopefully you are able to fuck over the devs and golden parachute your c-suite bastards one last time.
So, in slackware you get dependency resolution via sbopkg which installs any third party tool, but it’s done by maintaining a list of dependencies for each thing in a file, parsing that and then creating a DAG (directed acyclic graph) as needed. It keeps the system simple and manageable as most tools if not all are bash scripts.
Cons include having to manage it yourself and needing to install the full base to ensure you’ve got all the assumed packages installed.
There is no right and wrong answer tbh kinda just a matter of taste.
The thing that I like is that it since most third party packages are built from source I can force it to compile on my single stack of tools. I don’t need to have multiple versions of a library installed cause a package needed different version of something. Things stay fairly coherent. And maintaining a mirror becomes easy as you only need a couple of GB for a release compared to the terabytes needed for an Ubuntu as you’ll need all the various packages available to resolve all possible dependencies. This to me is doesn’t make sense from a maintenance PoV. Also your system doesn’t do things you’re not aware of.
Tho arch kinda does something similar by offloading third party packages to the aur. Where things are compiled by source mostly
Here’s some thoughts from someone in the community https://docs.slackware.com/slackware:package_and_dependency_management_shouldn_t_put_you_off_slackware
I hope my word salad makes sense!
Lolol yes, it’s a weird straight circle indeed.
However applying those fixes and then learning to fix it is a great way to learn how to troubleshoot and unb0rk your system.