Llevo meses notando cosas como las siguientes, pero nunca he presentado un informe porque nunca pude reproducirlas de forma consistente. Pero, por fin, por accidente, ÂĄlas he capturado en cĂĄmara! (AsĂ que por favor disculpen las pausas y la confusiĂłn reflejadas en los movimientos de mi cursor).
Las cosas a las que hay que prestar atenciĂłn son:
Que un tema aparezca misteriosamente en no leĂdos (de hace dĂas, de la categorĂa howto)
El segundo punto es algo similar a un error comĂșn que veo (pero que nunca he podido reproducir en vĂdeo) donde hago clic en un tema desde nuevos en una categorĂa que estoy rastreando, pero su propio estado no se muestra como rastreado a menos que actualice la pĂĄgina. (Me pregunto si eso estĂĄ relacionado con esto.)
Justo antes de grabar esto, estaba intentando reproducir ese error rastreando Contribute > Bug y luego haciendo clic en uno de sus temas desde la pestaña de no leĂdos. No pude, pero al dejar de rastrear Contribute > Bug, mi pestaña de no leĂdos se llenĂł con unos 20 temas cerrados en Contribute > Bug de alrededor de 2015, lo que parece ser el mismo error que el punto 3.
I canât consistently reproduce the first, where the correct notification level is only shown after a refresh (of a category, or a topic). Itâs been happening to me for months, but whenever I try to reproduce it, it doesnât happen.
The second, which I think is a bit more minor, but still a nuisance can be reproduced (for a limited time only) like so:
Clear /unread
Track a category currently set to âNormalâ
Go back to /unread and observe posts not previously in it
Iâve been able to do this with a number of categories, but only once for each. Once Iâve dismissed the posts from unread, they never appear again.
Consistently reproducing it takes a little more work, so hold onto your hats, itâs gonna get a bit crazy:
Go to unread in a category of your choosing which has a notification level of âNormalâ, observe nothing there:
So, the bug here is that previously opened topics in a category become tracked, and appear in unread (unless previously dismissed), when the category is tracked, whereas nothing happens to old not-opened-before topics.
To me, what should happen is either:
Nothing changes about the notification status of old topics in a category when it becomes tracked, previously opened or not.
or
All old topics become tracked when the category is tracked, but are automatically dismissed, so only new activity appears in the unread tab.
I lean towards the second solution, provided explicitly set notification levels on topics are kept.
I havenât investigated how this works with other notification levels, I imagine its the same, but I feel it would confuse things for the time being.
La primera serĂa que los temas no se estĂĄn rastreando correctamente de forma implĂcita. Si asĂ fuera, todos los temas de Community Building > Praise deberĂan aparecer en este paso:
Parece que esa lista solo muestra los temas con un registro de seguimiento de ârastreadoâ, y eso no funciona segĂșn lo esperado. Lo que deberĂa ocurrir es mostrar todos los temas con un registro de seguimiento de ârastreadoâ, y todos los temas que pertenecen a una categorĂa rastreada. (Lo mismo aplicarĂa para la funciĂłn de âseguirâ).
La segunda serĂa la apariciĂłn de temas aparentemente arbitrarios como no leĂdos cuando rastreas una categorĂa (asumo que es un efecto secundario del cambio de estado de seguimiento de temas anteriores de âregularâ a ârastreadoâ), lo cual podrĂa solucionarse descartando automĂĄticamente esos temas como no leĂdos.
Se reduce al hecho de que un tema no puede ser simultĂĄneamente nuevo y no leĂdo:
Aunque estĂĄ implĂcitamente rastreado, el tema no aparece en no leĂdos porque el usuario nunca lo ha visto
El tema no aparece en nuevo porque estĂĄ mĂĄs allĂĄ del umbral de tu configuraciĂłn âConsiderar temas nuevos cuandoâ
Es un problema difĂcil de resolver, porque que todos los temas antiguos de una categorĂa aparezcan en tu pestaña de âno leĂdosâ realmente no es una buena experiencia de usuario.
âDescartarlos automĂĄticamenteâ es bastante costoso a nivel de base de datos (se tendrĂa que crear un nuevo registro TopicUser para cada tema en la categorĂa que acabas de rastrear).
Realmente no llegamos a una idea ordenada para resolver el problema, y la discusiĂłn se enfriĂł. Una opciĂłn que @sam propuso fue
From a practical perspective, that doesnât make sense to me. If I buy a book and put it on my shelf having not opened it, it is both new and unread.
Wouldnât it be possible to have an old topic (with no tracking record) only appear in unread when thereâs new activity on it?
So, just as a tracking record is created on new activity for topics in watched categories, a tracking record would be created on new activity for topics in tracked categories.
Combined with the above, couldnât we just dismiss topics where the tracking record has been changed to âtrackingâ as a result of tracking the category, which would mean the same user experience, without any additional database writes? (If I understand how tracking records, dismissing and TopicUser relate.)
This way, it seems to me, we could have a mailing list experience for tracking too!
Sure, I agree. I was talking purely about how it currently works in discourse.
I believe @sam thought this would have major performance issues
Iâm 99% sure a new record isnât created for tracked topics - @sam said âcreated when we notify usersâ, and tracking doesnât cause notifications. Maybe fixing this is the solution
Ok⊠Iâve done some testing in my dev environment. As a simplest possible repro:
Set previous visit timeout hours site setting to 0, to make testing quicker
User A sets âConsider topics new whenâ to âcreated since I was last hereâ
User A sets Category1 to tracked
User B posts in Category1
User A observes the topic in ânewâ, but does not open it
User A leaves the site
User A comes back to the site later, and User Bâs post is gone from the ânewâ tab
User B posts again in the same topic
The topic does not appear in either ânewâ or âunreadâ for User A, even though they are tracking the topic
That same repro works for âwatchingâ a category as well. A notification is sent, but no TopicUser row is created (checked on the rails console). It seems that this:
is not happening for some reason, both for watched and tracked categories.
Would it though? We already have topics listed in the latest tab and the new/unread tabs simultaneously. And the two (new and unread) are for different purposes: new is âshow me the newest topics on this siteâ and unread is âshow me topics Iâve expressed an interest in, but havenât (finished) read(ing)â. For new to achieve its purpose it has to have unread topics in it which are new, and for unread to achieve its purpose it needs to have new topics in it which are unread.
Currently the unread tab is rather dysfunctional.
Interesting, thanks for doing all this investigation! So it would seem like if this did actually happen (or more specifically, a TopicUser row was created on topic update, rather than notification, to include tracked categories), then our problems here would be solved. @sam thoughts?
I am fine to change the semantics of âtracked categoryâ so it means, if a category is tracked it will unconditionally show up in new regardless of your new duration, it does not mean this now.
