[chore] Rewrite all remaining Github links

2025-06-05 21:59:39 +02:00 · 2025-04-27 13:36:27 +02:00
parent 5bfccdad3c
commit 93c3c153f0
67 changed files with 134 additions and 140 deletions
--- a/docs/admin/backup_and_restore.md
+++ b/docs/admin/backup_and_restore.md
@@ -178,7 +178,7 @@ hooks:

 For PostgreSQL, you'll want to use `postgresql_databases` instead.

-The file mentioned in `patterns_from` can be created by transforming the output from the GoToSocial CLI media [`list-attachments`](cli.md#gotosocial-admin-media-list-attachments) and [`list-emojis`](cli.md#gotosocial-admin-media-list-emojis) commands. In order to generate the right patterns you can use the [`media-to-borg-patterns.py`](https://github.com/superseriousbusiness/gotosocial/tree/main/example/borgmatic/media-to-borg-patterns.py) script. How Borg patterns work is explained in [their documentation](https://man.archlinux.org/man/borg-patterns.1).
+The file mentioned in `patterns_from` can be created by transforming the output from the GoToSocial CLI media [`list-attachments`](cli.md#gotosocial-admin-media-list-attachments) and [`list-emojis`](cli.md#gotosocial-admin-media-list-emojis) commands. In order to generate the right patterns you can use the [`media-to-borg-patterns.py`](https://codeberg.org/superseriousbusiness/gotosocial/tree/main/example/borgmatic/media-to-borg-patterns.py) script. How Borg patterns work is explained in [their documentation](https://man.archlinux.org/man/borg-patterns.1).

 You'll need to put that file on your GoToSocial instance and make sure the file is executable. It requires Python 3 which you will already have if you have Borg and Borgmatic installed. It only depends on the Python standard library.

--- a/docs/admin/cli.md
+++ b/docs/admin/cli.md
@@ -13,7 +13,7 @@ GoToSocial - a fediverse social media server

 For help, see: https://docs.gotosocial.org.

-Code: https://github.com/superseriousbusiness/gotosocial
+Code: https://codeberg.org/superseriousbusiness/gotosocial

 Usage:
  gotosocial [command]
--- a/docs/advanced/security/sandboxing.md
+++ b/docs/advanced/security/sandboxing.md
@@ -18,7 +18,7 @@ Different distributions have different sandboxing mechanisms they prefer and sup
 We ship an example AppArmor policy for GoToSocial, which you can retrieve and install as follows:

 ```sh
-$ curl -LO 'https://github.com/superseriousbusiness/gotosocial/raw/main/example/apparmor/gotosocial'
+$ curl -LO 'https://codeberg.org/superseriousbusiness/gotosocial/raw/main/example/apparmor/gotosocial'
 $ sudo install -o root -g root gotosocial /etc/apparmor.d/gotosocial
 $ sudo apparmor_parser -Kr /etc/apparmor.d/gotosocial
 ```
--- a/docs/advanced/sqlite-networked-storage.md
+++ b/docs/advanced/sqlite-networked-storage.md
@@ -32,4 +32,4 @@ You'll need to update the following settings:
 * `db-sqlite-journal-mode`
 * `db-sqlite-synchronous`

-We don't provide any recommendations as this will vary based on the solution you're using. See [this issue](https://github.com/superseriousbusiness/gotosocial/issues/3360#issuecomment-2380332027) for what you could potentially set those values to.
+We don't provide any recommendations as this will vary based on the solution you're using. See [this issue](https://codeberg.org/superseriousbusiness/gotosocial/issues/3360#issuecomment-2380332027) for what you could potentially set those values to.
--- a/docs/advanced/tracing.md
+++ b/docs/advanced/tracing.md
@@ -19,7 +19,7 @@ tracing-insecure-transport: true
 [obs]: ../configuration/observability.md
 [tempo]: https://grafana.com/oss/tempo/
 [grafana]: https://grafana.com/oss/grafana/
-[ext]: https://github.com/superseriousbusiness/gotosocial/tree/main/example/tracing
+[ext]: https://codeberg.org/superseriousbusiness/gotosocial/tree/main/example/tracing

 ## Querying and visualising traces

--- a/docs/api/swagger.md
+++ b/docs/api/swagger.md
@@ -14,8 +14,8 @@ Most of the GoToSocial API endpoints require a user-level OAuth token. For a gui
    
    See the following issues for more context:
    
-    - [#1958](https://github.com/superseriousbusiness/gotosocial/issues/1958)
-    - [#1944](https://github.com/superseriousbusiness/gotosocial/issues/1944)
-    - [#2641](https://github.com/superseriousbusiness/gotosocial/issues/2641)
+    - [#1958](https://codeberg.org/superseriousbusiness/gotosocial/issues/1958)
+    - [#1944](https://codeberg.org/superseriousbusiness/gotosocial/issues/1944)
+    - [#2641](https://codeberg.org/superseriousbusiness/gotosocial/issues/2641)

 <swagger-ui src="swagger.yaml"/>
--- a/docs/api/swagger.yaml
+++ b/docs/api/swagger.yaml
@@ -1583,7 +1583,7 @@ definitions:
            max_profile_fields:
                description: |-
                    The maximum number of profile fields allowed for each account.
-                    Currently not configurable, so this is hardcoded to 6. (https://github.com/superseriousbusiness/gotosocial/issues/1876)
+                    Currently not configurable, so this is hardcoded to 6. (https://codeberg.org/superseriousbusiness/gotosocial/issues/1876)
                format: int64
                type: integer
                x-go-name: MaxProfileFields
@@ -1965,7 +1965,7 @@ definitions:
                x-go-name: Rules
            source_url:
                description: The URL for the source code of the software running on this instance, in keeping with AGPL license requirements.
-                example: https://github.com/superseriousbusiness/gotosocial
+                example: https://codeberg.org/superseriousbusiness/gotosocial
                type: string
                x-go-name: SourceURL
            terms:
--- a/docs/configuration/database.md
+++ b/docs/configuration/database.md
@@ -146,7 +146,7 @@ db-tls-ca-cert: ""
 #
 # PLEASE NOTE!!: This setting currently only applies for Postgres. SQLite will always use 1 connection regardless
 # of what is set here. This behavior will change in future when we implement better SQLITE_BUSY handling.
-# See https://github.com/superseriousbusiness/gotosocial/issues/1407 for more details.
+# See https://codeberg.org/superseriousbusiness/gotosocial/issues/1407 for more details.
 #
 # Examples: [16, 8, 10, 2]
 # Default: 8
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -38,4 +38,4 @@ We introduced a sign-up flow in v0.16.0. The server you want to sign up to must

 ## Why's it still in Beta?

-Take a look at the [list of open bugs](https://github.com/superseriousbusiness/gotosocial/issues?q=is%3Aissue+is%3Aopen+label%3Abug) and the [roadmap](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/ROADMAP.md) for a more detailed rundown.
+Take a look at the [list of open bugs](https://codeberg.org/superseriousbusiness/gotosocial/issues?q=is%3Aissue+is%3Aopen+label%3Abug) and the [roadmap](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/ROADMAP.md) for a more detailed rundown.
--- a/docs/federation/http_signatures.md
+++ b/docs/federation/http_signatures.md
@@ -20,7 +20,7 @@ When sending a request, GtS will attempt first *with* query parameters included.

 When receiving a request, GtS will attempt to validate the signature first *with* query parameters included. If the signature fails to validate, it will reattempt validation without query parameters included.

-See [#894](https://github.com/superseriousbusiness/gotosocial/issues/894) for more details.
+See [#894](https://codeberg.org/superseriousbusiness/gotosocial/issues/894) for more details.

 ## Incoming Requests

@@ -38,7 +38,7 @@ ED25519

 GoToSocial request signing is implemented in [internal/transport](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/internal/transport/signing.go).

-Once https://github.com/superseriousbusiness/gotosocial/issues/2991 is resolved, GoToSocial will use the `(created)` pseudo-header instead of `date`.
+Once https://codeberg.org/superseriousbusiness/gotosocial/issues/2991 is resolved, GoToSocial will use the `(created)` pseudo-header instead of `date`.

 For now however, when assembling signatures:

@@ -82,4 +82,4 @@ For Mastodon, the public key of a user is served as part of that user's Actor re

 Remote servers federating with GoToSocial should extract the public key from the `publicKey` field. Then, they should use the `owner` field of the public key to further dereference the full version of the Actor, using a signed `GET` request.

-This behavior was introduced as a way of avoiding having remote servers make unsigned `GET` requests to the full Actor endpoint. However, this may change in future as it is not compliant and causes issues. Tracked in [this issue](https://github.com/superseriousbusiness/gotosocial/issues/1186).
+This behavior was introduced as a way of avoiding having remote servers make unsigned `GET` requests to the full Actor endpoint. However, this may change in future as it is not compliant and causes issues. Tracked in [this issue](https://codeberg.org/superseriousbusiness/gotosocial/issues/1186).
--- a/docs/getting_started/index.md
+++ b/docs/getting_started/index.md
@@ -68,7 +68,7 @@ If you decide to use a VPS instead, you can spin yourself up something cheap wit
 !!! warning "Cloud storage volumes"
    Not all cloud VPS storage offerings are equal, and just because something claims to be backed by an SSD doesn't mean that it will necessarily be suitable to run a GoToSocial instance.
    
-    The [performance of Hetzner Cloud Volumes](https://github.com/superseriousbusiness/gotosocial/issues/2471#issuecomment-1891098323) is not guaranteed and seems to have very volatile latency. This will result in your GoToSocial instance performing poorly.
+    The [performance of Hetzner Cloud Volumes](https://codeberg.org/superseriousbusiness/gotosocial/issues/2471#issuecomment-1891098323) is not guaranteed and seems to have very volatile latency. This will result in your GoToSocial instance performing poorly.

 !!! danger "Oracle Free Tier"
    [Oracle Cloud Free Tier](https://www.oracle.com/cloud/free/) servers are not suitable for a GoToSocial deployment if you intend to federate with more than a handful of other instances and users.
@@ -149,7 +149,7 @@ If you can't leave `443` and `80` open on the machine, don't worry! You can conf

 ## Clustering / multi-node deployments

-GoToSocial does not support [clustering or any form of multi-node deployment](https://github.com/superseriousbusiness/gotosocial/issues/1749).
+GoToSocial does not support [clustering or any form of multi-node deployment](https://codeberg.org/superseriousbusiness/gotosocial/issues/1749).

 Though multiple GtS instances can use the same Postgres database and either shared local storage or the same object bucket, GtS relies on a lot of internal caching to keep things fast. There is no mechanism for synchronising these caches between instances. Without it, you'll get all kinds of odd and inconsistent behaviour. Don't do this!

--- a/docs/getting_started/installation/container.md
+++ b/docs/getting_started/installation/container.md
@@ -45,7 +45,7 @@ If desired, update the GoToSocial Docker image tag to the version of GtS you wan
 * `X.Y.Z`: release tag. This points to a specific, stable, release of GoToSocial.

 !!! tip
-    Both the `latest` and `snapshot` tags are moving tags, whereas the `X.Y.Z` tags are immutable. The result of pulling a moving tag might change from day to day. `latest` on one system might not be the same `latest` on a different system. It's recommended to use the `X.Y.Z` tags instead so you always know exactly which version of GoToSocial you're running. The list of releases can be found [right here](https://github.com/superseriousbusiness/gotosocial/releases), with the newest release at the top.
+    Both the `latest` and `snapshot` tags are moving tags, whereas the `X.Y.Z` tags are immutable. The result of pulling a moving tag might change from day to day. `latest` on one system might not be the same `latest` on a different system. It's recommended to use the `X.Y.Z` tags instead so you always know exactly which version of GoToSocial you're running. The list of releases can be found [right here](https://codeberg.org/superseriousbusiness/gotosocial/releases), with the newest release at the top.

 ### Host

--- a/docs/getting_started/installation/metal.md
+++ b/docs/getting_started/installation/metal.md
@@ -34,14 +34,14 @@ cd /gotosocial
 Now, download the latest GoToSocial release archive corresponding to the operating system and architecture you're running on.

 !!! tip
-    You can find the list of releases [right here](https://github.com/superseriousbusiness/gotosocial/releases), arranged with the newest release at the top.
+    You can find the list of releases [right here](https://codeberg.org/superseriousbusiness/gotosocial/releases), arranged with the newest release at the top.

 For example, to download a version for running on 64-bit Linux:

 ```bash
 GTS_VERSION=X.Y.Z # replace this
 GTS_TARGET=linux_amd64
-wget https://github.com/superseriousbusiness/gotosocial/releases/download/v${GTS_VERSION}/gotosocial_${GTS_VERSION}_${GTS_TARGET}.tar.gz
+wget https://codeberg.org/superseriousbusiness/gotosocial/releases/download/v${GTS_VERSION}/gotosocial_${GTS_VERSION}_${GTS_TARGET}.tar.gz
 ```

 Then extract it:
--- a/docs/locales/zh/admin/backup_and_restore.md
+++ b/docs/locales/zh/admin/backup_and_restore.md
@@ -178,7 +178,7 @@ hooks:

 对于 PostgreSQL，你应该使用 `postgresql_databases`。

-`patterns_from` 中提到的文件可以通过转换 GoToSocial CLI 媒体命令 [`list-attachments`](cli.md#gotosocial-admin-media-list-attachments) 和 [`list-emojis`](cli.md#gotosocial-admin-media-list-emojis) 的输出来创建。要生成正确的模式，您可以使用 [`media-to-borg-patterns.py`](https://github.com/superseriousbusiness/gotosocial/tree/main/example/borgmatic/media-to-borg-patterns.py) 脚本。有关 Borg 模式如何工作的详情，参见 [他们的文档](https://man.archlinux.org/man/borg-patterns.1)。
+`patterns_from` 中提到的文件可以通过转换 GoToSocial CLI 媒体命令 [`list-attachments`](cli.md#gotosocial-admin-media-list-attachments) 和 [`list-emojis`](cli.md#gotosocial-admin-media-list-emojis) 的输出来创建。要生成正确的模式，您可以使用 [`media-to-borg-patterns.py`](https://codeberg.org/superseriousbusiness/gotosocial/tree/main/example/borgmatic/media-to-borg-patterns.py) 脚本。有关 Borg 模式如何工作的详情，参见 [他们的文档](https://man.archlinux.org/man/borg-patterns.1)。

 您需要将该文件放在您的 GoToSocial 实例上，并确保该文件是可执行的。它需要 Python 3，安装 Borg 和 Borgmatic 后您应该已经具备。它仅依赖于 Python 标准库。

--- a/docs/locales/zh/admin/cli.md
+++ b/docs/locales/zh/admin/cli.md
@@ -13,7 +13,7 @@ GoToSocial - 一个联邦制社交媒体服务器

 帮助文档参见：https://docs.gotosocial.org。

-代码仓库：https://github.com/superseriousbusiness/gotosocial
+代码仓库：https://codeberg.org/superseriousbusiness/gotosocial

 用法：
  gotosocial [command]
--- a/docs/locales/zh/advanced/security/sandboxing.md
+++ b/docs/locales/zh/advanced/security/sandboxing.md
@@ -12,7 +12,7 @@
 我们提供了一个 GoToSocial 的 AppArmor 示例策略，你可以按以下步骤获取并安装：

 ```sh
-$ curl -LO 'https://github.com/superseriousbusiness/gotosocial/raw/main/example/apparmor/gotosocial'
+$ curl -LO 'https://codeberg.org/superseriousbusiness/gotosocial/raw/main/example/apparmor/gotosocial'
 $ sudo install -o root -g root gotosocial /etc/apparmor.d/gotosocial
 $ sudo apparmor_parser -Kr /etc/apparmor.d/gotosocial
 ```
--- a/docs/locales/zh/advanced/sqlite-networked-storage.md
+++ b/docs/locales/zh/advanced/sqlite-networked-storage.md
@@ -32,4 +32,4 @@ SQLite 的运行模式假定数据库和使用它的进程或应用程序位于
 * `db-sqlite-journal-mode`
 * `db-sqlite-synchronous`

-我们不提供任何建议，因为这将根据你使用的解决方案而有所不同。请参阅 [此问题](https://github.com/superseriousbusiness/gotosocial/issues/3360#issuecomment-2380332027)以了解你可能设置的值。
+我们不提供任何建议，因为这将根据你使用的解决方案而有所不同。请参阅 [此问题](https://codeberg.org/superseriousbusiness/gotosocial/issues/3360#issuecomment-2380332027)以了解你可能设置的值。
--- a/docs/locales/zh/advanced/tracing.md
+++ b/docs/locales/zh/advanced/tracing.md
@@ -19,7 +19,7 @@ tracing-insecure-transport: true
 [obs]: ../configuration/observability.md
 [tempo]: https://grafana.com/oss/tempo/
 [grafana]: https://grafana.com/oss/grafana/
-[ext]: https://github.com/superseriousbusiness/gotosocial/tree/main/example/tracing
+[ext]: https://codeberg.org/superseriousbusiness/gotosocial/tree/main/example/tracing

 ## 查询和可视化追踪

--- a/docs/locales/zh/api/authentication.md
+++ b/docs/locales/zh/api/authentication.md
@@ -30,7 +30,7 @@ curl \

    本着这种精神，上述示例使用了`read`，这意味着当未来支持范围令牌时，应用将仅限于执行`read`操作。

-    你可以在[此处](https://github.com/superseriousbusiness/gotosocial/issues/2232)阅读更多关于计划中 OAuth 安全功能的信息。
+    你可以在[此处](https://codeberg.org/superseriousbusiness/gotosocial/issues/2232)阅读更多关于计划中 OAuth 安全功能的信息。

 成功调用会返回一个带有 `client_id` 和 `client_secret` 的响应，我们将在后续流程中需要使用这些信息。它看起来像这样：

--- a/docs/locales/zh/api/swagger.md
+++ b/docs/locales/zh/api/swagger.md
@@ -14,8 +14,8 @@ GoToSocial 使用 [go-swagger](https://github.com/go-swagger/go-swagger) 从代
    
    有关更多背景信息，请参见以下问题：
    
-    - [#1958](https://github.com/superseriousbusiness/gotosocial/issues/1958)
-    - [#1944](https://github.com/superseriousbusiness/gotosocial/issues/1944)
-    - [#2641](https://github.com/superseriousbusiness/gotosocial/issues/2641)
+    - [#1958](https://codeberg.org/superseriousbusiness/gotosocial/issues/1958)
+    - [#1944](https://codeberg.org/superseriousbusiness/gotosocial/issues/1944)
+    - [#2641](https://codeberg.org/superseriousbusiness/gotosocial/issues/2641)

 <swagger-ui src="swagger.yaml"/>
--- a/docs/locales/zh/api/swagger.yaml
+++ b/docs/locales/zh/api/swagger.yaml
@@ -1562,7 +1562,7 @@ definitions:
            max_profile_fields:
                description: |-
                    此实例允许每个账户设置的最大附加字段数。
-                    目前不可配置，硬编码为 6。详见 (https://github.com/superseriousbusiness/gotosocial/issues/1876)
+                    目前不可配置，硬编码为 6。详见 (https://codeberg.org/superseriousbusiness/gotosocial/issues/1876)
                format: int64
                type: integer
                x-go-name: MaxProfileFields
@@ -1947,7 +1947,7 @@ definitions:
                x-go-name: Rules
            source_url:
                description: 本实例部署的软件的源代码 URL，应 AGPL 许可要求提供。
-                example: https://github.com/superseriousbusiness/gotosocial
+                example: https://codeberg.org/superseriousbusiness/gotosocial
                type: string
                x-go-name: SourceURL
            terms:
--- a/docs/locales/zh/configuration/database.md
+++ b/docs/locales/zh/configuration/database.md
@@ -131,7 +131,7 @@ db-tls-ca-cert: ""
 # 乘数 8 是一个合理的默认值，但你可能希望为在非常高性能硬件上运行的实例增加此值，或为使用非常慢的 CPU 的实例减少此值。
 #
 # 请注意！！：此设置目前仅适用于 Postgres。SQLite 将始终使用 1 个连接，无论此处设置为何。这种行为将在实现更好的 SQLITE_BUSY 处理时更改。
-# 更多详情请参见 https://github.com/superseriousbusiness/gotosocial/issues/1407。
+# 更多详情请参见 https://codeberg.org/superseriousbusiness/gotosocial/issues/1407。
 #
 # 示例: [16, 8, 10, 2]
 # 默认: 8
--- a/docs/locales/zh/faq.md
+++ b/docs/locales/zh/faq.md
@@ -38,4 +38,4 @@ GoToSocial 默认配置了基于 IP 的[限流规则](./api/ratelimiting.md)，

 ## 为什么还在 Beta 阶段？

-查看[当前 bug 列表](https://github.com/superseriousbusiness/gotosocial/issues?q=is%3Aissue+is%3Aopen+label%3Abug)和[路线图](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/docs/locales/zh/repo/ROADMAP.md)以获取更详细的信息。
+查看[当前 bug 列表](https://codeberg.org/superseriousbusiness/gotosocial/issues?q=is%3Aissue+is%3Aopen+label%3Abug)和[路线图](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/docs/locales/zh/repo/ROADMAP.md)以获取更详细的信息。
--- a/docs/locales/zh/federation/http_signatures.md
+++ b/docs/locales/zh/federation/http_signatures.md
@@ -20,7 +20,7 @@ GoToSocial 使用 [superseriousbusiness/httpsig](https://codeberg.org/superserio

 接收请求时，GtS 将首先尝试验证包含查询参数的签名。如果签名验证失败，它将尝试在不包含查询参数的情况下重新验证签名。

-详细信息请参见 [#894](https://github.com/superseriousbusiness/gotosocial/issues/894)。
+详细信息请参见 [#894](https://codeberg.org/superseriousbusiness/gotosocial/issues/894)。

 ## 传入请求

@@ -38,7 +38,7 @@ ED25519

 GoToSocial 的请求签名在 [internal/transport](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/internal/transport/signing.go) 中实现。

-一旦解决了 https://github.com/superseriousbusiness/gotosocial/issues/2991 ，GoToSocial 将使用 `(created)` 伪标头代替 `date`。
+一旦解决了 https://codeberg.org/superseriousbusiness/gotosocial/issues/2991 ，GoToSocial 将使用 `(created)` 伪标头代替 `date`。

 然而，目前在组装签名时：

@@ -82,4 +82,4 @@ https://example.org/users/example_user#main-key

 与 GoToSocial 联合的外站服务器应从 `publicKey` 字段提取公钥。然后，它们应该使用公钥的 `owner` 字段签名 `GET` 请求，进一步解引用 Actor 的完整版本。

-这种行为是为了避免外站服务器对完整 Actor 端点进行未签名的 `GET` 请求引入的。然而，由于不合规且引发问题，此行为可能会在未来发生变化。在 [此问题](https://github.com/superseriousbusiness/gotosocial/issues/1186) 中进行跟踪。
+这种行为是为了避免外站服务器对完整 Actor 端点进行未签名的 `GET` 请求引入的。然而，由于不合规且引发问题，此行为可能会在未来发生变化。在 [此问题](https://codeberg.org/superseriousbusiness/gotosocial/issues/1186) 中进行跟踪。
--- a/docs/locales/zh/getting_started/index.md
+++ b/docs/locales/zh/getting_started/index.md
@@ -64,7 +64,7 @@ GoToSocial 的轻量系统要求意味着它在配置良好的单板计算机上
 !!! warning "云存储卷"
    并非所有的云 VPS 存储都相同，声称基于 SSD 的存储并不一定适合作为 GoToSocial 实例的运行环境。
    
-    [Hetzner 云卷的性能](https://github.com/superseriousbusiness/gotosocial/issues/2471#issuecomment-1891098323)没有保证，且延迟波动较大。这会导致你的 GoToSocial 实例表现不佳。
+    [Hetzner 云卷的性能](https://codeberg.org/superseriousbusiness/gotosocial/issues/2471#issuecomment-1891098323)没有保证，且延迟波动较大。这会导致你的 GoToSocial 实例表现不佳。

 !!! danger "Oracle 免费套餐"
    如果你打算与多个其他实例和用户联合，[Oracle 云免费套餐](https://www.oracle.com/cloud/free/) 服务器不适合用于 GoToSocial 部署。
@@ -145,7 +145,7 @@ GoToSocial 需要开放端口 `80` 和 `443`。

 ## 集群 / 多节点部署

-GoToSocial 不支持[集群或任何形式的多节点部署](https://github.com/superseriousbusiness/gotosocial/issues/1749)。
+GoToSocial 不支持[集群或任何形式的多节点部署](https://codeberg.org/superseriousbusiness/gotosocial/issues/1749)。

 尽管多个 GtS 实例可以使用相同的 Postgres 数据库和共享的本地存储或相同的对象桶，但 GtS 依赖于大量的内部缓存以保持高效。没有同步这些实例缓存的机制。没有它，你会得到各种奇怪和不一致的行为。不要这样做！

--- a/docs/locales/zh/getting_started/installation/container.md
+++ b/docs/locales/zh/getting_started/installation/container.md
@@ -45,7 +45,7 @@ nano docker-compose.yaml
 * `X.Y.Z`：发布标签。这指向 GoToSocial 的特定、稳定的版本。

 !!! tip "提示"
-    `latest` 和 `snapshot` 标签是动态标签，而 `X.Y.Z` 标签是固定的。拉取动态标签的结果可能每天都会变化。同一系统上的 `latest` 可能与不同系统上的 `latest` 不同。建议使用 `X.Y.Z` 标签，以便你始终确切知道运行的是 GoToSocial 的哪个版本。发布列表可以在[这里](https://github.com/superseriousbusiness/gotosocial/releases)找到，最新的发布在顶部。
+    `latest` 和 `snapshot` 标签是动态标签，而 `X.Y.Z` 标签是固定的。拉取动态标签的结果可能每天都会变化。同一系统上的 `latest` 可能与不同系统上的 `latest` 不同。建议使用 `X.Y.Z` 标签，以便你始终确切知道运行的是 GoToSocial 的哪个版本。发布列表可以在[这里](https://codeberg.org/superseriousbusiness/gotosocial/releases)找到，最新的发布在顶部。

 ### 主机

--- a/docs/locales/zh/getting_started/installation/metal.md
+++ b/docs/locales/zh/getting_started/installation/metal.md
@@ -34,14 +34,14 @@ cd /gotosocial
 现在，下载与你运行的操作系统和架构相对应的最新 GoToSocial 发行版压缩包。

 !!! tip "提示"
-    你可以在[这里](https://github.com/superseriousbusiness/gotosocial/releases)找到按发布时间排列的发布列表，最新的发行版位于最上面。
+    你可以在[这里](https://codeberg.org/superseriousbusiness/gotosocial/releases)找到按发布时间排列的发布列表，最新的发行版位于最上面。

 例如，下载适用于 64 位 Linux 的版本：

 ```bash
 GTS_VERSION=X.Y.Z # 替换此处
 GTS_TARGET=linux_amd64
-wget https://github.com/superseriousbusiness/gotosocial/releases/download/v${GTS_VERSION}/gotosocial_${GTS_VERSION}_${GTS_TARGET}.tar.gz
+wget https://codeberg.org/superseriousbusiness/gotosocial/releases/download/v${GTS_VERSION}/gotosocial_${GTS_VERSION}_${GTS_TARGET}.tar.gz
 ```

 然后解压：
--- a/docs/locales/zh/repo/CONTRIBUTING.md
+++ b/docs/locales/zh/repo/CONTRIBUTING.md
@@ -43,7 +43,7 @@

 目前，我们使用 Github 的问题追踪系统来管理错误报告与功能请求。

-你可以在[此处](https://github.com/superseriousbusiness/gotosocial/issues "GoToSocial 的 Github 问题页")查看所有开放的问题。
+你可以在[此处](https://codeberg.org/superseriousbusiness/gotosocial/issues "GoToSocial 的 Github 问题页")查看所有开放的问题。

 在创建新问题之前，不论是错误还是功能请求，**请现仔细搜索所有仍处于打开状态和已被关闭的问题，以确保它尚未被解决过**。你可以使用 Github 的关键字搜索来进行此操作。如果你的问题与已有问题重复，它将被关闭。

@@ -123,8 +123,6 @@ conda env export -n gotosocial-docs --from-history --override-channels -c conda-

 Golang 的一个特点是，它所依赖的源代码管理路径与 `go.mod` 中使用的路径以及各 Go 文件中的包导入路径相同。这使得使用分支有些棘手。

-假设你要将 GoToSocial 分支到 `github.com/yourgithubname/gotosocial`，然后将存储库克隆到 `~/go/src/github.com/yourgithubname/gotosocial`。你可能会在尝试运行测试或构建时遇到错误，因此你可能会更改 `go.mod` 文件，使模块名称为 `github.com/yourgithubname/gotosocial` 而不是 `github.com/superseriousbusiness/gotosocial`。但这样做会破坏项目中的所有导入路径。这简直是噩梦！于是，你不得不逐一在源代码文件中将 `github.com/superseriousbusiness/gotosocial` 替换为 `github.com/yourgithubname/gotosocial`。这样确实能行得通，但一旦你决定对原始存储库发起合并请求，所有路径变更都会被包含在内！哦不！
-
 正确的解决方案是先派生存储库，然后克隆上游存储库，并将上游存储库的 `origin` 设置为你分支的源。

 有关更多细节，请参阅[这篇博客](https://blog.sgmansfield.com/2016/06/working-with-forks-in-go/)。
@@ -136,11 +134,11 @@ Golang 的一个特点是，它所依赖的源代码管理路径与 `go.mod` 中
 >
 > 现在克隆上游存储库（而非派生的存储库）：
 >
-> `mkdir -p ~/go/src/github.com/superseriousbusiness && git clone git@github.com:superseriousbusiness/gotosocial ~/go/src/github.com/superseriousbusiness/gotosocial`
+> `mkdir -p ~/go/src/code.superseriousbusiness.org && git clone git@codeberg.org:superseriousbusiness/gotosocial ~/go/src/code.superseriousbusiness.org/gotosocial`
 >
 > 转到你的计算机上上游存储库的顶级目录：
 >
-> `cd ~/go/src/github.com/superseriousbusiness/gotosocial`
+> `cd ~/go/src/code.superseriousbusiness.org/gotosocial`
 >
 > 将当前的 origin 远程源重命名为 upstream：
 >
@@ -148,7 +146,7 @@ Golang 的一个特点是，它所依赖的源代码管理路径与 `go.mod` 中
 >
 > 把你的派生分支添加为 origin：
 >
-> `git remote add origin git@github.com:yourgithubname/gotosocial`
+> `git remote add origin git@codeberg.org:username/gotosocial`
 >

 在第一次构建项目之前，一定要运行 `git fetch`。
@@ -159,7 +157,7 @@ Golang 的一个特点是，它所依赖的源代码管理路径与 `go.mod` 中

 要开始构建，你需要先安装 Go。GtS 目前使用 Go 1.21，因此你也应该使用这个版本。安装指南见[此处](https://golang.org/doc/install)。

-安装 go 后，将此存储库克隆到你的 Go 路径中。通常，此路径为 `~/go/src/github.com/superseriousbusiness/gotosocial`。
+安装 go 后，将此存储库克隆到你的 Go 路径中。通常，此路径为 `~/go/src/code.superseriousbusiness.org/gotosocial`。

 安装完上述环境与依赖后，可以尝试构建项目：`./scripts/build.sh`。此命令将构建 `gotosocial` 二进制文件。

@@ -396,7 +394,7 @@ golangci-lint run

 ### 测试

-GoToSocial 提供了一个 [testrig](https://github.com/superseriousbusiness/gotosocial/tree/main/testrig)，包含一些可以用于集成测试的模拟包。
+GoToSocial 提供了一个 [testrig](https://codeberg.org/superseriousbusiness/gotosocial/tree/main/testrig)，包含一些可以用于集成测试的模拟包。

 没有模拟的一个东西是数据库接口，因为使用内存中的 SQLite 数据库比模拟所有东西要简单得多。

--- a/docs/locales/zh/repo/README.md
+++ b/docs/locales/zh/repo/README.md
@@ -258,15 +258,15 @@ GoToSocial 支持 [OpenID Connect (OIDC)](https://openid.net/connect/) 身份提

 ## 已知问题

-由于 GoToSocial 仍处于测试阶段，存在很多错误。我们使用 [GitHub issues](https://github.com/superseriousbusiness/gotosocial/issues?q=is%3Aissue+is%3Aopen+label%3Abug) 跟踪这些问题。
+由于 GoToSocial 仍处于测试阶段，存在很多错误。我们使用 [GitHub issues](https://codeberg.org/superseriousbusiness/gotosocial/issues?q=is%3Aissue+is%3Aopen+label%3Abug) 跟踪这些问题。

-由于每个 ActivityPub 服务端实现对协议的解释略有不同，有些服务端尚未与 GoToSocial 正常联合。我们在 [这个项目](https://github.com/superseriousbusiness/gotosocial/projects/4) 中跟踪这些问题。最终，我们希望确保任何可以与 Mastodon 正确联合的 ActivityPub 实现也能够与 GoToSocial 联合。
+由于每个 ActivityPub 服务端实现对协议的解释略有不同，有些服务端尚未与 GoToSocial 正常联合。我们在 [这个项目](https://codeberg.org/superseriousbusiness/gotosocial/projects/4) 中跟踪这些问题。最终，我们希望确保任何可以与 Mastodon 正确联合的 ActivityPub 实现也能够与 GoToSocial 联合。

 ---

 ## 安装 GoToSocial

-查看我们的 [入门文档](https://docs.gotosocial.org/zh-cn/latest/getting_started/)，并浏览我们的 [发布页面](https://github.com/superseriousbusiness/gotosocial/releases)。
+查看我们的 [入门文档](https://docs.gotosocial.org/zh-cn/latest/getting_started/)，并浏览我们的 [发布页面](https://codeberg.org/superseriousbusiness/gotosocial/releases)。

 <!--releases-start-->
 ### 支持的平台
@@ -340,7 +340,7 @@ Docker 镜像 `superseriousbusiness/gotosocial:latest` 始终对应于最新稳

 要使用二进制发布从主分支运行，请从我们的 [自托管 Minio S3 仓库](https://minio.s3.superseriousbusiness.org/browser/gotosocial-snapshots)下载适合你架构的 .tar.gz 文件。

-S3 存储桶中的快照版二进制发布由 Github 提交哈希控制。要获取最新的，请按上次修改时间排序，或者查看 [这里的提交列表](https://github.com/superseriousbusiness/gotosocial/commits/main)，复制最新的 SHA，并在 Minio 控制台过滤器中粘贴。快照二进制发布会在 28 天后过期，以降低我们的托管成本。
+S3 存储桶中的快照版二进制发布由 Github 提交哈希控制。要获取最新的，请按上次修改时间排序，或者查看 [这里的提交列表](https://codeberg.org/superseriousbusiness/gotosocial/commits/main)，复制最新的 SHA，并在 Minio 控制台过滤器中粘贴。快照二进制发布会在 28 天后过期，以降低我们的托管成本。

 ### 从源代码构建

@@ -373,7 +373,7 @@ S3 存储桶中的快照版二进制发布由 Github 提交哈希控制。要获

 如果你有问题或反馈，可以[加入我们的 Matrix 空间](https://matrix.to/#/#gotosocial-space:superseriousbusiness.org)，地址是 `#gotosocial-space:superseriousbusiness.org`。这是联系开发人员的最快方式。你也可以发送邮件至 [admin@gotosocial.org](mailto:admin@gotosocial.org)。

-对于错误和功能请求，请先查看是否[已有相应问题](https://github.com/superseriousbusiness/gotosocial/issues)，如果没有，可以开一个新问题工单(issue)，或者使用上述渠道提出请求（如果你没有 Github 账户的话）。
+对于错误和功能请求，请先查看是否[已有相应问题](https://codeberg.org/superseriousbusiness/gotosocial/issues)，如果没有，可以开一个新问题工单(issue)，或者使用上述渠道提出请求（如果你没有 Github 账户的话）。

 ---

--- a/docs/locales/zh/repo/ROADMAP.md
+++ b/docs/locales/zh/repo/ROADMAP.md
@@ -47,13 +47,13 @@

 ### 2023 年中

- [x] **话题标签** -- 实现话题标签的联合与查看，让用户发现他们可能感兴趣的帖文。（完成！ https://github.com/superseriousbusiness/gotosocial/pull/2032）。
+- [x] **话题标签** -- 实现话题标签的联合与查看，让用户发现他们可能感兴趣的帖文。（完成！ https://codeberg.org/superseriousbusiness/gotosocial/pulls/2032）。

 ### 2023 年中到年底

- [x] **投票** -- 实现对投票的解析、创建和参与功能。（完成！ https://github.com/superseriousbusiness/gotosocial/pull/2330）
- [x] **静音帖文/贴文串** -- 取消订阅贴文串的回复通知；不在时间线上显示特定帖文。（完成！ https://github.com/superseriousbusiness/gotosocial/pull/2278）
- [x] **有限联合/白名单** -- 允许实例管理员默认阻止与其他实例的联合。（完成！ https://github.com/superseriousbusiness/gotosocial/pull/2200）
+- [x] **投票** -- 实现对投票的解析、创建和参与功能。（完成！ https://codeberg.org/superseriousbusiness/gotosocial/pulls/2330）
+- [x] **静音帖文/贴文串** -- 取消订阅贴文串的回复通知；不在时间线上显示特定帖文。（完成！ https://codeberg.org/superseriousbusiness/gotosocial/pulls/2278）
+- [x] **有限联合/白名单** -- 允许实例管理员默认阻止与其他实例的联合。（完成！ https://codeberg.org/superseriousbusiness/gotosocial/pulls/2200）

 ### 2024 年初

--- a/docs/locales/zh/user_guide/importing_posts.md
+++ b/docs/locales/zh/user_guide/importing_posts.md
@@ -28,7 +28,7 @@

 ## 如何导入你的帖文

-当前，该过程需要借助利用 GTS API 的第三方工具。未来，我们可能会将此功能整合到 GoToSocial 内部：请关注 [issue #2](https://github.com/superseriousbusiness/gotosocial/issues/2) 以获取最新动态。
+当前，该过程需要借助利用 GTS API 的第三方工具。未来，我们可能会将此功能整合到 GoToSocial 内部：请关注 [issue #2](https://codeberg.org/superseriousbusiness/gotosocial/issues/2) 以获取最新动态。

 [`slurp`](https://github.com/VyrCossont/slurp)（由 GTS 开发者 Vyr Cossont 开发）可以导入来自 [Mastodon 归档](https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-mastodon-archive) 和 [Pixelfed 归档](https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-pixelfed-archive) 的帖文。请查阅 `slurp` 的文档、[Mastodon 关于导出数据的说明](https://docs.joinmastodon.org/user/moving/#export) 以及 Jeff Sikes 的文章 [“使用 Slurp 将 Pixelfed 帖文导入 GoToSocial”](https://box464.com/posts/gotosocial-slurp/) 以了解更多细节。你需要熟悉命令行基础，并提前安装 Git 和 Go 编译器。

--- a/docs/locales/zh/user_guide/posts.md
+++ b/docs/locales/zh/user_guide/posts.md
@@ -136,7 +136,7 @@ GoToSocial 允许你在贴文中附加媒体文件，大多数客户端会在贴
 为了避免泄漏你的位置信息，GoToSocial 努力在上传媒体时通过清零 Exif 数据点移除 Exif 信息。

 !!! danger "危险"
-    为了方便和保护隐私，GoToSocial 在上传图片文件时会自动移除 Exif 标签。然而，**无法自动移除 mp4 视频的 Exif 数据**（参见 [#2577](https://github.com/superseriousbusiness/gotosocial/issues/2577)）。
+    为了方便和保护隐私，GoToSocial 在上传图片文件时会自动移除 Exif 标签。然而，**无法自动移除 mp4 视频的 Exif 数据**（参见 [#2577](https://codeberg.org/superseriousbusiness/gotosocial/issues/2577)）。
    
    在你将视频上传至 GoToSocial 之前，建议确保该视频的 Exif 数据标签已经被移除。你可以在线找到多种工具和服务来做到这一点。
    
--- a/docs/user_guide/importing_posts.md
+++ b/docs/user_guide/importing_posts.md
@@ -28,7 +28,7 @@ The limitations on interactions with other accounts are an intentional politenes

 ## How to import your posts

-The process currently requires third-party tools which use the GTS API. In the future, we may integrate this into GoToSocial itself: please follow [issue #2](https://github.com/superseriousbusiness/gotosocial/issues/2) for updates.
+The process currently requires third-party tools which use the GTS API. In the future, we may integrate this into GoToSocial itself: please follow [issue #2](https://codeberg.org/superseriousbusiness/gotosocial/issues/2) for updates.

 [`slurp`](https://github.com/VyrCossont/slurp) (by GTS developer Vyr Cossont) can import [post archives from Mastodon](https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-mastodon-archive) as well as [from Pixelfed](https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-pixelfed-archive). Please consult `slurp`'s docs, [Mastodon's instructions for exporting your data](https://docs.joinmastodon.org/user/moving/#export), and ["Importing Pixelfed Posts to GoToSocial with Slurp" by Jeff Sikes](https://box464.com/posts/gotosocial-slurp/) for more details. You'll need to be familiar with command-line basics, and have Git and a Go compiler installed.

--- a/docs/user_guide/posts.md
+++ b/docs/user_guide/posts.md
@@ -136,7 +136,7 @@ Traditionally, these Exif data points are used by photographers to help them cat
 To avoid leaking information about your location, GoToSocial makes a best-effort attempt to remove Exif information from media when you upload it, by zeroing out Exif data points.

 !!! danger
-    For your convenience and privacy, GoToSocial currently removes Exif tags from image files when they are uploaded. However, **automated removal of Exif data from mp4 videos is not currently supported** (see [#2577](https://github.com/superseriousbusiness/gotosocial/issues/2577)).
+    For your convenience and privacy, GoToSocial currently removes Exif tags from image files when they are uploaded. However, **automated removal of Exif data from mp4 videos is not currently supported** (see [#2577](https://codeberg.org/superseriousbusiness/gotosocial/issues/2577)).
    
    Before you upload a video to GoToSocial, we recommend ensuring that Exif data tags are already removed from the video. You can find various tools and services online for doing this.