I just use termux + the simple http server built into python
No one complained when s6, another init system, also offered a sudo alternative (before systemd did, too). But when Poettering does it, it's bad and wrong and ununixlike!
Maybe setuid has been extremely problematic, and more than one entity has sought alternatives?
What? Github is not open source.
And plenty of people have issues with Github: https://sfconservancy.org/GiveUpGitHub/
their entire hosting site is, itself, proprietary and/or trade-secret software
Discord is adding ads soon. Currently, they don't enforce the TOS violation of custom clients, but maybe after they add ads, they will begin to do so. I would be very careful with any of this.
Non linkedin link shortener link (yes I want to go to a page that's not linkedin):
The person telling you to "learn what AD is" is kinda a douche, but they aren't wrong.
AD is mainly 3 components in one:
- Configuration management across a variety of machines
- Shared logins
- Shared user data across many machines
All of these are doable on Linux. In many ways. Many, many ways. That you have to set up yourself.
For configuration management, do you want ansible, puppet, chef, nix, etc?
For shared logins, do you want openldap, lldap, Red Hat's ldap, etc?
For shared user data, do you want nfs, systemd-homed, or something else?
And for all of those, you have to evaluate, maybe test, and then select a solution, and then set it up yourself in a resilient manner.
Nixos, as a server distro, can host the relevant services needed for this. As a desktop distro, it can also do configuration management. But that's missing the point of AD, in my opinion.
The point of AD, and how it managed to become so popular, is that it is all of those, in an all-in-one solution that is simple to use (joining Windows machines to a domain is trivial), and it also comes with paid support.
Even if you were to build your own alternative on Nixos, which would be a lot of tinkering and twiddling, then you would end up with some of the same core features, but you would have to maintain, secure, etc, it yourself, and not having to do those to such an extent is why people buy Active Directory. There would be no alternative to things like Group Policy, instead you would be writing your own nix code.
So yeah. Unless someone comes along and builds an all-in-one solution on top of Nixos, nixos isn't really an alternative to active directory. You can replicate the core features. But it's not an alternative.
https://nixlang.wiki/en/tricks/distrobox
Not the nix way, but when you really need something to work, you can create containers of other distros.
Was watching a twitch streamer learning linux, and chat convinced them to open vim for the first time. Not a single person gave the real answer of how to exit, all joke answers like "Power off," and it was hilarious.
The screen uses the most power out of any other piece if thr system, for daily use (on laptops which supported driversets for the OS)
Just turn the brightness down, and that will save you more battery life than tinkering with anything, unless you know a specific piece of the system (nvidia gpu) is killing your battery life.
where does diagonal fall?
The issue people have with snaps isn't the containerization or the bundles, but the proprietary backend. There is no way to point the snaps at a different store other than the one canonical controls. Canonicals forcing snaps on people pisses a lot of people off because it's a blatant power grab, an attempt to get people dependent on something they have control over in a microsoft-esque move. Flatpaks and docker don't have that issue.
The solution to what you want is not to analyze the code projects automagically, but rather to run them in a container/virtual machine. Running them in an environment which restricts what they can access limits the harm an intentional
or accidental bug can do.
There is no way to automatically analyze code for malice, or bugs with 100% reliability.