+1 for Dewald getting his own session at Chirp! ;) (Seriously!)
On Apr 10, 2:49 pm, Dewald Pretorius wrote:
> Maybe it's because I'm of the older generation, have been there and
> done that, and have discovered that the top looks so green because of
> all the crap that lies and flies there, tha
Many of our users are complaining that recently, using our app, they
are getting bizarre "Account update failed: pending email is invalid"
errors when trying to change profile info on Twitter (location, full
name, bio).
I see that this is a known issue -- http://bit.ly/bFs79q (not sure if
there i
Might I suggest that since you now have email contact with Twitter,
that you cease copying ALL of your correspondence with them to this
group?
On Feb 16, 1:53 pm, Jim Fulford wrote:
> Brian,
> I have made the requested changes to my application, but the support
> ticket has been closed and is no
ng your users a PHP proxy pass-thru script that they can
> > upload to their servers, and there is no way that Twitter can even
> > identify the offending app, let alone suspend/ban/blackhole it.
>
> > On Feb 16, 12:28 pm, PJB wrote:
> > > Presumably to do the OAuth v
mean. It will be great to know what is the Twitter
> approved way of providing vanity plates. It is obviously a feature
> that will rock, if we can get a level playing field by that rule being
> made public to all of us.
>
> On Feb 16, 11:04 am, PJB wrote:
>
> > Van
y and fear in the developer community. The only
> thing you accomplish is creating a bigger nightmare for yourself.
>
> On Feb 15, 9:51 pm, PJB wrote:
>
> > Yep, that should have been implicit in my post.
>
> > Anti-spam actions should be chiefly aimed at abusive users, rather
Feb 15, 5:24 pm, Dewald Pretorius wrote:
> Well PJB, there is always a completely different approach that Twitter
> could take.
>
> They could bolster their internal coding and defenses against what
> they consider to be abuse, much like they did for duplicate content,
> and then
Frankly, I sort of hope that Twitter DOESN'T further define their
nebulous rules. Why? Because when they do, the axe often falls on
legitimate app developers (rather than abusive users or problem apps)
in really short-sighted ways. Moreover, their rules are usually
blanket pronouncements withou
972/weve-been-suspended-by-twitter
>
>
>
> On Mon, Feb 15, 2010 at 10:34, PJB wrote:
>
> > Wow. What's really of concern is the capricious approach Twitter
> > seems to have with app developers. Some apps are given a month to
> > make a change, some are c
or, because then it is a fence and not a broad gray
> > smudge.
>
> > Most app developers are _not_ "the enemy" and most app developers will
> > be more than happy to not develop or to disable features that violate
> > the rules.
>
> > If only we can unde
+1 to what Dewald says.
We are purposely NOT developing certain features for fear that Twitter
may suddenly change their rules once again. Is this the sort of
business environment that Twitter wishes to foster?
We had assumed that, at the very least, applications would be
contacted before any s
ehttp://twitter.com/account/redirect_by_id?id=92595586
>
> Other then an account here and there, from what was probably a bug in the
> validation code, there should be no accounts being created with such
> characters.
>
>
>
> Abraham
>
>
>
> On Wed, Feb 3, 2010 at 1
Hm, wait... this account was created in Nov 2009 and has spaces and a
\n in his screen_name??
http://twitter.com/users/show.xml?user_id=92595586
On Feb 3, 4:59 pm, PJB wrote:
> Just FYI, Twitter screen names are not (or, apparently, didn't use to
> be) restricted to 0-9A-Z-_
Just FYI, Twitter screen names are not (or, apparently, didn't use to
be) restricted to 0-9A-Z-_
6295462
Magic carpet1
3939231
Walking the dog2
92595586
Its mine\nM2
We're also seeing non-ASCII in some other screen names. (Though we
don't currently know what they are... we just know they exis
Right now, the "ad" in the sidebar on the right-hand side of
Twitter.com is invariably: i) a micro, community, or feel-good sort of
app, ii) a mega-app that most people already know about, that has VC,
connections to Twitter folks directly, or a good PR firm.
This leaves many non-Bay Area (or med
Your question is not germane to the topic at hand. Nor, for that
matter, is it germane to this discussion group at all.
On Jan 15, 12:21 am, BrandonUSA wrote:
> Is there a service to remove all the people you are following at once?
Woo hoo... something must have changed... for at least the past 24
hours, I am noticing incredible performance from API calls. Seems to
be at least 40% faster than earlier in the week.
Can we please get some confirmation that the cursor-less calls won't
be going away this coming Monday?
On Dec 22 2009, 4:13 pm, Wilhelm Bierbaum wrote:
> We noticed that some clients are still calling social graph methods
> without cursor parameters. We wanted to take time to make sure that
> pe
at the
> implementing code on our end. A curl timing would be nice (time curl
> URL > /dev/null) too.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Services, Twitter Inc.
>
> On Mon, Jan 4, 2010 at 9:18 PM, PJB wrote:
>
> > On Jan 4, 8:58 pm, John Kalucki wrote:
> >
retrieval of 40,000
> followers in two seconds. I'd be very interested in looking at the
> implementing code on our end. A curl timing would be nice (time curl
> URL > /dev/null) too.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Services, Twitter Inc.
>
> On Mon, Jan
On Jan 4, 8:58 pm, John Kalucki wrote:
> at the moment). So, it seems that we're returning the data over home
> DSL at between 2,500 and 4,000 ids per second, which seems like a
> perfectly reasonable rate and variance.
It's certainly not reasonable to expect it to take 10+ seconds to get
25,00
sor: 9.5
cursorless: 3
60,000 to 80,000 ids
cursor: 12.25
cursorless: 3.12
On Jan 4, 7:58 pm, Jesse Stay wrote:
> Ditto PJB :-)
>
> On Mon, Jan 4, 2010 at 8:12 PM, PJB wrote:
>
> > I think that's like asking someone: why do you eat food? But don't say
> > be
I think that's like asking someone: why do you eat food? But don't say
because it tastes good or nourishes you, because we already know
that! ;)
You guys presumably set the 5000 ids per cursor limit by analyzing
your user base and noting that one could still obtain the social graph
for the vast m
Why hasn't this been announced before? Why does the API suggest
something totally different? At the very least, can you please hold
off on deprecation of this until 2/11/2010? This is a new API change.
On Dec 23, 7:45 pm, Raffi Krikorian wrote:
> yes - if you do not pass in cursors, then the
API documentation page says: "If the cursor parameter is not
provided, all IDs are attempted to be returned, but large sets of IDs
will likely fail with timeout errors."
There was no reference in any of the previous announcements to
deprecating this valuable ability. Is it now also doomed for t
Willhelm:
Your announcement is apparently expanding the changeover from page to
cursor in new, unannounced ways??
The API documentation page says: "If the cursor parameter is not
provided, all IDs are attempted to be returned, but large sets of IDs
will likely fail with timeout errors."
Yesterd
On Oct 21, 11:28 pm, Nigel Cannings
wrote:
> Hope that is a better explanation, and might I say on behalf of all
> the Perl hackers on the list, keep the good work up!
Hear hear! Net::Twitter is a brilliant and easy-to-use Perl interface
to Twitter.
moths are eating up
significant API resources.
On Oct 21, 9:54 pm, PJB wrote:
> From my testing, SOME api calls go through just fine (e.g., grabbing
> DMs). OTHERS are particularly slow (e.g., create friend).
>
> From the rumours I have heard, Twitter is delegating performance to
>
>From my testing, SOME api calls go through just fine (e.g., grabbing
DMs). OTHERS are particularly slow (e.g., create friend).
>From the rumours I have heard, Twitter is delegating performance to
more "benign" calls, and degrading performance for other calls more
closely associated with "spam"
be treated as such. I personally detest all those stupid
> > twitter-based games. Point is, with Twitter's userbase, some get through the
> > cracks. Don't like it, report it. This is like complaining that cops only
> > pull over SOME speeders. Yeah, some are going to ge
PB
On Oct 13, 12:47 pm, Chad Etzel wrote:
> On Tue, Oct 13, 2009 at 3:38 PM, PJB wrote:
>
> > Wrong. Basic Authentication will obviously ALWAYS be an option for
> > desktop clients, regardless of whether or not it is via API.
>
> Please explain this statement?
> -Ch
> For the sake of argument, let's take this at face value as true. How
> about the search pollution issue with recurrent tweets in general?
You may have a point. But it comes down to uneven enforcement.
Twitter smacks down an app because they allow an individual to recur,
say, every Monday: "T
> > You clearly do not understand the basics of HTTP. Do you think that
> > Twitter is going to somehow deny Firefox, IE, and other desktop
> > clients from connecting to Twitter with a simple username and password
> > only?
>
> Since when do Firefox and IE use the API to communicate with Twitt
On Oct 13, 12:48 pm, JDG wrote:
> > Wrong. Basic Authentication will obviously ALWAYS be an option for
> > desktop clients, regardless of whether or not it is via API.
>
> Explain to me where it's obvious that basic auth will ALWAYS be an option
> for desktop clients. Furthermore, please expla
> If the desktop client uses OAuth (which, if and when they deprecate basic
> auth, will be all), you bet your ass they can regulate desktop clients. All
> they have to do is ban any tweets using the Consumer Secret and Key for that
> app (and any subsequent keys said jackass developer attempts t
http://search.cpan.org/dist/Net-Twitter/lib/Net/Twitter.pod
On Oct 13, 3:33 am, apfelmaennchen
wrote:
> I really find it difficult to understand documentation how to code a
> TWITTER-API in perl. But with a bit "start-help", I think I'll be able
> to proceed.
>
> Can somebody help me with a sam
ticular app feature that has many
legitimate uses.
On Oct 13, 6:32 am, JDG wrote:
> They can still check for duplicate tweets, and can still suspend accounts
> violating the TOS, regardless of client.
>
> On Mon, Oct 12, 2009 at 23:23, PJB wrote:
>
> > I worried about this. Does
I worried about this. Doesn't Twitter realize this will just shift
things to desktop apps which they have less control over?!?
On Oct 12, 7:24 pm, Dewald Pretorius wrote:
> Any developer who has included and/or is thinking about including a
> recurring tweet feature in your app, please take not
What are you going to do when Twitter makes a huge unannounced change
to their API in, say, 3 months and totally alters everything? It has
happened before; it will happen again! This isn't a particularly
mature platform to be writing about, especially with a publication
date 6+ months away!
On
Well, in the last dragnet, http://twitter.com/ricksanchezcnn,
http://twitter.com/scottkwalker, http://twitter.com/karlrove were all
suspended. And while you might disagree with their politics, it's
pretty evident from their tweets that they were not spammers. These
well-known personalities (and
Agreed. What else is wefollow.com, which Twitter freely advertises,
but a ranking of people by followers (just look at some of the top
people in the categories and you have to ask yourself, wtf!?) When
the value of a Twitter account is determined by followers (as apps
like wefollow make clear),
If it is not in the Twitter API documentation, if the API call not
work for you, if you see no reference to it here on this forum... I am
at a loss why you are asking whether it exists or not. Clearly it
does not.
On Oct 7, 11:29 am, Rick Yazwinski wrote:
> I see comments via google about havi
This is an annoying inconsistency with the Twitter API.
If you do an authenticated call to view a user's friends/followers,
and that user is either blocking the authenticated user or is private,
you will not be able to view their friends/followers. You will get
"not authorized" error. However,
Would be good if Twitter.com used API to determine, e.g., DM count on
right-side. Right now it is woefully wrong if we delete DMs via API.
On Sep 15, 2:16 pm, Alex Payne wrote:
> The main twitter.com site already uses the API in some places. Our
> revised mobile site is built entirely on the A
Please also stop willy-nilly changing the error codes and error
messages. Since your error messages are so often inaccurate, some of
us have setup special rules to decipher what the errors actually are
-- when you change the text or code, our rules break.
For example, suspended users are/were g
We are seeing random, intermittent empty result sets from friends/ids,
called without page or cursor arguments. These empty results return
without error, and frequently "correct" themselves when tried again.
Is this a known issue? What is the status of this issue?
ou
"contact the press"!!! ;)
Regards, PB
On Sep 11, 10:46 am, "Dean Collins" wrote:
> -Original Message-
> From: twitter-development-talk@googlegroups.com
> [mailto:twitter-development-t...@googlegroups.com] On Behalf Of PJB
> Sent: Friday, September 1
Dean:
Can you please stop posting about your individual TWITTER ACCOUNT
issue on a Twitter developer forum? No "app" was blacklisted in your
case -- rather your account was suspended. There's a big difference,
and this particular forum topic is about API Rules, NOT about Twitter
account rules
This document needs further detail, specifics, and allowances.
1. "Identify the user that authored or provided the Tweet"
What do you mean by this? Presumably the author of the tweet is the
person for whom the tweet appears on Twitter.com and who therefore
actually made the tweet or authorize
We believe an unannounced Twitter API change happened today or
yesterday, and we just want to fill the group in on our findings.
This change caused some consternation from some of our user base
("your app doesn't work!"), and we want to help preclude that for
others.
As you know, if user A block
John:
Will the "third system" be used if, e.g., the user has 1000 friends
and we request friends/ids WITHOUT pagination? Or must we include
pagination arguments even if <5000 to use the third system?
PJB
On Sep 7, 9:52 pm, John Kalucki wrote:
> I don't know all the de
"For now, we're sending the row-count-queries queries back to the
second system, which is otherwise idle, but isn't consistent with the
first or third system. "
Can you help us better understand what queries you're talking about?
Do you mean, e.g., that any queries that call for *ALL* friends/id
The fix to last nights 5000 limit to friends/ids, followers/ids now
returns with approximately 1-5% duplicates.
For example:
User1:
followers: 32795
unique followers: 32428
User2:
friends: 32350
unique friends: 32046
User3:
followers: 19243
unique followers: 19045
NEITHER of these figures co
It's a good idea to have lots of checks in place. Twitter reliably
returns unreliable data... ESPECIALLY BEFORE HOLIDAY WEEKENDS. In
fact, for a couple of calls yesterday we got non-error responses
saying that the user had ZERO followers. Then it was 5000 followers.
Now it is their follower co
Actually, before yesterday, Twitter's friends_ids/followers_ids calls
were pretty close to being accurate. Now, with this new fix, they are
totally off from what is displayed on Twitter.com. So, whatever "fix"
was made yesterday, has broken the accuracy of the count (where
accuracy == matching
It seems as though you fixed one thing, and broke something else in
the process.
A large number of our users are complaining that the f/f counts (that
we compute from friends_ids() for example) are woefully off (in the
order of several thousand) from the counts displayed on Twitter.com.
Before y
The friend/follower counts are TOTALLY off. Why can't new features be
introduced without breaking critical existing features? When will
this be fixed. Many of us rely on these counts for accurate f/f
counts!
On Sep 4, 8:49 pm, John Kalucki wrote:
> The 5k limit is a bug. Working to fix.
>
>
er apps IS VERY HARD.
If you don't have expensive programming and db experience, STAY AWAY!
This app's NOT for you!
On Sep 3, 2:29 am, Nicholas Granado wrote:
> PJB ... really? There really no need to flame-bait this thread. I think
> Scott put it perfectly.
>
> Cheers,
>
$_ =~ s/\-([^\[]+?)\-/process($1)/ges foreach (@tweets);
On Sep 2, 6:50 pm, Dante Soiu wrote:
> And not computer language, Dante Soiu
Thanks Jon... can you let us know if past friendships/create (etc)
calls that haven't yet worked, will eventually work? Since we
database all of these actions, we're worried that we're going to have
bad data for the past, e.g., 48 hours, unless those non-error calls
actually go through.
On Aug
Woke up this morning to find that several of our users have written in
noting that friendship actions taken through our application are not
working.
We confirmed this problem, across multiple IPs and multiple different
apps. Friendships/create works inconsistently: about 30% of the time
they wo
We are experiencing similar problems. Friendship create is returning
success, yet checking Twitter.com directly, or friends/ids.xml does
NOT show the id of the friended user. At least not immediately. It
appears as though there is a several hour delay before updating.
On Aug 30, 11:28 pm, Ben
Hehehe... your regex isn't much better!
/(.+?)<\/a>/is
On Aug 21, 9:54 pm, Gonzalo Larralde
wrote:
> On Sat, Aug 22, 2009 at 1:17 AM, TCI wrote:
>
> > Recently you added nofollow's, and now you moved the nofollow after
> > the href. Some of us filter these out and you changing them is only
>
Usenet, IRC... I am starting to feel like its 1993 all over again!
Maybe next we can get a game of Netrek going on NeXt stations! ;)
On Aug 18, 3:35 pm, Marcel Molina wrote:
> We've heard your requests for greater transparency and more frequent
> communication in the last couple weeks around th
The scariest part about all of this, frankly, is less the trademark
stuff, and more the fact that he is being punished for violating
Twitter's terms and services. As near as I can tell, his app just
follows users who tweet certain keywords. It doesn't even UNFOLLOW
them (thus potentially churn
This is all rather scary, especially for those of us dedicating
significant resources to Twitter-related development.
I was having a new logo designed... it was going to be in light blue.
I guess I will have to reconsider that option now!
Before I bring you back to your regularly scheduled programming
concerning intellectual property issues and whether or not someone may
or may not be sued, I do have something API-related...
Is anyone else experiencing problems today with friends/ids and
followers/ids returning empty sets, yet wi
67 matches
Mail list logo
