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/SVGXSOWEQCTWLILRSZM7MLKQQFVXEEPG/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "SVGXSOWEQCTWLILRSZM7MLKQQFVXEEPG",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/KYYG6EXV4ZEGDMGRGYOUMNSJRBNHLAS2/?format=api",
    "sender": {
        "address": "kk7p (a) wavecable.com",
        "mailman_id": "ecaeda8313f54fe6b33b16a345e6ba3a",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/ecaeda8313f54fe6b33b16a345e6ba3a/emails/?format=api"
    },
    "sender_name": "lyle johnson",
    "subject": "[eagle] Re: Revised Module Suggestion",
    "date": "2007-10-16T16:33:28Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/TKYG6WPJFJYQWJ55GNUWR4XPKE2B4UEB/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/RGBF4BYLBT5366C4HEFXACRMWTFABRA6/?format=api",
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/I4LVKDOIQI2GWFFQ3PN5EFEC4WNNSFUS/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "The Eagle design has been the most open in the history of AMSAT.\n\nAs we all know, there are certain limitations to who can discuss what with \nwhom due to the way our governement views spacecraft and related technology. \n So, if certain parties make an observation to certain other parties, this \ninformation has to be distilled and then shared in mandated ways.   This may \nresult in some lag before the larger community is generally aware of such \ninformation.\n\nFurther, if two or three members of the Eagle team have a beer and discuss \ncertain things, and they have not come to any well-defined suggestions, it is \nnot being \"closed\" to continue to discuss (maybe over another beer) before \nfloating the idea(s) to the group.\n\nWe are all in this together, we are partner-volunteers trying to create a \nsignificant technical resource, and we need to always give one another the \nbenefit of the doubt and attribute only the highest and best possible reasons \nfor any particular event.\n\nI choose to not believe anyone is deliberately trying to hide anything from \nanyone else.  Further, if I get a phone call and discuss something or field a \nquestion, I don't necessarily feel obligated to transcribe (or even summarize) \nthe conversation and report it here.\n\nI know, and I think everyone else does (if not, they do now) that IHU-3 \ndevelopment has been stalled for a while for various reasons.  I am the guy \nmost at fault for this delay.  Bob, Rick and others are looking at ways to get \nit moving forward again.  I don't think Rick was announcing a major change to \nthe IHU-3 as some secret conclave's conclusions.  He simply mentioned that \nsome aspects of it are being thought about by some members of the team in the \ncontext of the larger issues surrounding it.  His mention of the fact that \nthis is being thought about is *sharing* -- not hiding.\n\nI saw no specific proposal, nor did I get the impression that there is a \nspecific proposal being hidden.\n\nThis is a hobby, guys.\n\nLet's have fun!\n\n73,\n\nLyle KK7P\n\n  \n",
    "attachments": []
}