facebook-pages

4

PAGES LIKE THESE ON FACEBOOK LISTEN UP: there are numerous Facebook pages that have been using my cosplay photos and not linking back.
If you admin these or have seen this please link back or ask the admin to link back to my blog.
Better yet report , or let me know.
I do not appreciate not being linked back. I cosplay and would like to be known for it. So if my weddingstuck photos are being passed around on Facebook pages please do link back to me.

This counts for all of my cosplays. I hate how these pages do not credit artists I’m generally okay with being reposted as long as I’m linked back but a lot of others state on their pages that they are not so when you do repost please link back. But these pages do not do this, they find images from google and refuse to right click and find the source and ignore who the Cosplayer is and then that Cosplayer is not known or credited. This is wrong because as an artist I would like to be known and I think all artists deserve recognition. So if you don’t know who is in the photo or who did what don’t post it. Just don’t. This speaks for face book, tumblr, Instagram , ANYWHERE! THESE PAGES NEED TO NOT DO THIS
I REPEAT THESE PAGES NEED TO NOT DO THIS
ESPECIALLY IF AN ARTIST HAS SAID TO NOT REPOST THEIR WORK OUTSIDE OF TUMBLR OR WHERE EVER YOU FOUND THE WORK

DO NOT DO IT.

THIS IS WRONG.

youtube

https://www.facebook.com/pages/Big-Time-Games/446271218777876
Please listen and give your support everybody, I’m counting on you!

-Badger 
Narrator / Admin

 

Getting Your Tumblr Posts on a Facebook Page Timeline

After a long time of having this option disabled (or simply not available) we can now send our Tumblr posts to a Facebook Page once again (We talk about Pages here, Not Profiles).

  1. Go To Blog Settings >> Check Share posts on your Timeline
  2. After you log in to Facebook you will see a message that says: Tumblr would also like permission to: Manage your pages Tumblr may login as any of your X Pages, including: (A list with your Pages). Click on Allow.
  3. Now, Go Back to your TUMBLR and go to Blog Settings >> Scroll Down and, from the dropdown menu (that was not there before) choose which page (or profile) you will send your posts to.

Source: Send Tumblr Posts to Facebook Pages.

Major Facebook pages getting mass-spammed by pro-Muslim activists

In an effort to draw attention to the controversial YouTube video that has sparked major protests in the Middle East and may have led to the death of a U.S. ambassador, protesters have taken to a number of major news and celebrity Facebook pages to spam a variation of the above message — no matter on which post. The message here is from the Sky News page; other pages that have been hit include Reuters, The Washington Post, Barack Obama and Michael Phelps. The New York Times has more info on the controversial video that sparked these protests.

The value of a 'like'

Recently I got myself involved in a LinkedIn group conversation which was aiming to connect small businesses with a Facebook page, to other small businesses with a Facebook page, in order to generate some additional ‘Likes’.

Attracted to the post based on it’s simplicity, and being a social media buff I was excited by the opportunity to connect with other professionals - I signed right up!

From this one posting I gained an additional fifteen 'likes’ in just 48 hours. Not bad going.

However, it also got me thinking deeper about value. 

Great, I’ve got fifteen new people/businesses to talk to online but how many of those am I genuinely connected to? How many leads am I getting from it?

The answer is zero, for now! What I propose here is that it goes back to the age-old debate of quality versus quantity. So, how valuable are my likes exactly?

Below I set about starting to explore the pro’s and con’s then provide a short analysis on what I think it all means.

What’s good about a like? /// 

  • Increase visibility
  • Connect you with other businesses and individuals
  • Promote your page via your 'fans’
  • Increase readership potential
  • Link to your blog, website, Twitter…
  • Help develop your SEO 

And the downside? ///

  • Fans can filter information from you
  • You are more exposed to spam
  • You cannot control the wall posts from others
  • Numbers do not equal loyalty.

Do numbers = popularity? ///

It may look great having hundreds (maybe thousands) of 'likes’ on your business page but if you are keen on stats, it is much better to monitor; conversations, 'liked’ posts and shares. 

If you are leading a popular page then this is where the real value in knowing your numbers lie.

Is having a business page worth it? ///

The simple answer is yes! You can see above that the pro’s far outweigh the cons. So we have established an element of value, but how do you judge yours?

I have created myself some a list of rules which help establish my integrity:

  • I want to create useful and rewarding content
  • I want to reach people genuinely interested in my business and/or topics
  • I want to connect with potential clients, customers and peers
  • I want to engage with other businesses I genuinely like.

After opting to put my Facebook page onto the LinkedIn group, I actually received a couple of spam wall postings too. I’ll define the spam like this: no greeting, no acknowledgement of the page or how they found it, just a link to their page! That’s not how I want to grow page 'likes’, or do business. It’s just not valuable, nor is it an engaging way to generate contacts. This is why integrity matters.

Who is it good for? ///

It’s probably something SME’s in the B2B arena will benefit from the most. If you are a B2C business then growing and monitoring your Facebook page activity in this way may prove fruitless, as consumers fit a much wider bracket. You can however advertise your page targetted to specific interests and age groups etc so there is a level of control available.

Conclusion ///

The quality of your readership/fan base/likes is much more important. Growing it based on your own integrity may take longer but you can be assured that the people and businesses you connect with are interested and, like 'real-life’ clients, you build a level of trust with each other (which is what I hope for Pinch too).

Finally, it is probably worth pointing out here that, if you do choose to develop your own page in this way, it has echoes of an integrated approach. If you align you online (and offline) practices to your goals they are more likely to be met.

If you would like to read further about making the most of your Facebook business page then take a look at the links I’ve pulled together for you below. From beginner to advanced, hopefully there is something for everyone.

If you like what you read and want to keep up with more Pinch views, tips and news, then please do connect on Facebook

Want to know how you are performing online? Exclusive reader offer is available via the QR code in last week’s post. Click here to crack it or Pinch Me /// to get in touch and see how best we can work together.

COSPLAY FACEBOOK PAGES & REACH

Hey there! I’m smzeldarules, a cosplayer in Western New York. I’ve been cosplaying since 2006, but took a break while I was in college. In 2014, a year after graduating, I finally got back into the hobby and also made my active cosplay facebook page! I’ve learned a LOT about facebook’s strange rules and how to get your posts shared with more people from having my cosplay facebook, my graphic design facebook (which I confess, I’m not very active on), research, and even a little bit from my job. I hope to help cosplayers looking for stress-free and money-free ways to improve their facebook reach with these tips!

1. Create a fanbase of people who will interact with you.

            - FIRST THING’S FIRST, the number of followers you have or get is NEVER what should matter, what DOES matter is how interactive they are with your posts; and that means you should aspire to get followers who will like what you make and talk about what you post with you. If you just get random people to like your page, they will become “empty likes” and might even unfollow you.

2. Find which posts get the most interactivity.

            - You can find your most interacted posts by going to your page’s “Insights” tab, scrolling down to the “Your 5 Most Recent Posts” and clicking it to see all of your posts, then filtering the table by Reach. It should then list them with the most engagements at the top.

            - Ask yourself: What works about these posts? Why did so many people like/comment/share/engage with me about these specific posts?

            - Try to do the same for a lot of your posts, whether it be the content in the photo you posted or the link you shared, or maybe it was the way you shared/posted it. You now know what most of your followers are most interested in regarding your cosplay, and if you keep that up, your followers will eventually end up getting more people to talk about your work and discuss with you on your posts. When people engage with your posts, since they are more than likely public, their friends are most likely going see their engagement on their news feeds, and if they’re interested they might want to follow you too!

3. Square images for timeline posts are key!

**Disclaimer: **Keep in mind this is just for timeline posts! Do whatever the heck you want with photoshoot photos and other pictures; I’m sure they’re absolutely beautiful no matter what size and they deserve to be unedited :) But anyway,

            - Facebook apparently will automatically try to “boost” timeline image posts with equilateral sides more than if they don’t have equal sides.

            - 504x504px is the size in which square images will be displayed on your timeline. When you click it, will be closer to real size. Long vertical pictures will be shoved to the left though. So it’s better to post horizontal images with a minimum width of 504px than vertical images if not square.

            - Use Photoshop or any equivalent. I even suggest posting instagram photos often if you can because they’re automatically square!

            - Square images also look way nicer on people’s newsfeed if you’re just posting one image as a timeline post. Example:

4. Boosts for free!

            - You DON’T need to spend money for Facebook to “boost” your post. If you have a good amount of followers who interact with you regularly, and you post things that your followers are most interested in, one thing at a time, “boost"s will just happen. Timeline image posts being the sizes Facebook focuses on do help, but a big chunk of people who follow and interact with you are more important. Obviously interaction won’t be as huge as if you give into the corporate devil and pay Facebook for it, but don’t you want people who are genuinely interested in your work following you, and not random people who don’t give a crap and will probably just unfollow you the next day?

Thought so.

            - If you’re willing, tag your personal page in your photos. It will increase the reach to your personal friends, since they are more than likely going to see "Your name” was tagged in “Your cosplay page”’s picture. When your friends like your posts, since they’re public, their friends are more than likely to see it too; another way to increase reach. You could even do this to get your page started and then stop tagging yourself in posts that you don’t feel like tagging yourself in.

            - The scheduled post function is wonky for multiple reasons. For one, your page will still say it was posted at whatever time you scheduled it. Say for instance, you schedule something to be posted in 2 weeks - once the time does come, it’ll be posted and on your page it will say the date and time of posting. But, it will be shown on your cosplay page as posted 2 weeks prior so it won’t be shown on your photo collage at the left side of your screen if you post pictures regularly. It will be seen in your albums, but as a photo from “2 weeks ago.” I don’t know if it’s just me but I hate that.

            - There’s just a lot of bugs in the scheduled posts function; I’d rather just wait for Facebook to fix the bugs in it…if they ever do. More than half the time it messes up for me and doesn’t even get shared with many people anyway, no matter what size an image is or what the content is! “Boosts” very rarely happen on posts I schedule as well. So in my opinion, at the current state it’s in, scheduling posts aren’t worth it.

           - Time of day can help boost your post reach too. I usually find lunch time and 5pm-6pm on weekdays do very well. I have pretty good luck with any times on the weekend too.

5. **~~~Pretty graphics~~~**

            - Make sure you have a really nice profile picture and cover photo showcasing some of your best work!

            - Believe me, it really makes a difference. It might be the graphic designer in me talking for the most part, but I cringe when I see graphics that are stretched out! I see it mostly on cover photos. Do a little research, find a graphic editor software to make one, or have a friend make one for you! Facebook cover photos are 851x315px, and then profile pictures are going to be shown as a square no matter what with the current layout.

            - Even making a logo for your cosplay name is a nice touch if you want! Cosplay for me is just a fun hobby, but being a graphic designer at the same time motivates me to create eye catching graphics already, so it’s just an added bonus I guess.

           - Make your graphics .pngs as much as possible! Facebook really likes to decrease the quality of jpgs (which are already compressed).

6. Spam4Spam… I mean Share4Share is the devil.

            - This is part opinion but also factual as well.

            - Basically s4s is literally just spam to me unless you’re wholeheartedly expressing interest and appreciation for the person’s work.

             - You’re just clogging up your followers feeds AND WILL POTENTIALLY LEAD TO PEOPLE UNFOLLOWING YOU, which means LESS REACH! Do you really want that? All the power to you if you do but if you’re mindlessly just sharing people’s pages and not even posting your own cosplay work, people will ask themselves why did they even like your page in the first place?

7. Change up your content every now and then.

            - Just a little SEO tidbit. Changing content and the way things are worded will help search engines pick up your page - This goes for not just facebook pages but any webpage you have!

Feel free to ask me questions if you stumble upon this and/or share with friends!

Here’s some other helpful links too:

“All Facebook Image Dimensions: Timeline, Posts, Ads”

“10 Changes to the Facebook Page Layout: What Marketers Need to Know”

“Fb pages: Sizes & Dimensions”

smzeldarules / / facebook | cospix | worldcosplay | acp

Facebook, an Indian, and a Chinese guy Understand THIS...MEANWHILE, Third-Party Bloggers are FUCKED!

f8 Videos Available

We had an awesome f8 conference in San Francisco last week. Thanks for everyone who attended or participated via one of the many viewing parties. Videos of all of the f8 sessions are now available online at https://f8.facebook.com/.

Scraping OG Objects

We’re already hard at work improving the Open Graph since last week’s announcement. This week, to make updating Open Graph objects easier, we’ve released the ability to scrape objects at the same time as you publish actions. Just add scrape=true to the POST parameters when publishing the action:

https://graph.facebook.com/me/recipebox:cook? scrape=true& method=POST& recipe=http://www.example.com/pumpkinpie.html& access_token=YOUR_ACCESS_TOKEN

Note that you only need to scrape an object if the meta tags have changed. If we ever encounter an URL that we’ve never scraped, we will scrape it regardless of the absence (or presence) of the scrape parameter. We also automatically scrape objects approximately every seven days, though we will respect Expires: headers. See the Open Graph documentation on Creating and Using Actions for the full details.

Reminder: Breaking Changes coming on Oct 1st

The following breaking changes are slated to go into effect on the 1st of October:

  1. OAuth 2.0 Migration

    All apps must migrate to OAuth 2.0 for authentication. The old SDKs, including the old JavaScript SDK (FeatureLoader.js) and old iOS SDK (facebook-iphone-sdk) will no longer work.

  2. Apps on Facebook authentication and security migration

    All Canvas and Page tab apps must convert to process signed_request (fb_sig will be removed) and obtain an SSL certificate for use in Secure Canvas URL and Secure Page Tab URL (unless you are in Sandbox mode).

  3. Auth 1.0 deprecation

    Auth.promotesession, auth.createtoken, auth.expiresession, auth.getsession will be removed on Oct 1st. Details on support for OAuth 2.0.

  4. manage_pages permission required to access user accounts (/me/accounts)

    We are modifying access to the FQL page_admin table and the graph.facebook.com/me/accounts endpoint. Previously, with basic permissions granted, an app could go to this endpoint or the FQL table to access the list of a users’ apps and Pages. We are going to require that apps have the manage_pages permission in order to obtain access to this information.

We will post an update on the rollout plan on Monday, Oct 3rd (the changes themselves will proceed as planned).

Canvas Ticker Flyouts

Last week, we launched flyouts for the Canvas ticker. These flyouts appear when a user hovers over or clicks on a ticker story. They provide richer information to users about what’s going on with their friends, and often allow users to like and comment on the story.


For games, we have also launched “passing stories” in the Canvas ticker. These are stories in which gamers are informed when one friend gets a new high score which exceeds another friend’s high score. This is most appropriate for arcade-style games where you get a score each time you play. To have these stories appear for your app, make sure to use the scores method in the Graph API each time your user gets a new high score.


One important side effect of this change, for apps using Adobe Flash, is that it is more important than ever that your app use “opaque” mode for any flash objects occurring within the iframe. If you don’t, your game will be hidden when a popup occurs. Please see Special Considerations For Flash Developers for more information.

Support for Multiple Domains in the Developer App

We have heard from developers that only being able to set one App Domain in the Developer App is sometimes not enough. For example, if you are redirecting users for geographic distribution of load, you may want to redirect some users to a URL in the myapp.com domain, while redirecting others to a URL in the myapp.co.jp domain. Now, you can do this in the Developer App. Simply set multiple domains in the App Domain field:


Now, you can specify a redirect_uri in either domain. Your App’s URL (Website and/or Mobile Web URL) must be derived from one of the domains listed in the App Domain field.

Resources from “Making Fast Social Apps” talk at f8

After last week’s f8 conference, several people asked for references to the resources mentioned during this talk. Here are the links mentioned in the presentation:

Bugs

A couple of weeks ago, we introduced a new bugs tool. In the past week in the new bugs tools there were:

  • 381 bugs reported
  • 22 bugs accepted
  • 7 bugs fixed

Although no new bugs can be filed in Bugzilla, we will continue working on closing out the remaining open bugs in Bugzilla. The total number of open bugs in Bugzilla is now 1,381 (up 56 from last week, due to re-opened bugs).

Facebook Stack Overflow activity

Activity on facebook.stackoverflow.com this week:

  • 574 questions asked
  • 178 answered, 31% answered rate
  • 316 replied, 55% reply rate


Requests are an important Social Channel for users to communicate with their friends from within apps. Coupled with the Open Graph updates announced at f8 last week, Requests continue to be a core part of how people share app activity with friends.

As part of the FBML deprecation, we will stop supporting our old request model and will no longer fix bugs on January 1, 2012. We highly encourage all developers to move to Requests 2.0 by this date. Today we’re announcing several new features to Requests 2.0 to make the process of sending and receiving requests even more efficient for users and developers.

New features for Requests 2.0

We have heard repeated feedback from developers and users that requiring users to click ‘Send Request’ every time they wish to send requests to the same friends interferes with game play and limits sharing. To reduce this friction, we’re introducing frictionless Requests, which improves the experience for both users and developers.

Frictionless Requests enable users to send requests to specific friends from within an app without having to click on a pop-up confirmation dialog. Upon first sending a request to a friend from within an app, a user may authorize the app to send subsequent requests to the same friend without prompting for his permission. By default, the check box is checked. This removes a dialog from the flow and streamlines the process of sharing with friends.

To enable frictionless Requests you must initialize the JavaScript SDK with ‘frictionlessRequests:true’. You’ll send requests to users via the Requests Dialog just as before. As users share with friends, they may authorize the app to send future requests to specific friends on their behalf.

You can specify an array of user_ids in the ‘to’ field of the request dialog. Only if all of the user_ids are frictionless, the confirmation dialog will not display and the users will be notified of the request. If even one of the recipients is not frictionless, the confirmation dialog will be displayed and the user must press ‘Send Request’ for the requests to be sent.

Here’s a full JavaScript example for how to use frictionless requests.

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="https://www.facebook.com/2008/fbml"> <head> <title>Frictionless Request Example</title> </head>  <body> <div id="fb-root"></div> <script src="http://connect.facebook.net/en_US/all.js"></script> <p> <input type="button" onclick="sendRequestToOneRecipient(); return false;" value="Send Request to One User" /> <input type="text" value="User ID" name="user_id" size=”50” /> </p> <p> <input type="button" onclick="sendRequestToManyRecipients(); return false;" value="Send Request to Many Users" /> <input type="text"  value="Comma Delimited List of Multiple User IDs"  name="user_ids" size=”50” /> </p>  <script> FB.init({ appId  : 'YOUR_APP_ID', status : true, cookie : true, frictionlessRequests : true, oauth: true });  function sendRequestToOneRecipient() { var user_id = document.getElementsByName("user_id")[0].value; FB.ui({method: 'apprequests', message: 'My Great Request', to: user_id,  }, requestCallback); }  function sendRequestToManyRecipients() { var user_ids = document.getElementsByName("user_ids")[0].value; FB.ui({method: 'apprequests', message: 'My Great Request', to: user_ids, }, requestCallback); }  function requestCallback(response) { // Handle callback here console.log(response); } </script> </body> </html>
Performance improvements

We have spent the past few months on rewriting the back-end for requests to make them faster to ensure users have the best experience with Requests 2.0. However in doing so, we ran into issues which require a breaking change to Requests 2.0 to make them more efficient.

To opt-into higher performance Requests 2.0 enable the migration “Requests 2.0 Efficient” in the developer app. This setting is available in the Advanced section of your app settings.

Setting the ‘Request 2.0 Efficient” in the app migration changes the format for request IDs in the JavaScript requests callback method.

Previously the response param that looked like:

{ request_ids: ‘request_id1, request_id2, …’ }

With the “Requests 2.0 Efficient” migration, the JavaScript request callback method now receives a response param like below to represent the changes to the request ids explained above:

{ request: ‘request_id’ to:[array of user_ids] }

A request now has a single ID representing the actual request object and is then concatenated with the user_id to create the full request ID which represents the request for the specific recipient.

This prevents a developer from having to make a second GET request back to the Graph API to identify the recipients once a request has been sent. To construct the request ID for a user you concatenate as follows: ‘<request_object_id>_<user_id>’. Thus the request IDs from the example above would be:

150785095008591_499802820 180646335344553_499802852

To delete a request, the developer must issue an HTTP DELETE request to:

DELETE https://graph.facebook.com/[<request_id>_<user_id>]?access_token=[USER or APP ACCESS TOKEN]

Note: You can concatenate the request_id and user_id without doing the migration so that you can verify everything works before actually migrating.

Here is a full PHP sample which shows you how to concatenate the request_id and user_id in order to delete the outstanding requests for a user.

<?php require_once('php-sdk/facebook.php'); $config = array( 'appId' => 'YOUR_APP_ID', 'secret' => 'YOUR_APP_SECRET', ); $facebook = new Facebook($config); ?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="https://www.facebook.com/2008/fbml"> <head> <title>Deleting Requests Example</title> </head> <body>  <?php $user_id = $facebook->getUser(); if ($user_id) {  //Get the Request Ids $request_ids = explode(',', $_REQUEST['request_ids']);   //Construct full Request_Id function build_full_request_id($request_id, $user_id) { return $request_id . '_' . $user_id; }  //For each Request construct full Request_id and Delete foreach ($request_ids as $request_id) {  echo ("reqeust_id=".$request_id."<br>"); $full_request_id =  build_full_request_id($request_id,$user_id);         echo ("full_reqeust_id=".$full_request_id."<br>");  try { $delete_success = $facebook->api("/$full_request_id",'DELETE'); if ($delete_success) { echo "Successfully deleted " . $full_request_id; } else { echo "Delete failed".$full_request_id;  } }          catch (FacebookApiException $e) { echo "error"; }    } } //User TOS if user has not authenticated your App else if (!isset($_REQUEST['error'])){         $params = array( 'redirect_uri' => 'http://localhost/~namitag/requests.php' ); $loginUrl = $facebook->getLoginUrl($params); echo  '<script>window.top.location.href="'.$loginUrl.'";</script>';         } else { echo ("user denied permission"); }  ?> </body> </html>
Migrations and breaking changes

Starting today new apps will automatically be opted into “Upgrade to Requests 2.0” and “Requests 2.0 Efficient" and these migrations will no longer be available in the app settings for new apps. This requires developers to use the new request_id format as detailed above. In addition when a user is directed to your app, by clicking a Request from the app, the games dashboard, or from a Request notification, you must delete the request after it has been accepted. These are not automatically deleted once they have been clicked, thus it is the developer’s responsibility to clear them once they have been consumed. See sample above for how you can delete these requests.

In 90 days - on January 1, 2012- existing apps will be opted into “Requests 2.0 Efficient” and “Upgrade to Requests 2.0” migrations and all developers must ensure that they are using the correct request_id format and deleting requests appropriately.

We look forward to improved requests experience with frictionless Requests and our performance improvements. For more information reference our documentation here. Please provide feedback and thoughts in the comments below.



When Platform launched in 2007, FBML was a key component for developers building on Facebook, with millions of apps successfully built using this technology. Over time, as Platform matured and embraced open standards, such as OAuth 2.0, HTML, and Javascript, the need for FBML has decreased. Last August, we announced our intent to move away from FBML. In March, we removed the ability to create new FBML apps. Today, we are announcing the FBML deprecation schedule:

  • January 1, 2012: FBML will no longer be supported. We will not fix FBML bugs after this date with the exception of security and privacy issues
  • June 1, 2012: FBML apps will no longer work on Facebook. All FBML endpoints will be removed.

We realize that some of you may still be relying on FBML for your apps. We want to make sure that you have all the resources you need for an easy and speedy migration. Over the past few months, we’ve been working with developers to understand the remaining use cases for FBML. Based on these conversations, we identified two primary use cases remaining: Requests and Static FBML tabs on Pages.

Requests

We have already announced the new and improved Request 2.0 which should make migrating from FBML Request much simpler. To upgrade to Requests 2.0, apps should send requests by using the Request Dialog. To learn more about Requests 2.0 and how to migrate from FBML Requests, see our documentation on Requests.

Static FBML

Custom tabs on Pages are an important aspect of Facebook Platform. Many developers and Page admins rely on Static FBML for hosting this content. With the deprecation of FBML, this content must be moved to an iFrame based solution. There are several free iFrame solutions available that allow easy migrate Static FBML content to HTML. The Preferred Developer Consultant Finder on Facebook is a great tool to find PDCs to help guide you through the upgrade process. In addition, we have worked with WildFire, one of these PDCs, to create a step by step tutorial to guide your migration. The tutorial is available here.

We are excited to move into a modern, standards based Platform. Please provide feedback and thoughts in the comments below.



Many of you have received an email reminder to support OAuth 2.0 and HTTPS by October 1st. To help Canvas and Page Tab App developers more easily update their Secure URLs, we have pushed changes to admin.setAppProperties that let you set your secure_callback_url and secure_page_tab_url programmatically. You can read the documentation for this API method here. You will need to use an app access token and the secure_callback_url and secure_page_tab_url must be a fully qualified URL beginning with https:// and must point to a directory (i.e., end with a ’/’) or a dynamic page (i.e., have a ’?’ somewhere).

For example:

<?php $app_id = 'YOUR_APP_ID'; $app_secret = 'YOUR_APP_SECRET';  // Get an App Access Token $app_token_url = 'https://graph.facebook.com/oauth/access_token?' . 'client_id=' . $app_id . '&client_secret=' . $app_secret . '&grant_type=client_credentials';  echo '<pre>'; echo $app_token_url; echo '</pre>';  $app_access_token = file_get_contents($app_token_url);  echo '<pre>'; echo $app_access_token; echo '</pre>';  // Set Secure URLs - modify to the appropriate URLs $set_url = 'https://api.facebook.com/method/admin.setAppProperties?' . 'properties={"secure_callback_url":"https://www.example.com/canvas/",' . '"secure_page_tab_url":"https://www.example.com/pagetab/"}&' . $app_access_token;   echo $set_url;  $set_result = file_get_contents($set_url);  echo '<pre>'; echo 'Set result: ' . $set_result . '<br />'; echo '</pre>';    ?>

We will soon provide this functionality in the Graph API, but wanted to first provide this REST API to help developers meet the October 1st deadline.

FBML apps

We have heard that there is some confusion about whether FBML apps must support HTTPS. FBML developers still need to know whether users are browsing Facebook over a secure connection since they need to detect whether to serve iframe or video content over HTTPS. As a result, FBML apps must obtain SSL certificates in order to serve this type of content to users browsing over a secure connection. If you have an FBML app, please obtain an SSL certificate for your app to receive traffic from users browsing Facebook over a secure connection.

If you enable SSL for your FBML app, please make sure that your SSL certificate includes all intermediate certificates in the chain of trust as our SSL validation is strict. You can use third-party SSL analysis tools (e.g., https://www.ssllabs.com/index.html) to check your certificate status and fix any errors (and warnings). If your SSL certificate has problems, you may see “Empty response received” error when you load your FBML canvas app.

Please let us know if you have any questions in the comments below.



Go to:
http://www.facebook.com/developers/emailsettings.php
Facebook, Inc. P.O. Box 10005, Palo Alto, CA 94303

 »f8 Videos Available We had an awesome f8 conference in San Francisco last week. Thanks for everyone who attended or participated via one of the many viewing parties. Videos of all of the f8 sessions are now available online at https://f8.facebook.com/ . Scraping OG Objects We’re already hard at work …Dogmeat 

mehreenkasana asked:

LOVE the new avatar, you guys!

» SFB says: Hey, thanks! It’s actually tied to our new-look Facebook page, which has a fully-illustrated timeline of our 113 year history. (We may keep the avatar for a couple extra days if people dig it. One reader who shall remain anonymous complained. :( ) Bet you didn’t know we were around for 113 years, did you? Well, it’s true. Check out our post about it from this morning, too! — Ernie @ SFB

Sharing some fandom support ^_^

We all love Dan!!! ❤ ❤ ❤
No, ok, it’s not only this… ;P *tries to be serious*
I just want to share some info on this unofficial Italian Page on fb:

Dan Feuerriegel - Italia

Probably you are all aware of what happened not so long ago with the girl who was admin of this page (rude attitude on twitter and everything happened after this), but I don’t want to talk about this because we all agree on the fact that it was really sad and unjustifiable.
People are people. Fandom is fandom. And for some obscure human reason, we can’t stay all together in peace and harmony even if we all love and support the same awesome man.
Come to the goat farm!! We have peace and love… and Nagron!!
*O* *runs*
Arghhh! Remain on subject, mind!! <__<

Ok, what I was saying… ehm… yes! Concentration! ^O^
I’ve never been very active in the italian fandom - in this page and in general cause there were/are some things that I don’t like/understand :( but we all know that fandom, everywhere, is made by people and people can be… a lot of thing: amazing things and… not so good things :P - but I wanted to share this because I really think that Dan deserves all the possible support, all around the world, so I talked to the admins and they assured me that *the person* who created a lot of problems in the past is no more an admin, obviously, and she can no longer speak on behalf of their page.
They’re sorry for all this mess and now the’re trying to renew the page, changing many things and moderating post and comments in a different way from the past.
I thought I’d post this thing here since I first condemned this page when everything happened, but I believe that anyone should have the chance to change their own path, and I’m sure that they can find the right one this time ^_^

There’s some good in this world, Mr Frodo… and it’s worth… NO! Wrong fandom! Sorry! ;P

 Ok, I know that today is #FF on Twitter and not here LOL but, since I’m sharing love and support for our Fury, let me share even the other fanpages on Facebook:

 Dan Feuerriegel Spain

Dan Feuerriegel France

Dan Feuerriegel Czech and Slovak 

( If I forgot someone that I’m not aware of please tell meee >.< )

Ok, end of sharing, rumbling, peace&love and hearts&rainbows ^O^ now you can ignore me again……. noooo don’t ignore meee! I’m here!! *waves her hands in the air* 
You really must stop with coffee and NagronExtendedScene_ *mind shakes head and rolls eyes*

^__________^

Italian translation under the cut….

Keep reading