Comment 18 for bug 1321750

Reuben, my use case was to enable Caffeine after booting a system and leave it enabled over many screen-sleep and suspend/wake cycles. I never had to fiddle with it again until reboot, significantly simplifying the disablement of the desktop environment's session lock when I didn't need it. However, if I knew I was going to be away from the computer for an extended period of time and wanted it to lock when going to screensaver, I would disable Caffeine and leave. I rinsed and repeated for a couple years.

It was a very convenient experience and I grew to depend on Caffeine. I certainly understand that for your purposes and that of other users who use it only for purposes like media consumption, the newly streamlined interaction with Caffeine is preferable. I'm not certain what the correct etiquette is in this case. Is it reasonable for me to expect you to tailor Caffeine for uses outside your own?

I don't think there needs to be any emotion around this development. As you say, if someone wants a different experience with the software, they can fork it. Perhaps this'll be the impetus to trigger someone else to learn how to do that.

If you see fit to restore the function that allowed me to use Caffeine in this way, I would certainly appreciate it. This is another area I'm not clear on, again since you're doing all the work. Is a bounty in order?