[docs] rename assets to public to avoid conflicting with template
|
@ -33,7 +33,7 @@ When your instance encounters a mention or an announce of a status or account it
|
|||
|
||||
It is possible to both block and allow the same domain, and the effect of combining these two things depends on which federation mode your instance is currently using.
|
||||
|
||||
![A flow chart diagram showing how the two different federation modes treat incoming requests.](../assets/diagrams/federation_modes.png)
|
||||
![A flow chart diagram showing how the two different federation modes treat incoming requests.](../public/diagrams/federation_modes.png)
|
||||
|
||||
### In blocklist mode
|
||||
|
||||
|
|
|
@ -20,13 +20,13 @@ Instance moderation settings.
|
|||
|
||||
### Reports
|
||||
|
||||
![List of reports for testing, showing one open report.](../assets/admin-settings-reports.png)
|
||||
![List of reports for testing, showing one open report.](../public/admin-settings-reports.png)
|
||||
|
||||
The reports section shows a list of reports, originating from your local users, or remote instances (shown anonymously as just the name of the instance, without specific username).
|
||||
|
||||
Clicking a report shows if it was resolved (with the reasoning if available), more information, and a list of reported toots if selected by the reporting user. You can also use this view to mark a report as resolved, and fill in a comment. Whatever comment you enter here will be visible to the user that created the report, if that user is from your instance.
|
||||
|
||||
![The detailed view of an open report, showing the reported status and the reason for the report.](../assets/admin-settings-report-detail.png)
|
||||
![The detailed view of an open report, showing the reported status and the reason for the report.](../public/admin-settings-report-detail.png)
|
||||
|
||||
Clicking on the username of the reported account opens that account in the 'Accounts' view, allowing you to perform moderation actions on it.
|
||||
|
||||
|
@ -36,7 +36,7 @@ You can use this section to search for an account and perform moderation actions
|
|||
|
||||
### Federation
|
||||
|
||||
![List of suspended instances, with a field to filter/add new blocks. Below is a link to the bulk import/export interface](../assets/admin-settings-federation.png)
|
||||
![List of suspended instances, with a field to filter/add new blocks. Below is a link to the bulk import/export interface](../public/admin-settings-federation.png)
|
||||
|
||||
In the federation section you can create, delete, and review explicit domain blocks and domain allows.
|
||||
|
||||
|
@ -56,7 +56,7 @@ The domain allows section works much like the domain blocks section, described a
|
|||
|
||||
Through the link at the bottom of the Federation section (or going to `/settings/admin/federation/import-export`) you can do bulk import/export of blocklists and allowlists.
|
||||
|
||||
![List of domains included in an import, providing ways to select some or all of them, change their domains, and update the use of subdomains.](../assets/admin-settings-federation-import-export.png)
|
||||
![List of domains included in an import, providing ways to select some or all of them, change their domains, and update the use of subdomains.](../public/admin-settings-federation-import-export.png)
|
||||
|
||||
Upon importing a list, either through the input field or from a file, you can review the entries in the list before importing a subset. You'll also be warned for entries that use subdomains, providing an easy way to change them to the main domain.
|
||||
|
||||
|
@ -86,7 +86,7 @@ Custom Emoji will be automatically fetched when included in remote toots, but to
|
|||
|
||||
#### Local
|
||||
|
||||
![Local custom emoji section, showing an overview of custom emoji sorted by category. There are a lot of garfields.](../assets/admin-settings-emoji-local.png)
|
||||
![Local custom emoji section, showing an overview of custom emoji sorted by category. There are a lot of garfields.](../public/admin-settings-emoji-local.png)
|
||||
|
||||
This section shows an overview of all the custom emoji enabled on your instance, sorted by their category. Clicking an emoji shows it's details, and provides options to change the category or image, or delete it completely. The shortcode cannot be updated here, you would have to upload it with the new shortcode yourself (and optionally delete the old one).
|
||||
|
||||
|
@ -94,7 +94,7 @@ Below the overview you can upload your own custom emoji, after previewing how th
|
|||
|
||||
#### Remote
|
||||
|
||||
![Remote custom emoji section, showing a list of 3 emoji parsed from the entered toot, garfield, blobfoxbox and blobhajmlem. They can be selected, their shortcode can be tweaked, and they can be assigned to a category, before submitting as a copy or delete operation](../assets/admin-settings-emoji-remote.png)
|
||||
![Remote custom emoji section, showing a list of 3 emoji parsed from the entered toot, garfield, blobfoxbox and blobhajmlem. They can be selected, their shortcode can be tweaked, and they can be assigned to a category, before submitting as a copy or delete operation](../public/admin-settings-emoji-remote.png)
|
||||
|
||||
Through the 'remote' section, you can look up a link to any remote toots (provided the instance isn't suspended). If they use any custom emoji they will be listed, providing an easy way to copy them to the local emoji (for use in your own toots), or disable them ( hiding them from toots).
|
||||
|
||||
|
@ -102,7 +102,7 @@ Through the 'remote' section, you can look up a link to any remote toots (provid
|
|||
|
||||
### Instance Settings
|
||||
|
||||
![Screenshot of the GoToSocial admin panel, showing the fields to change an instance's settings](../assets/admin-settings-instance.png)
|
||||
![Screenshot of the GoToSocial admin panel, showing the fields to change an instance's settings](../public/admin-settings-instance.png)
|
||||
|
||||
Here you can set various metadata for your instance, like the displayed name/title, thumbnail image, (short) description, and contact info.
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ You can open new account sign-ups for your instance by changing the variable `ac
|
|||
|
||||
A sign-up form for your instance will be available at the `/signup` endpoint. For example, `https://your-instance.example.org/signup`.
|
||||
|
||||
![Sign-up form, showing email, password, username, and reason fields.](../assets/signup-form.png)
|
||||
![Sign-up form, showing email, password, username, and reason fields.](../public/signup-form.png)
|
||||
|
||||
Also, your instance homepage and "about" pages will be updated to reflect that registrations are open.
|
||||
|
||||
|
@ -29,11 +29,11 @@ In the meantime, admins and moderators on your instance will receive an email an
|
|||
|
||||
Instance admins and moderators can handle a new sign-up by either approving or rejecting it via the "accounts" -> "pending" section in the admin panel.
|
||||
|
||||
![Admin settings panel open to "accounts" -> "pending", showing one account in a list.](../assets/signup-pending.png)
|
||||
![Admin settings panel open to "accounts" -> "pending", showing one account in a list.](../public/signup-pending.png)
|
||||
|
||||
If you have no sign-ups, the list pictured above will be empty. If you have a pending account sign-up, however, you can click on it to open that account in the account details screen:
|
||||
|
||||
![Details of a new pending account, giving options to approve or reject the sign-up.](../assets/signup-account.png)
|
||||
![Details of a new pending account, giving options to approve or reject the sign-up.](../public/signup-account.png)
|
||||
|
||||
At the bottom, you will find actions that let you approve or reject the sign-up.
|
||||
|
||||
|
|
|
@ -39,6 +39,6 @@ If you wanted to see all GoToSocial traces, you could instead run:
|
|||
|
||||
Once you select a trace, a second panel will open up visualising the span. You can drill down from there, by clicking into every sub-span to see what it was doing.
|
||||
|
||||
![Grafana showing a trace for the /api/v1/instance endpoint](../assets/tracing.png)
|
||||
![Grafana showing a trace for the /api/v1/instance endpoint](../public/tracing.png)
|
||||
|
||||
[traceql]: https://grafana.com/docs/tempo/latest/traceql/
|
||||
|
|
|
@ -914,7 +914,7 @@ Now, `remote_1` boosts/reblogs a post from a third account, `remote_2`, residing
|
|||
|
||||
`local_account` does not follow `remote_2`, and neither does anybody else on `our.server`, which means that `our.server` has not seen this post by `remote_2` before.
|
||||
|
||||
![A diagram of the conversation thread, showing the post from remote_2, and possible ancestor and descendant posts](../assets/diagrams/conversation_thread.png)
|
||||
![A diagram of the conversation thread, showing the post from remote_2, and possible ancestor and descendant posts](../public/diagrams/conversation_thread.png)
|
||||
|
||||
What GoToSocial will do now, is 'dereference' the post by `remote_2` to check if it is part of a thread and, if so, whether any other parts of the thread can be obtained.
|
||||
|
||||
|
|
|
@ -20,7 +20,7 @@ You can find more detail on system requirements below, but in short you should a
|
|||
|
||||
For a small instance (1-20 active users), GoToSocial will likely hover consistently between 250MB and 350MB of RAM usage once the internal caches are hydrated:
|
||||
|
||||
![Grafana graph showing GoToSocial heap in use hovering around 250MB and spiking occasionally to 400MB-500MB.](../assets/getting-started-memory-graph.png)
|
||||
![Grafana graph showing GoToSocial heap in use hovering around 250MB and spiking occasionally to 400MB-500MB.](../public/getting-started-memory-graph.png)
|
||||
|
||||
In the graph above you can see that RAM usage spikes during periods of load. This happens, for example, when when a status gets boosted by someone with many followers, or when the embedded `ffmpeg` binary is decoding or reencoding media files into thumbnails (especially larger video files).
|
||||
|
||||
|
|
|
@ -33,7 +33,7 @@ GoToSocial 当前提供“黑名单”和“白名单”联合模式,可以通
|
|||
|
||||
可以同时屏蔽和允许同一个域,结合这两者的效果取决于你的实例当前使用的联合模式。
|
||||
|
||||
![一个流程图,显示两种不同联合模式如何处理传入的请求。](../assets/diagrams/federation_modes.png)
|
||||
![一个流程图,显示两种不同联合模式如何处理传入的请求。](../public/diagrams/federation_modes.png)
|
||||
|
||||
### 在黑名单模式下
|
||||
|
||||
|
|
|
@ -20,13 +20,13 @@ GoToSocial 管理设置面板使用 [管理 API](https://docs.gotosocial.org/zh-
|
|||
|
||||
### 举报
|
||||
|
||||
![一个展示未解决举报的举报列表。](../assets/admin-settings-reports.png)
|
||||
![一个展示未解决举报的举报列表。](../public/admin-settings-reports.png)
|
||||
|
||||
举报部分显示来自本站用户或外站(匿名显示,仅显示实例名称,不显示具体用户名)的举报列表。
|
||||
|
||||
点击举报可以查看其是否已解决(若有理由则显示),更多信息,以及由举报用户选定的被举报贴文列表。你也可以在此视图中将举报标记为已解决,并填写评论。如果该用户来自你的实例,你在此处输入的任何评论都会对创建举报的用户可见。
|
||||
|
||||
![待处理的举报的详细视图,显示被举报的贴文和举报理由。](../assets/admin-settings-report-detail.png)
|
||||
![待处理的举报的详细视图,显示被举报的贴文和举报理由。](../public/admin-settings-report-detail.png)
|
||||
|
||||
点击被举报账户的用户名会在“账户”视图中打开该账户,从而允许你对其执行管理操作。
|
||||
|
||||
|
@ -36,7 +36,7 @@ GoToSocial 管理设置面板使用 [管理 API](https://docs.gotosocial.org/zh-
|
|||
|
||||
### 联合
|
||||
|
||||
![已封禁实例列表,有一个字段用于过滤/添加新的屏蔽。下面是批量导入/导出界面的链接](../assets/admin-settings-federation.png)
|
||||
![已封禁实例列表,有一个字段用于过滤/添加新的屏蔽。下面是批量导入/导出界面的链接](../public/admin-settings-federation.png)
|
||||
|
||||
在联合部分,你可以创建、删除和审核明确的域名屏蔽和域名允许。
|
||||
|
||||
|
@ -56,7 +56,7 @@ GoToSocial 管理设置面板使用 [管理 API](https://docs.gotosocial.org/zh-
|
|||
|
||||
通过联合部分底部的链接(或访问 `/settings/admin/federation/import-export`),你可以批量导入/导出屏蔽列表和允许列表。
|
||||
|
||||
![导入中包含的域列表,提供选择某些或全部域的方法,更改其域,以及更新子域使用方法。](../assets/admin-settings-federation-import-export.png)
|
||||
![导入中包含的域列表,提供选择某些或全部域的方法,更改其域,以及更新子域使用方法。](../public/admin-settings-federation-import-export.png)
|
||||
|
||||
通过输入字段或文件导入列表后,你可以在导入子集之前查看列表中的条目。你还会在使用子域的条目中收到警告,此处还提供一种轻松将其更改为主域的方法。
|
||||
|
||||
|
@ -86,7 +86,7 @@ GoToSocial 管理设置面板使用 [管理 API](https://docs.gotosocial.org/zh-
|
|||
|
||||
#### 本站
|
||||
|
||||
![本站自定义表情部分,显示按类别排序的自定义表情概览。有很多加菲猫表情。](../assets/admin-settings-emoji-local.png)
|
||||
![本站自定义表情部分,显示按类别排序的自定义表情概览。有很多加菲猫表情。](../public/admin-settings-emoji-local.png)
|
||||
|
||||
此部分显示你的实例上启用的所有自定义表情的概览,按类别排序。点击某个表情可显示其详细信息,并提供更改类别或图像的选项,或完全删除它。这里无法更新短代码,你需要自己上传带有新短代码的表情(可以选择删除旧的表情)。
|
||||
|
||||
|
@ -94,7 +94,7 @@ GoToSocial 管理设置面板使用 [管理 API](https://docs.gotosocial.org/zh-
|
|||
|
||||
#### 外站
|
||||
|
||||
![外站自定义表情部分,显示从输入的贴文中解析的 3 个表情的列表: blobcat、blobfoxbox 和 blobhajmlem。可以选择它们,微调短代码,并在提交复制或删除操作前为其分配类别](../assets/admin-settings-emoji-remote.png)
|
||||
![外站自定义表情部分,显示从输入的贴文中解析的 3 个表情的列表: blobcat、blobfoxbox 和 blobhajmlem。可以选择它们,微调短代码,并在提交复制或删除操作前为其分配类别](../public/admin-settings-emoji-remote.png)
|
||||
|
||||
通过“外站”部分,你可以查找任何外站贴文的链接(前提是该实例未被封禁)。如果使用了任何自定义表情,它们将被列出,这样就提供了一种轻松复制到本站表情的方法(供你自己在贴文中使用),或者也可以禁止它们(从贴文中隐藏)。
|
||||
|
||||
|
@ -102,7 +102,7 @@ GoToSocial 管理设置面板使用 [管理 API](https://docs.gotosocial.org/zh-
|
|||
|
||||
### 实例设置
|
||||
|
||||
![GoToSocial 管理面板的截图,显示了更改实例设置的字段](../assets/admin-settings-instance.png)
|
||||
![GoToSocial 管理面板的截图,显示了更改实例设置的字段](../public/admin-settings-instance.png)
|
||||
|
||||
在这里,你可以为你的实例设置各种元数据,如显示名称/标题、缩略图、(简短)描述和联系信息。
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
你的实例将会在 `/signup` 端点提供注册表单。例如,`https://your-instance.example.org/signup`。
|
||||
|
||||
![注册表单,显示电子邮件、密码、用户名和理由字段。](../assets/signup-form.png)
|
||||
![注册表单,显示电子邮件、密码、用户名和理由字段。](../public/signup-form.png)
|
||||
|
||||
此外,你的实例主页和“关于”页面将更新,以反映注册现已开放。
|
||||
|
||||
|
@ -29,11 +29,11 @@
|
|||
|
||||
实例管理员和版主可以通过管理面板中的“账户” -> “待处理”部分来审批或拒绝新注册。
|
||||
|
||||
![管理员设置面板打开到“账户” -> “待处理”,显示列表中有一个账户。](../assets/signup-pending.png)
|
||||
![管理员设置面板打开到“账户” -> “待处理”,显示列表中有一个账户。](../public/signup-pending.png)
|
||||
|
||||
如果没有注册申请,以上列表将为空。如果有待处理的注册申请,你可以点击打开账户详情页:
|
||||
|
||||
![新待处理账户详情,提供批准或拒绝注册的选项。](../assets/signup-account.png)
|
||||
![新待处理账户详情,提供批准或拒绝注册的选项。](../public/signup-account.png)
|
||||
|
||||
在底部,你会看到批准或拒绝注册的操作选项。
|
||||
|
||||
|
|
|
@ -39,6 +39,6 @@ tracing-insecure-transport: true
|
|||
|
||||
选择一个追踪后,将打开第二个面板,显示对应数据跨度的可视化视图。你可以从那里深入浏览,通过点击每个子跨度查看其执行的操作。
|
||||
|
||||
![Grafana 显示 /api/v1/instance 端点的追踪](../assets/tracing.png)
|
||||
![Grafana 显示 /api/v1/instance 端点的追踪](../public/tracing.png)
|
||||
|
||||
[traceql]: https://grafana.com/docs/tempo/latest/traceql/
|
||||
|
|
|
@ -907,7 +907,7 @@ GoToSocial 通过在对话贴文串上下迭代,尽可能获取外站贴文,
|
|||
|
||||
`local_account` 未关注 `remote_2`,`our.server` 上也没有其他人关注,因此 `our.server` 未曾见过 `remote_2` 的这篇贴文。
|
||||
|
||||
![贴文串的示意图,展示了来自 remote_2 的贴文,以及可能的祖先和后代贴文](../assets/diagrams/conversation_thread.png)
|
||||
![贴文串的示意图,展示了来自 remote_2 的贴文,以及可能的祖先和后代贴文](../public/diagrams/conversation_thread.png)
|
||||
|
||||
此时,GoToSocial 会对 `remote_2` 的贴文进行“解引用”,检查其是否属于某个贴文串,以及贴文串的其他部分是否可以获取。
|
||||
|
||||
|
|
|
@ -14,7 +14,7 @@ CSS(级联样式表)是一种与 HTML 一起使用的编码语言,它决
|
|||
|
||||
这是一个标准的 GoToSocial 账户页面:
|
||||
|
||||
![一个 GoToSocial 测试账户页面。标准配色方案是灰色、蓝色和橙色。](./../assets/cssstandard.png)
|
||||
![一个 GoToSocial 测试账户页面。标准配色方案是灰色、蓝色和橙色。](./../public/cssstandard.png)
|
||||
|
||||
假设我们想将背景颜色改为黑色而不是灰色。
|
||||
|
||||
|
@ -30,7 +30,7 @@ CSS(级联样式表)是一种与 HTML 一起使用的编码语言,它决
|
|||
|
||||
如果我们返回到账户页面并刷新页面,现在它看起来是这样的:
|
||||
|
||||
![同一个 GoToSocial 测试账户页面。背景现在是黑色。](./../assets/cssblack.png)
|
||||
![同一个 GoToSocial 测试账户页面。背景现在是黑色。](./../public/cssblack.png)
|
||||
|
||||
如果我们想要更炫一点,可以使用下面的 CSS 代码为背景添加渐变效果:
|
||||
|
||||
|
@ -42,7 +42,7 @@ CSS(级联样式表)是一种与 HTML 一起使用的编码语言,它决
|
|||
|
||||
保存 CSS 并刷新账户页面后,页面现在看起来是这样的:
|
||||
|
||||
![同一个 GoToSocial 测试账户页面。背景现在从深红色开始,向下渐变为紫色。](./../assets/cssgradient.png)
|
||||
![同一个 GoToSocial 测试账户页面。背景现在从深红色开始,向下渐变为紫色。](./../public/cssgradient.png)
|
||||
|
||||
## 可访问性
|
||||
|
||||
|
|
|
@ -53,7 +53,7 @@ GoToSocial 支持使用 `Move` 活动进行账号迁移。
|
|||
|
||||
然后,进入“迁移”部分,查看“别名账号”子部分:
|
||||
|
||||
![展示已填写账号别名的别名账号子部分。](../assets/migration-aliasing.png)
|
||||
![展示已填写账号别名的别名账号子部分。](../public/migration-aliasing.png)
|
||||
|
||||
在第一个还未填写账号别名框中,输入你希望**发起迁移**的账号的 URL。这表示你要发起迁移的账号属于你,即你“也被称为”该账号。
|
||||
|
||||
|
@ -65,7 +65,7 @@ GoToSocial 支持使用 `Move` 活动进行账号迁移。
|
|||
|
||||
在 Mastodon 上,“账号迁移”设置部分看起来如下:
|
||||
|
||||
![Mastodon “账号迁移”设置页面。](../assets/migration-mastodon.png)
|
||||
![Mastodon “账号迁移”设置页面。](../public/migration-mastodon.png)
|
||||
|
||||
如果你正在从 Mastodon 账号迁移到 GoToSocial 账号,你会在“新账号代号”字段中填写 GoToSocial 账号的 `@[username]@[domain]` 值。例如,如果你的 GoToSocial 账号用户名是 `@someone`,并且在实例 `example.org` 上,那么在此处输入 `@someone@example.org`。
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
RSS 是[简易信息聚合](https://en.wikipedia.org/wiki/RSS)的缩写。这是一种在网络上共享内容的非常成熟的标准。你可能在你喜欢的新闻网站和博客上看到过这个活泼的橙色 RSS 标志:
|
||||
|
||||
![橙色 RSS 图标](../assets/rss.svg)
|
||||
![橙色 RSS 图标](../public/rss.svg)
|
||||
|
||||
如果你愿意,可以配置你的 GoToSocial 账户,以将你的贴文以 RSS 订阅源的形式发布到网上。这让没有 Fediverse 账户的人也能定期获取你的贴文更新。这非常适合使用 GoToSocial 发布长篇博客形式的贴文,并希望任何人都能轻松阅读它们的情况。
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ GoToSocial 提供了一个设置界面,你可以在这里更新你的贴文和
|
|||
|
||||
## 账户
|
||||
|
||||
![用户设置界面的账户部分截图,显示头像、横幅背景图和昵称的预览,并提供更改它们的表单字段](../assets/user-settings-profile-info.png)
|
||||
![用户设置界面的账户部分截图,显示头像、横幅背景图和昵称的预览,并提供更改它们的表单字段](../public/user-settings-profile-info.png)
|
||||
|
||||
在账户部分,你可以更改昵称、头像和横幅背景图。你还可以选择启用手动批准关注请求,并选择提供公开的贴文 RSS 源。
|
||||
|
||||
|
@ -184,7 +184,7 @@ markdown 设置表示你的贴文应被按 Markdown 格式解析,这是一种
|
|||
|
||||
例如,下图显示了一个公开可见性贴文的默认互动规则,允许任何人点赞或转发,但仅允许粉丝和你关注的人回复。
|
||||
|
||||
![互动规则,图中显示“谁可以点赞” = “任何人”,“谁可以回复” = “粉丝”和“关注的人”,“谁可以转发” = “任何人”。](../assets/user-settings-interaction-policy-1.png)
|
||||
![互动规则,图中显示“谁可以点赞” = “任何人”,“谁可以回复” = “粉丝”和“关注的人”,“谁可以转发” = “任何人”。](../public/user-settings-interaction-policy-1.png)
|
||||
|
||||
请记住,互动规则不具备前向可追溯性。应用默认互动规则之后创建的贴文将默认使用新设置的规则,但在此之前创建的任何贴文将使用创建时的默认规则。
|
||||
|
||||
|
@ -231,7 +231,7 @@ markdown 设置表示你的贴文应被按 Markdown 格式解析,这是一种
|
|||
|
||||
在导出和导入部分,你可以从 GoToSocial 账户导出数据或将数据导入账户。
|
||||
|
||||
![导出/导入页面。](../assets/user-settings-export-import.png)
|
||||
![导出/导入页面。](../public/user-settings-export-import.png)
|
||||
|
||||
### 导出
|
||||
|
||||
|
|
Before Width: | Height: | Size: 102 KiB After Width: | Height: | Size: 102 KiB |
Before Width: | Height: | Size: 90 KiB After Width: | Height: | Size: 90 KiB |
Before Width: | Height: | Size: 125 KiB After Width: | Height: | Size: 125 KiB |
Before Width: | Height: | Size: 95 KiB After Width: | Height: | Size: 95 KiB |
Before Width: | Height: | Size: 200 KiB After Width: | Height: | Size: 200 KiB |
Before Width: | Height: | Size: 224 KiB After Width: | Height: | Size: 224 KiB |
Before Width: | Height: | Size: 109 KiB After Width: | Height: | Size: 109 KiB |
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
Before Width: | Height: | Size: 485 KiB After Width: | Height: | Size: 485 KiB |
Before Width: | Height: | Size: 492 KiB After Width: | Height: | Size: 492 KiB |
Before Width: | Height: | Size: 488 KiB After Width: | Height: | Size: 488 KiB |
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 23 KiB |
Before Width: | Height: | Size: 59 KiB After Width: | Height: | Size: 59 KiB |
Before Width: | Height: | Size: 90 KiB After Width: | Height: | Size: 90 KiB |
Before Width: | Height: | Size: 131 KiB After Width: | Height: | Size: 131 KiB |
Before Width: | Height: | Size: 87 KiB After Width: | Height: | Size: 87 KiB |
Before Width: | Height: | Size: 227 KiB After Width: | Height: | Size: 227 KiB |
Before Width: | Height: | Size: 133 KiB After Width: | Height: | Size: 133 KiB |
Before Width: | Height: | Size: 633 KiB After Width: | Height: | Size: 633 KiB |
Before Width: | Height: | Size: 879 KiB After Width: | Height: | Size: 879 KiB |
Before Width: | Height: | Size: 1.1 KiB After Width: | Height: | Size: 1.1 KiB |
Before Width: | Height: | Size: 76 KiB After Width: | Height: | Size: 76 KiB |
Before Width: | Height: | Size: 110 KiB After Width: | Height: | Size: 110 KiB |
Before Width: | Height: | Size: 72 KiB After Width: | Height: | Size: 72 KiB |
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 17 KiB |
Before Width: | Height: | Size: 650 KiB After Width: | Height: | Size: 650 KiB |
Before Width: | Height: | Size: 652 KiB After Width: | Height: | Size: 652 KiB |
Before Width: | Height: | Size: 635 KiB After Width: | Height: | Size: 635 KiB |
Before Width: | Height: | Size: 639 KiB After Width: | Height: | Size: 639 KiB |
Before Width: | Height: | Size: 855 KiB After Width: | Height: | Size: 855 KiB |
Before Width: | Height: | Size: 631 KiB After Width: | Height: | Size: 631 KiB |
Before Width: | Height: | Size: 682 KiB After Width: | Height: | Size: 682 KiB |
Before Width: | Height: | Size: 637 KiB After Width: | Height: | Size: 637 KiB |
Before Width: | Height: | Size: 680 KiB After Width: | Height: | Size: 680 KiB |
Before Width: | Height: | Size: 658 KiB After Width: | Height: | Size: 658 KiB |
Before Width: | Height: | Size: 663 KiB After Width: | Height: | Size: 663 KiB |
Before Width: | Height: | Size: 653 KiB After Width: | Height: | Size: 653 KiB |
Before Width: | Height: | Size: 266 KiB After Width: | Height: | Size: 266 KiB |
Before Width: | Height: | Size: 98 KiB After Width: | Height: | Size: 98 KiB |
Before Width: | Height: | Size: 62 KiB After Width: | Height: | Size: 62 KiB |
Before Width: | Height: | Size: 102 KiB After Width: | Height: | Size: 102 KiB |
Before Width: | Height: | Size: 108 KiB After Width: | Height: | Size: 108 KiB |
|
@ -14,7 +14,7 @@ This allows you to customize the appearance of your GoToSocial profile for users
|
|||
|
||||
Here's a standard GoToSocial profile page:
|
||||
|
||||
![A GoToSocial test profile page. The standard color scheme of grey, blue, and orange.](./../assets/cssstandard.png)
|
||||
![A GoToSocial test profile page. The standard color scheme of grey, blue, and orange.](./../public/cssstandard.png)
|
||||
|
||||
Let's say we want the background color to be black instead of grey.
|
||||
|
||||
|
@ -30,7 +30,7 @@ We then click on Save Profile Info.
|
|||
|
||||
If we go back to our profile page and refresh the page, it now looks like this:
|
||||
|
||||
![The same GoToSocial test profile page. The background is now black.](./../assets/cssblack.png)
|
||||
![The same GoToSocial test profile page. The background is now black.](./../public/cssblack.png)
|
||||
|
||||
If we want to get really fancy, we can add an ombre effect to the background, by using the following CSS code instead:
|
||||
|
||||
|
@ -42,7 +42,7 @@ If we want to get really fancy, we can add an ombre effect to the background, by
|
|||
|
||||
After saving the css and refreshing the profile page, the profile now looks like this:
|
||||
|
||||
![The same GoToSocial test profile page. The background now starts dark red and fades to purple further down the page.](./../assets/cssgradient.png)
|
||||
![The same GoToSocial test profile page. The background now starts dark red and fades to purple further down the page.](./../public/cssgradient.png)
|
||||
|
||||
## Accessibility
|
||||
|
||||
|
|
|
@ -53,7 +53,7 @@ To do this, you must first log in to the GoToSocial settings panel with your GoT
|
|||
|
||||
From there, go to the "Migration" section, and look at the "Alias Account" subsection:
|
||||
|
||||
![The Alias Account subsection, showing a filled-in account alias.](../assets/migration-aliasing.png)
|
||||
![The Alias Account subsection, showing a filled-in account alias.](../public/migration-aliasing.png)
|
||||
|
||||
In the first free account alias box, enter the URL of the account you wish to move **from**. This indicates that the account you wish to move from belongs to you, ie., you are "also known as" the account.
|
||||
|
||||
|
@ -65,7 +65,7 @@ Once you have created the account alias from your GoToSocial account, pointing b
|
|||
|
||||
On Mastodon, the "Account migration" settings section looks something like this:
|
||||
|
||||
![The Mastodon "Account migration" settings page.](../assets/migration-mastodon.png)
|
||||
![The Mastodon "Account migration" settings page.](../public/migration-mastodon.png)
|
||||
|
||||
If you were moving to a GoToSocial account from a Mastodon account, you would fill in the "Handle of the new account" field with the `@[username]@[domain]` value of your GoToSocial account. For example, if your GoToSocial account has username "@someone" and it's on the instance "example.org", you would enter `@someone@example.org` here.
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
RSS stands for [Really Simple Syndication](https://en.wikipedia.org/wiki/RSS). It's a very well established standard for sharing content on the web. You might recognize the jolly orange RSS logo from your favorite news websites and blogs:
|
||||
|
||||
![The orange RSS icon](../assets/rss.svg)
|
||||
![The orange RSS icon](../public/rss.svg)
|
||||
|
||||
If you like, you can configure your GoToSocial account to expose an RSS feed of your posts to the web. This allows people to get regular updates about your posts even when they don't have a Fediverse account. This is great when you're using GoToSocial to create longer-form, blog style posts, and you want anyone to be able to read them easily.
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ You will be prompted to log in with your email address and password after provid
|
|||
|
||||
## Profile
|
||||
|
||||
![Screenshot of the profile section of the user settings interface, showing a preview of the avatar, header and display name, and providing form fields to change them](../assets/user-settings-profile-info.png)
|
||||
![Screenshot of the profile section of the user settings interface, showing a preview of the avatar, header and display name, and providing form fields to change them](../public/user-settings-profile-info.png)
|
||||
|
||||
In the profile section you can change your display name, avatar and header images. You can also choose to enable manually approving follow requests, and opt-in to providing a public RSS feed of your posts.
|
||||
|
||||
|
@ -184,7 +184,7 @@ This allows you to do things like:
|
|||
|
||||
For example, the below image shows a policy for Public visibility posts that allows anyone to like or boost, but only allows followers, and people you follow, to reply.
|
||||
|
||||
![Policy showing "Who can like" = "anyone", "Who can reply" = "followers" and "following", and "Who can boost" = "anyone".](../assets/user-settings-interaction-policy-1.png)
|
||||
![Policy showing "Who can like" = "anyone", "Who can reply" = "followers" and "following", and "Who can boost" = "anyone".](../public/user-settings-interaction-policy-1.png)
|
||||
|
||||
Bear in mind that policies do not apply retroactively. Posts created after you've applied a default interaction policy will use that policy, but any post created before then will use whatever policy was the default when the post was created.
|
||||
|
||||
|
@ -231,7 +231,7 @@ Please see the [migration document](./migration.md) for more information on movi
|
|||
|
||||
In the export & import section, you can export data from your GoToSocial account, or import data into it.
|
||||
|
||||
![The export/import page.](../assets/user-settings-export-import.png)
|
||||
![The export/import page.](../public/user-settings-export-import.png)
|
||||
|
||||
### Export
|
||||
|
||||
|
|