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/SYTNNC6UD7VKXROL5ID25NOYTYW7D2ME/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "SYTNNC6UD7VKXROL5ID25NOYTYW7D2ME",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/XZ222TWPOJZDSVYAYCQDWTOTW2Y6FAZY/?format=api",
    "sender": {
        "address": "rs2atmink (a) yahoo.com",
        "mailman_id": "9c45660f0a7244d29e7513376fd2ba8b",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/9c45660f0a7244d29e7513376fd2ba8b/emails/?format=api"
    },
    "sender_name": "Robert Switzer",
    "subject": "Re: [amsat-bb] Standard for AMSAT status board observations of FS-3",
    "date": "2018-06-02T12:00:18Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7I2XLYDAF3BFMPVBOGP7PZGIBLF24WNZ/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/FTWE6KW3CGTA46VLWF4RXOMIEX3FPOSD/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": " PFS3-1 is the path for APRS digipeating, correct?\nI assume all the other passes displayed are from the BBS.\nIs there a list of what I would expect to see?\n73, Rob KA2CZU\n\n    On Friday, June 1, 2018, 5:06:51 PM EDT, Ryan Noguchi via AMSAT-BB <[email protected]> wrote:  \n \n  The pass I just got on had a much more sedate downlink, with a roughly-estimated average of about one PFS3-1 or PFS3-11 undecoded packet about every 4 seconds or so over the course of the pass. Despite seeing a bunch of beacon and message traffic by WD9EWK and KB6LTY and completing a QSO with WD9EWK, I was able to get that My Message indication for the first time in quite a while, and see my beacons and messages get sent with no more than a second or two delay.  A huge change from the past couple of days, with no change in my configuration. \n\nI can certainly report FS-3 was Blue for this pass. Thanks for the QSO, Patrick! It seemed like you got a steady stream of traffic on AO-91 just before, enough that I couldn't get through myself, which is my typical experience on the FM birds during daylight hours. \n\n73, Ryan AI6DO\n\n    On Friday, June 1, 2018, 12:31:01 PM PDT, Patrick STODDARD (WD9EWK/VA7EWK) <[email protected]> wrote:  \n \n John,\n\nNormally, working FalconSat-3 should be the same as any\nother orbiting digipeater, where you would see a \"My\nMessage\" or \"My Position\" notification on your HT's screen\nwhen you are digipeated. FalconSat-3 sends down so much\ndata, that it is possible your HT misses the digipeated\npacket, or it received it with a series of other packets\nso fast you miss the on-screen notification. That's why\nI find myself checking the listing of stations heard and\nmessage listings during a FalconSat-3 pass, in case I\nmissed something.\n\n  \n_______________________________________________\nSent via [email protected]. AMSAT-NA makes this open forum available\nto all interested persons worldwide without requiring membership. Opinions expressed\nare solely those of the author, and do not reflect the official views of AMSAT-NA.\nNot an AMSAT-NA member? Join now to support the amateur satellite program!\nSubscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb\n  \n",
    "attachments": []
}