The problem is that syncing between devices is not implemented in KeePass itself but through an external tool (Nextcloud, Syncthing, or whatever else). The sync client will only see the ciphertext and won’t be able to tell which records have been changed, only that two different binary files have a common ancestor and are in conflict.

The most obvious solution is to lock and close the database when it’s not in use (which is a good practice from a security perspective too), and to sync immediately when it is changed.

tl;dr: yes, credentials are cached locally. https://github.com/dani-garcia/vaultwarden/discussions/4676

The major downside to the single file storage used by Keepass is that it’s easy to accidentally create a conflict between files on different devices if they’re not synced immediately. Conflicting files have to be merged manually or data might be lost. I’ve run into this several times with Keepass + Nextcloud. In comparison, a central master database with local cache can resolve conflicts between individual records.

deleted by creator

Tailscale should work. It uses Wireguard and does some UDP fuckery to get around the firewall and NAT (including CGNAT). I can stream Jellyfin through it at 1080p native with no significant buffering, it’ll work for music.

Look at this: https://github.com/ChthonVII/guildwarslinuxinstallguide?tab=readme-ov-file#part-11-toolbox

“Run EXE inside Wine prefix”

It might not work, though. I’ve tried to use a similar tool with Snowrunner, it found the process, but didn’t actually work.

One of these might help: https://steamcommunity.com/app/275850/discussions/0/601902145259725017/

Although I wouldn’t be surprised if it was caused by NMS’s own network backend. When the Corvette update was launched, multiplayer was fine on my work computer, but did not work on my home PC. It’s a constant dumpster fire.

If you have Steam installed, try putting them in ~/.local/share/Steam/compatilitytools.d.

He can’t, he had to re-run a benchmark.

Is this what normies feel like when Linux users tell them to just use Linux? I have some apologies to make.

POW is a far higher cost on your actual users than the bots.

That sentence tells me that you either don’t understand or consciously ignore the purpose of Anubis. It’s not to punish the scrapers, or to block access to the website’s content. It is to reduce the load on the web server when it is flooded by scraper requests. Bots running headless Chrome can easily solve the challenge, but every second a client is working on the challenge is a second that the web server doesn’t have to waste CPU cycles on serving clankers.

POW is an inconvenience to users. The flood of scrapers is an existential threat to independent websites. And there is a simple fact that you conveniently ignored: it fucking works.

Interface configuration and DNS resolution are managed by different systems. Their file structures are different. It’s been like this for many decades, and changing it is just not worth breaking existing systems.

No numbers, no testimonials, or even anecdotes… “It works, trust me bro” is not exactly convincing.

The option doesn’t have a value. You just need to specify that the option should be present, e.g. defaults,noatime,windows_names,uid=1000,gid=1000 in fstab, or mount.ntfs -o noatime,windows_names,uid=1000,gid=1000 for manual mounts.

This comment on the UDisks github page elaborates on why the ntfs-3g driver does not automatically restrict the usable characters.

UDisks itself does mount NTFS volumes with the windows_names option, and the last comment in the same thread explains why enforcing that restriction with no way to opt out is a breaking change for some users.

uid=1000,gid=1000,dmask=022,fmask=133

You can very easily fuck up your NTFS filesystem and make it unmountable in Windows. Would anyone be surprised to learn that not even Windows is fully compliant with the NTFS specifications? Some characters, like :, are valid for NTFS filenames, but illegal in Windows, and if you create such a file (e.g. in a wineprefix’s dosdevices), Windows will refuse to mount it. Ask me how I know.

The solution is to specify the windows_names option every time you mount the filesystem, both in fstab and when using mount.ntfs.

If this is as significant an issue as you imply, please link some credible sources.

As far as I can tell, the “Chinese server” (or EU server) is just a public ID and Relay server, and necessary for the application to function unless a self-hosted server is used.

You can host the open-source ID and Relay servers for simple remote access at no cost. The pro subscription is mainly about account and device management.

services:
  hbbs:
    container_name: hbbs
    image: rustdesk/rustdesk-server:latest
    command: hbbs
    volumes:
      - ./data:/root
    network_mode: "host"
    depends_on:
      - hbbr
    restart: always

  hbbr:
    container_name: hbbr
    image: rustdesk/rustdesk-server:latest
    command: hbbr
    volumes:
      - ./data:/root
    network_mode: "host"
    restart: always

Then why are you complaining about not getting a Gamers Nexus video that benchmarks game performance spelled out to you when it isn’t even relevant to your use case?

Being able to use anything other than Windows without any significant loss in performance is a pretty fucking big advantage.

Mount the network share (fstab or mount.cifs), and pass the login using the username= and password= mount options. Then point the volume at the mount point’s path.

https://www.mattnieto.com/how-to-mount-an-smb-share-to-a-docker-container-step-by-step/