

What will this new distro do that CachyOS doesn’t already (or can’t) do?


What will this new distro do that CachyOS doesn’t already (or can’t) do?
Kind of a small thing, but I use an Ultrawide monitor with Sway, so I wrote a oneliner to swap to a higher or lower display scale depending on the workspace I’m on. I like to game in full rez while I’d write code or read with a HiDPI resolution that’s easier to squint at. Also adding hotkeys to change scaling on demand is nice
but on desktop Linux you need to either create a new user (and remove world-readable permissions from your main account files), or create a custom Docker container, or create a chroot, or launch a VM
You don’t need to do any of that stuff to achieve application sandboxing. bubblewrap or firejail exist for exactly this purpose. Firejail in particular can integrate with AppArmor (which most mainstream distros that aren’t RHEL or Fedora ship with) so you get MAC on top of sandboxing.
it would have been nice if that was in the documentation
Its been in the docs for at least 7 years now (check the Last Modified date).


No free Apple TV app is kind of a deal-breaker. Even Emby has one. Also the Roku app still crashes fairly regularly for me just randomly either browsing or during playback.
I’d love to use it fulltime but I don’t want to have to buy new devices just to use it. Plex already works and I picked up a lifetime pass when it wasn’t insanely priced.
It’s just way easier to get helix to a usable state for the languages I write in than it is with vim. I don’t have to go plugin hunting or vetting random github repos; all the support mostly comes shipped with the editor. Throw some lines in TOML file and you’re good, vs downloading a plugin manager, downloading plugins, configuring those plugins and hoping you got everything right and the plugin repo’s README isn’t 10 years out of date.
vim feels like a downgrade.
100%
I use it where it’s available and helix isn’t
You register a new device on your tailnet and advertise it as an exit node. When other devices on your tailnet use the exit node all of their traffic goes through that device. If that exit node has a wireguard connection setup, all other devices using it will also use that same connection. The only tricky part was making sure wg-quick’s systemd service starts before tailscaled’s does (mentioned that in my op).
Tailscale offers this as a service but I dont use tailscale directly. I basically set this up manually and use headscale as my control server instead of using tailscale’s control servers.
I’m only using 1 vpn provider (mullvad) and using a wireguard config for 1 location. Headscale provides my mesh network controller, and pihole is a dns server. Not sure how you came to that conclusion
personally I just use headscale with tailscale clients and mullvad vpn via wireguard on the control server. there’s a bit of systemd magic required to make sure wg-quick starts before headscale does. dns is setup via a pihole device and I just point headscale’s config at that device for dns. it’s a pretty simple setup, but I have no issue doing everything via cli so this works well for me.


It’s K.Dotnet


Absolutely. I use navidrome daily but the only client I’m aware of on iOS is substreamer. I’d be happy to try your app once support lands!


This looks really nice! Glad to finally see a decent FOSS iOS music client; well done! Is there any chance that you have plans for navidrome support lined up for the future?
Edit: Didn’t see that you’ve already answered my question.


What it lacks is the math stuff from tables unfortunately.
It also lacks reminders, alerts, and notifications. I really wanted to like it when I tried it out, but this was a huge deal breaker for me.
That looks like the Platinum9 theme for XFCE. Setup for it are basically the normal steps to getting Window Decorations installed for XFCE (here), but in general it’s just:
$ git clone https://github.com/grassmunk/Platinum9 ~/.themes/Platinum9
Then set the Window Decoration theme using xfce4 settings
As someone with a burned out 9800x3D and an equally useless X870 motherboard, I would personally say to maybe wait for benchmarks, user reviews, and such for whatever CPU AMD puts out in 2027.


Sure. I wrote the docker-compose file in the repository. Unless something major has changed, it should be pretty straightforward to just clone the repo and then run
$ docker compose up
I see. When I wrote that out it was more of a “Why would some one pick this over CachyOS or plain Arch?” and I think you’ve adequately answered that.
I can say the same, except I’ve never had a real issue with Arch in the 15(+) years I’ve known of it and used it. Every issue I’ve had with it was my own fault and was just part of learning of how package managers work. Nothing unique to Arch is inherently confusing or prone to user error in my opinion. But that’s just my own bias.
Good luck with this distro. My only bit of feedback is that distros with a bus-factor of 1 usually die out quickly (burn out is real). I would say if you’re planning to have any support channels look into on-boarding some trustworthy comrades to assist you with this. Other than that wish you the best homie!