On Tue, May 19, 2020 at 02:12 AM, Shal Farley wrote:
As are the file upload notifications. We've already got this mix of messages and notifications. What that also means is that the message archive is also the activity feed for the group, the place where a member can go to see everything that has happened in the group (yes, ignoring for the moment notifications that do not yet exist, like wiki updates). For better or worse, this is also how Facebook Groups is structured. I think the concept of an activity feed is important for the group, and if we end up pulling all the notifications out of the message archive, then I think we would need to create a new activity feed view somewhere.
Yes, that's correct. Muting would just be another form of notification control.
I've added a new list view to the group hashtag page, and that preference is remembered automatically. I'm definitely open to suggestions for how to better structure that page should we go the hashtags-for-notifications route, including adding bulk operation controls.
I have tried to think of other ways to do notifications, and I have been unable to come up with anything better or more straightforward. Take #cal-invite messages, for example. If the notification and hashtag muting settings are separate (and in separate areas of the site), you'd end up with some duplicate functionality. If I want nothing to do with #cal-invite messages, I'd have to mute the hashtag, and then I'd also have to go and make sure I'm not receiving any notifications about them.
Also, adding hashtags to existing moderator notifications makes it a little easier to identify which notification is which when changing the notification setting.
I'm definitely open to considering other ideas, but I haven't been able to come up with anything else that feels as straightforward as this.
Please let me know what you think.