Hi all,
I haven't got some much time to work as much as I would like to on Inkscape. But I try to read mails from development and user ML, plus get a look at evolution of bugs, RFE and CVS on a daily basis. I also try to check wiki updates as often as possible. And each time I consult wiki, i face the same problem : I remove at least 3 or 4 spams a day !!! It's my modest contribution, hoping developpers don't get that much annoyed by the spam. But I think that spam removal is only an emergency solution. I'm not sure is can last for long. First because spam (and its removal) break the history of the wiki modification. Then because I'm not sure that this wiki janitor tasks have a real added value. If I remember well, spam nuisance had already been discussed on this ML a few months ago. I think it is time to think about it once more. Spending some time on this issue now, will save some (stupid) waste of energy in the long run. If I remember well several solutions had been issued but rejected : - post by registered members : main drawback = loss of the direct contact with potential users - confirmation message + non computer readable question = not convenient for people with vision problems. ...
Regards,
Matiphas
On Mo, 2004-10-18 at 12:50 +0200, Gazal, Geraud (GE Healthcare) wrote:
Hi all,
I haven't got some much time to work as much as I would like to on Inkscape. But I try to read mails from development and user ML, plus get a look at evolution of bugs, RFE and CVS on a daily basis. I also try to check wiki updates as often as possible. And each time I consult wiki, i face the same problem : I remove at least 3 or 4 spams a day !!! It's my modest contribution, hoping developpers don't get that much annoyed by the spam. But I think that spam removal is only an emergency solution. I'm not sure is can last for long. First because spam (and its removal) break the history of the wiki modification. Then because I'm not sure that this wiki janitor tasks have a real added value. If I remember well, spam nuisance had already been discussed on this ML a few months ago. I think it is time to think about it once more. Spending some time on this issue now, will save some (stupid) waste of energy in the long run. If I remember well several solutions had been issued but rejected :
- post by registered members : main drawback = loss of the direct contact
with potential users
- confirmation message + non computer readable question = not convenient for
people with vision problems.
The second is not too big of a problem: I mean, I don't mean to be discriminating, but first of all there aren't all that many people with vision problems and secondly, for people for whom it's hard to read an image with some numbers and letters (that's what I think you're talking about) it won't be quite possible to use a graphics program imho. maybe you can display the numbers as bitmap and svg...the svg could be scalable with the font size.
On Mon, 18 Oct 2004, Gazal, Geraud (GE Healthcare) wrote:
I haven't got some much time to work as much as I would like to on Inkscape. But I try to read mails from development and user ML, plus get a look at evolution of bugs, RFE and CVS on a daily basis. I also try to check wiki updates as often as possible. And each time I consult wiki, i face the same problem : I remove at least 3 or 4 spams a day !!! It's my modest contribution, hoping developpers don't get that much annoyed by the spam. But I think that spam removal is only an emergency solution. I'm not sure is can last for long. First because spam (and its removal) break the history of the wiki modification. Then because I'm not sure that this wiki janitor tasks have a real added value.
Yes, it definitely is a help, to keep it under control. The other thing you can do to help mitigate it is to send me a list of the IP addresses or terms that crop up; I can then use this to establish bans and edit blocks for them. That way you're not simply continually reverting the same spammer's stuff.
I also agree we probably need to find good longer term solutions, preferrably ones that don't take a lot of effort to implement (unless someone would be interested in doing the coding). I'm not sure about using the signup approach, both because it's a hassle for users, but also because I've seen at least a couple spammers that were posting as a signed-in account. Although, if the spam becomes too much of a problem and there are no other ideas, maybe it'd be worth trying.
Bryce
participants (3)
-
Bryce Harrington -
David Christian Berg -
Gazal, Geraud (GE Healthcare)