• 0 Posts
  • 121 Comments
Joined 2 years ago
cake
Cake day: February 14th, 2024

help-circle
  • At least one studio, Larian, has confirmed this is the case for them.

    When discussing the pressures the company faces when releasing a game in early access, such as audience expectations, Vincke told us, “Interestingly, another [issue Larian is facing] is really the price of RAM and the price of SSDs and f**k, man. It’s like, literally, we’ve never had it like this.”

    He continued, “It kind of ruins all of your projections that you had about it because normally, you know the curves, and you can protect the hardware. It’s gonna be an interesting one. It means that most likely, we already need to do a lot of optimization work in early access that we didn’t necessarily want to do at that point in time. So it’s challenging, but it’s video games.”





  • I’m throwing in my vote for CachyOS. Not because it’s the easiest to use (though it isnt difficult imo) but because it works out of the box, then they have nice wiki to guide you through simple things (like using Lutris and Proton). It’s also Arch based so there’s the arch wiki to fall back on. I ran Windows for 35 years and just switched to Linux in like October, fwiw.







  • I do, in fact. I get that they are typically open-source, and I also understand how ridiculously difficult it is to create one from scratch. If LibreWolf or whoever want to make privacy focused browsers based on mozilla foundation or google’s work then that’s fine and I support it, but I’m personally curious if there are any mainstream browsers that don’t have any (or minimal) reliance on google and mozilla foundation. Someone pointed me towards an engine in development Servo which looks quite interesting! Hopefully there will be a browser based on it soon.

    https://www.spacebar.news/servo-undercover-web-browser-engine/

    At the start of the millennium, Internet Explorer used its own Trident engine on Windows and Tasman on Mac, Opera used Presto, some embedded devices used NetFront, Netscape had Gecko, and KDE made KHTML for its Konqueror browser. Those browsers eventually faded away or adopted a competing engine to simplify development. KHTML was the basis for Safari’s WebKit, which in turn became Chromium’s Blink engine, and Netscape’s Gecko engine became the foundation for Firefox. Opera ditched its custom Presto engine in 2013 and switched to Chromium, and Microsoft Edge made the same move in 2020.

    This is a danger to the open web in more ways than one. If there is only one functioning implementation of a standard, the implementation becomes the standard. The web becomes to Google what Java is to Oracle. It also means the limitations and security flaws in Chromium affect most other browsers, which became a topic of conversation with Google’s recent Manifest V3 transition.










  • From their blog post about it:

    An unauthorized third party accessed a limited subset of customer data from one of our databases. While we quickly contained the incident, information that was accessed included emails, usernames, securely hashed passwords and authentication data. Any account passwords that may have been accessed were securely hashed, in accordance with best practices, meaning they cannot be read by a third party.

    The passwords were hashed and, I’m inferring from their language, salted per-user as well. Assuming a reasonable length password (complexity doesn’t matter much here, what we want is entropy) it would take a conventional (i.e. not quantum) computer tens to hundreds of millions of years to crack one user’s password.