互联网与文化drewdevault.com
请不要在 FOSS 项目中使用 Discord
Please don't use Discord for FOSS projects
2021 — 2024，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
Drew DeVault 撰文呼吁开源（FOSS）项目不要用 Discord 作为官方社区平台。文章指出 Discord 是闭源专有软件，要求注册、依赖单一公司，且聊天形式不适合公开、可检索、可长期留存的技术讨论，建议改用 IRC、邮件列表、论坛等开放方案。
为什么经久不衰：它触及开源社区基础设施的长期争论：平台应开放、可检索、可留存，而 Discord 恰恰相反，这一矛盾至今未解决，所以多年后仍被反复讨论。
HN 评论精选
开源替代品功能与体验不足，才是 Discord 流行的真正原因。
人们选择平台看的是功能，而不是代码许可证——Matrix 和 Zulip 追了多年，功能和体验仍然赶不上 Discord，在那之前人们没有理由迁移。至于 IRC，Drew 以苦行著称，声称不能分享 GIF、视频、文件、没有线程和历史记录都是特性而非缺陷，但用户并不买账，只会用脚投票。不是每个人都愿意仅仅因为 IRC 是开源的就去忍受学习和使用它的痛苦。
phoe-krk查看英文原文
People choose platforms because of their functionality, not because of their code licensing status - see the case of Scala, linked in a different sibling comment. Matrix and Zulip, even after years of chasing, still sadly haven't caught up to Discord functionality- and UX-wise; until that happens, people won't have a good reason to budge. Regarding IRC, Drew is kind of famous with his ascetism, claiming that the impossibility to share GIFs, videos, files, use threads, have internal chat history, are all features rather than limitations[1]. The thing is, people don't care about it, they'll simply vote with their own legs. Mail and mailgroups face a similar UX challenge. Not everyone is willing to endure the pain of learning and using mailgroups and IRC just because they're FOSS. [1] https://drewdevault.com/2019/07/01/Absence-of-features-in-IRC.html
聊天工具在异步、公开、可检索、可留存等方面根本不适合做用户支持渠道。
抛开闭源问题不谈，我认为任何聊天工具都不适合作为公开的用户-开发者界面。原因：1) 异步性——用户需要时间整理 bug 报告，开发者需要时间复现，且时区不同；2) 长周期——讨论可能持续数天甚至数月，一年前的对话应和昨天的一样容易访问；3) 公开性——无需注册、用浏览器即可阅读，方便其他用户搜索已有讨论；4) 永久性——每条消息应有不变的 URI 并链接到相关讨论；5) 可检索性。Discord、Slack、Matrix 这类系统专注于同步、易逝的交流，从根本上不满足这些要求。
jerjerjer查看英文原文
Disregarding closed source issue I find Discord, any chat, unsuitable as a public user-developer interface. Why? 1. Asynchrony. User needs time to collect data, write a bug report and so on. Developer needs time to reproduce the issue, work on it. Finally there are a lot of timezones - people ask/answer at different points of time. 2. Long lasting. Communication can take days, weeks and even months as new details emerge. Accessing a year old thread should be as easy as accessing a thread created yesterday. 3. Publicity. You want everything written to be as public as possible. Read access should be available to everyone without registration. Read access should be available via web browser. So that other users (who often experience the same issues) can easily find existing communication on the topic, and if they can't find it themselves you can at least send them a link which brings me to permanence. 4. Permanence. Each individual communication (message) should be accessible by a URI which never changes. Each individual communication page should have links to thread/parent/children/references. 5. Searchability. Follows from (3) and (4) but the easier it is for a user to find past discussions - the less noise you'll have. Chat systems such as Discord, Slack or Matrix are fundamentally incompatible with these requirements as they are focused on synchronous, ephemeral communication.
仅用聊天的开源项目会把潜在用户和贡献者挡在门外。
如果一个开源项目只有聊天社区而没有论坛或邮件列表，我会主动寻找替代项目。原因：聊天几乎无法有效搜索，而论坛能快速判断你是否遇到常见问题并找到解决办法；在聊天里提问后过一两天再追踪回复非常困难，除非你恰好和核心开发者同时在线；而且我不想为了看这些信息注册十几个不同的服务或私有论坛。更糟的是还可能淹没在无关闲聊里，或收到“你发错频道了”的回复。
rcarmo查看英文原文
On a related note, I’ve found myself actively seeking alternatives (edit: to the project itself, not just to chat) when an OSS project only has a chat-based community as opposed to forums or mailing-lists, for two (edit: three) reasons: - it’s impossible to search chats meaningfully, whereas forums/DLs let you quickly figure out if you’re facing a common issue (and finding resolutions easily) - asking about something in chat and tracking replies a day or two later (because you will quite likely not get a quick reply to complex issues) is also quite hard unless you just happen to be awake at the same time as a core dev and can actually spend the time together (although that usually devolves into “file an issue with more details and tag me”). - I don’t want to sign up for a dozen different services or private forums to even access that info. Not to mention that (depending on community) you might just get a lot of irrelevant chatter thrown in, or just plain “this is the wrong channel” replies because there are no signposts.
Discord 强制绑定手机号等做法印证了对其专有平台的担忧。
我以前觉得用 Discord 也还行，虽然不太喜欢。最近我开始收到“我们怀疑你的账号有问题，请绑定手机号才能加入该服务器”的提示——这多半是借口，Discord 只是想胁迫我交出手机号。而且不少社区开启了强制绑定手机号才能加入的选项。事实证明当初的坏感觉是对的。
2pEXgD0fZ5cF查看英文原文
I remember a while ago I was very much in the "I guess it's ok to use Discord, even if I don't like it". A number of tech/programming communities are there, and so I participated despite having a bad feeling about it. Now more recently I started receiving my first "hey we believe there is something wrong with your account, attach a (first time, new) phone number to it to join this server". That is most likely a lie of course, Discord just wants to blackmail me into giving them my phone number. Also apparently there is an option to make an attached phone number mandatory in order to join a server, which quite a number communities activate for some reason. So it turns out the bad feeling was correct.
历次讨论
同类还值得读
如今电脑上几乎所有操作在感知上都比 1983 年更慢（2017）
Almost everything on computers is perceptually slower than it was in 1983 (2017)
2017 年的推文串认为，尽管计算机硬件比 1983 年快得多，日常操作的感知速度却常常更慢：启动、界面响应和网络应用被层层抽象、动画、后台检查与网络依赖拖累。
互联网与文化上首页 5 次 · 2017–2020twitter.com网站肥胖危机
The Website Obesity Crisis
Maciej Cegłowski（idlewords）的经典演讲文稿《网站肥胖症危机》，批评现代网页越来越臃肿：动辄数 MB 的 JavaScript、追踪脚本和广告，把本可以轻…
互联网与文化上首页 5 次 · 2016–2021idlewords.com编辑精选亚马逊那本标价 23,698,655.93 美元的苍蝇书
Amazon’s $23,698,655.93 book about flies
博文讲的是亚马逊上一本关于果蝇的二手书被标到 23,698,655.93 美元。
互联网与文化上首页 5 次 · 2011–2022michaeleisen.org浏览器 User-Agent 字符串的历史
History of the browser user-agent string (2008)
2008 年的经典文章用戏谑的“创世纪”口吻，讲述浏览器 User-Agent 字符串如何从简单的标识演变成层层叠加的伪装：浏览器为了绕过按 UA 分发的网站检测，纷纷把自己伪装…
互联网与文化上首页 5 次 · 2012–2022webaim.org编辑精选最后的问题——艾萨克·阿西莫夫
The Last Question - Isaac Asimov
阿西莫夫最著名的短篇科幻小说《最后的问题》的在线全文。
互联网与文化上首页 5 次 · 2009–2019multivax.com编辑精选