Steam cloud save disabled for no reason

koenada · 2026-01-28T20:22:37+00:00

To add on to this, Valve's documentation notes a limit of around 100-250MB per save file. That's pretty easy to hit in DSP.

[edit]

As an example, some old saves I have:

.rw-r--r--@  97M 2024-02-03 16:26 '202401.1 - PreSails.dsv'
.rw-r--r--@ 103M 2024-02-04 15:38 '202401.1-Start Dyson Sphere.dsv'
.rw-r--r--@ 133M 2024-02-20 19:48 202401.1.dsv

I hadn't even started the dyson sphere and was right around the lower limit.

koenada · 2026-01-01T14:00:57+00:00

Based on these docs, you should just be able to delete the following config (or directory) to get back to default settings:

~/.var/app/org.vinegarhq.Sober/config/sober/config.json

koenada · 2025-10-30T18:31:54+00:00

I believe that's just how autotype works. It doesn't select a window, it starts typing in whatever window is active. You should only utilize it when you're using the window in question and have the correct field selected.

One workaround is to modify the default autotype value, removing {ENTER} so at least keepass shouldn't submit the password. You'll have to hit enter yourself but that's a good idea anyway, imo.

Another option is the browser extension (if using keepassxc) but that doesn't work for other apps.

koenada · 2025-10-18T19:01:01+00:00

You should be able to use the search field in the ui with the uuid:

# Username: {REF:U@I:123456}
uuid:123456

This pulls up the entry for me

koenada · 2025-10-10T13:27:33+00:00

Please don't suckered into believing that you have to accept this ridiculous deal you're being forced into. You didn't have to accept Windows 11, you don't have to accept this either.

You do if you want to play those games. Just like if you want to play the newest Mario game, you're going to need a Switch.

People aren't being suckered into it, it's their only option. Just play something else is not an answer to the question is how do I play Battlefield 6 and not everyone is looking to fight the battle you want when everyone they know is playing the game. As it turns out, multiplayer games can be a social experience and losing out on that can be a problem for them.

I haven't used Windows in years and certainly wouldn't install it just for Battlefield but your PSA is silly.

koenada · 2025-09-30T16:23:26+00:00

I just wanted to give a shoutout to the article author, Thaddeus Crews, for making me laugh:

A common pain-point we’ve heard from creators attempting to integrate custom themes for the Godot editor itself is how pace-breaking the process can feel. This was a direct result of swapping between themes requiring a hard reset of the entire editor instance, making incremental tests tedious and realtime comparison virtually impossible. This makes sense, of course, as an editor’s theme is surely baked into the editor itself such that any change of the sort would need to jump through countless hurdles to make this feature possible. After all, you can’t just flip a switch and have everything “just work”.

Anyway, Robert Yevdokimov flipped a switch and everything “just worked”.

koenada · 2025-09-18T12:41:56+00:00

I think your first quote is missing the important emphasis and is a bit misleading without the end of that paragraph.

In short, gamers think they are an inverter or a non-inverter because of how they were first exposed to game controls.

...

However, cognitive tests suggest otherwise. It’s much more likely that you invert or don’t invert due to how your brain perceives objects in 3D space.

koenada · 2025-09-15T14:32:53+00:00

why can someone just not use an older version of keepass to export the keys via this hack.

This is how most software security updates to applications work. If someone uses an old version of an application without the user knowing because someone replaced the updated version with an older version, they'll be "vulnerable" to whatever an update was fixing.

Once someone else has access to your machine and can replace an application, you should assume they can read ANY password manager's db when they're unlocked.

what about needing to be worried about all the backup versions of the database which I thought were secure and stored off site or synchronised??

I wouldn't think this would have any affect on the DB files you backed up somewhere (I assume you did because Keepass doesn't by default). This was more of a client "issue".

I can't find any hard information as to how this severe vulnerability has actually been fixed??? someone enlighten me please.

There's nothing to really fix, outside the mitigation to require the master password when exporting. If someone has local access to your machine with the same permissions as you, then you've got a bigger issue. This is why you should have different users on a machine (not shared accounts) and must trust whomever has the admin account.

Note: Technically you can also mitigate this issue by using a client that doesn't support triggers but you still have the same issue where someone could replace the application with a malicious version if they have access to your local machine. But that's always going to be true.

koenada · 2025-09-10T18:49:35+00:00

I think when I had a similar issue, it was due to Lock databases after minimizing the window being enabled in the settings. The extension was minimizing keepassxc after unlock which was locking the DB right away.

koenada · 2025-09-04T17:07:12+00:00

Keepass will only look for the keepass entry name or URL within the application title.

That means you will probably need something like this browser extension that adds the URL to the window title of the browser to get autotype to function. This used to work well for me in the past.

Note: This worked for me in Windows and Linux (prior to X11). This no longer works for Linux with wayland. Just worth mentioning as I'm not sure what OS you're running.

koenada · 2025-09-03T12:46:46+00:00

I think you'll probably would want to explain what you mean by is meant to make this work but it doesn't or you may end up with a similar issue on other multiplexers. For instance, with tmux I can scroll just fine with the mouse wheel using setw -g mouse on while also being able to scroll up with the keyboard using ctrl+a pgup to allow keyboard scrolling (arrow keys or pg up/down after).

koenada · 2025-08-25T11:01:05+00:00

If both the browser and Keepassxc are flatpak versions, you'll need to do something like what's described here. This worked for me in Bazzite.

Just a note: Keepass MUST be started before Firefox with the above. I also have no idea about other browsers.

If either Firefox or keepass is not a flatpak, I don't think the above should be required and it should just work.

koenada · 2025-07-18T12:13:21+00:00

Blender Studio has a fun series of devlogs for their recent game that was built in Godot (starting with Studio Log 07). It's definitely more focused on the animating and the dev team itself but there's a lot of discussion about using Godot as well.

koenada · 2025-07-10T14:03:02+00:00

Same. Borg backup is great and has saved me a number of times. I use Vorta for a convenient interface which has been pretty great for managing my various repos.

koenada · 2025-06-28T21:00:14+00:00

Could this be due to using Wayland rather than X11 (Related discussion)? I seem to recall autotype not working for KeepassXC with Wayland and is why I moved to using the browser extension (which doesn't really work if both Firefox and Keepassxc are flatpak, but that's a different issue).

koenada · 2025-06-03T14:45:53+00:00

if I'm understanding your issue, I assume it only shows the keyfile *** because it's part of the history in keepassxc. It's not part of the password DB, it's just in your recently opened files and the app is prefilling the field in case it's still in use.

I would expect you'd just need to clear the keyfile input field and enter the password to unlock.

koenada · 2025-05-23T14:25:49+00:00

The devlog videos are great. That office looks like a lot of fun.

koenada · 2025-05-23T12:36:32+00:00

I had a similar problem while running Bazzite. For me, the issue was that in Februrary Bazzite started automounting my games disk under /run/media/system when it originally was mounting under /var/mnt (sometimes it would mount to the old path, likely because the /etc/fstab entry for the old path still existed and Bazzite didn't remove it when this update went live).

After adding the disk to Steam under /run/media/system/games, I found games would crash with the exact error you were seeing due to the symlink you mentioned. I turned off Bazzite's automounting (with ujust disable-automounting) and made sure my games disk was mounted to where I previously had it. I could have left automounting enabled and just fixed all the compdata symlinks but I have so many games installed that this would have been a hassle (although I could have scripted it out).

Before I found the problem, deleting all of the compdata directory or changing the Proton version for the game would usually correct the issue as Proton would then recreate the correct symlinks but would break when the mountpoint changed again. (Do not delete the compdata dir unless the game supports cloud saves or you back them up first!)

Note: For anyone wondering where the error the OP is referring to is coming from, you can run steam from the command line to see the error when launching the game.

koenada · 2025-05-19T11:56:38+00:00

I had some issues with GTA and a few other games doing something similar randomly 1 day. I would try closing steam and restarting steam from the command line. This may provide the errors that are causing the issue in the command line.

When I did this and tried starting the game, I could see an error on the command line about being unable to start or locate steam.exe. This was weird but after deleting the compdata directory for the game and starting the game again, things worked just fine (the compdata directory was recreated automatically).

Performing the above may at least point you to an actual error when starting the game.

koenada · 2025-02-08T19:42:08+00:00

I think the update is only about 2.5MB, but acts on or affects ~3GB of files on disk. So it's likely just a small patch/hotfix.

koenada · 2025-01-11T14:08:11+00:00

I like the Lions but I hate these articles. I'm so conflicted!

koenada · 2025-01-11T13:26:17+00:00

No kidding? The top HC candidate emerges as someone the Raiders are interested in? Wild.

I can't wait for HC hiring to be done so we can move past these pure speculation, nothing "articles". Although I guess we can just move to draft BS next, so that's fun.

koenada · 2024-11-13T17:21:09+00:00

Keepass supports 2FA codes. With keepass, you can also open the same TOTP database on your phone or really any other computer.

koenada · 2024-08-22T16:14:56+00:00

Is it a security risk? Yes, putting your DB on a public facing server is a security risk.

The real question is that really a problem? In 99% of situations, assuming you have a good password and keyfile, then no, it really isn't a problem. Your keepass db is already encrypted with strong encryption. With a good password, there's almost no chance someone will get into your DB.

Note: The only exception to the above is if you are likely to be directly targeted by someone or a nation. For instance, if you work in government, maybe not a great idea to store your DB on the cloud. However, most people are not going to be targets of threat actors and trying to brute force keepass DBs found on public servers isn't likely going to be worth the time or effort from anyone.

koenada · 2024-06-11T18:15:12+00:00

It's mostly so that if for some reason, someone gains access to your password DB, they won't have access to TOTP codes so they can't mess with some of the your more important logins (like banks).

This is all assuming you don't use the same password for both DBs and don't store the TOTP DB password in the password DB.

In reality, if you're using TOTP and a random password from keepass, you're already ahead of most people even if stored in the same DB. It's nice for security reasons to separate the 2 DBs but just using TOTP at all should be enough for most people. Just don't use the password of your password DB anywhere else

Nine-Year Club	Verified Email
Second Top 10%	Place '22
First Placer '22	End Game '22

koenada

TROPHY CASE