Opened 10 years ago

Last modified 4 years ago

#8826 new enhancement

no default away message

Reported by: zorkerz Owned by: deryni
Milestone: Component: unclassified
Version: 2.5.5 Keywords:
Cc:

Description

The default away message in pidgin says "I'm not here right now". This makes some large assumptions about how people use the away settings. I propose the default away message be blank. Nothing more than away should be shown to others by default since this is the only message the user has explicitly selected.

Change History (15)

comment:1 Changed 10 years ago by deryni

  • Status changed from new to pending

The default idle-based autoaway message defaults to that. The global user-selectable Away status does not. Given that pidgin also defaults to use mouse and keyboard usage for idle reporting and auto-away determination it is likely that the user is in fact not at the computer anymore (or perhaps doing something like watching a movie which leaves them as unlikely to respond as being gone and in many ways does have them no longer present).

I see no harm in the default wording, and no real gain to be had from changing it.

comment:2 Changed 10 years ago by zorkerz

  • Status changed from pending to new

I see you are right then that its likely the user is gone. Still I think a blank default away message is most preferable. To get rid of the default away message I had to delete it and make a new blank message to prevent the default from being recreated every time I went idle. I could be in the minority here it is by no means a major issue.

comment:3 Changed 10 years ago by deryni

Actually, there may be slightly more here that needs looking at. I had assumed that by default we started with no status selected thus triggering the default message fall-back and that selecting the global Away status would avoid that. We may want to think about making that easier.

comment:4 Changed 10 years ago by datallah

A blank message would be less discoverable than the current default.

comment:5 Changed 10 years ago by Warlon

Less discoverable? It took me ages to find out how to disable that default message. I kept going through the settings looking for "default away message" setting. A blank text would be way better as a default.

comment:6 Changed 10 years ago by deryni

Discoverable in what sense? The user already can't see the default message in the preferences dialog. I was suggesting that we should give users an easier way then creating their own saved Away status to not use the default message.

No, a blank message would not be 'way' better, it would be in one sense better.

comment:7 Changed 10 years ago by craftyguy

I tend to agree with zorkerz. There should definitely be an easier way to completely disable auto responses while 'away'. I personally do not like the added 'pollution' to existing chat windows when I go idle and somebody sends a message, and it's just annoying.

comment:8 Changed 10 years ago by QuLogic

  • Owner changed from lschiere to rekkanoryo

comment:9 Changed 9 years ago by stevehanler

Personally, I'd prefer it to be blank. I'm using protocol plugins that update my Twitter and Facebook statuses to whatever my Pidgin status is and my Twitter account is getting quite a few "I'm not here right now" messages which I then have to go delete.

comment:10 Changed 9 years ago by deryni

  • Owner changed from rekkanoryo to deryni

Yeah, I'm going to change this so the global default Away status has no message and that we ship with a default Away status which has our current default message, and that status is set as the default idleaway status to use. Sound good to everyone?

comment:11 Changed 9 years ago by calhotdog007

When can we expect the fix to be released? This "I'm not here right now" feature does not make sense at all and annoys everybody I know who uses Pidgin.

And try google this: pidgin "i'm not here right now"

comment:12 Changed 9 years ago by bambamland

I totally agree, this default message not only makes no sense but is always popping out, even sometimes when going back to an "online" status. This should either be defaulted to "blank" or easily changeable in the configuration menu. Is there a configuration file we can change this in otherwise ?

comment:13 Changed 9 years ago by Hubird

I have not problem with the message being there after Pidgin has determined me to be away, the problem I have is that it does not disappear after my status is changed to online again.

comment:14 Changed 9 years ago by deryni

People who are seeing the away message remain after they come back and revert to an non-away status should file a new ticket about that, as that is a separate issue than what is being discussed here. Please check for an existing ticket about that, it is possible one exists (though I don't recall having seen one offhand.)

comment:15 Changed 4 years ago by tubaman

I run this script before launching pidgin to remove the bogus status messages:

#!/usr/bin/env python
"""Remove bogus statuses from pidgin's status.xml file"""
import sys
import os
import logging
import HTMLParser
import xml.etree.ElementTree as ET


def parse_status(status):
    state, = [c.text for c in status if c.tag == 'state']
    h = HTMLParser.HTMLParser()
    try:
        message, = [h.unescape(c.text) for c in status if c.tag == 'message']
    except ValueError:
        message = None
    return (state, message)


def is_bogus(status):
    state, message = parse_status(status)
    #if state == 'available' and message == "I'm not here right now":
    if message == "I'm not here right now":
        return True


def main(argv=None):
    if argv is None:
        argv = sys.argv
    logging.basicConfig(level=logging.WARN)
    status_path = os.path.join(os.environ['HOME'], '.purple', 'status.xml')
    logging.debug("parsing %r", status_path)
    tree = ET.parse(status_path)
    statuses = tree.getroot()
    assert statuses.tag == 'statuses'
    assert statuses.attrib['version'] == '1.0'
    statuses_seen = set()
    for status in statuses:
        logging.debug("checking %s", ET.tostring(status))
        assert status.tag == 'status'
        if parse_status(status) in statuses_seen:
            logging.debug("is redundant")
            statuses.remove(status)
        elif is_bogus(status):
            logging.debug("is bogus")
            statuses.remove(status)
        else:
            logging.debug("not bogus or redundant")
        statuses_seen.add(parse_status(status))
    tree.write(status_path)


if __name__ == '__main__':
    sys.exit(main())
Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!