The multi-pathway communication

TradeRange.net uses Cloudflare Proxy to provide the website faster and better, as well as DDOS protection and bot detection. This also allows us to leverage Cloudflare's CDN network caching to reduce our server load.

Regrettably, Cloudflare has regional limitations, which affect some potential users.

Russia and China are the most notable countries that limit access to cloudflare protected services. We didn't want to leave the spread of benefits offered by Cloudflare, so we have been considering possible alternatives.

Currently the main option is to separate the app and website. Our entire site is proxied through Cloudflare. This will not change. The app on the other hand has the frontend stored locally and polls the backend via api.traderange.net. We intend to review the potential of creating an api2.traderange.net or a separate domain that isn't proxied that connects to a VPS of our own and relays information to our main server. This will undoubtedly be slower than using Cloudflare, but the difference shouldn't be noticeable for most users.

The idea is that the app will check the first api subdomain and if unavailable will move to the next one. In line with our desire to give users choices about how their data is sent and relayed we will detail this in the privacy policy if deployed and will offer users the ability to choose which path their data takes by selecting it in the settings page of the app.