caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sam Kuper <sampablokuper@posteo.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Mon, 17 Jan 2022 22:47:00 +0000	[thread overview]
Message-ID: <20220117224700.k6nr32asw57ym6qu@posteo.de> (raw)
In-Reply-To: <50AF4FEF-5CD6-40E7-9FA3-78814CBEE230@etorok.eu>

On Mon, Jan 17, 2022 at 06:23:05PM +0000, Edwin Török wrote:
> Although it won't help in participating in discussions on
> discuss.ocaml.org, I've recently found out that it has an RSS mode:
> discuss.ocaml.org/latest.rss.  I don't know how good RSS software is
> from an accessibility point of view, but would this at least allow you
> to read the discussions happening there?

I'm unsure how long Discourse retains posts in its RSS feed(s), but
looking at the link you posted above, I don't see any posts older than 3
Jan 2022 (14 days ago).

That's a far cry from the Mbox archives of traditional mailing lists,
which (on well-run lists) can stretch back years/decades.  Those
archives are often goldmines of helpful information.

Also, in addition to missing the bulk of the forum's past posts, unless
users set something up to slurp the RSS feed at least every 14 days (I
don't currently have such a thing set-up), they'd also end up with gaps
in their local stores going forward.

Plus, for local searching/browsing an RSS store of any size, unless
users use an RSS-to-email bridge, they'd need to be running a decent RSS
reader in addition to a MUA.

Additionally, as you point out, even if someone did go to that trouble,
it would still not in itself enable them to post to Discourse.



> As for discourse itself it looks like they are planning on adding a
> chat feature with some limited bridging in the future. If that makes
> it possible to connect with an XMPP or Matrix client would it solve
> the accessibility issues?
> (https://meta.discourse.org/t/introducing-discourse-chat-pre-alpha/210734/5)

For me, the answer to your question would depend on two things:

1.  How well the feature was implemented (cf. RSS feed above), and

2.  My finding a satisfactory XMPP or Matrix client to run alongside my
    MUA - or perhaps some kind of XMPP-email bridge.

(For people who are already happy with their XMPP or Matrix set-ups,
only the first of the above two criteria would apply.)

Plus, if user registration still imposes accessibility hurdles, then
this would still mean read-only access for some users.


Best wishes,

Sam

-- 
A: When it messes up the order in which people normally read text.
Q: When is top-posting a bad thing?

()  ASCII ribbon campaign. Please avoid HTML emails & proprietary
/\  file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.

  parent reply	other threads:[~2022-01-17 22:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 18:56 [Caml-list] Type Error in OCaml Code mukesh tiwari
2022-01-15 21:18 ` Nicolás Ojeda Bär
2022-01-16  9:40   ` [Caml-list] Ask questions on the mailing lists too orbifx
2022-01-16 14:31     ` Sam Kuper
2022-01-17  9:20       ` Sébastien Hinderer
2022-01-17  9:33         ` 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:06                 ` Gabriel Scherer
2022-01-18  1:51                   ` Sam Kuper
2022-01-19 15:46                     ` Sébastien Hinderer
2022-01-18  9:48                   ` orbifx
2022-01-18 15:55                     ` Simon Cruanes
2022-01-19 16:31                       ` Sébastien Hinderer
2022-01-19 17:51                         ` 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:42                           ` 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:37                             ` Vasilis Goumas
2022-03-11  9:42                               ` Gabriel Scherer
2022-01-19 15:33                   ` Sébastien Hinderer
2022-01-19 21:43                     ` Gabriel Scherer
2022-01-19 22:01                       ` 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 [this message]
2022-01-17  9:53         ` Alan Schmitt
2022-01-17 13:52           ` Sam Kuper
2022-01-19 15:18             ` Sébastien Hinderer
2022-01-19 15:54           ` Sébastien Hinderer
2022-01-20  9:12             ` Alan Schmitt
     [not found]             ` <87pmom7sz7.fsf@m4x.org>
2022-01-20 14:15               ` Sébastien Hinderer

Reply instructions:

You may reply publicly 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=20220117224700.k6nr32asw57ym6qu@posteo.de \
    --to=sampablokuper@posteo.net \
    --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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).