Show an email

GET /hyperkitty/api/list/[email protected]/email/VUY3XQL5OD6RO3ASQAKAYSPDMOKJUKRK/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/VUY3XQL5OD6RO3ASQAKAYSPDMOKJUKRK/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "VUY3XQL5OD6RO3ASQAKAYSPDMOKJUKRK",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/ZI3ROGEKNXO523ZCICHNEI6COHEQD7PF/?format=api",
    "sender": {
        "address": "amsat (a) w7brs.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Jeff Wandling W7BRS",
    "subject": "[amsat-bb] Re: Linksys routers and 2M \"birdies\"",
    "date": "2009-02-05T02:00:50Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/LBTSEUDVPVLNOMMLRSBJL222RUCABR4S/?format=api",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Oh OK, so yea Bruce does have a different opinion about securing networks \nvs. the data you hold.  You dropped the name but didn't give any context.\n\nYes, I've read his remarks on this.  He has a different opinion.  In a \nsituation where the bandwidth wasn't an issue, I would agree 100%.  In the \ncontext of bandwith, I'd do what I could to keep the pedestrian user from \nwasting my precious bandwidth.\n\nHis remarks don't deal with the bandwidth as far as I remember. He was \nspeaking to the point of securing your data.  If I had his income, and a \nnetwork to match I wouldn't worry as much about the script kiddy next door \nstealing a few Mb/sec.\n\nHis message, in a nutshell; secure your data.  The idea that you can \nprotect your data by password protecting your network is the main \ncomplaint he has. I agree.  It's foolish to think protecting your \nnetwork secures your data.\n\nI quote: \"If I configure my computer to be secure regardless of the \nnetwork it's on, then it simply doesn't matter. And if my computer isn't \nsecure on a public network, securing my own network isn't going to reduce \nmy risk very much.\"\n\n\nThe article is here, if you want to refer to it:\n\nhttp://www.schneier.com/blog/archives/2008/01/my_open_wireles.html\n\n\n  -jeff\n\n\nOn Wed, 4 Feb 2009, Doug Faunt N6TQS +1-510-655-8604 wrote:\n\n> Err, check out Bruce Schneier's view on this.\n>\n> 73, doug\n>\n>   Date: Wed, 4 Feb 2009 16:59:06 -0800 (PST)\n>   From: Jeff Wandling W7BRS <[email protected]>\n>\n>   Yup, and..\n>\n>   For liability reasons, I wouldn't share your bandwidth with another\n>   household.  Who knows what they'll do with the connection. Download\n>   illegal stuff, share illegal stuff, etc.. It's just bad juju.\n>\n>   Make your SSID unpublished, run IPCop on a spare beige box, and use an\n>   AccessPoint not a dual router-hub.\n>\n>   -jeff\n>\n>   On Wed, 4 Feb 2009, Sebastian wrote:\n>   > Well for one thing, in stateside, it's usually against the rules of\n>   > the ISP to share a connection with your neighbors.\n> _______________________________________________\n> Sent via [email protected]. Opinions expressed are those of the author.\n> Not an AMSAT-NA member? Join now to support the amateur satellite program!\n> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb\n>\n",
    "attachments": []
}