From 9193e2b08371536e836bb13609b4bfe0b02c3bf6 Mon Sep 17 00:00:00 2001
From: Steven Jacobs <stjacobs@fastmail.fm>
Date: Wed, 1 Oct 2025 22:38:34 -0400
Subject: [PATCH] fix tangled repo urls

Tangled now redirects `tangled.sh` to `tangled.org` and also redirects
`/slices.network/slices` to `/@slices.network/slices`. Some part of this
causes issues when cloning from the URL in the README.

```
$ git clone https://tangled.sh/slices.network/slices
Cloning into 'slices'...
remote: service unsupported: ''
fatal: unable to access 'https://tangled.sh/slices.network/slices/': The requested URL returned error: 403
```

Updating it to the URL in the tangled UI works as expected.

I also updated the only other usage of `tangled.sh` and
`/slices.network/slices` without the `@` to avoid relying on the
redirect.
---
 README.md               | 2 +-
 docs/getting-started.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 52f23f3..8bd7769 100644
--- a/README.md
+++ b/README.md
@@ -52,7 +52,7 @@ Think of it as your own customizable view into the AT Protocol network.
 1. Clone the repository:
 
 ```bash
-git clone https://tangled.sh/slices.network/slices
+git clone https://tangled.org/@slices.network/slices
 cd core
 ```
 
diff --git a/docs/getting-started.md b/docs/getting-started.md
index abeb117..f51be6f 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -457,4 +457,4 @@ cp .env.example .env
 - Join our [Discord community](https://discord.gg/slices)
 - Check out [example apps](https://github.com/slices/examples)
 - Read the [AT Protocol docs](https://atproto.com/)
-- Report issues on [Tangled](https://tangled.sh/slices.network/slices/issues)
+- Report issues on [Tangled](https://tangled.org/@slices.network/slices/issues)
-- 
2.43.0