• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • I really like the way Ameliorated/AME Wizard handles the debloating. You take a Windows ISO and install like usual, then run AME with a playbook (like AtlasOS), which strips out the bloat through a collection of scripts . AME Wizard is open source, and you can directly inspect all the scripts within the playbook, whereas Tiny11 is a whole ISO that is hard to verify. Not saying that I can personally vouch that it is completely trustworthy, as I have only taken a brief look at the code and scripts, but I like to have the option. It also means that I could modify out any changes I don’t like.

    I found out about AME Wizard when I had to reformat a MiPad2 tablet with 2gb of RAM, and so far it has worked better than when the tablet was new. The only downside is that you go through the full Win 11 install, so you need enough available space and then reclaim the wasted space after, but it is at least mostly automated.








  • I’m no lawyer so I could be completely off-base, but I think the existence of homebrew can make all 3 points defensible, depending on what evidence exists about their primary intent being breaking the DRM. If they have posted publicly things like “this patch should bypass DRM for this particular game” then they would be screwed, but posts like “supports/extends this feature so we can better emulate the functionality in this particular game” should be fine? At least if I understand the precedent set by the Connectix ruling in addition to the wording of what you pasted?









  • What’s the biggest code base you have ever reviewed? What’s the most recent TLS vulnerability you have encountered, as opposed to the last vulnerability in other parts of your OS? Code being swapped by the server, maybe, but are you saying you do a code review every time you update a package or dependency of some other project? This is only less secure in some inconceivably convoluted chain of events that no practical person could enact. No sane person does what you’re saying. Everyone has to trust someone else with code blindly at some point.



  • It’s depressing that no other devices are getting SteamOS yet, either as out-of-the-box or at least supported fully day one. Here is why I suspect we are watching it die a second time.

    • Valve hasn’t released it standalone, which is probably making these manufacturers nervous
    • If Valve is even offering it to the manufacturers, money is probably flowing one way or another, as professional service fees to Valve, or ransom demands from manufacturers entrenched with Windows
    • Microsoft might still be doing their usual anticompetitive crap, offering incentives to keep SteamOS off of as many devices as possible

    We are going to be held hostage on Windows for years to come because this is delaying the critical mass for adoption. Even though there are all the other viable community distros, we need the brand to keep things moving.