ndt-server VS SFTPGo

Data source: https://www.measurementlab.net

I get a test from https://www.measurementlab.net/ with it. Do realize that I'm from Europe and that testing a connection with an overseas server has a major impact on performance.

This is one of the better ones, but you can run whatever one you want, just don't use speedtest.net as they're trash now.

Tests are using the first hit when Googling "Speedtest" which connects to https://www.measurementlab.net/

To be specific in my thought here: we could fairly easily allow an admin to modify the endpoint in our client to measure loss & latency to an internal address or service in the cloud rather than our default. Speeds on the other hand are something we can't support just yet as it would require a test server near that endpoint. For what it's worth, the speed test application we use does have other examples for deploying your own test server. We'd need to do a deep dive into what that looks like from an engineering and business perspective before enabling teams to spin these up and use them as targets.

At a RIPE meeting I received this tip. Run an NDT test on https://www.measurementlab.net Although my skepticism at first I always seem to be getting a reliable response.

Google now uses https://www.measurementlab.net when you search for Speed Test so I have that bookmarked now

one possible solution: https://www.measurementlab.net/tests/ndt/

Well that is interesting, it's definitely something with googles built in speed test (thru https://www.measurementlab.net/).

I was just using speedtest.com and measurementlab.net/ before.

EDIT: Thanks for the recommendations from all of you!! I've chose to use the below: - Files: sftpgo - Calendar: baikal - Notes: memos (But beware, it sends opt-out telemetry) - Network folder: webdav on sftpgo

Give a try to SFTPGo

> Even these projects have gotten to a level of sophistication that it would implode without big tech support.

The worst thing is that all this FAANG or VC backed companies make a lot of people believe that they are the only viable way.

> Why do you think you don't see any interesting oss tech from hobbyists is these days?

Actually not true, just an example, https://github.com/drakkan/sftpgo. But there are plenty of them.

This is possible using SFTPGo. The default Windows installer register SFTPGo as a Windows service. You can download the portable version and run it manually or install SFTPGo from the Scoop packages. You can use the built-in SFTPGo virtual permissions to only allow uploads. SFTPGo uses virtual users, no system users are required.

I suggest contacting your SFTP server vendor. I guess they have an auto blocking policy like this

Basically it's a file storage managed over HTTPS. Nextcloud is pretty heavy, that's the reason why I using just a single statically compiled cross-platform binary SFTPgo

Using SFTPGo you can easily configure read-only accounts. SFTPGo uses virtual users and virtual permissions. So you don't need to create system users for your SFTPGo users and you don't need to use chmod to make folders read-only (but the system user that SFTPGo runs as needs file system level permission to access the files/folders you want to share)

SFTPGo provides SFTP, FTP/S and HTTP/S so you can share the same files using different protocols and thus meet the different needs of your business partners. Allowed protocols can be enabled/disabled per-user

You could check out SFTPGo, it may meet your needs.