On Thursday, July 7, 2011 12:45:05 AM UTC+1, themattharris wrote:
This should now be fixed. Let us know if you find it isn't.
Yep - confirmed as fixed for me ... many thanks guys !
--
T
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter:
I've been happily pulling back a user's lists with a query like
http://api.twitter.com/1/lists.json?callback=abcscreen_name=schmerg
but suddenly (sometime in the last 24 hours I suspect) this is returning
pure json, not jsonp.. that is
{lists:[], next_cursor:0, previous_cursor:0,
Glad it's not just me then !
Here's an entire curl request with headers in case that gives any clues (eg
if it's particular hosts behind a load balancer)
Cheers
--
Tim
curl -v
http://api.twitter.com/1/lists.json?callback=abcscreen_name=schmerg;
* About to connect() to api.twitter.com port
On Friday, July 1, 2011 7:54:00 PM UTC+1, Taylor Singletary wrote:
Thanks everyone, I'll report this to the team -- not quite sure what's
happening.
Just to set expectations, I also don't have an ETA on a fix.
Thanks - ETA not required, just one of things where filing a bug report is
Thanks Matt, filed as a feature request rather than a defect
http://code.google.com/p/twitter-api/issues/detail?id=2250
--
T
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
On Saturday, June 11, 2011 1:23:47 PM UTC+1, Adam Green wrote:
I believe that at least part of Twitter's motivation is based on
protecting users from spam and viruses. In that case, why not
implement some purging alogrithms? Here's an easy one. If an account
follows nobody and only sends
He was maybe thinking of a response to a similar question on another thread.
The way the tweet and follow buttons are done has changed. If you want to
create a button after widgets.js has been loaded (any sort of dynamic use),
then you're supposed to do this by adding an iframe with appropriate
While looking at localStorage in the browser, I noticed that when I connect
with @anywhere various details are written to localStorage for my page
including
twitter_anywhere_cache_[account/verify_credentials,[]]_expiry:
1307546741323
twttr_anywhere_expiry: 1307552140184
which if
The point of t.co, as I understand it, is twitter's very different dynamic
with regards to spam.
Consider a scenario: someone creates a new account, sends one message with
@mentions of 5 high profile people, almost no text, but an http ref (perhaps
wrapped behind a shortener, maybe not).
In
Apologies to the forum if this is considered bad form but there are sources
other than the Twitter API to find out who follows who on Twitter, so you
could search for the tweets using the Twitter API, assemble a list of users,
and then call another service to find out who follows who. You're
Personally I read the full source to see what's going on, and then figure
out how to work around bits of it, so for example I might see when the
header title is set and the selectors used, and then use its own routines to
modify them (eg hdr = widget.byClass(twtr-hd, div) and then manipulate
If the standard widget code (http://twitter.com/widgets) is what you're
looking at then I should point out
* Author: Dustin Diaz (dus...@twitter.com)
* For full documented source see
http://twitter.com/javascripts/widgets/widget.js
* Hosting and modifications of the original source IS
I think you can only really rely on IDs having different values.
In general, at the moment with Twitter, you could assume they increase over
time, but (and I don't work for Twitter) typically ID allocation on large
multihost systems don't work by allocating strictly sequential IDs without
I'm pretty sure all tweet IDs are in a single global ordering, so 1 week
ago is the same numerical ID (for the since_id) param for every user
account.
So you could post a single tweet (or similar) every day and use this to
build a date to ID mapping over time... then you'll know an ID to use
The users/show API includes a statuses_count field which tells you how
many tweets the user has posted
http://dev.twitter.com/doc/get/users/show
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
On Monday, April 4, 2011 2:19:38 AM UTC+1, Jeff Tucker wrote:
Unfortunately (I can't believe that I'm writing this) I am having a
hard time getting spammers to actually spam me. Is there any way that
I can somehow get access to the tweets of several dozen spam accounts
(prior to when
If you pull the full documented source for the rather excellent twitter
widgets (http://twitter.com/widgets), you'll find exactly the routine to do
this.
/**
* relative time calculator
* @param {string} twitter date string returned from Twitter API
* @return {string}
The twitter widget used to call the old address, but a new version was
posted a couple of days ago (without incrementing the version number in the
comment at the top) that construct URLs of the 2nd form... guess they
standardised this and I'm pretty sure it changed over only in the last week
18 matches
Mail list logo
