Growl - Revision history

Graggle at 00:35, 22 April 2026

2026-04-22T00:35:50Z

← Older revision		Revision as of 00:35, 22 April 2026
Line 72:		Line 72:
	This is what it looks like		This is what it looks like
	weechat ---> socat on redbrick ---> SSH -R ---> socat on localhost ---> mumble		weechat ---> socat on redbrick ---> SSH -R ---> socat on localhost ---> mumble
			[[Category:Archive]]

Dregin at 14:51, 27 April 2009

2009-04-27T14:51:01Z

← Older revision		Revision as of 14:51, 27 April 2009
Line 12:		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 46:		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 67:		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 (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.		- 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		This is what it looks like
	weechat ---> socat on redbrick ---> SSH -R ---> socat on localhost ---> mumble		weechat ---> socat on redbrick ---> SSH -R ---> socat on localhost ---> mumble

Dregin at 16:42, 26 April 2009

2009-04-26T16:42:14Z

← Older revision		Revision as of 16:42, 26 April 2009
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)

Dregin: /* So... WTF is all this shit doing???? */

2009-04-26T16:28:26Z

So... WTF is all this shit doing????

← Older revision		Revision as of 16:28, 26 April 2009
Line 65:		Line 65:
	- 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

Dregin at 16:21, 26 April 2009

2009-04-26T16:21:34Z

@@ 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.
 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

Dregin: 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...

2009-04-26T16:14:16Z

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...

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 someone hilights my nick or PMs me in weechat (there're probably similar scripts for IRSSI, but fuck that heap of shit)

I'm using a nice little program in ubuntu called mumble for my notifications. Get it [[http://www.mumbles-project.org/download/ here]].

Once you've installed and launch it an icon should appear over there beside your clock.

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

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

sudo apt-get install socat

Once that's done you need to start socat locally:

socat TCP-LISTEN:PORT,reuseaddr,fork UDP:127.0.0.1:9887 &

Then log into redbrick with a port redirect going on:

ssh USER@login.redbrick.dcu.ie -R PORT:127.0.0.1:PORT

Once you've logged into redbrick another instance of socat needs to be launched (I'm told committee require permission for network services to be run, but since when has anyone ever given a shit about these things??????????????????/) tsocks is in there thanks to DCU's proxy.

I run this inside a screen instance before launching weechat. If weechat's already running you can just do ctrl+z to suspend it, run the following command and then run 'fg' to bring weechat back from the dead.

tsocks socat UDP-LISTEN:9887,reuseaddr,fork TCP:127.0.0.1:9996 &

Everything's ready to go now, so just launch weechat (my build of dev version 0.2.7 is available at /home/associat/d/dregin/weechat/bin/weechat-curses)

Depending on the version of weechat you're running do either:

For 0.2.7
wget http://www.mysticcoders.com/tools/downloads/growl-net-notify.pl -O ~/.weechat/perl/autoload/growl-net-notify.pl

OR for 0.2.6
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
/perl load growl-net-notify.pl

OR

/perl load growl-net-notify-0.2.6.pl

/help growl

/growl setup YOUR_IP YOUR_LOCAL_PASSWORD PORT