<?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"
	>
<channel>
	<title>Comments on: Questions for JapanSoc Users #1</title>
	<atom:link href="http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/</link>
	<description>Nick Ramsay blogging from Gifu, Japan.</description>
	<pubDate>Sun, 23 Nov 2008 09:19:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: ChrisG</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3470</link>
		<dc:creator>ChrisG</dc:creator>
		<pubDate>Tue, 04 Mar 2008 08:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3470</guid>
		<description>I agree about the link. I think it is better for users if it goes directly to the article. I click the comments link to see the comments or read more of the description.</description>
		<content:encoded><![CDATA[<p>I agree about the link. I think it is better for users if it goes directly to the article. I click the comments link to see the comments or read more of the description.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Ramsay</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3469</link>
		<dc:creator>Nick Ramsay</dc:creator>
		<pubDate>Tue, 04 Mar 2008 04:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3469</guid>
		<description>Thanks for the feedback, Brad. I've made some changes to the FAQ (which is already linked to from every page) to try and make things clearer:

&lt;a href="http://www.japansoc.com/about/en#readerssubmit" rel="nofollow"&gt;Question 8&lt;/a&gt; on the FAQ, "How can I get my readers to submit my articles?", has the code for Blogger, Wordpress, Movable Type, Typepad, and I've just added Javascript, too. There's now a link to the &lt;a href="http://www.longcountdown.com/2008/02/23/japansoc-video-tutorial-social-bookmarking-button/" rel="nofollow"&gt;video tutorial for Wordpress&lt;/a&gt; I made, too. I've also added a link to &lt;a href="http://tips-for-new-bloggers.blogspot.com/2007/08/social-bookmarking-links-in-blogger.html" rel="nofollow"&gt;this article&lt;/a&gt; which should helper Blogger users like yourself. Beyond that, I don't know what more I can do. 

I hear what you're saying about clicking the title and going to the JapanSoc page instead of the actual blog post, but I have to disagree. I think linking the title to the JapanSoc story page is an extra step between the homepage and reading the submitted articles. Why frustrate readers by making them go through that extra step? If they want to read comments or discuss the article they can click the Discuss/Comment link (just like on Digg.com). That's just my opinion and I'd be interested in hearing what other users think.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback, Brad. I&#8217;ve made some changes to the FAQ (which is already linked to from every page) to try and make things clearer:</p>
<p><a href="http://www.japansoc.com/about/en#readerssubmit" rel="nofollow">Question 8</a> on the FAQ, &#8220;How can I get my readers to submit my articles?&#8221;, has the code for Blogger, Wordpress, Movable Type, Typepad, and I&#8217;ve just added Javascript, too. There&#8217;s now a link to the <a href="http://www.longcountdown.com/2008/02/23/japansoc-video-tutorial-social-bookmarking-button/" rel="nofollow">video tutorial for Wordpress</a> I made, too. I&#8217;ve also added a link to <a href="http://tips-for-new-bloggers.blogspot.com/2007/08/social-bookmarking-links-in-blogger.html" rel="nofollow">this article</a> which should helper Blogger users like yourself. Beyond that, I don&#8217;t know what more I can do. </p>
<p>I hear what you&#8217;re saying about clicking the title and going to the JapanSoc page instead of the actual blog post, but I have to disagree. I think linking the title to the JapanSoc story page is an extra step between the homepage and reading the submitted articles. Why frustrate readers by making them go through that extra step? If they want to read comments or discuss the article they can click the Discuss/Comment link (just like on Digg.com). That&#8217;s just my opinion and I&#8217;d be interested in hearing what other users think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3466</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Mon, 03 Mar 2008 23:01:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3466</guid>
		<description>I'd like clearer info on how to get visitors to my blog to "Soc" my articles. I can't find info on how to do this. How do I add a text link or button? A link on how to do this should be on EVERY page of JapanSoc if you want the site to take off.

Also when viewing the list of articles/posts, clicking on the post title should take the user to the JapanSoc page about the article not the original post. Instead make it take you to the same page that the "Read More" link takes the user. 

Sometimes I'm curious on the comments my posts get but I keep getting sent to my post, not the JapanSoc page. (I know that sounds confusing).

This would also keep users on JapanSoc longer.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like clearer info on how to get visitors to my blog to &#8220;Soc&#8221; my articles. I can&#8217;t find info on how to do this. How do I add a text link or button? A link on how to do this should be on EVERY page of JapanSoc if you want the site to take off.</p>
<p>Also when viewing the list of articles/posts, clicking on the post title should take the user to the JapanSoc page about the article not the original post. Instead make it take you to the same page that the &#8220;Read More&#8221; link takes the user. </p>
<p>Sometimes I&#8217;m curious on the comments my posts get but I keep getting sent to my post, not the JapanSoc page. (I know that sounds confusing).</p>
<p>This would also keep users on JapanSoc longer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Y-N</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3196</link>
		<dc:creator>Ken Y-N</dc:creator>
		<pubDate>Fri, 18 Jan 2008 00:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3196</guid>
		<description>Thanks for the tooltip! I'd also love to see a thumbnail of the poster beside each comment...</description>
		<content:encoded><![CDATA[<p>Thanks for the tooltip! I&#8217;d also love to see a thumbnail of the poster beside each comment&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris B</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3193</link>
		<dc:creator>Chris B</dc:creator>
		<pubDate>Thu, 17 Jan 2008 13:58:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3193</guid>
		<description>The font is cool!
Cliched?? 
You mean Bamboo font has been used so much it has lost it's meaning?

Bamboo font FTW!!!</description>
		<content:encoded><![CDATA[<p>The font is cool!<br />
Cliched??<br />
You mean Bamboo font has been used so much it has lost it&#8217;s meaning?</p>
<p>Bamboo font FTW!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tori</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3192</link>
		<dc:creator>Tori</dc:creator>
		<pubDate>Thu, 17 Jan 2008 07:05:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3192</guid>
		<description>@Deas,

Do you mean that you don't think there should be any grammar/kanji/Japan-tips? Or are you just saying there should be a balance?

I think categorisation may be the hardest part of running this type of site. The niches are nearly endless (and everyone has there own particular interests) but put too many categories and the site will probably suffer.</description>
		<content:encoded><![CDATA[<p>@Deas,</p>
<p>Do you mean that you don&#8217;t think there should be any grammar/kanji/Japan-tips? Or are you just saying there should be a balance?</p>
<p>I think categorisation may be the hardest part of running this type of site. The niches are nearly endless (and everyone has there own particular interests) but put too many categories and the site will probably suffer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Ramsay</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3187</link>
		<dc:creator>Nick Ramsay</dc:creator>
		<pubDate>Wed, 16 Jan 2008 03:58:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3187</guid>
		<description>You don't like that font? You'll have to take it up with my wife because she chose it! ;)

I agree about the Latest Comments' lack of tool tip / readable url. I'll look into it. Thanks again.

&lt;strong&gt;UPDATE: I was able to hack it myself and add the story title as a tooltip for each comment.&lt;/strong&gt;</description>
		<content:encoded><![CDATA[<p>You don&#8217;t like that font? You&#8217;ll have to take it up with my wife because she chose it! <img src='http://www.longcountdown.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>I agree about the Latest Comments&#8217; lack of tool tip / readable url. I&#8217;ll look into it. Thanks again.</p>
<p><strong>UPDATE: I was able to hack it myself and add the story title as a tooltip for each comment.</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Y-N</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3185</link>
		<dc:creator>Ken Y-N</dc:creator>
		<pubDate>Wed, 16 Jan 2008 00:30:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3185</guid>
		<description>A couple of further suggestions:

The bamboo font "Japan Soc" is a bit cliched.

In the Latest Comments section, it would be nice to see from which stories and/or which users the comments are coming from - at the moment the URL is just a number, so I can't even see from the tooltip where it goes.</description>
		<content:encoded><![CDATA[<p>A couple of further suggestions:</p>
<p>The bamboo font &#8220;Japan Soc&#8221; is a bit cliched.</p>
<p>In the Latest Comments section, it would be nice to see from which stories and/or which users the comments are coming from - at the moment the URL is just a number, so I can&#8217;t even see from the tooltip where it goes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Ramsay</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3181</link>
		<dc:creator>Nick Ramsay</dc:creator>
		<pubDate>Tue, 15 Jan 2008 14:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3181</guid>
		<description>Thanks Deas. I've put your name on my review list, and I'll make that the last one for now. 

There isn't actually a duplicate content issue at all. If a url has already been submitted, it can't be submitted again. The issue was that it's hard to tell if a particular url has already been submitted unless you actually try to submit it yourself, in which case you'll get a "Duplicate Content" message if it already exists on JapanSoc.

I know what you're saying about "junk" stuff, but some people love YouTube clips of Japanese game shows, others are mad about Gundam, and some just want to learn the language. JapanSoc will hopefully offer something to please everyone, but all we can do is vote for what we like and hope others agree with us!</description>
		<content:encoded><![CDATA[<p>Thanks Deas. I&#8217;ve put your name on my review list, and I&#8217;ll make that the last one for now. </p>
<p>There isn&#8217;t actually a duplicate content issue at all. If a url has already been submitted, it can&#8217;t be submitted again. The issue was that it&#8217;s hard to tell if a particular url has already been submitted unless you actually try to submit it yourself, in which case you&#8217;ll get a &#8220;Duplicate Content&#8221; message if it already exists on JapanSoc.</p>
<p>I know what you&#8217;re saying about &#8220;junk&#8221; stuff, but some people love YouTube clips of Japanese game shows, others are mad about Gundam, and some just want to learn the language. JapanSoc will hopefully offer something to please everyone, but all we can do is vote for what we like and hope others agree with us!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deas</title>
		<link>http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3179</link>
		<dc:creator>Deas</dc:creator>
		<pubDate>Tue, 15 Jan 2008 06:13:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.longcountdown.com/2008/01/11/questions-for-japansoc-users-1/#comment-3179</guid>
		<description>Hey there - completed the steps above. Thanks for the offer.

My only worry about  JapanSoc is that it will go the way that so many social sites (Digg, etc.) / Japan-related sites do and end up with a group of adolescent "contributers" who have never been to nor intend to go to Japan, and whose interests are...well...adolescent, for lack of a better word. You know what I mean? The offensive content decision you settled on seems fine for now, though. I just remember someone saying that they hoped that the site didn't become a grammar tips / kanji memorization techniques / how-to _(mundane thing here)_ in Japan guide in a comment thread earlier. I agree. There are other, weirder places it could go, too. I suppose the best way to fight this would be to encourage aggressive burial of junk stuff. And all I can really ask for is my own vote, right? :-)

Is it wrong that I may bury much more than I soc for a while? Ha ha - not to be a killjoy or anything. I just have an idealistic view for what your site could be and really hope it gets there. It's got promise. Ha ha.

Anyway, regarding the above points, sounds like you've got things covered (excluding a way to help avoid duplicate content). I'll chime in again on the next go-round. Thanks again!</description>
		<content:encoded><![CDATA[<p>Hey there - completed the steps above. Thanks for the offer.</p>
<p>My only worry about  JapanSoc is that it will go the way that so many social sites (Digg, etc.) / Japan-related sites do and end up with a group of adolescent &#8220;contributers&#8221; who have never been to nor intend to go to Japan, and whose interests are&#8230;well&#8230;adolescent, for lack of a better word. You know what I mean? The offensive content decision you settled on seems fine for now, though. I just remember someone saying that they hoped that the site didn&#8217;t become a grammar tips / kanji memorization techniques / how-to _(mundane thing here)_ in Japan guide in a comment thread earlier. I agree. There are other, weirder places it could go, too. I suppose the best way to fight this would be to encourage aggressive burial of junk stuff. And all I can really ask for is my own vote, right? <img src='http://www.longcountdown.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Is it wrong that I may bury much more than I soc for a while? Ha ha - not to be a killjoy or anything. I just have an idealistic view for what your site could be and really hope it gets there. It&#8217;s got promise. Ha ha.</p>
<p>Anyway, regarding the above points, sounds like you&#8217;ve got things covered (excluding a way to help avoid duplicate content). I&#8217;ll chime in again on the next go-round. Thanks again!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
