Could I play around with it by installing in qemu and if I like that, take my configuration.nix from qemu and install it as my main OS?
Absolutely. That's how I got started ;)
If you install Nix (the package manager) on your current system, you can actually directly build a vm from a config file via nixos-rebuild build-vm.
NixOS can’t configure desktop environments, such as Gnome and KDE.
That's because those DEs are configured via config files in your home and NixOS is only about system management; it does not touch your home (other than creating its directory).
If you want to configure home files, you use home-manager which has some support for configuring those DEs.
NixOS is stable, so NixOS works best in server environments.
NixOS has a "stable" version and a rolling one. The stable one is bi-annual though with no LTS, so it's more of a Fedora than a Debian.
The rolling channel ("nixos-unstable") is where all the actual development happens. It has similar stability to Arch, though we do more QA through our CI.
You cannot get an update where the e.g. bootloader breaks. That just doesn't happen for us because the update must have passed a test where the bootloader gets installed in a VM and then booted before it can reach you.
there was a point where the NixOS stable branch… broke. I’m not sure what went down, but I think that a manual merge train messed smth up.
Stable is pretty damn stable, we usually only backport security fixes and the odd bug fix. If a bug fix introduces new bugs, that could "break" stable in a way but stable "breaking" in a major way is pretty much unheard of. Again, as I mentioned, basic things like networking or filesystems are tested by CI.
You're going to have to be a bit more specific than that.
There’s also the situation where they store the entire package store in Amazon S3 because someone else paid for it. That someone disappeared, and they expect the community to stem the costs now. If they don’t pay up, NixOS stability is once again dead.
This is way overblown. That someone is still paying. They've just said they don't want to continue doing so (which is absolutely understandable) and asked to find an alternative soon. They're not suddenly cutting us off; this is not an immediate threat.
The NixOS foundation has funds set aside to continue even this very expensive way of hosting the cache for at least a year. Even if they were to suddenly cut us off (which they won't), we'd be fine.
The post you linked is a call to action to find solutions to reduce that cost and to find a way to sustainably finance it without relying on a single sponsor.
More critical would be if the CDN in front of the S3 Bucket (which is what actually serves most paths to users) were to disappear but the provider of said CDN is directly sponsoring us they haven't shown any sign of wanting out. People are brainstorming to find possible alternatives to that setup aswell though, just in case.
We're fine. Even in the worst case scenario, we'd be fine. In the migration time frame, there might be hiccups here and there but that's not too concerning or special.
I feel like the tooling is all over the place. There are many ways to do one thing, and you never know what’s the right thing to do.
Yeah, tooling has been in a bit of a weird spot where we're currently in the transition between the old and the new way of doing things. The new way isn't finished yet however an is still unstable.
The "old way" works just fine though and you can ignore all the new stuff if you don't like instability. I myself still use the old way. Sometimes I use the "new way" too because it's got some convenient features.
I’m just terrified it’ll get my underwear and clothes wet while being cold and unpleasant.
The beam is way more focused than you might imagine. It can't reach your clothes, there's a fat-ass human in the way ;)
Als vom Endnutzer entfernbar sollte eine Gerätebatterie gelten, wenn sie mit handelsüblichen Werkzeugen aus dem Produkt entfernt werden kann, das heißt ohne Verwendung von Spezialwerkzeugen, es sei denn, die Werkzeuge werden kostenlos bereitgestellt, oder von herstellerspezifischen Werkzeugen, Wärmeenergie oder Lösungsmittel für die Demontage. Als handelsübliche Werkzeuge werden Werkzeuge angesehen, die Endnutzern ohne Nachweis von Eigentumsrechten auf dem Markt zur Verfügung stehen und ohne Einschränkungen - mit Ausnahme von Gesundheits- und Sicherheitseinschränkungen - verwendet werden können.
Ich les das so: Wenn du die ohne Spezialwerkzeuge entfernen kannst, passt das.
I see two reasons:
This is more a question for /c/lemmy
Not 100% sure this device even has a chip. SatStat doesn't show values for orientation; only for magnetic field which I heard Is used to emulate a compass but I'm really not sure.
Das ist sorgfältig so formuliert, dass das wirklich nur Geräte ausnimmt, die speziell für den Unterwassergebrauch gemacht sein:
Um die Sicherheit der Endnutzer zu gewährleisten, sollte in dieser Verordnung für Gerätebatterien in Bezug auf Geräte, die Gerätebatterien enthalten und speziell dafür ausgelegt sind, während des aktiven Betriebs hauptsächlich in einer Umgebung eingesetzt zu werden, in der regelmäßig Spritzwasser-, Strahlwasser- oder Unter-Wasser-Bedingungen herrschen und die abwaschbar oder abspülbar sein sollen, eine begrenzte Ausnahme von den für Gerätebatterien geltenden Entfernbarkeits- und Austauschbarkeitsanforderungen vorgesehen werden.
Auf Smartphones trifft das nur selten zu; die sind zwar oft wasserfest, aber offensichtlich nicht dafür gemacht, hauptsächlich Unterwasser benutzt zu werden.
Selbst wenn es wasserfest ist, muss man, wenn sicherheitstechnisch möglich, das Gerät so gestalten, dass sich der Akku tauschen lässt:
Diese Ausnahme sollte nur dann gelten, wenn es nicht möglich ist, das Gerät dahingehend anders auszulegen, dass die Sicherheit des Endnutzers und die sichere Weiterverwendung des Geräts gewährleistet ist, nachdem der Endnutzer die Batterie unter ordnungsgemäßer Befolgung der Gebrauchsanweisung entfernt und ausgetauscht hat.
Es gibt jetzt schon IP68-Rated Smartphones mit austauschbarem Akku, von daher...
So, und wenn das auch nicht möglich ist, dann muss man das immernoch von unabhängigen reparierbar machen lassen:
Wenn die Ausnahme gilt, sollte das Produkt so ausgelegt sein, dass die Batterie nicht von Endnutzern, sondern nur von unabhängigen Fachleuten entfernt und ausgetauscht werden kann.
Das absolute "🖕-Apple-Gesetz". Holy Shit.
Wer hat dieses Gesetz geschrieben und wie zur Hölle haben die das an CDU und deren "Freunden" vorbeigemogelt?
Well, that's the crux. "Public for anyone to use" is a huge liability. No public service is really secure. They can be hardened but that's about it.
One way to harden a locally hosted setup could be to use Tailscale funnel. It's effectively a proxy for network traffic to one specific port of a machine on your network. You don't even need a static IP address or open ports here.
You're still vulnerable to problems with the specific service you're exposing though, so it's highly recommended to harden the service itself. Containerisation can be an option here but also systemd service hardening.
Step #1 is to package cockpit-machines. I haven't dared to touch JS with even a 10ft pole, so I can't help you with that but I can highly recommend to take a look at how similar packages work and copy what they do.
Modules come later; they just wire up some packaged applications to the system. I'm not familiar with the project but it seems like cockpit-machines is a UI of sorts? If it doesn't need any system configuration, you don't need a module. Users would just install the package, run the binary and that's that.
Modules are for when you need e.g. a system service like a web server.
I also used it for a while but I find that I use a set of apps all the time and simply tapping a known position on screen is just so much faster.
"Normal" launchers have searchable app drawers too, so that works for the rest.
With those requirement, the first question you should ask yourself is whether you really want e in your bike at all.
What are the reasons you want an electric bike over an acoustic one?
Next is what you're going to be using it for. You said it was for the daily commute. A commute can be anything from a 5min ride through a quiet neighbourhood to a 1h ride through the forest and countryside.
Distance, terrain, traffic etc. make a difference on what kind of bake suits your best. How does (or will) your commute look like?