[twitter-dev] Re: How-To: Load the Twitter XML into a VB.Net XML Document...
If you force datatyping to alpha, six chars, this will be a nonproblem Sent from my iPhone On Jul 1, 2009, at 8:00 AM, Obrzut sa...@peyoteuk.com wrote: Did I state otherwise? You are not reading my words - you are being blinded by the noise from your own head. What I stated is this; I authenticate my VB.NET web browser via PIN etc THIS means my browser is authenticated. If I try to access a page via the program with a TCP Client - I have to re-authenticate via PIN. This WAS a problem - my solution is to continue to use the web browser for authentication and extract the XML pages into an XML Document. Hence the above code. If you state otherwise - that you CAN use a TCP Client after already authenticating your VB.Net web browser - you are wrong. I imagine you think I am wrong - and that I am an idiot. Believe me - I am very skilled at programming. And this is my experience. The library is faulty. It does not process leading zero pins. The OAuth implementation is stupid - because it does not authenticate an program but a TCP method. Hence, you guys are s off the mark here it hurts me to talk to you. Really, srsly, it's pathetic that you DO NOT LISTEN. On Jul 1, 4:58 am, DWRoelands duane.roela...@gmail.com wrote: You can absolutely authenticate in a web page, even if your application is not a web application. Mine works that way. Here's how it should go. Bojan, please correct me if I'm wrong. 1. Your application calls GetAuthorizationLink() to get the URL of the authorization page (you've got this already). 2. Your application opens a web browser to that link. In .NET, you can do this with Process.Start(The URL that you get from GetAuthorizationLink). 3. The user sees the six-digit PIN on the screen. 4. Your application prompts the user to enter the six-digit PIN that they see. 5. Your application calls GetAccessToken(), passing the six-digit PIN as the input parameter. 6. The OAuth object has two properties that should now be populated: Token and TokenSecret. These are the items you will use for all subsequent OAuth requests to Twitter. Your application should now be authorized via OAuth. On Jun 30, 8:58 pm, Obrzut sa...@peyoteuk.com wrote: This is because of OAuth. It uses HTML pages to validate. Perhaps I am wrong - but once I use a web browser to validate - I cannot use a TCP Client to get the XML because I authenticated via a web browser. When I tried to (for example) send the pin back via a HTTP Web Request it failed. I am not sure if I am using the OAuth library Interface Class I have for VB.NET correctly!?
[twitter-dev] Re: Security Best Practices
Sounds like the assumption is that part of the keypair is in the source. That is clearly a bad idea ... The software should obly provide for processes and not ever content Sent from my iPhone On Jul 1, 2009, at 11:10 AM, Andrew Badera and...@badera.us wrote: No one's snarking, but again, interesting you would interpret it that way. Open source all you want, each person deploying an instance will have to get their own keys. What's so tough about that? On Wed, Jul 1, 2009 at 11:07 AM, DWRoelandsduane.roela...@gmail.com wrote: Andrew, This isn't about credit in the source parameter. It's about application security. Twitter has stated that Basic Auth will eventually be deprecated. OAuth will eventually be the only method of authentication available. When that happens, developers of open source clients will be forced to reveal their Consumer Key Secret. This is a very real problem; open-source developers of desktop clients will have to reveal their Consumer Key Secret. Can we keep this discussion focused on the technical issues at hand, rather than snarking about one another's motives? It's not productive. Regards, Duane On Jul 1, 10:57 am, Andrew Badera and...@badera.us wrote: Not what I said in the least, but it's interesting that you should interpret it that way. Re-read what I said. If someone is open sourcing something, in the true spirit of open source, they shouldn't care about getting credit in the source parameter. Thanks you and good night, I'm here all week, try the veal, don't forget to tip your waitresses and angry developers. On Wed, Jul 1, 2009 at 10:50 AM, Cameron Kaiserspec...@floodgap.com wrote: Yes, but don't distribute it. Obviously config files are human readable, but you blank out secrets before publishing them. People using open source libraries will have to get their own keys. So, either you really are contributing in the spirit of open source, and you don't care about getting credit, or you're doing it for self promotional purposes, and the conversation is moot anyhow. That's an asinine statement. So everybody who doesn't make their open source software anonymous is a publicity whore? -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- In memory of John Banner ---
[twitter-dev] Re: Poll: Demographics of Twitter Dev--please answer a few questions
On Thu, May 21, 2009 at 9:03 PM, Neicole neic...@trustneicole.com wrote: I'm interested in the demographics of Twitter Developers. I'd appreciate it if you'd answer a few questions. Just respond to this post with your answers: 1. female? 2. married 3. yes, adult children 4. age range:over 50 I'll summarize and post the results. Thanks!
[twitter-dev] Re: Our own redirecting URL is being changed to a bit.ly URL
Hi Emrah, I ended up using bitly, but thanks. On Fri, May 22, 2009 at 3:10 AM, Emrah KAVUN e...@ekanet.net wrote: Hi, If it can be in any help, I have a kind of private url shortening service that I could adapt to your needs. www.fwd.li. I can't really design the page because I am blind (the reason why there is no logo). However it might come handy to have an url shortening api service designed individually for your apps. I currently support plain text and xml output. Cheers, Emrah P.s.: if someone is interested in making a logo, you're welcome. If someone else would like to carry on the dev, welcome as well. :) TjL wrote: On Tue, May 19, 2009 at 10:48 PM, Cameron Kaiser spec...@floodgap.com wrote: The best you can do is use the bit.ly API to un-shorten the link and grab your URL key from there. Have a look at the /expand method in their API: http://code.google.com/p/bitly-api/wiki/ApiDocumentation Or, implement your own URL shortening scheme (either internally, or using a specific service that meets your needs), with the assumption that the shortening will occur and at least this way you can control the situation under how the shortening is handled. I believe that Twitter will shorten links over 30 characters, but this does not *always* seem to be the case. Your best bet (IMO) is to determine which service you want to use and shorten the links yourself. I started putting together a list of them not too long ago and came up with these: bit.ly xrl.us tr.im snipr.com tinyarro.ws tinyurl.com icanhaz.com budurl.com There are, no doubt, others.
