Someone brought this up on a forum that I track and it reminded me that I've
wondered about it for a long time now.
At the moment, when you delete a contact, they go away, but next time you
register a transport to the same service they come back. This causes an
effect I used to call "living dead"... contacts which haven't been in use for
years suddenly spring back to live and we have no way to get rid of them.
The transport obviously only remembers as long as the spool file still
exists, which is all it can be expected to do in the circumstances.
But... I've never understood why when I delete a legacy contact, the transport
can't also remove that contact from the underlying service so that I don't
get nagged about them ever again. And in this day and age, people who use
transports don't use the "native" legacy client at all... so effectively we
have no way to delete those contacts at all.
Would it be reasonable to request such a feature? I assume the protocol for
deleting contacts on the legacy services isn't much more hairy than the
protocol for adding them in the first place. :-)
TX
--
Email: Trejkaz Xaoza <[EMAIL PROTECTED]>
Web site: http://trypticon.org/
Jabber ID: [EMAIL PROTECTED]
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://modevia.com/pipermail/py-transports/attachments/20050803/ce357972/attachment.pgp
From [EMAIL PROTECTED] Tue Aug 2 14:29:28 2005
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Tue Aug 2 14:29:25 2005
Subject: [py-transports] Deleting contacts
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Well speaking for PyAIM and PyICQ, it's supposed to do that. ;D If it's
not, it's a bug. hehehe (it's supposed to delete them from ICQ/AIM, not
just locally)
Daniel
--
"The most addictive drug in the world is music."
- The Lost Boyz
>
> Someone brought this up on a forum that I track and it reminded me that
> I've
> wondered about it for a long time now.
>
> At the moment, when you delete a contact, they go away, but next time you
> register a transport to the same service they come back. This causes an
> effect I used to call "living dead"... contacts which haven't been in use
> for
> years suddenly spring back to live and we have no way to get rid of them.
> The transport obviously only remembers as long as the spool file still
> exists, which is all it can be expected to do in the circumstances.
>
> But... I've never understood why when I delete a legacy contact, the
> transport
> can't also remove that contact from the underlying service so that I don't
> get nagged about them ever again. And in this day and age, people who use
> transports don't use the "native" legacy client at all... so effectively
> we
> have no way to delete those contacts at all.
>
> Would it be reasonable to request such a feature? I assume the protocol
> for
> deleting contacts on the legacy services isn't much more hairy than the
> protocol for adding them in the first place. :-)
>
> TX
>
> --
> Email: Trejkaz Xaoza <[EMAIL PROTECTED]>
> Web site: http://trypticon.org/
> Jabber ID: [EMAIL PROTECTED]
> GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
