From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (mailfrom) identity=mailfrom; client-ip=8.23.224.60; helo=out.smtp-auth.no-ip.com; envelope-from=kevin@carhart.net; receiver= Received: from out.smtp-auth.no-ip.com (smtp-auth.no-ip.com [8.23.224.60]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 310CF77DC3 for ; Sun, 25 Mar 2018 01:09:07 -0700 (PDT) X-No-IP: carhart.net@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from carhart.net (unknown [99.52.200.227]) (Authenticated sender: carhart.net@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 4BA6C356 for ; Sun, 25 Mar 2018 01:11:07 -0700 (PDT) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id w2P8B57X027867 for ; Sun, 25 Mar 2018 01:11:05 -0700 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id w2P8B5s9027850 for ; Sun, 25 Mar 2018 01:11:05 -0700 Date: Sun, 25 Mar 2018 01:11:04 -0700 (PDT) From: Kevin Carhart To: Edbrowse-dev@lists.the-brannons.com In-Reply-To: <20180224120744.eklhad@comcast.net> Message-ID: References: <20180224120744.eklhad@comcast.net> User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [Edbrowse-dev] version X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.25 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 08:09:08 -0000 Sounds good to me. I noticed this in the roadmap message: Another possibility is json support. Nasa calls up 11 different json files via xhr, and does nothing with them as far as I can tell. That seems unlikely. -- Doesn't it place those? I thought that the real space-related content, such as it is, was partially coming from JSON. Is there more to JSON support besides JSON.parse and JSON.stringify? Actually, if you have something else in mind besides these two functions, this could be good, because sometimes pages report "invalid JSON" errors. I'm not sure if there is one overall cause for these. When I tried to research Chuck's request for dyndns, this was in part a JSON error.