• 0 Posts
  • 37 Comments
Joined 4 months ago
cake
Cake day: June 8th, 2025

help-circle


  • Oh my bad, I misread the first line. In that case, I would guess that Proton on Steam might be using a different version of the DirectX translation layer. I’m not sure which that is, since im not sure which directx version the game uses.

    Very interesting that at least one person reported the same error happening on Windows.

    Edit: My guess is that wine is using WINED3D, the directx 9 to opengl translation layer, while proton is using DXVK. Since the game reportedly has this error on windows, the issue might actually be that DXVK is doing the “correct” thing and crashing the same way it would on windows.

    Did you verify that PROTON_USE_WINED3D=1 crashes with the exact same error and not a new one? Since you said the game works with vanilla wine, which defaults to wined3d, I would expect this to fix it.


  • Steam uses the Steam runtime and can automatically apply specific settings and configurations known as Protonfixes.

    Try using Proton in Lutris and enabling the Steam runtime. Lutris has support for a tool called Umu Launcher which essentially replicates Steams method of launching games and applies Protonfixes for you. I don’t know the exact requirements to use it, but looking around in the discord (unfortunately) might get you some info.







  • I love Nushell, it’s so much more pleasant for writing scripts IMO. I know some people say they’d just use Python if they need more than what a POSIX shell offers, but I think Nushell is a perfect option in between.

    With a Nushell scripts you get types, structured data, and useful commands for working with them, while still being able to easily execute and pipe external commands. I’ve only ever had two very minor gripes with Nushell, the inability to detach a process, and the lack of a -l flag for cp. Now that uutils supports the -l flag, Nushell support is a WIP, and I realized systemd-run is a better option than just detaching processes when SSHd into a server.

    I know another criticism is that it doesn’t work well with external cli tools, but I’ve honestly never had an issue with any. A ton of CLI tools support JSON output, which can be piped into from json to make working with it in Nushell very easy. Simpler tools often just output a basic table, which can be piped into detect columns to automatically turn it into a Nushell table. Sometimes strange formatting will make this a little weird, but fixing that formatting with some string manipulation (which Nushell also makes very easy) is usually still easier than trying to parse it in Bash.




  • The browser isnt paid though. https://help.kagi.com/orion/faq/faq.html#business

    I agree the $5 a month option is pretty useless, but I also think $10 is completely reasonable for everything you get.

    Also even if it was paid why would it have issues with a package manager? Paid software generally just uses an account or license key to verify payment, with the executable being frwely available. JetBrains and Burp Suite are two software that come to mind and both are in many repositories.

    Edit: To be clear, the browser will only be for Kagi and Orion+ members during the testing phase, likely just to control the size of the testing group. After that it will be free.


  • They’ve been open sourcing parts of it the entire time. Looks to me like they’re doing what they said.

    You can easily monitor network connections to see what addresses its sending packets to. You can’t collect information without sending it somewhere. Run Firefox through a proxy, and you’ll see it is far from private. The source code will show you what they’re sending, but nothing about what they’re doing with it after it’s received.


  • Open source =/= private. Chromium and Firefox are open source, and both have horrible privacy defaults. I have far more trust in Kagi than Mozilla or Google. There are many ways to verify privacy than other than reading the source code.

    Besides, they have shared that they plan to open source the browser once the project is ready, and some components are already open source. Making a project open-source is a much bigger task than people realize. While community contributions may take some maintenance load off of your staff, they now become responsible for much more external code review, which requires more scrutiny due to coming from outside sources.

    https://help.kagi.com/orion/faq/faq.html#oss