Are we sure we want this? Aren't there zillions of active bots? What's special about SDC ones?

For now, yes. SDC bots in particular are editing very frequently across millions of files right now (as opposed to the many bots that just upload files instead of altering metadata for existing ones), and a decent number of community members still do not yet have interest in monitoring SD information.

In T247433#5963365, @Cparle wrote:

Are we sure we want this? Aren't there zillions of active bots? What's special about SDC ones?

And we don't have any pre-existing mechanism of dealing with this kind of thing? @MarkTraceur

Since there is an existing mechanism to block bot updates, and there aren't many (if any) Structured Data bots running at the moment, we'll put this on the back burner for now and see if it becomes an issue.

This is probably a duplicate of T246746. This ticket is likely about edits by my bot, which I fired off about the same time and I got a lot of unpleasant feedback about. As I understand it, not all edits by bot accounts are marked as "bot edits", but only edits with a "bot=1" flag set somewhere for each edit. For my edits, I am using QuickStatements, an excellent tool by @Magnus. QuickStatements is able to operate on SDC only in batch mode (aka asynchronous mode) and in that mode it either does not set that flag properly or that flag does not work properly in that mode. The issue was reported also at https://github.com/magnusmanske/quickstatements_rs/issues/2.

There are so many mass edit tools, maintained by many people. Perhaps a better way would be to mark all the edits by bot accounts as "bot edits"

This continues to the the issue. I reported it also at https://bitbucket.org/magnusmanske/wikidata-todo/issues/124/qs-should-send-all-requests-with-bot-1

Relates to T262750: Allow to exclude bots from watchlist notifications

More generally, I think the issue is that people should be able to determine what slots to watch (do I want to get notifications about mediainfo slot changes or just main slot changes?). This will increasingly get more important as there will be more slots, some of them conceptually part of the main content (e.g. what is now the template documentation subpage should eventually become the documentation slot, and there is no reason one wouldn't want to watch that), some of them background mechanisms not very relevant to the user.

I made a tiny tentative patch (linked to T262750) which simply adds a "Email me also for bot edits of pages and files" option similar to the one which exists for minor edits. Is it exactly what we need, no, but it would be a decent stopgap until proper slot filtering is available.

Almost two years latter, it is still an issue. See my talk page when small maintenance tasks are swamping people's watchlists.

In T247433#7611456, @Jarekt wrote:

Almost two years latter, it is still an issue. See my talk page when small maintenance tasks are swamping people's watchlists.

According to your talk page, you are making those edits without the bot flag, so I don't see how that's relevant to this task.

Either you'd need T174349: Allow tag filter on Special:RecentChanges and Watchlist to be inverted (enable the not operator) and then a filter could be set based on the OAuth tags those edits get, or T110249: Allow OAuth applications to be granted rights the user doesn't have which would allow OAuth tools to set the bot flag on their edits.