> The Cunctator wrote:
> >> http://sep11.wikipedia.org/
> >
> > Is there some way for me to be able to tweak the settings myself? E.g.
> > stylesheet, default text, etc. Otherwise I guess I'll build a mockup of
> > the interface.
>
> Not yet, no.
>
> Mock away...
>
Other than dev. access, of course. I suppose I should avoid that timesink.
Jonathan Walther wrote:
> *cough*Postgres*cough* Anyone else agree it's time to switch to a
> database that is just as fast as MySQL, but does row level locking
> without slowing down any other concurrent database accesses, plus has
> roll-back and all the other nice ACID features?
Worth a shot; I'll see if I can get it running on my test server.
-- brion vibber (brion @ pobox.com)
Can someone set this up for Cunc?
----- Forwarded message from The Cunctator <cunctator(a)kband.com> -----
From: The Cunctator <cunctator(a)kband.com>
Date: Sat, 26 Oct 2002 13:31:45 -0400
To: Jimmy Wales <jwales(a)bomis.com>
Subject: sep. 11.
Would you be willing to set up sep11.wikipedia.org with the Phase III
software? If you do so, I can do the work so that the advocacy/tribute pages
can be redirected from Wikipedia to there.
Thanks,
tc
----- End forwarded message -----
Brion wrote:
>Saving verrryyyy llloonnnggg pages seems to precipitate this. I just
>cropped off the upload log ([[Wikipedia:Upload log]]) from several
>gazillion lines each with two links, and it took a few minutes to
>finish saving, blocking the database until it was done.
Could it be that updating the link tables (links, brokenlinks and
imagelinks) takes a long time? Are these tables properly indexed?
Axel
__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/
Attached is a quick-n-dirty PHP script which should parse the
Accept-language header correctly and pick the most preferred known
language. Ie; if the first language is not in our known list, we keep
going to the next ones until we find one or run out.
-- brion vibber (brion @ pobox.com)
<?
$knownlangs = array( "de", "en", "eo", "fr" ); #etc
$lang = "en"; # Last-ditch fallback, it's the most developed wiki
$lastquality = 0.0;
# Note HTTP reference RFC 2616 - ftp://ftp.isi.edu/in-notes/rfc2616.txt
$langtag = '((?:[a-zA-Z]{1,8})(?:-[a-zA-Z]{1,8})*)';
$qvalue ='(0(?:\.[0-9]{1,3})?|1(?:\.0{1,3}))';
$eachbit = '^' . $langtag . '(?:;q=' . $qvalue . ')?(?:,\s*)?(.*)$';
$alh = trim( $HTTP_SERVER_VARS["HTTP_ACCEPT_LANGUAGE"] );
echo "$alh<br>\n\n";
while(strlen($alh)) {
if( preg_match( "/$eachbit/", $alh, $m ) ) {
$tag = $m[1];
$quality = $m[2];
if(strlen($quality) == 0) $quality = 1;
$alh = $m[3];
#echo "language '$tag' quality '$quality'\n";
if(in_array($tag, $knownlangs) and $quality > $lastquality) {
$lang = $tag;
$lastquality = $quality;
}
} else {
break;
}
}
echo "Using language $lang with preference $lastquality";
?>
I have copied the old list members and archives over to the new list,
and have begun forwarding the old list address
(wikitech-l(a)nupedia.com) to wikitech-l(a)wikipedia.org. I beleive that
it is working without problem. Please let me know otherwise. I also
beleive that I copied the membership options correctly, though I'm not
absolutely positive. One thing I expect will be slightly different is
the time that the daily digests are received. I beleive the new
server is set to UTC whereas the old server was on PDT, and I beleive
digests go out at 5:00pm server local time...
Please let me know if you witness any trouble.
--
"Jason C. Richey" <jasonr(a)bomis.com>
I have installed mailman on the new server to server the wikipedia
lists. More specifically, someone requested a list "francais-l" be
added to the nupedia domain, but I found that a list by that name is
already in use for Nupedia's purposes, so I made it
francais-l(a)wikipedia.org instead. So, we now have the ability to make
any wikipedia lists point to wikipedia.org...
So, my question is this: On the old scheme, we prefixed the list name
with 'wiki' to indicate that it was for wikipedia. As I copy the old
lists to the new server, should I convert the list-names as well? I
think not, but I thought I should ask.
Also, are these the only wikipedia lists? I think they are.
Intlwiki-l
Wikitech-l
Wikipedia-l
WikiNL-l
And I think this begs another question. The Dutch list is WikiNL, and
the french list is francais-l (though this new list is not yet
public). Should we go with a standardized naming scheme on the
language-specific (or is it country-specific?) lists. Should I change
francais-l to wikiFR-l?
Jason
--
"Jason C. Richey" <jasonr(a)bomis.com>
LDC wrote:
>Giskart wrote:
>>I see that more and more people are use Wiki-makeup
>>and removing HTML tags. But I like to use HTML-tags.
>>Is there, from a technical point of view any difference
>>between the folowing notations;
>>== Foobar ==
>><h2>Foobar</h2>
>Wiki markup is preferred because a good Wikipedia article
>is not only useful to read, but easy to edit. We want non-
>compter nerds to be able to easily edit and add to topics
>in which they are interested. Also, I still have a long-
>term plan of eliminating most HTML for security reasons.
The security issue should be a separate concern.
We can allow "<h2>...</h2>" as wiki markup
without allowing "<span onmouseover="...">...</span>".
I do agree that "==" is better, however,
and we should make wiki markup look like HTML markup
only for rarely used but supported features (like <strike>)
and as a deprecated alternative for newbies' sakes.
>I also treat Wiki markup specially in the software in a
>few places; for example == Foobar == will cause a page
>to be ranked higher in a search for "Foobar", but the
>equivalent HTML tag will not.
I've also suggested treating the rendering of "=" markup in HTML
analogously to how we treat its rendering for numbered headers:
the shortest string of '='s will always be <h2>,
even if it happens to be the currently deprecated "===".
But then "<h3>" could still be used to force an <h3> tag in the HTML.
Although this proposal got little response and is unlikely to happen,
the point is that some variation is possible, and might be desirable,
for certain purposes.
-- Toby