IRC bots for Laziness, Impatience, and Continuous Deployment
eng.wealthfront.com
IRC bots for Laziness, Impatience, and Continuous Deployment
1–10 of 15 posts
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#2Interesting to see someone who is using IRC in this fashion. I personally have been an advocate of using XMPP in the same way. While IRC offers a good amount of features, XMPP provides the ability to scale and dive into multiple different realms. Just one example that comes to mind is constant updates from your XMPP bots, channels, etc. in a single location similar to Twitter, but for your development.
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#3Interesting to see someone who is using IRC in this fashion. I personally have been an advocate of using XMPP in the same way. While IRC offers a good amount of features, XMPP provides the ability to scale and dive into multiple different realms. Just one example that comes to mind is constant updates from your XMPP bots, channels, etc. in a single location similar to Twitter, but for your development.
You are so enterprisey! :)
We'll bridge protocols if we need to cross that, um, bridge.
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#4Interesting to see someone who is using IRC in this fashion. I personally have been an advocate of using XMPP in the same way. While IRC offers a good amount of features, XMPP provides the ability to scale and dive into multiple different realms. Just one example that comes to mind is constant updates from your XMPP bots, channels, etc. in a single location similar to Twitter, but for your development.
IRC is easy. Its a basic text protocol that requires a socket and some minimal parsing to work with. Whenever I use XMPP, its never that simple. The protocol is too verbose for its own good imho.
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#5Interesting to see someone who is using IRC in this fashion. I personally have been an advocate of using XMPP in the same way. While IRC offers a good amount of features, XMPP provides the ability to scale and dive into multiple different realms. Just one example that comes to mind is constant updates from your XMPP bots, channels, etc. in a single location similar to Twitter, but for your development.
IRC is easy . Its a basic text protocol that requires a socket and some minimal parsing to work with. Whenever I use XMPP, its never that simple. The protocol is too verbose for its own good imho.
Xmpp allows you to be a bit more secure and fine tune the usage. If your client or library doesn't actually make this simpler, something has failed.
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#6My complaint with IRC (and I freely admit that it could be that I am not using the "right" client) is that there is just this sea of text on the screen. There is very little formatting to speak of, and it reminds me of everyone talking at once on a conference call.
slighty off-topic: I am proud to say that I was introduced to Wealthfront via HN, and I was so impressed by their engineering blog that I went to their website. And it sounded cool, so I joined.
And ever since then, I continue to see some awesome things from them, and so far their investment-matchmaking service has paid off, too.
Win-win if I've ever heard one.
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#7This is exactly why I wrote https://github.com/thwarted/nodebot, as a I ran into problems scaling and securing things like supybot, and integrating it with shell scripts. nodebot is announce only, and doesn't join the channels (so your IRC server needs to be setup to allow that), and since it's not centralized, high traffic from one node/service that ends up getting rate throttled by the server doesn't delay messages from other nodes/services. Each machine has an identity, but it can be configured to have a different identity (because I'd rather that git messages come from "git" rather than from the machine that ran the hook).
We use it at yelp for monitoring all manner of system status. There's separate channels for scribe log processing, nagios alerts, code deployments, and load balancer status. Our git hooks announce when developers push and merges are happening, and who's branches are being deployed. We get announcements when config files change. And it's all on-demand, if you're not interested in seeing it, you don't need to join the channel, IRC is perfect for these kinds of updates.
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#8Earlier quoted context omitted.
IRC is easy . Its a basic text protocol that requires a socket and some minimal parsing to work with. Whenever I use XMPP, its never that simple. The protocol is too verbose for its own good imho.
Xmpp allows you to be a bit more secure and fine tune the usage. If your client or library doesn't actually make this simpler, something has failed.
Of course! All problems in computer science can be solved by another level of indirection!
More seriously, are you saying that SSL/TLS and SASL are both insecure?
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#9This is exactly why I wrote https://github.com/thwarted/nodebot , as a I ran into problems scaling and securing things like supybot, and integrating it with shell scripts. nodebot is announce only, and doesn't join the channels (so your IRC server needs to be setup to allow that), and since it's not centralized, high traffic from one node/service that ends up getting rate throttled by the server doesn't delay message…
Nice. Last.fm has a nice post at http://www.metabrew.com/article/how-we-use-irc-at-lastfm.
We also have separate channels for each message type. IRC is pub-sub, yay! Plus you can direct-message a bot and it will DM you back, to not pollute the channel you're currently in.
Do you have any bots that take commands? I think that's where it gets really useful.
Re: IRC bots for Laziness, Impatience, and Continuous Deployment
#10Earlier quoted context omitted.
IRC is easy . Its a basic text protocol that requires a socket and some minimal parsing to work with. Whenever I use XMPP, its never that simple. The protocol is too verbose for its own good imho.
Xmpp allows you to be a bit more secure and fine tune the usage. If your client or library doesn't actually make this simpler, something has failed.