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/JJZUDQ3MFZOBPJVHNXYHZ4ID5OFT7EQV/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "JJZUDQ3MFZOBPJVHNXYHZ4ID5OFT7EQV",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/QORCMXUZY5HRL44UWAQAKKTYD4K5J5MN/?format=api",
    "sender": {
        "address": "rwmcgwier (a) comcast.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Robert McGwier",
    "subject": "[eagle]  Budget,  Eagle presentation, etc.",
    "date": "2006-08-25T23:13:27Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/WFPMPOA5RQEE6YA2LOJSM62NGB46PCFR/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "I will be calling all of those folks I am involved with on projects to \nget budget guesstimates together for Jim to build a budget so Rick and I \ncan build the engineering budget to submit to Gunther so he can submit \nit back.  (Are we confused yet?).   I want John to do the prototype \nreceiver,   Marc to do the prototype transmitter while we work on the \nmodulator.  I am going to be pushing to get the antenna elements \ntogether for testing at our west coast testing grounds and then proceed \nto build the array.   I want this done (the array) in the next twelve \nmonths so the budget will include that.   I hope to test a bunch of \nparts at LTI that will be suitable for a high efficiency design for C \nband.   I have not said anything but there has been a lot of loose talk \nabout tapering on the phased array.  \n\nI will deliver a paper, talk on Eagle that goes as follows:\n\nHere is the old design.   Here are those areas the engineering team feel \nneed to be changed and why.  Here is a concept that at first glance \nappears to be adequate but it is NOT a design.  It is a concept that \nneeds to be analyzed to be a design by filling in the details on how one \ndoes a mission.  We will detail those issues that have mitigated in \nfavor of the changes.  I will discuss the payloads from my tranponder \nteam,  the RX, the TX work, etc.  Matt has said,  and I support,  his \ndoing the digital transponder design talk.\n\nIf anyone has input, send it privately please.\n\n\n\n73's\nBob\nN4HY\n\n\n-- \nAMSAT VP Engineering. Member: ARRL, AMSAT-DL, TAPR, Packrats,\nNJQRP/AMQRP, QRP ARCI, QCWA, FRC. ARRL SDR Wrk Grp Chairman\n\"You see, wire telegraph is a kind of a very, very long cat.\nYou pull his tail in New York and his head is meowing in Los\nAngeles. Do you understand this? And radio operates exactly\nthe same way: you send signals here, they receive them there.\nThe only difference is that there is no cat.\" - Einstein\n\n",
    "attachments": []
}