I agree. I use multiple clients throughout the day and the ability to
know where I left off is a huge plus so that I don't have to
"memorize" what the last tweet I read was (especially if its been a
while). Although it would be a bit difficult and can turn into a
nightmare for the website. For exa
Very cool! I will definitely watch this project as it develops!
On Aug 25, 7:50 am, x5315 wrote:
> Have you ever seen your favourite celebrity ask a question, and you
> were wondering about the answer too? Or have you ever been taking part
> in a competition and been wondering who else was enter
I was starting to worry that something was wrong with Twobile (basic
auth). Any news from the mothership on what's happening?
On Aug 17, 10:42 am, Aaron Forgue wrote:
> My app, too, appears to be blocked. I can't even get status codes -
> the requests just timeout with no response.
>
> On Aug 17
I agree with janole. I believe the simple "Reply" concept would be
best in this regard. For example, if I had a tweet that I found,
regardless of who its from, I can retweet it, but link together the
original tweet in the same manner that we do for the replies. Thus, we
create a chain of where a r
Thank you for providing the saved searches API, but I do have a bit of
a question. I haven't yet played with it, but I am wondering about the
use of location-based searching in the saved search APIs. If this can
still be performed, is it like the query performed on
search.twitter.com's advanced se
I'd love to be mentioned! Count me in too!
Username: @twobile
URL: http://www.infinitumsoftware.com/twobile
Email: spa...@infinitumsoftware.com
Author of Twobile
Technology: C# on Windows Mobile devices
Thanks!
On Feb 23, 11:33 am, Alex Payne wrote:
> There isn't one that I'm aware of, but if
OTECTED]> wrote:
> > Confirming that I can replicate this issue. We'll clear it up.
>
> > On Tue, Oct 7, 2008 at 12:55 PM, Sean P. <[EMAIL PROTECTED]> wrote:
>
> >> As of the time of this writing, calling /statuses/public_timeline.xml
> >> doesn'
As of the time of this writing, calling /statuses/public_timeline.xml
doesn't appear to be returning any results (though it has an HTTP 200
OK). Anyone else know what's going on (haven't seen anything posted
yet on status.twitter.com)?
