webappsec-permissions-policy VS contain-facebook

Compare webappsec-permissions-policy vs contain-facebook and see what are their differences.

webappsec-permissions-policy

A mechanism to selectively enable and disable browser features and APIs (by w3c)

contain-facebook

Facebook Container isolates your Facebook activity from the rest of your web activity in order to prevent Facebook from tracking you outside of the Facebook website via third party cookies. (by mozilla)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
webappsec-permissions-policy contain-facebook
5 27
392 954
0.0% 1.0%
6.9 7.8
7 days ago 29 days ago
Bikeshed JavaScript
GNU General Public License v3.0 or later Mozilla Public License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

webappsec-permissions-policy

Posts with mentions or reviews of webappsec-permissions-policy. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-11-24.
  • Smart Move, Google
    8 projects | news.ycombinator.com | 24 Nov 2022
    Thanks for the docs. The examples (2 & 3, https://github.com/w3c/webappsec-permissions-policy/blob/mai...) seem to me to say that search.google.com can’t grant location permissions to an iframe if the parent was forbidden them, but I didn't find an explicit example for what happens if the iframe domain already got permission previously.

    As you say the UI for requesting in this case would be weird, and this seems like a big security hole to me, but I can’t see a bit of the spec that explicitly forbids (though I only scanned the doc.)

  • Amazon is blocking Google’s FLoC
    4 projects | news.ycombinator.com | 15 Jun 2021
    there is apparently no way to define a default disable either, so to turn off all the random features, the header becomes huge.

    https://github.com/w3c/webappsec-permissions-policy/issues/1...

    What is happening in w3c?!

  • Optimise your site - Addressing recommendations from securityheaders.com
    1 project | dev.to | 30 Apr 2021
    This took a fair bit of investigation. I'm not convinced that it's the most well-documented header, in terms of the properties that you can set. Effectively, this is a list of values that determine which permissions are allowed for this website. Given I don't need access to location, camera, microphone or accelerometer. I did have issues finding consistent documentation on this one, so ended up having to combine the Feature-Policy documentation from MDN as well as the permissions policy examples from w3c.
  • User-Agent Client-Hints, take 2
    2 projects | dev.to | 12 Mar 2021
    Since Chrome v84 the Chrome team has had a few set backs which has resulted in some changes. In addition, the feature policy header, for delegating the client hints to third parties, has changed name to Permissions-Policy.

contain-facebook

Posts with mentions or reviews of contain-facebook. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-28.

What are some alternatives?

When comparing webappsec-permissions-policy and contain-facebook you can also consider the following projects:

ichnaea - Mozilla Ichnaea

noscript - The popular NoScript Security Suite browser extension.

OsmAnd - OsmAnd

firefox-container-proxy - [Firefox extension] Assign a proxy to a Firefox container

webappsec-feature-policy - A mechanism to selectively enable and disable browser features and APIs [Moved to: https://github.com/w3c/webappsec-permissions-policy]

Why-you-should-avoid-Google-AMP - An article on what Google AMP is, how it is destroying the openness of the Internet, and how to stop using it.

ua-client-hints - Wouldn't it be nice if `User-Agent` was a (set of) client hints?

Content-Type-Fixer-extension - Firefox extension to override dumb Content-Type headers with correct values

invidious-redirect - A (very) small WebExtension to redirect YouTube links to Invidious.

ViewImage - Extension to re-implement the "View Image" and "Search by image" buttons into google images.

hosts - 🔒 Consolidating and extending hosts files from several well-curated sources. Optionally pick extensions for porn, social media, and other categories.

contain-google - [Looking for maintainer] - Google Container isolates your Google activity from the rest of your web activity in order to prevent Google from tracking you outside of the Google website via third party cookies.