# Facebook-like Feed? **URL:** \ **Category:** Product Support\ **Created:** [May 8, 2019, 6:58pm UTC](https://meta.discourse.org/t/facebook-like-feed/117204 "2019-05-08T18:58:21Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [June 8, 2022, 10:03pm UTC](https://meta.discourse.org/t/facebook-like-feed/117204/10 "2022-06-08T22:03:58Z")
> [@oshyan](#): > > I think it’s a mistake to simply write-off an entirely, extremely popular method of interaction just because it _tends_ to have some downsides. There is no “simple write-off” here… it is more like a bunch of complex tradeoffs that make this something I am not too keen to explore. We already have this… [https://meta.discourse.org/g/trust\_level\_0/activity/posts](https://meta.discourse.org/g/trust_level_0/activity/posts) So I guess people are asking … “please sir, can I have ⏫ but on steroids please?” 1. Just kill the topic page in this mode … we don’t need no topic page … “topic page+list” all-in-one is where it is at. A single page for “topic+topic list” is what I want. 2. Effectively let me interact with all these random topics from 1 interface, composer needs to work on topic list. 3. Use some algorithm (either I control or admin controls) vs simply ordering on latest 4. Yeah… let’s keep “unread” / “new” / “read tracking” all working as well… cause we need it. 5. I am mixing topics and posts in 1 interface, you got to come up with some wonderful way of collapsing content… so please do that as well. There are months … maybe years in getting an interface like this going, it is not something that is easy to refine or design. We have tons of other significantly higher priority exploratory work I would look at .. exploring, prior to this giant can of snakes. --- _[View the full topic](https://meta.discourse.org/t/facebook-like-feed/117204)._