commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:
An improvement of the original (at: http://www.commandlinefu.com/commands/view/2872/update-twitter-via-curl) in the sense that you see a "from cURL" under your status message instead of just a "from API" ;-) Twitter automatically links it to the cURL home page.
Doesn't require password (asks for it instead)
*** CAREFULLY READ THE NOTES **** *** THIS DOES NOT WORK "OUT OF THE BOX" ***
You'll need a few minutes of CAREFUL reading before making your own Twitter feed:
In 2010 simple command line Twitter feed requests all stopped working because Twitter upgraded to SSL security.
Https requests for a filtered Twitter stream feed now require a special header called "oauth_header".
The benefit is that your stream feed and login info is securely encrypted.
The bad news is that an "oauth_header" takes some work to build.
Fortunately, four functions, imaginatively named step1, step2, step3 and step4 can be used to build a customized oauth_header for you in a few minutes.
Now, go look at "step1" to start creating your own oauth_header!
Pump up the chatter, run this script on a regular basis to listen to your twitter timeline.
This is a rough first cut using several cli clips I have spotted around. There is no facility to not read those things already read to you. This could also easily be put in a loop for timed onslaught from the chatterverse, though I think it might violate several pointsof the Geneva Convention
UPDATE - added a loop, only reads the first 6 twits, and does this every 5 mins.
This is the FOURTH in a set of five commands. Please see my other commands for the previous three steps.
This command builds the authorization header required by Twitter.
For this command to work, see my previous 3 commands (step1, step2 and step3) as they are required to build the environment variables used in this command.
For more information on the authorization header, go to dev.twitter.com/apps, click on any of your apps (or create a new one) and then click on the "OAuth Tool" tab.
This is the THIRD in a set of five commands. See my other commands for the previous two.
This step creates the oauth 1.0 token as explained in http://oauth.net/core/1.0/
The token is required for a Twitter filtered stream feed (and almost all Twitter API calls)
This token is simply an encrypted version of your base string. The encryption key used is your hmac.
The last part of the command scans the Base64 token string for '+', '/', and '=' characters and converts them to percentage-hex escape codes. (URI-escapeing). This is also a good example of where the $() syntax of Bash command substitution fails, while the backtick form ` works - the right parenthesis in the case statement causes a syntax error if you try to use the $() syntax here.
See my previous two commands step1 and step2 to see how the base string variable $b and hmac variable $hmac are generated.
This is the SECOND command in a set for five that are needed for a Twitter stream feed.
This command creates variable "b", the so-called "base string" required for oauth in Twitter stream feed requests. (The 256 char limit prevents giving it a better name)
We use five environment variables created by a previous step: id, k1, once, ts and k3.
The five environment variables are created in a separate command, please see my other commands.
For more information on the signature base string, see dev.twitter.com/apps, click on any app (or create a new one) and then go to the "OAuth Tool" tab.
Twitter stream feeds now require authentication.
This command is the FIRST in a set of five commands you'll need to get Twitter authorization for your final Twitter command.
*** IMPORTANT *** Before you start, you have to get some authorization info for your "app" from Twitter. Carefully follow the instructions below:
Go to dev.twitter.com/apps and choose "Create a new application". Fill in the form. You can pick any name for your app.
After submitting, click on "Create my access token". Keep the resulting page open, as you'll need information from it below.
If you closed the page, or want to get back to it in the future, just go to dev.twitter.com/apps
Now customize FIVE THINGS on the command line as follows:
1. Replace the string "Consumer key" by copying & pasting your custom consumer key from the Twitter apps page.
2. Replace the string "Consumer secret" by copying & pasting your consumer secret from the Twitter apps page.
3. Replace the string "Access token" by copying & pasting your access token from the Twitter apps page.
4. Replace string "Access token secret" by copying & pasting your own token secret from the Twitter apps page.
5. Replace the string 19258798 with the Twitter UserID NUMBER (this is **NOT** the normal Twitter NAME of the user you want the tweet feed from. If you don't know the UserID number, head over to www.idfromuser.com and type in the user's regular Twitter name. The site will return their Twitter UserID number to you. 19258798 is the Twitter UserID for commandlinefu, so if you don't change that, you'll receive commandlinefu tweets, uhm... on the commandline :)
Congratulations! You're done creating all the keys!
Environment variables k1, k2, k3, and k4 now hold the four Twitter keys you will need for your next step.
The variables should really have been named better, e.g. "Consumer_key", but in later commands the 256-character limit forced me to use short, unclear names here. Just remember k stands for "key".
Again, remember, you can always review your requested Twitter keys at dev.twitter.com/apps.
Our command line also creates four additional environment variables that are needed in the oauth process: "once", "ts", "hmac" and "id". "once" is a random number used only once that is part of the oauth procedure. HMAC is the actual key that will be used later for signing the base string. "ts" is a timestamp in the Posix time format. The last variable (id) is the user id number of the Twitter user you want to get feeds from. Note that id is ***NOT*** the twitter name, if you didn't know that, see www.idfromuser.com
If you want to learn more about oauth authentication, visit oauth.net and/or go to dev.twitter.com/apps, click on any of your apps and then click on "Oauth tool"
Now go look at my next command, i.e. step2, to see what happens next to these eight variables.
Share your "now playing" Amarok song in twitter!
Update twitter from commandline, without revealing your password and without having to type it interactively.
You 'll need to put a line "machine twitter.com login TWITTERUSER password TWITTERPASS" in $HOME/.netrc and better chmod 600 that file.
This is the 140 character long new year's countdown timer that was posted to the climagic account on twitter and identi.ca. There are saner ways of doing this of course, but probably none of those would fit. Uses the figlet command, but of course you can replace figlet with just echo if you want.
This version of tweet() doesn't require you to put quotes around the body of your tweet... it also prompts you for password. It will still barf on a '!' character.
Gets the latest Tweets in your friends timeline from Twitter. Uses curl and xmlstarlet.
A command to post a message to Twitter that includes your geo-location and a short URL. The link shortening service is provide by TinyURL, the geo-location service is provided by HostIP and the IP address lookup service is provided by AppSpot. This is an upgrade of an of one of my previous contributions: http://tinyurl.com/yd2xtzv.
Returns a JSON object, by connecting to the 'test' endpoint of the Twitter API. Simplest way to check if you can connect to Twitter. Output also available in XML, use '/help/test.xml' for that
great for outputting tweets from cron jobs and batch scripts
Found it on snipt, pok3, is it yours?
I put my user = m33600, the password and the status was my robot message:
Settima robot message: ALARM ZONE 3 (sent via command line).
Now bots may have their identity on twitter...
Updates your Ping.fm status and websites supported by ping.fm (like twitter, facebook, and google talk).
This will tell you which twitter user you are chronologically. For example, a number of 500 means you were the 500th user to create a twitter account.
Requires Net::Twitter. Just replace the double quoted strings with the appropriate info.
replace username, password, and nameofnewfriend with proper values. Remember to escape things like ! or & in your password