Since now I know how to make a request for SVN access, here's my
request:
Key: http://toolserver.org/~techman224/sshpubkey.txt
Commit name: techman224
Alternative commit name: techman
I will use my commit access to help categorize some extensions that
haven't been yet, and other small maintenance tasks I can handle if I
see them.
Thanks,
Techman224
I've analyzed Wikipedia's HTML code for representing geographical
coordinates. The current code is verbose and does not support the Geo
microformat correctly. Three alternatives, differing on functionality
and code size, are suggested as replacements:
http://www.princexml.com/howcome/2009/wikipedia/geo/
Alternative 1, which is comptible with Wikipedia's current syntax for
personalized presentation, reduces the number of elements from 14 to
10. Alternative 2, which uses CSS generated content to achieve
personalized presentations, reduces the number of elments from 14 to 5
and the code size from 798 to 248 bytes.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome(a)opera.com http://people.opera.com/howcome
Hello all,
A reminder that WikiSym 2009 will be in Orlando, Florida, from October
25-27. The deadline for submitting papers, workshops and panel
proposals is March 27; April 24th is the deadline for posters,
demonstrations and WikiFest (practical experience) proposals.
Topics of interest include:
* social software for collaboration and work group processes
* wiki user experiences, usability, and discourse analysis
* reputation systems, quality assurance processes
* scalability---social and technical
* wiki technologies and implementations
* translation and multilingual wiki content
* educational applications
* wiki for non-textual media (images, video, audio)
* content dynamics and wiki evolution
* wiki journalism
* wiki archiving and versioning
* wiki administration: dealing with abuse and resolving conflict
* wiki and the semantic web, knowledge management, tacit knowledge
* wiki for small audiences (departmental and family wikis)
* legal issues (copyright, licensing)
* visualization of wiki structure
* wiki fiction
For more information, see the Call for Papers:
http://www.wikisym.org/ws2009/tiki-index.php?page=Call+for+Papers
WikiSym is an annual conference devoted to research into all aspects
of wikis, including wiki communities, wiki software and technology,
and using wikis in education and organizations. Research papers about
the Wikimedia projects are welcome! Papers are peer reviewed and
archived in the ACM digital library (see past proceedings:
http://portal.acm.org/toc.cfm?id=SERIES11299&coll=ACM&dl=ACM&type=series&id…
The conference is colocated with OOPSLA 2009. For more, see:
http://www.wikisym.org/ws2009/
-- Phoebe Ayers (2009 Wikimedia Liason)
I'm curious what does
SELECT COUNT(DISTINCT old_text), COUNT(*) FROM text;
show on Wikipedia's database? On mine I get
COUNT(DISTINCT old_text): 2913
COUNT(*): 3560
I.e., 1/7 of the rows are redundant.
Currently undos, so frequent on wikis, just blindly create a duplicate row
instead of checking if the old one could be reused,
https://bugzilla.wikimedia.org/show_bug.cgi?id=18333 . Maybe some hardware
savings could even be achieved.
You could always email Brion or Tim directly...but they're
both really busy...
-Chad
On Apr 8, 2009 9:46 AM, "Aryeh Gregor"
<Simetrical+wikilist(a)gmail.com<Simetrical%2Bwikilist(a)gmail.com>>
wrote:
On Wed, Apr 8, 2009 at 2:50 AM, Jan Luca <jan(a)jans-seite.de> wrote: > Hello,
> > when will there a a...
I don't know. It's not up to me.
_______________________________________________ Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia....
Hello --
Given that the Renameuser extension now uses the job queue for renames
involving over 10,000 edits (and thus no longer locking the site for large
renames), is there any technical reason not to give administrators the
renameuser right?
And, if there are no technical prohibitions, is this something that would
require per-project voting or would switching it across all Wikimedia wikis
be acceptable?
Thanks!
MZMcBride
public(a)mzmcbride.com
en.wikipedia.org and others have seen a rash of abuse coming via Tor in
the form of account creations with abusive names and such; this is
taking up a large chunk of CheckUser and oversighter time and effort,
which is apparently not too fun.
It looks like the current settings don't generally restrict various
actions to a logged-in user when accessing through Tor; is there any
objection to tightening this up to restrict edits, account creations,
etc via Tor except when the account is explicitly excepted?
-- brion vibber (brion @ wikimedia.org)