<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: The Honor of 10</title>
	<atom:link href="http://aloedream.animeblogger.net/archives/382/feed" rel="self" type="application/rss+xml" />
	<link>http://aloedream.animeblogger.net/archives/382</link>
	<description>enjoying my nightmare</description>
	<pubDate>Sat, 07 Nov 2009 20:45:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ryan A</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20703</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Sun, 24 May 2009 17:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20703</guid>
		<description>@aurabolt

lol BELL CURVE. Well, the thing about using more levels doesn't really change the fact that a user only has 100% to deal with. 100% is the best a user can give any item. It's broken down more so the system doesn't have to support the tenth or hundredths places. There is no 8.5, but something might get a potential of 85% depending on the levels the user is using.

What does occur, is that if a new level is placed at the top, say 11, everything else is automagically shifted to appropriate percentages.

That's what I've mentioned as &lt;em&gt;potential&lt;/em&gt;, which is more useful in user-to-user evaluations than calculating a overall system rating. For that, we would use the energy/kinetic scoring. The difference is, kinetic scoring considers the depth and diversity of a user's ratings and adds the outcome to an absolute value for a given item.

The main difference in thinking about this sort of scoring, is transition.

&lt;strong&gt;Item X deserves grade Q.&lt;/strong&gt;

This is the current way.

&lt;strong&gt;Item X should be grouped in grade/level Q because of the set Y (other items in Q).&lt;/strong&gt;

This is better for dynamic ratings. It's about grouping items by grade, but not specifically caring what that grade value is... the algorithm will yield something relevant, which can then be looked at between items in the system. (all items are evaluated the same through connecting the dynamic user ratings).

The most important part is how the grade-levels are related greater,lesser,equal (equal implies the the two levels are the same level, level 1 = level 1).

Basic example using your 5 to 9 ratings:

5 = 5
6 = 4
7 = 3
8 = 2
9 = 1

5 levels. Now here are my levels, as possibly related to the above:

10 = 5
9 = 4.25
8 = 3.75
7 = 3.3
6 = 2.8
5 = 2.4
4 = 2.0
3 = 1.6
2 = 1.25
1 = 1

The actual numbers would be different, but don't evenly divide out because it matters how many items are on various levels. (similar to matching the centers of the bell curves)

At some point the numbers really don't matter... which is the objective. What matters is the position of a level and how many levels+items are above and below it. This could be perfectly used with a 10-point system, but hopefully it is clear why the results would be different. Also, bottom offsets would be good, or rather, having a list size, but allowing blank bottom slots where wanted.... no need for top offset since down-boosting is meh, and we care about the list in only one direction.</description>
		<content:encoded><![CDATA[<p>@aurabolt</p>
<p>lol BELL CURVE. Well, the thing about using more levels doesn&#8217;t really change the fact that a user only has 100% to deal with. 100% is the best a user can give any item. It&#8217;s broken down more so the system doesn&#8217;t have to support the tenth or hundredths places. There is no 8.5, but something might get a potential of 85% depending on the levels the user is using.</p>
<p>What does occur, is that if a new level is placed at the top, say 11, everything else is automagically shifted to appropriate percentages.</p>
<p>That&#8217;s what I&#8217;ve mentioned as <em>potential</em>, which is more useful in user-to-user evaluations than calculating a overall system rating. For that, we would use the energy/kinetic scoring. The difference is, kinetic scoring considers the depth and diversity of a user&#8217;s ratings and adds the outcome to an absolute value for a given item.</p>
<p>The main difference in thinking about this sort of scoring, is transition.</p>
<p><strong>Item X deserves grade Q.</strong></p>
<p>This is the current way.</p>
<p><strong>Item X should be grouped in grade/level Q because of the set Y (other items in Q).</strong></p>
<p>This is better for dynamic ratings. It&#8217;s about grouping items by grade, but not specifically caring what that grade value is&#8230; the algorithm will yield something relevant, which can then be looked at between items in the system. (all items are evaluated the same through connecting the dynamic user ratings).</p>
<p>The most important part is how the grade-levels are related greater,lesser,equal (equal implies the the two levels are the same level, level 1 = level 1).</p>
<p>Basic example using your 5 to 9 ratings:</p>
<p>5 = 5<br />
6 = 4<br />
7 = 3<br />
8 = 2<br />
9 = 1</p>
<p>5 levels. Now here are my levels, as possibly related to the above:</p>
<p>10 = 5<br />
9 = 4.25<br />
8 = 3.75<br />
7 = 3.3<br />
6 = 2.8<br />
5 = 2.4<br />
4 = 2.0<br />
3 = 1.6<br />
2 = 1.25<br />
1 = 1</p>
<p>The actual numbers would be different, but don&#8217;t evenly divide out because it matters how many items are on various levels. (similar to matching the centers of the bell curves)</p>
<p>At some point the numbers really don&#8217;t matter&#8230; which is the objective. What matters is the position of a level and how many levels+items are above and below it. This could be perfectly used with a 10-point system, but hopefully it is clear why the results would be different. Also, bottom offsets would be good, or rather, having a list size, but allowing blank bottom slots where wanted&#8230;. no need for top offset since down-boosting is meh, and we care about the list in only one direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aurabolt</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20680</link>
		<dc:creator>aurabolt</dc:creator>
		<pubDate>Sun, 24 May 2009 02:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20680</guid>
		<description>Holy shit, walls of text.

Right, everyone uses a different scale. A '7' does not mean the same for everyone. I do not care much for a title's overall rating, but I would like to see this implemented for generating user-compatibility-ratings (in MAL).

Using offsets does sound like a possible solution to "translating" a user's scale. On the other hand,  I refuse to support a dynamic-point system. Ten is enough. &lt;strike&gt;Any fucker who needs more than ten needs to quit inflating his/her goddamn scores.&lt;/strike&gt;

I personally use scores from '5' to '9' (similar to letter grades). '6' is the neutral line. '7' is where I start saving the series. '9' is reserved to only two series, so '8' is generally the most I give.</description>
		<content:encoded><![CDATA[<p>Holy shit, walls of text.</p>
<p>Right, everyone uses a different scale. A &#8216;7&#8242; does not mean the same for everyone. I do not care much for a title&#8217;s overall rating, but I would like to see this implemented for generating user-compatibility-ratings (in MAL).</p>
<p>Using offsets does sound like a possible solution to &#8220;translating&#8221; a user&#8217;s scale. On the other hand,  I refuse to support a dynamic-point system. Ten is enough. <strike>Any fucker who needs more than ten needs to quit inflating his/her goddamn scores.</strike></p>
<p>I personally use scores from &#8216;5&#8242; to &#8216;9&#8242; (similar to letter grades). &#8216;6&#8242; is the neutral line. &#8216;7&#8242; is where I start saving the series. &#8216;9&#8242; is reserved to only two series, so &#8216;8&#8242; is generally the most I give.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan A</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20458</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Mon, 18 May 2009 18:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20458</guid>
		<description>@ghostlightning, the beauty is that the system can translate whatever their 7 means, into an approximate "tier" in your own ratings. You don't have to figure out what another person's scale means, we just follow the ordering operations (&gt;,&lt;,=).

Of course, there are additional things which would make it more accurate, like finding an intersection series, and then showing the relative distance of other series compared between two lists, while accounting for the difference in tiers (ie. I have 54 tiers, Michael has 10 I believe).

Naturally, just because something ends up on the lowest tier of a smaller list, doesn't mean it should end up on the bottom of a larger list as well; it might end up somewhere in the middle, depending on a possible offset. This sort of thing isn't implemented at this time, but is possible.

@Michael, ^_^ MAL does what it does. I would have used MAL if it wasn't AniDB (thought MAL is less robust with better UI), which I was already fed up with since logging episodic watches and nothing more is quite useless. melative takes a different, less anal approach to experience, there is states and history.

Also, Michael, if you use Firefox and have time, come play with the Stream. http://melative.com/stream (might have to reset pass)

&lt;strong&gt;Edit/Addition:&lt;/strong&gt; @ghostlightning Not sure if you've come across this explanation, but I feel it might make more sense as to why this ratings system requires a different perspective about ratings (in terms of energy and potential). [&lt;a href="http://blog.melative.com/?p=46" rel="nofollow"&gt;link&lt;/a&gt;]

Converting to a 10-point system is indeed possible, but it is closest related to potential (or aggregate position on all lists). The issue is that if the aggregate position is the bottom 10%, that is technically a 1/10 on a fixed point system. Thinking in a fixed-point mindset here will cause trouble, since the true implication is that if there are 10 levels, said item appears on the bottom level. It's not exactly the same as rating it a absolute 1/10... it just means its at the bottom of all items in the system.... no real number needs to be attached... it's relative.</description>
		<content:encoded><![CDATA[<p>@ghostlightning, the beauty is that the system can translate whatever their 7 means, into an approximate &#8220;tier&#8221; in your own ratings. You don&#8217;t have to figure out what another person&#8217;s scale means, we just follow the ordering operations (>,< ,=).</p>
<p>Of course, there are additional things which would make it more accurate, like finding an intersection series, and then showing the relative distance of other series compared between two lists, while accounting for the difference in tiers (ie. I have 54 tiers, Michael has 10 I believe).</p>
<p>Naturally, just because something ends up on the lowest tier of a smaller list, doesn't mean it should end up on the bottom of a larger list as well; it might end up somewhere in the middle, depending on a possible offset. This sort of thing isn't implemented at this time, but is possible.</p>
<p>@Michael, ^_^ MAL does what it does. I would have used MAL if it wasn't AniDB (thought MAL is less robust with better UI), which I was already fed up with since logging episodic watches and nothing more is quite useless. melative takes a different, less anal approach to experience, there is states and history.</p>
<p>Also, Michael, if you use Firefox and have time, come play with the Stream. <a href="http://melative.com/stream" rel="nofollow">http://melative.com/stream (might have to reset pass)</p>
<p><strong>Edit/Addition:</strong> @ghostlightning Not sure if you&#8217;ve come across this explanation, but I feel it might make more sense as to why this ratings system requires a different perspective about ratings (in terms of energy and potential). [<a href="http://blog.melative.com/?p=46" rel="nofollow">link</a>]</p>
<p>Converting to a 10-point system is indeed possible, but it is closest related to potential (or aggregate position on all lists). The issue is that if the aggregate position is the bottom 10%, that is technically a 1/10 on a fixed point system. Thinking in a fixed-point mindset here will cause trouble, since the true implication is that if there are 10 levels, said item appears on the bottom level. It&#8217;s not exactly the same as rating it a absolute 1/10&#8230; it just means its at the bottom of all items in the system&#8230;. no real number needs to be attached&#8230; it&#8217;s relative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20456</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 18 May 2009 17:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20456</guid>
		<description>I don't MAL so I avoid stuff like this. 

10/10 for the post. ;)</description>
		<content:encoded><![CDATA[<p>I don&#8217;t MAL so I avoid stuff like this. </p>
<p>10/10 for the post. <img src='http://aloedream.animeblogger.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ghostlightning</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20448</link>
		<dc:creator>ghostlightning</dc:creator>
		<pubDate>Mon, 18 May 2009 12:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20448</guid>
		<description>I won't pretend that I got all of what you said, but I do sense that you've really thought this through. I like the idea (I think) that the system sorts things out automatically no matter the behavior of the user. What I'm less excited about is that I'd have to spend time figuring out what the user means when she rates something a 7. 

Is it 'good' 7? Or, as you say, a 'pity' 7?

Not everyone can be articulate, as I don't think even I can easily work through a meaning for each number (never mind the decimals, if any). So, having one prepared as a default that can be opted-out from is still a good idea I think.</description>
		<content:encoded><![CDATA[<p>I won&#8217;t pretend that I got all of what you said, but I do sense that you&#8217;ve really thought this through. I like the idea (I think) that the system sorts things out automatically no matter the behavior of the user. What I&#8217;m less excited about is that I&#8217;d have to spend time figuring out what the user means when she rates something a 7. </p>
<p>Is it &#8216;good&#8217; 7? Or, as you say, a &#8216;pity&#8217; 7?</p>
<p>Not everyone can be articulate, as I don&#8217;t think even I can easily work through a meaning for each number (never mind the decimals, if any). So, having one prepared as a default that can be opted-out from is still a good idea I think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan A</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20438</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Mon, 18 May 2009 04:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20438</guid>
		<description>@ghostlightning

&lt;strong&gt;Addition:&lt;/strong&gt; thinking on the system-wide level is important for standards, but giving user-level abilities to change the way the default works is something I like. A good [tangential] example would be the visibility coded into the stream, which allows users to have a completely private or friends-only microblog, but still maintain the ability to publish items with public visibility.

In this dynamic algo I've been developing, the experiences of the user, mix their ratings of each experience play into a larger calculation which results in 2 aggregate statistics.

The thing is, each user does not have equal weighting power. A user rating everything a 9 or 10 is not going to contribute much for a series as opposed to a user who has few things rated 10, and the series was rated 10 (as well as a full spectrum of ratings).

What a user grades a given series is important, but all other grades for other series are taken into consideration as well.

A large part of these dynamic ratings is generating accurate ratings for what ratings are given, relative to all the items within the system.

I believe AniDB does use those standards, but then again when considering the subset of Masterpieces, they can still be organized and rated. IMO, it's incomplete to leave it in such fashion. The other issue is that it can never be an exact rating even if going for a 9.786, since the more precision added the less we actually get what the hundredths and thousandths places mean. Using a sorted list nullifies the need for this decimal precision, but it's not to say we can't place things on the same level.

Everyone does not have to comply. This is true, which is even more push for dynamic ratings which allow users their own compliances, completely separate from other users, but at the same time, having an algorithm which makes aggregate sense of these various rating systems.

The tiers meaning: A&gt;B, A&lt;B, A=B ... that is it.

If a user imports their ratings from 10-point system, it's automatically in the standard. Over time they may branch out the ratings (especially in the upper tiers), but don't need to. If there happens to be more than 10 tiers, the list might be more expressive, such as a hybrid between a top X list and standard point-ratings. The list can change over time, becoming larger and more complex or smaller and less complex, or it doesn't need to do anything since normal 10-point ratings will work just the same individually; the difference is in calculating the aggregate.</description>
		<content:encoded><![CDATA[<p>@ghostlightning</p>
<p><strong>Addition:</strong> thinking on the system-wide level is important for standards, but giving user-level abilities to change the way the default works is something I like. A good [tangential] example would be the visibility coded into the stream, which allows users to have a completely private or friends-only microblog, but still maintain the ability to publish items with public visibility.</p>
<p>In this dynamic algo I&#8217;ve been developing, the experiences of the user, mix their ratings of each experience play into a larger calculation which results in 2 aggregate statistics.</p>
<p>The thing is, each user does not have equal weighting power. A user rating everything a 9 or 10 is not going to contribute much for a series as opposed to a user who has few things rated 10, and the series was rated 10 (as well as a full spectrum of ratings).</p>
<p>What a user grades a given series is important, but all other grades for other series are taken into consideration as well.</p>
<p>A large part of these dynamic ratings is generating accurate ratings for what ratings are given, relative to all the items within the system.</p>
<p>I believe AniDB does use those standards, but then again when considering the subset of Masterpieces, they can still be organized and rated. IMO, it&#8217;s incomplete to leave it in such fashion. The other issue is that it can never be an exact rating even if going for a 9.786, since the more precision added the less we actually get what the hundredths and thousandths places mean. Using a sorted list nullifies the need for this decimal precision, but it&#8217;s not to say we can&#8217;t place things on the same level.</p>
<p>Everyone does not have to comply. This is true, which is even more push for dynamic ratings which allow users their own compliances, completely separate from other users, but at the same time, having an algorithm which makes aggregate sense of these various rating systems.</p>
<p>The tiers meaning: A&gt;B, A&lt;B, A=B &#8230; that is it.</p>
<p>If a user imports their ratings from 10-point system, it&#8217;s automatically in the standard. Over time they may branch out the ratings (especially in the upper tiers), but don&#8217;t need to. If there happens to be more than 10 tiers, the list might be more expressive, such as a hybrid between a top X list and standard point-ratings. The list can change over time, becoming larger and more complex or smaller and less complex, or it doesn&#8217;t need to do anything since normal 10-point ratings will work just the same individually; the difference is in calculating the aggregate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ghostlightning</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20426</link>
		<dc:creator>ghostlightning</dc:creator>
		<pubDate>Sun, 17 May 2009 22:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20426</guid>
		<description>What could be done, for these sites that insist on aggregate ratings, is to insist on its own standards. 

10: Masterpiece, can be recommended to almost anyone. Lack of appreciation will be rare and almost always happen due to extenuating circumstances.
1: A total discredit to anime as a medium. Will only please collectors of terrible experiences.

...etc.

Everyone does not have to comply! One just has to opt-out of the system, which means one's ratings won't be part of the aggregate ratings.

All this does is to derive real conclusions from ratings. The conceptual heavy lifting will be in determining what the standards/ratings tiers/meanings will be.</description>
		<content:encoded><![CDATA[<p>What could be done, for these sites that insist on aggregate ratings, is to insist on its own standards. </p>
<p>10: Masterpiece, can be recommended to almost anyone. Lack of appreciation will be rare and almost always happen due to extenuating circumstances.<br />
1: A total discredit to anime as a medium. Will only please collectors of terrible experiences.</p>
<p>&#8230;etc.</p>
<p>Everyone does not have to comply! One just has to opt-out of the system, which means one&#8217;s ratings won&#8217;t be part of the aggregate ratings.</p>
<p>All this does is to derive real conclusions from ratings. The conceptual heavy lifting will be in determining what the standards/ratings tiers/meanings will be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan A</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20385</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Sat, 16 May 2009 18:20:24 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20385</guid>
		<description>@animekritik AniDB/MAL should get rid of its aggregate ratings and series placement then, but how one rates is tangential to how ratings are evaluated for everyone else (apart from the individual user). The reasoning behind giving a 10 or the top tier for a loved series is the liberty of the user; any rating perspective can be taken (overall enjoyment, technical qualities, story hardliners, etc). I think it's productive for users to note such a thing.

If I look at a rating history of a user, let's say on a 5 point scale, and I see nearly 100 4's and 60 5's, it really doesn't make any sense. That's 160 series which would have scored 8/10 or better on MAL. Is this good information about the titles [or the user]?

At some point these ratings lose significance. Dynamic ratings are an attempt at maintaining significance (mathematically, system-wide) even with such ratings. For the individual scope, it solely allows pliability (yes, one can have an 11 out of 10 if they want to) while staying relevant to other users (those who don't have the 11th tier).

@moritheil always subjectivity, but what are your thoughts on varying degrees? Or is it, like digital, either zero or one. As for the &lt;em&gt;Naruto is a 10&lt;/em&gt; ordeal which later must be re-evaluated, I wrote on the pliability of ratings history earlier this year. [&lt;a href="http://aloedream.animeblogger.net/archives/264" rel="nofollow"&gt;entry&lt;/a&gt;]

Finally, this notion of relative rating doesn't &lt;em&gt;require&lt;/em&gt; a different way about rating. It can be thought of directly comparing series, but users may still rating with a 10/10 scale, just as it would be done anywhere else. The difference comes in flexibility, customization, and calculated significance throughout the entire system.

I'd be interested to hear what changes you guys think might be beneficial to fixed-point systems. I begin these endeavors because I don't feel the available tools are adequate (multiple sites for media, fixed-point rating systems), which is the same for the microblogging stream on melative; allows status updates about externally defined topics (pure content message with none of that, #SeriesNameTag 05: ... garbage in the message).

Or another thought, I could translate your ratings and show exactly what they would look like in the system... this would be interesting with two users, which would bring in divergence/conformity though it's better with more users.</description>
		<content:encoded><![CDATA[<p>@animekritik AniDB/MAL should get rid of its aggregate ratings and series placement then, but how one rates is tangential to how ratings are evaluated for everyone else (apart from the individual user). The reasoning behind giving a 10 or the top tier for a loved series is the liberty of the user; any rating perspective can be taken (overall enjoyment, technical qualities, story hardliners, etc). I think it&#8217;s productive for users to note such a thing.</p>
<p>If I look at a rating history of a user, let&#8217;s say on a 5 point scale, and I see nearly 100 4&#8217;s and 60 5&#8217;s, it really doesn&#8217;t make any sense. That&#8217;s 160 series which would have scored 8/10 or better on MAL. Is this good information about the titles [or the user]?</p>
<p>At some point these ratings lose significance. Dynamic ratings are an attempt at maintaining significance (mathematically, system-wide) even with such ratings. For the individual scope, it solely allows pliability (yes, one can have an 11 out of 10 if they want to) while staying relevant to other users (those who don&#8217;t have the 11th tier).</p>
<p>@moritheil always subjectivity, but what are your thoughts on varying degrees? Or is it, like digital, either zero or one. As for the <em>Naruto is a 10</em> ordeal which later must be re-evaluated, I wrote on the pliability of ratings history earlier this year. [<a href="http://aloedream.animeblogger.net/archives/264" rel="nofollow">entry</a>]</p>
<p>Finally, this notion of relative rating doesn&#8217;t <em>require</em> a different way about rating. It can be thought of directly comparing series, but users may still rating with a 10/10 scale, just as it would be done anywhere else. The difference comes in flexibility, customization, and calculated significance throughout the entire system.</p>
<p>I&#8217;d be interested to hear what changes you guys think might be beneficial to fixed-point systems. I begin these endeavors because I don&#8217;t feel the available tools are adequate (multiple sites for media, fixed-point rating systems), which is the same for the microblogging stream on melative; allows status updates about externally defined topics (pure content message with none of that, #SeriesNameTag 05: &#8230; garbage in the message).</p>
<p>Or another thought, I could translate your ratings and show exactly what they would look like in the system&#8230; this would be interesting with two users, which would bring in divergence/conformity though it&#8217;s better with more users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moritheil</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20379</link>
		<dc:creator>moritheil</dc:creator>
		<pubDate>Sat, 16 May 2009 15:24:47 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20379</guid>
		<description>"I suppose concur, or rather, no matter how objective one may deem their rating, we must still take it as a subjective stance."

Which effectively makes it subjective to the reader.  There could be a distinction, I suppose, but categorically I think recognizing the subjectivity of ratings is essential.  The nature of subjectivity is that people try hard to be objective and still fail. 

I don't think that someone who insists that Naruto is a 10 is necessarily lying or deluded; it might be that Naruto has whatever they're looking for at the moment.  This will definitely not be what everyone is looking for, and it might not be what they themselves appreciate most in a few years.  In no way do those qualifiers detract from the sincerity of the rating.</description>
		<content:encoded><![CDATA[<p>&#8220;I suppose concur, or rather, no matter how objective one may deem their rating, we must still take it as a subjective stance.&#8221;</p>
<p>Which effectively makes it subjective to the reader.  There could be a distinction, I suppose, but categorically I think recognizing the subjectivity of ratings is essential.  The nature of subjectivity is that people try hard to be objective and still fail. </p>
<p>I don&#8217;t think that someone who insists that Naruto is a 10 is necessarily lying or deluded; it might be that Naruto has whatever they&#8217;re looking for at the moment.  This will definitely not be what everyone is looking for, and it might not be what they themselves appreciate most in a few years.  In no way do those qualifiers detract from the sincerity of the rating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: animekritik</title>
		<link>http://aloedream.animeblogger.net/archives/382/comment-page-1#comment-20374</link>
		<dc:creator>animekritik</dc:creator>
		<pubDate>Sat, 16 May 2009 14:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=382#comment-20374</guid>
		<description>on MAL i score strictly on my own love for the show.  if i absolutely love it, it gets a 10.  i don't see why someone would argue that the show they love is "really" a 6 or a 7 (people do it all the time, I know, but I don't see how it's appropriate in any way).  A house divided against itself cannot stand &amp; so forth...</description>
		<content:encoded><![CDATA[<p>on MAL i score strictly on my own love for the show.  if i absolutely love it, it gets a 10.  i don&#8217;t see why someone would argue that the show they love is &#8220;really&#8221; a 6 or a 7 (people do it all the time, I know, but I don&#8217;t see how it&#8217;s appropriate in any way).  A house divided against itself cannot stand &amp; so forth&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
