I'll try to report within 48 hours.

Having carried out a whole series of tests my first batch of observations and suggestions is set out below. I would like to think that they are “complete” but there almost certainly things that I have missed. (Sorry!)

Simple – to – report things first:

•  The creation of a Folder is notified, but the creation of a photo Album is not. (Note: there is a mix of terminology here; in the Activity log a Folder is called a directory, and the Notification refers to a directory as well; IMHO it would be better if the word directory was not used.

• The Move of a.File is notified, but the Move of a Photo is not. FWIW there is no available entry in the Activity log for the movement of a Photo.

• If a Photo is Edited, e.g. by adding some Description or changing its Name then a Notification is generated but the notification is to the effect that a new upload has taken place. This has the potential to be profoundly confusing. (Name changing can be a useful way of determining the order in which photos are displayed in an album, and adding a Description cannot be done at the time of upload; it can only be done by editing; neither action should be seen as in any way unusual. ) Edits should be notified as edits, not new uploads.

• Notifications of Folder / File activities are by instigator’s Display Name only but Notifications of Album / Photo activity are by Display Name and email address.  It should be by Display name only.  

• At this time deletions, edits and the like are not sent to the original owner of the material. If that notification is introduced, then it is essential that the notification is an accurate summary of what was done and not a complete mis – description. I would suggest that any such edit provides the option of including a “Reason for Edit” that can (again optionally) be fed back to the original owner.  That “reason for edit” would not need to be stored for future reference; its only purpose would be to advise the material’s originator of why changes were being made.
  
  Having said that while "uploaders" have the ability to not notify members of an upload I would prefer to have the ability to not inform original uploaders of any edits or deletions.

About half the time (can't see any consistent reason) hashtags do not appear in the subject line when moderator adds them.

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

Not intentional, it was a bug. Just fixed.

On Thu, Jul 2, 2020 at 03:54 AM, Andy Wedge wrote:

I've also noticed that the column header overwrites the Your Groups drop-down menu:

This has been fixed.

Thanks, Mark

On Sun, Jul 5, 2020 at 07:44 AM, paul fox wrote:

Is there a reason that the json files that accompany the exported image folders in the exported zip file don't include the Owner name that was associated with the folder on the site, along with the Title, Description, and creation date?

I've added more information to both the album and photo json exports.

Cheers, Mark

I've never seen "Past" listed before.  Do you have a top-tier (paid) group?

Sure thing.  Attached is a screenshot of my permissions on that group

If I am not allowed to Ban members, the Members button offers choices of Moderators, Bouncing, and Banned.  Selecting Banned causes the blue button to lose the alphabetical label and every member is listed.

It's the combination of the notification going to the person who did
the action plus the delay. They compound each other.

I thought we were given the option to have it go through the group or
not but regardless it is going through the group.

That's true for browser push notifications as I understand it, but as you found out, you still get the email several minutes later.

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