Simon

After lots of extensive testing, dependency cleaning, rebuilding and messing with build flags: This is not a fault caused by either electron-rebuild or electron-builder. It will happen even if you...

Actually the better way would be to just provide the --token option like it is specified in the install command by default - otherwise fall back to try to guess...

@alexellis made a one time donation as a small thank you

If you're going the hard way you might want to consider argon2id instead of scrypt concerning side-channel attack resistance: https://www.cryptolux.org/index.php/Argon2 https://tools.ietf.org/html/draft-irtf-cfrg-argon2-03#page-13 Otherwise customizable, read increased iterations should be sufficient for...

@c-bordon I'm currently trying to test-compile your branch-changes on an arm64 bullseye node (debian 11) ... How exactly do the commands look like to build the dashboard and indexer packages?...

This is an issue with the App. You can circumvent this by using FolderSync from the Play-Store which has Nextcloud-Support and syncs instantly without any issues. The advantage to this...

Downgrading to 4.2.0 does solve that issue, if that's an option.

Since this issue wasn't solved yet: I had that exact error while compiling for armhf, which indeed is a 32-bit SoC. Creating a architecture specific uptime_fact_armhf.go file didnt work out...

> Is there some advantage to having seaweedfs S3 layer involved as well? No, absolutely not. I was testing fusefs-s3fs about a year ago as the last try in regards...

Yes I did read all and verified it myself on my different hosts (some of them brand new) before I put it up - let me add reference from the...