

Maybe they just ignored the specs? I read that as it’s technically possible but you shouldn’t do it.


Maybe they just ignored the specs? I read that as it’s technically possible but you shouldn’t do it.


From the bug report in 2013:
It is not possible to implement this feature without violating the EWMH specification (it doesn’t consider that there are more than one active virtual desktops at the same time, it might cause windows to misbehave). Because of that there is no chance that this can be implemented on the base of X11


A missing feature that wasn’t possible under X and can be implemented now under Wayland. So it had nothing to do with KDE itself.


I don’t use Tailscale or Headscale as I’m the only user and happy with Wireguard.
But I had to add my Wireguard interface as default gateway for it’s IP range to my router. Maybe this was set on your old router but isn’t configured yet?


As others said it all depends on what you expect. I run stable diffusion on my gaming pc with 32GB RAM and a AMD 9070xt and it works fine. Did also on a 6800xt before that one died. A GPU with 16GB RAM helps a lot, would say that 12GB is the minimum. Lower will limit you in the models and speed.
For LLM just try it out, they work fine without special hardware for smaller models and as long as you are the only user. There are tools like Jan or lmstudio which make it easy to run.
Latency shouldn’t be a big problem if it doesn’t have massive spikes. Packet loss could be a problem, seems like Jellyfin doesn’t have an option zu increase the buffer size which may help. Or the problem is in combination with transcoding.
Maybe we don’t talk about the same. The uplink at OPs router isn’t the problem, there is enough upload speed so that others in Europe can stream. Users in Asia don’t have enough bandwidth, so there’s a bottleneck somewhere in between.
And yes, a VPN could help by routing the traffic through other hops, but chances are that it doesn’t help or even make it worse, but it’s worth trying.
The uplink isn’t the problem as it works for viewers in Europe.
Which test are you running exactly?
Two things I would check:
Resolvers configured in PiHole
Test using browser with DNS over HTTPS instead of the system configuration


I saw the thumbnail and thought those were cables in a cup of water. I was ready for a meme like “the opposite of a firewall”. I’m impressed and disappointed at the same time.


With integrated UPS! Just wonder if the performance is worth it.


That’s technically awesome, I just lack the imagination for a meaningful usecase.


It’s the public key so it’s not bad for security reasons. For me it just feels wrong to copy the content of a file to another using the clipboard. It can cause problems and one day you’ll do it out of habit with something you shouldn’t.


I’d be cautious following simple commands and configs without explanation or knowing what they do. And when someone copies public keys via clipboard I’m skeptic. Use ssh-copy-id or at least scp. And with Hetzner you can add your public key to their panel and it will be automatically added to every installation.
As it is stated, this is just a journal / checklist for someone and made publicly available. Don’t blindly follow such things without understanding what you are doing.
Damn you’re right, it doesn’t work out of the box like I expected. Have to admit that I never used it this way around. But it should work with --netns (network name spaces) which Wireguard uses: https://www.wireguard.com/netns/
Afaik it should work if you move Wireguard to it’s own namespace and than start qBittorrent with the new namespace (should even be doable without firejail).
@imetators @lemmy.dbzer0.com sorry for chasing you down that rabbit-hole, it sounded easier in my head


Sonarr is for series - that’s how I remember :-)
But I use Overseer anyway, so I don’t use them often directly.


Just host thelounge, its a web based irc client with integrated bouncer.
Wireguard