Starfighter @ Starfighter @discuss.tchncs.de

Posts

0

Comments

53

Joined

2 yr. ago

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.

I suspect that if you were to cut the screen at the rounded edges, the sensor island and the onscreen nav buttons you'll be left with a 16:9 screen.

In other words its a 16:9 screen with some margin for curves and controls.

One sensor should be enough. I believe they usually mount onto the inside of the window facing outwards so that lights and movement in the room don't influence it.

The simplest way of solving this would be with technically four separate automations. However you can place them all in the same HA Automation using multiple triggers and trigger IDs. (Or have one for the blinds and one for the lights with two triggers each)

I'm going to assume the blinds are somewhat light translucent.

For the blinds use a numeric trigger that fires if the lux value is over some threshold for let's say 10 minutes. That way it won't trigger for every tiny cloud. When triggered lower the blinds.

Add another numeric trigger for moving back up when the lux value is under some threshold for 10 mins. Test to make sure that lowering or raising the blinds doesn't darken or lighten the room enough to immediately have it trigger the other trigger. If it does then increase the difference between the two thresholds.

Copy the same procedure for the lights. The timer can be shorter here, maybe try 1 minute. Make sure that the thresholds are low enough as otherwise lowering the blinds would immediately turn the lights on. I would suggest first tuning the blind triggers and then tuning the light thresholds to your liking.

If you can't set the light thresholds low enough so that the blinds don't interfere with them you'll need a somewhat smarter automation but I'd try the easy way first.

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?

Infinity for Lemmy has a data saving mode that allows you to disable previews of images and videos selectively.

You asked for a way to block communities from other instances.

Now you can go through all communities on all federated instances and block them one by one. I'll surely be impressed by your endurance if you manage to do that.

Open the large drop down menu at the top of the screen and select "Local". Then only communities from your instance will show up.

You can also set that view to be the default in your account settings.

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.

HAOS does the same thing where it runs HA Core (the actual server software) in docker.

There are two possibly major drawbacks to managing docker yourself:

1. You'll have to manage updates, backups, etc.
2. You won't have access to the add-on store. You can still install add-ons by running their docker images but you'll have to configure their communication channels in addition to everything in point 1.

Proxmox on the other hand manages full virtual machines for you. There is an official HAOS virtual machine image which gives you the benefit of doing everything for you while still allowing you to run other virtual machines alongside it. Proxmox can manage full VM backups for you and collects performance statistics for each VM. Main drawback would be the added complexity and increased resource usage.

Cool to see support for the QOI format in a popular software package.

The "add to home screen" button turns into an "install" button when Firefox detects that the website is a progressive web app (PWA). Other browsers do the same.

The difference is that a PWA can define a custom icon and name for the "app" button on your home screen and that it can use some clever caching making many PWAs offline capable (meaning you don't need an internet connection to open the web page).

I understand the reluctance to press "install" but in the case of PWAs the install size is tiny and fully contained in Firefox and you get the added benefit of faster startup / loading times due to caching.