Email Detail
Show an email
GET /hyperkitty/api/list/[email protected]/email/SLD4UKBTK7QVBNEPBRHHMYC3HZ3Z6SM5/?format=api
{ "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/SLD4UKBTK7QVBNEPBRHHMYC3HZ3Z6SM5/?format=api", "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api", "message_id": "CAN6TEUcMdFyotQz-_U9Ah03mOVOqHc2zKYDTLv7g0co7xphLtg@mail.gmail.com", "message_id_hash": "SLD4UKBTK7QVBNEPBRHHMYC3HZ3Z6SM5", "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/AL5MKXLMJNTVKQUVDD2J5IDIMUAMR3DZ/?format=api", "sender": { "address": "amsat-bb (a) wd9ewk.net", "mailman_id": "21664df01bef4757931b7cdb42a9e768", "emails": "https://mailman.amsat.org/hyperkitty/api/sender/21664df01bef4757931b7cdb42a9e768/emails/?format=api" }, "sender_name": "Patrick STODDARD (WD9EWK/VA7EWK)", "subject": "Re: [amsat-bb] A suggestion for Experimenter's Wednesdays on AO-91", "date": "2017-12-15T02:33:02Z", "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/WBMGZXGNYWR6HUHECXASSH3N7GSTBL6S/?format=api", "children": [ "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/GJ37WU2TM6RUPWWGAUCDE46VTSNX4NFO/?format=api" ], "votes": { "likes": 0, "dislikes": 0, "status": "neutral" }, "content": "Hi Mac!\n\nYou offer a good idea. I thought about things like that, but\ncame back to the simple fact that AO-91 still has the \"new\ncar smell\" for being the newest and (in my opinion) best\nperforming FM satellite we currently have. Especially given\nthe recent series of messages discussing the new document\nSean KX9X wrote, it might be better to hold off on anything\nthat limits the use of AO-91 to those who would have a\ncomputer or other accessories to do the experiment. Once\nwe have another one or two FM satellites, Fox-1C and/or\nFox-1D, then it would be a great time to have something\nelse for the weekly experiments.\n\nThe APRS-capable satellites might be better for what you\npropose, yes. Unfortunately, there is the issue of the\nmisuse of 145.825 MHz by stations automatically beaconing\ntheir existence. Any experiment using ISS or NO-84 would\nbe tougher as you move east across the continental USA,\nas well as some other parts of the world.\n\n73!\n\n\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\nTwitter: @WD9EWK or http://twitter.com/WD9EWK\n\n\n\n\n\n\nOn Fri, Dec 15, 2017 at 1:53 AM, Mac A. Cody <[email protected]> wrote:\n\n> Patrick,\n>\n> This is certainly a fine idea, which may very well gain traction. If\n> I may, though, I'd like to propose an alternative experiment. Given\n> the recent (and ongoing) disaster and recovery in Puerto Rico after\n> Hurricane Maria,I was wondering how amateur LEO satellites could be\n> used for emergency response (I know that the use case for the Phase IV\n> satellite terminal is emergency response.). While DX and chasing grid\n> squares is great fun (I do both myself.), I am hoping that there might\n> be a way that LEO satellites could be used as a public service resource.\n>\n> Traditionally, long-distance emergency response has relied upon shortwave\n> communications. It takes a bit of infrastructure cost to set up and\n> operate a shortwave station. Effective antenna deployment, available\n> transceiver equipment, and a sufficient power supply are considerations\n> to be addressed. Perhaps, a pair of hand-held radios (or single full-\n> duplex), an Arrow antenna, and a computer (Raspberry Pi) could be used to\n> send and receive emergency messages via LEO satellites and might be a\n> viable\n> alternative. The messages could be sent digitally via, say, Narrow Band\n> Emergency Messaging System (NBEMS) to improve reliability of transcription.\n>\n> I'm sure that you or someone else might say \"Use the APRS birds for\n> emergency response messaging.\". That may be a fair statement, but my\n> idea might, at least, be an interesting experiment to try. An experiment\n> is still valuable when it shows that an idea does not work!\n>\n> 73,\n>\n> Mac Cody / AE5PH\n>\n>\n", "attachments": [] }