Since r61917 (3 February), running the api tests have been creating a
user called 'Useruser' which initially had a random password. r72475
(6 September) screwed up by using a hardcoded pasword.
Since it wasn't too bad for wikis allowing account creation, r74118
(1 October) made that user a sysop. F
On 26/10/10 08:45, George Herbert wrote:
> The current WMF situation is becoming "quaint" - pros use
> secure.wikimedia.org, amateurs don't realize what they're exposing.
I released a small patch today that let a user login with HTTPS. It is
in trunk as r75585 :
http://www.mediawiki.org/wiki/Spe
Conrad Irwin gmail.com> writes:
> There is no real massive load caused by https at runtime. There is however
> a significant chink of developer and sysadmin time needed to implement this
> and make it work.
Secure login in itself shouldn't require reconfiguration of the SSL
architecture, though
On Tue, Oct 26, 2010 at 10:00 AM, Chad wrote:
> This has been a long development process for almost 2 years
> now, and I'd like to thank Max, Mark H., Jure, Jeroen, Roan
> and Siebrand for their invaluable help in working on this. And
> especially thanks to Tim for starting the project and providi
Aryeh Gregor writes:
>
> To clarify, the subject needs to 1) be reasonably doable in a short
> timeframe, 2) not build on top of something that's already too
> optimized
Integrating a subset of RTMP (e.g. the
http://code.google.com/p/rtmplite subset) into the chunk-based file
upload API -- htt
Ryan Lane wrote:
> On Tue, Oct 26, 2010 at 4:39 PM, a b wrote:
>> After the recent dicussions open open-ness and clarity with requests by
>> serveral people what is contained within the RT after several people have
>> asked and given answers like "it's staff stuff".
>>
>> So what is stored in it
