So, I know this is a big thing, but with the new AIM out, with voice over ip and sounds and images and all, could we build that into gAIM(with heavy borrowing from other free software projects of course)? I know its a tall order, but do we plan on keeping up with the commercial releases feature set?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Don't forget file transfers! I'm told that all three of these (file transfers, direct connect and voice chat) run over the same protocol, Buddy Rendesvous. This requires switching from TOC to OSCAR-- as of right now, gaim's oscar support barely compiles, and doesn't work very well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, we are in luck (sort of). TOC has a few things that could help us out: toc_rvous_accept and toc_rvous_cancel (sent from us), and RVOUS_PROPOSE (sent from the server). I managed to get gaim to receive files from a few AIM users, and got them to think I could do anything a normal AIM user can do (even though I couldn't actually do it). All that needs to happen now is the rest of it get implemented. I'm working on the ability to send a file to an AIM user now; hopefully I'll have that done Real Soon Now (tm).
There's another command we can send, toc_rvous_propose, but the PROTOCOL document says it's not implemented yet. If it were implemented, then gaim users could request the transfers, which means gaim users could transfer between themselves. As it is now, if it's not implemented, AIM users have to do all the requesting.
Looks like we don't need Oscar as much as previously thought.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, I know this is a big thing, but with the new AIM out, with voice over ip and sounds and images and all, could we build that into gAIM(with heavy borrowing from other free software projects of course)? I know its a tall order, but do we plan on keeping up with the commercial releases feature set?
Don't forget file transfers! I'm told that all three of these (file transfers, direct connect and voice chat) run over the same protocol, Buddy Rendesvous. This requires switching from TOC to OSCAR-- as of right now, gaim's oscar support barely compiles, and doesn't work very well.
Well, we are in luck (sort of). TOC has a few things that could help us out: toc_rvous_accept and toc_rvous_cancel (sent from us), and RVOUS_PROPOSE (sent from the server). I managed to get gaim to receive files from a few AIM users, and got them to think I could do anything a normal AIM user can do (even though I couldn't actually do it). All that needs to happen now is the rest of it get implemented. I'm working on the ability to send a file to an AIM user now; hopefully I'll have that done Real Soon Now (tm).
There's another command we can send, toc_rvous_propose, but the PROTOCOL document says it's not implemented yet. If it were implemented, then gaim users could request the transfers, which means gaim users could transfer between themselves. As it is now, if it's not implemented, AIM users have to do all the requesting.
Looks like we don't need Oscar as much as previously thought.