Is this list documented somewhere? I searched for "privacy.query_stripping 
site:mozilla.org" and found only developer-centric links (Bugzilla issues, 
mailing list posts, commits, etc.)

Thanks,
Daniel Serodio

On Wednesday, June 29, 2022 at 3:33:26 AM UTC-3 xintrea wrote:

> This is a very strange decision. It will be necessary to create a WEB 
> standard with a list of "forbidden" parameters, so that other projects that 
> might accidentally use the same parameter names do not suffer.
>
> This update may cause mega-corporations to generate parameter names. 
> Visually, they will look like a random set of characters, inside they will 
> contain an encrypted name with a random initialization vector and a 
> checksum to distinguish between friend or enemy.
>
> ?vdj1967enxb52p99kiGFskdj785hFyu=kjQGj90sac17E6AJjk8afzmScA
>
> Further you will forbid to use "unreadable" names of parameters? Then they 
> will begin to make up random names from readable words. Will you start 
> limiting the length of parameter names next? Then you will destroy the 
> entire Internet.
>
> среда, 13 октября 2021 г. в 19:59:53 UTC+3, [email protected]: 
>
>> Hi folks,
>>
>> On Tue, Oct 12, 2021 at 1:37 PM Chris H-C <[email protected]> wrote:
>>
>>> To dveditz's points:
>>>
>>> > Are you tracking users, or campaigns?
>>>
>>> Me personally? Neither : ) But to my knowledge from helping with the 
>>> implementation of attribution collection in Firefox Telemetry the answer is 
>>> campaigns (and other things on that order)[1]. Basically `utm_` params.
>>>
>>> > do you track cross-site?
>>>
>>> Again, not me personally : ) But we may have partners driving us 
>>> traffic, and we may host the installer on non-first-party eTLD+1s for, I 
>>> dunno, CDN reasons? (not sure we do for Desktop, but we don't host our own 
>>> packages for Android and iOS as you'd imagine. App Stores. Ick.).
>>>
>>> > Are you likely to use fbclid= or other known tracker to do so?
>>>
>>> I doubt that very much. To my knowledge we're interested in 
>>> campaign/experiment/branch-level efficacy measurement, not user-level 
>>> tracking.
>>>
>>
>> Many thanks to :chutten for raising this, 'cuz otherwise it would have 
>> been me.  The attribution that we're talking about is not user-level, but 
>> we do use "well known" identifiers: from 
>> https://searchfox.org/mozilla-central/rev/b822a27de3947d3f4898defac6164e52caf1451b/browser/components/attribution/AttributionCode.jsm#45-54,
>>  
>> I see:
>>
>> "source",
>> "medium",
>> "campaign",
>> "content",
>> "experiment",
>> "variation",
>> "ua",
>> "dltoken",
>>
>> These are terms that Firefox's client-side attribution code recognizes  
>> It's possible that mozilla.org (bedrock) uses and/or recognizes more.  I 
>> believe that the first several of those are "industry standard" terms and 
>> while not user-level generally (or at this time), might be blocked were we 
>> and others to block more aggressively.  The "dltoken" is a per-download 
>> identifier.
>>
>> Nick
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/498eca6e-f8f6-4a37-9b6e-e6b58e67c56fn%40mozilla.org.

Reply via email to