I'm building a web app using rails. In this site I basically have several profiles, each of them linked to a specific profile picture from twitter.
Instead of install a twitter gem or similar, I just use this line of code:
https://twitter.com/<%= influencer.username %>/profile_image?size=original
It works great, but what I've discovered is that in some devices the browser can't show them. Specially on phones.
Any ideas of why this thing doesn't work?
Or, is there another way to do this?
The website (super beta) is: https://influencerlist.io
Thank you!
That’s because on phones, Twitter redirects to mobile.twitter.com, and the image URL is not available on mobile.twitter.com (try this in a browser for yourself). The correct way to obtain the user profile image would be via the Twitter API and querying the user object from /1.1/users/show.json (or, via the users/lookup batch endpoint).
Related
Okay, So I have seen multiple issues(answered and unanswered) regarding Instagram API, haven't found anything related to my problem.
I have made an app in iOS which lets users download only profile pictures of any Instagram user in HD resolution.
After a long struggle, I have found all of the related API's And I am able to get the HD variant of Profile pictures in the app. Now the thing is those APIs read the phone's browser cookies that if I have authenticated the user in Instagram or not. And if I don't authenticate before the HD profile query id doesn't give me the desired data i.e no HD profile Url.
It means that I can only get the Instagram authentication before letting my users search and query for the HD profile pictures. So I figured out and added that using Instagram Basic Display API.
The problem came when I submitted the app for the Facebook developer review. They keep saying that Instagram profile permission(s) should not be used to authenticate new users in your app.
And it's the 3rd time I told them that the app flow requires the authentication just to read cookies and I am not using any of the user's data for personal authentication, but they are not letting the app pass the review.
My need is can someone help me out if I am really using the wrong authentication process or maybe I am not able to convey my need to the reviewer. So what do I tell them, I am sure there is something going on wrong because I have seen some apps doing the same process in their apps.
Thanks for helping me out
In my application I need to generate a link and needs to share on Twitter and Facebook. For Facebook I have used its SDK but for Twitter I am not able to find any such SDK which I can integrate in my app and make it able to Tweet it.
On Twitter site I saw REST API but I think that cannot be used for Tweeting. One more thing, I have integrated the Twitter with the help of Social.framework but in case if user hasn't provided his/her details in iPhone then that code won't work and I think if Twitter App is installed in the iPhone we can just launch the app but I cannot pass Data to be Tweeted.
How would you have handled this situation?
http://wiki.akosma.com/IPhone_URL_Schemes#Twitter
Try using one of these URIs. You need to handle the case where the user does not have the app installed also. For that I believe you will want to launch the browser and send a web intent.
I want to directly open LinkedIn app (already installed) from our app. I followed the LinkedIn deep link URL scheme like:
linkedin://profile?id=35932112
The LinkedIn app opens and shows the target person. However, when it is above 3rd degree connection, it shows very limited information and asks to upgrade to premium account. But if I navigates to other persons within LinkedIn app, I can still see the full profile even above 3rd degree connection.
Did I miss anything? Is it LinkedIn policy or I have to do some more configurations?
Thank you very much in advance!
Try using the profile's public url instead, it's working well for me. The LinkedIn app will intercept it and open to the profile instead. The url is usually right under the profile picture and has the following format:
https://www.linkedin.com/in/userid
That's right, you cannot display information based on people that are not your primary connections. On newer versions of the app they restricted it even more; now it returns an error for second and third connections.
There is a way to do that but it's not that straight forward. Not sure what your logic is like and will it be helpful but it's something.
So when you login with LinkedIn you can request the public-profile-url property, it will be returned in the result as publicProfileUrl and then you can save it in your backend. This way it will be saved for all the users that has authenticated for the app. When you try to open that link it will open the LinkedIn app or Safari with that profile.
PS: Hope this helps someone, I can see you question is some time ago :)
I have a process that pulls all of the User's profile photos through a NET:HTTP connection. The problem is that I don't know if a user's account is using HTTP or HTTPS- the process works fine if I get this detail right. Is there a good, reliable way to have the Koala gem surface the user's security level?
I've been digging through the FB apis and cannot find any info on this. Hoping for some suggestions.
I resolved this issue by circumventing it entirely. I re-architected the applications to communicate with each other, rather than each making their own requests to the FB Graph.
The app that connects to the FB api dumps the content I need in the db, then a request is made to the other app (with the id of the new record). That app then calls back to the FB app, which provides a json service containing everything the other app needed from the graph. Completely eliminates http/https issues and authentication issues.
Let's say I want the user to be able to view my Twitter account feed via a button in my app's credits view.
What's the proper way to do this?
I can load the URL easily enough to twitter.com but what if the user doesn't use the web version of twitter but the Twitter app or Tweetbot, etc.?
I failed to find anything obvious about a twitter:// protocol.
Thank you!