- Mentioned In
- T121930: Cross-wiki mark as read doesn't work
T173595: Download button for audio and video files on Commons
T172560: "Loss of session data" on Beta Cluster
T131520: Tell Privacy Badger which pages belong to Wikimedia so it doesn't block cross-wiki requests
T129764: New Error Message for "Error Access to the remote domain was denied." (echo-api-failure-cross-wiki) message and use errorObj?
Thanks for noticing that @Tgr.
I just installed Privacy Badger, and it's not blocking anything yet-- are you seeing it block either of:
- The call to Special:CentralAutoLogin/checkLoggedIn (whenever you hit a wiki unauthenticated)
- The top-level redirect setting the cookie for loginwiki
If so, then we've got problems. Otherwise users with PB will get the same experience as anyone who has 3rd-party cookies disabled.
You need to log in and out a few times on different wikis. The extension keeps track of seeing the same cookie or script when the user visits different domains, and starts blocking after a certain limit.
After using it a while, autologin across second-level domains is sometimes broken but manual login always works. (Is that what you meant by the 3rd-party-cookies-disabled experience?)
login.wikimedia.org sometimes appears on the yellow setting (cookies blocked, scripts not blocked), most of the time it's not listed at all.
I spoke to Cooper Quintin (the author of Privacy Badger) today, and as a result of our conversation I filed a bug requesting the addition of a list of domain groups. We could then ask for *.wikipedia.org, *.wiktionary.org, *.wikisource.org, etc. to all be in the same group, so that Privacy Badger won't block requests between these domains by default.