erica / push-tweet
- Source
- Commits
- Network (0)
- Issues (0)
- Downloads (0)
- Wiki (1)
- Graphs
-
Branch:
master
commit 034fdffdb51bb2ba644f7bc3fbb1d838f5db99e6
tree 9a2911c10b2888c0dbda5b55a1a72edf0691521e
parent af3ca2da6767adaadc328a836f9f604f43cd457f
tree 9a2911c10b2888c0dbda5b55a1a72edf0691521e
parent af3ca2da6767adaadc328a836f9f604f43cd457f
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Mon Apr 06 21:03:35 -0700 2009 | |
| |
README | Mon Apr 06 21:11:04 -0700 2009 | |
| |
TreeNode.h | Mon Apr 06 21:03:35 -0700 2009 | |
| |
TreeNode.m | Mon Apr 06 21:03:35 -0700 2009 | |
| |
XMLParser.h | Thu Apr 09 10:29:36 -0700 2009 | |
| |
XMLParser.m | Thu Apr 09 10:29:36 -0700 2009 | |
| |
do-git | Mon Apr 06 21:03:35 -0700 2009 | |
| |
pushtweet.m | Fri Apr 10 01:19:02 -0700 2009 | |
| |
pushtweet.xcodeproj/ | Mon Apr 06 21:03:35 -0700 2009 | |
| |
pushtweet_Prefix.pch | Mon Apr 06 21:03:35 -0700 2009 |
README
The pushtweet utility basically sits and loops, polling search.twitter.com at the time interval you specify. When it finds a new tweet (i.e. one that does not match the tweet that was most recently stored), it pushes that to your iPhone. 1. You must supply your own push.pl (See Apple's dev forums). This is the utility that actually does the pushing. You must add your own credentials per the instructions. 2. You should update the TWEET_FILE to your own choice of location. Right now it saves to /Users/ericasadun/.tweet, which is probably where you don't want to save stuff. 3. Update the URL_STRING in XMLParser.m to the twitter search feed of your choice. Right now, it searches for, well, me. 4. Optionally set SHOW_TICK, when set to YES, will show the start of each fetch loop. 5. Out of complete paranoia, you'll need to supply your own push command. It should be easy to generate one from the twitter submitter and the message. You may want to add sound effects, etc. Pass the time interval between checks as the argument to the utility. It does atoi so time intervals are expected in integer seconds. Obviously, use at your own risk. Feel free to contribute bug fixes, etc. As always, feel free to contact me.
