Unsupported Status Problem
Posted: Sat Mar 11, 2006 6:09 am
Found something a bit troublesome:
As you know, different clients support different levels of tweaking one's status. From what I've seen, AIM is the most limited, and it was in dealing with AIM that I figured out that Adium does not let me know what I am actually projecting to the world.
I have a status that sets me to Invisible, and I was curious as to whether Adium somehow spoofed the server, or if I was setting myself to Away, or what. So, I set it and asked a friend what he saw. Adium was telling me that I was invisible, when in fact I was fully visible and listed not as Away, but Available. Ick.
I only recently got my mac, and Adium is my mac answer to my PC multiclient IM program, Trillian. Overall, it is much more customizable, which is why it surprises me that it does not include a feature that Trillian does- the ability to set status specifically for each service when creating an away state. It only allows me to choose the options that will really work for that service (Available or Away on AIM, for example), but I can choose different states in different clients for a single Away state, picking the most effective combination for what I want to accomplish.
As it is, I have to use setups specifically designed for AIM to avoid leaving myself completely out in the open, and I am worried that there might be other things I think I've set that are not going across because the client doesn't really allow them.
I would really like it if, at the least, when I attempt to set a status and I don't get the effect I intended (e.g., trying to go Invisible in AIM), Adium not cheerfully act as though it worked, showing me an inaccurate status icon. Is there any way to keep this from happening?
It would also be nice to be able to set per client status messages, but it is so easy to set the individual accounts that I am not as worried about that as I am about accurate feedback on what's going on. Limiting the options to what's really possible and maybe adding some intelligent dithering when the selected option isn't possible would really help, though.
FF
As you know, different clients support different levels of tweaking one's status. From what I've seen, AIM is the most limited, and it was in dealing with AIM that I figured out that Adium does not let me know what I am actually projecting to the world.
I have a status that sets me to Invisible, and I was curious as to whether Adium somehow spoofed the server, or if I was setting myself to Away, or what. So, I set it and asked a friend what he saw. Adium was telling me that I was invisible, when in fact I was fully visible and listed not as Away, but Available. Ick.
I only recently got my mac, and Adium is my mac answer to my PC multiclient IM program, Trillian. Overall, it is much more customizable, which is why it surprises me that it does not include a feature that Trillian does- the ability to set status specifically for each service when creating an away state. It only allows me to choose the options that will really work for that service (Available or Away on AIM, for example), but I can choose different states in different clients for a single Away state, picking the most effective combination for what I want to accomplish.
As it is, I have to use setups specifically designed for AIM to avoid leaving myself completely out in the open, and I am worried that there might be other things I think I've set that are not going across because the client doesn't really allow them.
I would really like it if, at the least, when I attempt to set a status and I don't get the effect I intended (e.g., trying to go Invisible in AIM), Adium not cheerfully act as though it worked, showing me an inaccurate status icon. Is there any way to keep this from happening?
It would also be nice to be able to set per client status messages, but it is so easy to set the individual accounts that I am not as worried about that as I am about accurate feedback on what's going on. Limiting the options to what's really possible and maybe adding some intelligent dithering when the selected option isn't possible would really help, though.
FF
