Just a quick questron, would two applications login in at the same time (via
the same credencals, to the same account) cause twitter to have issues?
I have a desktop client and background service that use the same database to
tweet RSS feeds to twitter and am experances some strange issues
No two ways about it oAuth on desktop's sucks and I imagan it's even worse on
mobiles.
Twitter can add new source prams to their database for non-oAuth users however
when I tryed they where unable to do so.
I'm currently developing a different .net desktop app (think Hootsuite for
desktops)
I 100% agree.
But another idea just struck me, why not put the OAuth part of your app in a
DLL (at lest the authentication and communication with twitter part) and hard
code it their.
You lose some of the open source nature of the app but it will be secure.
Sent using BlackBerry® from Orange
Why not check for the presence of the keys on start-up, if they are missing
re-direct the user (open a browser window) to the new apps page and/or a
step-by-step guide on you site. then store the keys as normal
Sent using BlackBerry® from Orange
-Original Message-
From: Raffi
TwitterVB - a .net framework for twitter and
PHP - custom written code to pull the public time line and users timelimes
Sent using BlackBerry® from Orange
-Original Message-
From: M. Edward (Ed) Borasky zzn...@gmail.com
Date: Sat, 30 Jan 2010 13:17:09
To: