Facebook 2019 Version

[Madox Valdivia]

Im the author of a Wordpress plugin that leverages the Facebook Graph API. Recently, some Graph calls are failing for new plugin users (only new users are affected). After some digging, I believe I've stumbled on the cause here:

So that leads to my first question: Am I missing something here? To me, this behavior seems to make versioning pretty much useless; whether or not my calls specify v2.0, Facebook will just call into the newest version that existed when that app happened to have been created. So the two-year time window Facebook gives for supporting old api versions (see ) does nothing, as I always need to support the most-current version the moment it's released (or new users with newly-created apps will be broken). Right?

Second question (assuming the above is correct): How can I query Facebook for the version that's being used (or rather, available to be used) by the current app? Since specifying v2.0 clearly doesn't mean it'll actually use v2.0, finding out if it's using an unexpected version could at least help preempt possible errors - i.e. it'd be valuable info to include with user bug reports. I expect that this information must somehow be in the access_token, but I've searched high and low and can't figure out how to ask, "What API version does this token apply to" (or perhaps, "What's API versions does this app support," or similar)?

endpoint, which will give you the Unix Timestamp when the respective App was created. See -api/reference/v2.1/app/#readfields You can then use for example PHP or JavaScript to transform the Unix Timestamp to a date.

It seems that an 'm' has accidentally found its way into my safari browser when launching Facebook. It now always launches the mobile version, no matter how many times I retype or delete the m, it autocorrects and it will only launch the mobile site. I have tried to delete browser history to no effect. What can be done?

Thanks Eric, I have tried all and it is still faulty. Now I have managed to relauch Facebook properly, but it only shows certain sites from the notifications menu. The moment I tap on my account or on home, it relaunches the mobile version. I am wondering if it is a Facebook issue as well. Anyway, I prefer to use it on my mobile devices at this stage since it is a pain on the mac.

Hi Dominic, I don't have the same menu in my safari. There is no 'search' or 'notifications' either. There is an option for 'prevent search engine from providing suggestions' in privacy which I have turned on, but it does not appear to be working. The search engine keeps on providing suggestions.

Two years ago, as we saw our repository continue to grow at a staggering rate, we sat down and extrapolated our growth forward a few years. Based on those projections, it appeared likely that our then-current technology, a Subversion server with a Git mirror, would become a productivity bottleneck very soon. We looked at the available options and found none that were both fast and easy to use at scale.

The rate of commits and the sheer size of our history also pose challenges. We have thousands of commits being made every day, and as the repository gets larger, it becomes increasingly painful to clone and pull all of it. Centralized source control systems like Subversion avoid this by only checking out a single commit, leaving all of the history on the server. This saves space on the client but leaves you unable to work if the server goes down. More recent distributed source control systems, like Git and Mercurial, copy all of the history to the client which takes more time and space, but allows you to browse and commit entirely locally. We wanted a happy medium between the speed and space of a centralized system and the robustness and flexibility of a distributed one.

Enabling the remotefilelog extension for employees at Facebook has made Mercurial clones and pulls 10x faster, bringing them down from minutes to seconds. In addition, because of the way remotefilelog stores its local data on disk, large rebases are 2x faster. When compared with our previous Git infrastructure, the numbers remain impressive. Achieving these types of performance gains through extensions is one of the big reasons we chose Mercurial.

Mercurial has several nice abstractions that made this extension possible. The most notable is the filelog class. The filelog is a data structure for representing every revision of a particular file. Each version of a file is identified by a unique hash. Given a hash, the filelog can reconstruct the requested version of a file. The remotefilelog extension replaces the filelog with an alternative implementation that has the same interface. It accepts a hash, but instead of reconstructing the version of the file from local data, it fetches that version from either a local cache or the remote server. When we need to request a large number of files from the server, we do it in large batches to avoid the overhead of many requests.

To help personalize content, tailor and measure ads and provide a safer experience, we use cookies. By clicking or navigating the site, you agree to allow our collection of information on and off Facebook through cookies. Learn more, including about available controls: Cookie Policy

This may be a browser sniffing issue. Many sites will check the user agent string (gives version of browser being used), if it believes that you are using a mobile version of the browser it will re-direct you to the mobile version of the site. Try resetting the user agent string to see if it helps. For details of how to do that see How to reset the default user agent on Firefox.

I've this problem sometimes in some sites. Not just for facebook. For example, now I can't access the normal page www.claro.com.br. I'm redirected to claro mobile.I've just deleted my .mozilla directory from my home and the problem persists. I've cleaned the cache, objects, cookies and it doesn't work.

Are your firewalls that maxed already? Generally speaking you don't see a massive performance hit simply decrypting untrust traffic on current platforms. Unless you're already pushing the limits of your platform, enabling decryption on your untrust traffic shouldn't push your resources on your firewall that hard.

1- I really don't want to decrypt "everything" because it might cause performance issues on the firewall, even on the 5250 platform. This firewall is does everything for both inbound and outbound traffics, including globalprotect.

1 - Anything within the 5200 series was designed from the ground up to have decryption cause limited impact. These boxes are designed to decrypt the traffic, and enabling decryption has limited overhead on these platforms. Unless you're already running into the platform limits of the 5250 and your firewalls weren't sized properly, you aren't going to run into anything by enabling decryption for untrust destined traffic. If you want to be extra cautious, enable it in limited groups so you can see the actual impact until everyone is included.

2 - Again, unless you are already reaching platform limits you aren't going to "choke" the firewall by decrypting untrust traffic. The 5200 series is designed to decrypt traffic with minimal impact to system resources, so unless you're already struggling you aren't going to choke it by enabling decryption.

Yes, I have, and when you decrypt everything it works a whole lot better than what you are describing. You shouldn't have any issues blocking posting or uploading images and the like. You won't be able to block liking posts or commenting; that is all going to get categorized as Facebook-base which you aren't blocking. If you want to go that far, you need to simply block access to Facebook.

@BPry: I finally get in touch with a senior TAC engineer from PAN and he agrees that my setup is correct. I do NOT have to decrypt everything. After I showed him, he agreed that the some of FB apps do NOT work as designed. I am able to show him that when using Firefox, users can NOT post on FB but users CAN post on FB using Chrome and Microsoft Edge. Finally I got a hold of a PAN Engineer who knows what he is doing, after many weeks of frustration.

You're wrong about not being able to block "like" and comments in FB. Both "like" and "comment" are part of facebook-posting app. The facebook-posting is not working as it should. The TAC engineer will take it up with their content team.

Interesting ... So if I'm to understand this correctly, I'm wrong because the signature works exactly as I told you they did and everything I told you is correct as things stand today ... okay.

What I am trying to say is that the PAN is NOT blocking "like" and "comment" as it should have. It is NOT working. It is being investigated by PAN TAC support. The FB apps "facebook-posting" should have blocked the "like" and "comment" but it does not. I do not allow "facebook-posting" in my rule base.

I heard back from PAN support after the case was opened six weeks ago. PAN support that it is a code issue in Application and Threat update. They will update the application and threat update sometime in the first week of March. Will see if they actually fix the issue.

On May 1, 2020, Facebook will remove version 2.12 of the Facebook Graph API. This change impacts Amazon Cognito customers who are using version 2.12 of the Facebook Graph API in their identity federation configuration. In this post, I explain how to migrate your Amazon Cognito configuration to use the latest version of the Facebook API.

3a8082e126