@tkama
Well the main problem is that there are no logs when you are not tracking IP …
Saving IP “anyway” is good for when your site is being attacked by a few IPs – you can block those IPs very easily since you’d see them in logs…

Custom CSS class: a) democracy seems to generic (might colide) but mainly, b) you can already have some prepared functionality, like boxing etc… BTW: Main target of this is to ADD ADDITIONAL classes, not removing the current one 😉

@tkama

Your option is “Log data & take visitor IP into consideration”
The description of this option is:

Saves data into Data Base. Forbids to vote several times from a single IP or to same WordPress user. If a user is logged in, then his voting is checked by WP account. If a user is not logged in, then checks the IP address. The negative side of IP checks is that a site may be visited from an enterprise network (with a common IP), so all users from this network are allowed to vote only once. If this option is disabled the voting is checked by Cookies only. Default enabled.

…see I do NOT want to restrict votes per IP ! 🙂 But I DO want to log the vote info … do you get it now ? 🙂 You are conditioning vote logging with IP restriction ! 🙂

…CSS class, let’s say you have a nice box wrapper with some cool shadow under class “panel” – you would have to add selector to CSS defining it, however you might not be able to because it is some external CSS framework…
Still “democracy” is too generic word, it should be something a bit more specific.

Also I said that main target is to add option to ADD ANOTHER class – which is really easy (your CSS & JS would remain intact).