Mark,

#cal-invite messages will be moderated. #cal-notice and #cal-reminder
messages will continue to not be moderated even if the group is
moderated. Seems complicated.

The calendar always has been, and looks like it will remain, a problem child. I think it is because it can cause an action at a future date/time, and that action's point is at least blunted, if not defeated, if the action doesn't happen on schedule.

This hints at two other things to watch for: Group Guidelines and Monthly Reminder. These particular notifications can only be created by a group moderator, so I don't think they need to obey any group-wide moderation setting when posting (and they haven't, to date).

Currently (as of 06-01) the monthly group guidelines message has two hashtags: #monthly #guidelines; perhaps that should consolidate to #guidelines-notice. The Monthly Reminder has none; perhaps it should have #monthly-notice. Just to fit the pattern.

Shal

Mark,

They all bypass the group setting of moderating all messages.

This should be fixed now.

I hope you didn't include the cal-xxxx notices in this fix. Group members won't likely be happy about late event reminders & notices.

Shal

On Fri, Jun 19, 2020 at 02:20 PM, Duane wrote:

I've just discovered a serious problem with these notifications.

Mark; I think I've found another one; the group I moderate uses hashtahgs (very) sparingly to minimise misuse or overuse. Although I remain puzzled about the apparent disappearance of the -notice feature (my #25467 refers) a couple of tests I have conducted suggest that these new "system" hashtags appear in the pick - list of hashtags that can be used by members (and moderators, come to that) and that availability for public use is something that our group would definitely not want; as far as I can see there would be no method of preventing their use by members.

Chris

Mark,

They all bypass the group setting of moderating all messages. ...

This should be fixed now.

Ok, now they are held in Pending, but I can't Approve them.

Just now when I tried to approve a #wiki-notice by email nothing happened.

Earlier when I tried to approve one by web it ended up "claimed" by me instead. Another moderator also tried and failed to approve it, then deleted it instead.

Shal

On Fri, Jun 19, 2020 at 08:58 PM, Mark Fletcher wrote:

This has been fixed.

Wow. That was quick. All good now.

Thanks
Andy

This has been fixed.

Thanks, Mark

Hi Mark,

I'm seeing issues displaying messages in Topics view on GMF (Messages and Expanded views seem to work OK).  If I set my display preferences to infinite scroll I see this:



If I use use any other display setting (20, 50 or 100 rows) the display stops after the 'About Features Pricing' footer.  It's the same whether I use Chrome or Firefox.

Regards,
Andy

It's worse than I thought. A repeating event that has been on the calendar since January is also not putting out reminders. This reminder was for one day before the event. It never happened. At this point I suspect none of our reminders are working. 

Since we have cancelled almost all meetings with reminders since the COVID shutdown, this was not evident until our first meetings again this week. This problem could have been lurking for 2-3 months since we cancelled several repeating meetings that had reminders set from Mid-March until now.

Don Pottenger,
VillasOfAda group owner

On Fri, Jun 19, 2020 at 12:58 AM, Mark Fletcher wrote:

The following notification hashtags have been changed:

Has this change been reverted? I cannot find any in the #xxxx-notice format now, and I definitely saw them yesterday.

Chris

Thanks, Mark. I even just now tried first adding the tag and then sending a message within the thread, akin to your "this is now fixed" messages, and there is still no effect on the notifications. This makes sense. Just some wishful thinking.
--
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

Hi All,

I have changed the Notify Members checkbox when uploading files so that it defaults to being unchecked, as before. I have also added new Notify Members checkboxes when adding/updating wiki pages and when uploading photos. They default to being unchecked.

I think of this as a stopgap measure until I can address the issues raised in a more complete fashion. I will work to come up with a proposal either later today or Monday.

Thanks, Mark

On Fri, Jun 19, 2020 at 04:31 PM, Bruce Bowman wrote:

Seems to me that the hashtag's "lock topic" mechanism is best reserved to address Chris's concern about people replying to the notification

If I'm honest I am now wondering about the wisdom of that idea, for reasons triggered by Shal's comment. I simply cannot work out in my own head what the optimum (for which read least annoying) settings might be, and being honest again I don't want to spend much time on thinking about it until the situation is more stable than it currently is; with the end point of the development being as yet undefined, any "solution" could turn out to be somewhat short - lived.

Someone - Andy I think - brought up Shal's occasional point about "least astonishment" at some point, and I think that ought to be a guiding principle here.

Chris.

On Fri, Jun 19, 2020 at 09:53 AM, Andy Wedge wrote:

Another thing I have noticed (testing some file uploads) is that if you lock the file upload topic in the archive and then do another upload:

a) the upload completes OK
b) a message is placed in the activity log to confirm which file was uploaded
c) no extra message is placed in the archive (as expected because the topic is locked)
d) here is no activity log entry to say that someone tried to send a message to a locked topic

I'm not sure if it is supposed to work that way or not in respect of (d) but it shows that locking the topic can also prevent new notifications being sent. I suspect the threading algorithm is playing a part here and a further upload in a few days time will generate another topic.

Seems to me that the hashtag's "lock topic" mechanism is best reserved to address Chris's concern about people replying to the notification (ref: https://beta.groups.io/g/main/message/25438).

For that reason I'd actually prefer that each notification appear in its own topic. 

Regards,
Bruce

Suppose I want to get web/app notifications for the tag #fixed in beta, to see when bugs (including ones I might have reported) are marked as #fixed. I don't think this would work because as I understand it, the notification only goes out when a new message bears the tag, not when an existing one gets the tag added. I haven't tested this but it would be great if the notification could go out whenever a tag is added.
--
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

Another thing I have noticed (testing some file uploads) is that if you lock the file upload topic in the archive and then do another upload:

a) the upload completes OK
b) a message is placed in the activity log to confirm which file was uploaded
c) no extra message is placed in the archive (as expected because the topic is locked)
d) here is no activity log entry to say that someone tried to send a message to a locked topic

I'm not sure if it is supposed to work that way or not in respect of (d) but it shows that locking the topic can also prevent new notifications being sent. I suspect the threading algorithm is playing a part here and a further upload in a few days time will generate another topic.

Andy