I'm going over Facebook's Open Graph API. All of it seems simple and is explained well except for the fb:admins meta tag. What is this for?
For example:
<meta property="fb:admins" content="USER_ID"/>
Facebook says this: A comma-separated list of either Facebook user IDs or a Facebook Platform application ID that administers this page. It is valid to include both fb:admins and fb:app_id on your page. I'm just not sure what this is.
I guess it is the combination of the ids that is tripping me up.
If you any of the social plugins, fb will look at the fb:admins tag to determine access to admin features directly from your site. For example, if you use the comment box, and you have <meta property="fb:admins" content="USER_ID"/> with your fbid, while logged in, it'll give you access to moderate the comment box. At least, thats my understanding
Related
Working on log analysis, I found a string with odd syntax and contents, by parsing page field of web log (a webshell?):
/campaign/(f(2ewt_ygmarlagti7sw4tvhj0zk17klgxnhnk1aawgtixm5x-2qmvsvouolvaffrhitumf4wnk496p2dbzmkc3ywfloksiixdtrlawmt78f_mg-45kdzzpdlnogeishkcgtohttp://www.facebook.com/externalhit_uatext.phptelf6gqmu2ia0i1j5lfgmcvw1))/home/index
Could someone guide me how to decode this string and find a clue ? Also why is the following:
http://www.facebook.com/externalhit_uatext.php
included in the string?
I am quoting https://www.facebook.com/externalhit_uatext.php
Facebook allows its users to send links to interesting web content to other Facebook users. Part of how this works on the Facebook system involves the temporary display of certain images or details related to the web content, such as the title of the web page or the embed tag of a video. Our system retrieves this information only after a user provides us with a link. You may have found this page because a Facebook user sent a link from your website to other Facebook users. If you have any questions or concerns about any links or content sent by one of our users, please contact us at legal#facebook.com.
My guess is that someone posted a link to your website to Facebook and someone clicked on that link (visited your website through that link). The (probably) encoded stuff seem a bit random though. If I were you I would either post a link from my website on Facebook, click on it and see if I get something similar. If it doesn't look like that, I would contact legal#facebook.com to clarify whether it is linked to them.
This has been driving me nuts all day:
I have an iOS app with a custom URL scheme defined, and am trying to share a link on FB which points to a page that has this scheme in its applink meta tags, so that tapping it should fire up my app.
Every little piece of it is working just fine. I can enter my URL scheme in safari on the phone and the browser launches my app. I have tested my webpage with the FB debug tool and there are no errors or warnings - it correctly identifies all the meta tags.
If I share the link using FB on the phone or on my laptop, all works fine.
HOWEVER, if I share the exact same link using FBSDKShareDialog, it does not work. It just opens the web page with the meta tags as if it was any regular web page.
Anyone has any idea why these two ways of sharing would be different? They look exactly the same otherwise.
If anyone else runs into this problem, here's the reply from FB:
When you share with mode automatic, the app does a fast app switch over to the FB app to show the native share dialog
The post is cached locally on the device, and it does not know about app links (since only Facebook server side knows about it)
When the user opens the FB, the user sees their cached story (with no app links behavior),
This doesn't manifest with the Web mode since the Facebook app needs
to pull from the server to get the post, in which case it has all the
app links info.
This is unlikely something that we'll fix. However, after a while, the
cache will expire, and Facebook app will re-pull the posts from the
servers, in which case the app link data will be available.
In order to test this, you can share the post on one device, and then
try clicking on the post from another device. The app links should
work at that point.
Which is kind of a lame response IMO - they parse the target page to build the preview, how hard would it be to remember the applink and use it?
There could be two possible issues:
Either the one told by #NJ, i.e. you are just trying to open the link in Facebook app, using the same device from which you posted the link.'
Solution - either open link in other device or cose and re-open your facebook app and do multiple refresh
Or You have some error in your meta tags. There is one important thing though, that Facebook never mentions, i.e. they cache the URL you provide.
So any one used the web link with meta tags the first time in Facebook, Whole meta tags will be cached, and you updated meta tags won't be parsed by facebook.
Solution
To get over with the issue, use below link
Facebook debug tool
Input your meta data included web page URL and
-click on show existing scrape information to find any error
Click on Fetch new scrape information for refreshing your URL on facebook. it will clear the cache for that URL in facebook server.
I'm using a custom action and I'm creating my facebook object on a different page than the page the user is meant to visit when they click the story on their timeline.
Is there any way I can sneak the right URL back in?
EG. To publish story from XYZ website, an object is automatically generated on ABC page for facebook to consume. We want the user to click on their timeline and still visit the XYZ page.
The simplest method is with a meta redirect in your objects meta tags.
<META http-equiv="refresh" content="0;URL=http://XYZwebsite">
A while ago I experimented with facebook apps and I specified custom og:types on my website.
It's a photo website with about 20,000 individual URL's and growing by about 1000 per week and the two object types I specified were these:
<meta property="og:type" content="mynamespace:album" />
(for thumbnail overview pages of a photo album, currently about 200 of these)
<meta property="og:type" content="mynamespace:picture" />
(for detail view of individual images, currently about 20,000 of these)
However, I never followed through with developing a custom app because I felt it wasn't worth users having to sign in and authorise my app just to like/share pictures so I ended up using the standard social plugin "like button" on these pages.
Unfortunately I forgot to remove the custom object types though. Now the likes on the social button seems to be counting correctly and the facebook linter doesn't complain about anything, but I am a bit worried if there are any adverse implications by leaving it like that, because when I removed the custom type temporarily (which I thought would then default to og:type website) the debugger warned me that the object previously had another type and that data might be corrupted. It is now using the custom object types again until I can find a solution...
So what should I do? Remove the custom types or leave them? What are the implications of either option? Is my content being shared correctly on the users walls if a user clicks the social plugin "like" and it finds a custom og:type?
Would be grateful if someone could clarify the best way out of this mess without screwing up all the accumulated user activity from the social plugin.
Thank you!
Facebook encourages developers to tag their content using open graph tags using tags that relate as closely as possible to the content itself. There will be no adverse effects to changing the tags present in a pre-existing tag, and it is just a warning that Facebook outputs, in case you had changed the tags by mistake.
Facebook uses the tags to categorise incoming posts (as the first time it is liked, Facebook sends a scraper to your page to find out what it can about it), and in the end, "anything helps". By changing the tag, it won't affect the classification of the posts published previously, but any new posts will have the new tag information.
If your new tags more closely resemble the content, then change away.
I want to create chrome extension that will show only the top stories from google news page. Now through permission in menifest will I be able to get the required div of google news page ?
You can get information on any page if you request corresponding domain permissions in manifest. Instead of parsing google news html it probably would be easier to parse its rss feed instead (if there is one).