Bot author here. That post was before twitter made changes on the id generation. Now it consists of four parts that you need to guess (the datacenterId, the workerId, a sequence and a timestamp).
For more details, the bot repo is here: https://github.com/pomber/escher-bot
As you said, it largely relies on reverse engineering and bruteforcing Twitter's ID generation.