# Stream of all latest replies: Would it be useful?

**URL:** https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851
**Category:** Feature
**Created:** [8월 7, 2015, 2:43오전 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851 "2015-08-07T02:43:44Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![jspautsch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jspautsch/32/62603_2.png) [@jspautsch](https://meta.discourse.org/u/jspautsch)
#### Post date: [8월 7, 2015, 2:43오전 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/1 "2015-08-07T02:43:44Z")

</div>

I run a fairly small Discourse community and I love it, great features for keeping tabs on conversations you’re interested in and discovering new content.

Something I’ve found myself wanting, however, is a better way of reading up on all the latest _replies_ across a myriad of topics. As someone who’s active and invested in the community, I find myself wanting to check out most every reply, erring on the side of “this could be interesting” instead of not. Problem is, this involves a lot of clicking in and out of multiple threads, many times just to view a single reply that I then quickly scan and determine whether or not it’s interesting to me. Or, I have a strong interest in a specific category, and want to read up on anything posted in that category.

One idea I had to solve this was to somehow display a list of ALL the latest replies to ANY thread, either across multiple categories or in a single category, and then of course the list would live-update and allow you to reply directly from that page. Like a continuous “stream of consciousness” that I can read and reply to without having to click through different topics repeatedly.

Just going off the basic concept, what are your guys thoughts on a feature like this? Does it sound useful, or is it impractical? Does it actually solve a user need? Would more than a handful of people actually use it? What kind of community would be interested in something like this? Is it within the scope of Discourse?

If it would be useful, how would it be implemented? Would it an optional feature admins could enable? A plugin? Would it be placed in the top bar, e.g. next to “latest”, and take you to a new page, or a sidebar like in Facebook that’s always on and filters to the category you’re currently viewing?

I can throw together some mockups if people need more of a visual idea of what I’m talking about.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [8월 7, 2015, 2:45오전 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/2 "2015-08-07T02:45:56Z")

</div>

I have thought about it before, but I feel the use case is narrow. Someone who reads every post, or a moderator, or the site is super low volume. You would lose some (all?) topic context as well, with a stream of the latest replies showing in topic like layout…

---

<div class="post-metadata">

### Author: ![jspautsch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jspautsch/32/62603_2.png) [@jspautsch](https://meta.discourse.org/u/jspautsch)
#### Post date: [8월 7, 2015, 2:58오전 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/3 "2015-08-07T02:58:24Z")

</div>

What if it’s only for tracked/bookmarked/watched topics?

Yeah there’d have to be some kind of styling/extra indicators to make sure the original topic, category, etc are properly represented.

---

<div class="post-metadata">

### Author: ![jspautsch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jspautsch/32/62603_2.png) [@jspautsch](https://meta.discourse.org/u/jspautsch)
#### Post date: [8월 7, 2015, 3:04오전 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/4 "2015-08-07T03:04:44Z")

</div>

The best argument _against_ it that I can think of is that it potentially breaks Discourse’s entire model, turning it into a glorified chat/shoutbox/social network app with lots of tagging and categorization features, which seems undesirable. Keeping discussion focused around topics seems like the whole point, so creating a view that breaks the topic-based flow of information might be a bad idea.

If that made any sense.

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [8월 7, 2015, 3:56오전 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/5 "2015-08-07T03:56:37Z")

</div>

Check out `/posts.json` . There’s no UI, because it’s more useful for consumption by programs than by humans…

---

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [8월 7, 2015, 4:24오전 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/6 "2015-08-07T04:24:51Z")

</div>

> [@riking](#):
>
> Check out /posts.json

I just tried here. The returned JSON had 46 posts.  
Seems that should be enough.

But I’m thinking this would be better as a plugin (or maybe an app?) than a feature

---

<div class="post-metadata">

### Author: ![jspautsch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jspautsch/32/62603_2.png) [@jspautsch](https://meta.discourse.org/u/jspautsch)
#### Post date: [8월 7, 2015, 11:49오전 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/7 "2015-08-07T11:49:24Z")

</div>

> [@Mittineague](#):
>
> But I’m thinking this would be better as a plugin (or maybe an app?) than a feature

My thoughts as well, given the narrow use case.

Maybe I’ll brush up on Ruby and give it a shot.

---

<div class="post-metadata">

### Author: ![RCheesley](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rcheesley/32/455409_2.png) [@RCheesley](https://meta.discourse.org/u/RCheesley)
#### Post date: [5월 8, 2018, 7:30오후 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/8 "2018-05-08T19:30:55Z")

</div>

Just wondering if @jspautsch or anybody worked on this in the end?

I’d like to be able to offer an option of a stream-based layout in addition to the regular layouts for those who prefer to consume information in this way (ala Facebook, LinkedIn etc). Have tried searching but not found anything related to this topic hence re-opening an old one.

Guessing it would be a case of pulling in the posts.json and formatting it but no idea where to start with that!

Ruth

---

<div class="post-metadata">

### Author: ![Plastic\_Hub](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/plastic_hub/32/168220_2.png) [@Plastic\_Hub](https://meta.discourse.org/u/Plastic_Hub)
#### Post date: [2월 3, 2020, 10:38오후 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/9 "2020-02-03T22:38:01Z")

</div>

안녕하세요,  
저도 이 기능이 있으면 좋겠습니다. 많은 사용자들이 이런 방식으로 주제와 상호작용하고 있어서, 이 방법으로 동향을 파악하는 것이 훨씬 쉽거든요(그렇지 않다면 어떻게 해야 할까요?).

초보자인데, 이 기능을 갖추려면 어떤 과정이 필요할까요? `posts.json` 파일은 볼 수 있는데, 필터링하는 것이 얼마나 어려운지 잘 모르겠습니다. 이걸 구현하려면 디스코스를 해킹해야 하는 건가요, 아니면 플러그인으로 처리되는 건가요?

감사합니다.  
g

---

<div class="post-metadata">

### Author: ![Mevo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mevo/32/187732_2.png) [@Mevo](https://meta.discourse.org/u/Mevo)
#### Post date: [2월 3, 2020, 11:05오후 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/10 "2020-02-03T23:05:13Z")

</div>

간단한 해결책 중 하나는 특정 날짜 이후의 게시글을 검색 기능으로 리다이렉트하는 것입니다. 예를 들어, 오늘에서 2주 전(또는 “내일 이전”)을 기준으로 하되, 결과를 최신 게시글 순으로 정렬하면 됩니다. 이렇게 하면 이 스레드에서 논의되는 내용을 확인할 수 있지만, 발췌만 표시됩니다. 이를 통해 모든 메시지의 맥락을 파악할 수 있으며, 관심 있는 항목을 클릭하면 해당 스레드로 이동할 수 있습니다.

아래 두 가지 기능이 있으면 좋겠습니다:

1. “게시글 순 정렬” 파라미터만 있는 완전히 빈 검색으로 리다이렉트할 수 있는 기능.
2. 검색 기능에서 발췌 대신 메시지를 전체로 표시할 수 있는 옵션(URL을 통해 트리거 가능). 이렇게 하면 여기서 논의되는 것과 거의 동일한 결과를 얻을 수 있습니다.

**예시** (2020년 1월 16일 이후의 게시글을 최신순으로 정렬):  
[https://meta.discourse.org/search?q=after%3A2020-01-16%20order%3Alatest](https://meta.discourse.org/search?q=after%3A2020-01-16%20order%3Alatest)  
[질문: 왜 메타는 원박스(onebox)를 하지 않나요?]

---

<div class="post-metadata">

### Author: ![Plastic\_Hub](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/plastic_hub/32/168220_2.png) [@Plastic\_Hub](https://meta.discourse.org/u/Plastic_Hub)
#### Post date: [2월 3, 2020, 11:08오후 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/11 "2020-02-03T23:08:28Z")

</div>

@Mevo : 정말 감사합니다. 검색 기능이 얼마나 강력한지 이제야 알았어요 🙂

---

<div class="post-metadata">

### Author: ![Plastic\_Hub](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/plastic_hub/32/168220_2.png) [@Plastic\_Hub](https://meta.discourse.org/u/Plastic_Hub)
#### Post date: [4월 5, 2020, 5:49오후 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/12 "2020-04-05T17:49:03Z")

</div>

안녕하세요,  
검색 해킹은 실제로 유용하지만, 더 깔끔하게 처리하는 방법을 선호합니다. 누군가가 이를 컴포넌트로 구현하는 방법을 1단계부터 5단계까지 간단하게 알려주실 수 있을까요? 가능하면요. 이 방법을 사용하여 최신 ‘사진’ 모듈을 만들 수도 있습니다.  
많은 도움 부탁드립니다.  
g

---

<div class="post-metadata">

### Author: ![Paracelsus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/paracelsus/32/164912_2.png) [@Paracelsus](https://meta.discourse.org/u/Paracelsus)
#### Post date: [8월 5, 2020, 1:45오후 UTC](https://meta.discourse.org/t/stream-of-all-latest-replies-would-it-be-useful/31851/13 "2020-08-05T13:45:21Z")

</div>

안녕하세요, 이 기능은 저도 이전에 궁금해했던 흥미로운 기능입니다.

> **[Uipath](https://forum.uipath.com/g/uipath/activity/posts)**
>
> Uipath

을 우연히 발견했는데, 우리가 원하는 것과 거의 비슷하지만 특정 그룹 하나만 보여주는 대신, 이 활동 탭에서 모든 그룹을 동시에 볼 수 있으면 좋겠습니다. 또한 최신 페이지와 같이 실시간으로 업데이트되기를 바랍니다.
