Preventing damage to database by misdirected editors by auto-subscribing stable editors of all entities?

[mmirG]

IvanDobsky started a thread titled

How to deal with editors ignoring requests to stop damaging the database

A question to the Autoeditors. And MB in general. Quality Control question. (Not sure if this is the right place… but I think this is relevant to people here… but bump this to a new thread if needed. I wanted eyes and brains on this question) I understand that Autoeditors can speed up edits. But who is it that goes and undoes the errors caused by someone who clearly misunderstands how MB works? When a user appears, especially a noobie, who is clearly ignoring requests to s…

The main focus was about how the bad edits could be repaired.

Another element of repairing bad edits briefly touched on in the above thread is spotting bad edits reliably/quickly.
To this end: could subscribing to edited entities be automated (with opt-out available) such that editing an entity results in an auto-addition to a auto-generated Subscription category?

Artists that an Editor adds to the database seem to end up in the personal “Artist Subscriptions” already.

[jesus2099]

@mmirG

Artists that an Editor adds to the database seem to end up in the personal “Artist Subscriptions” already.

You can set your preferences:

Edit: Or you can simply, like me, subscribe to your collection.

[The_King]

I use the subscribe to my own collection method but wish there was a way to ignore and not show my edits in the list.

[jesus2099]

For this we need either one of my long awaited complement to great feature “subscribe to collection”:

• MBS-3922: Edit search: Filter edits by collections
• MBS-8500: Allow filtering edits on collection subscriptions

What I use in the meantime is go to my collection edits page with two user scripts activated:

• Ctrl+Click one of my edits to collapse them all (POWER VOTE) and
• There is a red bar that shows me my last reviewed edit (LAST_SEEN_EDIT from SUPER TURBO).