mirror of
https://github.com/superseriousbusiness/gotosocial.git
synced 2025-10-04 00:29:49 +00:00
[docs] Fix broken links and typos (#4418)
# Description Fix links and typos in docs and settings page: * Fix https://codeberg.org/superseriousbusiness/gotosocial/issues/4328 * Fix https://codeberg.org/superseriousbusiness/gotosocial/issues/4360 Also fix broken issuetracker links as forgejo does not support search queries like "label:bug" The translation for Zh-cn still says "this project" according to google translate, I only fixed the link. ## Checklist Please put an x inside each checkbox to indicate that you've read and followed it: `[ ]` -> `[x]` If this is a documentation change, only the first checkbox must be filled (you can delete the others if you want). - [x] I/we have read the [GoToSocial contribution guidelines](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/CONTRIBUTING.md). - [ ] I/we have discussed the proposed changes already, either in an issue on the repository, or in the Matrix chat. - [x] I/we have not leveraged AI to create the proposed changes. - [x] I/we have performed a self-review of added code. - [x] I/we have written code that is legible and maintainable by others. - [ ] I/we have commented the added code, particularly in hard-to-understand areas. - [x] I/we have made any necessary changes to documentation. - [ ] I/we have added tests that cover new code. - [ ] I/we have run tests and they pass locally with the changes. - [ ] I/we have run `go fmt ./...` and `golangci-lint run`. Reviewed-on: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4418 Co-authored-by: Markus Unterwaditzer <markus-tarpit+git@unterwaditzer.net> Co-committed-by: Markus Unterwaditzer <markus-tarpit+git@unterwaditzer.net>
This commit is contained in:
Markus Unterwaditzer
tobi
parent
f9cb086c53
commit
d9ee6cddea
10 changed files with 18 additions and 18 deletions
|
|
@ -292,9 +292,9 @@ Don't like GtS but still want to use the fediverse? Like GtS but prefer not to u
|
|||
|
||||
## Known Issues
|
||||
|
||||
Since GoToSocial is still in beta, there are plenty of bugs. We use [Codeberg issues](https://codeberg.org/superseriousbusiness/gotosocial/issues?q=is%3Aissue+is%3Aopen+label%3Abug) to track these.
|
||||
Since GoToSocial is still in beta, there are plenty of bugs. We use [Codeberg issues](https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378161) to track these.
|
||||
|
||||
Since every ActivityPub server implementation has a slightly different interpretation of the protocol, some servers don't quite federate properly with GoToSocial yet. We're tracking these issues [in this project](https://codeberg.org/superseriousbusiness/gotosocial/projects/4). Eventually, we want to make sure that any implementation that can federate nicely with Mastodon should also be able to federate with GoToSocial.
|
||||
Since every ActivityPub server implementation has a slightly different interpretation of the protocol, some servers don't quite federate properly with GoToSocial yet. We're tracking these issues [with the federation label](https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378188). Eventually, we want to make sure that any implementation that can federate nicely with Mastodon should also be able to federate with GoToSocial.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -87,8 +87,8 @@ Thirdly, we want to make GtS as customizable as possible by allowing admins to e
|
|||
|
||||
The main technical challenges we foresee on the project are:
|
||||
|
||||
1. Ensuring compatibility with other AP servers (see here: https://codeberg.org/superseriousbusiness/gotosocial/projects/4).
|
||||
2. Ensuring compatibility with clients that use the Mastodon API (see here: https://codeberg.org/superseriousbusiness/gotosocial/projects/5).
|
||||
1. Ensuring compatibility with other AP servers (see federation issues: https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378188).
|
||||
2. Ensuring compatibility with clients that use the Mastodon API (see client compatibility issues: https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378194).
|
||||
3. Designing nuanced federation safety features that allow instance admins to screen federation without totally breaking it. This will require careful design discussions and lots of testing.
|
||||
4. Implementing our own open-source http signature library with a reference implementation of the latest draft of the http signature proposal: https://httpwg.org/http-extensions/draft-ietf-httpbis-message-signatures.html.
|
||||
5. Writing + maintaining our own extensions to the AP protocol (see below).
|
||||
|
|
|
|||
|
|
@ -83,8 +83,8 @@ Thirdly, we want to make GtS as customizable as possible by allowing admins to e
|
|||
|
||||
The main technical challenges we foresee on the project are:
|
||||
|
||||
1. Ensuring compatibility with other AP servers (see here: https://codeberg.org/superseriousbusiness/gotosocial/projects/4).
|
||||
2. Ensuring compatibility with clients that use the Mastodon API (see here: https://codeberg.org/superseriousbusiness/gotosocial/projects/5).
|
||||
1. Ensuring compatibility with other AP servers (see federation issues: https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378188).
|
||||
2. Ensuring compatibility with clients that use the Mastodon API (see client compatibility issues: https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378194).
|
||||
3. Designing nuanced federation safety features that allow instance admins to screen federation without totally breaking it. This will require careful design discussions and lots of testing.
|
||||
4. Implementing our own open-source http signature library with a reference implementation of the latest draft of the http signature proposal: https://httpwg.org/http-extensions/draft-ietf-httpbis-message-signatures.html.
|
||||
5. Writing + maintaining our own extensions to the AP protocol (see below).
|
||||
|
|
|
|||
|
|
@ -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://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.
|
||||
Take a look at the [list of open bugs](https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378161) and the [roadmap](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/ROADMAP.md) for a more detailed rundown.
|
||||
|
|
|
|||
|
|
@ -38,4 +38,4 @@ GoToSocial 默认配置了基于 IP 的[限流规则](./api/ratelimiting.md)，
|
|||
|
||||
## 为什么还在 Beta 阶段？
|
||||
|
||||
查看[当前 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)以获取更详细的信息。
|
||||
查看[当前 bug 列表](https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378161)和[路线图](https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/docs/locales/zh/repo/ROADMAP.md)以获取更详细的信息。
|
||||
|
|
|
|||
|
|
@ -272,9 +272,9 @@ GoToSocial 支持 [OpenID Connect (OIDC)](https://openid.net/connect/) 身份提
|
|||
|
||||
## 已知问题
|
||||
|
||||
由于 GoToSocial 仍处于测试阶段，存在很多错误。我们使用 [Codeberg issues](https://codeberg.org/superseriousbusiness/gotosocial/issues?q=is%3Aissue+is%3Aopen+label%3Abug) 跟踪这些问题。
|
||||
由于 GoToSocial 仍处于测试阶段，存在很多错误。我们使用 [Codeberg issues](https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378161) 跟踪这些问题。
|
||||
|
||||
由于每个 ActivityPub 服务端实现对协议的解释略有不同，有些服务端尚未与 GoToSocial 正常联合。我们在 [这个项目](https://codeberg.org/superseriousbusiness/gotosocial/projects/4) 中跟踪这些问题。最终，我们希望确保任何可以与 Mastodon 正确联合的 ActivityPub 实现也能够与 GoToSocial 联合。
|
||||
由于每个 ActivityPub 服务端实现对协议的解释略有不同，有些服务端尚未与 GoToSocial 正常联合。我们在 [这个项目](https://codeberg.org/superseriousbusiness/gotosocial/issues?labels=378188) 中跟踪这些问题。最终，我们希望确保任何可以与 Mastodon 正确联合的 ActivityPub 实现也能够与 GoToSocial 联合。
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -99,7 +99,7 @@ Profiles can have up to
|
|||
<li><a href="#signup">Register an Account on {{ .instance.Title -}}</a></li>
|
||||
<li><a href="#rules">Rules</a></li>
|
||||
<li><a href="#terms">Terms and Conditions</a></li>
|
||||
<li><a href="#domain-permissions">Domain permissions</a></li>
|
||||
<li><a href="#domain-permissions">Domain Permissions</a></li>
|
||||
</ol>
|
||||
</div>
|
||||
</nav>
|
||||
|
|
@ -173,7 +173,7 @@ Profiles can have up to
|
|||
</div>
|
||||
</section>
|
||||
<section class="about-section" role="region" aria-labelledby="domain-permissions">
|
||||
<h3 id="domain-permissions">Domain permissions</h3>
|
||||
<h3 id="domain-permissions">Domain Permissions</h3>
|
||||
<div class="about-section-contents">
|
||||
<p>
|
||||
ActivityPub instances federate with other instances by exchanging data with them over the network.
|
||||
|
|
@ -206,7 +206,7 @@ Profiles can have up to
|
|||
{{- if .blocklistExposed }}
|
||||
<a href="/about/domain_blocks">View the list of domains blocked by this instance</a>
|
||||
{{- else }}
|
||||
This instance does not publically share its list of blocked domains.
|
||||
This instance does not publicly share its list of blocked domains.
|
||||
{{- end }}
|
||||
</p>
|
||||
<h4>Allowed domains</h4>
|
||||
|
|
@ -215,7 +215,7 @@ Profiles can have up to
|
|||
{{- if .allowlistExposed }}
|
||||
<a href="/about/domain_allows">View the list of domains explicitly allowed by this instance</a>
|
||||
{{- else }}
|
||||
This instance does not publically share its list of explicitly allowed domains.
|
||||
This instance does not publicly share its list of explicitly allowed domains.
|
||||
{{- end }}
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@
|
|||
<ul>
|
||||
<li>GoToSocial-specific: <a href="https://thefedi.wiki/gotosocial/user/gotosocial-servers" rel="nofollow noreferrer noopener" target="_blank">thefedi.wiki list of open registration GoToSocial servers</a></li>
|
||||
<li>Mastodon-specific: <a href="https://joinmastodon.org/servers" rel="nofollow noreferrer noopener" target="_blank">joinmastodon.org server picker</a></li>
|
||||
<li>Various fedi softwares: <a href="https://fedi.garden/" rel="nofollow noreferrer noopener" target="_blank">fedi.garden server picker</a></li>
|
||||
<li>Various fedi tools: <a href="https://fedi.garden/" rel="nofollow noreferrer noopener" target="_blank">fedi.garden server picker</a></li>
|
||||
</ul>
|
||||
{{- if .instance.Registrations }}
|
||||
<p>Or, just <a href="signup">register for an account on this instance</a>!</p>
|
||||
|
|
|
|||
|
|
@ -37,8 +37,8 @@
|
|||
<div class="about-section-contents">
|
||||
<p>
|
||||
Want to log in and start posting?
|
||||
Unlike other ActivityPub softwares, GoToSocial does not provide its own
|
||||
webclient. Instead it implements the Mastodon client API, so you can use
|
||||
Unlike other ActivityPub software, GoToSocial does not provide its own
|
||||
web client. Instead it implements the Mastodon client API, so you can use
|
||||
a variety of third-party clients to log in to your account here:
|
||||
</p>
|
||||
<ul class="applist nodot" role="group">
|
||||
|
|
|
|||
|
|
@ -101,6 +101,6 @@ Instance Logo
|
|||
<h1>{{- .instance.Title -}}</h1>
|
||||
</a>
|
||||
{{- if .showStrap }}
|
||||
<aside>home to {{ template "strapUsers" . }} who wrote {{ template "strapPosts" . }}; knows of {{ template "strapInstances" . }}</aside>
|
||||
<aside>home to {{ template "strapUsers" . }} who have written {{ template "strapPosts" . }}; knows of {{ template "strapInstances" . }}</aside>
|
||||
{{- end }}
|
||||
{{- end }}
|
||||
Loading…
Reference in a new issue