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/Y3GA3YSVTZYR2WFGIROIPNFUF3A2NPED/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "Y3GA3YSVTZYR2WFGIROIPNFUF3A2NPED",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/Y3GA3YSVTZYR2WFGIROIPNFUF3A2NPED/?format=api",
    "sender": {
        "address": "rhyolite (a) nettally.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "RFI-EMI-GUY",
    "subject": "[amsat-bb] Re: MANCHESTER encosing schemes",
    "date": "2008-03-28T03:49:21Z",
    "parent": null,
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/OBSXEIHOE3BNGT6YQ6N4DTX6X6LLRMLO/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Thanks Jim!\n\nJim Sanford wrote:\n>\n> See Embedded Systems Design for Feb 2008.  www.embedded.com\n> 73 and good luck!\n> Jim\n> [email protected]\n>\n>\n> RFI-EMI-GUY wrote:\n>> Can anyone point me to some simple schemes for Manchester encoding \n>> and decoding. The application would be for high speed data over a low \n>> cost ISM link (manufacturer advises against long strings of data in \n>> 111 or 000's)\n>>\n>>   \n>\n>\n>\n\n-- \nJoe Leikhim K4SAT\n\"The RFI-EMI-GUY\"©\n\n\"Treason doth never prosper: what's the reason?\nFor if it prosper, none dare call it treason.\"\n\n\"Follow The Money\"  ;-P\n\n\n",
    "attachments": []
}