I'm pretty busy and don't have a lot of time, and I can't easily explain this for good reasons, however:
It is likely that unsophisticated attempts at burner accounts (if you don't know what a residential IP is, or ever heard of browser fingerprinting, you are unsophisticated) are currently detectable by the CEA online team. There was a comment about using a pseudonymous email—this is absolutely not enough.
My guess is that this applies to 90% of burner usage, weighted by user.
That is, there is a script or turnkey way that a dev can spend less than 2 days to systematically identify 90% of burner accounts used and the identities of 90% of people using them, provided they have a CEA account (which they will have, because of EAG).
My current understanding of the online team and CEA culture is that there is <10% chance this will be used against anyone in a way a normal (non-EA person) would find disagreeable (modulo internal leakage, who has access to production data, etc.).
However, note that because this data is stored indefinitely (CEA has not declared a retention policy) It is possible in future “regimes” of CEA this could be used.
The information in this comment should be incorporated by those using burner accounts or the establishment of a "burner culture".
I would probably accept the interpretation that some existence of these capabilities is causally the result of me. That is, it is not the fault of CEA, the CEA online team, Ben West or the dev who implemented this, but mine.
Aside: I also recommend not immediately disabling my account when I comment once, as this creates weird consequent dynamics that are difficult to control.
I'm pretty busy and don't have a lot of time, and I can't easily explain this for good reasons, however:
It is likely that unsophisticated attempts at burner accounts (if you don't know what a residential IP is, or ever heard of browser fingerprinting, you are unsophisticated) are currently detectable by the CEA online team. There was a comment about using a pseudonymous email—this is absolutely not enough.
My guess is that this applies to 90% of burner usage, weighted by user.
That is, there is a script or turnkey way that a dev can spend less than 2 days to systematically identify 90% of burner accounts used and the identities of 90% of people using them, provided they have a CEA account (which they will have, because of EAG).
My current understanding of the online team and CEA culture is that there is <10% chance this will be used against anyone in a way a normal (non-EA person) would find disagreeable (modulo internal leakage, who has access to production data, etc.).
However, note that because this data is stored indefinitely (CEA has not declared a retention policy) It is possible in future “regimes” of CEA this could be used.
The information in this comment should be incorporated by those using burner accounts or the establishment of a "burner culture".
I would probably accept the interpretation that some existence of these capabilities is causally the result of me. That is, it is not the fault of CEA, the CEA online team, Ben West or the dev who implemented this, but mine.
Aside: I also recommend not immediately disabling my account when I comment once, as this creates weird consequent dynamics that are difficult to control.