#230 [Suggestion] Block FLoC on GNUSocial

Avoinna
3 vuotta sitten avasi aab · 1 kommenttia
aab kommentoitu 3 vuotta sitten

From https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea

"[...]FLoC is designed to help advertisers perform behavioral targeting without third-party cookies. A browser with FLoC enabled would collect information about its user’s browsing habits, then use that information to assign its user to a “cohort” or group. Users with similar browsing habits—for some definition of “similar”—would be grouped into the same cohort. Each user’s browser will share a cohort ID, indicating which group they belong to, with websites and advertisers. According to the proposal, at least a few thousand users should belong to each cohort (though that’s not a guarantee).

If that sounds dense, think of it this way: your FLoC ID will be like a succinct summary of your recent activity on the Web."

More concise info, the suggestion, and the way to implement it, can be found in https://plausible.io/blog/google-floc.

APACHE:

Adding to https://notabug.org/diogo/gnu-social/src/nightly/DOCUMENTATION/SYSTEM_ADMINISTRATORS/webserver_conf/htaccess.sample

Header always set Permissions-Policy: interest-cohort=()

NGINX:

Adding to https://notabug.org/diogo/gnu-social/src/nightly/DOCUMENTATION/SYSTEM_ADMINISTRATORS/webserver_conf/nginx.conf.sample

add_header Permissions-Policy "interest-cohort=()";

From https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea "[...]FLoC is designed to help advertisers perform behavioral targeting without third-party cookies. A browser with FLoC enabled would collect information about its user’s browsing habits, then use that information to assign its user to a “cohort” or group. Users with similar browsing habits—for some definition of “similar”—would be grouped into the same cohort. Each user’s browser will share a cohort ID, indicating which group they belong to, with websites and advertisers. According to the proposal, at least a few thousand users should belong to each cohort (though that’s not a guarantee). If that sounds dense, think of it this way: your FLoC ID will be like a succinct summary of your recent activity on the Web." More concise info, the suggestion, and the way to implement it, can be found in https://plausible.io/blog/google-floc. APACHE: Adding to https://notabug.org/diogo/gnu-social/src/nightly/DOCUMENTATION/SYSTEM_ADMINISTRATORS/webserver_conf/htaccess.sample <IfModule mod_headers.c> Header always set Permissions-Policy: interest-cohort=() </IfModule> NGINX: Adding to https://notabug.org/diogo/gnu-social/src/nightly/DOCUMENTATION/SYSTEM_ADMINISTRATORS/webserver_conf/nginx.conf.sample add_header Permissions-Policy "interest-cohort=()";
lnxw37 kommentoitu 3 vuotta sitten

LIGHTTPD:

Adding to https://notabug.org/diogo/gnu-social/src/nightly/DOCUMENTATION/SYSTEM_ADMINISTRATORS/webserver_conf/lighttpd.conf.example

  1. Make sure mod-setenv is enabled. See https://redmine.lighttpd.net/projects/1/wiki/Docs_ModSetEnv

  2. Add setenv.set-response-header += ( "Permissions-Policy" => "interest-cohort=()" ).

LIGHTTPD: Adding to https://notabug.org/diogo/gnu-social/src/nightly/DOCUMENTATION/SYSTEM_ADMINISTRATORS/webserver_conf/lighttpd.conf.example 1. Make sure mod-setenv is enabled. See https://redmine.lighttpd.net/projects/1/wiki/Docs_ModSetEnv 2. Add `setenv.set-response-header += ( "Permissions-Policy" => "interest-cohort=()" )`.
Kirjaudu sisään osallistuaksesi tähän keskusteluun.
Ei merkkipaalua
Ei osoitettua
2 osallistujaa
Ladataan...
Peruuta
Tallenna
Sisältöä ei vielä ole.