Frequently Asked Questions

1. The gcal bot is my friend but I can't see any events in my calendar

   This could happen if the registration process has failed. Go to twittercal.com and repeat the procedure. If you still have a problem, don't hesitate to contact us.

2. There is a delay between the message I sent and the update of my calendar

   Due to the new Twitter policy to reduce heavy traffic from clients, the bot check for new messages every minute. The delay can be a bit longer is its request quota has been reached; but don't worry it's a matter of minutes.

3. How do I unsuscribe from the service?

   You can revoke our access to your calendar at any time. Go to your Google Account and select “change authorized web sites” then revoke access for Twittercal.

4. I see “d gcal” in the title of my event, how can I get rid of it?

   Using the shorcut “d gcal” is only required when sending a direct message from an external client or from your own Twitter page. If you go to twitter.com/gcal and send a message from there, you don't have to use the shortcut.

5. What are the different syntaxes for creating events?

   We use the Google Calendar Quick Add feature. It's a way to describe events using natural language. We support anything Google does. Go on this page for more information.

6. Does Twittercal work with a Google Apps hosted calendar?

   No. Due to the way authentication work with hosted calendars, supporting this service would require to store your password. Regarding our privacy policy, we could not afford it. As soon as Google support a safer authentication method, we will support the service.

7. What technologies did you use to make Twittercal?

   The Twittercal website is powered by Ruby on Rails. The bot itself is powered by Java. Both are hosted on a Dedibox dedicated server in France.

←