And this is Identi.ca, Twitter, and posting between the two, written , and concerning Web, Sundry Hacks
Comments
Surely moving to another single-point service is missing the point?
Phil: that's what the OpenMicroBlogging stuff is about. If Twitter and Jaiku and Plurk and everyone else implemented that then there would be no single-point services. Until they do, it's *all* single-point.
[...] has been a lot of discussion lately about micro blogging and the many problems associated with twitter. Something [...]
Ah yes, "This is a great idea which is rather hampered by the fact that basically no-one has implemented it yet." ;)
Phil: yep. It's like being the first dude with a telephone. But _someone_ has to be the first dide with a telephone, which is why I'm at identi.ca :)
I don't quite get why they don't use xmpp.
server-2-server : check
pub-sub : check
encryption : check
opensource : check
internet standard : check
huge client base : check
now. someone enlighten me please.
Alex - I agree, federated XMPP pubsub is a "better" solution, but let's face it, any old schmo with web hosting can run a PHP app, whereas far fewer people have the opportunity to run an XMPP server. This is important.
Any old schmoo with webhosting won't have a traffic limitation (processor time) that's interesting for a microblogging infrastructure though. The people having their own server are far more interesting - and they should be able to setup a xmpp server.
They might be more interesting, but surely that's not the point? As far as I can see it, laconica is a way out of being locked into a single microblogging service ever again, not a way to be locked into a smaller service on the server of someone you might know. If you're only federating with your contacts then your requirements scale up with the size of your personal network, which seems reasonable to me, and should happily deal with a grouping of around Dunbar-proportions.
I certainly won't be signing up on identi.ca, although in a few months' time (when federation works as advertised) I will probably set up my own laconica install. I'm not daft enough to move off twitter just for lock-in somewhere else.
You don't have to use Jabber to post to identi.ca! You could do this using a very simple python script.
An example can be found here http://pastebin.com/f78360ff8
saperduper: does this "simple" Python script handle OpenID, which is how I log into identi.ca? Using documented APIs rather than screen-scraping is the way to do it...
[...] OAuth isn’t the answer here. My use-case for this is, say, a little script that allows me to post to Identi.ca. OAuth requires me (the “Consumer”) to request a “Consumer Secret” and a [...]
[...] have thus far failed to get Aq’s reflector working so find me on which ever suits you most and take your chances. I am really interested to [...]
[...] http://yennygirl.com/?p=2012 - bookmarked by 6 members originally found by vraius on 2008-08-05 Comment on Identi.ca, Twitter, and posting between the two by alex http://www.kryogenix.org/days/2008/07/03/identica-twitter-and-posting-between-the-two - bookmarked [...]
I'm now using Twitterfeed for this, because it can now post to Identi.ca. So, subscribe to your Twitter page's RSS feed and post it to Identi.ca and it all works. Well done Twitterfeed.
[...] while back I wrote a reflector which sent posts from Twitter to Identi.ca if you want to post to both. However, that required [...]
[...] Identi.ca could, theoretically, be the bridge to get all of these different platforms working together through the OpenMicroBlogging project, but there is one big pitfall preventing this, even more than the logistical challenges of getting platforms to communicate. It’s getting people to do the same. As Stuart Langridge said last year: [...]
If you're running this script on Linux, you need to add the she-bang at the top of the .py file:
#!/usr/bin/python
Or you'll just get this error:
./twitter-identica.py: line 1: import: command not found
./twitter-identica.py: line 3: syntax error near unexpected token `('
./twitter-identica.py: line 3: `config = ConfigParser.ConfigParser()'
[...] it’s all the [...]