ACM SIGCHI General Interest Announcements (Mailing List)


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
1.0 (1.0)
"ACM SIGCHI General Interest Announcements (Mailing List)" <[log in to unmask]>
"Kellogg S. Booth" <[log in to unmask]>
Sun, 24 Jul 2016 17:57:01 -0500
Bill Hefley <[log in to unmask]>
Bill Hefley <[log in to unmask]>
text/plain; charset=utf-8
text/plain (48 lines)
An even simpler thing to fix is to say what the CFP is for, unless you only want those insiders who already know what that acronym of alphabet soup means. I get these announcements for, say for example, the ACKEMEEE conference and nowhere in the message does it ever say in WORDS what the conference is. Think about your users!

Bill Hefley, PhD
Senior Member, ACM
Founding Editor, interactions
Clinical Professor, University of Texas at Dallas

Sent from my iPad

> On Jul 24, 2016, at 12:38 PM, Kellogg S. Booth <[log in to unmask]> wrote:
> The following is a somewhat random selection from hundreds of messages on CHI-ANNOUNCE that I have received that include a disclaimer along the same lines:
> “Our apologies if you receive multiple copies of this CFP.” 
> How hard can it be to fix this?
> I would think that having in the header of emails a unique identifier in a “CROSS-POST” field that mail clients (the programs we use to send and receive email) know about and (if a user indicates they want the feature) displays only the first copy of any message that has that identifier. Identifiers could be obtained from a service (or multiple services, if there is concern about having a single source that could monopolize or otherwise benefit unfairly — each service would have its own prefix for the identifiers it issues).
> Anyone sending notices, instead of including the seemingly obligatory apology and disclaimer, could instead click the botton on their (compliant) mailer to automatically get an identifer that would be inserted into the header. Including the same identifier in subsequent emails to various listservs would guarantee that users who choose to use compliant mail clients, and who set their preferences accordingly, would see only a single copy. A mail client’s search function could easily be adapted to show all of the messages with the same identifier if a user wanted to see if there were significant differences across them.
> I would imagine the hardest part of getting this solution would be whatever agreement has to be reached regarding email headers (if indeed they need to be approved by a standards body).
> The following states the case better than I could for why we should find a solution for this problem rather than continuing the practice of actively apologizing at the start of every annoucement.
> The proposed solution is not new. It is essentially how Usenet worked (and still works). That relied on people reading  posts with a news reader client that followed the conventions. Now people have largely moved to using regular email for announcements, but the mail clients have not adopted the behavior of news reader clients that dealt with this fairly well.
>    ---------------------------------------------------------------
>    For news of CHI books, courses & software, join CHI-RESOURCES
>     mailto: [log in to unmask]
>    To unsubscribe from CHI-ANNOUNCEMENTS send an email to
>     mailto:[log in to unmask]
>    For further details of CHI lists see
>    ---------------------------------------------------------------

    For news of CHI books, courses & software, join CHI-RESOURCES
     mailto: [log in to unmask]

    To unsubscribe from CHI-ANNOUNCEMENTS send an email to
     mailto:[log in to unmask]

    For further details of CHI lists see