Sun, Sep 16
Found this issue, too, I'll add these messages in a patch and upload it in a second :)
Sat, Sep 1
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!
Jul 17 2018
Jul 15 2018
Jul 12 2018
Jul 7 2018
Jul 2 2018
Jun 29 2018
Actually I seem to be incorrect. The extension does not require the people permission at all, as the displayName, where I thought it is used, comes from another set of data (where a server API key is used, instead of an actual permission of the user to access his data). So, let's reduce the scope of permissions here :D