For general Groups.io questions, please see the Group Managers Forum and Group_Help groups. Note: those groups are volunteer-led and are not officially run by Groups.io.
moderated
Re: Message Approval
#suggestion
#done
On Sat, Aug 22, 2020 at 8:03 AM Duane <txpigeon@...> wrote: I normally read and approve pending messages one at a time. Now and then I select all pending messages and click Approve. Most of the time it doesn't make any difference, but I noticed an anomaly this morning. It appears that the messages are actually processed for approval in the order listed on the pending page. In my case, it shows as newest first. This can lead to a follow up reply being posted to the group before the initial reply. I believe it would be more appropriate for messages to be processed in the order received when multiple messages are being approved. When approving multiple messages at once on the website, we now start to process them in order that we originally received them. Because of the nature of the queuing system used to process messages, it's not 100% guaranteed that the messages will always be added to the archives in that order, but most likely they will. Thanks, Mark
|
|
moderated
Re: Cannot reply from +owner address
#suggestion
Chris Jones
On Sun, Aug 23, 2020 at 03:49 PM, Bruce Bowman wrote:
This post was prompted by a question that was recently asked in GMF.I made the same request in April 2018; see #16576. Chris
|
|
moderated
Re: Special Notice vs Special Message inconsistency
#bug
On Sun, Aug 23, 2020 at 10:49 AM, Andy Wedge wrote:
Also, we can currently search the activity log for 'sent message' and 'sent message requiring approval' but there's no search for 'sent special notice'. I am not sure why messages with a 'special' attribute are referred to as a 'notice' when those without are just 'messages'. Perhaps using two terms to distinguish them ('Special' and 'Notice') is overkill and the current term 'special message' as seen in the activity log is a better description.As best I can tell, there is no way to isolate messages sent as special notices via a search of the activity log. You can enter "sent special message" in the search box but it still turns up nothing. In addition, there are some ways that a special notice can be sent to the group without generating a log entry at all (e.g.: a #cal-reminder). One option would be to have the [Special] subject tag -- currently added to special-notice emails -- retained in the message archive as well. But my actual preference to identify special notices would be to include a "Special" filter in the pull-down menu at upper left (i.e.: analogous to what is currently available for Polls). Regards, Bruce
|
|
moderated
Cannot reply from +owner address
#suggestion
When starting a New Topic, a pull-down menu for the From address allows me to select whether I'm posting from my home address or the +owner address. This option is missing when replying to an existing topic. The reason for this difference in behavior is not apparent to me.
This post was prompted by a question that was recently asked in GMF. Thanks for your consideration, Bruce
|
|
moderated
Special Notice vs Special Message inconsistency
#bug
Hi Mark,
picking up on a GMF topic about searching for special notices that have been sent it has highlighted the fact that the documentation and web dialogue pages refer to sending Special Notices but these get referred to in the activity log as Special Messages. Can we get some consistency for these terms please? Also, we can currently search the activity log for 'sent message' and 'sent message requiring approval' but there's no search for 'sent special notice'. I am not sure why messages with a 'special' attribute are referred to as a 'notice' when those without are just 'messages'. Perhaps using two terms to distinguish them ('Special' and 'Notice') is overkill and the current term 'special message' as seen in the activity log is a better description. Regards, Andy
|
|
moderated
Message Approval
#suggestion
#done
I normally read and approve pending messages one at a time. Now and then I select all pending messages and click Approve. Most of the time it doesn't make any difference, but I noticed an anomaly this morning. It appears that the messages are actually processed for approval in the order listed on the pending page. In my case, it shows as newest first. This can lead to a follow up reply being posted to the group before the initial reply. I believe it would be more appropriate for messages to be processed in the order received when multiple messages are being approved.
Thank you, Duane
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
I don't know about the email commands, but the suggestion for the website strikes me as the height of simplicity.
Something needs to be done to remedy this. Yes, it's really broken. Clearly if you're asking whether it's broken you have not yet experienced it. It's one thing to intellectually argue that "it does what it says it does," and that "locking the topic again the next evening seems logical." It's another to experience being completely unable to resurrect a topic simply because it was locked due to group time-out, and before even realizing that, to experience a manually unlocked topic coming back as locked over and over again. It is completely unintuitive and (I would argue) unexpected. At least, it was highly unexpected by me, and I have been aware and appreciative of the auto-lock and auto-moderate feature since the day it was implemented. Only later did I start to experience this issue. -- J Messages are the sole opinion of the author, especially the fishy ones.
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
On Wed, Aug 19, 2020 at 08:00 PM, JohnF wrote:
Here's my suggestion. If a moderator is actively unlocking a topic that follows the auto-lock rules (via the web), pop up a message indicating that the topic was locked per the rules, and does the moderator wish to exclude the topic from the rules, Yes/No? If No, then it will lock again later that evening. If Yes, it will be excluded from the auto-lock.I'm not aware of any way to lock/unlock a topic via email commands. If this is being done by API, there could be an optional setting to make it permanent or not as part of the request. If not specified, it defaults to No.This strikes me as really complicated. Backing up, I have to ask...is this really broken? If so, it seems to me that the fix is worse than the problem. Regards, Bruce
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
And do the same for auto-moderation when the group is set to auto-moderate.
toggle quoted messageShow quoted text
On Aug 19, 2020, at 5:14 PM, J_Catlady via groups.io <j.olivia.catlady=gmail.com@groups.io> wrote: --
J Messages are the sole opinion of the author, especially the fishy ones. My humanity is bound up in yours, for we can only be human together. - Desmond Tutu
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
Sounds 100% good to me.
toggle quoted messageShow quoted text
On Aug 19, 2020, at 5:00 PM, JohnF via groups.io <johnf1686=yahoo.com@groups.io> wrote: --
J Messages are the sole opinion of the author, especially the fishy ones. My humanity is bound up in yours, for we can only be human together. - Desmond Tutu
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
Here's my suggestion. If a moderator is actively unlocking a topic that follows the auto-lock rules (via the web), pop up a message indicating that the topic was locked per the rules, and does the moderator wish to exclude the topic from the rules, Yes/No? If No, then it will lock again later that evening. If Yes, it will be excluded from the auto-lock.
If this is being done by email commands, a message could be sent requesting the same answer. If the moderator doesn't respond, that's treated as a No. If this is being done by API, there could be an optional setting to make it permanent or not as part of the request. If not specified, it defaults to No. If a topic is excluded from auto-locking, a nondescript message would indicate this when a moderator with locking privileges views the topic on the web, mostly to prevent bug reports ("Hey, why isn't this topic being auto-locked????") I think that will be the friendliest way to do it. It could also use a #noautolock hashtag, but I don't want to encourage hashtag pollution. JohnF
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
Another problem is that there appears to be no activity-log entry for a topic that becomes locked or moderated automatically due to group time-out. The log shows "xyx unlocked topic," and then the topic appears locked again the next day with no explanatory log entry. So at the bare minimum this is a logging - er - failure (not a bug! not a bug!;). It makes the re-locking *appear* to be a bug to moderators trying to figure out why the topic shows up locked the next day after they locked it. Having a log entry for this would at least mitigate confusion.
So to summarize, these are my suggestions, and then I'll beg out of this thread: Best solution: provide a "Do not relock [remoderate] automatically" setting that can be applied selectively by hand to individual topics in a group with a auto-lock [auto-moderate] setting Temporary mitigation of confusion: either disallow the unlocking [unmoderating] of automatically timed-out topics, or provide a warning/confirmation box Long-term logging improvement: add log entries "topic automatically locked [moderated] due to group setting" -- J Messages are the sole opinion of the author, especially the fishy ones.
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
On Wed, Aug 19, 2020 at 03:33 AM, Andy Wedge wrote:
I'm not sure I would call re-locking a topic a bug though.I somehow missed this in the thread. It's inconvenient/unworkable (I'll avoid the loaded term "bug") if you want to be able to manually unlock a topic and have it stay unlocked. In other words, "resurrect" a locked topic. That is currently impossible. I wonder how many of the people participating in this thread have actually experienced this problem. My guess is zero or very few. It is an incredible PITA when it happens to you. The system warning I suggested in the last message ("this topic has timed out and will be relocked within 24 hours, are you sure you want to unlock it") would be only a temporary fix but I think it necessary because of the current unexpected behavior. Mods who unlock a topic are left scratching their heads when it comes back locked again the next morning. Nobody, or very few, people are going to realize what happened (it took me a long time and I'm a sophisticated user). So the warning at least stops people from going through the conniptions that I did. But I think that's only a temporary fix and there really needs to be an option to manually unlocked timed-out topics. The same goes for automatic topic moderation, by the way. Everything in this thread applies to that feature as well. -- J Messages are the sole opinion of the author, especially the fishy ones.
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
Typo - “ cannot be unlocked”
toggle quoted messageShow quoted text
On Aug 19, 2020, at 8:48 AM, J_Catlady via groups.io <j.olivia.catlady@...> wrote:
-- J Messages are the sole opinion of the author, especially the fishy ones.
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
No, I think it can legitimately be called an unlocking bug. De minimus, the system should either forbid the attempted unlocking (“this topic has timed out and cannot needs unlocked”) or provide a warning and a confirmation (“are you sure you want to unlock this topic? It has timed out per the group setting and will be relockrf automatically within 24 hours”).
toggle quoted messageShow quoted text
On Aug 19, 2020, at 8:45 AM, Duane <txpigeon@...> wrote:
-- J Messages are the sole opinion of the author, especially the fishy ones.
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
On Wed, Aug 19, 2020 at 10:30 AM, J_Catlady wrote:
Call it a bug with being able to manually unlock a topic.I wouldn't call it a bug there either. You know as well as I do that if there were no way to unlock a topic, someone would ask for it because they'd accidentally locked the wrong topic. Or needed to unlock an old topic that had been auto-locked, as you want to. Duane
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
If you want to mince words and say it’s not a bug in the feature because the feature works as described (of course it does), then blame the other side. Call it a bug with being able to manually unlock a topic. 😊
toggle quoted messageShow quoted text
On Aug 19, 2020, at 8:27 AM, J_Catlady via groups.io <j.olivia.catlady@...> wrote:
-- J Messages are the sole opinion of the author, especially the fishy ones.
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
Right. The alternative, whatever you want to call it ( “never lock topic” is not bad but I’m not crazy about it - maybe “exclude from locking time-out”) could be on the More menu. I don’t care where it is on the UI or how it’s implemented (More menu is fine, if the arrow drop down, doesn’t really matter) but providing the variable is essential for the time-out feature to be actually useful.
toggle quoted messageShow quoted text
On Aug 19, 2020, at 8:19 AM, Duane <txpigeon@...> wrote:
-- J Messages are the sole opinion of the author, especially the fishy ones.
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
On Wed, Aug 19, 2020 at 09:52 AM, J_Catlady wrote:
there should be a different alternativeIt sounds like what you want is another option - Never Lock Topic - on the More menu. Maybe use the lock-open icon to differentiate from the Unlock Topic option that uses the unlock icon. I believe the current operation is correct, not a bug, in that it operates exactly like it's supposed to - lock anything older than xx days. Duane
|
|
moderated
Re: Retroactive Topic Locking?
#misc
#suggestion
Correction - an auto-locked topic stays locked forever.
toggle quoted messageShow quoted text
On Aug 19, 2020, at 7:52 AM, J_Catlady via groups.io <j.olivia.catlady@...> wrote:
-- J Messages are the sole opinion of the author, especially the fishy ones.
|
|