Change "Subscribe" Semantics for Blocking/Muting Lists

[zanfranceschi]

Is your feature request related to a problem? Please describe.
In the moderation lists context, me and some other folks find it's very confusing to "Subscribe" to a list of accounts one wants to block or mute. Maybe the word "Subscribe" generally means you want to subscribe to something you want to consume and not block/mute.

Describe the solution you'd like
Change the "Subscribe" semantics to something more related to moderation – examples: "moderation actions", "moderation", "action", "block or mute", etc

[DanielHe4rt]

Agree. First time using the "block all" list, I tried everything before click in "Subscribe" since it was an toxic account list.

Good catch @zanfranceschi!

[LucasMorais1998]

I admit that the "Subscribe" also confused me a bit at first, because if it's a list of people I don't want to be in contact with, "Subscribe" kind of makes us subconsciously think of the opposite.

[scottdotweb]

"Subscribe" is basically too low level. If a list has "block all" and "mute all" buttons, those imply a subscription to the list to apply the action to its members, so there's no need to have it as an action first.

[jamesonwilliams]

I just closed similar #6167 - will throw my 2 cents into the pool after thinking about it a bit more:

There are multiple valuable actions one might take on a mod list: block, mute, subscribe to all. The bug here is that we have this subscribe button acting as a menu, when all three options should be presented as primary actions in the main presentation on this screen, as a header element under the mod list name/description.