From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [192.168.2.90] ([108.95.88.138]) by ewsd; Tue Dec 10 14:48:10 EST 2019 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Stanley Lieber Mime-Version: 1.0 (1.0) Subject: Re: [9front] date -t vs rfc3339 i which is correct: Message-Id: References: <361ED9A9F4CE301DE0E938744EF73C41@eigenstate.org> In-Reply-To: <361ED9A9F4CE301DE0E938744EF73C41@eigenstate.org> To: 9front@9front.org Date: Tue, 10 Dec 2019 14:48:09 -0500 X-Mailer: iPhone Mail (17B111) List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: proven lossless full-stack session manager i don=E2=80=99t recall what the original need was. werc=E2=80=99s blagh app generates an atom feed, which needs rfc3339 dates, a= nd an rss feed, which needs rfc2822 dates. 9front=E2=80=99s date -m is good f= or rfc2822. but since werc is targeted at the lowest common denominator p9p, i implement= ed 9front date -m and -t as rc functions in werclib.rc. i noticed the rfc333= 9 vs iso-8601 discrepancy when atom.tpl still failed to validate atom feeds.= so, werclib.rc/^fn ndate now has flags -a for rfc3339, -t for iso-8601, and= -m for rfc2822. i kept -t for now (it=E2=80=99s just an echo statement) in c= ase somebody needs it later. sl