Privacy Badger breaks some deliberate third party interactions such as oAuth with facebook youtube disqus etc.

Sometimes when a user tries to use oAuth to log into a site with facebook or google or tries to use disqus to comment on a site or makes some other deliberate interaction with a third party resource it gets blocked. This presents a bad experience to the user who is prevented from using a website in the way they intended. We need to find a generalizable solution to this
### Current Workarounds

_facebook oauth and comments_:
unblock www.facebook.com
unblock connect.facebook.com
unblock static.ak.facebook.com
unblock s-static.ak.facebook.com

_you tube comments_:
unblock apis.google.com

_disqus comments_:
unblock disqus.com

_google oauth_:
unblock oauth.googleusercontent.com
unblock apis.google.com

Start by reproducing the Facebook, Google, YouTube, and Disqus interactions described in the issue, noting which resources Privacy Badger blocks and which manual unblocking steps work. Read the surrounding issue discussion for a proposed generalizable approach. Done means deliberate third-party interactions work without requiring users to manually unblock multiple domains while unwanted tracking remains blocked.

Written by the indexing model from the issue text.