I took a run at your web site. It's got some kind of Flash script that causes Firefox to throw an error, and it takes *way* too long to load. So, you've got bigger problems than oAuth to solve.
As for hiring developers, there is a list of developers who have self- registered with their areas of expertise at http://apiwiki.twitter.com/Developers. This appears to have been edited last about 4 months ago, so I suspect there are a few names missing. ;-) The whole "Twitter developer registry" thing is probably something Ryan Sarver will want to comment on, possibly even before Chirp. ;-) Meanwhile, you could look through that list and see if there are people in your geographic area with oAuth and .NET experience, at least as claimed by themselves. I'm personally not a .NET developer, so I can't help you. On Feb 13, 7:56 am, Ryan Alford <ryanalford...@gmail.com> wrote: > You can ask technical questions here. > > You had developers that gave up because of cookie handling? Uhhh... > > Ryan > > Sent from my DROID > > On Feb 13, 2010 10:44 AM, "Merrows" <sa...@merrows.co.uk> wrote: > > Thanks for all the interesting comments. Actually I have found it hard > to locate the expertise. > > I have some code samples already, but I really need someone or at > least a technical forum (similar to the kind of thing for Google > Products which allows QA type of messages) for twitter. Is there > anything like that for twitter or is this it? > > I have already hired a few developers for this task, and they > implement Basic Auth, or they just give up as finding the code too > hard (mainly handling the callbacks and cookie handling seems the hard > part). > > If anyone is interested the actual application it is a new site > calledwww.fullbe.comI am buillding which will allow users to comment on > products via their twitter names. > > On Feb 11, 6:02 pm, alexro <arodyg...@gmail.com> wrote: > > > Also check out LinqToTwitter, it includes... > > >http://twittervb.codeplex.com-Hide quoted text - > > > - Show quoted text -