Jump to content

Growl: Difference between revisions

184 bytes added ,  27 April 2009
no edit summary
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:


For a WTF IS GOING ON bit scroll to the bottom.
For a WTF IS GOING ON bit scroll to the bottom.
[[http://www.redbrick.dcu.ie/~dregin/pix/weeget_02.png Screenshot]]


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 10: Line 12:


  - Right click it and choose preferences.
  - Right click it and choose preferences.
  - Enable network notifications
  - Enable network notifications.
  - Set a password.
  - Set a password.


You may need to forward UDP port 9887 to your local machine on your router.
You may need to forward UDP port 9887 to your local machine on your router.


On your local machine you're gonna have to install socat
On your local machine you're gonna have to install socat:
 


  sudo apt-get install socat
  sudo apt-get install socat
Line 44: Line 45:
  wget http://www.mysticcoders.com/tools/downloads/growl-net-notify-0.2.6.pl -O ~/.weechat/perl/autoload/growl-net-notify-0.2.6.pl
  wget http://www.mysticcoders.com/tools/downloads/growl-net-notify-0.2.6.pl -O ~/.weechat/perl/autoload/growl-net-notify-0.2.6.pl


load the plugin with
Load the plugin with:
 
  /perl load growl-net-notify.pl
  /perl load growl-net-notify.pl


Line 65: Line 67:
  - Socat listens for message from redbrick (the SSH -R bit in step 2 there) to the port that Mumble is listening to on 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
  - 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.
  - The socat instance on redbrick is listening for shit (growl 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.
 
This is what it looks like
weechat ---> socat on redbrick ---> SSH -R ---> socat on localhost ---> mumble
138

edits