Monday, July 19, 2010

The API is ready tomorrow

It went faster than expected, so if there’s anyone that wants to test the API, let us know right away via Feedback.

No more ringtones for now

This has been shut down, while looking for a better replacement provider.

Long overdue: Media Upload API

Work has been started on an API that will support all the media types that Twitizer can handle, that include many image, video and audio formats. Actually exactly the same formats you today can e-mail or upload to Twitizer, including most of those used by mobile phones.

The API will be TwitPic and partly TwitVid compatible which means you just need to change the host URL to use Twitizer instead, and it adds video and audio on top of what TwitPic supports.

There will be optional parameters, like GPS position, as well.

This is expected to be ready during this week.

Blame the tiny donut

There was by mistake one ‘o’ too much in the e-mail retriever code, which caused it too fail. That’s fixed now, and the messages that had been queued up have been taken care of.

Sorry about that.

Thursday, July 8, 2010

Alias mix-up fixed

A bug sometimes caused messages with the Twitizer address in the “Cc” or “Bcc” fields, but not in the “To” field, to be addressed to someone else completely (actually the person that sent the previous the queue). This is fixed now.

We also added that if Twitizer doesn’t find a Twitizer address in the “To” field it will now also check the “Cc” and “Bcc” fields for a valid address, provided those fields are included. It will catch the first such address it finds and use that as the recipient.

We hope this will make the placement of the Twitizer address more flexible. E.g. you can now send the message “To” some friends and at the same time “Cc” it to Twitizer. You hopefully get the general idea.