From 76bc17dd7ffeb1855b7ccc93e4942407774f6dba Mon Sep 17 00:00:00 2001 From: Abner Coimbre Date: Tue, 13 Jan 2026 11:49:29 -0800 Subject: [PATCH] Revolt Against Discord: Link the Guide --- content/english/news/revolt-against-discord.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/english/news/revolt-against-discord.md b/content/english/news/revolt-against-discord.md index 47bbbca..d3b4139 100644 --- a/content/english/news/revolt-against-discord.md +++ b/content/english/news/revolt-against-discord.md @@ -29,7 +29,7 @@ UPDATE 1/12/2026: Users [can now request](/chat) invite codes directly. #### Addressing common objections There are three typical arguments against using Revolt that I should tackle here. -1. *"Revolt will be a walled garden like Discord and therefore not crawlable."* I believe that private, ephemeral conversations should remain private. We can curate and surface the best technical discussions into a public wiki so important knowledge isn’t lost. +1. *"Revolt will be a walled garden like Discord and therefore not crawlable."* I believe that private, ephemeral conversations should remain private. We can curate and surface the best technical discussions into a [public wiki](/guide) so important knowledge isn’t lost. 2. *“Abner is a dictator."* Guilty as charged. I’m running this as a BDFL, with a decade of organizing Handmade since my early college days. There’s an escape hatch though, because every meetup host can dump their mailing list locally. I don't lock people in. This cuts both ways too: hosts who violate [community values](/about) -- e.g. running meetups sponsored by Microsoft -- are cut off from the water tap. They won't be able to send newsletters nor access new subscribers to the mailing list.