By bringing an article to the front page, either with the old comment thread or with a fresh one (plus a reference to the old one), it becomes something that the community is doing.
The main problem with your proposal is that it unnecessarily forces everyone who reads the front page to participate in your project. (Eliezer wrote over 600 posts on Overcoming Bias. If they were all reposted, that would drastically change the character of the front page.)
If on the other hand, the reposts were to appear at a URL that is not currently being used, /r/sequences/ say, then each person could decide whether to participate in your project or to continue to use LW the way they are using it now.
Parenthetically, if I were to write software to support your project, I would create an RSS feed of (new) comments on the (old) posts in the sequences. That way, someone who is reading a post in the sequences knows that if they make a comment (e.g., to ask a question), it will probably be noticed. In fact, the probability that it will be noticed is high even now, but would rise if there were a way for readers to watch for the comment without needing to scan the firehose that is http://lesswrong.com/comments/.
Note that such an RSS feed could be created without modification of the software behind lesswrong.com (since the necessary information is already in http://lesswrong.com/comments/.rss and the new RSS feed can be published at a domain other than lesswrong.com) which is probably a good thing given the difficulty some here have had recently in getting the attention of a someone with the authority to pull changes into the software behind lesswrong.com.
The main problem with your proposal is that it unnecessarily forces everyone who reads the front page to participate in your project. (Eliezer wrote over 600 posts on Overcoming Bias. If they were all reposted, that would drastically change the character of the front page.)
If on the other hand, the reposts were to appear at a URL that is not currently being used, /r/sequences/ say, then each person could decide whether to participate in your project or to continue to use LW the way they are using it now.
Parenthetically, if I were to write software to support your project, I would create an RSS feed of (new) comments on the (old) posts in the sequences. That way, someone who is reading a post in the sequences knows that if they make a comment (e.g., to ask a question), it will probably be noticed. In fact, the probability that it will be noticed is high even now, but would rise if there were a way for readers to watch for the comment without needing to scan the firehose that is http://lesswrong.com/comments/.
Note that such an RSS feed could be created without modification of the software behind lesswrong.com (since the necessary information is already in http://lesswrong.com/comments/.rss and the new RSS feed can be published at a domain other than lesswrong.com) which is probably a good thing given the difficulty some here have had recently in getting the attention of a someone with the authority to pull changes into the software behind lesswrong.com.