Hi Alex, I thought I'd share a few feature requests/suggestions I've been thinking about. No pressure, they're not crucial things and I know you're busy. If any are possible, awesome, if not, NBD: [Notifications][Shortcuts] A global keyboard shortcut that brings WFC's Notification popup into direct (input) focus would be awesome, similar to available shortcuts for Main/Rules/Log panels. I rely on WFC's keyboard shortcuts all the time (especially CTRL-TABing between Rules<->Log windows, CTRL-R for refreshing connection log), including the recent in-notification keyboard shortcuts, which I also use often. Adding a global shortcut to bring it to focus would assist with those who have lots of open windows constantly and can't always attend to the notification queue at the moment. [Notifications][Shortcuts] Could a few additional keyboard shortcuts be added for notifications? Namely CTRL-TAB for moving right/up through Notifications queue CTRL-SHIFT-TAB moves left/down through Notifications CTRL-9 jumps to last notification in queue CTRL-1 jumps to first notification in queue These shortcuts mirror all the standard web browsers, and the pattern fits in line with the keyboard shortcuts in the other panels (which also utilize common browser keyboard shortcut functionality). [Notifications] After processing a notification in the stack, ability to maintain current position in Notification stack -- I'll often have a pile of fresh notifications that need processing. As it is now, when processing a notification anywhere in the stack (e.g. "7/13"), after processing that notification, WFC drops you all the way back to the beginning of the stack every time you process a notification. I'll frequently have a handful of MS notifications at the start of the queue that I'll have to deal with later (because of MS entanglements), but processing them soon enough that it isn't worth tossing them onto the silenced-notification list. Could this be changed (or optioned) so that current Notification queue position is held after processing a notification anywhere in the stack? [ConnectionLog] Could an exclusion wildcard be added to the Connection Log's "Search" box functionality? I'll often have a scattered bunch of connections in the log that I'd rather not see, and it'd be great if we could add a "!" in front of a word in the search box which then filters that out of the current connection log view. For example, if the log had a bunch of svchost.exe connections scattered across the log from various Services, typing "!wuauserv" in the search box would filter out svchost.exe connections having to do with that service. Or perhaps if you're focusing on third-party firewalling connection issues, you could type CTRL-F, then "!svc" and all svchost.exe connections would be filtered out of the log temporarily. It'd be super helpful if so!