-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I've set up an NNTP gateway for Wikimedia mailing lists. The
"wikimedia.*" hierarchy is available via news.tcx.org.uk. More
information: <http://news.tcx.org.uk/wikimedia.html>.
Unlike GMane, this gateway does not rename lists (all lists are
wikimedia.<list name>), and does not munge email addresses inside posts,
which breaks PGP signatures.
However, posting via NNTP is not currently possible. (I expect to fix
this in a few days.)
Only a few lists are available right now, but if people find it useful,
I will add the rest of them (at least those with public archives).
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEARECAAYFAk1HLeEACgkQIXd7fCuc5vJFWwCeJvcsA+RSvgF8IXkRxxlk1q2r
t0oAn1ei8J9VqHfb/EUy7h1o8VWehE4r
=omjK
-----END PGP SIGNATURE-----
Here's an interesting question. Is there any way for
Special:WhatLinksHere to distinguish between links from a template
rather than links from the actual article text? I presume at present
it all just goes into a links table generated on save, and can't be
distinguished ...
- d.
---------- Forwarded message ----------
From: Carcharoth <carcharothwp(a)googlemail.com>
Date: 6 February 2011 23:56
Subject: Re: [WikiEN-l] Most wanted
To: English Wikipedia <wikien-l(a)lists.wikimedia.org>
On Sun, Feb 6, 2011 at 10:19 PM, Magnus Manske
<magnusmanske(a)googlemail.com> wrote:
> Many of these links are due to templates, which I can do little about.
Can *anyone*, even in principle, do something about that? It really
bugs me that the "what links here" function doesn't distinguish
between links arising from templates (often not directly relevant) and
links directly from the article wiki-text. If the answer is something
to do with parsers, please do explain!
Carcharoth
_______________________________________________
WikiEN-l mailing list
WikiEN-l(a)lists.wikimedia.org
To unsubscribe from this mailing list, visit:
https://lists.wikimedia.org/mailman/listinfo/wikien-l
Dear all,
In Chinese Wikipedia, some user said that he do not want to use Vector skin
anymore so he change the skin back to MonoBook. However, the edit toolbar is
still the new editor. I want to ask that is it now possible to use the
MonoBook's edit toolbar but not the Vector's Wikieditor?
Thanks.
HW
User from zhwp
To help both non-English speakers and people who can't type very well,
I've created a GreaseMonkey script which checks your response to the
FancyCaptcha challenges seen on Wikimedia and elsewhere.
http://userscripts.org/scripts/show/96233
The script is not specific to GreaseMonkey and could easily be
provided in some other way, such as a gadget or site JS.
The check is done as you type, and a tick icon is shown instantly if
the response you have given matches a pair of words in the dictionary.
This helps you to spot typos before you press "submit".
Restrictions in FancyCaptcha mean that the dictionary only needs to
have about 8500 words, so it's easily embedded in the script.
My original idea was to search for near matches and to provide an
autocomplete drop-down, but the necessary UI code for that seemed a
bit too complicated for a quick weekend project. Maybe later.
-- Tim Starling
I've just opened a new account on the Danish Wikipedia.
I was asked to read the following Captcha :
http://da.wikipedia.org/w/index.php?title=Speciel:Captcha/image&wpCaptchaId…
I provided the following answer : "shipsneeds" and it was accepted.
But I must confess that reading the second "e" and the "d" was
difficult for me.
I was anguished, because I feared that if I answered a wrong answer, I
would not be given a second chance for some time.
I don't see why both "e"s should have a different look. Because they
looked different, I was puzzled during a long time before eventually
choosing to type a second "e". The vertical bar of the "d" being
extremely short in comparison with that of the "h" and that of the
"p", I was wondering if the last character could not be a square
looking "o" or a manual script "a".
I had all these difficulties although I am among the advanced readers
and speakers of English. I Know that "ee" is an often found character
combination in English. I could also recognize the words "ships" and
"needs".
What about non-English speakers ?
Should we not have Japanese-based, Malayalam-based (there is a lot of
talk nowadays in having Wikipedia growing in India), etc. captchas ?
For the time being, while the captcha is English-based, how about
adding a button with "let me try another captcha" for people
experiencing a captcha that is very difficult to read ?
I just checked and determined that there appear to be no AAAA records
yet for the WMF servers.
I have to admit to having been negligent in examining the IPv6
readiness of the Mediawiki software. Is it generally working and
ready to go on IPv6?
Does the Foundation have a IPv6 support plan ready to go?
The importance of this is going to be high in the Asia-Pacific region
within a few months:
http://www.potaroo.net/tools/ipv4/rir.jpg
(APNIC runs out of IPv4 space to give to providers somewhere around
August, statistically; RIPE in Feb or March 2012, ARIN in July 2012).
In each region, ISPs then will start running out of IPv4 to hand out
within a month to three months of the registry exhaustion.
We have a few months, but by the end of 2012, any major site needs to
be serving IPv6.
Out of curiosity, is anyone from the Foundation on the NANOG mailing lists?
--
-george william herbert
george.herbert(a)gmail.com
Hi,
I have some difficulties to use the actual Selenium framework for testing MW
and an extension:
- In trunk, selenium tests are both in tests/selenium and
maintenance/tests/selenium. Why is that?
- If I want to test Mediawiki versions other than the latest, how would I do
that if files for both the testrunner and the application under test are
only in trunk?
Or is there just too much going on for Selenium testing at the moment that
one should wait?
Regards,
Benedikt
--
Karlsruhe Institute of Technology (KIT)
Institute of Applied Informatics and Formal Description Methods (AIFB)
Benedikt Kämpgen
Research Associate
Kaiserstraße 12
Building 11.40
76131 Karlsruhe, Germany
Phone: +49 721 608-47946 (!new since 1 January 2011!)
Fax: +49 721 608-46580 (!new since 1 January 2011!)
Email: benedikt.kaempgen(a)kit.edu
Web: http://www.kit.edu/
KIT University of the State of Baden-Wuerttemberg and
National Research Center of the Helmholtz Association
Our site has 4 skins that display the logo - 3 standard and 1 site-
specific. The site-specific skin uses rounded edges for the individual
page area frames, while the standard skins use square edges. This means a
logo with square edges looks fine for the standard skins, but not for the
site-specific skin. A logo with rounded edges has the opposite
characteristic.
The programmer who designed the site-specific skin solved this problem
with a hack. The absolute url to a different logo with rounded edges is
hardwired into the skin code. Therefore, if we want to reorganize where
we keep the site logos (which we have done once already), we have to
modify the site-specific skin code.
While it is possible that no one else has this problem, I would imagine
there are skins out there that would look better if they were able to use
a skin specific logo (e.g., using a different color scheme or a different
font).
My question is: has this issue been addressed before? If so, and there is
a good solution, I would appreciate hearing of it.
Regards,
--
-- Dan Nessett
Hey all,
I've been working on the InlineEditor extension again, primarily working on a new interface that doesn't use the different edit modes anymore, as the usability testing showed that this was not the right approach. Luckily, without a change in the underlying algorithms, it was doable to combine all the edit modes into one interface. This also resulted in the deletion of tens of files plus hundreds of lines of code [1], which usually is a good thing, because it shows it's a simpler and more natural approach. If you're interested in testing this on your own wiki or looking at the code, grab your copy from SVN. [2]
If you're interested in testing this, a wiki has been set up here: http://janpaulposma.nl/sle/wiki As you might know, some more usability testing will be done soon by GRNET [3], so we can see if this interface works better or not. Feel free to ask questions and throw in suggestions, etc.
Best regards,
Jan Paul
[1] http://www.mediawiki.org/w/index.php?path=%2Ftrunk%2Fextensions%2FInlineEdi…
[2] http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/InlineEditor/
[3] https://code.grnet.gr/projects/wikipedia-wysiwyg/wiki
