From: Sébastien Hinderer <Sebastien.Hinderer@inria.fr> To: caml-list@inria.fr Subject: Re: [Caml-list] Ask questions on the mailing lists too Date: Wed, 19 Jan 2022 17:31:39 +0100 Message-ID: <Yeg861TWxfFy5ICj@prajna.paris.inria.fr> (raw) In-Reply-To: <Yebi4VyeVD5ts7FK@church> Simon Cruanes (2022/01/18 15:55 +0000): > I think there's a tension between the needs of people who are used to > 30 years old mailing list software (like the GNU mailman) and the larger > number of people used to fancy UIs like discord. To the latter group, > discourse is barely "modern" enough; to the former, it's too > javascript-heavy. Agreed. > By the way Sam, I opened https://discuss.ocaml.org/about in a TUI > browser and it looked kind of ok. Well thei=re is no real equivalence between the ability to view a page in a text-mode browser and its accessibility. NOt even an implication in one direction or another. Similarly, I don't think it's expected, nowadays, that a website is browsable without JS support for it to conform to WCAG. > I don't know about registration > though, it'd be good if there was a way to register purely by email to > make it more accessible. For the rest, _once registered_, as far as I'm > concerned, it's just a mailing list software. Well as was mentionned, the mailing-list mode needs to be enabled and that seems to have accessibility issues. Sébastien.
next prev parent reply index Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 18:57 [Caml-list] Type Error in OCaml Code mukesh tiwari 2022-01-15 21:19 ` Nicolás Ojeda Bär 2022-01-16 9:40 ` [Caml-list] Ask questions on the mailing lists too orbifx 2022-01-16 14:32 ` Sam Kuper 2022-01-17 9:20 ` Sébastien Hinderer 2022-01-17 9:34 ` Daniil Baturin 2022-01-17 14:30 ` Sam Kuper 2022-01-17 14:56 ` Daniil Baturin 2022-01-17 17:36 ` Sam Kuper 2022-01-17 21:08 ` Gabriel Scherer 2022-01-18 1:51 ` Sam Kuper 2022-01-19 15:46 ` Sébastien Hinderer 2022-01-18 9:49 ` orbifx 2022-01-18 15:55 ` Simon Cruanes 2022-01-19 16:31 ` Sébastien Hinderer [this message] 2022-01-19 17:55 ` Sam Kuper 2022-01-19 18:09 ` Sam Kuper 2022-01-19 19:09 ` Sébastien Hinderer 2022-01-19 20:53 ` Sam Kuper 2022-01-19 18:43 ` Simon Cruanes 2022-01-19 19:03 ` Sébastien Hinderer 2022-01-19 20:50 ` Sam Kuper 2022-01-20 20:56 ` Edwin Török 2022-03-11 8:46 ` Sébastien Hinderer 2022-03-11 9:38 ` Vasilis Goumas 2022-03-11 9:43 ` Gabriel Scherer 2022-01-19 15:33 ` Sébastien Hinderer 2022-01-19 21:43 ` Gabriel Scherer 2022-01-19 22:02 ` Sam Kuper 2022-01-19 22:38 ` Sébastien Hinderer [not found] ` <50AF4FEF-5CD6-40E7-9FA3-78814CBEE230@etorok.eu> 2022-01-17 22:47 ` Sam Kuper 2022-01-17 9:54 ` Alan Schmitt 2022-01-17 13:53 ` Sam Kuper 2022-01-19 15:18 ` Sébastien Hinderer 2022-01-19 15:54 ` Sébastien Hinderer 2022-01-20 9:13 ` Alan Schmitt [not found] ` <87pmom7sz7.fsf@m4x.org> 2022-01-20 14:16 ` Sébastien Hinderer
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=Yeg861TWxfFy5ICj@prajna.paris.inria.fr \ --to=sebastien.hinderer@inria.fr \ --cc=caml-list@inria.fr \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
caml-list - the Caml user's mailing list Archives are clonable: git clone --mirror https://inbox.ocaml.org/caml-list AGPL code for this site: git clone https://public-inbox.org/ public-inbox