discussions not being automatically designated as 'followed'
Until recently when I posted on a discussion I would get an email and a notification that someone had posted a comment and the discussion was marked as one I am following.
The other day I had difficulty understanding something Sitesurf had said and 'replied' to 3 of her answers to other people re the very thing I didn't understand. And I waited, and I waited, as normally Sitesurf is very prompt in replying. Was she on holiday?
Eventually I realised that I was no longer getting notifications re discussions I had recently commented on. So I searched for the discussion to which I was waiting for Sitesurf to reply.
She was as good as ever, and had replied. Now I understood the problem I had asked about but I also found that the discussion had not been marked as 'following'. So I marked it.
I will check that this post is marked once I post and in future will try to remember to check that, when I want a reply, the discussion is marked as following. I do not know if others have had this problem, or maybe it is due to a very temporary glitch?
Hi Anneduol1ngo ,
It's like that since Duo made a Maintenance on the forums: see the 3rd top discussion of the main "Duolingo" forum for English speakers for the official announcement "Forum Maintenance Session Complete" (or this previous one announcing the maintenance).
You'll see in the first one that this bug has been reported by several users there.
Thanks. I am not very good at doing searches in that I tend not to be able to find the answers I want. I did do a search prior to posting and didn't find this discussed. Perhaps I wouldn't have reported it as a bug if I had seen it had already been reported.
Ok, it was not marked as followed, I had to do it manually, and I also have checked my settings and everything there is OK. So it seems there is a problem unless the system has changed. I'll keep and eye, and unless someone suggests otherwise, will report this as a bug.
Even worse, now having added this, the discussion has changed again to one not being followed. So I will report it as a bug.