Feb 16 2016
So how exactly does your link answer my question about the source of your claim that <p> is deprecated on Wikipedia?
Feb 6 2016
Jan 21 2016
Jan 18 2016
And not to mention I personally never use <p> like that, so I don't get why do you direct your ill-thought advises at me.
Do you really think the only use of the <p> tag is centering?????? What the hell is this your 'fix' on fixing something that ain't broken? What is your problem with the way the <p> is used? Huh?
It doesn't suffice. For one, it doesn't seem to satisfy the requirement of being able recover the exact code.
Jan 17 2016
Jan 15 2016
Jan 7 2016
Our ruwiki admin OneLittleMouse encountered a similar issue with unblocking 184.108.40.206/16 and 220.127.116.11/18.
Mar 10 2015
The question is, why do you feel you have the right to decide instead of me whether to use it. I explicitly opted out, and you should comply with that. When I first heard about HTTPS rolling out on Wikimedia projects, I myself raises concerns about the possibility it will negatively impact my access and capability to participate, and several users supported me. We were told we will be able to opt out, and indeed for a while it had been working great, albeit sometimes this bug occurs, and now you say you lied to us or what? If some dumbass admin on those projects decided he is the smartest being in the entire world, why do I have to suffer?
Mar 9 2015
Even better title would be "Occasionally, projects enforce HTTPS regardless of user settings". It occurs from time to time on all projects I participate in, just that Russian Wiktionary was the one I had trouble when reporting this.
Okay, tell me, do you still consider this is not a bug and why the title is still misleading. And, for the record, I honestly don't know what to expect from this ticket anymore. Maybe it will get fixed. Most likely, as it stands, nothing will be done. But there are also chances that HTTP will be blocked completely on some grounds I have no clue of, and I 'd rather not.
Mar 8 2015
Okay, I'll calm myself down. Still, I believe the root of the misunderstandings is not in me being unclear, but reading my comments only partially.
This makes no sense. I have never met such incompetent developer. I filed a bug about HTTPS occasionally being forced even if you opted out. You reproduced the bug on your end somehow but instead of fixing it you declared it intentional even if it's against the official Wikimedia policy regarding HTTPS and the fact that you can still access the wikis via HTTP when the bug doesn't occur, as a developer I assume you must know the policy well. You now remind me of Valve fixing a bug in their game by officially calling it intentional after 2 years of silence on that matter.
No, it doesn't, because you are just wrong. I don't know what business you have to do working on Wikimedia projects, but it seems you know too little and have poor reading comprehension. Because you ignored half of my statements and thus missed the fact you can freely opt out of forced HTTPS as a registered user on Russian Wikimedia projects.
Mar 7 2015
Now the same thing is going on on Russain Wikipedia, except this time I have no cookies to delete.
Mar 6 2015
What the hell is going on really? What does it mean "it has no effect"??? You can opt out of secure connection in Russian wikiprojects as a registered user. That's what my current preference across all Wikimedia projects is.
OMG. I've said multiple times: I WAS DAMN LOGGED IN.
Mar 5 2015
- Opened a wiki page via insecure link. It opened in a secure connection (expected: still insecure connection).
- Tried to change the URL to get back to insecure. Got redirected to secure (expected: insecure connection).
- At this point I discovered my preferences are set to "Always keep on secure connection" or whatever is the exact wording. Turned it off.
- Repeated #2. Same results.
- Logged out. Deleted all ForceHTTPS cookies.
- Logged in. Checked no such cookies are present.
- Repeated #4-6 several times. No luck.
Ugh, what? It forces while logged in. Change the title back.
Mar 3 2015
Hello. I went there to read. I hadn't been there I think since the time of introduction of forced HTTPS for anonymous editors because on all wikis I had visited prior I already changed the option to not force it on me. I was logged in already by the time the bug occured via Central Auth. So, after I went there (via insecure link, BTW), I noticed I was on secured connection. I tried to switch back to HTTP, then realized I might have never opted out, so I went to preferences and changed that, after I did the usual deletion of all ForceHTTPS cookies and logging in-out. I expected to be able to read the wiki using insecure connection after that. Instead the server still forces me to use secure one.