Skip to content

How to deal with comments #23

@timoschilling

Description

@timoschilling

I think the timeouts come from to much comments in the database.

Since now we have a Heroku scheduler wich deletes the comments each hour.

I have following the logs during the first scheduler run, before it starts we have 99% timeouts, ~1 minute after the run the timeouts going down to 0%.

There are 3 way to go for the future:

  1. turing off comments (Switch over to Rails4 #22)
  2. IP blocking (Implement a permanent IP ban #14)
  3. login required comments (Github Auth as Login #21)
  4. Comment Captcha
  5. cleanup
  6. delete all comments each hour (current behavior)
  7. delete comments older then x hours each hour

My opinions are:

  1. it reduce the fictionality 👎
  2. it never catch all IP's and sometimes to many 👎
  3. will stop users from trying the demo 👎
  4. it's ok, but nobody likes Captchas 👎
  5. can result in adding a comment and don't seeing it 👎
  6. removing old comments should not disturb anybody 👍

I'm interested in, what others think about this? // cc: @seanlinsley, @pcreux, @eshaiju

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions