Next scheduled rescrape ... never
Version 1
Last scraped
Scraped on 05/05/2025, 17:19:38 UTC
I think I have fulfilled all the requests from the forum 
Almost 
You mentioned in the past that the switch/swap coins button would be in the next update.Quote
If value is odd or n/a or 0, then amount does not meet min/max requirements.
You should calculate that in the backend, and make everything consistent. - @hoeczek: I don't think it's a good idea to include exchanges that don't support a specific pair in the results (screenshot).
Haha I mentioned it but also in this post https://bitcointalk.org/index.php?topic=5536727.msg65245814#msg65245814 i resigned from it.
and about the second part, I had to add that loading page as when I tested API responses it looks like average API response for each is from 1 to 5 sec (mostly depends on Crypto pairs). So I have 10 services integrated and in the worst case it is 10*5 sec. But average for all is around 26 sec.
As I am not using JS (target audience is also hidden services with onion domain) I cannot block button for the time of getting info from API's so I added loading page, also I switched from getting one by one to getAllRatesParallel() function which is using curl_multi_exec so I can ask each API in same time.
I still need to dive into it, but for now loading page solves my problems, informs users and wait time is not as bad as some time ago.
So for now I have on my list:
-show consistent info if pair is supported, not meet requirements etc.
-work on optimization
-more testing on
Original archived Re: Cheap Crypto Deal
Scraped on 05/05/2025, 17:14:39 UTC
I think I have fulfilled all the requests from the forum
Almost You mentioned in the past that the switch/swap coins button would be in the next update.Quote
If value is odd or n/a or 0, then amount does not meet min/max requirements.
You should calculate that in the backend, and make everything consistent. - @hoeczek: I don't think it's a good idea to include exchanges that don't support a specific pair in the results (screenshot).
Haha I mentioned it but also in this post https://bitcointalk.org/index.php?topic=5536727.msg65245814#msg65245814 i resigned from it.
and about the second part, I had to add that loading page as when I tested API responses it looks like average API response for each is from 1 to 5 sec (mostly depends on Crypto pairs). So I have 10 services integrated and in the worst case it is 10*5 sec. But average for all is around 26 sec.
As I am not using JS (target audience is also hidden services with onion domain) I cannot block button for the time of getting info from API's so I added loading page, also I switched from getting one by one to getAllRatesParallel() function which is using curl_multi_exec so I can ask each API in same time.
I still need to dive into it, but for now loading page solves my problems, informs users and wait time is not as bad as some time ago.
So for now I have on my list:
-show consistent info if pair is supported, not meet requirements etc.
-work on optimization
-more testing on ECR-20 tokens