Re: [pygame] how to remove spam comments in pygame wiki

[Nirav Patel <olpc@xxxxxxxxxxxxxx>]

One solution to comment spam is to just use recaptcha on anonymous
comments.  It'll at least remove bot spam and make it more annoying
for repeat human spammers.

Nirav

On Tue, Jul 28, 2009 at 7:11 PM, René Dudfield<renesd@xxxxxxxxx> wrote:
>
>
> On Tue, Jul 28, 2009 at 8:39 PM, jug <jug@xxxxxxxxxxxxxx> wrote:
>>
>> Hello,
>>
>> We are still working on the pygame website rewrite. I'm currently
>> implementing a snippets
>> app that should replace the cookbook section in the wiki. The code is
>> handled as code,
>> apart from the description. Thus, you can download the snippets directly
>> as .py file. Then,
>> its easier for everyone (who has an account) to add new snippets, to find
>> useful snippets
>> and to remember them.
>
> There's a cook book and code search for this now.  This searches the 1000s
> of projects on the internet for each use.  It's much better than a snippet
> section you decided on.
>
>
>>
>> Since comments will be reserved for registered users, number of spam
>> comments and other
>> waste content should decrease a lot. For the rest, we may have something
>> like "mark as spam"
>> buttons, so you can tell the site admins directly if you notice any spam.
>
> why do you get to decide this?  Many of the valid comments are made without
> login, those would not exist if it required a login.
>
>
>
>>
>> Documentation is another problem. I think, with the website rewrite, also
>> the docs should
>> modernized. AFAIK, The current system is something self-made that uses
>> documentation thats
>> already written in html. It blends htms and stlyle to one html file, so it
>> is quite impossible to change
>> the style or to include it to the rest of the site. I don't know how the
>> comments work, but it looks not
>> good. As well, it would be better to have some kind of api access or at
>> least methodical urls to
>> access documentation programmatically form the rest of the site, the apis
>> or even the attached
>> irc bot.
>
> You're completely wrong about the documentation system.  I suggest you
> actually read it before commenting on it.
>
>
>>
>> I don't know about all the possible documentation systems and generators,
>> but sphinx[1] may be
>> adequate. Further on, I'm not sure if documentation should include
>> comments. I think it would be
>> better to use the snippets section to show really useful code snippets (we
>> could link against them
>> from the online docs) and for other stuff the wiki. If there is really
>> sth. missing in the docs, it should
>> be added to them, so also users who download the docs an read it offline
>> should see these additions.
>>
>> Next (maybe pre-final) testing phase will come soon,
>> including the new snippets app and much more.
>>
>
> The comments section is staying.
>
>
>
>