Title: Poisonous plant names.
Personal Authors: Wagstaff, D. J., Wiersema, J. H.
Author Affiliation: FDA, Center for Food Safety and Applied
Nutrition, Washington, DC 20204, USA.
Editors: Garland, T., Barr, A. C.
Document Title: Toxic plants and other natural toxicants
Abstract:
This chapter describes a checklist of poisonous plant names, which
currently includes 4672 species in 1646 genera and 255 families.
There are 11 614 common names. This list of plants reported to be
toxic represents approximately 1% of the known vascular plants of
the world. The checklist is organized in a DataPerfect database.
Publisher: CAB International
_________________________________________________________________
Greetings, Purodha
We've got this nice clean (relatively unused) wiki sitting around.
Why not put suggestions on there and use some approval voting
to see which names have the most support?
~ Kylu
__________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now at
http://ca.toolbar.yahoo.com.
Xanthium works for me too... should really confuse people nicely.
(I'd say it tsanthium but I could be wrong...)
Larry Pieniazek
Hobby mail: Lar at Miltontrainworks dot com
When we named nightshade, the theme was "poisonous plants".
Current servers (from https://wiki.toolserver.org/view/Servers )
* Hemlock
* Nightshade
* Willow
* Zedler (Not a poisonous plant, but names after Johann Heinrich Zedler,
who was an 18th century German encyclopedist. This is in keeping with
the WMF naming scheme.)
* Yarrow
* Vandale (As above, but Van Dale was Dutch.)
* Clematis (Poisonous plant, not an encyclopedist)
Short, usable, and thematic (poisonous plant) names might be:
* Azalea
* Daphne
* Digitalis
* Foxglove
* Hellebore
* Holly
* Lilly
* Oleander
* Privet
* Wolfsbane
* Yew
"Daphne", "Holly" and "Lilly" have the distinction of also being female
names, which would give us another opportunity to confuse those
trying to understand our naming schema.
I'm rather fond of Azalea personally, though I think someone reminded me
recently that "nightshade" was my suggestion, so I'll sit this one out.
~ Kylu
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
Hi there,
When looking at the replication lag, I see that s3 is not replicating
and I understand the impact of it on the relationship between the tools
and the projects hosted on s3. But I also see that commons-s1 is not
replicating, and I don't understand anymore: if it is a replica of the
Commons DB, tools working on Commons should be affected by it, right?
But it seems not to be the case. What didn't I understand?
Regards,
Eusebius
While looking at the access statistics of the Query-to-map tool I discovered
that a large portion of the hits are generated by one single austrian DSL IP
(90000 hits yesterday (9% of all hits that day), 55000 hits so far today, ).
Seemingly random queries to lots of tools. Example:
84.114.164.84 - - [11/Jan/2009:14:03:43
+0000] "HEAD /%7Ekolossos/wp-world/umkreis.php?la=pt&lon=16.285&lat=48.134444&rang=50&map=1
HTTP/1.1" 200 0 "-" "Jakarta Commons-HttpClient/3.1"
84.114.164.84 - - [11/Jan/2009:14:03:49
+0000] "HEAD /~para/earth.php?latdegdec=48.134444&londegdec=16.285&scale=300000
HTTP/1.1" 301 0 "-" "Jakarta Commons-HttpClient/3.1"
84.114.164.84 - - [11/Jan/2009:14:03:49
+0000] "HEAD /~kolossos/wp-world/umkreis.php?la=nl&lon=16.285&lat=48.134444&rang=50&map=1
HTTP/1.1" 301 0 "-" "Jakarta Commons-HttpClient/3.1"
84.114.164.84 - - [11/Jan/2009:14:03:50
+0000] "HEAD /~kolossos/wp-world/umkreis.php?la=pt&lon=16.285&lat=48.134444&rang=50&map=1
HTTP/1.1" 301 0 "-" "Jakarta Commons-HttpClient/3.1"
What is going on here? Proxy?
Daniel
P.S.: there is a webserver on that IP. Looks like a broken Mediawiki
installation, a broken forum installation. No further info though.
I am preparing the Technology Report for this week's edition of the Signpost
on enwiki. (see http://en.wikipedia.org/wiki/User:Aude/Technology_report)
I have some idea about how toolserver works, aware that there are issues
with replication and that Yarrow (one of the servers) was down. What is the
status now? It sounds like things are not 100% back to normal. How long
(estimated) will it take to be back to normal?
There are a number of tools linked from the featured article candidates
pages. Are these all working 100%? What other tools are affected?
http://en.wikipedia.org/wiki/Wikipedia:Featured_article_candidates/Typhoon_…
Any information for the Signpost would be most appreciated.
Cheers,
-Aude
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
as Wikimedia deleted the MySQL binlogs required for replicating s3 on the
Toolserver, replication is now halted. a full dump/import is required to fix
replication. because disk space on yarrow is limited at the moment, and we are
about to receive new servers, i might wait until this before reimporting.
(however, if that's likely to take a long time, i might do it sooner.)
- river.
-----BEGIN PGP SIGNATURE-----
iD8DBQFJYWeSIXd7fCuc5vIRAo03AJ9ouEHS98oTwKPugzcUsc8Lp+LmSgCffFmd
gK3xul+k9UinKPPHH5Q3PWg=
=pnlB
-----END PGP SIGNATURE-----