diff --git a/content/posts/missing-half-activitypub-potential.md b/content/posts/missing-half-activitypub-potential.md
index 0b494f3..3cf5d81 100644
--- a/content/posts/missing-half-activitypub-potential.md
+++ b/content/posts/missing-half-activitypub-potential.md
@@ -27,6 +27,8 @@ C2S offers a standardized way for clients or bots to interact with ActivityPub s
 
 It gets better. Have you ever been frustrated about having a Mastodon account and a PeerTube account and a Forgejo account and a Lemmy account and so on? With this system, you just need one account, and all the processing apps operate on the data of your one account. Boom. Problem solved.
 
+It's also compatible with the ActivityPub spec and existing implementations. Hooray!
+
 This gives us an explosion of possibilites for what we can now do with ActivityPub. Now literally anyone can run an ActivityPub app. Just run the processing app on your computer, or even a phone. You don't need a domain name or web server or anything.
 
 Except... this isn't all rainbows and sunshine. Separating storage and processing like this introduces latency and hurts performance. Another possibility is that we could make the ActivityPub server also handle running sandboxed user-uploaded processing apps, so that the processing apps can be physically close to the storage.
@@ -37,7 +39,7 @@ The upshot of all of this is that if you want to write an ActivityPub app, you n
 
 I told you earlier that I was going to explain that research project, but now you already know what it's about. The stuff above.
 
-So you might be wondering, sure these ideas sound amazing, but do they actually work? And my honest answer is I don't know. I glossed over way to many technical details. The whole point of this post isn't to declare this is the panacea to all of ActivityPub's technical woes, but rather to get your brain spinning and thinking. And don't forget that by far the toughest challenges for the fediverse are not technical, but rather social, like moderation or [these challenges](https://discuss.coding.social/t/major-challenges-for-the-fediverse/67).
+So you might be wondering, sure these ideas sound amazing, but do they actually work? And my honest answer is I don't know. I glossed over way to many technical details. The whole point of this post isn't to declare this is the panacea to all of ActivityPub's technical woes, but rather to get your brain spinning and thinking. And don't forget that by far the toughest challenges for the fediverse are not technical, but rather social, like moderation or [these challenges](https://discuss.coding.social/t/major-challenges-for-the-fediverse/67). We can't stop arguing over which decentralized web protocol is best while really it's the social problems that need solutions.
 
 Bonus! Let's solve another notoriously difficult ActivityPub problem: nomadic identity. (Much of this is copied from this [braindump of decentralized protocol ideas](https://git.exozy.me/a/Kela))