Received: from mout-y-209.mailbox.org (mout-y-209.mailbox.org [91.198.250.237]) by mail-b.sr.ht (Postfix) with ESMTPS id AE715FF13F for <~mieum/booksin.space@lists.sr.ht>; Wed, 28 Oct 2020 07:12:51 +0000 (UTC) Authentication-Results: mail-b.sr.ht; dkim=pass (2048-bit key) header.d=namu.blue header.i=@namu.blue header.b=HnmJGF2S Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:105:465:1:1:0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-y-209.mailbox.org (Postfix) with ESMTPS id 4CLfst3yjczQlQJ for <~mieum/booksin.space@lists.sr.ht>; Wed, 28 Oct 2020 08:12:50 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=namu.blue; s=MBO0001; t=1603869168; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=D/mlQqsyqBK7cvv7RRauKFhHKImZ3QBPxLGlLDLxadw=; b=HnmJGF2SXPPJA8pvuq6xfsBpa78ND2xoRLc+tfE7PSVD4AmPacA09sHKJyWI/gIF5wduMI ctxD0F2G4WWrZ1Rm1QBG2nOv0H3u6tssuxph5ziNlS0oxeUkDWEkvNG/JQNpmC2An6++AQ 22Spsz+9yumdBr286Zn+7egcfAWkUtJy/wpfz/GxFk5ATulnsT4Ne58PC0DokUU236B7ZX JZlUY9Dm2r3HyC57hb6S+O0H45xKpS+xPkSeC7LEEZqvz5nwoiMtB2nfxAGQzuKdPj+yF8 hBlFmeEbgjZXHrjMPEMqri1EOe3f6LtS0SC58aB3IMFcja8uYBJm8I6uImnXZw== Received: from smtp1.mailbox.org ([80.241.60.240]) by spamfilter04.heinlein-hosting.de (spamfilter04.heinlein-hosting.de [80.241.56.122]) (amavisd-new, port 10030) with ESMTP id pHauhntDknIE for <~mieum/booksin.space@lists.sr.ht>; Wed, 28 Oct 2020 08:12:46 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 From: "mieum" To: <~mieum/booksin.space@lists.sr.ht> Subject: The brick and mortar Date: Wed, 28 Oct 2020 16:04:36 +0900 Message-Id: X-MBO-SPAM-Probability: X-Rspamd-Score: -2.16 / 15.00 / 15.00 X-Rspamd-Queue-Id: A34CB17E8 X-Rspamd-UID: 81d6d1 I'm continuing the conversation from the previous thread here, for "organization's" sake. >I think we can set up a sr.ht CI service to scan changed text >frontmatter (including frontmatter for new texts) and then to send that >to the main booksin.space server database (which can then update >relevant pages). That would combine both worlds pretty neatly, but I >don't know if there are any security implications to consider. Also, >the CI would have to be disabled/changed for mailing list submissions, >so that no one can affect the server by posting patches on the mailing >list. This is an intresting idea, I didn't consider this. What sorts of security implications do you anticipate other than unsolicited mailing list patches?=20 >P.S: I don't know if it showed up, but I had attached my updates to >Nathan's text in my previous message. I did see that, sorry I didn't get a chance to comment. When I get home I will add it to the repo and server...so there's something there! I'll have a little more time to set things up this evening. Thanks for being patient everyone. And please, don't hesitate to make suggestions! I may have brought the beer, but that doesn't make me in charge of the party :) ~mieum