Comments by "Gilad Barlev" (@GSBarlev) on "KDE Global Themes Are Inherently Unsafe" video.

  1. The second I saw "$configPath" I facepalmed. I also immediately thought of the Steam issue and thought, "At least this poor dev is in good company."
    4
  2. Flatpaks?
    2
  3.  @RadikaRules  The latter.
    2
  4. This seems like a good use-case for automated UAT. Set out a few rules of expected behavior: (1. After installing a theme, I should be able to access my home directory) Then create macros for installing the theme and checking each UAT condition. Now create a VM snapshot from a working base KDE installation, run your macros, and summarize the results in a dashboard. Will you catch every issue? No. But you won't ever get burned by the same issue if each problem is captured as a new test case as it's discovered.
    2
  5. Big difference between a warning that "this theme might not work" and "this theme has the ability to run arbitrary code," which I am terrified to learn is apparently... standard practice.
    2
  6. Agreed. I'm a Stan of famously duck-typed Python, but I use type hints and mypy for everything I write (including notebooks). It's notable that one of the most well known developers of mypy is Guido himself.
    1
  7. ​ @Redmage913 I'm trying to remember the permissions set by Timeshift—I hope it's not u+w but I'm not positive.
    1
  8. I mean, I never browse the AUR. I only packages from it that are: 1. Recommended by the Arch wiki, 2. Recommended by a credible (and recent) blog, or, 3. Linked to from the official documentation of a project I would otherwise be building from source I also always check the AUR page for: A. date of last version B. comments along the lines of "this broke my system and hard-bricked by pet badger."
    1