Being perfectly honest, this is one of the reasons I'm working on GLBSE 2.0, to get rid of this problem. And on that note, I'm almost ready to put up the latest changes to dev.glbse.com, which has basically just be user input validation.
thumbs up for improvements on that (input validation), is badly needed
while whining over the soon to be gone design of the 1.0 web client I was thinking if the API would be powerful enough to allow custom clients and the reimplementation of the current design (or something of comparably elegant and simple) as I can't get used to the new look & feel. let's see what the dev version brings and post a handful of new bugs found (I know at leas one more dedicated user who's willing to sync and perform coordinated testing once you release something new).
would you mind to indicate & update the version already since software is in this pre-release state? it would help the guerrilla testers to better reference bugs' affect/fix versions and allow better focus on what needs to be retested between the site updates. without release notes it's hard to track versions of what is to be tested. it would also help to know where you version the code and maybe add some lyrics //comments to your code if it's going to be public. not volunteering developing but willing to help with the release mgmt folklore and QA in general.
either as a date/timestamp of the code that you install in glbse or incrementing in old fashioned way 2.01, 2.02 etc.
the uptime checking of glbse 1.0 would not be that difficult. I
strongly humbly recommend using it as long as possible. because
1) i like it more
2) it has great record of security (not yet been compromised afaik, surely not only due to the epic downtimes but also because of the quality of the current code, and the use of webkeys - should be pretty hard to brute force)
3) has only minor defects which do not affect functionality (create buy or sell that is paired immediately and it won't display list of tx that result from that closing; one has them the other not, not sure which one is which. history in web client is limited to 10 entries; the python client can browse full history. some history pages sort newest first, some sort the other way.)