Usability with slow internet

[kirkins]

I'm having an issue that sounds similar to #1576.

Unfortunately my internet is slow right now.

This has led to find that both Busy client and server have a maximum timeout of 5 seconds.

Related issue for rpc.

[Sekhmet]

We for sure don't want to increase the timeout on the server to 15 seconds (as it will cause a request to take up to 15 seconds to finish).

[kirkins]

@Sekhmet if it is "up to 15 seconds" I think that is fine for anyone with slow Internet.

If it is minimum 15 seconds that will be a problem. Is this maximum 15 seconds or minimum?

The problem with 5 seconds is that busy.org becomes completely unusable for anyone with a slow internet connection. If I switch to Steemit.com instead on slow internet it takes a while, over 5 seconds but it eventually loads.

With this current timeout Busy just says if you can't load a request in 5 seconds you can't use the site.

There are a lot of people using Steem in developing countries so I'm sure this issue is extremely common.

[Sekhmet]

Let's say api.steemit.com has some problem and won't finish request that we make on the server -> user is waiting for 15 seconds for Busy.org to respond.
Client timeout can be changed, but I don't think we should keep hundreds of open connections on the server, just because we are waiting for API to suddenly come back to life.

[kirkins]

@Sekhmet I see the server part is just concerning communication between Busy and Steem API?

I didn't realize that, I'll have to do some more testing. The PR as it is now doesn't improve the situation for me at all.

[Sekhmet]

If you want to change timeout on the client only you can do it here:

busy/src/client/steemAPI.js

Line 3 in cd3b1a3

const client = createClient(process.env.STEEMJS_URL || 'https://api.steemit.com');

[kirkins]

@Sekhmet thanks, that fixes it for me.

Note: deleted original 2 commits.

[bonustrack]

Thank you, seem to be working well now 👍