Re: proposed JMAP file abstraction
George Michaelson <[email protected]> Mon, 16 Feb 2026 10:38:33 +0700
| Newsgroups | gmane.mail.nmh.devel |
|---|---|
| Message-ID | <CAM2GGym6KJ1S5VmXKpNZW0BM+oP4tqKqHB=rZtixYbHy0QeTVw@mail.gmail.com> |
--000000000000232268064ae8b1ca Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If it meant I could keep the front-end (shell) semantics but work with slightly different back-end objects, I would at least be able to exploit muscle memory. in all other regards I think you're right. Fuse FS type overlay would make this entirely moot. I remember a few decades ago having similar feelings about "can we map MH onto IMAP" and the retorts were "yes, but you do it first" along with "no, and it's a stupid idea" and I think this "can we make MH work with more modern <x>" is the hisenberg problem of our age: we love the s/w but the rest of the world keeps on inventing things. STOP INVENTING THINGS! cheers -G On Mon, Feb 16, 2026 at 1:33=E2=80=AFPM Ken Hornstein <[email protected]> wrot= e: > >What do people think? Could this work for a more natural (n)mh workflow > >with mail? > > > >https://datatracker.ietf.org/doc/html/draft-ietf-jmap-filenode-04 > > I read this, and it seems like it's describing "NFS using the JMAP > protocol". Which ... does not seem to change anything from the nmh > perspective? > > If I'm wrong about this protocol, please, explain it to me! > > --Ken > --000000000000232268064ae8b1ca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">If it meant I could keep the=C2=A0front-end (shell) semant= ics but work with slightly different back-end objects, I would at least be = able to exploit muscle memory.=C2=A0<div><br></div><div>in all other regard= s I think you're right. Fuse FS type overlay would make this entirely m= oot.</div><div><br></div><div>I remember a few decades ago having similar f= eelings about "can we map MH onto IMAP" and the retorts were &quo= t;yes, but you do it first" along with "no, and it's a stupid= idea" and I think this "can we make MH work with more modern <= ;x>" is the hisenberg=C2=A0problem of our age: we love the s/w but = the rest of the world keeps on inventing things. STOP INVENTING THINGS!</di= v><div><br></div><div>cheers</div><div><br></div><div>-G</div></div><br><di= v class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gma= il_attr">On Mon, Feb 16, 2026 at 1:33=E2=80=AFPM Ken Hornstein <<a href= =3D"mailto:[email protected]">[email protected]</a>> wrote:<br></div><blockquo= te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px = solid rgb(204,204,204);padding-left:1ex">>What do people think? Could th= is work for a more natural (n)mh workflow<br> >with mail?<br> ><br> ><a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-jmap-fileno= de-04" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/do= c/html/draft-ietf-jmap-filenode-04</a><br> <br> I read this, and it seems like it's describing "NFS using the JMAP= <br> protocol".=C2=A0 Which ... does not seem to change anything from the n= mh<br> perspective?<br> <br> If I'm wrong about this protocol, please, explain it to me!<br> <br> --Ken<br> </blockquote></div> --000000000000232268064ae8b1ca--