Help talk:Unified login
Latest comment: 1 year ago by Al12si in topic Wikidata: Not working + bad interaction design
 | This page is to discuss unified logins which were introduced in the early 2010s with the amalgamation of the previous configuration of separate accounts on separate wikis. For current day issues with a login to Wikimedia, please log a bug report in phabricator:. |
- External discussion
- [Wikitech-l] Single user login status --Brion Vibber
- [Wikitech-l] Primary account for single user login --Ans 11:00, 1 November 2007 (UTC)
logging into all accounts simultaneously?
" Special:UserLogin now logs the user in to every unified wiki simultaneously " doesn't work for me. I login at meta.wikimedia.org, then try en.wikipedia.org, but have to login again. And it doesn't seem to be a cookie problem because I stay logged in in meta.wikimedia.org. --Utonsal (talk) 23:34, 28 October 2022 (UTC)
- @Utonsal: Each wikisister will set its own set of cookies, so meta is in wikisister "wikimedia.org" and enWP is on the "wikipedia.org", so most likely is a cookie issue if failing. Try to flick your browser to request permission, or check your settings and search for the cookie. — billinghurst sDrewth 09:16, 29 October 2022 (UTC)
Wikidata: Not working + bad interaction design
Central login isn’t working for Wikidata, but to make things worse, it doesn’t warn you until after you have made your first edit, so unless you remember Wikidata requires a separate login, you are almost guaranteed to leak your IP by trying to connect a Wikipedia page.
Which is like even worse than not having central login, because if you don’t have central login you will remember to log in when you switch wikis.
Can this be either fixed (if technically possible), or at least have the warning appear before you edit (i.e., have the warning appear as soon as you hit Edit, as opposed to after you hit Publish). Thanks. Al12si (talk) 20:15, 20 November 2022 (UTC)
- @Al12si: Wikidata is working fine for central login, please check that you have your cookies suitable enabled as that is usually the issue that we see. Do some good cache purging. With regard to a warning for IP editing, that already exists for the wikis in a traditional edit page (tested right now), so if you think that needs to be exist for WD's style of editing, that will need to be recommended to them specifically. Best to ask at d:Wikidata:Project chat. — billinghurst sDrewth 22:27, 21 November 2022 (UTC)
- @Billinghurst My cookies are fine (and the fact that only Wikidata is not working shows that cookies isn’t my problem). I also perpetually run in private mode so caches aren’t the problem — if anything this always happens after a browser restart which means a cache clear will actually cause the problem.
- If anything it’d be the auto-block features that modern browsers use that’s blocking the cookies. This could be something that the designers of central login didn’t envision when the feature was designed a decade ago when privacy browsers didn’t exist. A solution would be to add instructions to the login screen to tell users what domains to whitelist. — Al12si (talk) 22:33, 21 November 2022 (UTC)
- @Al12si: That it doesn't work for you is not an indication that it doesn't work; if it is working for others, then it is working, and there is something about a configuration, you may well have rejected cookies for WD, how can I tell? Wikidata is a different interface methodology, and not a traditional WMF wiki textbox, so you will need to talk to them about how they manage IP edits differently and for your proposed intervention. For technical design issues, where you have considerations about how you believe that some features of modern browsers may be interacting and you have identified what you consider a bug, then please create a bug report at phabricator:, a general statement here on this talk page of "It is not working for me, fix it" isn't going to resolve the issue. — billinghurst sDrewth 22:45, 21 November 2022 (UTC)
- PS: @Billinghurst: I suspect the problem with meta, mentioned in the question right above mine, is the exact same issue. Modern browsers automatically block cross-site cookies by default, that’s probably why not all accounts are logged in. This problem can only get worse as this kind of browser becomes more and more mainstream. Al12si (talk) 22:49, 21 November 2022 (UTC)
- PPS: @Billinghurst Assuming our two issues are the same, that’s two people complaining about the same problem in less than a month. Most people wouldn’t even talk about it (if only for the fact that it’s extremely hard to even find this talk page); I’d say it’s not prudent to claim it’s “working for most people”. Al12si (talk) 22:54, 21 November 2022 (UTC)
- @Al12si: there are so many users of WD and the sister WMFs, and essentially zero complaints on a daily basis, so I think that it is reasonable to say that it is working. This is not to say that there are not people having issues and this may continue to occur, however, these are bugs to be reported that contain all the information of the browser used, and the settings that users have in place. All of those issues need to be recorded as bugs in phabricator. — billinghurst sDrewth 04:50, 22 November 2022 (UTC)
- @Billinghurst As I mentioned, this talk page is extremely difficult to find. Took me literally four months to realize this talk page even exists. A lack of complaints does not mean a lack of problems when the channel for complaints is not perceivable.
- The Phabricator ticket you ask for will eventually arrive — later after I test it on Opera GX and other modern browsers. But you cannot dismiss the problem if default browser behaviour is going to guarantee people can’t log on to every wiki.
- I will unsubscribe from this thread since this isn’t going anywhere. I’ll suggest to my home wiki’s admins to remove the link to this talk page since this talk page isn’t helping people. — Al12si (talk) 06:15, 22 November 2022 (UTC)
- @Al12si: there are so many users of WD and the sister WMFs, and essentially zero complaints on a daily basis, so I think that it is reasonable to say that it is working. This is not to say that there are not people having issues and this may continue to occur, however, these are bugs to be reported that contain all the information of the browser used, and the settings that users have in place. All of those issues need to be recorded as bugs in phabricator. — billinghurst sDrewth 04:50, 22 November 2022 (UTC)
- PPS: @Billinghurst Assuming our two issues are the same, that’s two people complaining about the same problem in less than a month. Most people wouldn’t even talk about it (if only for the fact that it’s extremely hard to even find this talk page); I’d say it’s not prudent to claim it’s “working for most people”. Al12si (talk) 22:54, 21 November 2022 (UTC)