Community Page
- www.ChristopherSPenn.com/ Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- Happy 4th of July...from your cousins in Canada!
- Look at the Personal Democracy Forum. From what I understand, it had record attendance this year even with all the tweeting and live blogging. Instead of complaining about it, conference organizers...
- Great thoughts to live by, Chris. Have a happy and safe 4th.
- Podcamp started as a series of conversations, in many ways, over time, we've sometimes drifted more towards the presenter/audience model than necessary. I find that I may learn a thing or two...
- Chris, great insightful post and timely given the Anderson inspired FREE debate. As others have commented the interpersonal magic that happens in between sessions and over lunch is usually more...
Christopher S. Penn's Awaken Your Superhero
Christopher S. Penn's Awaken Your Superhero
The Mac’s Terminal is the UNIX command line. It’s hard core, the stuff that Apple actually tries to keep away from the casual user. It’s the direct line to the heart of the machine, and it’s where cool scripting action can occur. Here’s
... Continue reading »
2 years ago
2 years ago
2 years ago
#!/usr/bin/env sh
curl -u yourusername -d status="$1" -s -o /dev/null http://twitter.com/statuses/update.xml
1 year ago
I work with ubuntu 7.10
I've follow the steps but when I type in the terminal:
tw
and ask for my host password I enter my twitter pass, but it says:
Couldn't resolve host
The host pass and the twitter pass are different?
Thanks
1 year ago
Only to add the script works in gnu/linux OS too
Regards
1 year ago
Cool. I'll be looking into Chris Brogan's question. I'm definitely interested in seeing Tweets in the Terminal.
1 year ago
1 year ago
crimeboy@groselia:~$ cat twi
#!/bin/bash
# requires curl
###########################
######## CONFIG
USER=YOULOGIN
PASS=YOURPASS
URL="http://twitter.com/statuses/update.xml"
###############
curl -u $USER:$PASS -d status="$*" -s -o /dev/null ${URL}
1 year ago
I like you script, its simple and sweet. I only have to say that its probably not a good idea to advise people to chmod something to 777. This would enable other users (who would have access to your machine or network) to see not only the password which is hard coded in the script, but to change the script and insert something malicious. Perhaps something a bit more conservative like 700 would be a better choice. This value would mean that the owner (you) has read, write and execute permissions on the file, but no one else. I know you probably, and rightfully trust the people on your network, but hey--its the same amount of typing and you get free security :).
Kind Regards,
Jesse
1 year ago
1 year ago