TYPO3 currently has a couple of implementations which in a default setup will dispatch external requests that may be used for (undeclared) information collection such as usage tracking. I take privacy very seriously and am naturally opposed to software making any external requests unless the user opts in, and I am particularly against such requests if they are enabled by default and have no opt-out setting.
I therefore would like to raise the discussion about whether or not to remove such mandatory external requests from all current TYPO3 versions and make it an official rule to never implement such requests unless they are opt-in and disabled by default, and to carefully consider whether the request is important enough to merit its existence.
- TYPO3 currently exposes installations without any way to opt-out.
- At the time of writing this, such external requests are even causing performance issues (see https://forge.typo3.org/issues/91507).
- By forcing external requests to happen we risk lowering the trust of users that their usage of TYPO3 is not being unwillingly tracked.
- GDPR concerns may apply since presumably, these remote requests are at the very least logged on the remote server along with an IP-address.
- (A) Completely disallow the implementation of external requests from TYPO3 unless they are implemented by a third party developer (making them very clearly opt-in).
- (B) Implement an opt-in mechanism for such requests which allows them to be disabled by default and only be dispatched if a user knowlingly opts in.
- Institute a rule for future development that such requests should either be disallowed entirely (A) or always be disabled by default and only enabled on explicit opt-in (B).
Topic Initiator: Claus Due