토픽 중간에 모바일에서 시청 상태를 변경할 수 없습니다

You used to be able to change watching status from the timeline view on mobile, but that is no longer possible. As far as I can tell, there’s now no way to change watching status without going to the bottom of the topic, and therefore marking the whole topic as read.

2개의 좋아요

Any thoughts on this issue?

1개의 좋아요

I don’t remember we could do it from the timeline in mobile view, but this is not the kind of thing I remember.

But indeed, changing the watching status from the timeline on mobile seems right.

1개의 좋아요

확인해 드리는 동안 인내심을 가져 주셔서 감사합니다. 모바일에서 토픽 타임라인에 의도적인 변경을 가했습니다. 이는 공간을 절약하고, 내비게이션과 전반적인 사용자 경험에 부정적인 영향을 줄 수 있는 시각적 혼란을 줄이기 위한 조치입니다. 현재 이 변경 사항은 되돌리지 않을 예정입니다.

권장되는 우회 방법은 알림 수준을 변경한 후 토픽이 읽지 않은 상태로 유지되도록 확인해야 할 때 읽지 않음으로 표시 버튼을 사용하여 토픽을 읽지 않은 상태로 되돌리는 것입니다. 해당 버튼이 아직 표시되지 않는 경우, 인터페이스 설정에서 토픽을 읽지 않음으로 표시 설정을 활성화할 수 있습니다.

원하지 않는 소식이라는 점에 공감합니다. 더 많은 피드백을 공유해 주시려면 Contribute > Feature 토픽을 열어 사용 사례를 더 자세히 설명해 주시기 바랍니다. 이는 기존 솔루션을 발견하거나 향후 개선 사항을 계획하는 데 도움이 될 수 있습니다.

3개의 좋아요

This topic was automatically closed after 2 days. New replies are no longer allowed.

At my request, this topic was reopened and recategorized as a feature. I felt it was easier than creating a new topic for the same conversation.


Unfortunately, this does not really work all that well as a workaround. The problem with this workaround is that Mark unread only does so for the last post. Any previous post that is still marked as read. Let me give an example of when this has been a problem.

A community I participate in often runs book clubs with weekly assignments, using a new topic for each week. If I get behind in the reading, I still want to track or watch each week’s topic so I don’t lose track of them. Let’s say I catch up in the book club after a few weeks and I’m now ready to read one of the topics. Since I only just finished the week’s reading, I really want to read the topic from start to end. But if there are 15 posts, it’s possible that 10 of them are already marked as read from when I set the topic to tracking/watching. Obviously I can scroll up to the top manually, but if I only have time to read the first 3 posts, it won’t remember that I’m up to post 4 since it still thinks I’m up to post 11.

I think there are some options to alleviate this problem besides reverting the previous changes.

  1. Mark unread could also reset/clear the latest post read, effectively marking the entire topic as unread, not just the last post.
  2. Mark unread could be added as an option in the context menu for individual posts, giving users the ability to choose how far back in the topic they want to mark as unread. For my example above, this would allow me to mark the first post as unread, effectively making the entire topic unread.
  3. Give the option to change the watching status without opening a topic. This might be a bit tight on mobile, but perhaps there’s enough room for a ... context menu button next to each topic for additional options. (Honestly, on the New topics page I’ve wanted that for dismissing individual topics instead of all new topics anyway, so I think this could be generally useful.)

Hopefully at least one of these options can solve this problem.

Whoa! This is quite a regression for us.

We want people to visit topics via their mobiles at an in person event via QR codes on each table and tick ‘Watching’ if they want to remain connected to the ongoing discussion.

This is not going to work with the current minimal mobile UI - that scroll to the bottom on mobile makes this unfeasible in most cases.

My thoughts for workarounds:

  1. Keep the Topics super short / locked down for the time of the interaction
  2. Lower default_other_auto_track_topics_after_msecs to immediate for the event
    • this will likely result in a lot of false hits for other users or if they browse though
    • unfortunately, this isn’t per category!
  3. Run a script at the end of the day to force tracking/watching as appropriate for those who have visited (or maybe liked) the Topic

Sorry @seanblue - these won’t help your use case.
The simplest workaround for you is to use a bigger device!

1개의 좋아요