Opening the app for the first time on my Fairphone 5 (listed as unsupported) actually crashed the OS, but after that it seems to be working ok.

Closing out of the in-app gallery causes the app to crash. But that can easily be worked around by using some other gallery app.

I’ll be testing it for a bit to see how it fares against other HDR methods…

Why not set up backups for the Proxmox VM and be done with it?

Also makes it easy to add offsite backups via the Proxmox Backup Server in the future.

Cushy is an experimental Graphical User Interface (GUI) crate for the Rust programming language. It features a reactive data model and aims to enable easily creating responsive, efficient user interfaces. To enable easy cross-platform development, Cushy uses its own collection of consistently-styled Widgets.

Are there any implementations of this out there or is this purely theoretical (at this point in time)?

Adding a Turing award to your profile is certainly one way to flesh it out

Typst

You can use their online web-editor (similar to OverLeaf for LaTeX) or download the open-source engine and run it locally (there are extensions available for many text editors).

Compared to LaTeX I find it much more comfortable to work with. It comes with sane, modern defaults and doesn’t need any plugins just to generate a (localized) bibliography or include links.

Since Typst is very young compared to LaTeX I’m sure that there are numerous docs / workflows that can’t be reproduced at the moment but if you don’t need some special feature I’d recommend giving it a shot.

The uom crate implements this for Rust.

The core functionality is based on generics but there are some macros for defining custom measurement systems.

I can’t talk about the other libraries but the uom crate does the same thing.

The dimensions are encoded as a vector of generics, allowing you to get the correct unit even when dividing a distance by time for example.

It’s quite the clever use of Rusts type system.

I started out with WireGuard. As you said its a little finicky to get the config to work but after that it was great.

As long as it was just my devices this was fine and simple but as soon as you expand this service to family members or friends (including not-so-technical people) it gets too annoying to manually deal with the configs.

And that’s where Tailscale / Headscale comes in to save the day because now your workload as the admin is reduced to pointing their apps to the right server and having them enter their username and password.

Getting the configs to work with my personal devices was already a little finicky but doing that for not-so-technical family members was starting to be a bit too much work for me.

I’m hoping that Headscale will cut that down to pointing their app at the server and having them enter their username and password.

Was running Wireguard and am now in the process of changing over to Tailscale (Headscale).

It uses Wireguard for the actual connections but manages all the wireguard configs for you.

Nextcloud is just a web service. How he or anyone can access it is not determined by nextcloud but by the routers, firewalls, vpns and potentially reverse proxies that are routing the traffic to nextcloud.

With the proper configuration of all traffic handling services it will not be possible to access anything other than the intended endpoint i.e. nextcloud.

Within nextcloud any user can only access their own files plus anything that is explicitly shared to them.