This message I see quite often:
Sorry- we have a problem...
The wikimedia.org servers are currently overloaded, or down.
Hopefully this will be fixed soon; please check back in a few minutes, as the problem is most likely temporary
To get information on what's going on you can visit #wikipedia.
An "offsite" status page is hosted on OpenFacts.
Donations
Due to the ever-increasing number of people visiting Wikipedia and its sister Wikimedia projects, we have a constant need to buy new hardware to keep the site running. If you'd like to help, please donate.
Some links to pass the time:
* Wikipedia's ever-increasing popularity
* Paper describing the wikimedia network structure
Generated Wed, 02 Jun 2004 15:17:04 GMT by wikipedia.org
(squid/2.5.STABLE4-20040219)
-=-=-=-=-=-=-=-=-=-=-=-=-=- cut here -=-=-=-=-=-=-=-=-=-=-=-=-=-
but I can edit another article without delay. And I can also save the
article in question if I play with logout/login. Looks like a cache
problem to me.
--
| ,__o
| _-\_<,
http://www.gnu.franken.de/ke/ | (*)/'(*)
On Wed, 2 Jun 2004, Pochung Chen wrote:
>
>
> Begin forwarded message:
>
> > Pochung(Pektiong) Chen(Tan) wrote:
> >> Hi There,
> >> The user community on "southern min" (min-nan) wikipedia would like
> >> to request to rename the currently used "zh-cfr" to "zh-min-nan".
> >> The tag "cfr" makes no sense to the native speaker and the user
> >> community.
> >> The tag "zh-min-nan" makes sense and is a registered RFC 3066 tag.
> >> Please rename the name of southern min wikipedia a.s.a.p, thanks!
> >> pektiong
> >
> >
> > How about minnan.wikipedia.org? It's shorter, doesn't conflict with
> > anything, and is easy to remember.
> >
> > -- Tim Starling
Please use zh-min-nan.wikipedia.org. This name is the consensus of the
community. And following are some rationals.
*most current wikipedia use ISO 639-1/-2 language tag.
*for any new wikipedia whose language doesn't have its own ISO 639-1/-2
language tag, we should use a language tag which is compatible with ISO
639-1/-2.
*we hence should use "RFC 3066 - Tags for the Identification of Languages"
when it is possible. http://www.faqs.org/rfcs/rfc3066.html
*note that for RFC 3066 schema,
All 2/3-letter subtags are interpreted according to assignments found in
ISO standard 639-1/2, i.e., RFC 3066 is compatible with ISO 639.
*RFC 3066's tag for Southern min language is zh-min-nan
http://www.iana.org/assignments/lang-tags/zh-min-nan
I hope those arguments can convince the people here that the only logical
name should be "zh-min-nan.wikipedia.org". The article
Taiwanese(linguistics) on English wikipedia should provide many useful
informaiton if you fell the need to understand this language more.
http://en.wikipedia.org/wiki/Taiwanese_%28linguistics%29
best
pektiong
I noticed some messages while logged in to will today:
Message from syslogd@will at Tue Jun 1 20:21:45 2004 ...
will kernel: CPU0: Temperature above threshold
Message from syslogd@will at Tue Jun 1 20:21:45 2004 ...
will kernel: CPU1: Temperature above threshold
Message from syslogd@will at Tue Jun 1 20:21:45 2004 ...
will kernel: CPU1: Running in modulated clock mode
Message from syslogd@will at Tue Jun 1 20:21:45 2004 ...
will kernel: CPU0: Running in modulated clock mode
.. and so on, continuing until 20:41 - which suggests that someone might have
forgotten to plug in a fan or two. Jimbo, if you're heading to the colo
tomorrow, could you take a look at it please?
-Jerome
Hi.
I've played around with the /User:xyz/monobook.css feature today. It's
incredibly cool. Not just because I can customise the look of the site
for myself, but also because it's pretty damn flexible.
However, almost all formatting for infoboxes like the taxoboxes and
article series boxes (ignoring for a second the question whether we
still want them, with the categorisation system in place now) is in the
markup for those tables themselves.
It should instead be in a Wikipedia-global CSS file.
So my idea would be to have a [[Wikipedia:monobook-global.css]] or
something like that, which contains the CSS for these boxes, and which
is also wiki-editable, so as to allow users (or at least sysops) to
define new classes for new kinds of elements as they are invented.
Then
(a) we can keep the styling out of the table mark-up
(b) users can customise these things with the same flexibility as
everything else!
Thoughts?
While we're at it, please could someone casually add a class="..."
attribute to the table row in the TOC that contains the words "Table of
Contents"? Thanks ;-)
Timwi
Hello,
As shaihulub told me on irc, it seems the parser using tokenizer.php
have been disabled. It looks like we are now using an old parser instead.
Lot of the recent bug reports on sourceforge are related to this swicth:
lot of features and bugfixing are no more implemented / fixed :-(
It seems there is a performance issue on the tokenizer, so should we :
1/ get ride of the tokenizer (current situation) and fix bug /
reimplement features
2/ improve the tokenizer performances
;)
--
Ashar Voultoiz
[[w:fr:Utilisateur:Hashar]]
Hi,
currently the wiki-down message reads:
Sorry! The wiki is experiencing some technical difficulties,
and cannot contact the database server.
In the interest of better usability and comprehensibility, please could
someone change it to:
Wikipedia is currently experiencing technical difficulties.
Please try again later. We apologise for the inconvenience.
Please also let me know how many more times I need to post this until
someone at least replies to it, much less actually changes it.
Thanks,
Timwi
TimWi wrote:
"Shouldn't it be called WikiTimeline? ;-)"
Although made specifically for Wikipedia it can be used outside a wiki
context.
Updating an existing timeline (e.g. correcting or adding an event) should be
easy indeed for uninitiated, yet creating an original design and fine-tuning
may easily take a couple of hours. I'm not sure everyone would consider that
'wikiwiki' enough. :)
Once I got some new features online, and unicode support added, I will work
on more examples, which can serve as a template.
----
Here are two great sites that may serve as inspiration, my hands itch to
recreate some of those timelines verbatim, but I'm afraid that would be 'not
done'.
Hyperhistory (e.g. click on button 'people' left, then on 'special
lifelines', right.
http://www.hyperhistory.com/online_n2/History_n2/a.html
I hope we will have a set like this in a years time (click on full size
image for any map), possibly even with images. The main effort will be to
gather all info without snatching everything from here (most of these maps
are based exclusively on data from Brittanica).
http://chaos1.hypermart.net/pg/world.html
Erik Zachte
Currently we get a lot of big gaps between paragraphs as well as at the
beginning and end of articles. The parser generates things like this:
<p><br/>
</p><p><br/>
</p>
whenever there is a Category or inter-wiki link on a line of its own.
Please could someone modify the parser so that, after taking out the
category and inter-wiki links, it removes (ignores) all whitespace at
the beginning and end of the article, and reduces sequences of paragraph
breaks to a single one?
Thanks,
Timwi
Hi There,
The user community on "southern min" (min-nan) wikipedia would like
to request to rename the currently used "zh-cfr" to "zh-min-nan".
The tag "cfr" makes no sense to the native speaker and the user community.
The tag "zh-min-nan" makes sense and is a registered RFC 3066 tag.
Please rename the name of southern min wikipedia a.s.a.p, thanks!
pektiong
I was actually coming to this mailing list today, to discuss the same thing. I'm glad its noticed. I can't see anything against Timwi's idea, it seems to work perfectly.
- Zanimum
wikitech-l-request(a)Wikipedia.org wrote:
Date: Tue, 01 Jun 2004 11:28:38 +0100
From: Timwi
Brion Vibber wrote:
> That's not actually a bug;
It's a usability bug.
> it's just that *nothing* interacts well with
> right-aligned images/tables (for instance, section edit links, and other
> right-aligned images/tables).
The categories shouldn't be inside the article itself; they should be
moved further up a bit:
ARTICLE TITLE Categories: Foo | Bar
------------------------------------------------------------------------
Article text...
Of course, this is my opinion. Discussion is welcome.
Greetings,
Timwi
---------------------------------
Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now