[[List of dramatists]] and, I imagine, quite a few other lists, are
organised alphabetically.
The page has a TOC which, while being useful, is butt-ugly due to excesive
length. What would be great for this sort of TOC is an alternative
presentation such as A | B | C | D or even just A B C D. Since we have a
code to suppress the TOC, could we create one that would flag generation
of a compact, horizontal layout?
I can also see potential for a skin where the ToC is rendered as
position:fixed (Supported now by most modern browsers other than IE for
Windows).
I would offer to help with implementation but my expertise in server-side
scripting is in a language other than php :-(
--
[ Note new address/phone from July 12th! ]
[ dramatic design --- for web | print | theatre ]
[ 146 lemon st | new plymouth 6401 | new zealand ]
[ tel +64-6-757-8090 | cell +64-27-221-5053 ]
[ fax +64-6-757-8090 | e richard(a)dramatic.co.nz ]
[ web http://www.dramatic.co.nz/ ]
This software is used to make maps like those on
http://meta.wikipedia.org/wiki/The_first_useful_maphttp://meta.wikipedia.org/wiki/The_polygon_map
It's not all the software I have here.
Queries in city names database are being made separately,
here only "cities2.pl" with cities for the first useful map is attached.
This software needs:
* absolutely most recent version of ImageMagick (5.5.7-10)
5.5.7-9 is not recent enough, it contains very serious bug
* Ruby and RMagick
* Geo::E00 (attached)
And data:
* NASA's BlueMarble (raster background)
ftp://mitch.gsfc.nasa.gov:21/pub/stockli/bluemarble/
* CIA World DataBank II in text format (rivers)
http://www.evl.uic.edu/pape/data/WDB/
* UNEP/GRID data (boundaries / polygons)
http://www.grid.unep.ch/data/grid/gnv19.php
I'm not terribly certain about copyright status of this.
If it's bad, we always have 1988 free data and
only a couple of borders to digitalize.
It should be possible to run it without BlueMarble
or rivers data if these features aren't used.
Boundary data is necessary.
Jimbo wrote:
>Through the work of a user who I won't name because
>I'm not sure if he wants to be anonymous on this,
>I now have a potential contact in the right
>department at AOL who may be sympathetic to our
>plight with respect to Michael.
A good place to start is
http://www.wikipedia.org/wiki/User:Michael which lists
all of Michael's pseudonyms and know IP
address/ranges. IPs for the user names will have to be
retrieved by somebody with developer access.
--mav
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Through the work of a user who I won't name because I'm not sure if he
wants to be anonymous on this, I now have a potential contact in the
right department at AOL who may be sympathetic to our plight with
respect to Michael.
Presumably, I'm going to need a log of ip numbers and times (GMT, I
guess) so that they can establish the account name from that.
Can someone help me with this?
--Jimbo
How difficult would it be to implement a user/ip watchlist (or add
such functionality to the current watchlist feature)? It seems that
it would be useful to many sysops to be able to add "micheal" to their
watchlist, or his IP, or even an IP block (I mean a range of IPs here,
like an IP with netmask) that would indicate a person using his ISP
(or him with a new IP).
Something like this could track an IP block in real time before an edit is
attempted, giving sysops a chance to block an IP before he tries to
edit. Though this doesn't seem too useful, it could give a vandal the
impression that our system is automatically tracking them down, even
when they delete their cookies, change their login, and change IPs.
It might cause them to give up.
Also, it might be helpful to "hold" (for a few minutes) edits made by
an IP range with a message like "your edit has been held temporarily
due to our super-intelligent vandalism filter. If the edit is
legitimate, you can rest assure that it will be processed in a few
minutes. If your edit is vandalism, you should head for the hills, we
know who you are." This way, sysops could revert the vandalism before
the vandal gets the satisfaction of seeing it go live.
--
"Jason C. Richey" <jasonr(a)bomis.com>
>> Hrmm. I thought part of the joy of IP blocks was that vandal user
>> accounts can't come in from that IP either. I've used this at least
>> once to ban a logged-in vandal.
>
> If a user on the same IP continues the pattern of vandalism, surely
> we would ban that user?
Why make life difficult? If we actually know a vandal's IP address, why allow
him to use it with all the 30 accounts he's already created?
--
Allan Crossman - http://dogma.pwp.blueyonder.co.uk
PGP keys - 0x06C4BCCA (new) || 0xCEC9FAE1 (compatible)
This post is dedicated to Michael :)
I did a quick hack which allows sysops to ban logged-in users. This was
discussed on wikien-l long, long ago, and was widely agreed to be a good
idea (well, not that widely, but Jimbo was particularly keen). Basically you
just type the username into the ban IP box. I changed a few messages to
indicate that you could do it.
Blocking a logged-in user by IP address was slightly trickier (but still
only required a handful of lines). Whenever any banned user successfully
logs on and accesses a page, their IP address is automatically blocked. The
reason given is 'Autoblocked because you share an IP address with "Michael".
Reason: blah blah blah', and the "blocked by" field is copied. That way the
"you are banned discuss this with xxxx" message still makes sense. As usual,
these automatically generated entries, and the original username entries,
can be unblocked by any sysop (even blocked sysops).
I know Michael has been making a nuisance of himself again, so I'm sure a
lot of people will be interested in seeing this go live quickly.
I also fixed that annoying undeletion problem (mostly). It still doesn't
update the search index, or user_newtalk, or site_stats, or probably a few
other things. But at least the link table is fixed up.
-- Tim Starling
Michael Becker wrote:
>So the new and improved notice will read: "All content is
>available under the terms of the GNU Free Documentation
>License. See Wikipedia:Copyrights for suggested practices."
There is one problem with this; it is a lie. Wikipedia has many photos that
are used under "fair use" or "non-commercial use" doctrines.
-- mav
Hi,
I've got an Google Adwords coupon free of charge with a
web server I ordered. I don't need this coupon for my
server so I thought about donating it to wikipedia.
It's a 50 Euro coupon and if we create an add using
the keyword "encyclopedia" google estimates it to
cost 12 Euros per day when paying only the minimal
Cost-per-Click rate of 5 cent. This would mean it's
a 4 days campaign.
Any thoughts?
Regards,
JeLuF
> May I suggest one more piece of logic?
> An IP block is automatically released if a non-banned user logs in on it.
> (which means that the IP has been reassigned away from the vandal)
Hrmm. I thought part of the joy of IP blocks was that vandal user accounts
can't come in from that IP either. I've used this at least once to ban a logged-
in vandal.
A vandal shouldn't be able to escape the block by creating new user accounts
(or falling back to user accounts that already exist)
I myself would like to suggest a feature: when we get sysop ability to ban
logged-in users, the last IP of a banned user should itself be banned for, oh,
an hour or so (without actually revealing the IP address to any non-developer,
if there are privacy concerns). Is that feasible?
Note the part about not revealing the IP address - this shouldn't become a way
for sysops to determine arbitrary users' IP addresses, by banning them briefly
(though actually I would like to be able to check IP addresses, but I guess if
we're going to have a privacy policy we can't do that).
Evercat
--
Allan Crossman - http://dogma.pwp.blueyonder.co.uk
PGP keys - 0x06C4BCCA (new) || 0xCEC9FAE1 (compatible)