The kickstarter comments page of this product does not look so glamorous ( https://www.kickstarter.com/projects/tiinyai/tiiny-ai-pocket... )

There is also https://thingino.com/ which has a clear set of supported cameras. The installation is straight forward if you choose a cam with SD-Card flashing support. I upgraded two of the Sonoff Slim Gen2 without any issues.

I found Thingino to be very buggy and frustrating to use despite using 2 different supported cameras. The stream would constantly drop out, services would sometimes crash and wouldn't get automatically restarted. I tried tweaking all available parameters, resetting, updating but eventually I just gave up (a few months ago).

e.g. https://github.com/themactep/thingino-firmware/issues/640

I bought the cheapest PTZ camera they have listed and, as you say the install was easy. The interface is useful and it does what it says on the tin.

I also use thingino and it was very easy to use. It has wireguard support, but I just set up my firewall so cams are only accessible over tailscale.

I was pleasantly surprised to see the appropriate NixOS configuration in the middle of the article. NixOS stream-lines the whole configuration process to a couple of lines of configuration which can be copy-pasted without changing anything.

Isn't `dmesg` just `journalctl -k` on operating systems with systemd enabled?

It's more like the opposite. journalctl -k displays the kernel messages, but with a considerable amount of extra overhead because it has to go though the journal daemon.

https://github.com/systemd/systemd/blob/9afd5740391980fee5d8... https://github.com/systemd/systemd/blob/9afd5740391980fee5d8...

Whereas dmesg reads the kernel messages directly from the kernel.

https://github.com/karelzak/util-linux/blob/99c92a4820569970...

Not disputing your point, but some of that extra code does allow you to do cool things. Add a `-k -b=-{n}` to see a previous boot's dmesg, or filtering with `-k --until` for time filtering, &c. All with the same interface you're using to process your other logs too.

For me, the *_history is a deeply personal thing as it shows how i work and how i changed my working over the years.

I think you are very brave to make this document available to the world - it is not something i would like to do.

EDIT: I think of it like the browser history for your daily work.

EDIT 2: It seems quite a lot of people think it is a good idea to store their bash_history on github, who knew! google dork: "inurl:github.com intitle:bash_history"

Not quite the same but nix[0] and the nix expression language [1] is also missing from the list.

[0] https://github.com/NixOS/nix [1] https://nixos.org/nix/manual/#ch-expression-language

Sure, why not. Give us a master list with all the things.

on nixos it is:

    services.nginx.virtualHosts."myhost.org" = {
        enableSSL = true;
        enableACME = true;
        root = "/var/www/myhost.org";
    }

Put that in your host configuration and the nginx will be configured to start up the nginx with SSL enabled. All other locations required for the acme request are automatically configured. Systemd timers are also added for automatic renewal. IMHO it does not get any better than this.

edit1: no extra location required

More complex configurations are possible as well, of course:

https://github.com/Erisia/Madoka/blob/master/configuration.n...

The points why freelan is better regarding security are no real issues, but tradeoffs in terms of performance which just copy-pasted from the tinc-vpn security faq[1].

I have been using tinc for quite a long time and it feels pretty stable, but the configuration of new nodes is quite a PITA. For that reason a lot of bootstrapping scripts have been built around this [2]. Also, i love the possibility to easily dump the whole (known) network graph and create great graphs from this info [3].

I am using it mostly for reaching hosts behind NAT and creating a secure environment for these hosts.I never have tried the 'connect whole network' feature.

[1] http://www.tinc-vpn.org/security/

[2] https://github.com/krebscode/painload/blob/master/retiolum/s...

[3] http://euer.krebsco.de/graphs/retiolum/retiolum_1.svg

Tinc's problematic protocol (security wise) killed it for me before. For example, it didn't have pfs.

It seems that with 1.1pre3 or 4 they have gotten a new, experimental protocol. Hopefully it is an improvement.

it actually was and is up for me, just loading horribly slow. The essence of this post is: "Windows suspend/resume may work just fine. Mac too. But Linux’s suspend/resume isn’t a buggy pile of crap. It’s an intelligent buggy pile of crap, that just wants to be loved."