AUTHOR'S NOTES Regarding the html manifest.appcache method: * Chrome does implement an updated manifest.appcache and thus reloads from the server if wanted, but only after its own cache has been cleared. And that is too bothersome for the average user. * Firefox does not even do that. It seemingly totally ignores an updated manifest.appcache, even with Ctrl+F5. It's worse than that, even: the source code *is* renewed, according to Notepad++, but the rendering stays the same! Seemingly, the html manifest.appcache method makes FF render the appcached version, no matter what. Therefore: * The method should preferably not be used. * If it is used, for every updated version a new, different URL and a ditto tiny.cc URL must be made. Furthermore, due to cross-browser differences regarding the display and processing of decimal separators, i.e. point vs. comma, per-browser different entries are necessary.