Ability to mark any post as unread

Continuing the discussion from How Coinbase Uses Discourse to Educate Customers and Improve SEO:

The interviewee of the referenced blog article states the following dislike:

If a post on a topic can be “unread”, why can’t I mark it unread again after reading it?

and I’d like to talk a bit about that and the workflow that is not possible at the moment.


Concept

In email clients, you can mark any email as “unread”, even in a longer discussion or thread, and return to it later. Most clients allow you to filter or navigate unread emails only, so this workflow is a breeze for when you decide you need to work on something again later, such as prepare a reply.

The same holds true for RSS readers, where you find a post that deserves more attention than what you give currently and you want to save it for later.

In Discourse, however, the concept of marking specific posts as unread is not a thing and unread posts can only occur at the end of a thread that you didn’t scroll into the view yet. Additionally, the algorithm that chooses to automatically mark posts as read can be inaccurate depending on your reading habits (i.e. whether you use mouse scrolling or j/k keys).

Why Not Bookmarks?

I understand that bookmarks are a possible workaround for this situation. But “bookmarks” semantically mean something different in most situations because I only intend to (re-)read the “unread” posts once and not save it for recurring occasions. Thus, one-time bookmarks and long-term bookmarks would get mixed and you’ll have to remember to unbookmark each “unread” post when you access it. They would also not get displayed in the “Unread” front page tab.


Required Changes for Discourse

  • The unread indicator (currently blue dot next to relative post timestamp) needs to be toggleable, which likely requires repositioning and redesign. Also with a keyboard shortcut, suggesting m (already used for topic track state).
  • There needs to be a way to traverse between unread posts within a thread, up and down.

It’s not high priority for me, but it deserves to be discussed imo.

3 „Gefällt mir“

A much higher priority for us is to have a cleaner way of dealing with “reading holes” eg: topics where you read post 1-10, 50 but did not read 11-49. If what you are describing would likely create reading holes and not behave in a very intuitive way cause you could only do it effectively for the last post in a topic.

2 „Gefällt mir“

Yes, it would (or rather should) be possible to create these “reading holes” that way.

My second suggested change is supposed to hint at the reading holes issue. I suppose there are generally two ways to solve this:

  1. Hide read posts.
  2. Do not hide read posts and instead provide buttons/key binds to traverse to next or previous unread post.

I can not evaluate how gray and blue unread counters are relevant here, because I don’t clearly understand how they work at this moment, however.

I like it and asked before

3 „Gefällt mir“

yeah I use Discourse as a teacher and there are topics I need to come back to in like 4 months (Bookmark) and there are topics I need to remember to answer in a few days (mark as undread).

3 „Gefällt mir“

Agreed! I need a feature like this. Any workaround with a plug-in?

Any progress on this? Is it on the roadmap?

It is not on any roadmap I am aware of. Use bookmarks.

3 „Gefällt mir“

Assuming that the Discourse Calendar plugin will also work in PMs, perhaps you can work around it by creating a calendar PM to yourself and adding replies with links to posts you want to come back to at a certain point in time?

That sounds awfully complex when we already have several means to track notable threads.

4 „Gefällt mir“

Absolutely. It was just an idea for those who are not happy with existing functionality.

A theme component can now allow you to do this per:

https://meta.discourse.org/t/defer-topic-button-mark-topic-unread/110951

7 „Gefällt mir“

Könntest du vielleicht genauer erklären, wie das geht?
Das verlinkte Thema existiert nicht oder ist nicht zugänglich.

1 „Gefällt mir“

Ich denke, das liegt daran, dass diese Funktion jetzt Standard ist und nicht mehr in einer Theme-Komponente enthalten ist.

Wenn Sie unten in einem Thema auf „Themen-Steuerung“ klicken, sollten Sie die Option dort finden:

3 „Gefällt mir“

Ist das etwas, das aktiviert werden muss? Ich sehe es weder hier noch auf discuss.gradle.org.

1 „Gefällt mir“

Sie müssen dies zunächst in Ihren Profileinstellungen unter Discourse Meta - The Official Support Forum for Discourse aktivieren. Es kann auch standardmäßig für neue Benutzer über die Site-Einstellung unter /admin/site_settings/category/all_results?filter=defer aktiviert werden.

4 „Gefällt mir“

Ah, danke.
Ich hätte nicht erwartet, dass das etwas ist, das man braucht oder umschalten kann.
Wenn du es nicht möchtest, kannst du den Knopf einfach nicht drücken, genau wie den Lesezeichen-Knopf und so weiter.

1 „Gefällt mir“

Der ursprüngliche Grund für die Einstellungen war, dass es den unteren Bereich des Themas, besonders auf dem Desktop, unübersichtlich macht. Die Funktion ist außerdem nur für Anwender des „Inbox Zero“-Workflows nützlich, was eine kleinere Gruppe sein dürfte als die Nutzer, die Lesezeichen und die anderen Buttons in diesem Bereich verwenden.

2 „Gefällt mir“

Ich stimme nicht zu, dass es nur für „Inbox Zero

2 „Gefällt mir“

Neugierig, nutzt du Lesezeichen-Erinnerungen?