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/6G6L6XBPW5FQEBY7ISCPK2DYRS3MNA24/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "003a01c6ebd3$ff370320$f50c910c@3GIGP4",
    "message_id_hash": "6G6L6XBPW5FQEBY7ISCPK2DYRS3MNA24",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/R7Q7L6GL6UZ4CIL74HPC3LSIM3JTW33B/",
    "sender": {
        "address": "btynan (a) omniglobal.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Bill Tynan",
    "subject": "[eagle] Re: Service class names",
    "date": "2006-10-09T18:51:57Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/OBUTZEOE6KFHVAMV5EWR6CVCFCP3CSS6/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Been think about this more.  How about dumping the word \"class\" altogether.\n\nWhy not use \"level\" instead?.\n\nFurthermore, I have come to agree with those who say that terms like \"H\" are \ningrained in the mind of users as band designations.\n\nSo, I suggest Level A would be what was called Class 0, Level B as what was \ncalled Class 1 etc.\n\nThis is MY final word on the subject but, obviously, I don't have the final \nword.\n\n73,\n\nBill\n----- Original Message ----- \nFrom: \"Eric Blossom\" <[email protected]>\nTo: \"Jim Sanford\" <[email protected]>\nCc: \"'AMSAT Eagle'\" <[email protected]>\nSent: Monday, October 09, 2006 1:03 PM\nSubject: [eagle] Re: Service class names\n\n\n> On 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>\n> I recommend A, B, C, D, or alpha, beta, delta, gamma\n>\n> I think that assuming that all \"Class 1\" users are digital voice users\n> is a mistake.   Also, S, V, and H are overloaded with frequency band\n> meanings.\n>\n> _______________________________________________\n> Via the Eagle mailing list courtesy of AMSAT-NA\n> [email protected]\n> http://amsat.org/mailman/listinfo/eagle\n>\n> \n\n\n",
    "attachments": []
}