When we designed the scripting system, the hypothesis was that if we provided an API that would allow scripts to get references to PipeWire objects and subscribe to their events independently, then any functionality could easily be built on top. In the above example of hooks that select the default “sink”, for instance, a user could add a custom script with a hook that also reacts to the “select-default-node” event and is linked in a specific position in the existing hooks chain, using hook dependencies. Most importantly, though, these APIs fail to work well with the “standard event source” and the hooks system, because they maintain their own references to PipeWire objects and fall into the same trap that the scripts used to.