On Sunday 28 July 2002 03:00 am, The Cunctator wrote:
> What are the articles this person has been changing?
For 66.108.155.126:
20:08 Jul 27, 2002 Computer
20:07 Jul 27, 2002 Exploit
20:07 Jul 27, 2002 AOL
20:05 Jul 27, 2002 Hacker
20:05 Jul 27, 2002 Leet
20:03 Jul 27, 2002 Root
20:02 Jul 27, 2002 Hacker
19:59 Jul 27, 2002 Hacker
19:58 Jul 27, 2002 Hacker
19:54 Jul 27, 2002 Principle of least astonishment
19:54 Jul 27, 2002 Hacker
19:52 Jul 27, 2002 Trance music
19:51 Jul 27, 2002 Trance music
For 208.24.115.6:
20:20 Jul 27, 2002 Hacker
For 141.157.232.26:
20:19 Jul 27, 2002 Hacker
Most of these were complete replacements with discoherent statements.
Such as "TAP IS THE ABSOLUTE DEFINITION OF THE NOUN HACKER" for Hacker.
For the specifics follow http://www.wikipedia.com/wiki/Special:Ipblocklist
and look at the contribs.
--mav
So, it seems (if I interpret Jimbo's mail on wikitech and the discussion
here correctly) that most of us would like *some kind* of category
scheme in wikipedia. I do, too! But, we seem to differ on the details
(shocked silence!).
So far, I saw three concepts:
1. Simple categories like "Person", "Event", etc.; about a dozen total.
2. Categories and subcategories, like
"Science/Biology/Biochemistry/Proteomics", which can be "scaled down" to
#1 as well ("Humankind/Person" or something)
3. Complex object structures with machine-readable meta-knowledge
encoded into the articles, which would allow for quite complex
queries/summaries, like "biologists born after 1860".
Pros:
1. Easy to edit (the wiki way!)
2. Still easy to edit, but making wikipedia browseable by category,
fine-tune Recent Changes, etc.
3. Strong improvement in search functions, meta-knowledge available for
data-mining.
Cons:
1. Not much of a help...
2. We'd need to agree on a category scheme, and maintenance might get a
*little* complicated.
3. Quite complex to edit (e.g., "<category type='person'
occupation='biologist' birth_month='5' birth_day='24' birth_year='1874'
birth_place='London' death_month=.....>")
For a wikipedia I'd have to write myself, I'd choose #3, but with
respect to the wiki way, #2 seems more likely to achieve consensus (if
there is such a thing;-)
Magnus
--- Stirling Newberry <stirling.newberry(a)xigenics.net> wrote:
>
> On Mar 9, 2005, at 7:52 PM, Mark Williamson wrote:
>
> > What about people who speak Hopi as their first language and would
> > like to read about Milwaukee?
>
> What about the vast majority of our readers who have needs that are
> being ignored while certain individuals ride their private hobby
> horses?
Er, that is what I do already by writing about the things I find to be
interesting. That is the hobby horse I ride. Why is this wrong?
-- mav
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
I have been amazed at the passions that were stirred up when I proposed that we distribute free fonts.
There have been two types of reaction: Point to a source that has a partial solution, sometimes for money and bickering about the level of handholding that a user may need.
As there is not one golden solution, it is not simple to say spend $$ and you are ready.
It can also become part of the installation of software that goes with a DVD for of-line use. When having enough fonts is needed for the best wikipedia experience, why wouldn't we give a helping hand to our current users and help them in this way ??
Thanks,
Gerard
incidently
These days, when you navigate quietly on the smaller
wikipedias, this is what you see
http://ia.wikipedia.org/w/index.php?title=Wikipedia%3AFrontispicio&diff=0&o…
I thought I was working for a project trying to gather
free content so as to make free knowledge available ?
So why are we using copyrighted pictures ?
"This image is copyrighted. The copyright holder
allows anyone to use it for any purpose, provided that
the copyright holder and image provider are credited.
Image provided by hornyboy.com and copyright held by
RudeBox Media, Inc."
Ant
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Hoi,
More than 125 Italian politicians have now their own soundfile. They can
be found here: http://commons.wikimedia.org/wiki/Category:Italian_politician
More than 2500 words pronounced in Dutch can be found here:
http://commons.wikimedia.org/wiki/Category:Dutch_pronunciation
The idea is that you cannot reliably pronounce a word as it it should be
pronounced just by seeing the characters when the word originated from
another language. By making these resources available, it is clear how
they should be pronounced in the original language. Having
pronunciations available is important because they help people study a
language and, the wikipedia articles are a great resource to learn a
language; they are short, cover a subject well and many of the related
words related to a subject can be found in the article.
We are thinking of what (sound) resources would be popular as well..
Soccer stars like Ruud Gullit ?? We have volunteers that may pronounce
them in Italian, German or Dutch.
We would REALLY like to have pronunciations for soccer stars because the pronunciations of these gentlemen is often really bad. It would be a fun project to have.
Thanks,
GerardM
Hello, I have a question about your article that appeared in Wired. One of
my difficulties within the Wikipedia community, or, say for example, this
e-mail list, is the large number of people one is likely to come across. It
can be difficult to keep track of everyone, particularly in the context of
editing a diverse set of web pages So, I was wondering how do people come
to know of each other? In particular, for your article, how did you select
the folks you did? Asked Jimbo? Looked at the top contributors?
Thanks!
The following changes have been made to the Python Wikipediabot
framework since the previous overview of February 6. As always, the
new files can be downloaded at
http://cvs.sourceforge.net/viewcvs.py/pywikipediabot/pywikipedia/, and
one can of course use a newer version as well. Furthermore, changes
have been done to the Wikimedia software early February, and to the
bot as well. Therefore:
* versions of wikipedia.py older than 1.391 (February 5) do not work any more
* If you use a version of anything from February 6 or later, you
should use a version of everything (more precisely, wikipedia.py,
config.py and the specific bot you are using) from that date or later.
But on to the newer changes. For the bugfixes I will describe which
bot(s) is or are affected, and what goes wrong with older versions.
"int." means that the bug has been introduced in some earlier version.
Bugs both introduced and solved in the current period have not been
mentioned. For all changes the files and versions that are needed are
mentioned.
Andre Engels
== Dependencies ==
In general, if error messages occur upon downloading a new version of
a bot, getting a new version of wikipedia.py as well would be the
first idea. Versions of wikipedia.py 1.405 and higher need family.py
1.21 (and vice versa)
== Bug fixes ==
* general * wikipedia.py 1.397 (int. 1.392 - does not count number
of bot processes correctly)
* general * wikipedia.py 1.397 (int. 1.392 - cannot edit redirect
pages and cannot create new pages)
* general * wikipedia.py 1.406 (is unable to edit after having been
dormant for some time)
* catall.py * catall.py 1.13 (int. 1.12 - gives an error message
before ending)
* category.py * category.py 1.62 (int. 1.61 - major disfunction)
* category.py (and others) * catlib.py 1.32 (finds at most 200
articles in a category)
* interwiki.py * family.py 1.20 (does not find pages on csb:)
* interwiki.py * family.py 1.21, wikipedia.py 1.406 (does not
recognize [[{xx:PAGENAME}]] interwiki links and a few redirects)
* interwiki.py * interwiki.py 1.135 (crashes when the -continue
option is used with an empty dumpfile)
* interwiki.py * interwiki.py 1.136 (chance of not being removed
from the list of bot processes if stopped *very* soon after being
started)
* interwiki.py * titletranslate.py 1.38 (crashes when a non-existing
language is given as a hint)
* pagefromfile.py * pagefromfile.py 1.7 (int. 1.6 - gives error
message at end and is not removed from the list)
* pagefromfile.py * pagefromfile.py 1.8 (the option "-end" is not recognized)
* redirect.py * redirect.py 1.19 (int 1.18 - major disfunction)
* replace.py * replace.py 1.35 (int. 1.6 - gives error message at
end and is not removed from the list)
== Major changes ==
* interwiki.py can now, when asking for hints, be asked for the text
of the page by typing "?" or adding the "-showpage option *
interwiki.py 1.136
* replace.py and solve_disambiguation.py now give their diffs colored
(Unix only) * replace.py 1.37, solve_disambiguation.py 1.128,
wikipedia.py 1.404
* Two new features of sqldump.py: findr finds regular expressions; the
function of baddisambiguation is not clear to me * sqldump.py 1.17
* interwiki.py uses nb: instead of no: in presence of an nn: link or
on the nn: wiki * interwiki.py 1.139
== Minor changes ==
* Swedish translations for interwiki.py: interwiki.py 1.137
* Change of Icelandic text for category.py: category.py 1.63
* Hawaiian and Chichewa added to known languages (wiktionary only
Hawaiian yet): wikipedia_family.py 1.89, wiktionary_family 1.21
== Cosmetic changes / invisible changes ==
* Multiple alternative redirect texts for one language are supported:
wikipedia.py 1.406
* Special care for zh-cn/zh-tw difference removed: interwiki.py 1.139,
wikipedia.py 1.408
I would like to raise a little issue.
It is currently possible to do redirection from all projects to one
project image.
I'll give you a nice example.
Imagine you connect yourself to wikipedia, and get a bright orange
message "You have a message".
You click on it... and find yourself facing the autofellatio image.
You would love to vote for its deletion (you do not support such an
image on your project), but unfortunately, the image is on another
wikipedia, where maybe you do not have an account, and actually you have
no idea if this image is welcome or not welcome on the other pedia and
actually you may not even have the right to vote for its deletion.
If you are lucky enough, you quickly find the way to cancel the
redirect. Maybe not.
-------
Many months ago, we made it impossible to link to external images,
because we were fighting to avoid the goatse.
Now, several wikipedias are dirtied by the pornographic images available
on the english wikipedia.
So, I suggest that
* either we all agree to share common images, since they can impact us
and in this case, I would like that a common vote is held to decide the
deletion of this image from the english wikipedia
* or we agree that no local projects should be submitted to the
editorial choices made by other projects and redirections between
projects should be cancelled
* or we find a filtering solution, so that certain images not welcome to
other projects may not be redirected.
In case of all sensible images such as the autofellatio, it should be
the project choice whether to display it or not. And I think the
multiplication of complaints on the topic requires to think about a
viable solution for all of us.
Ant
The Dutch are progressing in creating a chapter of the Wikimedia
Foundation. A Wiki-site to support the initiative is live for a week now
at http://nl.wikimedia.org/ The domain wikimedia.nl has been squatted by
Sam van Buuren on January 25th, 2005. We'll have to reclaim that.
The Netherlands Antilles are still a country of the Kingdom of the
Netherlands (as is Aruba). Their official language is Papiamentu,
ISO-639 code is PAP. Surinam is a former colony of the Netherlands. Half
their population is living in the Netherlands. Their tongue is Sranang
Tongo, ISO-639 code presumed to be SRN. The Dutch Wikimedia chapter to
be incorporated will have as mission to support all projects run by
people in the Netherlands regardless of language. Frysian and Limurgian
projects (fy and li) have already been started. There are no projects in
Papiamentu or Sranang Tongo yet.
We would like to establish an initial framework for these two languages
to provide a head start to these communities. Waerth pushed me to take
the first step.
Dedalus
_________________________________________________________
Het ministerie van Sociale Zaken en Werkgelegenheid sluit elke aansprakelijkheid uit in verband met het niet juist, onvolledig of niet tijdig overkomen van de informatie in deze e-mail.
Aan dit bericht kunnen geen rechten worden ontleend.
Dit bericht is alleen bestemd voor de geadresseerde. Indien dit bericht niet voor u bestemd is, verzoeken wij u dit onmiddellijk aan ons te melden en de inhoud van dit bericht te vernietigen.
_________________________________________________________
The ministry of Social Affairs and Employment is not liable for any incorrect or incomplete transmission of the information in this e-mail or for any delay in its receipt.
This message shall not constitute any obligations.
This message is intended solely for the addressee.
If you have received this message in error, please inform us immediately and delete its content.
_________________________________________________________