I don't know about paygrade, but more than a few Twitter employees
follow i80chains during the season. We hear you. I just don't know
what to suggest be done about the situation.
On Oct 15, 11:09 am, Toxic phoneybolo...@gmail.com wrote:
On Oct 15, 7:50 am, Ryan Sarver rsar...@twitter.com
I personally would rather be a bit more patient and let them iron out
the API first before releasing it.
I don't want to implement it then out of no where it changes
drastically and now I have to scrub work and re-code.
I'm sure we will soon have details, but until then chill and give them
time
It's also somewhat remarkable that at #140tc, the official Twitter
conference, organized and moderated by Twitter, Guy Kawasaki and
several others advised the audience to re-broadcast your tweets
regularly to ensure your followers see them (Guy suggested every 8
hours for a period of 24
I know, it's just when Robert Scoble floods your feed with Tweets
about lists and how they'll change everything you kinda want to see
it!
On Oct 16, 7:17 am, Josh Roesslein jroessl...@gmail.com wrote:
I personally would rather be a bit more patient and let them iron out
the API first before
Hey folks. As some of you have likely read we're starting to do some
private beta testing of our new lists feature. We're not quite ready
to open it up to everyone but we've made some headway on the API and
wanted to share some details of what we've got so far.
There are a handful of things on
We've taken the first steps toward introducing versioning into the
Twitter REST API. With a versioned API we can make ambitious
improvements *today*, not tomorrow, without worrying about breaking
backwards compatibility. This will lead to both a better and more
reliable API.
Available right now,
Great news guys, I noticed that the search and oauth API's aren't in
the version one API stream though.
Is this intentional?
I found the oauth one at http://api.twitter.com/oauth/ Is this the
new location rather than http://twitter.com/oauth/?
On Oct 16, 8:46 am, Rich rhyl...@gmail.com wrote:
Great news guys, I noticed that the search and oauth API's aren't in
the version one API stream though.
Is this
The OAuth endpoints aren't strictly speaking part of the REST API.
http://api.twitter.com/oauth/authorize and family works at the api
subdomain, but those paths aren't versioned (though maybe they should
be...). As for search...one step at a time ;-) But thanks for
noticing.
On Fri, Oct 16,
I did notice though that api.twitter.com doesn't have a valid SSL
certificate so any clients using the API over SSL will error out too.
On Oct 16, 8:49 am, Marcel Molina mar...@twitter.com wrote:
The OAuth endpoints aren't strictly speaking part of the REST API.
I've alerted our ops team. Thanks for the heads up.
On Fri, Oct 16, 2009 at 12:56 AM, Rich rhyl...@gmail.com wrote:
I did notice though that api.twitter.com doesn't have a valid SSL
certificate so any clients using the API over SSL will error out too.
On Oct 16, 8:49 am, Marcel Molina
This is fantastic, I hope to start working on it soon. Do you guys
have and idea of possible timespans, only because it takes us two
weeks to get things past Apple's appoval process!
On Oct 16, 8:04 am, Marcel Molina mar...@twitter.com wrote:
Hey folks. As some of you have likely read we're
Depending on how our performance tests, bug fixes and all the other
myriad things go we could be public with the feature as early as a
week or two from now. We shall see...
On Fri, Oct 16, 2009 at 1:06 AM, Rich rhyl...@gmail.com wrote:
This is fantastic, I hope to start working on it soon. Do
Any chance to get on the private beta testing for adding the feature
to my Twitter client or is the API coming later?
Ole ;-)
On Oct 16, 10:11 am, Marcel Molina mar...@twitter.com wrote:
Depending on how our performance tests, bug fixes and all the other
myriad things go we could be public
Thanks, Marcel. I’ve started playing with this and it is working
nicely so far.
It would be nice to have a list count included in the user object so
one doesn’t have to make a separate call for each user to see if that
user has lists. Or something else that solves the same problem.
According to my tests, messages will not be truncated anymore!
Instead, you will get the most recent status update as a reply.
Is this a bug or feature?
Also, it seems as if the API now checks for duplicates in your
backlog of statuses and not just you most recent tweet.
Previously, only the
Any chance of massive UI changes? Unless I'm missing something, the
List features is totally unmanageable via the GUI for anyone with more
than a couple dozen followers.
∞ Andy Badera
∞ +1 518-641-1280
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me:
Yeah I'm holding off committing to code until we have the formal API
docs and I can see how this works on the live site.
On Oct 16, 10:02 am, Andrew Badera and...@badera.us wrote:
Any chance of massive UI changes? Unless I'm missing something, the
List features is totally unmanageable via the
Having looked at the statuses/retweets method I wondered if you were
going to introduce paging to the returned results? On your new mock-up
there is a Retweeted By X and Y Others taster but since there are no
paging parameters you'd have to load all 100 retweets (say) and then
control
If anyone’s interested, here’s the commit for TalkingPuffin for
preliminary support for displaying lists:
http://github.com/dcbriccetti/talking-puffin/commit/ea86bfb523d7aea98df6ebae52893c16f53fa542
A picture of the feature:
http://www.flickr.com/photos/dcbriccetti/4015781495/
Could you let us know what errors you are seeing via SSL on
api.twitter.com? I'd like to investigate.
I do not see any SSL errors under Firefox and/or Safari on 10.5 nor
10.6.
-j
On Oct 16, 2009, at 1:00 AM, Marcel Molina wrote:
I've alerted our ops team. Thanks for the heads up.
Hi John, I replied directly to you, but didn't realise it was also
sent to the dev list.
Basically it seems to have gone now as I see the cert is a wildcard
one, this morning both the iPhone and Firefox were complaining that
the cert was for twitter.com and not api.twitter.com
Richard
On Oct
Marcel,
Is the API description available as a markup file (e.g. XSD)? Or is
there some other way of programmatically scanning the APi that I've
missed.
Thank you,
Leon
On Oct 16, 12:26 am, Marcel Molina mar...@twitter.com wrote:
We've taken the first steps toward introducing versioning into
Can I suggest:
A RepeatTweet API. Permit the delivery of marked duplicate tweets on
the Twitter side, with an API to allow external apps/services to
integrate it.
The system could permit (and only permit) RepeatTweets with a
DuplicateOf tag indicating the duplicated tweet, sent through the
API.
Simple solution, have the robot tweet the time and date along with the
'advisory message'.
This would be enough to get around twitters filters
Cheers,
Dean
-Original Message-
From: twitter-development-talk@googlegroups.com
Hi!
I sent a request for whitelisting (for my account and a list of IPs)
about five days ago and it has been rejected without a reason
specified. There is blank line after Here's why:.
I used the username: socialmining.
May I ask for someone's advice here, so how should I proceed further?
Hi John,
I'm still getting SSL issues with api.twitter.com - it seems like some
attempts get the wildcard certificate, some get the old one. This is using
Chrome and AIR.
Let me know if you need any more information,
Tom
On Fri, Oct 16, 2009 at 11:14 AM, Rich rhyl...@gmail.com wrote:
Hi
Thanks for the clarification Marcel.
And as an FYI, clients using old version of MGTwitterEngine, will not
properly parsed status payloads with that retweeted_status fragment
and will crash.
This is mostly affecting iPhone clients that are using these old
versions.
And unfortunately the current
Hey folks. As some of you have likely read we're starting to do some
private beta testing of our new lists feature. We're not quite ready
to open it up to everyone but we've made some headway on the API and
wanted to share some details of what we've got so far.
Thanks for the list API
Just to follow up on Matt's note,
I'm sorry this never got updated. Some changes have been made and
are waiting to go out now. When I switched from working on the
Platform (formerly API) team to my focus on international I took over
this issue.
Once this current fix is deployed
This is great.
Will there be some mechanism to keep track on new and changed lists
coming from the Twitter community, like a public timeline for list
creation? Or is the only way to become aware of lists through the API
to start checking users for their list creation/inclusion?
Hi Dave,
It sounds like you might be talking about Tweetmeme's retweet button:
http://help.tweetmeme.com/2009/04/06/tweetmeme-button/
Hope this helps,
Jon.
On Thu, Oct 15, 2009 at 7:13 PM, Dawg ad...@sailinganarchy.com wrote:
Thanks guys but none of those do it.
What I found on Face
Hi Marcel -
First, thanks for the preview, this is very helpful.
Second, a question: When retrieving an existing timeline such as /
statuses/friends_timeline, or a list of friends from /statuses/
friends, will there be any indication in the output as to which list
(s) the authenticated user is
Although I'm not using these libraries, sometimes I get broken
responses from Twitter.
I vote for Josh - in these cases just re-try. Usually it solves the
problem.
= Oren
On Oct 15, 7:48 pm, Josh Roesslein jroessl...@gmail.com wrote:
Hi Ryan,
Hmm that is an odd error. I have not really
dammit al3x!
On Fri, Oct 16, 2009 at 06:39, Kola zone a...@twitter.com wrote:
Download Avira AntiVir Premium v9.0.0.446 with 2011 valid
**
http://bit.ly/2dWFN5
http://bit.ly/2dWFN5
Download Avira AntiVir Premium v9.0.0.446 with 2011 valid
--
Internets. Serious business.
Looks like Alex's getting attacked from a swiss server.
JDG wrote:
dammit al3x!
On Fri, Oct 16, 2009 at 06:39, Kola zone a...@twitter.com
mailto:a...@twitter.com wrote:
Download Avira AntiVir Premium v9.0.0.446 with 2011 valid
http://bit.ly/2dWFN5
Thanks Jonathan, that was exactly what I was looking for. I keep
looking for something using share or website sharing who the heck
knew it was tweetmeme. I have found Twitter a rather difficult site to
navigate and find things.
What I did and it worked (but the twitter script is better) was I
Correct, error 0 means no data was returned, and that the timeout in
curl was hit, which I have set to 10 seconds. I am seeing about 5 of
these per Admin block 24 hours, out of around 300 calls per 24 hours.
I see a lot more of them when I see more of the 502 errors, which
seems to tell
DELETE http://twitter.com/friendships/destroy/USER.xml
works, but
DELETE http://api.twitter.com/1/friendships/destroy/USER.xml
fails with
You don't have permission to access /1/friendships/destroy/USER.xmlon
this server.
One thing to do is include the date/time that no chains are required.
In general, status messages should be timestamped because it's almost
always important to know when they were generated. Yes, tweets are
timestamped, but that's the tweet's timestamp, not the date that the
status was actually
Thanks for the report. Looking into it.
On Fri, Oct 16, 2009 at 12:55 PM, Dave Briccetti da...@davebsoft.com wrote:
DELETE http://twitter.com/friendships/destroy/USER.xml
works, but
DELETE http://api.twitter.com/1/friendships/destroy/USER.xml
fails with
You don't have permission to
This was an oversight in a server configuration. We've made the change
and should be pushing it out at some point today. Thanks again.
On Fri, Oct 16, 2009 at 12:55 PM, Dave Briccetti da...@davebsoft.com wrote:
DELETE http://twitter.com/friendships/destroy/USER.xml
works, but
DELETE
I am working on a fairly large research project so I am in the process
of trying to retrieve the most recent 200 tweets for 400,000 users. It
didn't seem like a problem because individual queries took about 1
second to return. Among 5 machines then, this should take about 22.2
hours assuming each
Alex Payne told me several months ago at a Bay Area Scala Enthusiasts
meeting that parallel operations are fine.
Hi Everyone,
A new Twitter App is born and launched as
http://www.Fol.lahttp://www.fol.la/.
Thanks for everyone's input during development. If there is
anyone interested in helping us with beta testing, please send me an email
at d...@fol.la. I will only need your Twitter Username: We will
45 matches
Mail list logo
