If other people can read your .bash_history file, your Twyt password is the least of your problems.

Can you save your user and passwd? curl works but not as conveniently and you don\’t have the other features.

@gdelfino

Yes, it\’s not perfect but it gives someone busy an opportunity to tweet from the command line at any moment of the day.

for food in cereal toast \”an orange\”; do
twyt tweet \”It\’s $(date +%R) and now I\’m eating $food. How exciting!\”
sleep 200
done

or:

while read food
do twyt tweet \”It\’s $(date +%R) and now I\’m eating $food. How exciting!\”
done

;-)

I love that and I might steal it for my own evil purposes.

#!/bin/sh
# twitter_splitter – read file(s) or stdin,
# output as tweets of 140 characters or less
user=xyz

fmt -w 140 \”$@\” |
while read line; do
twyt tweet \”$line\” -u \”$user\”
sleep 1
done

If you pipe fmt output through tac (reverse cat), the tweets would come out in reverse order.

@copytodevnull

C

funnily i do use twitter for logging of a number of our processes it tweets time of start and then tweets when it ends so i can keep an eye on them from my phone.

I use an alias in the .bashrc file that call the shell script around curl
alias twitit=\’twitit.sh me secret \’

w/ them as params 1 and 2 everything else is the tweet. It\’s a slightly expanded version of Dave Thomas/Linux Journal\’s script:
#!/bin/bash -x

# created by DaveTaylor linux journal
user=\"$1\"
pass=\"$2\"
shift;
shift;
curl=\"/usr/bin/curl\"
[ -n \"$user\" -a -n \"$pass\" ] || exit

case \"${1-show}\" in
show)
$curl --basic --user \"$user:$pass\" \\
\"http://twitter.com/users/show/$user.json\" \\
| tr \',\' \'\\n\'
echo
;;
see)
$curl --basic --user \"$user:$pass\" \\
\"http://twitter.com/users/show/$2.json\" \\
| tr \',\' \'\\n\'
echo
;;
*)
$curl --basic --user \"$user:$pass\" --data-ascii \\
\"status=echo $@ | tr \' \' \'+\'\” \\
\”http://twitter.com/statuses/update.json\”
;;
esac

exit 0

Clever stuff. We 3 should take over the world!