Thu, Mar 21
Sat, Mar 16
I've found the same issue while trying to migrate jobs from the trusty grid to the new one (or better deleting the tool at all) :/
Feb 9 2019
Jan 31 2019
Yes, I'm available.
Jan 27 2019
As far as I know, this is already reflected in the current code base, as it does not require the profile permission anymore, and does not request it either, since:
I think, because:
- I get a lot of requests to autolink accounts, mostly from private wikis, which want to use GoogleLogin as it's only primary provider
- the implementation of an "create account after link provider authentication" UI (T138678: AuthManager should support to create a new account for a Link PrimaryAuthenticationProvider) may take some more time to get implemented
The documentation is correct from my point of view. If you check the keep me logged in checkbox, you will be kept login even if you use GoogleLogin to login. However, if you remove all authentication methods (which bypasses the Login form completely for convenience of the users) you can't check this checkbox.
Jan 8 2019
I wasn't very active this year, either. However, if no-one else has time or is interested, I'd be happy to attend, nevertheless.
Jan 2 2019
Nov 13 2018
Nov 11 2018
Nov 4 2018
Oct 28 2018
Oct 25 2018
There's a design prototype on wiki: https://m.wikidata.org/wiki/Wikidata:Client_editing_prototype
Oct 23 2018
Imported as https://codein.withgoogle.com/dashboard/tasks/6289154326396928/ for Google-Code-In
Oct 1 2018
Sep 27 2018
Sep 16 2018
Found this issue, too, I'll add these messages in a patch and upload it in a second :)
Sep 1 2018
Aug 11 2018
Coming from ULS, not CookieWarning.
Aug 6 2018
Already working on it...
Aug 2 2018
Jul 26 2018
Jul 23 2018
Jul 22 2018
Jul 21 2018
Jul 20 2018
Btw.: It seems you don't have the latest master version, latest master does not contain the CookieWarningDecisions class anymore, but instead the Decisions class.
First of all: I kind of thought, that you can already set an e-mail address only to one user, so that there's a one-to-one-relation from one user to one e-mail-address and vice versa. However, this turns out to be a wrong assumption. I'll cover the obligations resulting from that in the following answers to the comments :)
Jul 19 2018
Thanks for the response :) Great to hear, that the problem is fixed :)
@Tgr and @Anomie I would like to hear your opinion about (generally spoken) matching a user based on their e-mail address instead of their user account ID. Is there something which comes to your mind why this could be a bad thing? :)
Scope profile removed, *yay* :)
Hmm, is whitelisting the IP really the correct way of doing that? How does the electron service get's the content of the page? If it is displaying it like a normal user, it can just put the cookiewarning_dismissed cookie into the request and CookieWarning will not render the warning header at all. Isn't that a reasonable solution? :)
Thanks for filing this bug report and please excuse the very late response here :( Unfortunately it seems that there're some information missing. I tested it locally with MediaWiki 1.30 and the latest CookieWarning and it works pretty well. Does this problem still exist for you?
Jul 18 2018
I already worked with him and it was like a charm, nothing that would prevent him getting +2 rights from my point of view. +1!