[twitter-dev] Re: List creation updated (needs description param)
I confirm this behavior, but I just added the description field to the input form and it works like a charm. And I find it useful as well. - @NeluLazar On Nov 19, 1:44 am, Rich rhyl...@gmail.com wrote: I can confirm this too, the lists are not being created without a description On Nov 19, 4:13 am, Naveen knig...@gmail.com wrote: We are seeing this issue as well.. We create a list with:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-POST-lists This is returning all valid data with an id for the list, which indicates it was successfully created.. However when we try to get status for the list it is returning 404 Then we try to get the lists using http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-lists And it is not returned in the result, the newly created list is also not on the twitter website.. however if we include the description parameter(with empty content) the list is created and returns expected data and does show up on the twitter website.. There is a bug here... The work around is to just include an empty description field, which should not break anything in the future either. On Nov 18, 8:08 pm, Marcel Molina mar...@twitter.com wrote: The description parameter is not required to create a list. On Wed, Nov 18, 2009 at 3:57 PM, David dch...@gmail.com wrote: I've been using the List api in my app, and just noticed that the POST method to /:user/lists.:format returned the correct response, but didn't actually create a list. I've been following this api document:http://apiwiki.twitter.com/Twitter-REST-API-Method:-POST-lists What I did notice was that the Add New List ui on Twitter.com has a description field, and so I tried the same call with an additional post param description, and it worked. The description param can be empty, but it is required to make this call work. Might be a bug? Just a heads up for anyone who might be wondering. DC -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: How to find out which of your lists someone is a member of.
You may use GET /:user/:list_id/members/:id as an option: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-list-members-id - @NeluLazar On Nov 12, 9:13 am, tom tswool...@gmail.com wrote: Hi All, I'm looking for a way to get which of my lists (public and private) a user is a member of - akin to the lists drop-down on a user's profile on Twitter.com. Is this information available in an easier way than calling GET list members id for each list (or, more specifically, using less API calls)? Thanks, Tom
[twitter-dev] Incorrect signature returned for Lists API
I am experiencing Incorrect signature responses while requesting any Lists API XMLs. hash request/tweetvisor/lists/subscriptions.xml/request errorIncorrect signature/error /hash I tried various methods, with no success: POST, GET, HTTPS (default), HTTP. It only happens to Lists API calls, all other released API calls are working fine. If anyone know what's going on, please advise. Thanks, - @NeluLazar
[twitter-dev] Re: Incorrect signature returned for Lists API
Figured the answer for the issue above, for @jmathai's EPITwitter
library, here is the call code that works:
$twitterOAuthObj-{'get_'.(string)strtolower
($username).'ListsMemberships'}(array(...));
- @NeluLazar
On Nov 2, 10:37 am, Nelu Lazar cont...@nelulazar.com wrote:
I am experiencing Incorrect signature responses while requesting any
Lists API XMLs.
hash
request/tweetvisor/lists/subscriptions.xml/request
errorIncorrect signature/error
/hash
I tried various methods, with no success: POST, GET, HTTPS (default),
HTTP. It only happens to Lists API calls, all other released API calls
are working fine.
If anyone know what's going on, please advise. Thanks,
- @NeluLazar
[twitter-dev] Re: Incorrect signature returned for Lists API
And an update fot the EPI library: http://bit.ly/3KODt1
On Nov 2, 10:53 am, Nelu Lazar cont...@nelulazar.com wrote:
Figured the answer for the issue above, for @jmathai's EPITwitter
library, here is the call code that works:
$twitterOAuthObj-{'get_'.(string)strtolower
($username).'ListsMemberships'}(array(...));
- @NeluLazar
On Nov 2, 10:37 am, Nelu Lazar cont...@nelulazar.com wrote:
I am experiencing Incorrect signature responses while requesting any
Lists API XMLs.
hash
request/tweetvisor/lists/subscriptions.xml/request
errorIncorrect signature/error
/hash
I tried various methods, with no success: POST, GET, HTTPS (default),
HTTP. It only happens to Lists API calls, all other released API calls
are working fine.
If anyone know what's going on, please advise. Thanks,
- @NeluLazar
[twitter-dev] Re: Best way to implement caching of searches (with multithreading)?
Try memcached. - @NeluLazar On Oct 2, 7:36 am, Bjoern bjoer...@googlemail.com wrote: Hi, just wondering about a best practice thing. Suppose I show results of specific Twitter searches on a web site. How would I go about caching the searches? The naive approach seems to be to first check in my own database, then do a twitter search with the since_id parameter to only get results I don't already have. Then store the results from twitter in the database, too, and return the merged results to the web site. The problem I see is that if multiple user run the same search on my web site, threading issues might occur (as each user starts a separate thread on my server). Not only could multiple twitter searches with the same since_id be executed (maybe forgivable), but trouble starts when said results are to be inserted in my local database. Different threads could attempt to insert the same messages into my database. One simple solution I could imagine: just use the message ids from twitter as the primary key in my local database. That way, multiple threads saving the same message would just overwrite the message with itself. I actually wonder if that is a common solution - to use the twitter ids as primary keys (also for users, direct messages...). I have kind of arrived at the opinion that this would be the way of least resistance, although I feel a bit uneasy about it. An alternative that came to my mind might be to have single threaded background jobs do the copying of the search results from twitter to my database, and only show the results from my cache to the web site. This would cause some lag in the time the search results would appear, but it would not be too bad. However, if I have a lot of different searches, it would become infeasible to update all of them periodically. It would become necessary to only trigger an update when a user does the search. At that point things might get overly complicated: presumably I would need some kind of Ajax solution to trigger the caching with the first request, show a spinner while the updating of my local db is going on, and then show the results from my local cache/db. The trickiest part being to prevent the starting of multiple update tasks for the same search. All in all the simple solution might be the better way to go? Would be interested in hearing your opinions, experiences and solutions! Thanks! Björn
[twitter-dev] Re: Social Graph Methods followers/names ?
I subscribe to this request. Usernames in social graph methods' responses could be useful for many other implementations. @NeluLazar Tweetvisor.com On Sep 29, 7:22 am, Thomas Hübner thueb...@gmx.de wrote: Hi All, would it be possible to get an additional API function which delivers the screennames instead of ID's? The reason is, I work on a Client App in .NET On Startup I load the followers, friends and blocked ID's. I use this to show the status then in my application and enable/ disable the menus with follow/ unfollw DM and so on. So I save expensive API calls (follow someone which I already follow) which ends in API Errors. So far so good. Now I try to implement the search API. This delivers me ATOM XML back. I Try to fill my status object and included User object with the less informations in delivered ATOM to show it in the same Quality like a User Timeline. Unfortunately the only thing I have in ATOM result is the screenname combined with username in one tag. No Problem I resolve that with RegEx. What urgently is missed is the user ID to compare it with the followers and friend list of ID's Now 2 solutions are possible: 1) adding the userID in the search results 2) offer an API call within social graph methods which delivers screennames In case of 2) I could use the unique screenname as Key. This would be a disadvantage because of searchroutines work always slower on string. Better soulution would be to delivers the userID within the searchresults. Is there any way to realize this? I do not think that I'm the only one ho miss this. Best regards, Thomas
[twitter-dev] Re: About the oneforty application directory
I have checked the directory past days, and claimed my app. Congrats on a work very well done. A couple of suggestions: - the site doesn't currently allow new lines in the description field; this could be useful for listing features; - although it's understandable why the directory requires user's authentication, specific pages of the website may be more useful if public, to allow new users to familiarize with Twitter's capabilities and the apps around it. I live near Chicago, any chance you will add it to your tour? Nelu Lazar Founder Tweetvisor.com http://twitter.com/nelulazar On Sep 24, 3:24 pm, Alex Payne a...@twitter.com wrote: Just wanted to pass on a note from the team at oneforty.com, who recently launched with over 1300 Twitter applications in their directory. Your app might already be on their site. If it's not yet, you can register as a developer and add it. Once you register and claim your app you can promote it with screenshots, descriptions, tags, and reviews. If you saw the early alpha version of oneforty, it's much improved - real home page, most popular apps ranking and essentials. New item pages just launched and look much better than the prototype did. Their team working on the ability to sell apps right on the site. They're also definitely looking for your feedback. @freerobby, @graysky, @macasek, and @pistachio are often in the #twitterapi IRC channel. There's more contact info below, too. A note from the oneforty team and info on how to register, claim, edit add stuff: We built oneforty to help the best stuff being built on the Twitter API get found and get profitable. Come claim your apps, add content and add new projects in the Twitter appstore oneforty.com To get started: Sign in via oauth. (We whitelisted as many dev usernames as we could find. If you can't login already use invite code TWAPI and we'll let you right in.) Register as a developer:http://oneforty.com/me/developer_profile Search for and claim your app (Suggest Item if we don't have it yet!) Check out your item's page, make sure it's tagged well, tweet a link to it, etc Once approved, add details, screenshots, media coverage and more In the near future you'll be able to offer things for sale right in oneforty. For now we link to your sites and (optionally) let you collect donations. We want to help you get your app found, rated, reviewed and into the hands of the users who need it the most. We also want to get the Twitter community to do a better job supporting developers and apps so that your innovation can flourish. It's frustrating when great apps go defunct because of server costs, etc. We're anticipating decent blog and press coverage, so we want your to look its best! Please let us know whatever we can do to help you. Thank you. We'd really love to know what you think and what you want: Uservice feedback forum. Any questions at all, develop...@oneforty.com or 617-645-7767, anytime. oneforty Founder Laura (@Pistachio) Fitton will be at events in Fort Worth 9/25, Seattle 9/26-27, SF/bay area 9/27-30 and Boston 10/1 and would love to meet you (seehttp://bit.ly/tour140for Tweetup event info). She also wrote Twitter for Dummies. Check 'em out! -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Frequent 503/Over Capacity/Server Unavailable Errors
Hi,
I use EpiOAuth for my Twitter dashboard application hosted on a
dedicated server, jmathai's async cURL Twitter class, memcached for
caching responses.
Almost every day, more frequently past days/weeks, my server logs API
errors that literally drives the site down, requiring the server to be
restarted in order to be accessible again. It looks like async cURL
doesn't stop for a client after a few seconds due to API
unavailability, but it continues to run until it receives something,
most likely after other connections have been requested, filling the
queue.
Since my application is kneed almost every time these API errors
occur, I would like to know if anyone experiences the same problems
and if you know any workaround or a solution to cURL blocking server
with requests.
For Twitter support, please let me know how should an app handle these
errors best, I am opened to any suggestions.
Frequent errors are:
1. HTTP Server Error 503 - No available server to handle this request
[Wed Sep 09 01:01:01 2009] [error] [client xx.xxx.xxx.xxx] PHP Fatal
error: Uncaught exception 'EpiOAuthException' with message
'htmlbodyh2HTTP Server Error 503/h2p No available server to
handle this request /p/body/html' in /tweetvisor.com/httpdocs/
classes/EpiOAuth.php:335\nStack trace:\n#0 /tweetvisor.com/httpdocs/
classes/EpiOAuth.php(312): EpiOAuthException::raise
('htmlbodyh2...', 503)\n#1 /tweetvisor.com/httpdocs/classes/
EpiOAuth.php(38): EpiOAuthResponse-__get('oauth_token')\n#2 /
tweetvisor.com/httpdocs/oauth_init.php(103): EpiOAuth-
getAuthenticateUrl()\n#3 /tweetvisor.com/httpdocs/includes.php(197):
include_once('/tweetvisor.com/tweetvisor.com/...')\n#4 /tweetvisor.com/
httpdocs/ajax_twitter_showonlineusers.php(2): require_once('/...')\n#5
{main}\n thrown in /tweetvisor.com/httpdocs/classes/EpiOAuth.php on
line 335, referer: http://tweetvisor.com/
2. Twitter / Over capacity
[Mon Sep 07 01:24:54 2009] [error] [client xx.xxx.xxx.xxx] PHP Fatal
error: Uncaught exception 'EpiOAuthException' with message '!DOCTYPE
html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://
www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\nhtml
xmlns=http://www.w3.org/1999/xhtml; lang=en xml:lang=en\n head
\n \tmeta http-equiv=Content-Type content=text/html;
charset=utf-8 /\n \tmeta http-equiv=Content-Language content=en-
us /\n \ttitleTwitter / Over capacity/title\n \tlink
rel=icon href=http://static.twitter.com/favicon.ico; type=image/
ico /\n \tstyle type=text/css\nbody{background:#9AE4E8 url
(http://s.twimg.com/images/bg.gif) no-repeat fixed left
top;color:#333;font:0.75em Helvetica,Arial,sans-serif;text-
align:center}\n#container { width: 755px; margin: 0 auto; padding:
0px 0; text-align: left; position: relative; }\n#content { width:
100%; margin-top: 0px; float: left; padding-bottom: 15px; background:
transparent url(http://s.twimg.com/images/arr2.gif) no-repeat scroll
25px 0px;}\n.subpage #content .wrapper { background-color: # in /
tweetvisor.com/httpdocs/classes/EpiOAuth.php on line 335, referer:
http://tweetvisor.com/
3. Twitter / Error
[Mon Sep 07 02:02:17 2009] [error] [client xxx.xx.xxx.xxx] PHP Fatal
error: Uncaught exception 'EpiOAuthException' with message '!DOCTYPE
html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://
www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\nhtml
xmlns=http://www.w3.org/1999/xhtml; lang=en xml:lang=en\n head
\n \tmeta http-equiv=Content-Type content=text/html;
charset=utf-8 /\n \tmeta http-equiv=Content-Language content=en-
us /\n \ttitleTwitter / Error/title\n \tlink rel=icon
href=http://static.twitter.com/favicon.ico; type=image/ico /\n
\tstyle type=text/css\nbody{background:#9AE4E8 url(http://
s.twimg.com/images/bg.gif) no-repeat fixed left top;color:#333;font:
0.75em Helvetica,Arial,sans-serif;text-align:center}\n#container
{ width: 755px; margin: 0 auto; padding: 0px 0; text-align: left;
position: relative; }\n#content { width: 100%; margin-top: 0px;
float: left; padding-bottom: 15px; background: transparent url(http://
s.twimg.com/images/arr2.gif) no-repeat scroll 25px 0px;}\n.subpage
#content .wrapper { background-color: #fff; pad in /tweetvisor.com/
httpdocs/classes/EpiOAuth.php on line 335, referer: http://tweetvisor.com/
Thanks,
- @NeluLazar
