[Robbie]

[quote author=FarmBoy link=topic=7028.msg53615#msg53615 date=1354035856]
This is one of the problems I had with the execution of the Stanford board at ESPN. They post the articles on both the Stanford and Pac12 sections, but when you click on the articles, they have separate comments for the one linked on the Stanford-specific site vs. the one on the Pac12 site. So you don't get the critical mass to have a fruitful conversation because the commenters get divided.

I never thought about that, but you are right - I will bring this topic up.
[/quote]

Technical answer:

http://espn.go.com/blog/stanford-footbal...-announced

http://espn.go.com/blog/pac12/post/_/id/...-announced

note that the number after /id/ in the URL is different - that means that the author (or an editor) cut and pasted the content before posting - and it is no longer considered the same item in our content management system - so there is no way for the comment system to match up the items, and therefore the comments will be non-connected.

Not saying that this is a good answer (you should not use a technical justification for failing to satisfy a user need - basic design principle) - but it does explain why I do not expect to see it fixed easily.

[Robbie]

[quote author=FarmBoy link=topic=7028.msg53615#msg53615 date=1354035856]
This is one of the problems I had with the execution of the Stanford board at ESPN. They post the articles on both the Stanford and Pac12 sections, but when you click on the articles, they have separate comments for the one linked on the Stanford-specific site vs. the one on the Pac12 site. So you don't get the critical mass to have a fruitful conversation because the commenters get divided.

I never thought about that, but you are right - I will bring this topic up.
[/quote]

Technical answer:

http://espn.go.com/blog/stanford-footbal...-announced

http://espn.go.com/blog/pac12/post/_/id/...-announced

note that the number after /id/ in the URL is different - that means that the author (or an editor) cut and pasted the content before posting - and it is no longer considered the same item in our content management system - so there is no way for the comment system to match up the items, and therefore the comments will be non-connected.

Not saying that this is a good answer (you should not use a technical justification for failing to satisfy a user need - basic design principle) - but it does explain why I do not expect to see it fixed easily.