On Wed, Apr 15, 2020 at 12:47:06PM +0200, Ansgar wrote: > I'm not concerned about marking messages read after some time and > keeping the view time in ephermal storage for that. But that's not > what Discourse does: as described elsewhere it stores all read times > persistently on the server; that would not be neccessary for marking > posts as read even on a web application.
No, but it is required for things like knowing which posts in a topic is popular, so should be used for auto-summary. It also is used to reduce abuse, as a normal new user would spend time reading topics before posting for the first time. > Evolution also keep track of the mouse cursor, but that is something > different from recording clickstreams and evaluating them to increase > user participation as some people do. Your reply seems to put both on > the same level. My point is that it's unhelpful to automatically equate "user tracking" to something undesireable. > > Interestingly, I've generally mixed replying via email with visiting > > the > > site. I would agree that it's not en par with the web UI, but I don't > > think it ever can be, due to email being designed rather differently. > > >From my tries with Discourse, it just silently stripped all quotes out > from the reply. > Perhaps this is: https://meta.discourse.org/t/single-quote-block-dropped-in-email-reply/144802 > Is this documented in some discoverable place or hidden? I've still not > managed to discover any documentation for Discourse targeting the user > (compared to admin or API documentation). > https://discourse.mozilla.org/c/meta/faq/244 Generally, there isn't a central user documentation, because each discourse instacne can be configured quite heavily, depending on each community need. Neil --
signature.asc
Description: PGP signature
