Open an issue on this GitHub repository.
Currently, the only way to enable/disable Do Not Disturb is through Apple's Accessibility APIs. If Apple introduces a different API, I'll switch to that.
No. The app sits 100% idle until a screen-sharing session starts or ends. It does absolutely no polling and therefore uses zero CPU 99.9999% of the time.
Muzzle is smart. It restores Do Not Disturb to whatever state it was in just before you started screensharing. If you already had Do Not Disturb on, Muzzle leaves it on. If it was off, Muzzle turns it back off.
No. If you have set Do Not Disturb to turn on/off at specific times, Muzzle will not interfere with that schedule. This means, however, that Do Not Disturb could potentially turn off during a screen-sharing session if you have scheduled it to automatically turn off at that time. For best results, I recommend disabling automatic Do Not Disturb schedules.
Yes. For several reasons:
No. The folks who write software for iOS and macOS are who truly keep those platforms alive and vibrant. Apple treats developers with very little respect, takes 30% of their income for nothing, and makes their lives difficult at every turn. I'll have nothing to do with that until Tim Cook and company clean up their act. </rant>
TLDR: Absolutely nothing. This is an inside joke.
Long Version: Before I uncovered some secret sauce in macOS, I was going to use a very advanced, unstable technique to make Muzzle work. This technique is called mach_override. When I shared this with friends, they said this is the coolest name ever and that if there was a button labeled "mach override", they would click it no matter what. Ergo, button.
Welcome to the club. It meets on Wednesdays at 7:30 to yell at me on Twitter.