From time to time WMF run tests or additional services that may pose a privacy problem. Usually these are internal services, they try to avoid using third party services. Compared to other large web services this happen rather seldom, so I'm not sure whether it is necessary to prepare for blocking such services.
Blocking of such services could be done by maintaining a whitelist of valid IP-addresses and/or DNS names. That would make specific services fail if they load from individual IP-addresses. It could be more difficult to block services that load through the common loader, and report through cookies.
I just want to post this as a possible privacy problem. There are no serious threat for the moment that I'm aware of, except the analytics tool. That is internal, and not made for user tracking. It is also a check whether the user is logged in, which isn't really useful for this app and can be dismissed.
From time to time WMF run tests or additional services that may pose a privacy problem. Usually these are internal services, they try to avoid using third party services. Compared to other large web services this happen rather seldom, so I'm not sure whether it is necessary to prepare for blocking such services.
Blocking of such services could be done by maintaining a whitelist of valid IP-addresses and/or DNS names. That would make specific services fail if they load from individual IP-addresses. It could be more difficult to block services that load through the common loader, and report through cookies.
I just want to post this as a possible privacy problem. There are no serious threat for the moment that I'm aware of, except the analytics tool. That is internal, and not made for user tracking. It is also a check whether the user is logged in, which isn't really useful for this app and can be dismissed.