i hope that the dev-team has learned from the last error and not hasty announced on twitter to then delete it after a few days ...
i'm very curious what will happen on monday