It would probably be a good idea to move Clippy into a subprocess that can be manually disabled if possible. Currently it can never be turned off, even if the extension is uninstalled.

How can I detect if an extension has been uninstalled? I probably no longer need clippie running as a singleton instance, I'll look into just re-instantiating normally when the indicator is created. Note that I rebranded as 'eclipse' because I'm focusing on the ability to encrypt clipboard entries, thus the name/uuid change. Thanks again.

There is really is no way to reliably detect when an extension has been uninstalled. This is in fact the reason we disallow the creation of anything in `init()` or the top-level of imports, because there is no `uninit()` call. There are some cases, such as a drop down terminal, where the main functionality must continue running after `disable()` is called, and that's why we make an allowance for subprocesses. Those are an acceptable compromise because they run outside of the gnome-shell process.

Okay, we'll for now I've detected when the indicator is destroyed and have detached the Clippie process and reduced any memory impact. I did some work on it today and it's now stateless so I'm going to refactor it to remove the singleton object and allow it to be re-instantiated when the indicator is recreated. Thanks for the review.