rbw VS desktop

Yes, but it is quite uncomfortable to use, requiring you to get a session key and storing it somewhere. Instead, I've had good experiences with [rbw]. Maybe that would also be interesting for GP.

I've used to rbw for a rofi (and rofi-like frontend): https://github.com/fdw/rofi-rbw/

[rbw]: https://github.com/doy/rbw/

See https://github.com/doy/rbw for all the details

You can try using rbw to do that.

If you'd like a CLI client (also written in Rust), I'd recommend rbw, it's really simple but works a lot better for me than the official client.

If you know rust and C#, you can also look at bitwarden/server implementation (C#), or dani-garcia/vaultwarden (rust). Lastly, doy/rbw is a fully fledged CLI implementation of a client, and there is always looking at the official client implementation (bitwarden/browser and bitwarden/cli).

However, I've moved from that to rbw and I can honestly say it's much better. It handles locking/unlocking very well, and the interface actually makes sense.

I agree that the Bitwarden cli is awful. You have to log in, and store the token it gives you manually so that it knows you're logged in.

However, I found https://github.com/doy/rbw , and alternative OSS cli written in Rust, and it's exactly what I wanted. (Disclaimer: I liked it so much I wrote a rofi integration for it.)

Also forget about the automatic upload feature in the Android client, I switched to FolderSync for a reliable experience.

I've managed to get OnlyOffice working, Collabora Office previously broke for some reason. However latest upgrade also broke OnlyOffice. The solution for this is to put the secret and authorization headers into config.php in addition to the OnlyOffice plugin settings. [2] No idea why, but that is a thing.

My Nextcloud runs as a normal PHP application and I haven't had any issues with upgrading yet. Going from, I think, version 23 on Debian 11 to 27.1 now on a different machine running Debian 12 since I started using it.

Maybe I should find something more focused on file syncing, but the all-in-one approach of Nextcloud and its various plugins makes trying some new services very easy.

[1] https://github.com/nextcloud/desktop/issues/5031

[2] https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/60...

While reading this article, they were suggesting to modify the maxChunkSize in the Desktop client app configs, problem is, I've had this problem also on mobile... so that's not the solution I need.

I've added a link to this at https://github.com/nextcloud/desktop/issues/3912 which appears to be the right ID tracking it, and from what others have said this appears to be isolated to using the Virtual Files feature.

I know about this thread. If you look at the pull request that closes this, you see that this implements support in the clients for manual locking using the file_lock app. File locking like in a remote file system is probably not possible using a sync client (see this comment for example).

Nextcloud has had too many longstanding bugs like the one that mangles metadata, breaks sync, and requires server side intervention to fix [1]. I don’t trust them to do normal sync anymore. There’s no way I’d take the risk of letting them encrypt my data.

They need to slow down on features before tech debt ruins their product (if it hasn’t already).

1. https://github.com/nextcloud/desktop/issues/4378

Very regularly I get conflicts, right after editing a file. I found others having issues such as this Github issue and I tried some of the suggestions but so far none of them helped.