The development of Piper is being driven by the Home Assistant Project. That probably makes it one of the larger OSS TTS projects. Hope may not be lost yet ;)
The development of Piper is being driven by the Home Assistant Project. That probably makes it one of the larger OSS TTS projects. Hope may not be lost yet ;)
Seeing these little IT gems all over Lemmy always makes me smirk :)
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.
Sorry I don’t have a recommendation for you but this question often comes up in the Home-Assistant (local-first home automation software) community. So maybe have a look around those channels as well.
Apart from the visibility argument. With this kind of parking spot you have to leave the spot in the other direction than you came in. So you’ll only get the enhanced agility for one of the moves.
Would you rather have more agility when getting into the tight parking spot or when leaving onto a larger street?
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.
As in video wallpapers? Sure. KDE Plasma for one lets you install a bunch of wallpaper plugins ranging from video playback to live computed shaders and everything in between.
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.
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.