Mit https://github.com/LemmyNet/lemmy-ui
Viel Spaß beim Hacken ;)
what if they only distribute it to companies that sign an agreement not to redistribute?
You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
I often see self-hosted blogs and blogs on Github Pages.
Commies full of Leminists!
as a bonus I would love a system that kept all things related to the user in /home
To get it out of the way first: There are no financial issues. There are more than enough funds to continue operations as they are for a sufficiently long time.
What is actually happening is that a long time sponsor has indicated that they (understandably) no longer want to foot the huge bill of hosting the entire archive of binary caches ($9000/mo). Finding a more sustainable setup is what the community is currently concerned with.
There is no risk of operations shutting down any time soon, the NixOS foundation has funds set aside to continue even this unsustainable setup for at least a year. We just want to be more efficient with our and others resources going forwards.
That's what all this you might have heard of is about.
Btw, even if the binary cache were to go poof, we don't technically need it. NixOS is a source-based distro like Gentoo and source hosting is not a concern. The binary cache is immensely helpful though which is why we'd obviously prefer to keep it.
I'd recommend reading some more; especially w.r.t. imperative vs. declarative.
In NixOS, you'd do something like this:
{ config, ... }:
{
environment.systemPackages = if config.services.xserver.enabled then [
package1
package2
package3
] else [
# You could optionally make headless packages available here
];
}
You don't need to understand the exact semantics here but you can look at it like JSON but with functions. This is not a "program", the end-result is just data. You're not modifying some stateful system state with new state from an uncontrolled source (i.e. the Arch repos) but rather just "outputting" a different dataset.
NixOS then builds a concrete system out of this pure data specification. In this concrete system, those packages' executables are available in the "global" PATH.
You say "I want a system where x y z are installed" and it does it for you in a standardised manner. With the bash script, you explicitly tell it each step ("install x; install y; install z"). This pure data nature is what's meant by declarative.
This distinction rules out whole classes of issues you simply cannot run into with NixOS.
Another aspect is that, as long as you use the same revision of Nixpkgs and the same config file, you can re-create the exact same system (almost bit-for-bit). If you were to run your bash script in a year's time however, you'd get an entirely different system with totally different revisions of software and therefore possibly entirely different behaviour.
This is what's meant by reproducibility.
You can achieve some of the same things NixOS does using imperative tools but nowhere near the same quality.
Well, Nix has a very liberal definition of a "package". Your web browser, its wrapper script, a service file, a config file; those are all technically "packages" (or "derivation" as Nix calls them).
GDPR applies to companies operating in the EU, not every single entity on the internet
It applies to every single public entity on the internet that holds data of EU citizens. No matter which country they're located in.
AFAIK, this world-wide nature of the GDPR is pretty unique and quite contentious.
The GDPR includes exceptions for private purposes but hosting a lemmy instance with public signups is most certainly not intended to be of private nature, so the GDPR does apply.
I can't comment on whether that means the right to be forgotten needs to be exercised by federated instances, I just want to set the record straight here.
In School here in Germany, what this post outlines is exactly what was told to us, by actual paramedics.
They even had a dummy AED for demonstration purposes. It spoke out the instructions like a real one would and we were all supposed to practice putting the electrodes in the right places on a dummy human.
Note that there's both the rolling unstable channel and a bi-annual stable release channel.
It's called "competition".