Unfortunately it sounds like from user's experiences the one feature /
option it does not have is delivery of the full message, unless I am
misunderstanding the numerous criticisms I have read of Discourse.
Notification is fine if that's all you want, but if you don't want to
have to click over to another website in another tool besides your
email client, it sounds like there's no accommodation.
~m
On Tue, Oct 23, 2018 at 9:16 AM, Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx> wrote:
On Fri, Oct 19, 2018 at 06:38:50PM -0700, Máirín Duffy wrote:
So the big difference between filtering email lists into folders
that you
poll vs reading them in your inbox "timeline" / firehose, is that
you have
100% control over that and can change it to your prefs over time.
That's
very different than this proposal where the control is external to
each
individual and not changeable over time as needs change.
Discourse has a very rich set of features for different levels of
subscription and notification. These are individual and easy to
change on
the fly in a very fine-grained way. This is actually one of the
things that
I really like about it.
--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
council-discuss mailing list --
council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to
council-discuss-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
council-discuss mailing list -- council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to council-discuss-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
