New Karma module - any comments? Shall I release it?

Hello,

I've just created a new karma module.
I am not entirely sure other people would be interested in it. It's well code, well commented, and it's about to be tested on a production server (http://www.freesoftwaremagazine.com).

Now... here is a (probably not comprehensive) list of features:

• Javascript voting; however, the module works 1000% even if the
  user doesn't have Javascript

• Abuse control. The module allows you to limit users on how many karma points
  they cna give, to a particular user or in general. The admin can also decide
  on how many different comments a user can vote on

• Publishing the best comment in a special spot, ONLY for nodes associated
  to selected (configurable) terms. This allows certain forums (for
  example) to have this feature, and create a "Ask Jeeves"-like
  web sites

• Automatic assignment of roles depending on the karma range. This means
  that you can make some users more powerful according to the
  karma they have. It's DEADLY CRUCIAL that you create roles SPECIFICALLY
  for this module. This module will turn the set roles on and off, with
  no mercy. Roles are assigned when a user signs up, which means that
  you can assign a "default role" to a user.

• Automatic assignment of userpoints based on a custom formula when
  karma is assigned. The Karma module will take/give userpoints according
  to the karma received/taken away. This is handy if you allow people to
  "spend" their user points, for example.

• Bonus karma-voting owers to people with specific permissions. The module
  sets a number of specific permissions. When a user has them (because
  they are associated to a role, for example), then the user can give/take
  more karma on each vote.

• Ability to bury comments below a certain karma. The administrator
  can set a threshold under which a comment is marked as buried. The
  comment will still show up, but users won't be able to vote for it
  nor see its contents.

• Ability for the karma administrator to see all of the buried
  comments and vote on them (users can't vote for buried comments). This
  way, the administrator could un-bury them, or use this as
  anti-abuse mechanism.

• No HTML anywhere in the module. Everything is configurable from the
  admin interface

• Ability to put the karma form in the link section of the comment
  or anywhere in the comment template (by hand)

• Ability to see users by karma, and (for the karma administrator) the

• ability to see who got karma when

• Karma points expire in N days (where N is configurable). NOTE:
  points expire only as far as users are concerned. All of the
  queries consider ALL of the karma votes for comments. This makes sense:
  a user's karma will tend to 0 as time passes, whereas a comment's
  karma will stay forever

It doesn't use the voting API. However, it "interfaces" with it, meaning that when people get karma points, the module might invoke the userpoint API to give that user some userpoints.
(And yes, it works totally fine even if a vote is re-cast, since it checks the txn history if a vote is re-cast, please check the code)

You can get the module from here:

http://www.freesoftwaremagazine.com/sk.tgz

Please NOTE: don't enable the userpoint abilities just yet, since it needs a version of userpoints that is not available just yet (the author of userpoints, Khalid Baheyeldin, has the patch as is reviewing it, see my patch here: http://drupal.org/node/142956. The patch fixes an issue where the trail is not updated if no moderation is required, and the trail is ALWAYS NECESSARY to simple_karma in case a person re-votes ).

The obvious question first: why didn't I use the voting API to keep track of the karma? Basically, because karma and userpoints are two different things. They work in different ways, and it would be bad to confuse them. The main difference in terms of tables (that is, the real showstopper technically) is that karma has a 'giver' and a 'receiver', and they are both very important. If you are not convinced, have a look at the module's code (which is very easy to read and follow, BTW).

Why am I writing here?

I was just wondering if you guys thought I should release it to drupal.org (I have CVS access to the contrib repository) and if you had any comments, really. I really only have time for bug fixing, but any extra ideas will definitely be added to a nice "ideas.txt" file for the next release!

One note: the recalculation hasn't been tested yet. So please beware and backup your DB before trying this module.

Bye!

Merc.