开云体育

Hi all,

This week's change log:


Feel free to reply to this topic if you'd like to comment on the
changes. Or better yet, if you expect a lot of discussion start a new
topic (or rejoin an existing one) about a specific change.

NEW: Replaced the 'Only Moderators Can Create Hashtags' checkbox with
a dropdown, allowing messages with new hashtags to be either
bounced, or the new hashtags to be removed.

Stripping the inbound hashtags is a lot gentler on the group members than rejecting their posts. I'm not sure why a group moderator would choose to bounce the messages with hashtags, now that there's a choice.


Comments about these others are also welcome:

API: Changed group field: restrict_create_hash_tags is now
hash_tag_permissions.
SYSADMIN: Fixed log rotation issues on the DNS servers.
NEW: When exporting group data, you can now export hashtag data.
SYSADMIN: Now serving the cookie consent js/css code locally instead
of from a CDN, because that was timing out.
OTHER: Sent out the GDPR Privacy Policy update email. Dealt with a
bunch of angry responses.
INTERNAL: Deleted all user accounts not subscribed to any groups (or
only subscribed to updates@) that were at least one month old.
BUGFIX: Fix internal crash when a non-moderator of a subgroup rejects
via email a pending message.
BUGFIX: The FBL processing code was ignoring reports from some
domains.
CHANGE: Better behavior when uploading multiple files and one of them
is a duplicate of an existing file. Previously we would disgard all
files in the upload. Now we keep all of them up to the point of the
duplicate.
BUGFIX: If a file was renamed with either / or \ in the name, the file
would be unlinked and unreachable. Fixed the bug and re-linked the
affected files.
INTERNAL: Made exportuser and exportgroup more reliable when dealing
with large amounts of data.

Please call out any you find significant.

Shal


--
Help: /static/help
More Help: /g/GroupManagersForum/wiki
Even More Help: Search button at the top of Messages list

On Sat, Aug 11, 2018 at 09:41 AM, Shal Farley wrote:

Stripping the inbound hashtags is a lot gentler on the group members than rejecting their posts. I'm not sure why a group moderator would choose to bounce the messages with hashtags, now that there's a choice.

Agreed. I checked the group I moderate and found that it was set to "bounce" so moderators might be advised to check their own groups just to be certain that the setting is what they want it to be.

Chris

On Sat, Aug 11, 2018 at 06:32 AM, Chris Jones wrote:

I checked the group I moderate and found that it was set to "bounce"...

Yeah, me too. I was really surprised by this default and may comment on it in beta.
?
Bruce
--
The system Help is your friend.??/static/help

Bruce,

Yeah, me too. I was really surprised by this default and may comment
on it in beta.

Bounce was the prior behavior, so I'm sure that's default so as not to change a group's behavior unexpectedly.

Shal


--
Help: /static/help
More Help: /g/GroupManagersForum/wiki
Even More Help: Search button at the top of Messages list

On Sat, Aug 11, 2018 at 12:01 PM, Shal Farley wrote:

Bounce was the prior behavior, so I'm sure that's default so as not to change a group's behavior unexpectedly.

Okay, that makes sense for existing groups, may not make sense for new groups. I now suspect Mark implemented this simply to provide the "strip" alternative.

I wonder what happens if "Hashtags Required" is ON, "Hashtag Permissions" is set to strip, and a Subscriber sends a message with a new hashtag? Does the message post sans the hashtag, does the message get bounced after all (i.e.: after stripping, it no longer contains a hashtag), does the hashtag get created anyway?

I just tried this in Shalstest...it let the post go through and created the new hashtag. But I'm a Moderator there so that's no doubt a factor (I didn't want to downgrade myself and be unable to change the Settings back the way they were).?

Bruce
--
The system Help is your friend.??/static/help

Part of the problem here is that many of the terms aren't totally clear as to what they mean. So, I did some testing.

For example: The "Bounce" option.

What this means is that if there is an attempt to create a new hashtag in a new topic generated via email, then the email is held and a new email (not a reply to the first one) is generated by groups/io and sent to the member that attempted to break the rules. You can still use existing hashtags, so the require hashtags groups still work.

Here is an example message that comes back with the group name and link number edited. Depending on your email client, and this not being a reply, it may be difficult to notice this email. I was off doing other things and it was only later that I noticed it had shown up in my Spam folder (Hotmail).

========== Sample ============

Hello,

This group does not permit the creation of new hashtags except by the moderators. The subject of your message
contains at least one hashtag that is not allowed. Click on this link to edit your message subject and add appropriate tags:

/g/mygroup/editsubject/123456

Your message will not be sent to the group until you edit the subject.


Cheers,
The Groups.io Team
=============================

There is a problem with this, as the link only works if the person sending the email is already logged into their groups.io account. Otherwise, one gets dumped at the homepage. I don't know what would happen if this was a restricted group.?Once you get logged in, then the link brings you to the editsubject form where you get a chance to correct your errors and then the message will be posted.

Personally, I would rather just see scrapping the "bounce" option altogether. IMHO, this is not ready for prime time.
?
--?
Gerald