Quote from: SFR10 on Today at 06:05:00 PM

Quote from: hoeczek on March 29, 2025, 07:47:08 PM

if anyone sees any major errors or has any suggestions, let me know, I'll be happy to add something or fix it in my spare time.

A few notes:

- It would've been better if floating rates weren't static ^{[I'm not sure about the limitations of the APIs that you're currently using, but perhaps you can achieve thirty-second intervals for fetching data]}.
- I don't know much about coding stuff, but I think with a better server, the generation times can improve to an extent.
- A switch button would be nice.
- Despite clicking the "show me the results" button once, I got the following error on one occasion: Screenshot

Lastly, I'd like to thank you for coming up with yet another great website/tool.

Thanks for the feedback.

- Dynamic floating rates can be done, but it requires Javascript, and the site was built to work fine on Tor. JS is disabled in the Tor browser, and Tor users don't like JS

I can think about building it with some interactive parts for users with JS enabled, and if website detect JS is disabled then serve the current version. I have to think about it. For now it is just static.

- The generation time is based on the API response and has nothing to do with the server hardware (it more about network). I now have 10 APIs integrated and they are all checked at the same time, but if one is delayed then they are all waiting for it. I can think of a solution for this.

- Switch button? I think it's about to go to the next stage and swap coins. I didn't implement this because every API solves this in a different way, and if something were broken in the meantime, users would ask me about bugs, not the owner of the API. I do not want to take responsibility for transactions. This is just a simple exchange comparison.

- As there is no JS implemented in the code, I can't lock the button after it is clicked. So if someone will press it twice or more, then the error will be displayed. I have created an error page to limit requests to not ddos my site and not spam APIs requests (they are also limited by providers).

I hope it's clear now. Thank you for suggestions.