This incident is caused by coding errors that, for some reason worked in my testing but did not work for other users. It has been patched and should not happen again.
We're sorry for any inconvenience caused.
Posted over 1 year ago. Dec 01, 2017 - 08:04 EST
I guess it's fine now. Sorry for all the troubles.
Posted over 1 year ago. Nov 30, 2017 - 20:14 EST
The fix has been pushed. We'll wait half an hour and if everything is fine we'll just close this incident.