cocoaforge

Does anyone else get realy annoyed by the Adium connection errors? Every time I put my computer to sleep and wake it up, there is the error again waiting on my screen. Here are a few thoughts on the subject:

- iChat does one thing well: it keeps track of if you are connected to the internet or not and responds accordingly. You either see your contact list or you don't. It's all automatic.

- I live my life online. I KNOW when I'm not connected, and I would imagine most people are the same. I don't need Adium popping up a message for each and every service that can't connect (Okay, I get it - NONE OF THEM CAN CONNECT!)

- Why can't I turn off the error messages? Oh I've tried so hard. Is there a secret way to do it?

- I have never seen an adium connection error message and learned something I didn't already know. I have never seen an Adium connection error message and not been annoyed.

- The "error" message should only consist of your contacts disappearing. No contacts = not connected. I know this doesn't take care of people who only have a contact or two as it could simply mean their contacts are offline - but how about your contact list is replaced with a single contact that says "offline?"

- If Adium could not only disconnect, but reconnect automatically, I would pee my own pants.

Please, let me hear your input. Any devs out there want to tackle this?

EDIT: I do see a lot of other posts on this topic - but I have not seen one with a solution yet, or anything that says any of the devs think this is an issue or not.

It's not fully optimal, but theatrics don't help your situation.

Super secret solution: download the source code, fix the issue, submit a patch.

I searched around to see if there was a ticket for this issue but couldn't find one. Are the devs interested in changing it, making an option, or something? Or is it the way it is by design?

Sorry about the theatrics - I just don't get enough attention in real life.

sam-i-am wrote:I searched around to see if there was a ticket for this issue but couldn't find one. Are the devs interested in changing it, making an option, or something? Or is it the way it is by design?

Sorry about the theatrics - I just don't get enough attention in real life.

There's pretty much no chance of an 'option' because the current setup is suboptimal, and introducing options to patch bugs isn't Right.

Note that in *my* experience, Adium detects my Internet connection status and reliably disconnects when it drops and reconnects when it comes back up. I believe that most people who see otherwise have odd network configurations which trick OS X into thinking they are connected.

I'm absolutely interested in seeing our connection / connection error handling be improved, including a progressive retry system (reconnect, wait 2 seconds, reconnect, wait 5 seconds, reconnect, wait 10 seconds, reconnect, wait 30 seconds, etc.) rather trying 5 times in a row and stopping completely.

As Brian said, this'll be most likely to happen in a near timeframe if someone does it.

evands wrote: Note that in *my* experience, Adium detects my Internet connection status and reliably disconnects when it drops and reconnects when it comes back up.

Same here.

This is the only major reconnect problem I've experienced in a while: http://trac.adiumx.com/ticket/6710

I had this issue, I think having Parallels desktop installed causes it (it creates a couple of network connections that always appear connected in the network preference pane)

hardstyle wrote:I had this issue, I think having Parallels desktop installed causes it (it creates a couple of network connections that always appear connected in the network preference pane)

Oooh, interesting thought. I wonder if we're detecting them as "live".

(note: I know little/nothing about our network detection code)

Catfish_Man wrote:

hardstyle wrote:I had this issue, I think having Parallels desktop installed causes it (it creates a couple of network connections that always appear connected in the network preference pane)

Oooh, interesting thought. I wonder if we're detecting them as "live".

(note: I know little/nothing about our network detection code)

I think it's mostly CFNetwork stuff. Durin was mentioning that today.