138
edits
Growl: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(New page: OK. Growl is a notification protocol that talks to a service on your local machine and makes nice little bubbles pop up when certain events occur. I basically wanted to be told when someo...) |
No edit summary |
||
| Line 1: | Line 1: | ||
OK. Growl is a notification protocol that talks to a service on your local machine and makes nice little bubbles pop up when certain events occur. | OK. Growl is a notification protocol that talks to a service on your local machine and makes nice little bubbles pop up when certain events occur. | ||
For a WTF IS GOING ON bit scroll to the bottom. | |||
I basically wanted to be told when someone hilights my nick or PMs me in weechat (there're probably similar scripts for IRSSI, but fuck that heap of shit) | I basically wanted to be told when someone hilights my nick or PMs me in weechat (there're probably similar scripts for IRSSI, but fuck that heap of shit) | ||
| Line 52: | Line 54: | ||
/growl setup YOUR_IP YOUR_LOCAL_PASSWORD PORT | /growl setup YOUR_IP YOUR_LOCAL_PASSWORD PORT | ||
== So... WTF is all this shit doing???? == | |||
BASICALLY. | |||
- Mumble waits for notifications from localhost... The problem is that weechat is running remotely on a redbrick server in DCU. | |||
- SSH -R is sending messages from the redbrick server back to our localhost. | |||
- Socat listens for message from redbrick (the SSH -R bit in step 2 there) to the port that Mumble is listening to on localhost. | |||
- On redbrick the weechat script is sending it's growl notifications to localhost | |||
- The socat instance on redbrick is listening for shit (grolw notifications) on localhost and sending it to the port that SSH -R above is looking for.. Thus actually sending it backwards through our SSH connection to our localhost where mumble gets it and pops up a nice little notification box. | |||