Less Sophisticated Release Title

created_at field is not filed with the tweet's timestamp. Instead a new timestamp is created when the event is created (this is actually how it originally worked). Tweet's timestamp is now available in the "tweet_timestamp" tag.

I realized it's not a good idea to use tweet's timestamp because every Twitter account has its own worker and there are pauses of refresh_interval_secs seconds between tweet fetches. So if the tweets' timestamps were used for created_at field it would mean the bot can send event with created_at: T and later another (from another account worker) with create_at: T - x meaning the latter event would be inserted into the existing timeline so it would be easy to miss it.