From 87d196b8004c46d9d25b826cf2e64344df31719a Mon Sep 17 00:00:00 2001 From: Paul Butler Date: Mon, 10 Jun 2024 17:41:43 -0400 Subject: [PATCH] Update links (#742) --- README.md | 2 +- docs/pages/concepts/session-backends.mdx | 2 +- docs/pages/developing/contributing.mdx | 2 +- docs/pages/index.mdx | 2 +- docs/theme.config.jsx | 2 +- plane/README.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 54c820a3c..80cea41e8 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ Plane is a distributed system for **running stateful WebSocket backends at scale**. Plane is heavily inspired by [Figma’s mulitplayer infrastructure](https://www.figma.com/blog/rust-in-production-at-figma/), which dynamically spawns a process for each active document. Use cases include: -- Scaling up [authoritative multiplayer backends](https://driftingin.space/posts/you-might-not-need-a-crdt). +- Scaling up [authoritative multiplayer backends](https://jamsocket.com/blog/you-might-not-need-a-crdt). - Running isolated code environments (like REPLs, code notebooks, and LLM agent sandboxes). - Data-intensive applications that need a dedicated high-RAM process for each active user session. diff --git a/docs/pages/concepts/session-backends.mdx b/docs/pages/concepts/session-backends.mdx index 38914af7e..a1fde467a 100644 --- a/docs/pages/concepts/session-backends.mdx +++ b/docs/pages/concepts/session-backends.mdx @@ -25,4 +25,4 @@ Although the term *session backend* is relatively new, the concept is not. [Figm about their multiplayer approach which could be described as a session backend, as could the architecture of the [Jupyter](https://jupyter.org/) scientific computing environment and [VS Code for the web](https://code.visualstudio.com/docs/editor/vscode-web). -Read more about [session backends](https://driftingin.space/posts/session-lived-application-backends). \ No newline at end of file +Read more about [session backends](https://jamsocket.com/blog/session-backends). \ No newline at end of file diff --git a/docs/pages/developing/contributing.mdx b/docs/pages/developing/contributing.mdx index a34f7ebdb..10e827ead 100644 --- a/docs/pages/developing/contributing.mdx +++ b/docs/pages/developing/contributing.mdx @@ -1,7 +1,7 @@ # Contributing to Plane Plane is [developed on GitHub](https://github.com/jamsocket/plane), primarily by the -[Drifting in Space](https://driftingin.space/) team. +[Jamsocket](https://jamsocket.com/) team. We accept code contributions, as long as they are aligned with our roadmap and vision for Plane. diff --git a/docs/pages/index.mdx b/docs/pages/index.mdx index 7db06298a..357f01a1f 100644 --- a/docs/pages/index.mdx +++ b/docs/pages/index.mdx @@ -16,7 +16,7 @@ import Logo from '../components/logo' Plane is a distributed system for **running stateful WebSocket backends at scale**. Plane is heavily inspired by [Figma’s multiplayer infrastructure](https://www.figma.com/blog/rust-in-production-at-figma/), which dynamically spawns a process for each active document. Use cases include: -- Scaling up [authoritative multiplayer backends](https://driftingin.space/posts/you-might-not-need-a-crdt). +- Scaling up [authoritative multiplayer backends](https://jamsocket.com/blog/you-might-not-need-a-crdt). - Running isolated code environments (like REPLs, code notebooks, and LLM agent sandboxes). - Data-intensive applications that need a dedicated high-RAM process for each active user session. diff --git a/docs/theme.config.jsx b/docs/theme.config.jsx index 3cb816ac6..95cb5e531 100644 --- a/docs/theme.config.jsx +++ b/docs/theme.config.jsx @@ -12,7 +12,7 @@ export default { }, footer: { text: - Plane is an open-source project of Drifting in Space Corp. + Plane is an open-source project of Jamsocket. , }, head: () => { diff --git a/plane/README.md b/plane/README.md index 930bba9df..93743e2da 100644 --- a/plane/README.md +++ b/plane/README.md @@ -11,7 +11,7 @@ [Plane](https://plane.dev) is a distributed system for **running stateful WebSocket backends at scale**. Plane is heavily inspired by [Figma’s mulitplayer infrastructure](https://www.figma.com/blog/rust-in-production-at-figma/), which dynamically spawns a process for each active document. Use cases include: -- Scaling up [authoritative multiplayer backends](https://driftingin.space/posts/you-might-not-need-a-crdt). +- Scaling up [authoritative multiplayer backends](https://jamsocket.com/blog/you-might-not-need-a-crdt). - Running isolated code environments (like REPLs, code notebooks, and LLM agent sandboxes). - Data-intensive applications that need a dedicated high-RAM process for each active user session.