[twitter-dev] Problems with authentication [Java/Scala, Apache HttpClient]

2009-11-11 Thread Ted Neward
I’ve written a Twitter client library in Scala (a JVM-based
object/functional language) that uses Apache HttpClient to connect to the
Twitter servers, but now (while at a conference here in Munich) the Basic
HTTP authentication fails with a 401 and no other error message that I can
see. The HttpClient library *seems* to be sending the right information in
the right headers, and I know the authentication credentials work because I
can Curl to the page successfully. (This also means that the problem,
obviously, isn’t Twitter’s fault, at least as far as I can see.)

 

If you’ve worked with the Twitter API from Apache HttpClient in Java, can
you please ping me off-list? (Or, assuming the conversation isn’t considered
noise, on-list is fine, too.) I could use some ideas on how to successfully
debug the problem I’m having.

 

One other question vis-à-vis authentication: for Basic authentication,
should the realm be “Twitter API” (which is what Twitter sends back from a
successful Curl invocation), or should it be nothing at all? I’ve seen
examples that do both, and would like to do “the right thing”, whatever that
is. (It seems to make no difference with my authentication woes, either
way.)

 

Thanks!

 

Ted Neward

Java, .NET, XML Services

Consulting, Teaching, Speaking, Writing

 http://www.tedneward.com http://www.tedneward.com

 

 



[twitter-dev] Re: Alert: Twitpocalypse II coming Friday, September 11th - make sure you can handle large status IDs!

2009-09-10 Thread Ted Neward

What is the documented range for status IDs? (How high can they go?)

Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com

 -Original Message-
 From: twitter-development-talk@googlegroups.com [mailto:twitter-
 development-t...@googlegroups.com] On Behalf Of Alex Payne
 Sent: Wednesday, September 09, 2009 1:01 PM
 To: twitter-development-talk@googlegroups.com
 Subject: [twitter-dev] Re: Alert: Twitpocalypse II coming Friday,
 September 11th - make sure you can handle large status IDs!
 
 
 Sorry, an error in phrasing. It was previously mentioned that this
 change was pending. We had not previously announced a date for the
 change.
 
 Normally, we prefer to provide more advance notice where possible, but
 I'm letting you all know immediately after our operations team
 informed me that it was necessary to make this change on Friday.
 
 On Wed, Sep 9, 2009 at 12:13, Hwee-Boon Yarhweeb...@gmail.com wrote:
 
  May I know when and where was it mentioned that it will be
  artificially increased this coming Friday?
 
  --
  Hwee-Boon
 
  On Sep 10, 2:49 am, Alex Payne a...@twitter.com wrote:
  As mentioned previously, the Twitter operations team
 willartificially
  increase the maximum status ID to 4294967296 this coming Friday,
  September 11th. This action is part of routine database upgrades and
  maintenance.
 
  If your Twitter API application stores status IDs, please be sure
 that
  your datastore is configured to handle integers of that size.
 Thanks.
 
  --
  Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
 
 
 
 
 --
 Alex Payne - Platform Lead, Twitter, Inc.
 http://twitter.com/al3x



[twitter-dev] Re: Is twitter a fad or worth development efforts?

2009-09-03 Thread Ted Neward

Kinda asking the wrong group, aren't you?

Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
 


 -Original Message-
 From: twitter-development-talk@googlegroups.com [mailto:twitter-
 development-t...@googlegroups.com] On Behalf Of ka...@sbcglobal.net
 Sent: Thursday, September 03, 2009 9:42 AM
 To: Twitter Development Talk
 Subject: [twitter-dev] Is twitter a fad or worth development efforts?
 
 
 Is twitter a fad or worth development efforts?



[twitter-dev] Cookie warning

2009-09-03 Thread Ted Neward
Hey, all. When I use Jakarta Commons' HttpClient to access Twitter, I get a
warning about the cookie usage:

 

WARNING: Cookie rejected: $Version=0;
_twitter_sess=BAh7CzoRdHJhbnNfcHJvbXB0MDo

OcmV0dXJuX3RvIjRodHRwOi8vdHdpdHRl%250Aci5jb20vc3RhdHVzZXMvc2hvdy8zNzQ0NDIyMD
U2Ln

htbDoTcGFzc3dvcmRf%250AdG9rZW4iLTA4MTMxNWJiZjY3MDE5OWE0NzBmMDllNTVmNDc0N2Y0M
WI4M

DJj%250AZTM6CXVzZXJpBPhCOgQ6B2lkIiUyY2NkMGU1MWMyNmQ3MDcwN2U5Mzk0ZWZj%250AMDY
zMGE

yNiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZs%250AYXNoSGFzaHsABjoKQH
VzZW

R7AA%253D%253D--226af2aba32531a2d066cba43b24e347f3c2293e; $Path=/;
$Domain=.twit

ter.com. Illegal domain attribute .twitter.com. Domain of origin:
twitter.co

m

 

The code I'm using I think is OK; anybody else seen anything like this? Any
interpretation of what I might be doing wrong?

 

Ted Neward

Java, .NET, XML Services

Consulting, Teaching, Speaking, Writing

http://www.tedneward.com

 

 

 



[twitter-dev] Either destroy is/was failing, or my understanding of destroy is/was failing

2009-09-02 Thread Ted Neward
I've been hacking on the Twitter API, and I'm running into some serious
weirdness with destroy.

 

I post a message:

 

C:\ curl -u name:pass -d status=Testing
http://twitter.com/statuses/update.xml

?xml version=1.0 encoding=UTF-8?

status

  created_atWed Sep 02 10:10:23 + 2009/created_at

  id3708721364/id

  textTesting/text

  sourcelt;a href=quot;http://apiwiki.twitter.com/quot;
rel=quot;nofollowquot;gt;APIlt;/agt;/source

  truncatedfalse/truncated

  in_reply_to_status_id/in_reply_to_status_id

  in_reply_to_user_id/in_reply_to_user_id

  favoritedfalse/favorited

  in_reply_to_screen_name/in_reply_to_screen_name

  user

id70927096/id

nameTed Neward/name

screen_nameTestingScitter/screen_name

location/location

description/description

 
profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_no
rmal.png/profile_image_url

url/url

protectedfalse/protected

followers_count1/followers_count

profile_background_color9ae4e8/profile_background_color

profile_text_color00/profile_text_color

profile_link_colorff/profile_link_color

profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color

profile_sidebar_border_color87bc44/profile_sidebar_border_color

friends_count6/friends_count

created_atWed Sep 02 09:49:13 + 2009/created_at

favourites_count0/favourites_count

utc_offset/utc_offset

time_zone/time_zone

 
profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/
theme1/bg.gif/profile_background_image_url

profile_background_tilefalse/profile_background_tile

statuses_count4/statuses_count

notificationsfalse/notifications

verifiedfalse/verified

followingfalse/following

  /user

/status

 

. which is all good, but then I try to delete that message:

 

C:\ curl -u name:pass --http-request DELETE
http://twitter.com/statuses/destroy/3708721364.xml

?xml version=1.0 encoding=UTF-8?

hash

  request/statuses/destroy/3708721364.xml/request

  errorWe could not delete that status for some reason./error

/hash

 

 

What gives? Is this something that I'm doing wrong on my end? Momentary
server weirdness? (Though it seems to have been pretty consistent all
night.)

 

Ted Neward

Java, .NET, XML Services

Consulting, Teaching, Speaking, Writing

 http://www.tedneward.com http://www.tedneward.com