From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 4895A201B2 for ; Thu, 25 Jan 2024 16:41:49 +0100 (CET) Received: from auth.driusan.net ([207.148.18.58]) by 9front; Thu Jan 25 10:39:54 -0500 2024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=driusan.net; s=20180128; h=From:Date:Subject:To; bh=KQufo5hQ5hRAUxUyYtJPjnGuQjqXdd1ao0COBrViUUc=; b=R7zA7uO2Pt4K0c+dQW2g5ZphTxzyaaYsh6YNlajJ9r00MBxqcy6JUPXmFAwdc4I7eraEYqqN68V/QAaqbTtmYJYJ8tn3ExU+IKd/aOaDYnU4MeVApISeIbWNghldm2KP5IxNMLjklo+3Ms8BmYN/oFsBYlbE9oryc9K4wYzKnwVA/rbI2T5Azo5kseTNEBLa/F63WQlGba7Pz6F6/bDEnFRUvEJc11EBI1oieePXOcHmaLNGubYm4uIy6dhm78UeHe8MeHniV5QL6bQZFld/hwvMetoO61Er6uLLv84lt5ZngVngxUvzVSC4YWBFFbd7uTtheHmyVAVEUiR0KRATKg== Message-ID: <77B60E477DAF70190E4704C02B91AFEA@driusan.net> To: 9front@9front.org From: "Dave MacFarlane" Date: Thu, 25 Jan 2024 10:39:52 -0500 In-Reply-To: <4DA1C0F34E4C619BB89903111841CB1F@felloff.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: agile XMPP extension out-scaling-aware persistence-aware optimizer Subject: Re: [9front] str2json and jsonfmt Reply-To: 9front@9front.org Precedence: bulk Quoth cinap_lenrek@felloff.net: > very interesting. > > i tried jg but the problem with mangadex json was that > they had newlines in the values, which where not escaped > so the grep approach doesnt work so well. > > a file-system to parse it might do the trick. > > -- > cinap > *Not* escaped newlines? You mean their json looks something like: "{ "foo": "bar baz" }"? That isn't valid JSON and even with a filesystem would (should) fail when jsonparse() is called on it. (The above example fails with JSON.parse in both Firefox and Chrome, so if that is what you mean I'm not sure how they do anything with it..)