https://github.com/kisom/dropsonde-twitter

Twitter to SMS gateway built on Rails3.
https://github.com/kisom/dropsonde-twitter

Last synced: 18 days ago
JSON representation

Twitter to SMS gateway built on Rails3.

• Host: GitHub
• URL: https://github.com/kisom/dropsonde-twitter
• Owner: kisom
• Created: 2012-03-12T17:58:59.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2012-03-13T12:31:16.000Z (over 12 years ago)
• Last Synced: 2024-10-11T02:47:05.823Z (about 1 month ago)
• Language: Ruby
• Homepage:
• Size: 184 KB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# dropsonde-twitter

This was a project designed to provide a gateway between SMS and twitter

direct messages.

Doesn't Twitter support this already? Yes - *if* you're in a country

supported by their service. While I was in Tanzania, I wanted to keep

in touch with some friends via Twitter. While out in the sticks, SMS

was the only means of communications that I had, so I wanted to find a

way to use Twitter that way. 

Why didn't it work? No one supports sending SMSes programmatically to

the carrier I had.

Was it worth it? I learned quite a bit about architecting web apps (or

rather, how not to). One of the successes I had was, I think, in properly

sticking to the MVC paradigm and not attempting to put logic in the views.

The codebase is still ugly.

Can I use this and make it work for me? Most likely. You'll need to store

your Twitter consumer keys as environment vars on Heroku - CONSUMER_TOKEN

and CONSUMER_KEY.

Also, there are no tests. I am deeply ashamed of this.

Yes, there's commented out code. Here's why:

0. I designed this service to be used really only by me, because 99.99% 

of people are covered by the current service.

0. The only way to test some of the code was to push to heroku and pull 

down the crash logs.