On 4 Mar, 14:25, TjL wrote:
> There *should* be a way to start a "conversation chain" without
> setting an in-reply-to being added where it doesn't belong. That's
> where it makes sense that you would type in @NAME by hand.
>
> Twitter shouldn't be held hostage to "the way it used to be" for a
>
Thanks for the speedy response Matt. Much appreciated.
On Mar 5, 10:49 am, Matt Sanford wrote:
> Hi all,
>
> This is related to the login error
> (http://status.twitter.com/post/83602310/problems-logging-in
> ) and people are working on it.
>
> Thanks;
> — Matt Sanford
>
> On Mar 4, 200
We have already implmented Tweetmeme's API in our test site and will pish it
live on Friday. Good job Nick.
Thanks in advance
Sam
www.twitblogs.com/ssethi
This email is: [ ] bloggable [ ] twittable [ ] ask first [X] private
Sent from: Poplar Eng United Kingdom.
2009/3/4 Nick Halstead
https:/
Hi all,
This is related to the login error (http://status.twitter.com/post/83602310/problems-logging-in
) and people are working on it.
Thanks;
— Matt Sanford
On Mar 4, 2009, at 03:32 PM, dean.j.robinson wrote:
For example:
https://twitter.com/oauth/authorize?oauth_token=OMxcOPndHoO
I think something is wrong w/ https in general. I cannot post an
update. I'm getting back 404's for
https://twitter.com/statuses/update.json
https://twitter.com/statuses/update.xml
etc..
switching to normal http works fine. something is amiss...
curl dump:
$ curl -v -u :x -d status=te
For example:
https://twitter.com/oauth/authorize?oauth_token=OMxcOPndHoO57JMFURt8GyzKpnREj9oKf6aG6f3pU
that url doesn't work (returns stanard twitter page not found), but
this one does
http://twitter.com/oauth/authorize?oauth_token=OMxcOPndHoO57JMFURt8GyzKpnREj9oKf6aG6f3pU
This doesn't always
On Mar 4, 1:52 pm, Nicole Simon wrote:
> I would assume that they do use a simple OR.
Sure, but an OR of what?
On Wed, Mar 4, 2009 at 4:38 PM, atebits wrote:
> 1. If a client is making users jump through hoops to reply to a
> specific tweet, the client is doing it wrong.
[snip]
> The end of auto-linking was a fantastic change for two reasons: 1. it
> keeps everything simple (no new settings or flags or
O.k no worries - that makes sense. Thanks Matt
On Mar 3, 1:49 pm, Matt Sanford wrote:
> Hi Chris,
>
> I just checked your example and it looks like the third entry
> (http://twitter.com/dailythomas/statuses/1266693521
> ) has what you expect. Perhaps the issue is that most people using
>
I would assume that they do use a simple OR.
Nicole
--
Jetzt im Buchhandel:
"Twitter - Mit 140 Zeichen zum Web 2.0"
Amazon: http://tinyurl.com/6at9c5
http://mit140zeichen.de - http://twitter.com/m140z
Kontakt:
http://twitter.com/NicoleSimon
https://www.xing.com/profile/Nicole_Simon
skype: nic
Hey Twitter folks
I *love* that you guys index messages by smiley vs. frowny emoticons! It
looks like you normalize a wide range of "happy" and "sad" emoticons
together. I'm doing some searches in [[ :) ]] and trying to then identify
what the original smiley in the message was and it's a little t
I don't have much time to debate this, but two points:
1. If a client is making users jump through hoops to reply to a
specific tweet, the client is doing it wrong. Twitter.com does an
excellent job making it easy, as do the vast majority of iPhone
clients.
2. Adding another setting to control
Nick Halstead wrote:
Today we launched an API for tweetmeme, for those who havent tried it,
we aggregate all the twitter URL's to rank the most popular stories.
Well the upside of this is that we have massive database of all the
short URL's - and where they resolve to, included in this we also g
On Wed, Mar 4, 2009 at 12:38 PM, Nick Halstead wrote:
>
>
> We have tried to stick very closely to the RESTful + twitter style
> API
>
> The documentation is here -> http://www.tweetmeme.com/apidoc.php
>
> An example of the url fetcher ->
> http://api.tweetmeme.com/url_info?url=http://is.gd/lznv
>
Today we launched an API for tweetmeme, for those who havent tried it,
we aggregate all the twitter URL's to rank the most popular stories.
Well the upside of this is that we have massive database of all the
short URL's - and where they resolve to, included in this we also go
and grab the page tha
Protocol Buffers is yet another RPC scheme that requires compilation of the
data types. If on the other hand you define simple data types this can be
much simpler and finessed, and including dealing with such RPC issues as
endian-ness. wondering if is there any sort of compression of XML that
Back and forth with atebits over e-mail:
>>I, personally, found the false positives much more acceptable than the
>>current situation where you have to hunt for originating tweets for "false
>>negatives".
>Doing anything interesting like automatically crawling conversation
>webs is flat out impo
Thanks ... yes this is an important API to keep things clean, and
prevent us from driving traffic to dead twitter pages ...
On Mar 4, 9:19 am, TjL wrote:
> We had a conversation about this about a week ago which led to a
> feature request you may want to 'star':
>
> http://code.google.com/p/twi
If you don't want to limit it to only your friends you could just
search for #bh and do what you will with the results... unless there
is a conflicting #bh tag being used for something else?
-Chad
On Wed, Mar 4, 2009 at 9:49 AM, Nial wrote:
>
> Over at http://birdhive.net, we track our friend t
Adrian,
There is an issue that was just opened for this:
http://code.google.com/p/twitter-api/issues/detail?id=323
As always, star to show your priority.
Thanks,
Doug
@dougw
On Wed, Mar 4, 2009 at 7:12 AM, Adrian wrote:
>
> field:
>
> in_reply_to_screen_name
>
> exists for statuses
>
> /statu
2009/3/4 Nial
>
> Over at http://birdhive.net, we track our friend timeline to find
> people who have marked tweets with the #bh hashtag. Until very
> recently, I thought that passing the optional since parameter in my
> request would return all tweets in that timespan. It was only recently
> tha
There is currently no callback, subscription or push pattern available for
API methods.
Thanks,
Doug
@dougw
On Wed, Mar 4, 2009 at 10:26 AM, kprobe wrote:
>
> I've seen the doc on the "replies" API method in the documentation.
> Is there a way to capture a reply automatically in order to proces
2009/3/4 kprobe
>
> I've seen the doc on the "replies" API method in the documentation.
> Is there a way to capture a reply automatically in order to process it
> in real-time?
> Perhaps a callback.
Look at www.gnip.com.
-Stuart
--
http://stut.net/
Jeff,
In my tests, the request was successfully set, and my protected test user
was notified of a pending friend request.
Regards,
Doug
@dougw
On Wed, Mar 4, 2009 at 11:12 AM, Jeff Bishop wrote:
> Doug,
>
> Thank you. One question though. If I try to follow someone that is
> protected will t
I'll log your message here as an issue and see what I can do. And as
far as WebException is concerned, you can just cast its Response
property to HttpWebResponse rather than go digging in the header.
That's exactly what I do to retrieve the root's Response object. So
that means you can just cast t
hehe,
I discovered that last night too :)
Paul.
2009/3/4 Dimebrain
>
> Thanks Paul,
>
> I'll log your message here as an issue and see what I can do. And as
> far as WebException is concerned,
> you can just cast its Response property to HttpWebResponse rather than
> go digging in the header.
Thanks Paul,
I'll log your message here as an issue and see what I can do. And as
far as WebException is concerned,
you can just cast its Response property to HttpWebResponse rather than
go digging in the header. That's exactly what I do to retrieve the
root's Response object. So that means you c
We had a conversation about this about a week ago which led to a
feature request you may want to 'star':
http://code.google.com/p/twitter-api/issues/detail?id=311
I'm curious ... is there a feed that we can subscribe to that would
indicate accounts that have been suspended or deleted?
I'm working to cache as much data as possible on our new site -
http://www.TopFollowFriday.com - and obviously as the spammers show up
in the search feed we cache their accou
Doug,
Thank you. One question though. If I try to follow someone that is protected
will the Twitter API go ahead and submit the request without a problem or do I
need to do something different? I understand I could check the protected node
for its value to determine if the user was a protect
Nope its just running in a safari browser adn it works great.
Im using this javascript function for Base64
http://www.webtoolkit.info/javascript-base64.html.
here is the full code again:
function setTwitterStatus(twitterStatus){
var twitterStatus = 'status='+twitterStatus;
var req = new
field:
in_reply_to_screen_name
exists for statuses
/statuses/friends/USERNAME.xml
but in
/statuses/friends/USERNAME.json
it does not.
thank you.
Over at http://birdhive.net, we track our friend timeline to find
people who have marked tweets with the #bh hashtag. Until very
recently, I thought that passing the optional since parameter in my
request would return all tweets in that timespan. It was only recently
that I realised it just return
I've seen the doc on the "replies" API method in the documentation.
Is there a way to capture a reply automatically in order to process it
in real-time?
Perhaps a callback.
Jeff,
The friendship methods will allow you to create and destroy friendships on
the behalf of authenticated users. Their usage is explained at [1]. These
methods allow you to "follow" and "unfollow" users. Notification methods are
not necessary unless you would like to enable/disable device notifi
Hello,
I am developing a Twitter client titled WETweet. The purpose of this client is
to provide blind users using the Window-Eyes screen reader a better and more
rich experience using Twitter.
I had a question about automating the creation of friend relationships and
following and un-followi
Hi all,
Introducing http://TwitterAnalyzer.com, the world's most extensive
"Twitter User Analyzer" app.
After investing a lot of time and money, Twitter Analyzer is ready to
be introduced to Twitter's development community...
Twitter Analyzer is analyzing Twitter users with over 50 analyzing
stati
37 matches
Mail list logo