I recently set up a MediaWiki (http://server.bluewatersys.com/w90n740/)
and I need to extra the content from it and convert it into LaTeX
syntax for printed documentation. I have googled for a suitable OSS
solution but nothing was apparent.
I would prefer a script written in Python, but any recommendations
would be very welcome.
Do you know of anything suitable?
I've been tinkering with an extension to provide for a captcha to reduce
automated linkspamming while still staying out of the way for common use.
My preliminary code is running now on test.leuksman.com; the actual
"captcha" part is a really primitive plain text hack which would take
all of a few minutes for a dedicated attacker to crack, but don't worry
about that -- I'm not testing the protection yet, just the framework it
By default the captcha prompt will only kick in if an edit adds new URLs
to the text. Most regular editing shouldn't trip this -- wiki links,
plain text, or just preserving existing links. But if you add new HTTP
links that weren't there before, it'll then make you pass the captcha
before it saves.
The captcha step can also be bypassed based on user group (eg registered
bots, sysop accounts, optionally all registered users), and can also be
set to skip for any user who has gone through confirmation of their
account e-mail address.
I haven't coded it yet, but it should also be possible to add a URL
whitelist, for instance for the site's own local URLs.
As for a 'real' captcha generator to put into this system; I'm not too
sure what code is already out there that's not awful. There's a Drupal
plugin which would be easy to rip GPL'd PHP code from, but it doesn't
seem very robust.
There's a set of samples of various captcha output and their weaknesses
Obviously it would be good to either find something on the 'hard
captchas' list rather than 'defeated captchas', or roll our own that
doesn't suck too bad.
There's also the question of whether we can feasibly provide an audio
alternative or whathaveyou.
-- brion vibber (brion @ pobox.com)
Would it be especially complicated to add the namespace=? parameter to the
"What links here?" mechanism?
I would be quite happy to add it to the URL manually at first, but this
would be most useful ploughing through huge lists of links trying to make
out whether something is actually being linked to meaningfully.
I have just joined, I am from mumbai, india. I would like to get the
articles translated in marathi, my mother tongue. Looking at the effort
and no of volunteers, this will not be usable in any reasonable amount
That has made me think of alternatives - machine translation. A state
funded institute has a software available but I don't have access to it
Pl. comment about this approach. Has this been tried for any other
Thanks & regards,
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony
One of the inconvenience of the discussion page in wikipedia is the
fact that does not have a mail-client type of interface/display. That
is neither there is a email-summary type of display, nor a display
which would allow to display the threads easily.
Are there any plans to include such a feature.
A possibility to would be to have a input and output filter for a
neutral mbox format. For example the Debian bug track system has such
[cc'ed from thread on wikien-l to wikitech-l]
On wikien-l, Neil Harris wrote:
>charles matthews wrote:
>> But I think we know all this. To return to Toynbee, it is more a
>> question of how to get Wikipedians to 'feel challenged', on the
>> specifics. Right now, with the site running slow, the main practical
>> challenge seems to be hardward/developers/cash. _I_ mostly feel
>> challenged by the sheer breadth of approach needed.
>At the risk of being tedious,
Brion, what would it take to get article rating switched on? Is there
any such feature you would allow in, or is it basically off the agenda
and I should stop asking?
Magnus Manske wrote:
>P.S.: I think I actually found a *real* bug; it seems anyone can change
>the list of topics. I'll have to restrict that to sysops.
I'd expect on Wikipedia that'd be a steward-level thing. Remember that
after the testing phase, it's unlikely to change very often if at all,
and then only with the consent of the wiki's community.