使用 Discourse 替代电子邮件邮件列表

:bookmark: 本主题阐述了在群体对话和社区管理中,使用 Discourse 相较于传统电子邮件邮件列表的优势。

:person_raising_hand: 所需用户等级:所有用户

Discourse 是一个专为群体对话设计的现代化平台,相较于传统电子邮件邮件列表,它具有显著优势。虽然电子邮件在一对一或小规模沟通中依然有效,但 Discourse 在处理大型、持续的讨论方面表现卓越。以下是您应该考虑为您的社区使用 Discourse 的原因:

改进的导航与组织

链接与交叉引用

Discourse 让在不同主题之间建立链接变得轻而易举,从而构建起相互关联的讨论网络。此功能支持:

  • 在相关对话间轻松导航
  • 当某主题在其他地方被引用时自动通知
  • 为每个主题提供清晰的入站链接列表

分类与追踪

与难以管理多个邮件列表的挑战不同,Discourse 提供:

  • 具备细粒度追踪控制的分类
  • 专为已关注主题设立的“未读”页面
  • 展示全新主题的“新帖”页面
  • 突出热门讨论的“热门”页面

增强的用户体验

更低的入门门槛

Discourse 提供灵活的注册选项:

  • 社交账号登录(Google、Facebook、GitHub、Discord、LinkedIn 等)
  • 与自定义登录提供商的单点登录(SSO)
  • 邀请链接
  • 公司邮箱域名白名单

管理控制

通过以下方式防止垃圾信息并管理用户行为:

减少噪音

Discourse 通过以下方式鼓励有意义的互动:

  • 使用"点赞"来认可共识,而无需发表不必要的评论
  • 允许用户编辑自己的帖子,减少后续的更正回复

改进的可搜索性与归档

站内搜索

Discourse 提供强大的搜索功能:

  • 对所有内容进行全文搜索
  • 高级搜索选项,可按用户、日期、分类等进行筛选
  • 相似主题建议,防止重复讨论

利于 SEO 的内容

对于公开论坛,Discourse 能提升可发现性:

  • 搜索引擎友好的格式
  • 内部和外部链接有助于提升 SEO

灵活性与集成

电子邮件集成

Discourse 仍可满足以电子邮件为中心的用户需求:

  • 配置传入邮件以支持基于电子邮件的互动
  • 为偏好仅通过电子邮件参与的用户提供可选的“邮件列表模式”

移动设备与 PWA 支持

随时随地访问您的 Discourse 论坛:

  • Discourse 可作为渐进式 Web 应用(PWA)安装在移动设备上
  • 在所有实例(包括自托管实例)上接收推送通知
  • 使用 DiscourseHub 应用查看多个 Discourse 实例中的新帖和未读数量

RSS 订阅源

Discourse 为各种页面提供 RSS 订阅源:

  • 在主题 URL 后添加 .rss 即可获取单个主题的订阅源
  • 提供特定分类的 RSS 订阅源
  • 查看 本指南 以获取可用 RSS 订阅源的完整概览

从邮件列表切换时的注意事项

尽管 Discourse 具有诸多优势,但在过渡时请考虑以下因素:

  • 与简单的邮件列表相比,Discourse 需要更大量的托管资源
  • 部分用户可能需要时间来适应新的界面和工作流程
  • 对于非常小型或处于早期阶段的项目,部署完整的 Discourse 实例可能过于庞大

导入邮件列表内容

如果您决定切换到 Discourse,可以导入现有的邮件列表内容。有关导入邮件列表的指南,请访问我们的 邮件列表导入指南

其他资源

28 个赞

Another mailing list pro is: all mailing lists end up in one mailbox.

Depending on the user’s workflow, they may read them all in one place or filter them out to various labels or folders.

Discourse may have several related mailing-list equivalents in one place, but that’s generally just from one company.

If I’m interested in horse-riding and leap seconds and 13th-century Dutch art history, I’d probably rather fire up one email client in the morning (which I do anyway) than have to visit umpteen separate Discourse instances hosted on various websites.

I think what might be useful would be something like Usenet: a decentralised one-stop shop for all sorts of content, so the horse riders, leap-second buffs, and art history lovers could all be at the same place – they would then simply choose which categories to watch and which ones to ignore.

1 个赞

The new app for mobile does something similar to this in that all it really does is show the new/unread counts for each of your Discourse forums. Not sure if there is a web portal that does something similar? The stack exchange group of sites ended up having one notification box didn’t they which helped me picking up on posts across multiple system but I don’t think it had a shared front end portal.

Does Discourse have an RSS feed? I use Inoreader these days and it would be handy to have my various Discourse feeds in there as well.

1 个赞

This just works for hosted forums, right? So that would only partially help if one is also interested in Discourse forums that are self-hosted by other users/companies/groups/etc.

Counts and basic functionality is fine, push notifications are omitted

1 个赞

Indeed, but discourse will email you posts if you want it to.

Many pages do. Try appending “.rss” to a URL eg.

Why use Discourse instead of a email mailing list?

Discourse Meta - Latest topics

3 个赞

Also things such as categories, e.g. https://meta.discourse.org/c/faq.rss

4 个赞

A mailing list like google group has many good propertities.

If you want to make discourse compete the Mail list. You need at least these propertities:

For open groups:

  • The group can be managed by many people. Like anyone can add or delete themselves all by themselves.

  • So The group names must be presented somewhere.

  • The discussion should be emailed to the email box, at least optional. And, I believe the mail should be from the sender, not from noreply.discourse.org or other public mail box.

  • People can choose to post to someone in the list, or post to the group.

  • Some of the good topics should be presented to Discourse, while some should just be a notification or other short messages that should NOT be presented to the discourse.

###For private Groups, there should be one or a few managers.

  • How should we present there private groups? How should the Manager manage the groups? All big problems.

Discourse is not so mature to replace mail-lists.

I think we should devote great effort to solves all these problems first. Now is not the time for marketing.

Doesn’t Discourse allow that too, but with even greater granularity?

I don’t understand what you mean by this.

Like we do?

I can’t say I agree with that one. This is how broken, messy email chains happen.

Could you explain further? What is “the group” in this case?

Also don’t understand this one.

Just require logins? What’s the big problem?

3 个赞

@erlend_sh this is a really good article and covers some of the points I often have to make to people when I’m explaining why they need a forum as opposed to several mailing lists. I work primarily in the National Health Service in the UK, where email is used for everything (unless a fax machine can be used), and therefore people are literally drowning in emails, when there are so much better ways of handling and sharing information such as (but not limited to) Discourse forums. Most of the user-land resistance comes from a primal fear that you will increase that email volume. My contention is that if you know everything is archived on the forum you can simply delete the notifications or switch them off.

One killer feature of fora over mailing lists that you missed out is the access to ALL of the messaging history that you get when you join a forum. With older style ‘listserver’ mailing lists you only have whatever history you’ve saved in your email client.

This messaging history may well contain the answer to your question, so you can search, find your answer, and you don’t even need to post your n00b question. (If you had posted that n00b question on the mailing list, people would bark back at you ‘THAT question again? Wasn’t that answered just a few weeks ago?’ anyway, so if you can find the existing post it’s an advantage)

Admittedly, with some ‘mailing lists’ such as Google Groups you can search the messaging history to a degree, but this isn’t they way most people normally interact with the forum, so I think fewer people than you think would know/bother to do this.

Marcus

4 个赞

Thanks for pointing that out. I added a paragraph under “Search friendly archive that prevents repetition” including a showcase of our “Similar topic” JIT notification. Let me know if you have something to add to that.

3 个赞

Though on certain discourse forums this will still happen to you :wink: The difference is, of course, that on discourse you have a chance of avoiding it, provided you know the right search terms.

1 个赞

Over on the CAMRA Discourse forums, an attempt has been made to placate those very familiar and happy with mailing lists by saying you can make Discourse work like a mailing list.

Personally I feel this is a mistake as said members will never learn about the advantages of working in the much richer web interface.

For me the biggest plus of a forum is that I can edit my reply after posting. I’m crap at proof-reading before hand so often spot a typo.

And isn’t the story from Colin in the (UK) national health service a common one?

Sure, but there’s always the “extra features” of the web interface that will always be there, drawing people back and tempting them to check out the web UI. I’ve seen many people, originally “stubborn” and refusing to use the web, eventually switch over because the overall UX was so much better. Maybe not everyone, but it definitely happens. (Plus, I’m a big believer in the “meet people where they are” philosophy of building community.)

5 个赞

I would also add few more advantages of Discourse that I don’t think were mentioned:

  • very comprehensive usage statistics reporting interface
  • intuitive and engaging user feedback system with “likes” and “solutions” that attracts more participation
  • plugins for integrations with external products (YouTube, GitHub) that help connect communities and further engage users
  • effective moderation/spam filtering engine
8 个赞

我在 LibreHosters 上写了一份关于通过电子邮件使用 Discourse 的简短指南。我有什么遗漏的吗?

7 个赞

这并不是一个工作邮件列表和一个工作论坛之间的真正区别,但在实践中,我发现确保共享服务器上邮件列表电子邮件的可送达性是一项艰苦的工作。使用 Discourse 和 Mailgun,电子邮件通知的可送达性似乎更容易,而且这也不是一个潜在的问题,因为人们会在线访问论坛,而不是完全依赖接收电子邮件。这只是我个人的经验。

2 个赞

是啊,真不容易,@tshenry @simon 邮件可送达性是一个 极其 困难的问题。

6 个赞

如果您要求用户登录才能访问某些内容、发布或使用某些功能,那么 Discourse 实际上并不能消除电子邮件的可送达性问题,它只是使这些问题不那么频繁,因为您仍然需要能够向用户发送一些电子邮件来设置他们或更新密码。

根据我的经验(30 多年担任电子邮件管理员的经验),如果您只需要偶尔处理电子邮件递送问题,您可能甚至不会注意到何时发生变化。(而且这些变化会很频繁,例如当 ISP 修改其基本规则时。)

高流量列表确实会带来其他类别的问​​题,允许通过电子邮件回复或创建主题也是如此。

2 个赞