Bad idea.
1) reduces the credibility and thereby the value of the results in
twitter search
2) who determines which is popular- no matter how you try to calculate
this, someone will figure it out and spam the results.
3) people are used to searching twitter for breaking news, rather than
The API description says that authentication is supposed to be
required, but it is not. I don't know if this is a typo or if
something is wrong, but you don't have to be authenticated to get the
updates of a twitter list by ATOM (or any other format, for that
matter).
Not that I'm complaining:
Keep on fighting the good fight! We're doing what we can.
We're rooting for you- not because it benefits us but because of the
in justice against you.
count me in too. my web host shut me down because I was puttting too
much demand on the CPU. Now I've got to start making money from my
app!
On Jul 3, 8:00 am, João Pereira joaomiguel.pere...@gmail.com wrote:
I'm also interested in discuss these things. let me now if you find
something.
On
What do you mean by replication lag? Is this related to repeated
tweets in the search results?
I am migrating my app from rss to atom and realized something- a
problem I thought was limited to rss occurs with atom as well.
Here's the problem: sometimes, even within a matter of minutes, a feed
loses the latest item and then gets it back. This is supremely
annoying. I thought switching to
From my reading of the documentation, the best way to read DMs is by
email.
The direct messages come to you as an email with a particular header
that you can identify and parse.
I have been working with emails (not as direct messages, but when I
get a new follower) and I'd have to recommend
whenever I try to send an update or direct message everything just
works fine and dandy but when I begin the update directed @any_user I
simply get no reply from Twitter- no error, no nothing.
This is true whether or not I send a direct message or a update
status.
Is this an encoding issue? I
