Revision history [back]

Don't you hate it that all the feedback you get for your xmpp etc. chat account authentication is that a little green light in the user interface either stubbornly stays off or finally comes on? I'm sure the operating system can't be so tight on resources that we couldn't get some kind of a more resonable error messages, like "internet connection not available", "unable to resolve host name xxx", "unable to connect to server xxx port yyy", "authentication failed for account zzz on server xxx". And I'm not even talking about the mysterious "account must be updated" message that you see only after reboots.

There seem to be many "can't get xmpp working" and similar discussion chains here in Together that would certainly benefit from proper error feedback.

Don't you hate it that all the feedback you get for your xmpp etc. chat account authentication is that a little green light in the user interface either stubbornly stays off or finally comes on? I'm sure the operating system can't be so tight on resources that we couldn't get some kind of a more resonable error messages, like "internet connection not available", "unable to resolve host name xxx", "unable to connect to server xxx port yyy", "authentication failed for account zzz on server xxx". And I'm not even talking about the mysterious "account must be updated" message that you see only after reboots.

Yes, you can use a debugger to see what's going on, but this requires some rather specialized knowledge of the protocols involved, and SSL makes things of course more difficult.

There seem to be many "can't get xmpp working" and similar discussion chains here in Together that would certainly benefit from proper error feedback.

Don't you hate it that all the feedback you get for your xmpp etc. chat account authentication is that a little green light in the user interface either stubbornly stays off or finally comes on? I'm sure the operating system can't be so tight on resources that we couldn't get some kind of a more resonable error messages, like "internet connection not available", "unable to resolve host name xxx", "unable to connect to server xxx port yyy", "authentication failed for account zzz on server xxx". And I'm not even talking about the mysterious "account "Tili on päivitettävä" ("Account must be updated" updated") message that you see only after reboots.

Yes, you can use a debugger to see what's going on, but this requires some rather specialized knowledge of the protocols involved, and SSL makes things of course more difficult.

There seem to be many "can't get xmpp working" and similar discussion chains here in Together that would certainly benefit from proper error feedback.

Don't you hate it that all the feedback you get for your xmpp etc. chat account authentication is that a little green light in the user interface either stubbornly stays off or finally comes on? I'm sure the operating system can't be so tight on resources that we couldn't get some kind of a more resonable error messages, like "internet connection not available", "unable to resolve host name xxx", "unable to connect to server xxx port yyy", "authentication failed for account zzz on server xxx". And I'm not even talking about the mysterious "Tili on päivitettävä" ("Account must be updated") message that you see only after reboots.

Yes, you can use a debugger to see what's going on, but this requires some rather specialized knowledge of the protocols involved, and SSL makes things of course more difficult.

There seem to be many "can't get xmpp working" and similar discussion chains here in Together that would certainly benefit from proper error feedback.