On 10/12/06, Eugene Zelenko <eugene.zelenko(a)gmail.com> wrote:
>
> It's great news! Should we bug developers to install extension on
> Commons as soon as possible?
I don't see why not -- as long as we can control how the info is
imported (eg, to use Template:Information, and I guess some
flickrreview thing). I just tried it out and it is frankly far easier
than searching flickr!
Undoubtedly people will not realise it is installed and continue to
manually upload Flickr images, but for people who are aware of this,
it will be a huge boon. :)
cheers,
Brianna
user:pfctdayelise
I notice that recently there is a new "undo" link appearing when
viewing old diffs. Strangely, it only appears for diffs other than the
latest one. It looks like what it does is let you remove text that was
introduced in an old revision but subsequently "consolidated" by a
later edit. I have two questions about it:
1) Is there any documentation on it, and if so, could that be linked
to from the text that says "The edit was successfully undone. Please
click save to apply this change." (and also from the error message you
get when it can't undo due to intervening edits)
2) What's the rationale behind not making it available for the latest
edit? Presumably this is a political sensitivity about not giving
rollback to everyone, but it's a bit odd to effectively give rollback
for old edits, rather than for all edits, which would be much more
useful. Could we perhaps trial "rollback for everyone"?
Steve
An automated run of parserTests.php showed the following failures:
Reading tests from "/home/brion/src/wiki/phase3/maintenance/parserTests.txt"...
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Running test TODO: Images with the "|" character in the comment... FAILED!
Running test TODO: Parents of subpages, two levels up, without trailing slash or name.... FAILED!
Running test TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.... FAILED!
Running test TODO: Don't fall for the self-closing div... FAILED!
Running test TODO: Always escape literal '>' in output, not just after '<'... FAILED!
Reading tests from "/home/brion/src/wiki/phase3/extensions/Cite/citeParserTests.txt"...
10 previously failing test(s) now PASSING! :)
* Simple <ref>, no <references/>
* Simple <ref>, with <references/>
* <ref> with a simple template
* <ref> with a <nowiki>
* <!--comment--> in a <ref> (bug 5384)
* <references> after <gallery> (bug 6164)
* {{REVISIONID}} on page with <ref> (bug 6299)
* Blank ref followed by ref with content
* Regression: non-blank ref "0" followed by ref with content
* Regression sanity check: non-blank ref "1" followed by ref with content
Passed 451 of 471 tests (95.75%)... FAILED!
I have implemented a "redirect to section" feature. It requires
JavaScript, with the old behaviour maintained for non-JS browsers.
Use it wisely -- remember that a link from one page to the middle of
another will typically be unexpected and surprising behaviour for the
reader, especially when the source link has no # in it. This feature is
regularly requested, and so I implemented it on that basis. I'm sure there
are good applications, but some amount of common sense at the editorial
level is required.
-- Tim Starling
An automated run of parserTests.php showed the following failures:
Reading tests from "/home/brion/src/wiki/phase3/maintenance/parserTests.txt"...
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Running test TODO: Images with the "|" character in the comment... FAILED!
Running test TODO: Parents of subpages, two levels up, without trailing slash or name.... FAILED!
Running test TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.... FAILED!
Running test TODO: Don't fall for the self-closing div... FAILED!
Running test TODO: Always escape literal '>' in output, not just after '<'... FAILED!
Reading tests from "/home/brion/src/wiki/phase3/extensions/Cite/citeParserTests.txt"...
Running test Simple <ref>, no <references/>... FAILED!
Running test Simple <ref>, with <references/>... FAILED!
Running test <ref> with a simple template... FAILED!
Running test <ref> with a <nowiki>... FAILED!
Running test <!--comment--> in a <ref> (bug 5384)... FAILED!
Running test <references> after <gallery> (bug 6164)... FAILED!
Running test {{REVISIONID}} on page with <ref> (bug 6299)... FAILED!
Running test Blank ref followed by ref with content... FAILED!
Running test Regression: non-blank ref "0" followed by ref with content... FAILED!
Running test Regression sanity check: non-blank ref "1" followed by ref with content... FAILED!
Passed 441 of 471 tests (93.63%)... FAILED!
An automated run of parserTests.php showed the following failures:
Reading tests from "/home/brion/src/wiki/phase3/maintenance/parserTests.txt"...
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Running test TODO: Images with the "|" character in the comment... FAILED!
Running test TODO: Parents of subpages, two levels up, without trailing slash or name.... FAILED!
Running test TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.... FAILED!
Running test TODO: Don't fall for the self-closing div... FAILED!
Running test TODO: Always escape literal '>' in output, not just after '<'... FAILED!
Reading tests from "/home/brion/src/wiki/phase3/extensions/Cite/citeParserTests.txt"...
Running test Simple <ref>, no <references/>... FAILED!
Running test Simple <ref>, with <references/>... FAILED!
Running test <ref> with a simple template... FAILED!
Running test <ref> with a <nowiki>... FAILED!
Running test <!--comment--> in a <ref> (bug 5384)... FAILED!
Running test <references> after <gallery> (bug 6164)... FAILED!
Running test {{REVISIONID}} on page with <ref> (bug 6299)... FAILED!
Running test Blank ref followed by ref with content... FAILED!
Running test Regression: non-blank ref "0" followed by ref with content... FAILED!
Running test Regression sanity check: non-blank ref "1" followed by ref with content... FAILED!
10 previously passing test(s) now FAILING! :(
* Simple <ref>, no <references/>
* Simple <ref>, with <references/>
* <ref> with a simple template
* <ref> with a <nowiki>
* <!--comment--> in a <ref> (bug 5384)
* <references> after <gallery> (bug 6164)
* {{REVISIONID}} on page with <ref> (bug 6299)
* Blank ref followed by ref with content
* Regression: non-blank ref "0" followed by ref with content
* Regression sanity check: non-blank ref "1" followed by ref with content
Passed 441 of 471 tests (93.63%)... FAILED!
Dear Travis,
Yep.
Yours sincerely,
Jesse Martin
(Meta admin 'Pathoschild')
> From: "Travis Derouin" <travis(a)wikihow.com>
> Great,
>
> What are you using to block these proxies? Just the standard blocking
> functionality in Mediawiki?
>
> Thanks,
> Travis
>
>
On 12/7/06, John Doe <phoenixoverride(a)gmail.com> wrote:
>
> 85.234.128.0/20
> 85.234.144.54/31
> should handle the issue. Betacommand
>
> On 12/7/06, Luna <lunasantin(a)gmail.com> wrote:
> >
> > Oooh, good. Didn't know you subscribed to this list. :) Essjay's
> > original block was on 85.234.128.0/19 , the address we seem to be
> > friends with is 85.234.144.53
> >
> > On 12/7/06, John Doe < phoenixoverride(a)gmail.com> wrote:
> > >
> > > I can do the blocks of a range if you tell me what should NOT be
> > > blocked I can nail the rangeblock just right. Betacommand
> > >
> >
So doing the CIDR blocks is the only way?
To be pedantic and fully complete, we'd want:
85.234.128.0/20
85.234.144.0/27
85.234.144.32/28
85.234.144.48/30
85.234.144.52/32
== gap for unblockee at 85.234.144.53/32
85.234.144.54/31
85.234.144.56/29
85.234.144.64/26
85.234.144.128/25
85.234.145.0/24
85.234.146.0/23
85.234.148.0/22
85.234.152.0/21
Unless I missed a bit or bits somewhere doing this in head and on fingers.
This seems like we should automate something; either a netblock minus
exceptions interface tool to autogen the CIDR blocks from a top range plus
some exceptions, or adding in an explicit "unblock this IP" override and
have any CIDR block range lookup check the unblock override before returning
blocked or not.
Nobody does Cisco ACLs or BGP routing this way the hard way if they can help
it... and our admins by and large aren't network geeks.
--
-george william herbert
george.herbert(a)gmail.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In the previous discussion (about Special:Desysop), it was proposed to
merge the user rights pages (Special:Userrights, Special:Makesysop,
Special:Makebot, Special:GiveRollback, and now also Special:Desysop)
into the page Special:Userrights, using configuration settings. It seems
to be a good time to propose it:
I've merged these special pages to Special:Userrights using
configuration settings in
http://svn.wikimedia.org/viewvc/mediawiki/branches/rotem/userrights ,
which is an improved user rights page.
This proposed system adds the following features to Special:Userrights:
* Flexible configuration settings for a limited interface – for example,
you can allow bureaucrats to grant only these permissions and revoke
only those permissions, and allow the stewards to do everything.
* Checkboxes instead of lists, mainly because it's possible to disable
them separately while it's not possible in lists.
* Changing the permissions of remote users for stewards, controllable by
a permission ("userrights_remote"), like in the stewards interface of
Special:Makesysop.
* Log comment, to explain the change, like in Makebot.
You can either download and test it directly, or watch the following images:
http://img150.imageshack.us/my.php?image=mediawikinewuserrightsbureaucratsl…
The limited interface for bureaucrats, like it can be set in Wikimedia
sites.
http://img84.imageshack.us/my.php?image=mediawikinewuserrightsstewardsgg7.p…
The full interface for stewards, like it can be set in Wikimedia sites,
editing a remote user.
This change should deprecate Makesysop, Makebot, GiveRollback and
Desysop and make them implementable by using only configuration
settings. However, these extensions may be kept for old versions, and
for sites which were not updated. (There seems to be a compatibility
issue with Special:Makesysop because one of its core functions
(HTMLSelectGroups) was removed, but it can be defined in
SpecialMakesysop.php or SpecialMakesysop_body.php as a class function.)
Additional technical information may be found in
http://www.mediawiki.org/wiki/User:Rotemliss/User_rights_suggestion#How_to_…
. You can also read the other parts of the page, but it's a bit old and
not updated in some parts. You can also ask here about anything unclear.
What do you think about this implementation? Which changes should be
done? Do you think some features should be added, or dropped?
Thank you very much for the feedback.
- --
#define Name RotemLiss
#define Mail mail-AT-rotemliss-DOT-com
#define Site www.rotemliss.com
#define KeyFingerPrint 4AFD 8579 A449 4267 BED9 38E5 6EF8 5B1F EBDE 7AC0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE4b2abvhbH+veesARApwWAKCq1TGg1zVjTIjwDiH3f7AVe0sbGQCfV7hJ
NCU2Uwu1nrCv9ReNhVtaIxw=
=CBQh
-----END PGP SIGNATURE-----
