I tried learning using several different resources, but what did it for me was the nix pills (https://nixos.org/guides/nix-pills/). I'd say it's becoming a bit outdated now with the nix standalone command, but the fundamentals are still mostly the same.
I was kinda surprised to see that the development repos are hosted using mercurial (https://hg.slitaz.org/). I don't remember seeing other Linux distros using mercurial instead of git for development. The repos are apparently mirrored on GitHub but I don't see a lot of development happening there.
Currently, my main concern with YAML is that, by the spec, comments are not attached to a particular node (see https://yaml.org/spec/1.2/spec.html#id2767100). As a result, a lot of YAML parsers (like https://github.com/yaml/libyaml and https://github.com/chyh1990/yaml-rust) only filter out the comments during the parsing phase. This makes it less than ideal for a use-case where the configuration file is expected to be modified by both programs and humans.
TOML makes it more trivial to associate comments with a node. This is mainly because the language is simpler though, as the spec is not explicit about that (https://toml.io/en/v1.0.0#comment).
The project depends on `libspeechd-dev`/`speech-dispatcher-devel`, but there's no mention of support for voice commands. Does the framework support speech recognition? That could be pretty neat.
Been using Element for a while now (since back when it was called Riot). So far so good. I managed to convince a few friends to switch over from Hangouts and Signal. There's even a Rust Weechat plugin for Matrix, the underlying protocol. Would love to hear feedback if anyone tried it.
> An additional DisplayPort 1.2 output is provided via the USB C port.
For me this was the missing feature from the latest RPi. If on top of that the board can run a vanilla Linux kernel (the RPi can't from what I understand), I'm definitely buying one.
In my opinion the highlight here is the addition of the "Only this time" option when granting permissions to an app. I'm wondering though if this new privacy feature is only available for the 3 permission types listed in the post.
> With one-time permissions you can grant apps access to your microphone, camera or location, just that one time. The next time the app needs access to these sensors, it will have to ask you for permission again.
The vi mode for Bash. Blew my mind when I discovered it and it probably saved me hundreds of hours already.
I used to have multiple copies of this cheatsheet [0] at my desk for every new developer I would see editing a terminal command with the left and right arrows.
You can have a separate database file as a backup for your TOTP secrets. This way you can setup the TOTP with KeePassXC directly, then transfer the secret to your phone for example. This assumes you can trust the device from which you setup TOTP with KeePassXC.
I had to setup CI for a GitHub open source project recently, and decided to give GitHub Actions a try. I have to say it's pretty nice to have the CI directly handled by GH (GitLab has been doing it for years, I know...). I hope it's gonna help some open source projects to easily add CI validations to their PR workflow.
That being said, there was only Ubuntu images for the Linux builds, and I'm not aware of a way to run custom containers at the moment.
I received mine 2 weeks ago but still didn't test it. From the dev channels, I think they're still having some software issues with the screen on the dev kit.