How to deal with comments
Closed this issue · 6 comments
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:
- turing off comments (#22)
- IP blocking (#14)
- login required comments (#21)
- Comment Captcha
- cleanup
- delete all comments each hour (current behavior)
- delete comments older then x hours each hour
My opinions are:
- it reduce the fictionality 👎
- it never catch all IP's and sometimes to many 👎
- will stop users from trying the demo 👎
- it's ok, but nobody likes Captchas 👎
- can result in adding a comment and don't seeing it 👎
- removing old comments should not disturb anybody 👍
I'm interested in, what others think about this? // cc: @seanlinsley, @pcreux, @eshaiju
I like the idea of logging in using Github. I am wondering if using Cloudflare or so wouldn't help with preventing bots. Clouflare seems to prevent "attacks"...
I think it's fine to require Github OAuth login (#21) since 99% of people looking to use ActiveAdmin are going to have a Github account. We just need to make sure not to:
- request anything but the most basic of permissions
- store the OAuth private key in the repo (it should be stored in
heroku config)
@seanlinsley you mean "not in the repo" right? If yes, I agree with you
Yes, it was a list of things not to do with double negations. :)
On Sat Jan 17 2015 at 3:36:21 AM Timo Schilling notifications@github.com
wrote:
@seanlinsley https://github.com/seanlinsley you mean "not in the repo"
right? If yes, I agree with you—
Reply to this email directly or view it on GitHub
#23 (comment)
.
Sorry, I didn't read the not in "We just need to make sure not to:"
I'm closing this, there is still the #21