Hi Kevin
> What about re-trying in the event of an error? Or maybe delaying a few
> seconds if the network is down?
It’s the “detecting the network is down” bit that the code doesn’t currently
do: we need new code that hasn’t been written yet that can distinguish between
a genuine error and t
Thank you for your reply.
What about re-trying in the event of an error? Or maybe delaying a few
seconds if the network is down?
My laptop is accessing 3 node.js Tiddlywikis which hosted on a server. I
don't mean to be a whiner, but every time my laptop goes wakes from sleep,
I have to refre
Hi Kevin
Those errors are the result of the browser tab being suspending and resumed. We
should suppress those errors, but it’s hard to reliably distinguish between
true errors and expected errors, so TiddlyWiki currently dutifully displays
them to be on the safe side. My own habit at the momen
I'm getting frequent "syncer-browser-tiddlyweb - Error retrieving skinny
tiddler list: XMLHttpRequest error code 0" errors.
I run 3 node.js Tiddlywikis in 3 browser tabs, continuously. Often, after
I wake my laptop from sleep, they all three report this error. I haven't
observed any data loss
4 matches
Mail list logo
