@ArtOfCode For each action and for each path a graph with x=time and commit sha at that time then y=duration (lines for view/db/total) (prolly averaged over some time for smoothness). Also for each status code, same x, y=count of occurances of status code on route (again, averaged for smoothness).
Straw poll! If there were an option to provide metasmoke your SE account credentials (stored the same way tokens are), in exchange for auto-retraction of bad autoflags, would you be interested?
One thought was to create special MS credentials - you add a credential to your acct. as prescribed by the UI: "user-7@metasmoke.erwaysoftware.com" / "1gIbBeRiShHeRe!"
Pretty trivial to revoke that single credential if you want to, and trivial for staff to clean up stuff from sessions ending in that domain if I do go nuts
to add something useful to the discussion, I'd also feel uncomfortable giving out full credentials
about "Pretty trivial to revoke that single credential if you want to, and trivial for staff to clean up stuff from sessions ending in that domain if I do go nuts"
it's equally trivial for you then in theory to revoke my real, original login
I'd consider you somewhere pretty high in my list of online people ranked by trustworthiness. But still you're only a dog icon I don't exactly know pretty well.
@Undo Login'd be better, actually - run MS' net connection through a public Google proxy of the type that we see zillions of on mod reports, and you'd basically be invisible
@Undo still, you've probably got an hour before staff start taking notice... more if you start on the low traffic tags and build up something big to merge [javascript] into
@Undo Personally, I'd decline. I'm uncomfortable providing my credentials. If I was sufficiently motivated to have this functionality, I'd just write it as a browser extension, so people can just install it and not have to have an SE tab open. It would actually be fairly easy to do, you could do it just by listening to the MS WebSocket.
@ArtOfCode Only 28 seconds? While that's a bit long for an API request->response, it's not even close to a long regex search on MS. If MS was flooded with requests, that would, obviously, be a different issue.