I think that depends on what client on what OS you are using, or whether you're using a browser on a desktop, as Facebook uses different domains for different platforms. And I've noticed over time that they don't mind switching or adding domains, so I personally think it's not up to
@thelonelycoder to maintain such a list. He's
probably surely got better things to do. As soon as my wife starts complaining about 'social' limitations, I know Facebook has probably changed something again, sigh...
The process of following the logfile (option
f in the main menu) and whitelisting (or blacklisting, both option
el in the main menu) are both explained in detail at the
website (and on several occasions in this thread). If you enable AB-Solution (a script that has the possibility to block part of your internet traffic) and you suddenly find that an (internet dependent) app has stopped working or has limited functionality, following the logfile using option f is the first thing to look at. It's really that simple.
And yes, you might have to repeat those steps in order to get everything back to work, depending on which blocking file you're using. It helps to have a quiet network and to know which IP is assigned to the device (phone, tablet, pc etcetera) you're using the app or browser on, so it's easier to distinguish which device has tried to connect to a blocked domain. Once you've whitelisted all the required domains, you're all set and done. Until Facebook throws in a couple of new domains, that's when you get back to the f option in the main menu...