We have a fancy batch compute thingy that runs jobs. The details are not important but there are hundreds of jobs and people (not necessarily just Engineers TM) spend their days updating them or creating new jobs to try things out. The job storage is backed by git but this is more of a backup and record of changes then an indication that the jobs are treated as source code. Some of the changes are machine generated (jobs making jobs) and some people just hit 'save' a lot.
Even though this is noisy-idiosyncratic-psudo-backup isn't really 'source code' it is convenient to syn the repo into phabricator so people can query it and run herald rules on it (ex: 'email me for changes made to IMPORTANT_JOB'). However the volume of noisy changes obliterates the signal:noise ratio on `/feed`. Breaking apart the Publish/Notify settings would (I think) let people write their fancy herald rules but keep `/feed` useful.