Online Archive

I also have my emails archived using my spam filter, so if my mail server is down I can still reply from there and I can even enforce filtering rules if I feel like it. If I don't want texts from area codes other than my own I can just block them, for example. Of course, that doesn't stop them from making it to my phone, but I don't actually look for messages on my phone very often.

IRC

The great thing about email is that it just lands as raw text on the mail server. You can do absolutely anything you want with raw text, so this is where it gets nerdy. My favourite way to answer text messages is IRC. I got addicted to IRC at the office where we use it for everything: generating support tickets based off of caller display from inbound calls, alerts for new email tickets, vacation schedules, meeting call reminders, and just to chat and ask questions with colleagues. As a result, I always have an irssi window open and have alerts set up whenever my nick is mentioned.

I set up software on my mail server called Procmail which can take various actions for all incoming email. This is set up to copy the contents of my SMS emails and send them to myself in a special IRC channel. Since my nick is mentioned I get a notification in the corner of my screen when messages come in. Procmail actually runs a script that creates, or retrieves a nick for each phone number before sending the message to IRC. The nick is made up of a 3 character shortcut plus the actual phone number. That way I can tell who it was from and reply by referencing the shortcut as shown in the image. I have an IRC bot that then parses for the shortcut, finds the associated phone number and sends the message back to it as a reply via email. This way I can have multiple conversations going in the same window and can reply to each seperately.

My IRC channel is open from anywhere, but password protected outside of my LAN, so as long as my firewall is open and I have an IRC client, this is usually how I 'text'. The fallback is then my desktop email client. If that fails there is always webmail. If my mail server is down I can use my Archiver. Finally, if I don't have access to a keyboard, I can be an animal and answer with my cell phone, but what am I, some sort of Millenial.

API

As I mentioned, the SMS to Email interface is largely old news. It is an inelegant way of interacting with the service. There are a lot of steps, but less complicated than doing any serious programming to hack together a solution. I have since taken the time to do this better by interacting directly with the services API. For those who aren't aware, this is a Application Programmer's Interface. Basically it means that I can send requests directly to the service provider and handle the responses however I need. This is how apps like the third-party Android app I use work.

This largely just simplified how I get the data. Most of the user interaction is the same. While the emails still come in for archiving and replying will still work, I no longer do anything with Procmail. Instead, I can have my API program running anywhere I like, not just on my mail server. This is then able to submit new messages directly and poll for any new inbound messages to alert me to. When new messages still come in, the code that sends that message to IRC behaves basically as it did above and IRC replies are forwarded back through the API as well.

The main advantage to the API data is that it is all standard JSON which is a data structure that is extremely easy to work with. Emails are sort of clumsy for things that aren't regular email since they come with large headers. I need to parse the Subject to get the sending phone number, then need to make sure that only the text in the body gets collected as the message, and the rest is useless. Email is also not guaranteed to be an instant communication tool. It is robust so that if a message is delayed it will be retried regularly, but flow through multiple servers, including at least one spam and virus scan means that it could take seconds, minutes, or days. The messages in JSON cannot be confused with one another, because they inclued IDs that can be referenced in other API calls. There is no extra junk meta-data, and no extra steps to slow it down.

While the data is much easier to work with, but developing an API client application is more work. In the end though, because the functions that send and receive the messages are abstracted away from the interface, it is much easier to add new ways to interact. For instance, I have a Cronjob that looks through my calendar and sends me a text message for appointments, such as meetings that I have that day. If I'm away from the office 30 minutes prior, as indicated by my phone not being on the Wi-Fi, it will alert me to get back to the office. I could set up a task to automatically send other people messages on certain days/times. I have even set up a basic auto-reply robot that can provide myself and others with information. For instance, if the sender is on a trusted list, they can find out what I have scheduled by asking the robot. Unknown/untrusted numbers can get pointed to this website. I can text myself to have the bot give me OC Transpo bus information, or add an appointment to my schedule. Keep an eye out for a future Projects article on this robot as I'm working on a new version that will have many more features. This also solves the message filtering problem since the API allows me to delete the messages remotely and my phone will sync those deletions.

Some of this can be cobbled together with Google Calendar and a specific app for each task. Others just can't be done at all. But even with those that can be done, I would be changing from the way I want to interact with the system in order to get the result I want. I don't want Google to know my schedule, nor do I want 30 apps on the phone I rarely look at. If I sit in front of an IRC screen all day anyways, it is nice to get all of my notifications and messages there, where I can react to them with a comfortable keyboard.