Difference between revisions of "Developing Antispam"
(→Antispam Roles) |
(categorizing) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
=Antispam Privs= | =Antispam Privs= | ||
| − | In order to even see what's in the spam-handling pages, your dreamhack's basic-antispam user will need privs. | + | In order to even see what's in the spam-handling pages, your dreamhack's basic-antispam user will need [[Privileges|privs.]] |
| Line 18: | Line 18: | ||
The following roles, roughly, touch antispam stuff: | The following roles, roughly, touch antispam stuff: | ||
| − | * Site Admin - top of the priv chain of trust; manages large-scale sysbans. | + | * Site Admin - top of the priv chain of trust; manages large-scale sysbans. privs: admin:* |
* Terms of Service - courtesy antispam privs, can suspend | * Terms of Service - courtesy antispam privs, can suspend | ||
* Antispam Lead - can grant antispam privs to new spamwhackers, can suspend OpenID accounts, can suspend regular accounts, has finduser email. | * Antispam Lead - can grant antispam privs to new spamwhackers, can suspend OpenID accounts, can suspend regular accounts, has finduser email. | ||
| Line 24: | Line 24: | ||
If you're testing to make sure nothing has broken, you probably will want users with these sets of privs. (to do: add actual privs list for each role.) | If you're testing to make sure nothing has broken, you probably will want users with these sets of privs. (to do: add actual privs list for each role.) | ||
| + | |||
| + | =Working with Antispam= | ||
| + | |||
| + | Antispam is thrilled to help out the developers who are helping them! | ||
| + | |||
| + | =Miscellaneous= | ||
| + | * http://wiki.dreamwidth.net/wiki/index.php/Dreamhack_spam_prevention | ||
| + | * http://wiki.dreamwidth.net/wiki/index.php/Handling_Spam_Reports | ||
| + | * http://wiki.dreamwidth.net/wiki/index.php/Anti-Spam_Getting_Started | ||
| + | |||
| + | [[Category:Antispam]][[Category:Development]] | ||
Latest revision as of 08:05, 22 September 2015
Antispam is one of the more out-of-the-way corners of Dreamwidth development.
Antispam Privs
In order to even see what's in the spam-handling pages, your dreamhack's basic-antispam user will need privs.
The syntax to grant the necessary privs on the console is:
priv grant siteadmin:spamreports,sysban:talk_ip_test username
Antispam Pages
The antispam pages are located at http://www.dreamwidth.org/admin/spamreports
Antispam users also use http://www.dreamwidth.org/admin/console/ sometimes.
Antispam users have access to the sysban management page but don't often go there now. http://www.dreamwidth.org/admin/sysban
Antispam Roles
The following roles, roughly, touch antispam stuff:
- Site Admin - top of the priv chain of trust; manages large-scale sysbans. privs: admin:*
- Terms of Service - courtesy antispam privs, can suspend
- Antispam Lead - can grant antispam privs to new spamwhackers, can suspend OpenID accounts, can suspend regular accounts, has finduser email.
- Basic Antispam User - can sysban:talk_ip_test, can view spam reports, can close spam reports.
If you're testing to make sure nothing has broken, you probably will want users with these sets of privs. (to do: add actual privs list for each role.)
Working with Antispam
Antispam is thrilled to help out the developers who are helping them!
