-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase in spam in the past few weeks #74
Comments
Hey @jezdez. I'll take a look. Thanks for the report! |
Much appreciated! |
I'd also consider dropping Twitter for registration and only allow Github and Bitbucket. I think our audience that does have Twitter, but does not have Github goes towards zero. |
Yeah, agreed. |
Hi @jezdez.
We'll get it sorted. Thanks. |
@carltongibson Done. |
Ta. Just a thought... should I delete the spam posts whilst I'm in there? (I know that's a loosing battle but...) |
When you mark them from the website as spam (https://dsc.cloud/a46d84/6iAe6iikIpEqkNDcTPNA) you can then go into the "snippet flags" section and select the "remove snippet and ban user" admin action. |
Super. Thanks. I'll do a bit of that as I go. 🙂 |
OK, follow-up here with interim conclusions.
If anyone wants to help with any of these, super. But I'll potter away at them too. |
Im happy to pick up this work, should I start with #38 ? |
Hi @chriswedgwood. Yes. That would be super. Thanks! |
Hi @carltongibson 👋 Just learned about https://djangosnippets.org/ and was hoping I could start contributing right away. For the following interim conclusion: |
Hi @santos22 Great timing I was just about to start working on this feature and thankfully hadn't started. I think that is exactly what we are looking for! Once a snippet is flagged it should only be visible to staff and not to normal users? |
I'll start working on adding recaptha. May as well give it a go |
Hi @santos22. Rather an Admin Action. From the admin list view, it's easy to see spam, so it would be good to mark them from there. I hope that makes sense. |
Makes sense to me - currently working on that item 👍 Thanks for clearing that up! |
It seems as if there is a lot of new spam coming in from people using Twitter (IIUC) to sign up for djangosnippets. I would suggest to increase the bar for submission by
SOCIALACCOUNT_EMAIL_VERIFICATION
(which would require a separate email verification upon signup via twitter and github)SOCIALACCOUNT_QUERY_EMAIL
and maybeSOCIALACCOUNT_EMAIL_REQUIRED
(which would make the whole thing required)https://django-allauth.readthedocs.io/en/latest/configuration.html
@carltongibson @felixxm @stephrdev Does anyone have some spare cycles to take a look at this?
The text was updated successfully, but these errors were encountered: