We have a Discourse instance (forum.ohlasy.info) and a separate website (ohlasy.info) that displays a list of latest topics pulled from /latest.json. Users can click on the topic name to get to the discussion. The question is, where does the link lead to? I have tried /t/:id and /t/:id/latest. The first link always leads to the beginning of the topic, the second one leads to the last post. Is there an option to go to the first unread post for the current user (if logged in) and to the beginning of the topic otherwise?
1개의 좋아요
Sorry, I misunderstood the question! There is no single magic link that’ll take you to two different locations in the topic.
There is, however:
-
a link that will take you to the
bottom of the topic consistently
https://meta.discourse.org/t/slug/106476/last -
a link that will take you to the
top of the topic consistently
https://meta.discourse.org/t/slug/106476/1
2개의 좋아요
Thank you! Neither of these options work well for us, though. Linking to the first post doesn’t make much sense for logged-in users who have probably read most of the topic already. And linking to the latest post doesn’t work well for… almost anybody. Those who have seen a part of the topic would lose track and those who didn’t would be thrown in the middle of a discussion, having to scroll to the top.
Would you consider adding / accepting a feature that would allow linking to the latest post read by the logged-in user or to the first post if the user is not logged in?
Or do you have other suggestions how to make this “latest posts on our discussion forum” website box work well?
I am open to adding an /unread postfix like we have for /last, feel free to send a PR
5개의 좋아요
Note, there is a subtle difference between these two:
- latest read post
- first unread post
See also:
5개의 좋아요
Did this ever get added Sam? Going to t/id/unread doesn’t work - but perhaps a different word is being used?
If it hasn’t been added this would be a really nice feature to have 
Nope, not added yet.
I too would love a “go to first unread” keyboard shortcut. It is a nice power user feature that allows you to regain control if you are dumped into a topic you have already started tracking far into the topic.
Concrete example:
- I start tracking: Events Plugin 📅
- I read up to post 100
- I click a link somewhere by mistake to Events Plugin 📅 - #428 by oca
- I missed 100-428 now and have no easy way to get back to 100
Ability to jump to first unread post has not progressed over the years, same goes for: Remembered Topic location should be "First Unread" post instead of "Last Read" post
I think as it stands today, @codinghorror is happy to add a keyboard shortcut here for first unread. But we have not gotten to it yet, nor scheduled it.
I guess it is such an edge case to have these giant topics like @Wingtip tends to have AND have someone actively lobby for it.
The other problem with this power-user feature is that it is very hard to explain per: Will disable_jump_reply make a return? - #10 by codinghorror
5개의 좋아요
I’m glad you would like to see it too Sam and I hope we’ll see it soon
Another place where I think it would be incredibly handy is when viewing a post via the flag system - it would be nice that it either ignores you own personal position, or, whenever you click through to a specific post for and Topic it asks you on leaving whether you would like to retain your original position, or set the most recent portion. If it tells you which post you had previously see (and maybe all you to jump to it) along with the post you later came in to (perhaps via review queue or post link) I think that would be super useful 
The flag system is definitely a problem for me atm, as I am avoiding carrying out those duties as I don’t want to lose my own position in those topics. Pretty sure others probably feel similarly?
2개의 좋아요
Just wondering if any progress was made on this after?
I am considering moving a few more forums over to Discourse (in conjunction with our custom homepage system) but one of the biggest criticisms we had on previous installs is that those links (on our homepage and custom pages) always went to the first post and people found it frustrating having to scroll through the thread again.
I think what’s true today is that the link to a thread will go to the last read post if there are unreads, or to the top of the thread if there are not - or if the account is not logged in. (Please correct me if I’m wrong)
If you mean links from within DC then yes, but we are referring to links we can use outside of Discourse (such as on a custom homepage or parent site).
정말 절실히 필요한 기능이라고 생각합니다. 하지만 저는 모바일에서 사이트를 많이 사용하니까 단축키만으로는 부족합니다. 페이지 번호 옆에 버튼을 두는 건 어떨까요?
3개의 좋아요
최근에 이런 느낌을 갖게 된 경험이 있으신가요? 실제 사례를 모아두는 것은 항상 도움이 됩니다.
3개의 좋아요
나름대로의 일상적인 경험입니다.
저는 분주한 포럼을 운영하는데, 모든 글을 읽고 싶지만 항상 시간이 부족합니다.
그러다 @멘션이나 댓글을 받으면 알림이 오죠. 그런데 그 알림을 클릭하면 목록에서 훨씬 아래로 스크롤이 되어 많은 글을 놓치게 됩니다. 마지막으로 읽은 위치까지 다시 스크롤을 올려 찾는 것은 정말 악몽과도 같습니다.
그래서 알림 영역은 거의 사용하지 않게 되죠. 그 결과 며칠 뒤에야 알림을 확인하게 되고, 때로는 중요한 내용도 놓칩니다.
예를 들어 'Example Thread’라는 제목의 스레드에서 @멘션을 받았는데, 목록에서 그 스레드가 잘 보이지 않는다면 검색을 통해서도 찾을 수 없습니다. 검색을 하면 스레드 맨 위로 이동하게 되어 다시 맨 아래까지 스크롤을 내려가야 하니까요.
알림이 있는 스레드에서 마지막으로 읽은 위치로 바로 이동할 수 있는 쉬운 방법이 전혀 없습니다.
제 입장에서는 정말 난감한 상황입니다!
4개의 좋아요
저도 바로 떠오르는 것이 바로 이거예요 – 타임라인에 이미 있는 “뒤로” 버튼처럼, 다른 방향으로 스크롤할 때 나타나는 버튼인데, 대신 처음으로 읽지 않은 첫 번째 게시물로 이동하는 버튼이요.
이것이 표시될지 말지는 사용자 설정으로 만들 수 있을 것 같아요.
과거에는 이런 기능이 필요하다고 느낀 적이 있지만, 최근에는 개인적으로 그 필요성을 크게 느끼지 못해서, 이런 요청이 왜 나오는지를 이해하는 데 스토리가 도움이 되네요. 감사합니다.
5개의 좋아요