• 10 Posts
  • 1.43K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle






  • Well you’ve definitely overcomplicated things by introducing a lot of different variables into the mix. What you’ve set up is a hat on a hat. An abstraction on top of another abstraction.

    Let me break it down and just ask: are you just trying to ensure your friends can only access certain addresses on your network, and you’re using Tailscale ACLs for that purpose? It sounds like you just want proper routing security at the edge of your network and are going this route to avoid having to do that maybe?

    Tailscale has a place and works great for lots of things, but using it like this is going to cause all kinds of problems eventually. You’re basically just advertising a bunch of confused routes to the coordinator like this, and DERP connections will eventually fail or freak out because you’re providing multiple paths to different things if I’m reading this right. You’re also introducing A LOT of network overhead because of this, and I can forsee a lot of connectivity issues in gaming throughput if that’s the main purpose.




  • It really depends on what you intend to develop in, but I can say containers aren’t the way to go whatsoever.

    Every gaming SDK or IDE I’m aware of has their own version of sandboxed environments. You just start a project, clone it, then let their package management tooling do the rest.

    Maybe if you explain a bit more about your approach you could get more constructive answers.


  • As someone who works with multiple projects who have had to beg and plead to get broken packages taken down, I can confidently assert that it is.

    They’ve gotten too popular too fast, and dozens of projects have had similar experiences to OBS.

    Some issues we’ve dealth with in the past year:

    • unmaintained community package which included libraries that made our package vulnerable and was tripping up static scanners
    • one package unpublished due to a complaint from a completely unrelated person
    • spammed and suspect versions of our packages being published with shady blobs that aren’t part of our project

    There’s plenty more. There just isn’t any kind of moderation, and there needs to be. Regardless of their original intent, it’s now become too big to just let go. Similar things have happened over the years with almost every maintained public package repository: gems, npm, pypi…etc.

    Now it’s time for the Flathub folks to step up and do some moderation to prevent worse things from happening. The minimum they could do is add a flag for official packages that are confirmed to be from the proper sources, but that requires a bit of effort on their part.


  • There’s a ton, but I still don’t find them very useful. The real thing I find dumb is the hardware acceleration for 95% of use-cases. Unless you’re just sitting and watching scrolling output, I don’t see the need to sacrifice efficiency for faster rendering, and even then, I can’t say I’ve had many issues with standard terms either.

    Ghostty is the one getting the most hype recently, and it’s alright. It feels more put together than Kitty or Alacritty. Rio is mostly a toy with a bunch of goofy visual effects. Honestly can’t say any of them have features that improve my workflow over just having a bunch of named windows all over the place though.








  • Cachy - you might have some extra hoops to jump through. The performance difference is negligible for just desktop usage.

    PopOS - no real benefit unless you’re running Nvidia, and then it’s only for the moderately useful graphics switching stuff.

    You sound like you want Fedora for simplicity’s sake, honestly. There’s really no other major performance differences between desktop distros. Any tunings that one has you can just apply to another if you know their benefits.