Just your normal everyday casual software dev. Nothing to see here.

People can share differing opinions without immediately being on the reverse side. Avoid looking at things as black and white. You can like both waffles and pancakes, just like you can hate both waffles and pancakes.

  • 0 Posts
  • 274 Comments
Joined 2 years ago
cake
Cake day: August 15th, 2023

help-circle

  • I’ll be interested as well, but I don’t think that it is a bad thing so to speak. Both CD PROJEKT and Michal have high values when it comes to DRM-Free and open gaming. Gog is mostly supported by it’s backers and game revenue, I don’t think that will change. I don’t see the co-founder who created both the studio and the storefront performing a pump and dump on GoG. If anything we may end up seeing a more heavy push into DRM free areas now that it’s detached from the game studio. Additionally CD Projekt’s reason seems fully valid. It makes sense they would rather focus more on making games than distributing. Distributing games is no easy task, let alone maintaining an entire storefront that most of the corporate world dislikes due to the core principles of the storefront (I.E the push towards support and DRM-Free).

    It could be bad but, I’m not going to be super concerned until actual evidence ends up on the ground for it.


  • do you preorder games?

    Nowadays? Not a chance. Preorders nowadays seem to be more of a incentive to allow a studio to just not have a decent final product because people have already bought in.

    What about Early Access Games?

    If I really like the concept, yes.

    Do you feel differently about Early Access vs traditional preordering?

    Early access is not pre-ordering, and as such is treated extremely differently. Preordering tells me that the product will be finished on release, EA means that it’s going to need a lot of work for a finished product.

    If you are open to the idea in specific circumstances, what are those?

    I am extremly open to EA as it helps studios develop a product that otherwise may not be able to be created. Actual preordering is a strict closed door, there is very little reason in the digital world we live in to preorder a game.

    How do you decide if a game qualifies?

    I more likely will buy an early access game if I can open the page and not see:

    • Major blockers:
      • Lack of Linux support or compatibility
      • Reviews talking about the game being dead
      • Reviews talking about how the developer ignores the community
      • Update history either showing no changes or minor changes stretching back for a few months(the longer the gap the less likely I am to support the studio)
      • Opening the developer page and seeing they are actively working on a different game. (this is an instant deal breaker)
    • Minor Blockers
      • Developer responses in community pages saying “for support go to external site” usually discord. If you don’t want to support your game on the storefront, don’t use the storefront.
      • Update logs saying that they are actively working on DLC for their early access game. (free DLC gets a partial pass… but paid DLC for an Early Access game is a huge red flag for me)
      • No developer interactions in the community forums or an un-moderated community forum.
      • Toxic community in discussion forums or support channels (I understand this is out of the devs control at times but it still dissuades me from wanting to spend money on the games)



  • I’ve never rebuilt a container, but I also don’t have any containers that are deprecated status either. I swap off to alternatives when a project hits deprecation or abandonware status.

    My only deprecated container I currently have is filebrowser, I’m still seeking alternatives and have been for awhile now but strangely enough it doesn’t seem there are many web UI file management containers.

    As such though ever since I learned that the project was abandoned on life support(the maintainer has said they are doing security patches only, and that while they are doing more on the project currently, that could change), the container remains off, only activating it when i need to use it.









  • while docker does have a non-root installer, the default installer for docker is docker as root, containers as non-root, but since in order to manage docker as a whole it would need access to the socket, if docker has root the container by extension has root.

    Even so, if docker was installed in a root-less environment then a compromised manager container would still compromise everything on that docker system, as a core requirement for these types of containers are access to the docker socket which still isn’t great but is still better than full root access.

    To answer the question: No it doesn’t require it to function, but the default configuration is root, and even in rootless environment a compromise of the management container that is meant to control other containers will result in full compromise of the docker environment.


  • man, arcane looks amazing, I ended up deciding off it though as their pull requests look like they use copilot for a lot of code for new features. Not that I personally have an issue with this but, I’ve seen enough issues where copilot or various AI agents add security vulnerabilities by mistake and they aren’t caught, so I would rather stray away from those types of projects at least until that issue becomes less common/frequent.

    For something as detrimental as a management console to a program that runs as root on most systems, and would provide access to potentially high secure locations, I would not want such a program having security vulnerabilities.


  • as an ammendum to this comment edit, catfriend edited the post linked and added this to the end

    Edit: Regarding @nel0x , they did not have any history with the Syncthing (Android) project nor an expressive public profile when they applied to take over the Google Play Store entry in Feb 2025. I accepted this and transferred - believing in good will and we agreed on their task to be publishing what was on my repository to Google Play after their review. If they now desire to make their own app, there is, unfortunately no way to clean up the confusion caused if it is called the same other than kindly asking them to rename it.