On 2/20/11 4:52 PM, Platonides wrote:
You may have noticed that I included a horrible page to log you in
instead of the content (the lightweight page). That can be replaced
with a javascript login, if it is clear how to do it.
That's a terrible idea. I routinely edit (and do everything else)
Hoi,
The benefit of JavaScript is ease of use. Most people are not willing to do
without the modern comforts.
Thanks,
GerardM
On 3 March 2011 20:37, William Allen Simpson
william.allen.simp...@gmail.com wrote:
On 2/20/11 4:52 PM, Platonides wrote:
You may have noticed that I included
On Thu, Mar 3, 2011 at 2:37 PM, William Allen Simpson
william.allen.simp...@gmail.com wrote:
That's a terrible idea. I routinely edit (and do everything else)
without javascript running. There's really no need for it.
With JavaScript, we could skip the interstitial page when you log in
and
Platonides wrote:
CORS does seem to be the way to go. I have drafted a new proposal below
which attempts to fix several bug in our way of doing central login.
Two questions and a comment about this.
First, would this impede the ability to switch to an AJAX login interface in
the future?
On 02/20/2011 09:53 PM, MZMcBride wrote:
Platonides wrote:
CORS does seem to be the way to go. I have drafted a new proposal below
which attempts to fix several bug in our way of doing central login.
Two questions and a comment about this.
First, would this impede the ability to switch to
MZMcBride wrote:
Platonides wrote:
CORS does seem to be the way to go. I have drafted a new proposal below
which attempts to fix several bug in our way of doing central login.
Two questions and a comment about this.
First, would this impede the ability to switch to an AJAX login interface
On 02/20/2011 11:52 PM, Platonides wrote:
MZMcBride wrote:
Second, would this impede the ability to remove the you've been logged in
screen? Aryeh mentioned an idea that would allow MediaWiki to remove this
horrible workflow interrupter.[2]
You may have noticed that I included a horrible
Platonides platoni...@gmail.com writes:
CORS does seem to be the way to go. I have drafted a new proposal below
which attempts to fix several bug in our way of doing central login.
Would this allow CentralAuth to work with IE8 in the “medium” privacy
mode? I haven't tried it, but
On Sun, Feb 20, 2011 at 1:20 AM, Platonides platoni...@gmail.com wrote:
Create a multilingual wiki for handling logins, available as
https://login.wikimedia.org/
https://login.wikipedia.org/ https://login.wikiversity.org/ etc.
I would recommend users.*, that way in the future when we have
2011/2/17 Platonides platoni...@gmail.com:
Finally, I completely concur with Brion that the additional Log in
globally checkbox should be removed, and a better solution be sought,
per 1). It's not something that users should need to think about.
I'm happy with removing it *after* we get the
2011/2/17 Platonides platoni...@gmail.com:
The reason I set to add it was that loggin in on not-too-used sites
actually short lived my long sessions.
Bug 24471 [1] explains a similar problem although you have to read [2]
to understand it.
My take on all this is that it would be useful to
Erik Moeller wrote:
The experience that Sage describes in bug 24471 of not being
consistently logged in arguably shouldn't occur in the first place per
1). Can we log the user into _all_ public Wikimedia wikis without
incurring an unacceptable performance penalty? If so, how?
We can do it if
On Thu, Feb 17, 2011 at 3:27 PM, Platonides platoni...@gmail.com wrote:
The reason I set to add it was that loggin in on not-too-used sites
actually short lived my long sessions.
Bug 24471 [1] explains a similar problem although you have to read [2]
to understand it.
I agree it's some UI
13 matches
Mail list logo
