10-30-2018, 08:44 PM
Current problem: cent browser static server is overloaded, not enough resources for uploading or even process data from your side. That means I can't download file from your server anymore for peak hours because of overloaded servers, and many other users too (even with update feature).
Suggestion: please spend some time and invistiagate problem and implement proper solution which will avoid issues with downloading browser, download speeds, etc from your static server.
Possible solutions:
1. Torrent server where people will just download torrent and download browser from other clients via using torrent network.
Pros:
+ almost no loading on your side, whole BW will be well balanced between centbrowser users
+ maximum download speeds for client and for deviverying app
+ 100% guaranteed that the files will be shared across clients and files will be backuped on dozens of PCs
Cons:
- torrents can leak IP addresses of clients (users of CentBrowser), but it's how torrenting works, nothing critical.
- torrents require at least some of the public torrent tracker or even your own (announcer)
- In many countries as far as I know torrents are blocked (torrent traffic), but because you will deliver your app fully legal, I don't see any reasons to worry about
- clients need special software for downloading cent-browser (torrent client) (there is built-in extensions for doing it even from browser itself).
Extra suggestions related to torrent tracker:
- If you can do that thing, and if users will be not be against, you can super easy share data and use client PC's as extra sources for built-in updater in the browser (just for example), it will greatly reduce possible issues.
2. Optional uploading to alternative file-sharing sites with no download bw limits, or with big limits.
I mean next: except main static file hosting you will upload the same file to some of cloud service which allow to download file, or to any other service, where all bw will be processed via 3rd party provider and not your static file server. More alternative links - more stable will be downloads from the main site.
Candidates:
- Google Cloud Drive
- 4shared
- DropBox
- MediaFire
- 1fiecher
3. Optional uploading to specialized cloud based services for deliverying files or hosting them
Same as above, but these solutions developed for business and cost some money. (not too much, but still per months)
Candidates:
- wasabi.com - does not restrict traffic (but 5$/mo)
- aws
- google cloud drive
- ovh
4. Optional uploading to VPS with good port link and using any CDN
For example several providers with 10Gbit/s uplinks with normal price:
- https://fastpipe.io/cloudserver (10gbit/s) not limited traffic (recommend)
- https://blazingfast.io/ (10gbit/s) not limited traffic
Suggestion: please spend some time and invistiagate problem and implement proper solution which will avoid issues with downloading browser, download speeds, etc from your static server.
Possible solutions:
1. Torrent server where people will just download torrent and download browser from other clients via using torrent network.
Pros:
+ almost no loading on your side, whole BW will be well balanced between centbrowser users
+ maximum download speeds for client and for deviverying app
+ 100% guaranteed that the files will be shared across clients and files will be backuped on dozens of PCs
Cons:
- torrents can leak IP addresses of clients (users of CentBrowser), but it's how torrenting works, nothing critical.
- torrents require at least some of the public torrent tracker or even your own (announcer)
- In many countries as far as I know torrents are blocked (torrent traffic), but because you will deliver your app fully legal, I don't see any reasons to worry about
- clients need special software for downloading cent-browser (torrent client) (there is built-in extensions for doing it even from browser itself).
Extra suggestions related to torrent tracker:
- If you can do that thing, and if users will be not be against, you can super easy share data and use client PC's as extra sources for built-in updater in the browser (just for example), it will greatly reduce possible issues.
2. Optional uploading to alternative file-sharing sites with no download bw limits, or with big limits.
I mean next: except main static file hosting you will upload the same file to some of cloud service which allow to download file, or to any other service, where all bw will be processed via 3rd party provider and not your static file server. More alternative links - more stable will be downloads from the main site.
Candidates:
- Google Cloud Drive
- 4shared
- DropBox
- MediaFire
- 1fiecher
3. Optional uploading to specialized cloud based services for deliverying files or hosting them
Same as above, but these solutions developed for business and cost some money. (not too much, but still per months)
Candidates:
- wasabi.com - does not restrict traffic (but 5$/mo)
- aws
- google cloud drive
- ovh
4. Optional uploading to VPS with good port link and using any CDN
For example several providers with 10Gbit/s uplinks with normal price:
- https://fastpipe.io/cloudserver (10gbit/s) not limited traffic (recommend)
- https://blazingfast.io/ (10gbit/s) not limited traffic