| Summary: | progressive auto away states | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | _ <praseodym+kdebugzilla> |
| Component: | libkopete | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | wishlist | CC: | kdebugs-337 |
| Priority: | NOR | ||
| Version First Reported In: | 0.40.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
_
2003-09-09 15:58:59 UTC
*** Bug 63961 has been marked as a duplicate of this bug. *** On a similar vein, it would be nice if Kopete made use of Jabber's "Extended Away" status. There could be two auto away timeouts -- the first timeout changes the status to "Away", and the second timeout (which would be longer) changes the status to "Extended Away". Michael: the infrastructure to use this has since been added. *** Bug 99247 has been marked as a duplicate of this bug. *** ... culminating in an optional disconnect. Dear user, unfortunately Kopete is no longer maintained. Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat. |