Linked by AndrewZ on Mon 14th Jun 2010 13:40 UTC
Thread beginning with comment 430430
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: A topic near & dear...
by mala2 on Thu 17th Jun 2010 09:18
in reply to "RE[2]: A topic near & dear..."
IMO, the interesting thing about about im_kit/Caya isn't the fact that it's a multi-protocol IM client (yes, those are a dime-a-dozen) - but the way it's implemented. Specifically, the way that makes full use of Haiku's unique/interesting features.
Well, AFAICT from a user perspective caya is a pretty "normal" multi-protocol IM client. While it seems to reuse some of the IMkit's code, it is not resurrecting the IM kit approach - which I find really sad. Don't get me wrong! It's great that a modern IM client is developed at all, and as non-developing, non-paying user I really shouldn't complain. But for me the IM kit was the prime example of Be-ness.
RE[4]: A topic near & dear...
by plfiorini on Thu 17th Jun 2010 09:41
in reply to "RE[3]: A topic near & dear..."
IM Kit was really a mess... Everything could be replaced with another component that did the same thing, even the deskbar icon. That was horrible IMHO kind of Linux stuff
Caya offers just one chat client that works.
Eventually, Caya will export contacts to People file to make IM Kit users happy or maybe a People Kit that apps can use to find or create People file for contacts and add information to them!
RE[4]: A topic near & dear...
by StephenBeDoper on Thu 17th Jun 2010 20:06
in reply to "RE[3]: A topic near & dear..."
"
IMO, the interesting thing about about im_kit/Caya isn't the fact that it's a multi-protocol IM client (yes, those are a dime-a-dozen) - but the way it's implemented. Specifically, the way that makes full use of Haiku's unique/interesting features.
IMO, the interesting thing about about im_kit/Caya isn't the fact that it's a multi-protocol IM client (yes, those are a dime-a-dozen) - but the way it's implemented. Specifically, the way that makes full use of Haiku's unique/interesting features.
Well, AFAICT from a user perspective caya is a pretty "normal" multi-protocol IM client. While it seems to reuse some of the IMkit's code, it is not resurrecting the IM kit approach "
Ah. I hadn't use it before and assumed, incorrectly, that it was just im_kit under a new name.
- which I find really sad.
Definitely agreed.
Don't get me wrong! It's great that a modern IM client is developed at all, and as non-developing, non-paying user I really shouldn't complain. But for me the IM kit was the prime example of Be-ness.
Completely agreed.
The im_kit was responsible for the last example I can think of where something *positive* happened as a result of the Law of Unintended Consequences.
(warning: anecdote-ahoy)
I had been setting up MSN/passport accounts for a local business, and I'd been testing them with GAIM (cum Pidgin) in Windows. When I got home and hopped onto my BeOS machine, which ran im_kit at the time, I had to write an EMail one of the people I had setup IM accounts for.
I had a bit of a "WTF" moment when BeMail auto-completed the address, even though I'd never corresponded with that person before. Then it dawned on me: im_kit had automatically download the new contacts that GAIM had saved to the server, saved them as Person files - and because I'd used their EMail addresses for the passport usernames, they were all in my address book automatically.
It basically gave me (to use current buzzwords) integration with cloud storage for contact info, with automatic offline synchronization. And a few years before the terms "cloud storage/computing" were coined.





Member since:
2005-07-06
Thanks. I hadn't heard the name "Caya" before, didn't realize it was the continuation of the im_kit.
IMO, the interesting thing about about im_kit/Caya isn't the fact that it's a multi-protocol IM client (yes, those are a dime-a-dozen) - but the way it's implemented. Specifically, the way that makes full use of Haiku's unique/interesting features.
It was fairly well-known within the Haiku/BeOS community when it was still in active development (admittedly that hasn't been the case since 2006 or thereabouts).
Don't get me wrong, NetPenguin is probably my sentimental favourite FTP client. But the lack of a queue can be a problem when transferring a large number of files - E.g. if you're uploading a complex web-based application. If one file fails to transfer, then you have to start the whole transfer over again (as opposed to just re-queuing the files that failed to transfer).