☁️ Fix Cloudflare Speed #1083
Open
☁️ Fix Cloudflare Speed #1083
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☁️ Fix Cloudflare Speed
There have been multiple reports that the Cloudflare results are not accurate, at all. While it sometimes might work, I also suffered from substantially worse latency on my own instance.
This PR changes the data source of Cloudflare from a pure JS solution to a CLI-based solution. It uses CFSpeedtest, written in Rust.
However, for this to work there needs to be a way for MySpeed to hook into the latency tests. I've already opened a PR in code-inflation/cfspeedtest#204 but as of now, you need to manually compile the code from the PR and insert the binary inside the bin folder.
🚀 Changes made to ...
✅ Checklist
🔗 Related Issues
Fixes #985
Fixes #757