-44 upvotes, 3 direct replies (showing 3)
View submission: API Updates & Questions
You mention that there is a mod queue upgrade due out this week - any more details on this, or are all the queues properly serviced only in the September update?
Happy to provide a sneak peek - tomorrow we will launch and announce additional Mod Queue’s within our mobile app (“Removed,” “Reported,” “Edited,” and “Unmoderated”). We’ll also be including more context within Mod Queue’s by adding post titles to comments.
Have you fixed the borked chat Vs legacy chat issue yet ? Will I be forced to choose between functioning queues or a functioning chat if I allow the coming update
It sounds like you are referring to the “legacy chat�� and the “chat” buttons in the chat tab on desktop web. Is that correct? If so, the “legacy chat” contains your one-to-one and group chats. There should be no current issues with one-to-one and group chats - however, if you are experiencing an issue accessing them or chatting, please let us know in r/modsupport.
The “chat” button contains chat channels that are subreddit-embedded chats. We’re currently piloting this with volunteer communities. If you aren’t seeing chat conversations in this section, it is because you are not in a community that is testing this feature. Happy to share feedback with the team if this was a confusing experience.
Comment by [deleted] at 05/06/2023 at 23:06 UTC*
47 upvotes, 1 direct replies
[deleted]
Comment by fruitspunch-samuraiG at 06/06/2023 at 14:43 UTC
6 upvotes, 0 direct replies
More tools so we mods do all the job reddit should do :)
Comment by myalterego451 at 06/06/2023 at 06:56 UTC
2 upvotes, 0 direct replies
Good to hear that today's update will include those queues, though I'd have to say that seeing those come I to production so quickly, just as the API change comes in, does look a little like rushed development - let's hope it's not too buggy
Apologies, I was referring to this chat issue[1] which I made an assumption was linked to legacy Vs new chats. Comments on that thread seem to suggest it's been fixed now