Difference between revisions of "SoC geeklog2 spam solution"
(→Further Reading) |
m (outdated - added link to current list) |
||
(5 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
+ | This is an old project idea for our (now defunct) sister project, AptitudeCMS (aka Geeklog 2). This project outline is therefore only of historical interest and you can not apply for this project in future instances of the Google Summer of Code. Please see our [[Google Summer of Code|ideas page]] for a current list of GSoC project ideas. | ||
+ | |||
+ | |||
== Incentive == | == Incentive == | ||
The internet contains nearly as much Spam as it does HTML. A new generation of web applications must start out from their infancy iron-clad with defences against Spam. Geeklog2 is no exception. The objective of this project is to develop a plugin for the Geeklog2 system to provide spam filtering. | The internet contains nearly as much Spam as it does HTML. A new generation of web applications must start out from their infancy iron-clad with defences against Spam. Geeklog2 is no exception. The objective of this project is to develop a plugin for the Geeklog2 system to provide spam filtering. | ||
+ | |||
== Objective == | == Objective == | ||
* Implement a Geeklog2 plugin to provide an API for spam filtering | * Implement a Geeklog2 plugin to provide an API for spam filtering | ||
− | * Include an extensible framework (like | + | * Include an extensible framework (like Spam-X) for extending the abilities of the spam filter |
* Include modules to support key anti-spam systems including | * Include modules to support key anti-spam systems including | ||
− | * LinkSleeve | + | ** LinkSleeve |
− | * Akismet | + | ** Akismet |
− | * Project Honey Pot | + | ** Project Honey Pot |
− | * SWOT | + | ** SWOT |
− | * Local blacklists | + | ** Local blacklists |
− | * Bad | + | ** Bad Behavior |
+ | |||
== Level of Difficulty == | == Level of Difficulty == | ||
Line 19: | Line 24: | ||
''Medium'' | ''Medium'' | ||
− | The | + | The Spam-X approach, with the full OO world of PHP5 seems to be a good base approach, and we have code to talk to the above listed key anti-spam projects largely available. However, ensuring this is a performant, scaleable, extensible, maintainable and well implemented solution may pose some challenges. |
+ | |||
== Further Reading == | == Further Reading == | ||
− | [http://www.linksleeve.org/ LinkSleeve] | + | |
− | [http://akismet.com/ Akismet] | + | * [http://www.linksleeve.org/ LinkSleeve] |
− | [http://www.projecthoneypot.org/ Project Honey Pot] | + | * [http://akismet.com/ Akismet] |
− | [http://swot.fuckingbrit.com/ SWOT] | + | * [http://www.projecthoneypot.org/ Project Honey Pot] |
− | [http://www.bad-behavior.ioerror.us/ Bad | + | * [http://swot.fuckingbrit.com/ SWOT] |
− | [[ | + | * [http://www.bad-behavior.ioerror.us/ Bad Behavior] |
+ | * [[Spam-X Plugin]] | ||
+ | |||
+ | |||
+ | [[Category:Summer of Code]] [[Category:Development]] |
Latest revision as of 20:45, 4 March 2010
This is an old project idea for our (now defunct) sister project, AptitudeCMS (aka Geeklog 2). This project outline is therefore only of historical interest and you can not apply for this project in future instances of the Google Summer of Code. Please see our ideas page for a current list of GSoC project ideas.
Incentive
The internet contains nearly as much Spam as it does HTML. A new generation of web applications must start out from their infancy iron-clad with defences against Spam. Geeklog2 is no exception. The objective of this project is to develop a plugin for the Geeklog2 system to provide spam filtering.
Objective
- Implement a Geeklog2 plugin to provide an API for spam filtering
- Include an extensible framework (like Spam-X) for extending the abilities of the spam filter
- Include modules to support key anti-spam systems including
- LinkSleeve
- Akismet
- Project Honey Pot
- SWOT
- Local blacklists
- Bad Behavior
Level of Difficulty
Medium
The Spam-X approach, with the full OO world of PHP5 seems to be a good base approach, and we have code to talk to the above listed key anti-spam projects largely available. However, ensuring this is a performant, scaleable, extensible, maintainable and well implemented solution may pose some challenges.