Barrier is only for inputs IIRC. To get Keyboard Mouse and Video (more usually KVM) you need some kind of remote desktop software. Rustdesk is pretty straightforward. I think Gnome handles RDP access natively now if you're running a Gnome based Linux distro. Otherwise XRDP is a bit of a faff, but solid once it's working.
Morphit
joined 2 years ago
That's a biblically accurate implementation if ever I've seen one.
If you have the docker-compose.yml locally, you can nix run github:aksiksi/compose2nix to translate it into a nix file for inclusion in your nixos system config. I think that could be done in the config itself with a git url but I'm not that great at nix. You will surely still need some manual config to e.g. set environment variables for paths and secrets.
How do the DNS servers resolve local hostnames then? The pihole DHCP integration adds local hostnames to DNS when they are assigned an address. If there's two DHCP servers handing out leases, presumable only one would be accepted, how then would the DNS servers sync those names?
I think I had my secondary pihole resolve local names from the primary, and leases were copied over on a cronjob in case the secondary DHCP server had to be enabled.
Not that it particularly matters for just queries. The problem is that DHCP can only be enabled on one host. If that one fails then devices can't get on to the network themselves. I'd like to know a good way to have a failover DHCP server - my janky cronjob isn't great.
Where do you do DHCP? I had a primary pihole with DHCP enabled and a secondary with a cron job that enabled DHCP if the primary was down or disabled it if the primary was working. The cron job did sync DHCP leases from one to the other but it was a bit janky. I tried to update the secondary to pihole v6 and hosed it so I have no backup for now. I'd like to re-image the secondary and get a better setup - when I have time.
Edit to say I really wanted to try keepalived - that's really cool to fail over without clients noticing.
How are you setting font size? I'm running Plasma 6.3.5 and 150% desktop scale looks identical to 100% with a 150% page zoom in Firefox. Just scaling fonts sounds like it would make everything non-text appear the wrong size.
I do notice a weird behaviour where Firefox renders at 200% scale when it's entirely within a display at 100% scale. If it overlaps another display at all then it uses the appropriate scale for each monitor. Maybe that's a setting somewhere.
This is the default in NixOS when plasma6 is enabled. I went down the rabbit hole checking, it's set here.
What's wrong with fractional scaling in Firefox? It seems to work fine for me with kwin_wayland. Even if I have different scaling on each monitor, Firefox seems to respect it fine. Some really old software is a bit funky running through xwayland but nothing showstopping.
Think of the speeds you could fly at with no drag! I'm so bummed that the Grace Hopper drone didn't get to fly after Intuitive Machines fluffed their second landing. That would have been awesome outreach from NASA.
We want drones on the moon!
Yeah. Given that they kept the engine running at idle for a while, I was half expecting to see a trail. I'd like to know the dynamics of the touchdown. I'm sure they'll figure out most of it but they probably prioritised payload data over images of the touchdown.
Commiserations to IM. Really unlucky to fix issues from their first mission then end up with the same, if not a worse, result.
This video appeared on my home page and I had to look twice at the thumbnail: The Tomb of Saint Peter Explained
I'm upset that a meme I tried to remake with Unicode box drawing characters lines up terribly in apps: https://lemmy.ca/post/28490027 Shouldn't code blocks render in monospace?
On Lemmy's web frontend it's perfect:
On Connect it looks like this:
On Jerboa it's basically the same:
Eternity does use monospace but the box drawing characters seem to be too wide.
All I can find about it here is one post from a year ago: https://lemmy.ca/post/1492857
1
cross-posted from: https://feddit.uk/post/12276336
Sorry for the crap photos - I just wanted to share these extra keys I added to my Lily58.
I noticed there was a gap in the matrix so I tacked a spare hot-swap socket to the pads on the back of the PCB. That worked with minimal modification to my QMK set-up. I couldn't really use it dangling off some wires so I set out to make an extension that would slot in and be retained by one of the standoffs. I don't have a laser cutter or 3D printer so I just hacked these out of a sheet of ABS plastic following a printed template and glued them up. They're nice and solid and line up really well, despite being rather rough around some of the edges.
I'm finding the 1.5U keys a bit confusing at the moment, swapping them out for 1U keys makes it a bit easier to home my thumbs. These are certainly much easier to access than the outermost keys on the lower row or the keys below the display. I'm thinking they need to be called Lily Pads.
5
cross-posted from: https://feddit.uk/post/12276336
Sorry for the crap photos - I just wanted to share these extra keys I added to my Lily58.
I noticed there was a gap in the matrix so I tacked a spare hot-swap socket to the pads on the back of the PCB. That worked with minimal modification to my QMK set-up. I couldn't really use it dangling off some wires so I set out to make an extension that would slot in and be retained by one of the standoffs. I don't have a laser cutter or 3D printer so I just hacked these out of a sheet of ABS plastic following a printed template and glued them up. They're nice and solid and line up really well, despite being rather rough around some of the edges.
I'm finding the 1.5U keys a bit confusing at the moment, swapping them out for 1U keys makes it a bit easier to home my thumbs. These are certainly much easier to access than the outermost keys on the lower row or the keys below the display. I'm thinking they need to be called Lily Pads.
3
Sorry for the crap photos - I just wanted to share these extra keys I added to my Lily58.
I noticed there was a gap in the matrix so I tacked a spare hot-swap socket to the pads on the back of the PCB. That worked with minimal modification to my QMK set-up. I couldn't really use it dangling off some wires so I set out to make an extension that would slot in and be retained by one of the standoffs. I don't have a laser cutter or 3D printer so I just hacked these out of a sheet of ABS plastic following a printed template and glued them up. They're nice and solid and line up really well, despite being rather rough around some of the edges.
I'm finding the 1.5U keys a bit confusing at the moment, swapping them out for 1U keys makes it a bit easier to home my thumbs. These are certainly much easier to access than the outermost keys on the lower row or the keys below the display. I'm thinking they need to be called Lily Pads.
view more: next ›
In the System settings, under Window Management > Window Behaviour, in the Focus tab, there is a Focus stealing prevention selector. If it's set to extreme, then it does prevent switching to another desktop when I open a window that gets sent there.
I think that's what you want but I guess it would mess with all applications, not just Steam. I don't think you can do it per application.
I remember there being a window management protocol that would allow more control but I don't think Kwin implements it yet.