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/B46CP3LDFXAHQ3MOFFCTR2HA7P334SKH/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "B46CP3LDFXAHQ3MOFFCTR2HA7P334SKH",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/X7LZLZX2FPKZXUM2QJX4BCXGRQQG2AN2/?format=api",
    "sender": {
        "address": "hans.bx2abt (a) msa.hinet.net",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Hans BX2ABT",
    "subject": "Re: [amsat-bb] fcd pro +",
    "date": "2019-05-15T13:47:15Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/XSJ2QYHAWPSE3YRXXVI4B5KSTYLVLGXH/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/ER6HBBVHK2SHV2I7PUL4377MKNDQYWDR/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "The trend is to keep everything under lid and a secret and not share \nsource code or schematics. You might agree with this, but when I spend \nmoney to buy something I own it and I want the right to repair and that \nmeans documentation. It used to be like that, because I can easily \nrepair my old ham rigs from ICOM and Kenwood because they provide this \nkind of information. And yes, if there is no documentation then I will \nsteer clear of buying that product or other products from that company. \nThanks for the heads-up: will never buy a FCD+, that's for sure.\n\nHans\n\nBX2ABT\n\n\nOn 05/15/2019 09:27 PM, Peter Goodhall (2M0SQL) via AMSAT-BB wrote:\n> I'd guess that the first place to get support would be to email\n> Hanlincrest Ltd (Howard) who makes and supports the Funcube Dongle\n> email being [email protected], I don't think rewriting a comment on his\n> website is how anyone should expect to get support.\n>\n> Most commercial products don't provide schematic or access to firmware\n> code but for some reason, some of the ham radio community seems to\n> think they should be handed it.\n>\n> 73,\n>\n> Peter, 2M0SQL\n>\n> On Wed, 15 May 2019 at 01:37, Zach Metzinger via AMSAT-BB\n> <[email protected]> wrote:\n>> On 05/14/19 05:04, Nick Pugh via AMSAT-BB wrote:\n>>> My FCD Pro+ is broken how do I get it fixed?\n>>> Where can I get a schematic?\n>> Hello Nick,\n>>\n>> Howard Long, G6LVB, hasn't made a post on the funcubedongle.com website\n>> in ~4 years. He does not respond to comments on that website regarding\n>> the USB bugs in the FCDP+, so I don't think he'll be very responsive to\n>> broken hardware/schematic requests, either.\n>>\n>> Appealing directly to AMSAT-UK may have some effect.\n>>\n>> I believe that the secrecy surrounding this dongle stems from the NDA-ed\n>> silicon tuner and a desire to keep it from being cloned.\n>>\n>> It is unfortunate that such a wonderful gadget is both closed source and\n>> closed hardware.\n>>\n>> --- Zach\n>> N0ZGO\n>> _______________________________________________\n>> Sent via [email protected]. AMSAT-NA makes this open forum available\n>> to all interested persons worldwide without requiring membership. Opinions expressed\n>> are solely those of the author, and do not reflect the official views of AMSAT-NA.\n>> Not an AMSAT-NA member? Join now to support the amateur satellite program!\n>> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb\n> _______________________________________________\n> Sent via [email protected]. AMSAT-NA makes this open forum available\n> to all interested persons worldwide without requiring membership. Opinions expressed\n> are solely those of the author, and do not reflect the official views of AMSAT-NA.\n> Not an AMSAT-NA member? Join now to support the amateur satellite program!\n> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb\n>\n>\n>\n\n",
    "attachments": []
}