I'm just a computer scientist who happens to have a tumblr. I'm specially interested in artificial intelligence and research, atually I'm a PhD student, so the posts will probably be related with these circumstances.
jmora
March 1, 2010
Twitting constantly

I’ve been using internet for a while now, and I’ve probably spent a lot of time reading and writing, which may not be a good thing, n00bs!!one! Last summer, due to several complex interactions that will probably remain unknown for me, as I haven’t any intention to pay a psychologist to find out them, I decided to use the web 2.0 in a slightly different way, this blog was born and also my twitter account in the way it exists now.

Since then, a lot of activities that I may carry out in the web had a tweet associated, there are very few things that I like more than automation, and thus the tweets were primarily automated using twitter feed. But something more could be done in that respect.

I decided to join all the sources for twitter feed, and add some additional sources that were posting directly to twitter using yahoo pipes, this would allow to keep a constant flow of tweets, which would not be so dependent on my activity, which is more uneven. Probably it isn’t relevant in any aspect, but it looked like a good idea at that time. @replies are not included in this counting, in case there is any or you are wondering.

The problem is that it is extremely hard for yahoo pipes to handle tags properly for the services that have them (the label “category” in rss), actually it is impossible, it won’t handle lists, there are workarounds that could be satisfactory, but then twitter feed won’t be able to manage the output unless a web service is deployed to build a workaround to manage tags. Long story short, if I have to develop so much (something I may do but not in a foreseeable future) then I’ll probably forget about both solutions, yahoo pipes and twitter feed, and do something on my own. By now, there are no tags and that’s it. There will also be some posts that may be repeated in the beginning, but in the long term it will be fixed, I’m just explaining this for historical reasons, because I don’t even know if someone will read it now or will ever care about any of these things.

In any case, I’m considering the setup of this little fix as finished, it has been the first pipe I do in a slightly serious way and it is going to be the last one. It’s great to have computational resources as you have with pipes completely at your disposal and with an up-time that, I don’t know how good may be, but is there even if you do nothing about it. But the experience of the constant workaround to get something similar to the initial intention is very frustrating.

From now on, the frequency in the tweets should be constant.

Comments
blog comments powered by Disqus