Re: Are there any limitations on storing twitter data in a database?
On Nov 22, 1:35 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > Any restrictions on what you can store that's consumed via the REST > API or Search API is in our Terms of Service:http://twitter.com/terms This is the only relevant part I found in the Terms of Service: "The Twitter service makes it possible to post images and text hosted on Twitter to outside websites. This use is accepted (and even encouraged!). However, pages on other websites which display data hosted on Twitter.com must provide a link back to Twitter." So it seems that keeping a copy of (potentially large) parts of the social graph is fine. Amir > > On Sat, Nov 22, 2008 at 09:34, Amir Michail <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Can we store whatever we like in a database? > > > Are there any limitations on what can be stored and for how long? > > > Are there any rules against using stale data? > > > Amir > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
update_profile_colors changes will not work when a theme is selected
When I select a theme for my design (on the site), then update any color (background, text, link, etc) via the api no changes occur to my account. If I change any color manually via the site, then update colors via the api it works like it should. The strange thing about this is when accessing http://twitter.com/users/show/twitscribe.xml the color data is reflecting my update from the api even though the colors are incorrect when accessing my profile.
Re: Is update_profile_background_image not working?
If you're getting a 200 back I believe your request sent to twitter is correct. Go to Settings -> Design -> Change background image. You should see your uploaded image. Twitter is not showing custom background images updated through their api if a theme is selected. Unfortunately the only way to display the background image is to manually select it while logged in. I am running in to a similar situation when changing any of the design colors. On Nov 22, 5:46 pm, Max <[EMAIL PROTECTED]> wrote: > Hey guys - > > Working with the newish APIs for setting themes, and for some reason > update_profile_background_image is not setting the image. A couple of > things: > > - I believe my multipart is correct because I can use the exact same > request body to update my avatar using update_profile_image > - The response coming back is the equivalant of a show (that is, I am > not getting any response other than a 200). > > Also is there any timeline on the tile bit from October? > > Thanks guys - > > -Max
Re: a simple workaround for lack of OAuth
On Nov 23, 2:33 pm, TCI <[EMAIL PROTECTED]> wrote: > I find it better to get users to follow your account and then send > them a DM with a URL. Builds followers and eliminates errors from user > side. > R Are we allowed to have multiple accounts on twitter? If so, how many? Amir > > On Nov 22, 11:30 am, Amir Michail <[EMAIL PROTECTED]> wrote: > > > On Nov 22, 12:26 pm, "Chad Etzel" <[EMAIL PROTECTED]> wrote: > > > > This is a good method to verify (claim) an account, yes... but if you > > > wanted > > > them to be able to do any sort of authenticated request (like tweeting or > > > sending a direct message), you'd still need their password. That is, > > > unless > > > you are asking twitter to change the way their API works. > > > > By "future logins", do you mean to twitter? or to your service? > > > > -Chad > > > It would simplify future logins to my service over even OAuth. > > > The problem for me though is that without user-specific authentication > > (i.e., I use authentication under my account always), IP-based rate > > limiting is a severe problem making this at best a temporary solution. > > > Amir > > > > On Sat, Nov 22, 2008 at 12:22 PM, Amir Michail <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > One could just have the user enter an assigned code into the bio/url > > > > or even in a post (which would also help promote your service). Doing > > > > so would allow the user to "claim" the twitter account and associate > > > > it with his/her account in your service. > > > > > Unlike OAuth, this would even make future logins simpler. > > > > > Is this a reasonable way to go? > > > > > Amir
Re: a simple workaround for lack of OAuth
I find it better to get users to follow your account and then send them a DM with a URL. Builds followers and eliminates errors from user side. R On Nov 22, 11:30 am, Amir Michail <[EMAIL PROTECTED]> wrote: > On Nov 22, 12:26 pm, "Chad Etzel" <[EMAIL PROTECTED]> wrote: > > > This is a good method to verify (claim) an account, yes... but if you wanted > > them to be able to do any sort of authenticated request (like tweeting or > > sending a direct message), you'd still need their password. That is, unless > > you are asking twitter to change the way their API works. > > > By "future logins", do you mean to twitter? or to your service? > > > -Chad > > It would simplify future logins to my service over even OAuth. > > The problem for me though is that without user-specific authentication > (i.e., I use authentication under my account always), IP-based rate > limiting is a severe problem making this at best a temporary solution. > > Amir > > > > > On Sat, Nov 22, 2008 at 12:22 PM, Amir Michail <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > One could just have the user enter an assigned code into the bio/url > > > or even in a post (which would also help promote your service). Doing > > > so would allow the user to "claim" the twitter account and associate > > > it with his/her account in your service. > > > > Unlike OAuth, this would even make future logins simpler. > > > > Is this a reasonable way to go? > > > > Amir
Re: Python Twitter API Wrapper problem w/ Google app engine
On Nov 23, 3:15 pm, "Julio Biason" <[EMAIL PROTECTED]> wrote: > On 11/23/08, Amir Michail <[EMAIL PROTECTED]> wrote: > > > global User = , builtin id = > id>, data = u'request', data.get undefined, builtin None = None, name > > undefined, screen_name undefined, location undefined, description > > undefined, profile_image_url undefined, url undefined, status = None > > : 'unicode' object has no attribute > > 'get' > > > Any ideas on how to get this to work? > > Your "data" object is wrong. It's a string (with the content > 'request') and not a dictionary. > The authorization is rejected (response code 401) thus leading to this exception. Amir > -- > Julio Biason <[EMAIL PROTECTED]> > Twitter:http://twitter.com/juliobiason
Re: Python Twitter API Wrapper problem w/ Google app engine
On 11/23/08, Amir Michail <[EMAIL PROTECTED]> wrote: > global User = , builtin id = id>, data = u'request', data.get undefined, builtin None = None, name > undefined, screen_name undefined, location undefined, description > undefined, profile_image_url undefined, url undefined, status = None > : 'unicode' object has no attribute > 'get' > > Any ideas on how to get this to work? Your "data" object is wrong. It's a string (with the content 'request') and not a dictionary. -- Julio Biason <[EMAIL PROTECTED]> Twitter: http://twitter.com/juliobiason
Re: User Method Show "Friends" Down
It was likely an unrelated transient error. We're UTF-8 safe throughout. On Sat, Nov 22, 2008 at 21:51, DustyReagan <[EMAIL PROTECTED]> wrote: > > When it was down, I was getting the "Technical Error" robot page for > these 2 examples: > > http://twitter.com/statuses/friends/bob.xml?page=1 > http://twitter.com/statuses/friends/cesart.xml?page=3 > > They're working fine now, and I'm not getting anymore complaints on my > app. > > The only thing I noticed (after they came back up) is that the first > bio in (http://twitter.com/statuses/friends/bob.xml?page=1) had(has) a > star ★ in it. And (http://twitter.com/statuses/friends/cesart.xml? > page=3) someone's bio has a smiley face ☺ in it. And page 2 and 4 of > @cesart's friends don't seem to have any special characters in the > bios and they always worked. > > Not sure if the special characters was the problem, just something I > noticed. > > Dusty > > On Nov 22, 10:58 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> Could you provide examples? >> >> >> >> On Sat, Nov 22, 2008 at 20:24, DustyReagan <[EMAIL PROTECTED]> wrote: >> >> > Hmm... seems to be working now. >> >> > Could this have had something to do with the special characters in >> > peoples bios? Like the stars and faces and such? >> >> > On Nov 22, 3:46 pm, DustyReagan <[EMAIL PROTECTED]> wrote: >> >> It seems thathttp://twitter.com/statuses/friends/bob.xml?page=1is >> >> not working. >> >> >> I'm getting lots of complaints on FriendOrFollow.com from users seeing >> >> incorrect results. So it's not just "bob" with a broken page. Also, it >> >> doesn't appear to always be page 1. Sometimes it's a page in the >> >> middle like this example: >> >> >> WORKS =http://twitter.com/statuses/friends/cesart.xml?page=2 >> >> BROKEN =http://twitter.com/statuses/friends/cesart.xml?page=3 >> >> WORKS =http://twitter.com/statuses/friends/cesart.xml?page=4 >> >> >> I'm not sure if this is related to the "show_users" problem being >> >> discussed now also in the group. >> >> >> Dusty >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
