Domain: bitlbee.org
Stories and comments across the archive that link to bitlbee.org.
Comments · 72
-
Re:Why discontinue it?
Hasn't been a week since I last talked to someone on ICQ (from my IRC client via Bitlbee)
-
Re:Obligatory XKCD
Multi-protocol clients are good stop-gap measures that do not require additional protocols.
I did that for a while, but kept getting frustrated at various problems in every multi-protocol client I tried. My solution was to ditch multi-protocol clients entirely and go back to using an IRC client to connect to Bitlbee, which is an IRC daemon that acts as a gateway to the various protocols via a plugin-based design. In addition to its own protocol support, it can even use libpurple (pidgin) plugins to cover things that aren't handled by Bitlbee or its own plugins. (List & documentation links here.)
I like this decoupled setup because I can configure all the accounts in one place without getting tied to a specific client. When/if I get frustrated with an IRC client, I can just close it and switch to a new client, enter one server's settings, and everything is set. It also gives me a consistent interface to all of them, and one that's still keyboard-friendly. Plus I really like how you can use private messages OR an in-channel "Name: message here" format to communicate with different users. The latter is especially useful because you can talk to different people on entirely different networks in a single window and see their replies in the same window.
Oh, and since it's IRC, it's also easy to use a bouncer like znc as a way to stay connected and receive "offline" messages even on protocols that don't support it or have problems with it. It's not perfect, but bitlbee has solved most of my problems with the various clients and protocols I've used.
-
Re:Obligatory XKCD
Multi-protocol clients are good stop-gap measures that do not require additional protocols.
I did that for a while, but kept getting frustrated at various problems in every multi-protocol client I tried. My solution was to ditch multi-protocol clients entirely and go back to using an IRC client to connect to Bitlbee, which is an IRC daemon that acts as a gateway to the various protocols via a plugin-based design. In addition to its own protocol support, it can even use libpurple (pidgin) plugins to cover things that aren't handled by Bitlbee or its own plugins. (List & documentation links here.)
I like this decoupled setup because I can configure all the accounts in one place without getting tied to a specific client. When/if I get frustrated with an IRC client, I can just close it and switch to a new client, enter one server's settings, and everything is set. It also gives me a consistent interface to all of them, and one that's still keyboard-friendly. Plus I really like how you can use private messages OR an in-channel "Name: message here" format to communicate with different users. The latter is especially useful because you can talk to different people on entirely different networks in a single window and see their replies in the same window.
Oh, and since it's IRC, it's also easy to use a bouncer like znc as a way to stay connected and receive "offline" messages even on protocols that don't support it or have problems with it. It's not perfect, but bitlbee has solved most of my problems with the various clients and protocols I've used.
-
Re:Relevancy?
Because alas, people don't care about that. If it's "easy", "free" and "works", they'll go for it. I guess whatsapp was among the first smartphone "apps" that delivered on all three points (in their respective quotation marks), and then it was simply a matter of inertia and network effect.
Yes, it's shit, but no, there's nothing one can do about it.
I arranged myself around it with bitlbee (linked against libpurple (for which a plugin exists that speaks the whapsapp protocol)).
-
Re:its interesting, but only if you dont use facebUnfortunately sometimes FB is the only feasible and free way to stay in touch with someone, especially when they are technically illiterate.
If there's no such person in your life, okay, but others have to deal with it.
Turns out there's a great way to deal with it, completely eliminating the need to use their website. On one end it speaks numerous IM protocols (incl. facebook chat (which is essentially XMPP)); on the user end it pretends to be an IRCd, offering a uniform way to chat via the various IMsits completely OT, but i still feel obligated to say it. Facebook isnt interested in you as a person, theyre interested in you as a product.
Yes. But stale. It doesn't even sound smug anymore, can we finally stop pointing this out? Everyone knows it already.
-
Re:Come back
And I love IRC. But I still need to communicate with people who are on other messaging systems, which is why I love BitlBee too.
-
Re:One of the Unwashed Masses
``Their compatability with 3rd party messengers SUCKS''
This is a problem with all proprietary instant messaging services. Which is why I still use IRC. All features are documented, so if you want to interoperate, you can. There is a plethora of clients to choose from. And you can actually chat with people on the large IM networks, too (through BitlBee).
-
Re:Bravo
And if that's not your thing, perhaps BitlBee is (IRC interface to various IM protocols, including some public servers free for use).
-
Re:Russia toobitlbee ftw!
BitlBee brings IM (instant messaging) to IRC clients. It's a great solution for people who have an IRC client running all the time and don't want to run an additional MSN/AIM/whatever client. BitlBee currently supports the following IM networks/protocols: XMPP/Jabber (including Google Talk), MSN Messenger, Yahoo! Messenger, AIM and ICQ.
-
Re:lots of ideas- IRC chatting with EPIC4 or Irssi - I know IRC doesn't use a lot of bandwidth, but every little bit helps - Instant messaging with TTY clients - Centericq does some protocols - Pork for AIM - Cabber or Imcom for Jabber - These are both crashy I'm afraid - There might be a text version of Gaim or Pidgin Try Bitlbee.
-
Re:AOL's passive aggressive attention to IM
I use IRC because it's simple, and because I can easily run it anywhere that I like. Typically, I run it in a screen on my colo. I've never found a satisfactory IM client that runs in a console, so I've never much been a fan of them.
I don't usually plug my own product, but maybe BitlBee is what you're looking for. At least it has exactly the UI you need. :-) -
Re:DIfferent use casesEmail is still king. I can use attachments So can many IM protocols. it is platform independent (which IM is most-definitely NOT) What prevents developers from implementing, say, libpurple on the platforms that you think can't use instant messaging? Besides, if you have IRC then you have IM.
-
Yes it does
-
Re:Well nobody's really chimed in with IM yet
Better yet, just use a public bitlbee server on IRC. Can't get more lightweight than an app that isn't using any resources whatsoever. At least none of your resources.
-
Re:With so many alternatives..So use a jabber server that has transports to legacy networks.
But since you like IRC you might have use for http://www.bitlbee.org/ I'm aware of these possibilities, but in any case to communicate with the people using only MSN, I need to connect to the network one way or another. Yeah, I can do it indirectly through the methods you described, but I would still be using the MSN network in the end, I would still be affected with this censoring since it's a server side thing, and Microsoft would still be reading my messages ;) -
Re:With so many alternatives..
So use a jabber server that has transports to legacy networks.
But since you like IRC you might have use for http://www.bitlbee.org/ -
Use text-based IRC with an IM Gateway (Bitlbee)
With a Bitlbee gateway running on one of your own machines (or even a public gateway) you can use pretty much any IRC client you like!
-
Re:bsflite
You should consider BitlBee, an IRC gateway for all the major networks. All you need is an irc client like irssi, and a bitlbee server, either setup on your own PC, or a public bitlbee server.
BitlBee Official page
BitlBee on Wikipedia -
Re:pidgon/gaim is the only open source one, right?
Adium is open source but Mac only (based on libpurple). meebo isn't open source, but is also based on libgaim (now libpurple). Finch is Pidgin for the console. And then there's always the possibilities of using Jabber with a transport or using Bitlbee.
-
Re:The Hell with Games...
..what I want is an affordable DS cart loaded up with Firefox, a lightweight mail client (put the keyboard on the touchscreen), a lightweight AIM app, telnet/ssh, and maybe even an IRC client. Give me that, and I won't need an iPhone.
Firefox is impossible because the DS has too little memory to run it.
But you can have links/telnet/ssh/bitchX IRC with dslinux. A mail client (mutt or mailx) may be added in the future. If you have a host to run bitlbee on you can have AIM via bitchX.
You'll need to buy a Supercard or an M3 (they cost small bit more than a DS game), and possibly a NoPass device (don't know how much they are right now but they should cost less than Supercard/M3). Check the dslinux wiki for more information.
-
Re:Too Generic.
Have you tried bitlbee? It supports most protocols, and you connect to it using your IRC client.
It even has webcam support.
I've been using it for a while, and it's very stable. It's better than any other client i've used.
~kohaku -
Re:Too Generic.
Have you tried bitlbee? It supports most protocols, and you connect to it using your IRC client.
It even has webcam support.
I've been using it for a while, and it's very stable. It's better than any other client i've used.
~kohaku -
Re:IRC is dead. Use Jabber.
Do what I do. Use irssi.
http://www.bitlbee.org/ -
Re:another good one
That's why I use Trac as my bug tracker. It's a bit like a wiki, it works without any kind of account. Unfortunately spammers noticed that too, I have to see what I can do about that.
:-( -
Re:SSH blocked to?
See also: bitlbee.
-
Re:Impressive
You might be interested in Jabber's Multi-User Chat which let people join "chat rooms" on any Jabber server. One of the interesting features it has over IRC is the "history discussion delivery on join".
BTW, you can connect to Jabber (and most IM services) through any IRC client.
-
extend its lifespan considerably?
Linux 2.4.28-gentoo-r9 i686 Pentium II (Deschutes) GenuineIntel GNU/Linux. Runs apache2, mail (postfix+clamav+amavisd-new+spamassassin), 74 http://www.bitlbee.org/ users and some "other services". Should probably upgrade someday. However, I heard a rumor: If it's not broken, don't fix it.
-
BitlBee
I use BitlBee for talking to MSN/Yahoo!/AIM/ICQ/Jabber . Because BitlBee is a IRC to other chat networks gateway, it's possible to connect with an irc client for your mobile phone to some public server. I use jmIrc as IRC client. You only pay for GPRS or UMTS data. I bet this IM thingy will be more expensive.
-
Talking about googleOfftopic, but about google:
It looks like google opened op gtalk to the other public jabber networks. It's possible to talk server-to-server now!
afaik the Bitlbee team got the heads up. -
Console Alternative to Gaim
I am fond of BitlBee. It's an IRC-to-IM gateway. When on the console, I can have my IM sessions in the same app (irssi in my case) as my IRC sessions.
-
Bitlbee
Chatting about beta's of gaim, but no news about the 1.0 release of http://www.bitlbee.org/.
:-( -
Re:Good protocol is useless, if
One project you might consider having a look at is Bitlbee it supports Jabber, MSN, ICQ, AIM, Yahoo (and since it is doing jabber, googletalk) but you can talk through your irc client. It also works like the jabber server. Just another option. There is no client more configurable than the various irc clients, so as far as flexiblity I think you can have it all with this solution.
:) - Mind -
If you are allready on IRC...
...then bitlbee is a great way to use your existing IRC client (mirc, irssi, xchat or whatever) to access jabber, google chat, msn, yahoo and oscar (aim/icq). It's not perfect, it will not allow you to send or receive files (yet), but if you're fed up with bloated GUI clients, and are allready using an IRC client, it may be the best choice. At least you'll have all your chatting in one client.
-
BitlBee + rcirc
-
Bitlbee changed my life
Bitlbee is an irc gateway to all the messenger clients. This means that I can communicate with my MSN contacts over (what appears to me to be) irc.
This means I can run screen+irssi+bitlbee on my home server, and will never disconnect from any of my msn,aim,irc,etc and will be able to rejoin my clients from wherever in the world I am (very important for a laptop user like myself).
It organized all of my streams of communication into one single, easy, clean interface (irssi, really, but still) and allows me to manage my time much more efficiently then before. (not to mention the benefits of never logging off, so people can send you messages and you can pick them up without having to be "on line" at that moment.
I'm looking forward to naming my firstborn after it. -
i use all at once.
just get http://bitlbee.org/ (with irssi on a screen, yeah!).
or miranda.. -
BitlBee
Also viable alternative for IRC users, BitlBee: http://www.bitlbee.org/
It converts ICQ, Yahoo, MSN, Jabber protocols to IRC. -
Text mode IM has its advantages
I use bitlbee, an IRCd that talks to the major IM networks in text format. Access this in irssi (any tty irc client will do). Leave it running 24/7 on a server in a dtach (or screen) instance. Attach to it from anywhere on earth. See in the logs the time your buddies came and went, and any messages you missed. Chat from one machine, move to another and continue the conversation. At home on my LAN, I run the trigger script, and have it play sounds on all my PCs in the house when I get a message.
-
Re:gaim works for me, but loses ground from here
Also worth to mention BitlBee: http://bitlbee.org/
It converts ICQ, Yahoo, MSN, Jabber to IRC protocol. You need just standard IRC client to talk with your *IM friends! -
Re:gaim works for me, but loses ground from here
Bitlbee is much cooler than centericq. It communicates IM using IRC as a gateway.
screen+irssi --> bitlbee -
command line nut
yes, I'm a command line nut, but my favorite is actualy bitlbee, available at http://www.bitlbee.org/. It's an irc gateway for AOL, ICQ, jabber etc.
-
Re:Could some IM maker finally allow roaming..
at least your contact/buddy list is stored server side. anyway, heres an answer,
http://thekonst.net/centericq
ssh home when you want it.
if you want to keep it running, see http://www.gnu.org/software/screen/screen.html
also see http://gaim.sf.net/
gaims chat logs can simply be copied into eachother since each "conversation" is a seperate file.
its probably runs on all the platforms you need (the latest always compiles out of the box on os x with fink)
there are a few remote file shares you can use, some of which work over ssh, and thus your prefs/logs etc
can be kept with them. or you can simply script your client to sync whenever it starts / stops / whenever,
which would thus be transparent (and probably faster with something like rsync)
so anyway, yea, its sad that in this day and age, we dont have software working together much, but at least
you can work around it. centericq is a pretty simple way to not have to worry about any of it, all you need
is ssh. thus the beuty of remote apps. if you dont like centericqs interface, check out http://bitlbee.org/
to use an irc client instead. -
Re:A brief and largely incorrec summary of things
Dude, the answer to everything is Bitlbee.
-
emacsThe best developer's IDE is emacs, either GNU Emacs or XEmacs. It is extremely customisable and infinitely extensible. The entire thing is written in its own dialect of Lisp (called elisp), and so you can add just about any functionality to it.
There are multiple mail readers written for emacs; there is a news reader; a few web browsers; an interface to IRC (and with bitlbee, AIM/Yahoo/Jabber &c.); music players; calendaring.
The programming modes are excellent; the interface to make and gdb is second to none; the integration with a developer's environment is superb.
emacs is the r0x0r:-)
-
Precisely
This is precisely why I stay away from P2P software and use bitlbee for my IM handling.
I simply do not trust that the corporate authors of these infinitely connected clients are also exhaustively pedantic about fireproofing their code. As real truth would have it, OSS clients have historically been more resilient than their commercial counterparts.
The tin foil side of me thinks that the corporations actually like having security holes in their clients. <conjecture> The head of the MS Messenger department has this brother who married this girl whose younger brother owns stock in this company which specializes in "desktop advertising". </conjecture> Not saying that it was on purpose, but somehow that project absolutely had to be shipped by $DATE, even though the security audit wasn't quite complete. Coincidence? Probably.
(NOTE: This is a repost because there are crack-whore trolls with mod points that modded the first one flamebait, the second one redundant, and the third one finally received some semblance of a human response... WTF? Hey mod-trolls... QUIT STALKING ME!) -
Precisely
This is precisely why I stay away from P2P software and use bitlbee for my IM handling.
I simply do not trust that the corporate authors of these infinitely connected clients are also exhaustively pedantic about fireproofing their code. As real truth would have it, OSS clients have historically been more resilient than their commercial counterparts.
The tin foil side of me thinks that the corporations actually like having security holes in their clients. <conjecture> The head of the MS Messenger department has this brother who married this girl whose younger brother owns stock in this company which specializes in "desktop advertising". </conjecture> Not saying that it was on purpose, but somehow that project absolutely had to be shipped by $DATE, even though the security audit wasn't quite complete. Coincidence? Probably.
(NOTE: This is a repost because there are crack-whore trolls with mod points that modded the first one flamebait and the second one redundant... WTF? Hey trolls... QUIT STALKING ME!) -
Precisely
This is precisely why I stay away from P2P software and use bitlbee for my IM handling.
I simply do not trust that the corporate authors of these infinitely connected clients are also exhaustively pedantic about fireproofing their code. As real truth would have it, OSS clients have historically been more resilient than their commercial counterparts.
The tin foil side of me thinks that the corporations actually like having security holes in their clients. <conjecture> The head of the MS Messenger department has this brother who married this girl whose younger brother owns stock in this company which specializes in "desktop advertising". </conjecture> Not saying that it was on purpose, but somehow that project absolutely had to be shipped by $DATE, even though the security audit wasn't quite complete. Coincidence? Probably. -
YES!
I hope this is a sign of great things to come. I know that the GAIM, Bitlbee, and other crowds will hear this as music to our ears.
-
Use BitlBee
I feel completely the same way.
Have you tried BitlBee? It lets you access the lesser networks from IRC. In my experience, it has been rock solid. -
Re:Greasy Kids Stuff
Just use bitlbee.
It's an IRC to IM gateway, and allows you to check for MSN/ICQ/AOL messages instead of being disturbed by it while doing something...