Not something so complex that it requires docker. Not something that requires you to install a separate database. Not something that depends on redis and other external services.

This comment is a bit silly. Databases just make sense for many services, although many could just use sqlite which would be fine (and many do). Redis etc is usually optional and might increase performance in some cases.

I wouldn’t be a fan of something requiring docker, but it’s often just the easiest way to deploy these types of services (and the easiest way to install it as a user).

Anyway, I’ll echo that clear, up-to-date documentation is nice. I shouldn’t have to search through actual code or the bug/issues section to find current information (but I get this is very challenging). And I’d rather projects didn’t make Discord a source of documentation (especially not the primary one).

I’ll add that having a NixOS module is a big plus for me, but I don’t expect the developers themselves to maintain this.

Beyond the other comments is your public IP on ipinfo.io etc something like 100.64.X.X or 10.X.X.X?

If so, you’re behind a CG-NAT and raw wireguard will not work. I say this so you don’t waste time configuring something that will never work. Ignore the below if you have a real public IP.

Some ISPs will allow you to get a real dynamic ipv4 address for free, or you can configure ipv6 but any clients that you connect will also need public ipv6 support.

Otherwise, consider tailscale/headscale/netbird (SaaS or on a VPS) which have NAT traversal support.

Just a reminder that the comparison is against stock Wine and not with FSYNC (the Proton default). There’s still some impressive gains to be made over FSYNC too, just not as much as that benchmark. And possibly some stability improvements, too.