[twitter-dev] Re: New idea for twitter development
You can also try out HootSuite.com, helps you managing multiple profiles without logging in and out On Jun 21, 3:34 am, M1Sh0u wrote: > HI, I'm Mihai Matei, WEB Developer from Romania > > I have a new idea that could be implemented on twitter. The idea is > that any user can create secondary accounts. What that's means? Each > user can manage his accounts from the main account which is the first > account created. > > That help the user not to log out and after that log in to another > account. He can change his accounts from a top page select. > > What do you think about this idea ? > > Thanks and sorry for my bad english :)
[twitter-dev] Re: timestamps as Array keys in "trend currents"
I actually figured it out with some help through the #iphonedev IRC channel. If you enumerate through the result. You can get it no problem. for each (var item:Object in json_obj.trends) or such. Good luck. On May 14, 8:10 pm, techyJoe wrote: > I have a problems with the some API methods: specifically, "trend > current" , "trenddaily, and "trendweekly" methods.For starters, my > code will retrieve the JSON string containing the "trendcurrent" > json string. Using Curl, the Json string response is captured and > decode into a phparrayusing the json_decode() function in php. > > My problem seems to come from some of thearraykeys that were > generated; specifically, the timestampsarraykeys , for example, > ['2009-5-14] or ['2009-5-14 4:49:15]( these are just examples). I > know they are generated from 'Unix' timestamps, and I can generate > them independently. however, my question is: How can I duplicate and > access thesearraykeys? > > Any help would be very much appreciated
[twitter-dev] Re: Users not being indexed by Search
Ok, one more: - Posting duplicate content (links or tweets) This is a tactic that some "twitter celebrities" say is a good practice. I'm not saying that I agree or disagree, but ppl may get mixed messages... but, obviously you make the rules. -Chad On Mon, Jun 22, 2009 at 8:42 PM, Chad Etzel wrote: > Thanks for the link. One comment about one of the bullet points that > may get you un-indexed: > > - Misuse of hashtags (words followed by the '#' sign) > > Most (nearly all) of the complaints that Brooks and I got were from > people that participate in twitter chats (which necessitate the use of > hashtags). I obviously have no view into your heuristic weighting of > this bullet point, but I hope that this one doesn't carry much weight, > or at least has the smarts to not punish people for using only one > hashtag per tweet (spammers use lots per tweet). > > So, if people still find themselves un-indexed, is the MO to tell them > to open a support ticket and hope for the best? > > -Chad > > > > > On Mon, Jun 22, 2009 at 8:34 PM, Doug Williams wrote: >> Here is the help link [1] we now give to users when vanity searches do not >> return the expected results. >> >> 1. http://help.twitter.com/forums/10713/entries/42646 >> >> Thanks, >> Doug >> >> >> >> On Fri, Jun 19, 2009 at 7:08 AM, Doug Williams wrote: >>> >>> We have plenty of data, now. Thanks for everyone who sent usernames my >>> way. The fix is going to take some time as it requires rewriting algorithms >>> so we appreciate your patience. >>> >>> Thanks, >>> Doug >>> >>> >>> >>> >>> On Thu, Jun 18, 2009 at 6:23 PM, Brooks Bennett >>> wrote: Should we still be sending these? Any new insight on what is happening? The issue seems to have been growing over the past week where almost all of my support requests for my app are about this issue... Brooks On Jun 16, 7:59 pm, Doug Williams wrote: > Chad, > Let's see what light the article sheds and work from there. > > Send me false-positives in private so that I can share them with our > scientist. > > Thanks, > Doug > > > > On Tue, Jun 16, 2009 at 5:55 PM, Chad Etzel > wrote: > > > Thanks. Even after sending the first email, I got about 5 or 6 other > > complaints about the same thing. It just seems strange that so many > > are getting flagged... people I know, even. I know you can't divulge > > your algorithm, so I won't ask... > > > -Chad > > > On Tue, Jun 16, 2009 at 8:41 PM, Doug Williams > > wrote: > > > We exclude users from the search index if they are performing > > > behaviors > > that > > > are outside of our TOS or if they look spammy to our support staff > > > or > > > algorithms. The support folks are writing up an article for > > >http://help.twitter.comto explain this policy. I'll drop the link > > > here > > when > > > that is available. > > > > Thanks, > > > Doug > > > > -- > > > Do you follow me?http://twitter.com/dougw > > > > On Tue, Jun 16, 2009 at 10:27 AM, Brooks Bennett > > > > > > wrote: > > > >> I sent this to @twitterapi as well: > > >>http://twitter.com/BrooksBennett/status/2191822737 > > > >> Here are some people pondering the occurrence: > > > >>http://twitter.com/Sideache/statuses/2188774064 > > >>http://twitter.com/LynnMaudlin/statuses/2188727280 > > > >> This has been an issue off and on for about a month, but in the > > >> last > > >> few days it has really escalated. > > > >> Brooks > > > >> On Jun 16, 11:29 am, Chad Etzel wrote: > > >> > Hi Matt/Doug, > > > >> > In the last week or so, I've been getting a lot of complaints > > >> > from > > >> > TweetGrid users that people are not showing up in their > > >> > searches. > > >> > They automatically assume it's TweetGrid's fault and lob a > > >> > complaint > > >> > my way. I go verify that the user in question has stopped being > > >> > indexed by Search and then reply to them that this is the case > > >> > and > > >> > that they should open a support ticket with Twitter. > > > >> > This is somewhat time consuming and tedious. I'm not sure how > > >> > to ask > > >> > for a solution to this situation. I guess I just wanted to > > >> > express > > >> > that people are more actively starting to notice when people do > > >> > not > > >> > appear in search results. I have no idea why people are being > > >> > dropped > > >> > from indexing (I check each account manually), but is this a > > >> > very > > >> > common thing to flip the admin bit to block people from search? > > > >> > -Chad >>> >> >> >
[twitter-dev] Re: Users not being indexed by Search
Thanks for the link. One comment about one of the bullet points that may get you un-indexed: - Misuse of hashtags (words followed by the '#' sign) Most (nearly all) of the complaints that Brooks and I got were from people that participate in twitter chats (which necessitate the use of hashtags). I obviously have no view into your heuristic weighting of this bullet point, but I hope that this one doesn't carry much weight, or at least has the smarts to not punish people for using only one hashtag per tweet (spammers use lots per tweet). So, if people still find themselves un-indexed, is the MO to tell them to open a support ticket and hope for the best? -Chad On Mon, Jun 22, 2009 at 8:34 PM, Doug Williams wrote: > Here is the help link [1] we now give to users when vanity searches do not > return the expected results. > > 1. http://help.twitter.com/forums/10713/entries/42646 > > Thanks, > Doug > > > > On Fri, Jun 19, 2009 at 7:08 AM, Doug Williams wrote: >> >> We have plenty of data, now. Thanks for everyone who sent usernames my >> way. The fix is going to take some time as it requires rewriting algorithms >> so we appreciate your patience. >> >> Thanks, >> Doug >> >> >> >> >> On Thu, Jun 18, 2009 at 6:23 PM, Brooks Bennett >> wrote: >>> >>> Should we still be sending these? Any new insight on what is >>> happening? >>> >>> The issue seems to have been growing over the past week where almost >>> all of my support requests for my app are about this issue... >>> >>> Brooks >>> >>> On Jun 16, 7:59 pm, Doug Williams wrote: >>> > Chad, >>> > Let's see what light the article sheds and work from there. >>> > >>> > Send me false-positives in private so that I can share them with our >>> > scientist. >>> > >>> > Thanks, >>> > Doug >>> > >>> > >>> > >>> > On Tue, Jun 16, 2009 at 5:55 PM, Chad Etzel >>> > wrote: >>> > >>> > > Thanks. Even after sending the first email, I got about 5 or 6 other >>> > > complaints about the same thing. It just seems strange that so many >>> > > are getting flagged... people I know, even. I know you can't divulge >>> > > your algorithm, so I won't ask... >>> > >>> > > -Chad >>> > >>> > > On Tue, Jun 16, 2009 at 8:41 PM, Doug Williams >>> > > wrote: >>> > > > We exclude users from the search index if they are performing >>> > > > behaviors >>> > > that >>> > > > are outside of our TOS or if they look spammy to our support staff >>> > > > or >>> > > > algorithms. The support folks are writing up an article for >>> > > >http://help.twitter.comto explain this policy. I'll drop the link >>> > > > here >>> > > when >>> > > > that is available. >>> > >>> > > > Thanks, >>> > > > Doug >>> > >>> > > > -- >>> > > > Do you follow me?http://twitter.com/dougw >>> > >>> > > > On Tue, Jun 16, 2009 at 10:27 AM, Brooks Bennett >>> > > > >>> > > > wrote: >>> > >>> > > >> I sent this to @twitterapi as well: >>> > > >>http://twitter.com/BrooksBennett/status/2191822737 >>> > >>> > > >> Here are some people pondering the occurrence: >>> > >>> > > >>http://twitter.com/Sideache/statuses/2188774064 >>> > > >>http://twitter.com/LynnMaudlin/statuses/2188727280 >>> > >>> > > >> This has been an issue off and on for about a month, but in the >>> > > >> last >>> > > >> few days it has really escalated. >>> > >>> > > >> Brooks >>> > >>> > > >> On Jun 16, 11:29 am, Chad Etzel wrote: >>> > > >> > Hi Matt/Doug, >>> > >>> > > >> > In the last week or so, I've been getting a lot of complaints >>> > > >> > from >>> > > >> > TweetGrid users that people are not showing up in their >>> > > >> > searches. >>> > > >> > They automatically assume it's TweetGrid's fault and lob a >>> > > >> > complaint >>> > > >> > my way. I go verify that the user in question has stopped being >>> > > >> > indexed by Search and then reply to them that this is the case >>> > > >> > and >>> > > >> > that they should open a support ticket with Twitter. >>> > >>> > > >> > This is somewhat time consuming and tedious. I'm not sure how >>> > > >> > to ask >>> > > >> > for a solution to this situation. I guess I just wanted to >>> > > >> > express >>> > > >> > that people are more actively starting to notice when people do >>> > > >> > not >>> > > >> > appear in search results. I have no idea why people are being >>> > > >> > dropped >>> > > >> > from indexing (I check each account manually), but is this a >>> > > >> > very >>> > > >> > common thing to flip the admin bit to block people from search? >>> > >>> > > >> > -Chad >> > >
[twitter-dev] Re: Users not being indexed by Search
Here is the help link [1] we now give to users when vanity searches do not return the expected results. 1. http://help.twitter.com/forums/10713/entries/42646 Thanks, Doug On Fri, Jun 19, 2009 at 7:08 AM, Doug Williams wrote: > We have plenty of data, now. Thanks for everyone who sent usernames my way. > The fix is going to take some time as it requires rewriting algorithms so we > appreciate your patience. > > Thanks, > Doug > > > > > > On Thu, Jun 18, 2009 at 6:23 PM, Brooks Bennett wrote: > >> >> Should we still be sending these? Any new insight on what is >> happening? >> >> The issue seems to have been growing over the past week where almost >> all of my support requests for my app are about this issue... >> >> Brooks >> >> On Jun 16, 7:59 pm, Doug Williams wrote: >> > Chad, >> > Let's see what light the article sheds and work from there. >> > >> > Send me false-positives in private so that I can share them with our >> > scientist. >> > >> > Thanks, >> > Doug >> > >> > >> > >> > On Tue, Jun 16, 2009 at 5:55 PM, Chad Etzel >> wrote: >> > >> > > Thanks. Even after sending the first email, I got about 5 or 6 other >> > > complaints about the same thing. It just seems strange that so many >> > > are getting flagged... people I know, even. I know you can't divulge >> > > your algorithm, so I won't ask... >> > >> > > -Chad >> > >> > > On Tue, Jun 16, 2009 at 8:41 PM, Doug Williams >> wrote: >> > > > We exclude users from the search index if they are performing >> behaviors >> > > that >> > > > are outside of our TOS or if they look spammy to our support staff >> or >> > > > algorithms. The support folks are writing up an article for >> > > >http://help.twitter.comto explain this policy. I'll drop the link >> here >> > > when >> > > > that is available. >> > >> > > > Thanks, >> > > > Doug >> > >> > > > -- >> > > > Do you follow me?http://twitter.com/dougw >> > >> > > > On Tue, Jun 16, 2009 at 10:27 AM, Brooks Bennett < >> bsbenn...@gmail.com> >> > > > wrote: >> > >> > > >> I sent this to @twitterapi as well: >> > > >>http://twitter.com/BrooksBennett/status/2191822737 >> > >> > > >> Here are some people pondering the occurrence: >> > >> > > >>http://twitter.com/Sideache/statuses/2188774064 >> > > >>http://twitter.com/LynnMaudlin/statuses/2188727280 >> > >> > > >> This has been an issue off and on for about a month, but in the >> last >> > > >> few days it has really escalated. >> > >> > > >> Brooks >> > >> > > >> On Jun 16, 11:29 am, Chad Etzel wrote: >> > > >> > Hi Matt/Doug, >> > >> > > >> > In the last week or so, I've been getting a lot of complaints >> from >> > > >> > TweetGrid users that people are not showing up in their searches. >> > > >> > They automatically assume it's TweetGrid's fault and lob a >> complaint >> > > >> > my way. I go verify that the user in question has stopped being >> > > >> > indexed by Search and then reply to them that this is the case >> and >> > > >> > that they should open a support ticket with Twitter. >> > >> > > >> > This is somewhat time consuming and tedious. I'm not sure how to >> ask >> > > >> > for a solution to this situation. I guess I just wanted to >> express >> > > >> > that people are more actively starting to notice when people do >> not >> > > >> > appear in search results. I have no idea why people are being >> dropped >> > > >> > from indexing (I check each account manually), but is this a very >> > > >> > common thing to flip the admin bit to block people from search? >> > >> > > >> > -Chad >> > >
[twitter-dev] Re: last inserted ID
hmm, ok, I actually have not been getting that value everytime. I will look into it. Thanks! On Mon, Jun 22, 2009 at 4:44 PM, Marco Kaiser wrote: > Not sure if I miss your question, but the response body for a successful > status update returns a full status object, including the new ID. > > Hope this helps, > Marco > > 2009/6/23 Peter Denton > >> Hello, >> Is there any chance in the future a http 200 response from a status update >> could return the newly created twitter ID. Meaning, dup the effect of >> mysql_insert_id()? >> >> >> >> >> > -- Peter M. Denton www.twibs.com i...@twibs.com Twibs makes Top 20 apps on Twitter - http://tinyurl.com/bopu6c
[twitter-dev] Re: last inserted ID
Check out the response section: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses update On Mon, Jun 22, 2009 at 18:44, Marco Kaiser wrote: > Not sure if I miss your question, but the response body for a successful > status update returns a full status object, including the new ID. > > Hope this helps, > Marco > > 2009/6/23 Peter Denton >> >> Hello, >> Is there any chance in the future a http 200 response from a status update >> could return the newly created twitter ID. Meaning, dup the effect of >> mysql_insert_id()? >> >> >> >> > > -- 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.
[twitter-dev] Re: last inserted ID
Not sure if I miss your question, but the response body for a successful status update returns a full status object, including the new ID. Hope this helps, Marco 2009/6/23 Peter Denton > Hello, > Is there any chance in the future a http 200 response from a status update > could return the newly created twitter ID. Meaning, dup the effect of > mysql_insert_id()? > > > > >
[twitter-dev] last inserted ID
Hello, Is there any chance in the future a http 200 response from a status update could return the newly created twitter ID. Meaning, dup the effect of mysql_insert_id()?
[twitter-dev] Search: Language bug
Hi ! Im having trouble executing search queries for a specific language. For instance, the following json query returns a bunch of tweets in various languages (including english). http://search.twitter.com/search.json?q=TomTom+GO+910 in the results one can find "iso_language_code":"en".. Now, quering for english results yields no twitter at all! http://search.twitter.com/search.json?q=TomTom+GO+910&lang=en I found the following warning though: "warning":"adjusted since_id, it was older than allowed" Any sugestions? Thanks Pär
[twitter-dev] Re: API rate limits behaving differently when querying the user's accunt vs. other users
Thanks Matt! Adding the header explicitly solved my problem. I fully understand why auth is needed for the non-ID version. I am still unclear as to why auth is not required when the ID is specified, but I guess that's just a design choice. Cheers, Shy. On Jun 22, 8:23 am, Matt Sanford wrote: > Hi Shy, > > When you don't specify and ID we require authentication, when you > do specify and ID (no matter the user) we do not. This is mainly > because without authentication the non-ID version wouldn't make any > sense. When authentication is required we return HTTP 401 > (authentication required) and .NET does the same request again with > the credentials. When you pass in an ID we respond with valid data > since authentication is not required and .NET never actually sends the > credentials. You can get around this by setting the header manually > [1] or there is a HttpWebRequest.PreAuthenticate property [2], but it > does not works like one would expect [3]. I recommend the header route. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > [1] -http://groups.google.com/group/twitter-development-talk/browse_frm/th... > [2] -http://groups.google.com/group/twitter-development-talk/msg/be5e28a8e... > [3] -http://groups.google.com/group/twitter-development-talk/browse_frm/th... > > On Jun 20, 2009, at 1:32 AM, Shy Cohen wrote: > > > > > > > Hi Matt, > > > Here's the C# code that I use to fetch the data: > > > HttpWebRequest webRequest = (HttpWebRequest) WebRequest.Create > > (requestUri); > > webRequest.Credentials = new NetworkCredential(myUsername, > > myPassword); > > webRequest.Method = "GET"; > > WebResponse webResponse = webRequest.GetResponse(); > > XDocument response = XDocument.Load(new StreamReader > > (webResponse.GetResponseStream(), Encoding.UTF8)); > > > If requestUri is "http://twitter.com/friends/ids.xml"; then > > response.Headers["X-RateLimit-Remaining"] returns "1" > > > If requestUri is "http://twitter.com/friends/ids.xml?user_id=17283842"; > > then response.Headers["X-RateLimit-Limit"] returns "100". Please note > > that 17283842 is the user ID for the authenticated user (in other > > words, the ID of my account). > > > It seems that the difference is in whether I’m specifying the ID of > > the user for whom to get the list of friends implicitly (i.e. using > > the implicit ID of the signed-in user) or explicitly (i.e. by > > specifying it in the request). > > > Seems like this might be a bug (at least in the sense that it's > > unexpected behavior that is confusing the user ;-). What do you think? > > > Thanks, > > Shy. > > > On Jun 19, 12:21 pm, Matt Sanford wrote: > >> Hi Shy, > > >> When authenticated methods correctly reflect the whitelisting > >> and > >> unauthenticated methods do not the most common cause is a client side > >> issue where the authentication is not being sent. This is the case > >> with browsers, who wait for an HTTP 401 and then respond with > >> credentials. Some HTTP libraries do this as well (.NET comes to > >> mind). > >> If you let us know what library/language you're using we might be > >> able > >> to help. Another good thing to do is take a look at your request > >> headers … if there is no Authentication header you're not > >> authenticated. > > >> Thanks; > >> – Matt Sanford / @mzsanford > >> Twitter Dev > > >> On Jun 19, 2009, at 9:39 AM, Shy Cohen wrote: > > >>> My app, running under my white-listed creds, was hitting the 100/hr > >>> rate limit. I thought that maybe my white-listing did not go into > >>> effect, but TweetDeck was showing that I have 20K calls left. I ran > >>> the Twitterizer sample, and it was working fine too, showing the > >>> quota > >>> to be 20K. I was baffled. I started playing with this a little and I > >>> believe I finally found the issue! > > >>> It seems that calls to fetch data about the currently logged in user > >>> (e.g.http://twitter.com/statuses/user_timeline.xml) are subject to > >>> the 20K rate limit, while calls to fetch other users' data (e.g. > >>>http://twitter.com/followers/ids.xml?user_id=&page=) are > >>> counted against the IP (or something else, but not the creds I’m > >>> providing). > > >>> Is this correct? If so, what’s the reason behind it? > > >>> Also, is there a way to get around this without white-listing my > >>> (dynamically assigned) IP address? > > >>> Thanks, > >>> Shy.- Hide quoted text - > > >> - Show quoted text -- Hide quoted text - > > - Show quoted text -
[twitter-dev] Re: Oauth Error: 500 & Does Not Authorize
Matt, Sorry for the double post. :) But, basically, I am using Abraham's OAuth class. What I am doing is getting a request URL and token, saving the token to a database (using a vBulletin specific method -- that part at least works). By token I save both oauth_token and oauth_token_secret. Basically the flow uses the same file, but checks for a returned token. Upon that, I send an OAuth HTTP request to https://www.twitter.com/statuses/update with a status parameter. The debug code prints out the last HTTP request code, and all the keys and tokens that I use. 500 showed up... Would you like to see the actual file? As I will send it, but at least a few lines will be invisible or confusing as it's vBulletin specific and illegal for me to send it. Jeremy On Jun 22, 11:56 am, Matt Sanford wrote: > Hello, > > It's a bit difficult to provide much help based on the > description below. Is it possible for you to provide the HTTP request > and response headers (both are important) for the request returning > HTTP 500? Given that information I can try and track down the request > and find the cause of the problem. Also, in the future please do not > double post to the the list. It slows down response times while we all > process all of our incoming messages. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > On Jun 21, 2009, at 8:32 PM, King Kovifor wrote: > > > > > > > OK, so I have been having troubles with my aplication. I'm new to > > OAuth, so it's probably wrong somewhere on my end. > > > I got it so that it recognizes that the token is coming from my > > application, so it takes me and says "Deny" or "Allow". So far, so > > good. Ok. Clicking on Authorize, I get the "Redirecting you to the > > application" notification, so it redirects. I do a test to send a > > tweet, but it hasn't worked. So I threw in some debug code and I'm > > getting an HTTP response of 500! Twitter's end apparently? And if I > > check "Connections" the application that I authorized, IS NOT THERE. > > Now, this is where I'm lost, on both... help?
[twitter-dev] Re: via, RT, and reply_to linking
Not quite as useful as retweet_of_statu_id would be: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1add67766b6ca880/ On Mon, Jun 22, 2009 at 13:08, Chad Etzel wrote: > > For the moment, I'll skip my rant about how stupid I think the "via" > mechanism is, but I'm starting to notice a trend that several clients > are now starting to set the in_reply_to_status_id data when the tweet > is in fact a retweet/repost. > > I'm not sure how I feel about this. One the one hand, they aren't > replies, so it just seems like noise. One the other hand, it does give > a direct link to the original source. > > How do others feel about this? > -Chad > -- 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.
[twitter-dev] via, RT, and reply_to linking
For the moment, I'll skip my rant about how stupid I think the "via" mechanism is, but I'm starting to notice a trend that several clients are now starting to set the in_reply_to_status_id data when the tweet is in fact a retweet/repost. I'm not sure how I feel about this. One the one hand, they aren't replies, so it just seems like noise. One the other hand, it does give a direct link to the original source. How do others feel about this? -Chad
[twitter-dev] Re: New idea for twitter development
I get the feeling m1shu means this should be a twitter.com function, not that he is going to build an app to do this. On Mon, Jun 22, 2009 at 10:24 AM, Phil Nash wrote: > This sort of thing, whilst not built into Twitter has been made possible by > a number of 3rd party applications. Philip mentioned CoTweet, which is a > good example of a web based method of doing this. Multiple account > maintenance is also possible in popular desktop clients, like Tweetdeck, > Tweetie and Nambu and in their respective iPhone clients too. > > Why not give one of those a try? > > > Phil > > -- > Phil Nash > > Twitter: http://twitter.com/philnash > Find some music: http://yournextfavband.com > Web development: http://www.unintentionallyblank.co.uk > > > On Mon, Jun 22, 2009 at 12:31 PM, M1Sh0u wrote: > >> >> In settings panel I think that could be added a new tab named Create >> Secondary Accounts or Secondary Accounts which have a new sign up form >> with or without a new Email information and the same password as the >> main account. >> >> In the sign up form can be added a checkbox named 'Make this account >> the Main Account' and when user loges into twitter, the main account >> is opened first. Users can manage their new accounts switching them >> from a top page select named switch account, and the profile and >> settings informations can be changed for the selected account. >> >> Users should have the possibility to view the messages of all their >> accounts or just for the selected account. >> >> I think that this idea help users very much when they want to create >> more than one twitter accounts and they are not forced to log out and >> log in every time when they want to switch their accounts. >> >> Thanks and I hope that this idea is useful. >> >> >> On Jun 22, 7:26 am, Mandakini kumari wrote: >> > Hi >> > >> > Thanks can you give me detail how to do it ? >> > >> > >> > >> > On Sun, Jun 21, 2009 at 4:04 PM, M1Sh0u wrote: >> > >> > > HI, I'm Mihai Matei, WEB Developer from Romania >> > >> > > I have a new idea that could be implemented on twitter. The idea is >> > > that any user can create secondary accounts. What that's means? Each >> > > user can manage his accounts from the main account which is the first >> > > account created. >> > >> > > That help the user not to log out and after that log in to another >> > > account. He can change his accounts from a top page select. >> > >> > > What do you think about this idea ? >> > >> > > Thanks and sorry for my bad english :) >> > >> > -- >> > Regards >> > Mandakini >> > > -- Peter M. Denton www.twibs.com i...@twibs.com Twibs makes Top 20 apps on Twitter - http://tinyurl.com/bopu6c
[twitter-dev] Re: New idea for twitter development
This sort of thing, whilst not built into Twitter has been made possible by a number of 3rd party applications. Philip mentioned CoTweet, which is a good example of a web based method of doing this. Multiple account maintenance is also possible in popular desktop clients, like Tweetdeck, Tweetie and Nambu and in their respective iPhone clients too. Why not give one of those a try? Phil -- Phil Nash Twitter: http://twitter.com/philnash Find some music: http://yournextfavband.com Web development: http://www.unintentionallyblank.co.uk On Mon, Jun 22, 2009 at 12:31 PM, M1Sh0u wrote: > > In settings panel I think that could be added a new tab named Create > Secondary Accounts or Secondary Accounts which have a new sign up form > with or without a new Email information and the same password as the > main account. > > In the sign up form can be added a checkbox named 'Make this account > the Main Account' and when user loges into twitter, the main account > is opened first. Users can manage their new accounts switching them > from a top page select named switch account, and the profile and > settings informations can be changed for the selected account. > > Users should have the possibility to view the messages of all their > accounts or just for the selected account. > > I think that this idea help users very much when they want to create > more than one twitter accounts and they are not forced to log out and > log in every time when they want to switch their accounts. > > Thanks and I hope that this idea is useful. > > > On Jun 22, 7:26 am, Mandakini kumari wrote: > > Hi > > > > Thanks can you give me detail how to do it ? > > > > > > > > On Sun, Jun 21, 2009 at 4:04 PM, M1Sh0u wrote: > > > > > HI, I'm Mihai Matei, WEB Developer from Romania > > > > > I have a new idea that could be implemented on twitter. The idea is > > > that any user can create secondary accounts. What that's means? Each > > > user can manage his accounts from the main account which is the first > > > account created. > > > > > That help the user not to log out and after that log in to another > > > account. He can change his accounts from a top page select. > > > > > What do you think about this idea ? > > > > > Thanks and sorry for my bad english :) > > > > -- > > Regards > > Mandakini >
[twitter-dev] Re: user/show does not return 401
Hi Matt, I can see why it's done this way. The javascript code for adding credentials to the header is straight-forward and works fine. I don't do much http programming, so this was all new to me, but it would be nice if the api docs reflected what kind of authentication is required -- forced or passive. Thanks, Jonas On Jun 22, 11:08 am, Matt Sanford wrote: > Hi Jonas, > > The issue here is that /users/show allows both authenticated and > un-authenticated access. Unlike the bug you referenced [1], the RFC > does not really mention what to do in that case to my knowledge. For > resources that require authentication we respond with a 401, and the > browser prompts for a username/password and re-sends and authenticated > request. In the case of /users/show we return valid data when not > authenticated so the browser does not bother. > In most programming languages/libraries there is an option to > preemptively authenticate, or you can manually add the Authorization > header. Someone has even done this in Javascript [2], albeit in XUL > since it lacks a cross-domain security issue. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > [1] -http://code.google.com/p/twitter-api/issues/detail?id=135 > [2] -http://groups.google.com/group/twitter-development-talk/browse_frm/th... > > On Jun 19, 2009, at 8:21 PM, Jonas wrote: > > > > > When I send incorrect credentials with a user/show.json command I > > expect to get a 401 code from twitter. However, when I do this from a > > browser using xmlhttprequest I get 400 instead. Actually, for the > > first 100 tries I get 200 codes, and there after I get 400 codes, > > because there is a rate limit of 100 per hour. The point is, at no > > time does authentication ever occur. > > > Could this be a bug in twitter? > > > As this post explains > > >http://groups.google.com/group/twitter-development-talk/browse_thread... > > > the RFC dictates that the browser does not send credentials until it > > first receives a 401. > >
[twitter-dev] Re: Oauth Error: 500 & Does Not Authorize
Hello, It's a bit difficult to provide much help based on the description below. Is it possible for you to provide the HTTP request and response headers (both are important) for the request returning HTTP 500? Given that information I can try and track down the request and find the cause of the problem. Also, in the future please do not double post to the the list. It slows down response times while we all process all of our incoming messages. Thanks; – Matt Sanford / @mzsanford Twitter Dev On Jun 21, 2009, at 8:32 PM, King Kovifor wrote: OK, so I have been having troubles with my aplication. I'm new to OAuth, so it's probably wrong somewhere on my end. I got it so that it recognizes that the token is coming from my application, so it takes me and says "Deny" or "Allow". So far, so good. Ok. Clicking on Authorize, I get the "Redirecting you to the application" notification, so it redirects. I do a test to send a tweet, but it hasn't worked. So I threw in some debug code and I'm getting an HTTP response of 500! Twitter's end apparently? And if I check "Connections" the application that I authorized, IS NOT THERE. Now, this is where I'm lost, on both... help?
[twitter-dev] Re: Search beyond 7 days
On Sun, Jun 21, 2009 at 8:16 PM, Doug Williams wrote: > > Unfortunately not. We currently do not offer a method to retrieve > tweets past what is available within our pagination limits [1]. Not meant in the smart-ass way, may I point out that Google will return results much older. I've used queries like "site:twitter.com keyword" to find older tweets. Biggest problem, though, is that you're searching all the text, not just tweets. The query "site:twitter.com money" has about 2 million hits, though it is returning results from at least three domains - twitter.com, m.twitter.comand (new to me) explore.twitter.com. Nick
[twitter-dev] Re: API rate limits behaving differently when querying the user's accunt vs. other users
Hi Shy, When you don't specify and ID we require authentication, when you do specify and ID (no matter the user) we do not. This is mainly because without authentication the non-ID version wouldn't make any sense. When authentication is required we return HTTP 401 (authentication required) and .NET does the same request again with the credentials. When you pass in an ID we respond with valid data since authentication is not required and .NET never actually sends the credentials. You can get around this by setting the header manually [1] or there is a HttpWebRequest.PreAuthenticate property [2], but it does not works like one would expect [3]. I recommend the header route. Thanks; – Matt Sanford / @mzsanford Twitter Dev [1] - http://groups.google.com/group/twitter-development-talk/browse_frm/thread/14ac4568e4a1cb17 [2] - http://groups.google.com/group/twitter-development-talk/msg/be5e28a8e0b4fb33 [3] - http://groups.google.com/group/twitter-development-talk/browse_frm/thread/3d54172d7492cce3/74a5ddabe36d5d3c On Jun 20, 2009, at 1:32 AM, Shy Cohen wrote: Hi Matt, Here's the C# code that I use to fetch the data: HttpWebRequest webRequest = (HttpWebRequest) WebRequest.Create (requestUri); webRequest.Credentials = new NetworkCredential(myUsername, myPassword); webRequest.Method = "GET"; WebResponse webResponse = webRequest.GetResponse(); XDocument response = XDocument.Load(new StreamReader (webResponse.GetResponseStream(), Encoding.UTF8)); If requestUri is "http://twitter.com/friends/ids.xml"; then response.Headers["X-RateLimit-Remaining"] returns "1" If requestUri is "http://twitter.com/friends/ids.xml?user_id=17283842"; then response.Headers["X-RateLimit-Limit"] returns "100". Please note that 17283842 is the user ID for the authenticated user (in other words, the ID of my account). It seems that the difference is in whether I’m specifying the ID of the user for whom to get the list of friends implicitly (i.e. using the implicit ID of the signed-in user) or explicitly (i.e. by specifying it in the request). Seems like this might be a bug (at least in the sense that it's unexpected behavior that is confusing the user ;-). What do you think? Thanks, Shy. On Jun 19, 12:21 pm, Matt Sanford wrote: Hi Shy, When authenticated methods correctly reflect the whitelisting and unauthenticated methods do not the most common cause is a client side issue where the authentication is not being sent. This is the case with browsers, who wait for an HTTP 401 and then respond with credentials. Some HTTP libraries do this as well (.NET comes to mind). If you let us know what library/language you're using we might be able to help. Another good thing to do is take a look at your request headers … if there is no Authentication header you're not authenticated. Thanks; – Matt Sanford / @mzsanford Twitter Dev On Jun 19, 2009, at 9:39 AM, Shy Cohen wrote: My app, running under my white-listed creds, was hitting the 100/hr rate limit. I thought that maybe my white-listing did not go into effect, but TweetDeck was showing that I have 20K calls left. I ran the Twitterizer sample, and it was working fine too, showing the quota to be 20K. I was baffled. I started playing with this a little and I believe I finally found the issue! It seems that calls to fetch data about the currently logged in user (e.g.http://twitter.com/statuses/user_timeline.xml) are subject to the 20K rate limit, while calls to fetch other users' data (e.g. http://twitter.com/followers/ids.xml?user_id=&page=) are counted against the IP (or something else, but not the creds I’m providing). Is this correct? If so, what’s the reason behind it? Also, is there a way to get around this without white-listing my (dynamically assigned) IP address? Thanks, Shy.- Hide quoted text - - Show quoted text -
[twitter-dev] Re: user/show does not return 401
Hi Jonas, The issue here is that /users/show allows both authenticated and un-authenticated access. Unlike the bug you referenced [1], the RFC does not really mention what to do in that case to my knowledge. For resources that require authentication we respond with a 401, and the browser prompts for a username/password and re-sends and authenticated request. In the case of /users/show we return valid data when not authenticated so the browser does not bother. In most programming languages/libraries there is an option to preemptively authenticate, or you can manually add the Authorization header. Someone has even done this in Javascript [2], albeit in XUL since it lacks a cross-domain security issue. Thanks; – Matt Sanford / @mzsanford Twitter Dev [1] - http://code.google.com/p/twitter-api/issues/detail?id=135 [2] - http://groups.google.com/group/twitter-development-talk/browse_frm/thread/70bbd259e4217dde On Jun 19, 2009, at 8:21 PM, Jonas wrote: > > When I send incorrect credentials with a user/show.json command I > expect to get a 401 code from twitter. However, when I do this from a > browser using xmlhttprequest I get 400 instead. Actually, for the > first 100 tries I get 200 codes, and there after I get 400 codes, > because there is a rate limit of 100 per hour. The point is, at no > time does authentication ever occur. > > Could this be a bug in twitter? > > As this post explains > > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/35c3918ec2317e98/d05dd17c5a261dfa?lnk=gst&q=xmlhttprequest+401#d05dd17c5a261dfa > > the RFC dictates that the browser does not send credentials until it > first receives a 401. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Twitter Development Talk" group. To post to this group, send email to twitter-development-talk@googlegroups.com To unsubscribe from this group, send email to twitter-development-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/twitter-development-talk?hl=en -~--~~~~--~~--~--~---
[twitter-dev] Re: making API call to update status
Hi there, The read and read/write permission level is stored on a per-token basis. This is to prevent a user from authorizing your application as "read only" and you escalating it to "read and write" without their knowledge. You need to get a new token for the user in question to be able to write. You can also pass the oauth_access_type parameter in the user redirect [1] to specify. Thanks; – Matt Sanford / @mzsanford Twitter Dev [1] - http://groups.google.com/group/twitter-development-talk/browse_frm/thread/d4fefae61f5e7019 On Jun 21, 2009, at 4:30 PM, James wrote: On Jun 4, 2:57 pm, Abraham Williams <4bra...@gmail.com> wrote: If an application is created using read-only an account grants access and then the application changes to read-write the user needs to grant access again in order for the application to post updates. I've changed my application to read-write, reset the consumer key/ secret, and re-authenticated as an end-user, and I'm still getting the 'Read-only application cannot POST' error. It's been several hours. Either Twitter is taking a while to propagate the changes, or there's something else to do that I haven't thought of On Thu, Jun 4, 2009 at 00:13, avinash srivastava wrote: looks like while setting up your application you have asked for read permission only. Check for access type in your application settings on twitter and make it read and write. Avinash On Thu, Jun 4, 2009 at 10:20 AM, Nasir wrote: Hi, Can any one help me to make api call after authentication using OAuth- php. Its gives an error (Read-only application cannot POST) Thanks -- Abraham Williams |http://the.hackerconundrum.com 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] Public timeline rate limit exceeded after 10 call !?
Hi folks, I have read all the API documentation, search in Google, ask to be white listed, ask by email for help and I still can't find why http://twittearth.com often hit the rate limit. I call the API via this Php page : http://twittearth.com/twitter_proxy_optymized.php?urlpage=http://twitter.com/statuses/public_timeline.xml This URL is used by the Flash application online http://twittearth.com and by a screensaver. To be sure to not exceeded the rate I set a timeout between each call to the API, currently my timeout is 6 minutes ! On each call I cache the API answer in a file : http://twittearth.com/public_timeline.txt To be sure of what I do each time I call the API I write log in a file http://twittearth.com/log.txt My server is mutualized and maybe someone hit the API with this IP to, can I have access at the call stats from the Twitter side ? Thank for your help, I looking for a solution from months
[twitter-dev] Re: Storing OAuth Tokens in MySQL Database
The only token you need to store is the access token.
Oh and you should probably reset your consume keys now that they are
publicly known by everyone on this list.
On Mon, Jun 22, 2009 at 01:18, DevinPitcher wrote:
>
> include("../../../settings/mysql.php");
> require_once('twitterOAuth.php');
>
> mysql_connect("$mysql_host", "$mysql_username", "$mysql_password") or
> die("ERROR: Could not connect to MySQL.");
> mysql_select_db("$mysql_database") or die("ERROR: Could not connect to
> selected MySQL database.");
> $sql="SELECT * FROM cirrus_members WHERE member_id='$_SESSION
> [cirrus_member_id]'";
> $result=mysql_query($sql);
> $rows=mysql_fetch_array($result);
>
> $consumer_key = 'D6IpkcZ5RAXgVYpyLOuw';
> $consumer_secret = 'B0NqK3CiNHAaDzseK5YQ6BKE9KrWPb4YGgDIoRVhEnQ';
> $content = NULL;
>
> /* Set state if previous session */
> $state = $_SESSION['oauth_state'];
> /* Checks if oauth_token is set from returning from twitter */
> $session_token = $_SESSION['oauth_request_token'];
> /* Checks if oauth_token is set from returning from twitter */
> $oauth_token = $_REQUEST['oauth_token'];
> /* Set section var */
> $section = $_REQUEST['section'];
>
> if ($_REQUEST['access'] === 'revoke') {
> session_destroy();
> session_start();
> header("location:index.php");
> }
>
> /* If oauth_token is missing get it */
> if ($_REQUEST['oauth_token'] != NULL && $_SESSION['oauth_state'] ===
> 'start') {
> $_SESSION['oauth_state'] = $state = 'returned';
> }
>
> /*
> * 'default': Get a request token from twitter for new user
> * 'returned': The user has authorize the app on twitter
> */
> switch ($state) {
> default:
> /* Create TwitterOAuth object with app key/secret */
> $to = new TwitterOAuth($consumer_key, $consumer_secret);
> /* Request tokens from twitter */
> $tok = $to->getRequestToken();
>
> /* Save tokens for later */
> $_SESSION['oauth_request_token'] = $token = $tok['oauth_token'];
> $_SESSION['oauth_request_token_secret'] = $tok
> ['oauth_token_secret'];
> $_SESSION['oauth_state'] = "start";
>
> /* Build the authorization URL */
> $request_link = $to->getAuthorizeURL($token);
>
> /* Build link that gets user to twitter to authorize the app */
> $content .= 'Authenticate on Twitter.com a> to access this application.';
> break;
>
> case 'returned':
> /* If the access tokens are already set skip to the API call */
> if ($_SESSION['oauth_access_token'] === NULL && $_SESSION
> ['oauth_access_token_secret'] === NULL) {
> /* Create TwitterOAuth object with app key/secret and token key/
> secret from default phase */
> $to = new TwitterOAuth($consumer_key, $consumer_secret, $_SESSION
> ['oauth_request_token'], $_SESSION['oauth_request_token_secret']);
> /* Request access tokens from twitter */
> $tok = $to->getAccessToken();
>
> /* Save the access tokens. Normally these would be saved in a
> database for future use. */
> $_SESSION['oauth_access_token'] = $tok['oauth_token'];
> $_SESSION['oauth_access_token_secret'] = $tok
> ['oauth_token_secret'];
> }
>
> /* Create TwitterOAuth with app key/secret and user access key/
> secret */
> $to = new TwitterOAuth($consumer_key, $consumer_secret, $_SESSION
> ['oauth_access_token'], $_SESSION['oauth_access_token_secret']);
> /* Run request on twitter API as user. */
> if ($_GET['action'] == "getinfo") { $content = $to->OAuthRequest
> ('https://twitter.com/account/verify_credentials.xml', array(),
> 'GET'); }
> if ($_GET['action'] == "update") { $content = $to->OAuthRequest
> ('https://twitter.com/statuses/update.xml', array('status' => $_POST
> ['status']), 'POST'); }
> if ($_GET['action'] == "getreplies") { $content = $to->OAuthRequest
> ('https://twitter.com/statuses/replies.xml', array(), 'GET'); }
> if ($_GET['action'] == "") { $content = $to->OAuthRequest('https://
> twitter.com/statuses/friends_timeline.xml?count=5', array(), 'GET');
> $showTweetBox = "true"; }
> break;
> }
> ?>
>
> OK, so I have all of the code I need ready, but how can I store all of
> these tokens into a MySQL database for each user?
> I set up rows for each (oauth_state, oauth_token, oauth_token_secret,
> oauth_request_token, oauth_request_token_secret, oauth_access_token,
> and oauth_access_token_secret) so I can store any of them.
> I don't know which ones to store. Any ideas?
>
--
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.
[twitter-dev] Re: OAuth and pincodes...
Hi Chris, As it is currently written the PIN code will always be numeric, in part to handle the lowest-common-denominator of mobile handsets. There is no plan to change that. Thanks; – Matt Sanford / @mzsanford Twitter Dev On Jun 21, 2009, at 11:49 AM, Chris Kimpton wrote: Hi, To answer myself, yes it is. I guess I cannot assume that the twitter pin code will always be numeric - would be nice to give the user the numberpad if it is, but then they cannot switch to text... Regards, Chris 2009/6/20 Chris Kimpton Hi, A bit late to this party, so sorry for repeating stuff, but trying to get my old head around the twitter 1.0a OAuth changes. http://oauth.googlecode.com/svn/spec/core/1.0a/drafts/3/oauth-core-1_0a.html#auth_step3 http://groups.google.com/group/twitter-development-talk/browse_frm/thread/1c48fedf4ae7ed52/7d772dedcc756cbf#7d772dedcc756cbf I have a desktop client (an iphone app, Twitkwik) which 'now' supplies the user with a pin code after they authorise the app to use Twitter. My understanding is that the app should ask the user for the pin code and then send this (as oauth_verifier) when swapping the request token for an access token request. Does that sound correct? As far as I can tell, webapps can get round this by providing a callback. Thanks in advance, Chris
[twitter-dev] Re: New idea for twitter development
In settings panel I think that could be added a new tab named Create Secondary Accounts or Secondary Accounts which have a new sign up form with or without a new Email information and the same password as the main account. In the sign up form can be added a checkbox named 'Make this account the Main Account' and when user loges into twitter, the main account is opened first. Users can manage their new accounts switching them from a top page select named switch account, and the profile and settings informations can be changed for the selected account. Users should have the possibility to view the messages of all their accounts or just for the selected account. I think that this idea help users very much when they want to create more than one twitter accounts and they are not forced to log out and log in every time when they want to switch their accounts. Thanks and I hope that this idea is useful. On Jun 22, 7:26 am, Mandakini kumari wrote: > Hi > > Thanks can you give me detail how to do it ? > > > > On Sun, Jun 21, 2009 at 4:04 PM, M1Sh0u wrote: > > > HI, I'm Mihai Matei, WEB Developer from Romania > > > I have a new idea that could be implemented on twitter. The idea is > > that any user can create secondary accounts. What that's means? Each > > user can manage his accounts from the main account which is the first > > account created. > > > That help the user not to log out and after that log in to another > > account. He can change his accounts from a top page select. > > > What do you think about this idea ? > > > Thanks and sorry for my bad english :) > > -- > Regards > Mandakini
[twitter-dev] Storing OAuth Tokens in MySQL Database
getRequestToken();
/* Save tokens for later */
$_SESSION['oauth_request_token'] = $token = $tok['oauth_token'];
$_SESSION['oauth_request_token_secret'] = $tok
['oauth_token_secret'];
$_SESSION['oauth_state'] = "start";
/* Build the authorization URL */
$request_link = $to->getAuthorizeURL($token);
/* Build link that gets user to twitter to authorize the app */
$content .= 'Authenticate on Twitter.com to access this application.';
break;
case 'returned':
/* If the access tokens are already set skip to the API call */
if ($_SESSION['oauth_access_token'] === NULL && $_SESSION
['oauth_access_token_secret'] === NULL) {
/* Create TwitterOAuth object with app key/secret and token key/
secret from default phase */
$to = new TwitterOAuth($consumer_key, $consumer_secret, $_SESSION
['oauth_request_token'], $_SESSION['oauth_request_token_secret']);
/* Request access tokens from twitter */
$tok = $to->getAccessToken();
/* Save the access tokens. Normally these would be saved in a
database for future use. */
$_SESSION['oauth_access_token'] = $tok['oauth_token'];
$_SESSION['oauth_access_token_secret'] = $tok
['oauth_token_secret'];
}
/* Create TwitterOAuth with app key/secret and user access key/
secret */
$to = new TwitterOAuth($consumer_key, $consumer_secret, $_SESSION
['oauth_access_token'], $_SESSION['oauth_access_token_secret']);
/* Run request on twitter API as user. */
if ($_GET['action'] == "getinfo") { $content = $to->OAuthRequest
('https://twitter.com/account/verify_credentials.xml', array(),
'GET'); }
if ($_GET['action'] == "update") { $content = $to->OAuthRequest
('https://twitter.com/statuses/update.xml', array('status' => $_POST
['status']), 'POST'); }
if ($_GET['action'] == "getreplies") { $content = $to->OAuthRequest
('https://twitter.com/statuses/replies.xml', array(), 'GET'); }
if ($_GET['action'] == "") { $content = $to->OAuthRequest('https://
twitter.com/statuses/friends_timeline.xml?count=5', array(), 'GET');
$showTweetBox = "true"; }
break;
}
?>
OK, so I have all of the code I need ready, but how can I store all of
these tokens into a MySQL database for each user?
I set up rows for each (oauth_state, oauth_token, oauth_token_secret,
oauth_request_token, oauth_request_token_secret, oauth_access_token,
and oauth_access_token_secret) so I can store any of them.
I don't know which ones to store. Any ideas?
[twitter-dev] Re: New idea for twitter development
What about using www.cotweet.com? On Jun 21, 11:26 pm, Mandakini kumari wrote: > Hi > > Thanks can you give me detail how to do it ? > > > > > > On Sun, Jun 21, 2009 at 4:04 PM, M1Sh0u wrote: > > > HI, I'm Mihai Matei, WEB Developer from Romania > > > I have a new idea that could be implemented on twitter. The idea is > > that any user can create secondary accounts. What that's means? Each > > user can manage his accounts from the main account which is the first > > account created. > > > That help the user not to log out and after that log in to another > > account. He can change his accounts from a top page select. > > > What do you think about this idea ? > > > Thanks and sorry for my bad english :) > > -- > Regards > Mandakini
