Twitpic OAuth switching users issue - twitter

I'm using twitpic and logging in fine, but when changing accounts and trying to upload a pic within a short time frame (< 30 seconds) I get a "401 Unauthorized" back for a little while, and then it starts working after about a minute and my pictures upload.
This seems like maybe twitpic is caching something and it takes a little while to invalidate, or it's seeing that my IP address is the same but my oauth token is different. Anyone else have this issue, and if so how did you solve it?
Andrew

I had the exact same issue. Twitpic developers couldn't help for months!
However, I figured it to ASIHTTPRequest. If you're using ASIHTTPRequest for uploading to Twitpic servers, switch back to NSURLConnection. (or figure out why ASI would have such caching issue).
Even created https://github.com/Gurpartap/GSHTTPRequest and https://github.com/Gurpartap/GSFormDataRequest quickly modeled around ASI's counterparts for the quick replacement.
Hope it works out for you.

I had the same problem and found a fix for it:
yourRequest.shouldAttemptPersistentConnection = NO;
Hope this helps!

Related

Any twitter api or complete solutions for monodroid?

Looking for good solution for Twitter login and posting something... but there is no idea for now. How to do it in xamarine( IOS mono has complete solution, but monodroid...) help me please, if somebody knows how to do it.
If you just want to post something then you can easily do this by sending an Intent for use by an external app - e.g. see https://github.com/slodge/MvvmCross/blob/v3/Plugins/Cirrious/Share/Cirrious.MvvmCross.Plugins.Share.Droid/MvxShareTask.cs#L19
If you need a more complete solution then libraries like Tweetsharp have had MonoDroid ports/branches at various times, but I don't know the current status of any of these.
You might also want to take a look at Xamarin.Social. This component will let you tweet from your Xamarin.Android application.

URL Schemes and Facebook App 5.0

There's a question already related to groups, but it seems it's much more than that. Have URL schemes been completely thrown out of the new app (aside from the generic fb://), or is there a new list of supported schemes?
In particular, we can't get to a place details page. I've also tried /pages, /page, /places, /place...
Thanks,
Ivan
I'm not sure about those urls... but I just posted what I believe is a solution for facebook business pages.. it may help? Here it is below:
OK .. seriously this took me about 90 minutes of research to figure out. It works currently under facebook ios 5.0.1 for iPhone.. haven't tried it in iPad yet.
The url is fb://profile/132753734806
NOW the important part is that number. That links to one of my clients, Charles Scott. HOWEVER, that's not their FBID or Page ID.. their Page ID is 10150348920319807
so you would think it should be fb://profile/10150348920319807 but that gives me an error.
Here's how you get the correct code.. click on any of your page's photos.. here's an example for my client https://www.facebook.com/photo.php?fbid=10150348920319807&set=a.10150348920314807.356942.132753734806&type=1&theater
if you notice the FBID that does not work follows fbid= in that URL.. the number you WANT is just before the &type=1theater but following that last period. 132753734806 is the correct code to punch in after fb://profile/
I hope that makes some sense... I know zero about code or coding but this was bothering me so much and I knew there was a way.
Now, the two questions I would love to have answered/working.. 1. if this could work on android phones 2. create a working qr code for this url so people can scan with ios devices and have it open automatically
Good luck and I hope this helps everyone!
I tried Alessandro's way but did not succeed - the number he mentioned is new every time.
I tried fb://profile?id={pageId} and it worked in my case. {pageId} is simple page id number without any tricks. Facebook app version is 5.0.1

Twitter Share buttons Stopped Working

I have 2 sites where the Twitter Share buttons stopped working.
Has anyone experienced the same problem?
Here are links to my sites:
http://bit.ly/PMVJeA
http://bit.ly/MQQdYG
Problem seems isolated to IE8, not sure about Chrome...seems okay in FF14
Thank you very much for any help you can provide.
We're having issues at the moment that the new or old twitter version of the "Twitter Share Button" with any version of IE is causing some of the JavaScript on our sites to not execute. (Specifically header related)
After tinkering for an hour or so, I've shelved it. Just used IE browser detection to stop it from putting the Twitter button on IE browsers.
Sorry I can't be of more help - but I get the feeling that this is at Twitters end.

When did someone follow - Twitter API

I've been attempting to go over the Twitter API, albeit it has taken me a while and I'm being thrown back and forth between the old and the new site - however I was wondering if there is a date at all for when a user has decided to follow or; or if your able to tell when a user stopped following you?
I've been looking through here https://apiwiki.twitter.com/Twitter-API-Documentation to no avail, but I wondered if anyone knew of a way of doing it (outside of a separate monitoring system of course!)
Cheers,
Dan
The Twitter API doesn't explicitly provide dates for when a user started following you or stopped following you. This is something that you would need to monitor in some fashion.

How do I validate OAuth requests?

I'm trying to use OAuth with Twitter, and I have my head wrapped around the pieces that need to be put in place to get a request token. But, it's not working. And the error message that I'm getting back isn't terribly helpful.
Luckily I found a tester but again, the error message there isn't terribly helpful. "Invalid signature." Ok, great. But since there are several steps involved (truth be told, all of which confuse the hell out of me) in generating the signature, I'm at a loss.
Is there another tool out there that might be more helpful? Maybe one where I can see what the data should be at each step (check that the request concatenation is right, check that the initial signing is right - i'm using HMAC-SHA1, check that the base 64 is right, etc).
Yes. Run, do not walk, to Hueniverse - one of the neatest pieces of Javascript you'll see!

Resources