[twitter-dev] New POST Rate Limit on White-Listed IPs

[Dewald Pretorius]

A new rate limit error has cropped up when making POST requests.

What I do know about it:

The error message says, "Rate limit exceeded. Clients may not make
more than 378 requests per 60 minutes."

What I don't know about it:

a) Is this rate limit counted per Twitter API method (i.e., each one
has its own count - a count for statuses/update, another count for
direct_messages/new, etc.)?

b) Or, is this rate limit an aggregate count for all POSTs made by a
Twitter account?

It is well and fine to introduce a new form of rate limit, but advance
notice of it will be HIGHLY APPRECIATED.

Twitter: More information, please?

Dewald

[twitter-dev] Re: about OAuth

[thomas cavanaugh]

the only way to find out is to do it

On Sat, Oct 10, 2009 at 2:05 PM, Oguzhan  wrote:

>
> Hi Folks,
>
> I'm using OAuth in my twitter application and I was wondering
> something.
>
> Have received the user's permission by OAuth.
> I saved my database oauth_token after for example one day later. Can I
> update twitter status with my saved oauth_token?
>
>
>
>

[twitter-dev] Re: About the oneforty application directory

[Pistachio]

In reviewing this thread for work on our FAQs, I realized that this
aspect of the previous contract never got addressed here on this list.

We're not entirely sure where the impression that revenue would be
paid out as donations or gifts came from, but it was DEFINITELY never
the plan.

All revenue terms will be dealt with as revenue.

Any words in the (now defunct) contract mentioning gifts and donations
were referring explicitly to the actual gifts and donations that
developers can elect to receive at the site.

Warmly,
Laura

Laura Fitton, Founder
oneforty.com

On Sep 29, 4:31 am, Andrew Badera  wrote:
> As CTO of a startup involved with 501c3s for over two years now, I'm
> pretty confident in stating that development cannot be donated,
> period. Services cannot be donated for tax purposes. Only goods can be
> donated for tax deductions. Services are always taxable, period. No
> tax benefit for donated services.
>
> ∞ Andy Badera
> ∞ +1 518-641-1280
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me:http://www.google.com/search?q=andrew%20badera
>
> On Tue, Sep 29, 2009 at 2:47 AM, Chris Babcock
>
>  wrote:
>
> >  - Some development *is* done by non-profit organizations or could
> >   possibly be donated to a non-profit. If the structure of the
> >   developer agreement was conduscive to it, as this is, then
> >   non-profit work and code donations to non-profit orgs would be
> >   encouraged and there could be tax benefits.
>
> > Chris Babcock

[twitter-dev] Re: Where in API docs to get first tweet only

[Scott Haneda]

One last question I think.  Is there a way to control how many items  
come back in a request to the public timeline?  I currently can not  
tell how many there are in the result set, I will have to wait an hour.


However, if I could get a larger batch, I could query it much less  
often.

--
Scott * If you contact me off list replace talklists@ with scott@ * 

[twitter-dev] Re: Where in API docs to get first tweet only

[Scott Haneda]

Thank you.  I think I just got booted from hitting the public timeline  
too much.  I requested whitelisting via the whitelist form.  Since I  
am not authenticating, and am just curl'ing the json resource for the  
public timeline, is there a way for me to tell what is really happening?


I currently get an http 400 bad request, which I am betting is a  
throttle/block.


Is it possible to determine the remaining number of queries I am  
allowed via some command?

Thanks.
--
Scott * If you contact me off list replace talklists@ with scott@ *

On Oct 10, 2009, at 3:42 PM, John Kalucki wrote:


http://apiwiki.twitter.com/Streaming-API-Documentation

[twitter-dev] Re: Where in API docs to get first tweet only

[John Kalucki]

http://apiwiki.twitter.com/Streaming-API-Documentation


On Oct 10, 3:16 pm, Scott Haneda  wrote:
> Thanks Peter.  Any pointers on general docs on what the heck spritzer  
> and garden hose is?
>
> The public timeline api says this:
>         statuses/public_timeline
>         Returns the 20 most recent statuses from non-protected users who have
>         set a custom user icon. The public timeline is cached for 60 seconds 
> so
>         requesting it more often than that is a waste of resources.
>
> If I pull this into an RSS feed:
> feed://twitter.com/statuses/public_timeline.rss
>
> I refresh it a few seconds later, I get new tweets.  Is that 60 second  
> cache an out of date note in the docs?
>
> The API also states this is rate limited.  To get the data I am after,  
> I am going to be hitting this think pretty hard.  If there is no  
> cache, it will be more than 60 seconds in frequency, more like as soon  
> as the script is done working, I will request it again.  Pretty much  
> perpetual requesting.
>
> Or is this treated more like the search API, and is rate limited very  
> liberally?
> Thank you for your help this Saturday.
> --
> Scott * If you contact me off list replace talklists@ with scott@ *
>
> On Oct 10, 2009, at 2:06 PM, Peter Denton wrote:
>
> > Hi Scott,
> > Since it seems you are looking for a sampling situation, you might  
> > want to
> > poll the public timeline and check for 1st tweet, (created at and  
> > 1st update
> > timeframe are same/near day).
> > Also, you could expand your sample size and look into accessing the
> > spritzer  or garden hose and again running some best guess scenario of
> > signup and first tweet.
>
> > Cheers
> > Peter
>
> > On Sat, Oct 10, 2009 at 1:19 PM, Scott Haneda   
> > wrote:
>
> >> I'm not sure this is possible, I'm trying to avoid a local data  
> >> store to
> >> make it possible.
>
> >> I would like to get a small bit of data from a tweet, but only the  
> >> first
> >> tweet, ignoring that user from that point forward.
>
> >> I can of course grab their username and disregard, but my list will  
> >> grow
> >> quickly.
>
> >> If my goal is to get stats on what time of day most people are  
> >> joining
> >> Twitter and posting their first tweet, what would be the best place  
> >> to query
> >> for that data?
>
> >> I just need the time, and perhaps location fields. Would the search  
> >> API be
> >> good? I hear about this firehose thing, but don't know what that is.
>
> >> I'm thinking the public timeline may be best, but there may be way  
> >> too much
> >> data for me to deal with.
>
> >> Suggestions on methods appreciated.
>
> >> --
> >> Scott
> >> Iphone says hello.

[twitter-dev] Re: Where in API docs to get first tweet only

[Scott Haneda]

Thanks Peter.  Any pointers on general docs on what the heck spritzer  
and garden hose is?


The public timeline api says this:
statuses/public_timeline
Returns the 20 most recent statuses from non-protected users who have
set a custom user icon. The public timeline is cached for 60 seconds so
requesting it more often than that is a waste of resources.

If I pull this into an RSS feed:
feed://twitter.com/statuses/public_timeline.rss

I refresh it a few seconds later, I get new tweets.  Is that 60 second  
cache an out of date note in the docs?


The API also states this is rate limited.  To get the data I am after,  
I am going to be hitting this think pretty hard.  If there is no  
cache, it will be more than 60 seconds in frequency, more like as soon  
as the script is done working, I will request it again.  Pretty much  
perpetual requesting.


Or is this treated more like the search API, and is rate limited very  
liberally?

Thank you for your help this Saturday.
--
Scott * If you contact me off list replace talklists@ with scott@ *

On Oct 10, 2009, at 2:06 PM, Peter Denton wrote:


Hi Scott,
Since it seems you are looking for a sampling situation, you might  
want to
poll the public timeline and check for 1st tweet, (created at and  
1st update

timeframe are same/near day).
Also, you could expand your sample size and look into accessing the
spritzer  or garden hose and again running some best guess scenario of
signup and first tweet.

Cheers
Peter

On Sat, Oct 10, 2009 at 1:19 PM, Scott Haneda   
wrote:




I'm not sure this is possible, I'm trying to avoid a local data  
store to

make it possible.

I would like to get a small bit of data from a tweet, but only the  
first

tweet, ignoring that user from that point forward.

I can of course grab their username and disregard, but my list will  
grow

quickly.

If my goal is to get stats on what time of day most people are  
joining
Twitter and posting their first tweet, what would be the best place  
to query

for that data?

I just need the time, and perhaps location fields. Would the search  
API be

good? I hear about this firehose thing, but don't know what that is.

I'm thinking the public timeline may be best, but there may be way  
too much

data for me to deal with.

Suggestions on methods appreciated.

--
Scott
Iphone says hello.

[twitter-dev] Re: Where in API docs to get first tweet only

[Peter Denton]

Hi Scott,
Since it seems you are looking for a sampling situation, you might want to
poll the public timeline and check for 1st tweet, (created at and 1st update
timeframe are same/near day).
Also, you could expand your sample size and look into accessing the
spritzer  or garden hose and again running some best guess scenario of
signup and first tweet.

Cheers
Peter

On Sat, Oct 10, 2009 at 1:19 PM, Scott Haneda  wrote:

>
> I'm not sure this is possible, I'm trying to avoid a local data store to
> make it possible.
>
> I would like to get a small bit of data from a tweet, but only the first
> tweet, ignoring that user from that point forward.
>
> I can of course grab their username and disregard, but my list will grow
> quickly.
>
> If my goal is to get stats on what time of day most people are joining
> Twitter and posting their first tweet, what would be the best place to query
> for that data?
>
> I just need the time, and perhaps location fields. Would the search API be
> good? I hear about this firehose thing, but don't know what that is.
>
> I'm thinking the public timeline may be best, but there may be way too much
> data for me to deal with.
>
> Suggestions on methods appreciated.
>
> --
> Scott
> Iphone says hello.
>

[twitter-dev] Where in API docs to get first tweet only

[Scott Haneda]

I'm not sure this is possible, I'm trying to avoid a local data store  
to make it possible.


I would like to get a small bit of data from a tweet, but only the  
first tweet, ignoring that user from that point forward.


I can of course grab their username and disregard, but my list will  
grow quickly.


If my goal is to get stats on what time of day most people are joining  
Twitter and posting their first tweet, what would be the best place to  
query for that data?


I just need the time, and perhaps location fields. Would the search  
API be good? I hear about this firehose thing, but don't know what  
that is.


I'm thinking the public timeline may be best, but there may be way too  
much data for me to deal with.


Suggestions on methods appreciated.

--
Scott
Iphone says hello.

[twitter-dev] Re: about OAuth

[ryan alford]

You need the token and the token secret.



On Oct 10, 2009, at 3:40 PM, Oguzhan  wrote:

>
> Hi Folks,
>
> I'm using OAuth in my twitter application and I was wondering
> something.
>
> Have received the user's permission by OAuth.
> I saved my database oauth_token after for example one day later. Can I
> update twitter status with my saved oauth_token?
>
>
>

[twitter-dev] Re: twitter.com/followers/befriend_all ?

[Rick Yazwinski]

It'd be a great method to have - it'd save multiple calls to the api
to get friends and followers and add the delta.

On Sat, Oct 10, 2009 at 5:45 AM, Abraham Williams <4bra...@gmail.com> wrote:
> Fascinating. I don't remember ever hearing about this method. There are a
> couple of references on the
> net: http://www.google.com/search?hl=en&q="followers/befriend_all";
> Abraham
>
> On Fri, Oct 9, 2009 at 13:42, PJB  wrote:
>>
>>
>> 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 having a bot call this regularily to
>> > make sure your bot follows anyone following the bot... makes sense
>> > (rather than getting all friends and all followers and issuing
>> > seperate friend requests), however I see no reference to it on the
>> > twitter api site.
>> >
>> > Is this legit?
>> >
>> > When I call it it just redirects to my home page.
>> >
>> > Rick...
>
>
> --
> Abraham Williams | Community Evangelist | http://web608.org
> Hacker | http://abrah.am | http://twitter.com/abraham
> Project | http://fireeagle.labs.poseurtech.com
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from Madison, Wisconsin, United States

[twitter-dev] Re: Search API - HTTP Response Code 502, what to do?

[Zamite]

So basically, if its not a 503 on the search API I should be clear?

On Oct 9, 5:11 pm, jmathai  wrote:
> Get used to receiving random 502 (and other response codes) from the
> Twitter API.  If you don't know exactly what the code means I suggest
> retrying it.  If it's explicit that you're being rate limited then
> wait before you retry.
>
> http://twitter.com/jkalucki/status/4686847704http://twitter.com/jkalucki/status/4686422873
>
> On Oct 9, 5:12 am, Zamite  wrote:
>
> > Hey there,
>
> > I'm posting this because I'm concerned with the possibility of
> > exceeding the rate limit and so I would like advice on what to do.
> > I have an application that does several queries to the Search API on
> > several Geocode locations.
> > The twitter Search API documentation clearly states that if I hit a
> > 503 status code I should (and I do) have my application wait the time
> > specified in the "Retry-After" header.
>
> > However I haven't yet hit any 503 status codes, instead I'm receiving
> > a few 502 http status codes with the infamous "Time out!" whale
> > message. My question is:
>
> > How should I process these?
>
> > Since there is no "Retry-After" header on 502 codes I can't know how
> > much time to wait. Will it influence my rate limiting, and get me
> > banned if I ignore them? How long should I wait before the next
> > request? (a few seconds, minutes, until the next hour?)
>
> > Would appreciate any input I could get on this :)
>
> > Thank you.

[twitter-dev] about OAuth

[Oguzhan]

Hi Folks,

I'm using OAuth in my twitter application and I was wondering
something.

Have received the user's permission by OAuth.
I saved my database oauth_token after for example one day later. Can I
update twitter status with my saved oauth_token?

[twitter-dev] Re: Account management app - suspended accounts

[Andy Freeman]

Actually, what he's saying is that it's not always possible to have
public, concrete, and well-defined rules that work.

You clearly think that it's possible in this case.

So, let's be positive.

Let's see a set of rules that meets those criteria.  They have to be
concrete, well-defined, and presumably relatively fixed and easy-
enough to implement relatively efficiently.  They have to actually
address the abuse problems.  And they have to do all that while being
public, that is, known to potential abusers.



On Oct 9, 10:50 am, SuperCerial  wrote:
> How about you just answer my question?
>
> What you're saying is mankind is wrong to live by well defined and
> concrete rules. I could steal that car and it will be ok, then again
> it might not - what don't you try and find out. You really think
> that's right?
>
> Of course the reality is Twitter is another laissez fair bums on seats
> driven site and as google proved, there is nothing like the abiltiy to
> change the rules on a whim, or hide a problem for a company of this
> ilk.
>
> On Oct 9, 6:07 pm, John Kalucki  wrote:
>
>
>
> > Openness about abuse is generally counter-productive for everyone. For
> > example, opaque limits are harder to game and give better detection
> > signals. Also, practically, limits need to be adjusted without notice
> > to respond changing attacks. In the end, valid access that is
> > difficult to distinguish from access overwhelmingly used for invalid
> > purposes are sometimes, sadly, going to get caught in a low-latency
> > high-volume countermeasure system.
>
> > -John Kaluckihttp://twitter.com/jkalucki
> > Services, Twitter Inc.
>
> > On Oct 9, 5:23 am, SuperCerial  wrote:
>
> > > Absolutely true. on both counts...
>
> > > However, not so long ago Twitter banned many accounts by mistake
> > > because they used tweetlater.
>
> > > The trouble is on one hand Twitter supports, encourages the creation
> > > of these applications and on the other hand fails horribly to provide
> > > sufficient guidelines about their use. I know one of the accounts was
> > > purely posting quotes of a dead comedian, and this went down very well
> > > - had a big following of people who regularly responded positively.
> > > Account status today? Suspended. Why? Who knows. Who is being asked
> > > about this? Me.
>
> > > It is not up to the 600 individuals to contact Twitter but rather for
> > > Twitter to explain what is changing so people can ensure they are
> > > within these new parameters.
>
> > > On Oct 9, 10:07 am, Andrew Badera  wrote:
>
> > > > On Thu, Oct 8, 2009 at 11:03 PM, Abraham Williams <4bra...@gmail.com> 
> > > > wrote:
> > > > > Twitter's spam flagging system is an ever-changing trade secret. It is
> > > > > unlikely that you will get a direct answer. Have the 600 account 
> > > > > holders
> > > > > contact Twitter support and hopefully they will get re-enabled 
> > > > > quickly.
> > > > > Abraham
>
> > > > Or, in the event that they ARE spammers, hopefully they WON'T. People
> > > > writing, selling or hosting multiple-account management software need
> > > > to become a LOT more circumspect in who they serve as clientele, and
> > > > how precisely they serve them. There is a TON of abuse here, and
> > > > greedy people need to learn a lesson.
>
> > > > Not saying that's the case with the OP, but I'm EXTREMELY happy to see
> > > > more aggressive filtering going on! (And looking forward to the
> > > > Address Book!)
>
> > > > ∞ Andy Badera
> > > > ∞ +1 518-641-1280
> > > > ∞ This email is: [ ] bloggable [x] ask first [ ] private
> > > > ∞ Google me:http://www.google.com/search?q=andrew%20badera-Hide quoted 
> > > > text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

[twitter-dev] Re: SMS Notifications

[Adam Shannon]

I haven't tested either of those cases, but I'm noticing that SMS
notifications are delayed in general (some times over an hour).


-- 
- Adam Shannon ( http://ashannon.us )

[twitter-dev] Re: Whitelisted IPs only work when authed?

[Waldron Faulkner]

Are you sure your requests are coming from the same IP you
whitelisted? If you're on a shared host, for example, your outbound
requests may come from a different IP as your dedicated inbound IP. I
had this issue, had to bind curl to my dedicated IP, and it worked
fine. Setting the CURLOPT_INTERFACE option is what worked for me.

On Oct 9, 5:08 pm, Charles  wrote:
> I recently received email that confirmed my whitelisting status.  I
> have several IPs whitelisted, as well as the account.  From a shell on
> one of the whitelisted servers, I make a couple requests and then try:
>
> curlhttp://twitter.com/account/rate_limit_status.xml
>
> 
> 
>   150
>   1255123230 seconds>
>   2009-10-09T21:20:30+00:00
>   147
> 
>
> If, on the other hand, I try:
>
> curl -u username:passwordhttp://twitter.com/account/rate_limit_status.xml
>
> 
>   1
>   2009-10-09T21:57:09+00:00
>   2
>   1255125429 seconds>
> 
>
> I was under the impression I did not have to auth if I was making
> calls from the API?  Also:  if I use my application's oauth
> credentials to generate an oauth_request and use the oauth URL, I am
> still getting the lower rate limit.  Is this normal behavior?

[twitter-dev] Re: Issue with API?

[Dewald Pretorius]

In the authenticated friends timeline, I believe  tells you
whether that Twitter account is following you or not.

Dewald

On Oct 10, 11:55 am, eclipsed4utoo  wrote:
> Does anybody know if there is an issue with the friends_timeline REST
> method?  When I do it, it returns tweets from all of my friends.
> However, the "following" XML tag is false.  How can that be?  They are
> my friend if I am following them, correct?
>
> http://twitter.com/statuses/friends_timeline.xml
>
> and this is the first status that is returned.
>
> 
>     Sat Oct 10 14:36:56 + 2009
>     4761273314
>     
>               Disk2vhd Turns Your PC Into a Virtual 
> Machine:http://bit.ly/1z6lNa
>     
>     
>             http://www.tweetdeck.com/";
> rel="nofollow">TweetDeck
>     
>     false
>     
>     
>     false
>     
>     
>          43065412
>          George Dan Pirvu
>          gamearchitect
>          a giant cubicle
>          
>                 Programming games since 1997. Psychologist, internet
> marketer, horrible chess player.
>          
>          
>                  
> http://a3.twimg.com/profile_images/280718799/georgep_normal.jpg
>          
>          http://www.randombyte.com
>          false
>          7643
>          9AE4E8
>          33
>          0084B4
>          DDFFCC profile_sidebar_fill_color>
>          BDDCAD profile_sidebar_border_color>
>          8148
>          Thu May 28 07:08:07 + 2009
>          0
>          7200
>          Bucharest
>          
>                  
> http://a3.twimg.com/profile_background_images/19709051/olivemanna_isl...
>          
>          true
>          656
>          false
>          false
>          false
>          false
>     
>     
> 
>
> So how can that be?

[twitter-dev] Re: Issue with API?

[ryan alford]

I started thinking that also, but the twitter website shows this
person as a follower of mine.  So the tag should show as true, correct?



On Oct 10, 2009, at 12:03 PM, Dewald Pretorius  wrote:

>
> In the authenticated friends timeline, I believe  tells you
> whether that Twitter account is following you or not.
>
> Dewald
>
> On Oct 10, 11:55 am, eclipsed4utoo  wrote:
>> Does anybody know if there is an issue with the friends_timeline REST
>> method?  When I do it, it returns tweets from all of my friends.
>> However, the "following" XML tag is false.  How can that be?  They
>> are
>> my friend if I am following them, correct?
>>
>> http://twitter.com/statuses/friends_timeline.xml
>>
>> and this is the first status that is returned.
>>
>> 
>> Sat Oct 10 14:36:56 + 2009
>> 4761273314
>> 
>>   Disk2vhd Turns Your PC Into a Virtual Machine:http://
>> bit.ly/1z6lNa
>> 
>> 
>> http://www.tweetdeck.com/";
>> rel="nofollow">TweetDeck
>> 
>> false
>> 
>> 
>> false
>> 
>> 
>>  43065412
>>  George Dan Pirvu
>>  gamearchitect
>>  a giant cubicle
>>  
>> Programming games since 1997. Psychologist, internet
>> marketer, horrible chess player.
>>  
>>  
>>  
>> http://a3.twimg.com/profile_images/280718799/georgep_normal.jpg
>>  
>>  http://www.randombyte.com
>>  false
>>  7643
>>  9AE4E8
>>  33
>>  0084B4
>>  DDFFCC> profile_sidebar_fill_color>
>>  BDDCAD> profile_sidebar_border_color>
>>  8148
>>  Thu May 28 07:08:07 + 2009
>>  0
>>  7200
>>  Bucharest
>>  
>>  
>> http://a3.twimg.com/profile_background_images/19709051/olivemanna_isl
>> ...
>>  
>>  true
>>  656
>>  false
>>  false
>>  false
>>  false
>> 
>> 
>> 
>>
>> So how can that be?

[twitter-dev] Re: twitter.com/followers/befriend_all ?

[Dewald Pretorius]

I tried to check in Archive.org, but at some point in 2007 Twitter
excluded /api with robots.txt.

Besides, it was so interesting to see how the Twitter home page
evolved over time that I got completely distracted.

Dewald

PS. Oops. The other thread where I posted this was a mistake. Just
shows you the extent of my distraction.

On Oct 10, 6:45 am, Abraham Williams <4bra...@gmail.com> wrote:
> Fascinating. I don't remember ever hearing about this method. There are a
> couple of references on the 
> net:http://www.google.com/search?hl=en&q="followers/befriend_all";
> Abraham
>
>
>
> On Fri, Oct 9, 2009 at 13:42, PJB  wrote:
>
> > 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 having a bot call this regularily to
> > > make sure your bot follows anyone following the bot... makes sense
> > > (rather than getting all friends and all followers and issuing
> > > seperate friend requests), however I see no reference to it on the
> > > twitter api site.
>
> > > Is this legit?
>
> > > When I call it it just redirects to my home page.
>
> > > Rick...
>
> --
> Abraham Williams | Community Evangelist |http://web608.org
> Hacker |http://abrah.am|http://twitter.com/abraham
> Project |http://fireeagle.labs.poseurtech.com
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from Madison, Wisconsin, United States

[twitter-dev] Re: where will we be next year

[JDG]

that's more philosophical than anything.

On Sat, Oct 10, 2009 at 09:00, thomas cavanaugh wrote:

> where will twitter be in one year?
>
>
> On Sat, Oct 10, 2009 at 12:44 AM, Michael Steuer wrote:
>
>>
>> Is there a development question here?
>>
>>
>>
>>
>> On Oct 9, 2009, at 7:16 PM, tom  wrote:
>>
>>
>>> With the 2010 elections coming soon,and an angry electorate  I can see
>>> twitter playing an unheard of influence on these elections.. as i see
>>> it the tasks will be KEEP IT ACCURATE,keep it brief,and keep it
>>> relevant The pols are allready sitting up and taking notice,
>>> NOTE;;the 18 to 30 year old electors COULD CONTROL EVERY ELECTION,  if
>>> they chose to vote
>>>
>>
>


-- 
Internets. Serious business.

[twitter-dev] Re: Twitter API in 24 Hours

[Dewald Pretorius]

I tried to check in Archive.org, but at some point in 2007 Twitter
excluded /api with robots.txt.

Besides, it was so interesting to see how the Twitter home page
evolved over time that I got completely distracted.

Dewald

On Oct 10, 7:31 am, Abraham Williams <4bra...@gmail.com> wrote:
> Just put a big *beta* sticker on the front.
>
>
>
> On Sat, Oct 10, 2009 at 05:28, Andrew Badera  wrote:
>
> > That could be said about a lot of technologies with books being
> > published about them ...
>
> > ∞ Andy Badera
> > ∞ +1 518-641-1280
> > ∞ This email is: [ ] bloggable [x] ask first [ ] private
> > ∞ Google me:http://www.google.com/search?q=andrew%20badera
>
> > On Sat, Oct 10, 2009 at 6:26 AM, PJB  wrote:
>
> > > 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 Oct 9, 2:42 pm, Andrew Mager  wrote:
> > >> I am co-authoring a book about the Twitter API, and I was wondering if
> > >> any of you guys wanted to write a chapter.
>
> > >> The book will be in the SAMS 24 hour series, and it's scheduled to be
> > >> released mid-next year.
>
> > >> Here is our tentative table of contents:
>
> > >> Introduction to Twitter
> > >> An overview of Twitter and Microblogging
> > >> Common Types of Twitter Applications
> > >> Key Issues to Consider when Developing Twitter Apps
> > >> Overview of Twitters's API structure
> > >> The API is HTTP-based
> > >> The API uses Representational State Transfer (REST)
> > >> There are pagination limits
> > >> The Twitter API supports UTF-8 encoding
> > >> Getting Started with the API
> > >> Setting up an environment
> > >> Making your first API call
> > >> Parsing the reply
> > >> Message, date, author, image
> > >> Creating a simple display
> > >> Setting up an application framework
> > >> Creating a twitter Class
> > >> Various twitter libraries are available
> > >> PHP Class used in this book
> > >> Modifing our class
> > >> Twitter Error messages
> > >> What each error code means
> > >> Modifing our twitter Class
> > >> Passing credentials to twitter
> > >> Standard method (HTTP)
> > >> Using cookies (create, retrieve, delete)
> > >> OAuth
> > >> Sending and Receiving messages from Twitter
> > >> Creating a basic twitter client
> > >> Sending messages in twitter
> > >> Twitter search
> > >> Dealing with Twitter downtimes and errors
> > >> Twitter Beyond the API
> > >> Future of Twitter
> > >> Example Applications
> > >> Other Mashup Twitter Services
> > >> Twitter Etiquette
>
> > >> Ping me directly if you are interested! andrew.ma...@gmail.com
>
> --
> Abraham Williams | Community Evangelist |http://web608.org
> Hacker |http://abrah.am|http://twitter.com/abraham
> Project |http://fireeagle.labs.poseurtech.com
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from Madison, Wisconsin, United States

[twitter-dev] Re: Have you read the OneForty.com Developer Contract?

[Dewald Pretorius]

Laura,

Fair enough. Those are the rules that you have decided should apply to
your business.

But, I will not hand over to you and your sublicensees the keys to my
intellectual property or app licenses simply for the privilege of
editing my app's information on your service.

All you really require is the assurance that your business will not be
violating third-party IP by displaying their logos and other
proprietary marks on your website.

I'm not a lawyer and I don't even comb my hair like one, but I believe
one usually accomplishes the above by clearly attributing individual
rights to the owning party, or by a general legal statement that
attributes rights where appropriate.

Dewald

On Oct 10, 12:22 pm, Pistachio  wrote:
> Very well framed, Dewald. Why a contract for claiming the listing?
>
> We provide two ways to associate the developer with the item: Credit
> vs. Claiming.
>
> CREDIT: Providing the rightful developer with credit is no problem and
> attaches no contractual obligation. A listing on the site with the
> name of the developer (which we will add on request if the page does
> not already have it listed) is an editorial listing compiled from
> publicly available information.
>
> CLAIMING: The moment we hand over the keys to edit, that page is now
> (potentially) a promotional tool. It's now a business service being
> provided and the contract is to protect both parties. We fully expect
> many apps will never be sold on the site since that's always going to
> be the developer's choice. Regardless of what they do we're still
> offering a free (it will always be free) promotional platform that can
> be used to promote whatever business the item may be doing elsewhere.
> All we ask in return is a contract to protect both parties.
>
> Make sense?
>
> Warmly,
> Laura
>
> On Oct 9, 9:24 pm, Dewald Pretorius  wrote:
>
> > Maybe, at a more basic level my question is this:
>
> > Why do I need to enter into a contract with oneforty at all, when all
> > I want to do is say, "I am Joe, WonderSocialWidget is my app, and here
> > is more information about it."
>
> > Isn't this part of oneforty nothing more than a free application
> > directory, where the developer can identify him/herself and provide
> > more information if he/she chooses to do so?
>
> > Dewald
>
> > On Oct 9, 9:34 pm, Dewald Pretorius  wrote:
>
> > > Laura,
>
> > > If my understanding is correct, this new contract is applicable when I
> > > want to claim my app in oneforty.
>
> > > With that in mind:
>
> > > a) Why do I need to license to oneforty and your sublicensees
> > > (whomever that may be) all my trademarks, trade names, service marks,
> > > logos or other identifying or distinctive marks.
>
> > > Let's say "wondersocialwidget" is my trademark. By licensing it to
> > > oneforty and your sublicensees, I enable you (collective) to create
> > > sites called buywondersocialwidget.com, getsocialwidgethere.com,
> > > therealsocialwidget.com, etc., and there is nothing I can do to stop
> > > that because I have licensed you to do that. Just for the ability to
> > > claim my app in your service? That does not make sense. What then
> > > about the unclaimed apps? Will you be violating their trademarks by
> > > virtue of the fact that their developers have not agreed to this
> > > contract?
>
> > > b) Why is 3.2 necessary at all? In other words, why do I need to
> > > license my app to oneforty in order for me to claim it? Shouldn't all
> > > this licensing stuff be in the Reseller Agreement?
>
> > > Dewald
>
> > > On Oct 9, 8:14 pm, Pistachio  wrote:
>
> > > > Cross-posting this comment just posted to @BradleyJoyce's 
> > > > blog:http://bit.ly/2RqnU9
>
> > > > Hi folks,
>
> > > > We're doing our best to hear and respond to developer feedback and
> > > > better serve the community.
>
> > > > Our approach to the developer contract was wrong. We're working to
> > > > make it right. Here's how:
>
> > > > Revised Publisher Registration Contract
> > > >     * Effective immediately, the old Reseller Agreement is replaced
> > > > with a Publisher Registration Contract. (View it 
> > > > here:http://oneforty.com/terms/publisher_contract)
> > > >     * This lets you register as a developer and claim your apps.
> > > >     * We're still working on needed improvements to this contract to
> > > > create productive terms of service that cover registration, claiming
> > > > and optional donations
>
> > > > Two separate agreements:
> > > >     * Publisher Registration Contract (applies if you wish to register
> > > > for developer privileges to claim and edit your app)
> > > >     * Reseller Agreement (future: will only apply if you wish to offer
> > > > items for sale at oneforty.com when that functionality is rolled out).
> > > > This contract will be developed as part of our ecommerce pilot
> > > > program. Interested in being part of the pilot testing? Ping us at
> > > > develop...@oneforty.com.
>
> > > > Donations
> > > >     * To revise the cont

[twitter-dev] Re: Have you read the OneForty.com Developer Contract?

[Pistachio]

Very well framed, Dewald. Why a contract for claiming the listing?

We provide two ways to associate the developer with the item: Credit
vs. Claiming.

CREDIT: Providing the rightful developer with credit is no problem and
attaches no contractual obligation. A listing on the site with the
name of the developer (which we will add on request if the page does
not already have it listed) is an editorial listing compiled from
publicly available information.

CLAIMING: The moment we hand over the keys to edit, that page is now
(potentially) a promotional tool. It's now a business service being
provided and the contract is to protect both parties. We fully expect
many apps will never be sold on the site since that's always going to
be the developer's choice. Regardless of what they do we're still
offering a free (it will always be free) promotional platform that can
be used to promote whatever business the item may be doing elsewhere.
All we ask in return is a contract to protect both parties.

Make sense?

Warmly,
Laura


On Oct 9, 9:24 pm, Dewald Pretorius  wrote:
> Maybe, at a more basic level my question is this:
>
> Why do I need to enter into a contract with oneforty at all, when all
> I want to do is say, "I am Joe, WonderSocialWidget is my app, and here
> is more information about it."
>
> Isn't this part of oneforty nothing more than a free application
> directory, where the developer can identify him/herself and provide
> more information if he/she chooses to do so?
>
> Dewald
>
> On Oct 9, 9:34 pm, Dewald Pretorius  wrote:
>
> > Laura,
>
> > If my understanding is correct, this new contract is applicable when I
> > want to claim my app in oneforty.
>
> > With that in mind:
>
> > a) Why do I need to license to oneforty and your sublicensees
> > (whomever that may be) all my trademarks, trade names, service marks,
> > logos or other identifying or distinctive marks.
>
> > Let's say "wondersocialwidget" is my trademark. By licensing it to
> > oneforty and your sublicensees, I enable you (collective) to create
> > sites called buywondersocialwidget.com, getsocialwidgethere.com,
> > therealsocialwidget.com, etc., and there is nothing I can do to stop
> > that because I have licensed you to do that. Just for the ability to
> > claim my app in your service? That does not make sense. What then
> > about the unclaimed apps? Will you be violating their trademarks by
> > virtue of the fact that their developers have not agreed to this
> > contract?
>
> > b) Why is 3.2 necessary at all? In other words, why do I need to
> > license my app to oneforty in order for me to claim it? Shouldn't all
> > this licensing stuff be in the Reseller Agreement?
>
> > Dewald
>
> > On Oct 9, 8:14 pm, Pistachio  wrote:
>
> > > Cross-posting this comment just posted to @BradleyJoyce's 
> > > blog:http://bit.ly/2RqnU9
>
> > > Hi folks,
>
> > > We're doing our best to hear and respond to developer feedback and
> > > better serve the community.
>
> > > Our approach to the developer contract was wrong. We're working to
> > > make it right. Here's how:
>
> > > Revised Publisher Registration Contract
> > >     * Effective immediately, the old Reseller Agreement is replaced
> > > with a Publisher Registration Contract. (View it 
> > > here:http://oneforty.com/terms/publisher_contract)
> > >     * This lets you register as a developer and claim your apps.
> > >     * We're still working on needed improvements to this contract to
> > > create productive terms of service that cover registration, claiming
> > > and optional donations
>
> > > Two separate agreements:
> > >     * Publisher Registration Contract (applies if you wish to register
> > > for developer privileges to claim and edit your app)
> > >     * Reseller Agreement (future: will only apply if you wish to offer
> > > items for sale at oneforty.com when that functionality is rolled out).
> > > This contract will be developed as part of our ecommerce pilot
> > > program. Interested in being part of the pilot testing? Ping us at
> > > develop...@oneforty.com.
>
> > > Donations
> > >     * To revise the contract today, we had to temporarily disable the
> > > donation service.
> > >     * We have refunded all donations that were made under the terms of
> > > the old contract.
> > >     * We're revising the Publisher Registration Contract to allow us
> > > to turn donations back on for those who opt-in.
>
> > > Reseller Agreement
> > >     * As part of our ecommerce pilot, we'll create a second contract
> > > for developers who wish to sell products on our site.
> > >     * Its terms will be more developer friendly and created together
> > > with your feedback.
>
> > > Thank you for bearing with us while we work out these early kinks. We
> > > value your feedback, and we're anxious to make the Twitter community
> > > an even better place. As always, you can reach us at
> > > develop...@oneforty.com.
>
> > > Warmly,
> > > the oneforty team
>
> > > Laura, Mike, Michael and Robby
>
> > > 

[twitter-dev] Re: where will we be next year

[thomas cavanaugh]

where will twitter be in one year?

On Sat, Oct 10, 2009 at 12:44 AM, Michael Steuer  wrote:

>
> Is there a development question here?
>
>
>
>
> On Oct 9, 2009, at 7:16 PM, tom  wrote:
>
>
>> With the 2010 elections coming soon,and an angry electorate  I can see
>> twitter playing an unheard of influence on these elections.. as i see
>> it the tasks will be KEEP IT ACCURATE,keep it brief,and keep it
>> relevant The pols are allready sitting up and taking notice,
>> NOTE;;the 18 to 30 year old electors COULD CONTROL EVERY ELECTION,  if
>> they chose to vote
>>
>

[twitter-dev] Re: Have you read the OneForty.com Developer Contract?

[thomas cavanaugh]

Henry the VIII HAD IT RIGHT,"The first thing i am going to do is kill all
the lawwyers

On Sat, Oct 10, 2009 at 10:25 AM, Duane Roelands
wrote:

>
> No, no, a thousand times no.
>
> "Licensor further warrants to oneforty and its Customers and
> Sublicensees that the Licensed Item shall be free from defects in
> workmanship or design"
> Does OneForty understand that the "licensed item" is -software- and
> that software often contains bugs?  Who determines what a "defect in
> design" is?  OneForty?  Me?  Their lawyers?
>
> "Licensor further warrants to oneforty and its Customers and
> Sublicensees that the Licensed Item shall not contain any information
> or content of whatever nature that is defamatory, obscene, indecent,
> pornographic, seditious, offensive, threatening, liable to incite
> racial hatred, blasphemous..."
> "Blasphemous"?  Really?  So if my code includes a comment that states
> "I can't make this goddamn thing work", I'm violation of the
> contract.  "Offensive"?  To whom?
>
> "Licensor shall maintain reasonable insurance"
> Insurance?  I need to maintain insurance to claim my free, open-source
> Twitter client in OneForty's directory?
>
> "Licensor agrees that it will not use “oneforty”, “oneforty.com” or
> any other trademark held by oneforty in keyword meta tags or any pages
> of Licensor’s website or any website(s) owned or operated by
> Licensor."
> So, I can't have a link on my page that says "Check us out on
> OneForty!" or "We're listed on OneForty!" or "Post a review on
> OneForty!"
>
> Laura from OneForty has the best intentions, and I really believe that
> she wants to produce a developer-friendly community where everyone
> reaps benefits.  That's great, and I applaud her for her efforts to
> make this work.  This agreement (and the noxious one that preceded it)
> give me the impression that OneForty's lawyers have a fundamental
> ignorance of software, software development, and the internet in
> general.
>
>

[twitter-dev] Issue with API?

[eclipsed4utoo]

Does anybody know if there is an issue with the friends_timeline REST
method?  When I do it, it returns tweets from all of my friends.
However, the "following" XML tag is false.  How can that be?  They are
my friend if I am following them, correct?

http://twitter.com/statuses/friends_timeline.xml

and this is the first status that is returned.


Sat Oct 10 14:36:56 + 2009
4761273314

  Disk2vhd Turns Your PC Into a Virtual Machine: 
http://bit.ly/1z6lNa


http://www.tweetdeck.com/";
rel="nofollow">TweetDeck

false


false


 43065412
 George Dan Pirvu
 gamearchitect
 a giant cubicle
 
Programming games since 1997. Psychologist, internet
marketer, horrible chess player.
 
 
  
http://a3.twimg.com/profile_images/280718799/georgep_normal.jpg
 
 http://www.randombyte.com
 false
 7643
 9AE4E8
 33
 0084B4
 DDFFCC
 BDDCAD
 8148
 Thu May 28 07:08:07 + 2009
 0
 7200
 Bucharest
 
  
http://a3.twimg.com/profile_background_images/19709051/olivemanna_islandpalms.jpg
 
 true
 656
 false
 false
 false
 false




So how can that be?

[twitter-dev] Re: Have you read the OneForty.com Developer Contract?

[Duane Roelands]

No, no, a thousand times no.

"Licensor further warrants to oneforty and its Customers and
Sublicensees that the Licensed Item shall be free from defects in
workmanship or design"
Does OneForty understand that the "licensed item" is -software- and
that software often contains bugs?  Who determines what a "defect in
design" is?  OneForty?  Me?  Their lawyers?

"Licensor further warrants to oneforty and its Customers and
Sublicensees that the Licensed Item shall not contain any information
or content of whatever nature that is defamatory, obscene, indecent,
pornographic, seditious, offensive, threatening, liable to incite
racial hatred, blasphemous..."
"Blasphemous"?  Really?  So if my code includes a comment that states
"I can't make this goddamn thing work", I'm violation of the
contract.  "Offensive"?  To whom?

"Licensor shall maintain reasonable insurance"
Insurance?  I need to maintain insurance to claim my free, open-source
Twitter client in OneForty's directory?

"Licensor agrees that it will not use “oneforty”, “oneforty.com” or
any other trademark held by oneforty in keyword meta tags or any pages
of Licensor’s website or any website(s) owned or operated by
Licensor."
So, I can't have a link on my page that says "Check us out on
OneForty!" or "We're listed on OneForty!" or "Post a review on
OneForty!"

Laura from OneForty has the best intentions, and I really believe that
she wants to produce a developer-friendly community where everyone
reaps benefits.  That's great, and I applaud her for her efforts to
make this work.  This agreement (and the noxious one that preceded it)
give me the impression that OneForty's lawyers have a fundamental
ignorance of software, software development, and the internet in
general.

[twitter-dev] SMS Notifications

[Bob Thomson]

Can anyone confirm if there are ongoing issues with users registering
new devices or if anyone has had reports of users being sent SMS
messages even when they have SMS notifications turned off?

We're seeing several reports of the first and isolated reports of the
second from our users.

Thanks,

Bob

--

Founder, Twibbon.com

[twitter-dev] Re: Twitter API in 24 Hours

[Abraham Williams]

Just put a big *beta* sticker on the front.
On Sat, Oct 10, 2009 at 05:28, Andrew Badera  wrote:

>
> That could be said about a lot of technologies with books being
> published about them ...
>
> ∞ Andy Badera
> ∞ +1 518-641-1280
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me: http://www.google.com/search?q=andrew%20badera
>
>
>
> On Sat, Oct 10, 2009 at 6:26 AM, PJB  wrote:
> >
> >
> > 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 Oct 9, 2:42 pm, Andrew Mager  wrote:
> >> I am co-authoring a book about the Twitter API, and I was wondering if
> >> any of you guys wanted to write a chapter.
> >>
> >> The book will be in the SAMS 24 hour series, and it's scheduled to be
> >> released mid-next year.
> >>
> >> Here is our tentative table of contents:
> >>
> >> Introduction to Twitter
> >> An overview of Twitter and Microblogging
> >> Common Types of Twitter Applications
> >> Key Issues to Consider when Developing Twitter Apps
> >> Overview of Twitters's API structure
> >> The API is HTTP-based
> >> The API uses Representational State Transfer (REST)
> >> There are pagination limits
> >> The Twitter API supports UTF-8 encoding
> >> Getting Started with the API
> >> Setting up an environment
> >> Making your first API call
> >> Parsing the reply
> >> Message, date, author, image
> >> Creating a simple display
> >> Setting up an application framework
> >> Creating a twitter Class
> >> Various twitter libraries are available
> >> PHP Class used in this book
> >> Modifing our class
> >> Twitter Error messages
> >> What each error code means
> >> Modifing our twitter Class
> >> Passing credentials to twitter
> >> Standard method (HTTP)
> >> Using cookies (create, retrieve, delete)
> >> OAuth
> >> Sending and Receiving messages from Twitter
> >> Creating a basic twitter client
> >> Sending messages in twitter
> >> Twitter search
> >> Dealing with Twitter downtimes and errors
> >> Twitter Beyond the API
> >> Future of Twitter
> >> Example Applications
> >> Other Mashup Twitter Services
> >> Twitter Etiquette
> >>
> >> Ping me directly if you are interested! andrew.ma...@gmail.com
> >
>



-- 
Abraham Williams | Community Evangelist | http://web608.org
Hacker | http://abrah.am | http://twitter.com/abraham
Project | http://fireeagle.labs.poseurtech.com
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States

[twitter-dev] Re: Twitter API in 24 Hours

[Andrew Badera]

That could be said about a lot of technologies with books being
published about them ...

∞ Andy Badera
∞ +1 518-641-1280
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera



On Sat, Oct 10, 2009 at 6:26 AM, PJB  wrote:
>
>
> 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 Oct 9, 2:42 pm, Andrew Mager  wrote:
>> I am co-authoring a book about the Twitter API, and I was wondering if
>> any of you guys wanted to write a chapter.
>>
>> The book will be in the SAMS 24 hour series, and it's scheduled to be
>> released mid-next year.
>>
>> Here is our tentative table of contents:
>>
>> Introduction to Twitter
>> An overview of Twitter and Microblogging
>> Common Types of Twitter Applications
>> Key Issues to Consider when Developing Twitter Apps
>> Overview of Twitters's API structure
>> The API is HTTP-based
>> The API uses Representational State Transfer (REST)
>> There are pagination limits
>> The Twitter API supports UTF-8 encoding
>> Getting Started with the API
>> Setting up an environment
>> Making your first API call
>> Parsing the reply
>> Message, date, author, image
>> Creating a simple display
>> Setting up an application framework
>> Creating a twitter Class
>> Various twitter libraries are available
>> PHP Class used in this book
>> Modifing our class
>> Twitter Error messages
>> What each error code means
>> Modifing our twitter Class
>> Passing credentials to twitter
>> Standard method (HTTP)
>> Using cookies (create, retrieve, delete)
>> OAuth
>> Sending and Receiving messages from Twitter
>> Creating a basic twitter client
>> Sending messages in twitter
>> Twitter search
>> Dealing with Twitter downtimes and errors
>> Twitter Beyond the API
>> Future of Twitter
>> Example Applications
>> Other Mashup Twitter Services
>> Twitter Etiquette
>>
>> Ping me directly if you are interested! andrew.ma...@gmail.com
>

[twitter-dev] Re: Twitter API in 24 Hours

[PJB]

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 Oct 9, 2:42 pm, Andrew Mager  wrote:
> I am co-authoring a book about the Twitter API, and I was wondering if
> any of you guys wanted to write a chapter.
>
> The book will be in the SAMS 24 hour series, and it's scheduled to be
> released mid-next year.
>
> Here is our tentative table of contents:
>
> Introduction to Twitter
> An overview of Twitter and Microblogging
> Common Types of Twitter Applications
> Key Issues to Consider when Developing Twitter Apps
> Overview of Twitters's API structure
> The API is HTTP-based
> The API uses Representational State Transfer (REST)
> There are pagination limits
> The Twitter API supports UTF-8 encoding
> Getting Started with the API
> Setting up an environment
> Making your first API call
> Parsing the reply
> Message, date, author, image
> Creating a simple display
> Setting up an application framework
> Creating a twitter Class
> Various twitter libraries are available
> PHP Class used in this book
> Modifing our class
> Twitter Error messages
> What each error code means
> Modifing our twitter Class
> Passing credentials to twitter
> Standard method (HTTP)
> Using cookies (create, retrieve, delete)
> OAuth
> Sending and Receiving messages from Twitter
> Creating a basic twitter client
> Sending messages in twitter
> Twitter search
> Dealing with Twitter downtimes and errors
> Twitter Beyond the API
> Future of Twitter
> Example Applications
> Other Mashup Twitter Services
> Twitter Etiquette
>
> Ping me directly if you are interested! andrew.ma...@gmail.com

[twitter-dev] Re: Twitter API in 24 Hours

[Andrew Badera]

++ to what John said.

Also ... streaming? Ratelimiting? Whitelisting? How do @s work? Are
you going to cover Sign-in-with-Twitter? How about guns for cash? The
address book API? What about all the geolocation stuff?

Sheesh, I feel like I'm writing this for you. I'm going to stop now.
You're obviously missing a lot of the obvious.

∞ Andy Badera
∞ +1 518-641-1280
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera



On Fri, Oct 9, 2009 at 8:56 PM, John Meyer  wrote:
>
> I don't know if you have enough for a full book.  Even some of the chapters
> seem more like sub-sections at this point.
>
> Andrew Mager wrote:
>>
>> I am co-authoring a book about the Twitter API, and I was wondering if
>> any of you guys wanted to write a chapter.
>>
>> The book will be in the SAMS 24 hour series, and it's scheduled to be
>> released mid-next year.
>>
>> Here is our tentative table of contents:
>>
>> Introduction to Twitter
>> An overview of Twitter and Microblogging
>> Common Types of Twitter Applications
>> Key Issues to Consider when Developing Twitter Apps
>> Overview of Twitters's API structure
>> The API is HTTP-based
>> The API uses Representational State Transfer (REST)
>> There are pagination limits
>> The Twitter API supports UTF-8 encoding
>> Getting Started with the API
>> Setting up an environment
>> Making your first API call
>> Parsing the reply
>> Message, date, author, image
>> Creating a simple display
>> Setting up an application framework
>> Creating a twitter Class
>> Various twitter libraries are available
>> PHP Class used in this book
>> Modifing our class
>> Twitter Error messages
>> What each error code means
>> Modifing our twitter Class
>> Passing credentials to twitter
>> Standard method (HTTP)
>> Using cookies (create, retrieve, delete)
>> OAuth
>> Sending and Receiving messages from Twitter
>> Creating a basic twitter client
>> Sending messages in twitter
>> Twitter search
>> Dealing with Twitter downtimes and errors
>> Twitter Beyond the API
>> Future of Twitter
>> Example Applications
>> Other Mashup Twitter Services
>> Twitter Etiquette
>>
>> Ping me directly if you are interested! andrew.ma...@gmail.com
>>
>>
>
>

[twitter-dev] Re: twitter.com/followers/befriend_all ?

[Abraham Williams]

Fascinating. I don't remember ever hearing about this method. There are a
couple of references on the net:
http://www.google.com/search?hl=en&q="followers/befriend_all";
Abraham

On Fri, Oct 9, 2009 at 13:42, PJB  wrote:

>
>
> 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 having a bot call this regularily to
> > make sure your bot follows anyone following the bot... makes sense
> > (rather than getting all friends and all followers and issuing
> > seperate friend requests), however I see no reference to it on the
> > twitter api site.
> >
> > Is this legit?
> >
> > When I call it it just redirects to my home page.
> >
> > Rick...
>



-- 
Abraham Williams | Community Evangelist | http://web608.org
Hacker | http://abrah.am | http://twitter.com/abraham
Project | http://fireeagle.labs.poseurtech.com
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States

[twitter-dev] Re: where will we be next year

[Andrew Badera]

Note to you: post only when sober and relevant.

Note from us: thanks in advance.

∞ Andy Badera
∞ +1 518-641-1280
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera



On Fri, Oct 9, 2009 at 10:16 PM, tom  wrote:
>
> With the 2010 elections coming soon,and an angry electorate  I can see
> twitter playing an unheard of influence on these elections.. as i see
> it the tasks will be KEEP IT ACCURATE,keep it brief,and keep it
> relevant The pols are allready sitting up and taking notice,
> NOTE;;the 18 to 30 year old electors COULD CONTROL EVERY ELECTION,  if
> they chose to vote
>