commit: 5ececb07faf763e68c82591a7b26d300a2b8d8f8
parent 448fc21448f515fd8d68c9dc0a39161c9e9fa85c
Author: Drew DeVault <sir@cmpwn.com>
Date: Tue, 28 Dec 2021 10:54:42 +0100
Typo fix
Diffstat:
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/blog/Dont-use-Discord-for-FOSS.gmi b/content/blog/Dont-use-Discord-for-FOSS.gmi
@@ -12,7 +12,7 @@ You are making an investment when you choose to use one service over another. Wh
There are great FOSS alternatives to Discord or Slack. SourceHut has been investing in IRC by building more accessible services like chat.sr.ht. Other great options include Matrix and Zulip. Please consider these services before you reach for their proprietary competitors.
-Perceptive readers might have noticed that most of these arguments can be generalized. This article is much the same if we replace “Discord” with “GitHub”, for instance, or “Twitter” or “YouTube”. If your project depends on proprietary infrastructure, I want you to have a serious discussion with your collaborators about why. What do your choices means for the long-term success of your project and the ecosystem in which it resides? Are you making smart investments, or just using tools which are popular or that you’re already used to?
+Perceptive readers might have noticed that most of these arguments can be generalized. This article is much the same if we replace “Discord” with “GitHub”, for instance, or “Twitter” or “YouTube”. If your project depends on proprietary infrastructure, I want you to have a serious discussion with your collaborators about why. What do your choices mean for the long-term success of your project and the ecosystem in which it resides? Are you making smart investments, or just using tools which are popular or that you’re already used to?
If you use GitHub, consider SourceHut or Codeberg. If you use Twitter, consider Mastodon instead. If you use YouTube, try PeerTube. If you use Facebook… don’t.
diff --git a/content/blog/Dont-use-Discord-for-FOSS.md b/content/blog/Dont-use-Discord-for-FOSS.md
@@ -71,7 +71,7 @@ Perceptive readers might have noticed that most of these arguments can be
generalized. This article is much the same if we replace "Discord" with
"GitHub", for instance, or "Twitter" or "YouTube". If your project depends on
proprietary infrastructure, I want you to have a serious discussion with your
-collaborators about why. What do your choices means for the long-term success of
+collaborators about why. What do your choices mean for the long-term success of
your project and the ecosystem in which it resides? Are you making smart
investments, or just using tools which are popular or that you're already used
to?
