comment on

My experience with PM leads me to believe that voting has a much better chance of resulting in a useful categorization system than privilege (the tag adders, tag deleters, and considerers) does.

My bet is that privilege won't result in a very useful tag system and, even if it starts to, the effect won't last.

I think you need to allow anyone (or nearly so, maybe about level 3) to add keywords and nearly anyone to vote for/against keywords. But tracking votes is O( nodes * users ) and is the biggest part of our database. Keyword votes could be O( nodes * users * words ). But not tracking keyword votes just affords voting abuse... Maybe an alternative of only tracking recent votes and limiting number of votes per day would not balloon out of control but would strongly discourage voting abuse...

But I don't think you've designed a keyword system that will work yet. And I don't think that will be an easy design. But I think such could be very useful.

- tye

In reply to Re: Keyword Nodelet / Tagging documentation (vote > privilege) by tye
in thread Keyword Nodelet / Tagging documentation by castaway

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks