Make Busy.org work better in areas with slow connection

Related pull request.

This change was to fix the browsing experience for those with a very slow Internet connection.

When I would use busy from a certain room in my apartment (the part with the slowest Internet). I found the navigation would load but not the content itself. Where as steemit.com would take a long time but still eventually load.

I looked through the reported errors and found Steem user @dodybireuen had reported many people in Indonesia are experiencing the problem:

It is relatively hard to re-create the problem on fast wifi, I even used Chrome's network tools to simulate "slow 3g" which still wasn't slow enough to trigger the bug.

But on my own slow wifi I ended up finding the following error messages in the console:

In the end it was related to Busy assuming that if the front-end hadn't received a response within 5 seconds an error had occurred (which would be true on fast internet).

With some help from @Sekhmet, developer at Busy, I was able to adjust that time from 5 seconds to 15:

const options = {
  timeout: 15000,
};

const steemUrl = process.env.STEEMJS_URL || 'https://api.steemit.com';

const client = createClient(steemUrl, options);

It fixed the problem with my slow wifi at my house so hopefully it does the same for others!

---

Posted on Utopian.io - Rewarding Open Source Contributors

---