Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
It's "status by design". I made the very same remarks when this feature was released, here: https://meta.codidact.com/posts/282342/282346#answer-282346. Responses from the dev team were: ArtOfC...
Answer
#3: Post edited
by
Lundin
·
2022-05-18T09:01:31Z (almost 2 years ago)
- It's "status by design". I made the very same remarks when this feature was released, here: https://meta.codidact.com/posts/282342/282346#answer-282346.
- Responses from the dev team were:
- > ArtOfCode wrote 11 months ago:
- >
- > Part of the intent of this change is to create slightly more friction to commenting. We've seen both here and on SE that comments being easy to leave makes people less likely to think about what they're writing. Opening a new page for a full comment thread is just that little bit of friction that might change that; we'll see how it goes. (There are a few technical challenges to inlining full threads, too, but it can be done if we try this and it really doesn't work out.)
- > Monica Cellio wrote 11 months ago:
- >
- > Going to a new page does remove ready access to context (like if you need to consult the post the thread is attached to). It's a link away, but I think that's one issue behind the requests for inlining the thread. Maybe the answer is inlining or maybe the answer is some other change to the thread page.
- My feedback was overall positively received (+8 score), yet the feature has remained as it is.
We've been using it for almost a year now and my opinion still stands: loading a new page is cumbersome, unintuitive and confusing. Worst of all, you have to view the post and its related comments in separate windows, switching back and forth between two separate tabs - which is plain bad UI. I find no evidence that it makes people think more carefully before posting a comment.
- It's "status by design". I made the very same remarks when this feature was released, here: https://meta.codidact.com/posts/282342/282346#answer-282346.
- Responses from the dev team were:
- > ArtOfCode wrote 11 months ago:
- >
- > Part of the intent of this change is to create slightly more friction to commenting. We've seen both here and on SE that comments being easy to leave makes people less likely to think about what they're writing. Opening a new page for a full comment thread is just that little bit of friction that might change that; we'll see how it goes. (There are a few technical challenges to inlining full threads, too, but it can be done if we try this and it really doesn't work out.)
- > Monica Cellio wrote 11 months ago:
- >
- > Going to a new page does remove ready access to context (like if you need to consult the post the thread is attached to). It's a link away, but I think that's one issue behind the requests for inlining the thread. Maybe the answer is inlining or maybe the answer is some other change to the thread page.
- My feedback was overall positively received (+8 score), yet the feature has remained as it is.
- We've been using it for almost a year now and my opinion still stands: loading a new page is cumbersome, unintuitive and confusing. Worst of all, you sometimes (upon following a comment notification) have to view the post and its related comments in separate windows, switching back and forth between two separate tabs - which is plain bad UI. I find no evidence that it makes people think more carefully before posting a comment.
#2: Post edited
by
Lundin
·
2022-05-18T09:00:41Z (almost 2 years ago)
- It's "status by design". I made the very same remarks when this feature was released, here: https://meta.codidact.com/posts/282342/282346#answer-282346.
- Responses from the dev team were:
- > ArtOfCode wrote 11 months ago:
- >
- > Part of the intent of this change is to create slightly more friction to commenting. We've seen both here and on SE that comments being easy to leave makes people less likely to think about what they're writing. Opening a new page for a full comment thread is just that little bit of friction that might change that; we'll see how it goes. (There are a few technical challenges to inlining full threads, too, but it can be done if we try this and it really doesn't work out.)
- > Monica Cellio wrote 11 months ago:
- >
- > Going to a new page does remove ready access to context (like if you need to consult the post the thread is attached to). It's a link away, but I think that's one issue behind the requests for inlining the thread. Maybe the answer is inlining or maybe the answer is some other change to the thread page.
- My feedback was overall positively received (+8 score), yet the feature has remained as it is.
We've been using it for almost a year now and my opinion still stands: loading a new page is cumbersome, unintuitive and confusing. I find no evidence that it makes people think more carefully before posting a comment.
- It's "status by design". I made the very same remarks when this feature was released, here: https://meta.codidact.com/posts/282342/282346#answer-282346.
- Responses from the dev team were:
- > ArtOfCode wrote 11 months ago:
- >
- > Part of the intent of this change is to create slightly more friction to commenting. We've seen both here and on SE that comments being easy to leave makes people less likely to think about what they're writing. Opening a new page for a full comment thread is just that little bit of friction that might change that; we'll see how it goes. (There are a few technical challenges to inlining full threads, too, but it can be done if we try this and it really doesn't work out.)
- > Monica Cellio wrote 11 months ago:
- >
- > Going to a new page does remove ready access to context (like if you need to consult the post the thread is attached to). It's a link away, but I think that's one issue behind the requests for inlining the thread. Maybe the answer is inlining or maybe the answer is some other change to the thread page.
- My feedback was overall positively received (+8 score), yet the feature has remained as it is.
- We've been using it for almost a year now and my opinion still stands: loading a new page is cumbersome, unintuitive and confusing. Worst of all, you have to view the post and its related comments in separate windows, switching back and forth between two separate tabs - which is plain bad UI. I find no evidence that it makes people think more carefully before posting a comment.
#1: Initial revision
by
Lundin
·
2022-05-18T08:58:29Z (almost 2 years ago)
It's "status by design". I made the very same remarks when this feature was released, here: https://meta.codidact.com/posts/282342/282346#answer-282346. Responses from the dev team were: > ArtOfCode wrote 11 months ago: > > Part of the intent of this change is to create slightly more friction to commenting. We've seen both here and on SE that comments being easy to leave makes people less likely to think about what they're writing. Opening a new page for a full comment thread is just that little bit of friction that might change that; we'll see how it goes. (There are a few technical challenges to inlining full threads, too, but it can be done if we try this and it really doesn't work out.) > Monica Cellio wrote 11 months ago: > > Going to a new page does remove ready access to context (like if you need to consult the post the thread is attached to). It's a link away, but I think that's one issue behind the requests for inlining the thread. Maybe the answer is inlining or maybe the answer is some other change to the thread page. My feedback was overall positively received (+8 score), yet the feature has remained as it is. We've been using it for almost a year now and my opinion still stands: loading a new page is cumbersome, unintuitive and confusing. I find no evidence that it makes people think more carefully before posting a comment.