You are not logged in.
I have been trying different microblogging clients, trying to find the optimum tool: a tradeoff between functionality speed/lightness, and -ideally- open source.
Currently I am using Gwibber, which is pretty good in the latter two stakes, but is still some way behind some of the other apps in terms of functionality. I have heard that the Adobe Air clients, which by and large appear to be the preferred solutions for power users, have some questionable privacy issues.
For the record, I have tried gTwitter, Twitux, Mitter, TweetDeck, Twhirl, and Choqok. I know there are plenty others out there, and would be keen to hear Archers views on what works for them.
Offline
If you use gnome and can stand mono, there's a microblogging plugin for gnome-do --- I see a lot of dents from it on identi.ca.
There are also some very nice packages for emacs: identica-mode and twittering-mode. These are lightweight and gaining a lot of functionality.
For me, the best solution is xmpp with identi.ca. I like it that microblogging takes on the quality of a live conversation with xmpp. Of course, there are a gazillion xmpp clients out there.
Offline
I agree with madalu. Why not just use an xmpp gateway?
if you want to update many sites at once, try ping.fm
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Thanks madalu & cactus. You are both right about XMPP: while Twitter was still supporting it, it was the best solution. Once they turned it off, however...
Ping.fm is good for broadcasting, but doesn't really support conversation - that is why I have been looking at the desktop clients.
I haven't used emacs, but perhaps this is the spur I need to start experimenting.
Last edited by jasonwryan (2009-06-26 10:02:10)
Offline
qwit is my favorite twitter client .
English is not my native language .
Offline
qwit is my favorite twitter client .
+1, best client i could find on linux
He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.
Douglas Adams
Offline
Most complete client for Twitter and identi.ca I've found is Choqok. Sadly, it has some annoying bug and opens a lot of processes called kio_http sucking Ram like whores...
Another great client for Twitter (adaptable for other services) is TTYtter, and great if you use it with Tilda or something similar.
Both are in the AUR.
The Wheel weaves as the Wheel wills, and we are only the thread of the Pattern."
—Moiraine Damodred
Offline
After taking madalu's advice, I have been using Emacs with these two scripts:
1. http://www.emacswiki.org/emacs/TwitteringMode
2. http://blog.nethazard.net/identica-mode-for-emacs/
and I am won over. If only someone would write a script that allows you to publish to both services from the one mode (Gwibber-like functionality).
And apparently Emacs can do some other stuff as well...
Offline
curl rocks
curl -u user:pass -d status="Write your tweet here" http://twitter.com/statuses/update.xml
Too bad I don't understand basic bash scripting yet. How should I modify this, so that I got a script that could be run as a single command taking my tweet text as an argument?
Last edited by ilembitov (2009-06-26 22:07:36)
Offline
Put this in your .bashrc:
tweet(){
curl -u user:pass -d status="$*" http://twitter.com/statuses/update.xml
}
So you could do: tweet blablabla sjfkls sdjfskld sdjfls dfj, and ye. The $* inserts all text that tweet() takes from the command-line.
Offline
Thanks, Themaister
BTW, is it possible to get rid of all that output and substitute it with something like "your tweet has been successfully posted"?
Offline
Put this in your .bashrc:
tweet(){
curl -u user:pass -d status="$*" http://twitter.com/statuses/update.xml
}So you could do: tweet blablabla sjfkls sdjfskld sdjfls dfj, and ye. The $* inserts all text that tweet() takes from the command-line.
very cool thanx
+1 for the output thing also
Archlinux x86_64 | post-engineering | last.fm
Offline
tweet(){
curl -u user:pass -d status="$*" http://twitter.com/statuses/update.xml >>/dev/null
echo "Your tweet has been successfully posted"
}
Offline
Hah, that is pretty cool.
I was using Gwibber but now I just use Twitterfox. Only prob is it always shows the wrong date.
< Daenyth> tomkx: my girlfriend is linux
< Daenyth> srsly
< Daenyth> she loves the way I «make install»
< Daenyth> all her /dev entries are mode 7 for me
Offline
The Laconica wiki has the mother of all client lists:
http://laconi.ca/trac/wiki/Apps
/edit
...and, after testing pretty much all of them, TTYtter works best for me: http://www.floodgap.com/software/ttytter/
Last edited by jasonwryan (2009-08-21 11:00:20)
Offline
Hi, I've been doing some scripting exercise in bash and basically this is what I've come up with: clitter (cli-twitter ).
It's located on github and you can grab it with:
git clone git@github.com:n1ght/clitter.git
If you have any ideas/adjustments/etc just do what you want and let me know so I can check it out
Offline
I'm using identi.ca xmpp gateway also for tweeting (connected accounts)
Offline
nevermind this. found out myself.
Last edited by mimir (2009-09-20 00:47:02)
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." - A. Einstein
Offline
Put this in your .bashrc:
tweet(){
curl -u user:pass -d status="$*" http://twitter.com/statuses/update.xml
}
Okay so I copied this and installed curl to my xubuntu system and sent a test message out which I verified worked correctly, Many thanks to your good self.
Unfortunately my second message wouldn't go through and subsequent attempts to find out what the problem was were unsuccesful.
Here is my (only slightly) modified code
dent(){
curl -u user:pass -d status="$*" http://identi.ca/api/statuses/update.xml >>/dev/null
echo "Your dent has been successfully posted"
}
As you can see the changes I've made shouldn't be causing a problem. The dent that went through correctly was "dent testing a shell script" the following one that wouldn't go through was "dent Awesome!! I LOVE linux it's the shit!!! #linux #curl #identica"
While testing I found another flaw I sent a "dent test msg 1!" which sent properly then I sent "dent test msg 2!!" and it did send but like so "dent test msg 2dent test msg 1!" From this I take it that the script/shell is interpreting the ! as a command character and not as plain text.
If I send "dent test msg 3/1" it sends correctly but I have a slash included in the message then when I send "dent test msg 4/!" it again sends correctly and without appending the first message to the second alas I still have the unwanted slash in my message.
Any help you can offer would be appreciated greatly btw I hope I have done a good job explaining this and not made any silly errors I've never done scripting before and as such know very little.
Regards
Becker
Offline
Here are ever so slightly improved versions which tell you if something failed with the curl command.
Cheers
Barde
tweet(){
curl -u user:pass -d status="$*" http://twitter.com/statuses/update.xml >/dev/null && echo "Your tweet has been successfully posted" || echo "Fail!"
}
dent(){
curl -u user:pass -d status="$*" http://identi.ca/api/statuses/update.xml >/dev/null && echo "Your dent has been successfully posted" || echo "Fail!"
}
Offline
@becker_11 - the problem is that you have special shell characters like "!" and "#". Try doing:
$ dent "Awesome!! I LOVE linux it's the shit!!! #linux #curl #identica"
Ie, note the quotes that wrap the status string.
Offline
Gottcha! As I read your reply I was going to whinge that those characters (well at least the #) are integral to the way it works but then I finished reading and everything makes sense.
I think the / trick I was trying was something I read in either Perl or regex many moons ago about telling the shell to treat the following character as text, it never occurred to me to try the quotes ..... Thanks!!
p.s. It never occurred to me before I started nutting this out but I do seem to use alot of exclamation marks :-)
Offline
I have a few of ways. There's TTYtter, tircd/irssi (or some irc client), and I have my own tweet function:
function tweet
{
USERNAME="myuser"
PASSWORD="mypass"
if [ -z "$1" ]
then
echo "No status update entered. Showing last twenty updates:"
curl --basic --silent --user $USERNAME:$PASSWORD --get http://twitter.com/statuses/friends_timeline.xml | sed --quiet --expression='s/<name>\(.*\)<\/name>/\1/p' --expression='s/<text>\(.*\)<\/text>/\1/p'
exit
elif [ $(($(echo "$1" | wc -m)-1)) -gt 140 ]
then
echo "Tweet too long ($(($(echo "$1" | wc -m)-1)))"
exit
else
curl -s -u $USERNAME:$PASSWORD http://twitter.com/statuses/update.xml -d status="$1" > /dev/null
echo Status updated.
fi
}
Oops, meant for this post to be in another thread... http://bbs.archlinux.org/viewtopic.php? … 01#p738901
Last edited by Berticus (2010-04-07 13:03:36)
Offline
Since I last posted on this I have found Twidge which can be used for either twitter or identica and it's pretty good. My main complaint with these cli based apps is there is no remaining character count as your typing. When I use the web interface I find the count invaluable for knowing when I have to optimise my message to fit everything in
Offline
Since I last posted on this I have found Twidge which can be used for either twitter or identica and it's pretty good. My main complaint with these cli based apps is there is no remaining character count as your typing. When I use the web interface I find the count invaluable for knowing when I have to optimise my message to fit everything in
That's why I have a count performed in my tweet function. It's not real time and only occurs after submission, but it works.
Offline