March 30th, 2013
Until IPv6 will have conquered the world (and maybe neither that time) DSL will continue to operate with dynamic IP address. I have the usual home server behind my home router and sometimes I need to access remotely. What’s my home router’s external IP?
Until now I used a script in my server that uploads via ftp the ip on this site, an easy supybot plugin I wrote to ask my IRC bot the IP, or used one of my remote access plugins and I stopped sending the IP via mail (too much fighting with Gmail spam filters).
My friend Riccardo Catto had the same problem and asked me to write together a simple plugin that fetchs the external IP from one of the many sites that provide that kind of service. A bit of libpurle magic and we came out with this ‘What’s my IP’ plugin. I use it with finch in my home server and every time I need to know my external IP I just write ‘ip’ in a chat with finch buddy and it answer with something like:
Current IP Address: X.X.X.X
…and I kiss the monitor to thanks it.
Easy but somewhat useful :)
December 14th, 2012
Another plugin thet exploits Instant Messaging to transfer data. This time I’ve implemented a port forwarding using NetCat that do all socket stuffs. The plugin simply encode and transfer data from local pidgin to the buddy’s pidgin. There another ncat instance connect to the host we want to reach. The bandwidth is… ehm… quite low (1 KB/s with default settings) but sometimes it’s useful to pass through NATs, firewalls, …
It’s very basic and the next step should be to implement a real socket server that accepts multiple connections keeping them distinct (At the moment you can tell ncat to accept several clients but the traffic is mixed up).
If you have time to waste take a look!
May 30th, 2011
Now… I know I’m a bit obsessed by this arguments but I was quite unhappy with ImVT. Having become aware of the work to reach a minimal stable state with ImVT I realized I don’t have enough time. I’d like to write a library that handles only issues terminal related (interpret signals, escape/control sequences, …) allowing you to avoid to use a GUI (Gnome VTE forces you to have a gui for your terminal emulator) and to work with a simplified interface to push input and read processed output in some friendly way (markup? XML/HTML?). I’d like to but… now I can’t (and I don’t know if I were able to!).
So the idea I’ve done this new plugin, less versatile but a little bit more robust and far far away easier to write! The final result is a kind of telnet via IM. If you’re unsatisfied with ImVT
take a look to ImRA
and please leave a feedback!
October 13th, 2010
a small variant of the first method to detect invisible buddies in Google Talk.
The first method consisted in starting a chat with the buddy we assumed invisible. If we got the message “[email protected] is offline and can’t receive messages right now.” then the buddy was offline but if didn’t appear any message then we could determine that our buddy was really invisible.
Now this bug has been fixed by Google but…
Let’s try to invite the invisible buddy in a group chat and see what happens…
In Pidgin this is quite easy: right click on the offline (invisible) buddy and click on “Start a chat”. This will start a group chat if the buddy is invisible.
Obviously this bug will have a short life and the method it’s not stealth (and difficult to apply to all buddies but not impossible) but for now…