Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/65MRUOPH2IS4JLDMB3BB2R3HAQKRQ7JM/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "65MRUOPH2IS4JLDMB3BB2R3HAQKRQ7JM",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/R7Q7L6GL6UZ4CIL74HPC3LSIM3JTW33B/?format=api",
    "sender": {
        "address": "kene (a) braxtontech.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Ken Ernandes",
    "subject": "[eagle] Re: Service class names",
    "date": "2006-10-09T18:41:20Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/OBUTZEOE6KFHVAMV5EWR6CVCFCP3CSS6/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/WMEM4F4YQPAJU2KD7FNZ45GAWT2M4JIP/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Why not a simple naming system like???:\n\n1.  SMS Mode      (for Class 1)\n2.  Digital Voice (for Class 2)\n3.  Wideband      (for Class 3)\n\nJust my $0.02\n\n73, Ken Ernandes, N2WWD\n\n\n\n\n-----Original Message-----\nFrom: [email protected] [mailto:[email protected]] On Behalf Of\nEric Blossom\nSent: Monday, October 09, 2006 2:04 PM\nTo: Jim Sanford\nCc: 'AMSAT Eagle'\nSubject: [eagle] Re: Service class names\n\nOn Sun, Oct 08, 2006 at 01:52:39PM -0400, Jim Sanford wrote:\n> Team:\n> I learned at Symposium that some don't like some of the class names \n> we've been using to discuss various services.\n> \n> I reaffirmed at Symposium that we need consistent names for the services \n> we'll provide, just like we've settled on band names.\n> \n> To give us the precise nomenclature I think we need for effective \n> communication, I propose:\n> \n>    Class A for what we used to call Class 0 (A from the old \"Analog\", \n> which we need to stamp out.)\n>    Class S for what we used to call Class 1 (S from SMS)\n>    Class V for what we used to call Class 2 (small station digital Voice)\n>    Class H for what we used to call Class 3 (High rate)\n> \n> I started with A, B,  .  . . and decided to propose more intuitive names.\n> \n> Unless one of you strongly objects in the next few hours, I'll have the \n> ANS announcement and AMSAT web page updated.\n> \n> It was great to see many of you this weekend.\n> \n> Thanks & 73,\n> Jim\n> [email protected]\n\nI recommend A, B, C, D, or alpha, beta, delta, gamma\n\nI think that assuming that all \"Class 1\" users are digital voice users\nis a mistake.   Also, S, V, and H are overloaded with frequency band\nmeanings.\n\n_______________________________________________\nVia the Eagle mailing list courtesy of AMSAT-NA\[email protected]\nhttp://amsat.org/mailman/listinfo/eagle\n\n",
    "attachments": []
}