Brian,
not to ignore privacy issues but just to simplify the situation a
bit ...
What currently protects a user from a malicious (desktop) application
stealing all kinds of user data via submitting tweets through it's
proxy? And even by submitting such information directly to it's
website?
On
Hi, I'm Alex. London-based. Currently working on a conversation
tracking application.
My tools are .Net specific, thanks Mayo for LinqToTwitter library!
Thanks to all of you for providing great advice!
On Feb 21, 11:03 pm, Anton Krasovsky anton.krasov...@gmail.com
wrote:
Hi Guys,
@ak1394
Dmitri,
I believe such request still counts against your usage limit. Just to
remember to stay within the boundaries :)
On Feb 18, 10:15 pm, Dmitri Snytkine d.snytk...@gmail.com wrote:
Sorry to bother you, but I found out that this feature is already
available
Turns out I can easily get
The way I did it for my website is to store the tokens in a db and put
a custom persisting cookie on the user's browser. The user can 'sign-
off' removing the cookie and will have to authenticate with Twitter
next time she uses the protected functionality on my website. Or the
cookie can expire/be
Also check out LinqToTwitter, it includes a sample web application in
C#
On Feb 10, 10:33 pm, John Meyer john.l.me...@gmail.com wrote:
On 2/10/2010 7:48 AM, Merrows wrote: I am seeking someone skilled in .NET
3.5, C# to help with implementing
twitter oauth, and I would welcome any
