tcpsnitch 'eats' terminal mouse events

[oliviertilmans]

During this trace:
https://tcpsnitch.org/app_traces/200

I was unable to trigger mouse events (i.e. clicks) in the terminal. Not really an issue as I don't need it, but that might hints at a weird interaction somewhere... I'd guess due to the fact that the mouse events are fed to auxilliary processes (these are basically escape-sequences on stdin)--or this could be a buggy weechat plugin that hardcoded stdin=1.