At 11:52 25/10/04 +0100, Simon Marlow wrote:
I've now put binary zips for Windows of Haddock and Happy up on haskell.org. These are snapshots of recent CVS sources:
http://www.haskell.org/haddock/haddock-Win32-snap.zip http://www.haskell.org/happy/dist/happy-Win32-snap.zip
There's already a binary zip of Alex available.
Thanks. I've added some links from the Wiki page: http://www.haskell.org/hawiki/LibrariesAndTools http://www.haskell.org/hawiki/LibrariesAndTools#head-ed5b9922c3c8f6a33ac20f4... #g ------------ Graham Klyne For email: http://www.ninebynine.org/#Contact
Graham Klyne wrote:
Thanks. I've added some links from the Wiki page: http://www.haskell.org/hawiki/LibrariesAndTools
http://www.haskell.org/hawiki/LibrariesAndTools#head-ed5b9922c3c8f6a33ac20f4...
This page looks quite interesting, but it has nothing to do with Haskell anymore... :-] A quick look at http://www.haskell.org/hawiki/RecentChanges shows that the Haskell Wiki had quite a few spam problems recently. That's exactly why I think that very open Wikis are doomed to death nowadays, given the criminal energy of spammers. So I strongly argue that *the* Haskell libraries/tools pages remain plain old HTML pages, edited by someone who I can trust. Cheers, S.
Oh b..... How easy is it to password protect the Wiki? I'm thinking that a password known to the Haskell community would act as a sufficient bar to random spamming. (I guess someone has fixed the wiki for now, because those links look OK to me.) #g -- At 08:44 29/10/04 +0200, Sven Panne wrote:
Graham Klyne wrote:
Thanks. I've added some links from the Wiki page: http://www.haskell.org/hawiki/LibrariesAndTools
http://www.haskell.org/hawiki/LibrariesAndTools#head-ed5b9922c3c8f6a33ac20f4...
This page looks quite interesting, but it has nothing to do with Haskell anymore... :-] A quick look at http://www.haskell.org/hawiki/RecentChanges shows that the Haskell Wiki had quite a few spam problems recently. That's exactly why I think that very open Wikis are doomed to death nowadays, given the criminal energy of spammers. So I strongly argue that *the* Haskell libraries/tools pages remain plain old HTML pages, edited by someone who I can trust.
Cheers, S.
------------ Graham Klyne For email: http://www.ninebynine.org/#Contact
Graham Klyne
Oh b.....
How easy is it to password protect the Wiki? I'm thinking that a password known to the Haskell community would act as a sufficient bar to random spamming.
(I guess someone has fixed the wiki for now, because those links look OK to me.)
I could set the wiki to only allow editing by 'logged in' users. But that's also easy to fake. Right now, 'page revert' is allowed to any logged in users. I've been using IP address banning, but that's becoming less successful. I've been planning to switch to the AntiSpamGlobalSolution[1] when that solution is significantly better, it seems now is the time. By the way, many thanks to the Haskell Wiki users who revert spam on a regular basis! There will always be a tradeoff between security and ease of use, and the wiki approach is towards ease of use and little security. The advantage of a wiki is that anyone can edit it, so anyone can update the pages. That's good for taking work away from website administrators and giving it to the community at large, but it means that spammers can change stuff too. As Udo Stenzel said, spam scripts are only available for a few wiki engines. We could switch to using Flippi, but that still wouldn't keep out the manual wiki spammers. I would still like to use a Wiki written in Haskell on haskell.org [1] http://moinmoin.wikiwikiweb.de/AntiSpamGlobalSolution -- Shae Matijs Erisson - Programmer - http://www.ScannedInAvian.org/ "I will, as we say in rock 'n' roll, run until the wheels come off, because I love what I do." -- David Crosby
participants (3)
-
Graham Klyne -
Shae Matijs Erisson -
Sven Panne