Coki91

And the App still sucks balls because it only supports Vulkan-backed video decoding, which limits it's usage to fairly recent hardware instead of, you know the old underpowered devices which benefit the most and in which the Windows version does work

Which was brought up on day 1 of Beta release and nothing has been improved upon

It's the opposite actually, in terms of implementation Zram is a hack, but it does have it's use case when your system load doesn't far exceed your total RAM, on the other hand swap is tightly integrated into the system and it's on it's way to implement "Virtual Swap" which is effectively Zram but not a hack, making it like a hundred times better, see This blogpost for a detailed explanation

That would be "snap-pac" for anyone wondering, thanks for the tip but my system is not on btrfs yet, I did try all of it on a VM though so that's my next reinstallation for sure

I unironically pacman -Syu'd today and it broke 3 applications that depended on ffmpeg (yes it did update ffmpeg correctly) all from official repos

Tried to build them all from source for like an hour but the compilation also fails, ended up symlinking the libavcodec.so into it's previous' version name and everything works again with zero issues (who designed this shit?)

sudo sed -i

How bad cou...

HOLY SHIT

The site loads for me and after a few seconds I get a blank page... how do I deal with it?

Right, I didn't pick up on that m/multicast DNS difference, I thought I was talking about the same thing, thanks for clarification

Sounds like I do have options here, so while I wait for my ISP to comply, I'll also try out Avahi then

I think I understand why Avahi wouldn't work with that explanation, I keep digging and now my router is not exactly inaccessible, it's managed by my ISP instead which is annoying but I supposedly can still ask them to tweak things for me so I may have a chance

Tailscale already has DNS servers working on Tailnets (they call it mDNS, or magicDNS) which is I believe 100.100.100.100... actually, the documentation states that every tailscale-running device is a DNS server on itself too but either way that IP is private on every tailnet, remains accessible and host names are configurable on the Tailnet too

If I'm not mistaken on the functioning of DNS, I should be able to do it with that primary-router secondary-tailscale DNS setup I hypothesized and on LAN that will yield perfect connectivity, while out from home there would be no such records and it'll fall back to Tailscale's DNS which is already private (worst concern is just sending a request for a hostname on public network but that shouldn't be that big of a deal)

At this point I might have this solved, but of course, more input is nice too, It'll take some time for my ISP to work for me on this

I'm a bit conflicted with your answer, I suppose for a DNS server my best go-to should be my router, but I don't have access to it, next option would be DNS servers on each device and make localhost the primary server, then my router the secondary? Assuming that's the case I think that would break when I take a device off the local network as outside it would still assume things work like in the LAN. I could see it working if I had access to my router and primary server was DHCP provided (in LAN that would be my router with it's DNS configured to point to my devices with hostnames, outside it wouldn't have any and use the secondary) and secondary Tailscale's (which supports mDNS so with the same names it would hit my device's IPs from the tailnet) but I don't think I can get that router access...

Unless I misunderstood something of the solution, if so can I ask for clarification?