• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2025

help-circle








  • I had the same experience with cosmic. It was prone to crashes. I really like the idea of combining gnome with i3wm/hyprland though. I currently have one box using gnome with a tiling shell extension, but the issue there is extensions not being well supported between gnome versions.

    I wouldn’t be opposed to retrying cosmic now. It’s been a few years.




  • One thing to remember with VirusTotal is that it should only be used as a “tool of consensus”. A lot of AV solutions on their list will false flag binaries presumably to instill fear and get people to buy their solutions over more reputable AV providers. You want the AV that works the best which many people would equate to the most flagging (as logically incomplete as that may be).

    If you are seeing 66 flags and many of those being from reputable vendors, then I would say that what they show is likely accurate. Accuracy and relevance being two different things. 100% accuracy on keygen tools doesn’t mean that it is a relevant flag to what you’re trying to do.

    You could try software solutions like LOKI (the IoC scanner) or Azul to test specific binaries, though. I believe LOKI is just doing static analysis, but Azul I know automates the sandboxing.





  • I run NixOS as a daily driver and on a box for docker containers. I will say that it is stable to point that since nothing seems to ever really break, I don’t feel I really understand the configuration as well as I could (since I’m not having to fix things and learn).

    I started with just traditional NixOS but later moved to using flakes. Because of flakes input pinning, it’s much more reproducible but also even more stable. The biggest benefit I see to flakes is the use of local git for updating. Since I have git logs for auditing, if something were to go wrong, I’d just find that change in log and revert to before that commit hash (or just revert to different generation).

    The biggest problem I’ve had is how procedurally some tasks change and sometimes are made more difficult. Symlinks is a good example of that. In Arch, symlinking is just a basic one-liner. In NixOS, it’s a matter of writing config more verbosely to the configuration.nix file :

    (pkgs.writeTextFile {
      	name = "tst";
      	destination = "/bin/tst";
      	executable = true;
      	text = builtins.readFile ./scripts/tst;
    }) 
    

    That’s a good takeaway from NixOS: things are more verbose in setup, but tend to get set once and never again.