From 5dedd70a9696c34156d7c135ec787950f8c82104 Mon Sep 17 00:00:00 2001 From: Rick Staa Date: Tue, 18 Aug 2026 20:33:48 +0200 Subject: [PATCH] fix(links): send Discord links to the server we control The discord.gg/livepeer vanity slug was hijacked, so every Discord link in the docs pointed at a server Livepeer does not own. They now use the invite https://discord.gg/55SZFEEH5y, matching livepeer/website#94. Co-Authored-By: Claude Opus 5 (1M context) --- docs.json | 2 +- network/explanation/how-the-network-works.mdx | 2 +- network/index.mdx | 2 +- network/reference/faq.mdx | 2 +- network/who-this-is-for.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs.json b/docs.json index 83c80fd8c..1b7ed735b 100644 --- a/docs.json +++ b/docs.json @@ -142,7 +142,7 @@ "footer": { "socials": { "github": "https://github.com/livepeer", - "discord": "https://discord.gg/livepeer", + "discord": "https://discord.gg/55SZFEEH5y", "x": "https://x.com/livepeer" } } diff --git a/network/explanation/how-the-network-works.mdx b/network/explanation/how-the-network-works.mdx index 706aade70..9b00f809e 100644 --- a/network/explanation/how-the-network-works.mdx +++ b/network/explanation/how-the-network-works.mdx @@ -77,7 +77,7 @@ stake), and pays for the work in ETH. From an orchestrator's seat, gateways *are Want to be on that side of the marketplace — sending jobs instead of serving them? A developer platform and a Build section of these docs are on the way; until then, ask in the - [Livepeer Discord](https://discord.gg/livepeer). + [Livepeer Discord](https://discord.gg/55SZFEEH5y). ## The life of a job diff --git a/network/index.mdx b/network/index.mdx index 177be1101..8a8da1f94 100644 --- a/network/index.mdx +++ b/network/index.mdx @@ -30,7 +30,7 @@ marketplace: **Looking to build on Livepeer instead?** These docs cover *running* the network. A developer platform — and a Build section of these docs — is on the way. In the meantime, ask in the - [Livepeer Discord](https://discord.gg/livepeer); the team and community can point you at what's + [Livepeer Discord](https://discord.gg/55SZFEEH5y); the team and community can point you at what's possible today. diff --git a/network/reference/faq.mdx b/network/reference/faq.mdx index 1b4dab896..6b92e097b 100644 --- a/network/reference/faq.mdx +++ b/network/reference/faq.mdx @@ -131,7 +131,7 @@ of them before concluding the network is at fault. ## Still stuck? - + The most active real-time support. Search before posting. diff --git a/network/who-this-is-for.mdx b/network/who-this-is-for.mdx index a78890f63..eb20a31ca 100644 --- a/network/who-this-is-for.mdx +++ b/network/who-this-is-for.mdx @@ -49,7 +49,7 @@ supply it. That's the **demand side**, and its docs aren't here yet: a developer Build section of this site, are on the way. Until then, the best place to ask what's possible today is the -[Livepeer Discord](https://discord.gg/livepeer). If you're curious how demand reaches the network in +[Livepeer Discord](https://discord.gg/55SZFEEH5y). If you're curious how demand reaches the network in the meantime, [How the network works](/network/explanation/how-the-network-works) shows the full path from application to GPU.