I still have yet to do more work with osakit, but from the little time I used it, it seemed to have a few flaws. It's definitely worth using, but you may want to think about workarounds instead of long delays.
Why not have the page check whether the user has the appropriate properties (Browser, OS, etc) that seem to work best with osakit/your application, and if not, forward them to a page telling them what does work best, with the alternative of downloading the application?
Even if the problem is on blitzmax, there will still be plenty of people incapable of accessing it via osa due to access limits, computer illiteracy, and faulty browsers (along with faulty browser settings).
Why not have the page check whether the user has the appropriate properties (Browser, OS, etc) that seem to work best with osakit/your application, and if not, forward them to a page telling them what does work best, with the alternative of downloading the application?
Even if the problem is on blitzmax, there will still be plenty of people incapable of accessing it via osa due to access limits, computer illiteracy, and faulty browsers (along with faulty browser settings).