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/HKHQ2ESOHF27MMPXTPNMZSWGIDJOYFBQ/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "HKHQ2ESOHF27MMPXTPNMZSWGIDJOYFBQ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/H27DR6JA6YCJKOLVNUK563LMYAPTAI5X/?format=api",
    "sender": {
        "address": "gordonjcp (a) gjcp.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Gordon JC Pearce",
    "subject": "[amsat-bb] Re: OH2AUE P3E transponder demo video",
    "date": "2012-10-17T21:38:36Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/WAO5AD6EWHA5Z3RVLCTQRON5JA4G3IST/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/A7TTIRLV3EUQMR4JYJSBZFKK67AMHNEW/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "On 16/10/12 03:18, Ben Jackson wrote:\n\n>> It may be easy to reliably work a future generation of satellites with\n>> an HT and a rubber duckie.  But that won't be challenging.  And we (the\n>> operators) won't be learning anything new.\n>\n> But instead folks are promoting an anachronism. They're discussing\n> learning something new at the same time saying we should be using a\n> technology that has been in use since the 1960s.\n>\n> So then instead of focusing on linear transponders how about deploying\n> HSMM nodes into space, TDMA, or DMR technology? (No idea how feasible\n> any of of this is)\n\nDMR as it stands isn't viable because it relies on really tight timing \nin the slots - the \"book figure\" is 75 miles but people have pushed it \nto over 100.  The trouble here is that the speed of light just isn't \nthat fast ;-)\n\nIn any case, the challenge has changed.  I don't see any real challenge \nin the \"hard sats\", because the \"hard sat\" brigade all seem to use \nmassive aerial arrays, with computer-controlled steering and tuning.  I \ndon't see what's \"hard\" about it - it's just throwing technology and no \nreal skill at the problem.  Once you've figured out the mysteries of the \ncrappy proprietary software that people use to steer the aerials and \ntune the rig, it's point-and-shoot.\n\nThe FM sats can be worked with something as simple as a dual-band handie \nand a homebrew crossband pair of Yagis - and a great deal of operator skill.\n\nNo, the challenge today is this - are you ready?  The challenge is:\n\nGet something flying, for less than the GDP of a small nation.\n\nThere, I've said it.  It's down to money.  You know what else I'm going \nto say?\n\nThere is almost certainly never going to be another amateur HEO satellite.\n\nThere, I've said *that*, too.  Want to know why?  Because we're a \ntightfisted bunch and no-one is going to fly us for very nearly free. \nThe HEO crowd have some amazing technology, but it's going to cost a \nfortune - a very large fortune - to fly these Death Star-sized \nsatellites *at all*, never mind into HEO.\n\nThe future is small satellites, where we will have to cram as much radio \ninto a tiny cubesat payload as we can.  Even then it's going to be \nexpensive, so we're going to need to look at countries that are \ndeveloping their space programme to get launches - and that's going to \nbe India, Pakistan, Iran if they get their shit together, maybe Israel \nif we can get them interested in anything other than \"observation\" \nsatellites and probably one or two others.  Maybe some wealthyish \nAfrican countries will get in on it, like the DRC or Kenya.\n\nWe're going to have to try coming up with clever satellites, rather than \nflying a bent-pipe box the size of a fridge.  No-one is going to want to \nlift that, without us paying full price.\n\n-- \nGordon JC Pearce MM0YEQ\n",
    "attachments": []
}