Currently it seems that the english translation is seemingly maintained in a separate subdirectory, which means lots of duplicate work when changing things as they could easily drift out of sync. A proper i18n framework would probably be useful.
It is also hard to get into Misskey as a non-Chinese speaker since the translation does not even cover the menus :/

nginxなどのリバースプロキシ必須になったため

Can we change website's license under AGPL instead of MIT?

MFMが使える場所ごとに使われているパーサーが異なる。
ユーザーが使える構文セットもパーサーによって違うので、それを説明したほうが良さそう？

構文セット (パーサー)

• plain parser
• full parser

場所

• ノート本文
• チャット
• CW注釈
• ユーザーの名前
• ユーザーの自己紹介

The files src/docs/api/index.md and src/docs/advanced/api.md seem to have the same or very similar contents. I think one of them could be removed?

ブログのエントリ一覧とか

Which files and directories would have to be saved in a backup? I think it is only

• everything in the /files directory
• database
• configuration in .config/default.yml

I think this information would be important for instance administrators and should be added in misskey-hub/src/docs/admin/.

see also misskey-dev/misskey#7349 and misskey-dev/misskey#7726 (comment)

frontmatterでタグ定義して、同じタグを持つページを一覧できるようにする

Website is responsive, but the navigation menu doesn't appear when touching the hamburger.
Can I haz it? 🍔 🐱

Wrong posting

Misskeyの埋め込み、公開されているノートやユーザーしか埋め込まないんだから、各インスタンスごとにスクリプトを用意するんじゃなくてCDNかなんかで公開するようにしてiframeで埋め込めばいいんじゃねって思った

https://p1.a9z.dev/notes/90ntxln51t

frontmatterで指定できるようにするほか、本文内のリンクを抽出して関連ページを列挙する

https://vssue.js.org/

Keeping track of the instance list is simple so I think I could take care of that, but I am not sure about the acceptance criteria.

1. How many instances should be on the list?
   I think if the list gets too long it might get hard to read.
2. What criteria are there for an instance to be put on the list?
   • Not allowing illegal content is probably obvious, but even with that, what is illegal? Which countries laws?
     • e.g. in Germany: Swastika can be illegal
   • open registrations required?
   • minimum (or maximum) number of users to be notable?
   • maybe something else?

Even with formalized reasons we should probably still not blindly accept every request, there can always be exceptions.

Feature suggestions:
• Make custom CSS part of a custom theme.
OR
• Add Custom CSS in /settings/custom-css to saving a theme OR to a preference backup.
ALSO
• Make entered CSS persistent on a per user base.
• Add SAVE option to any CSS entered into /settings/custom-css.
• Add help information regarding custom CSS options.

Situation
• Custom CSS in /settings/custom-css is not saved with a preferenc backup or theme.
• Custom CSS is not persistent, when logging out and back in - or closing browser tab and then logging back in.
• There is no detailed help information anywhere about the use of custom CSS entered into /settings/custom-css.

The link in the Frequently asked questions page for Misskey apps currently leads to a 404 error. Which is a shame because I'm really wanting to know which apps are available for Misskey.

ダークモードで藍モードにしたときのみ
ライトモードで藍モードにしておき、ダークモードに切り替えたときには問題ない

a file is downloaded instead of the site. The site is working on the port. Nginx:

# For WebSocket
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

proxy_cache_path /tmp/nginx_cache levels=1:2 keys_zone=cache1:16m max_size=1g inactive=720m use_temp_path=off;

server {
    listen 80;
    listen [::]:80;
    server_name bronyfurry.com;

    # For SSL domain validation
    root /var/www/bronyfurry_c_usr/data/www/bronyfurry.com;
    location /.well-known/acme-challenge/ { allow all; }
    location /.well-known/pki-validation/ { allow all; }
    location / { return 301 https://$server_name$request_uri; }
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name bronyfurry.com;

    ssl_session_timeout 1d;
    ssl_session_cache shared:ssl_session_cache:10m;
    ssl_session_tickets off;

    # To use Let's Encrypt certificate

    # To use Debian/Ubuntu's self-signed certificate (For testing or before issuing a certificate)
    ssl_certificate "/var/www/httpd-cert/bronyfurry.com_2022-08-19-08-32_43.crt";
    ssl_certificate_key "/var/www/httpd-cert/bronyfurry.com_2022-08-19-08-32_43.key";

    # SSL protocol settings
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
    ssl_prefer_server_ciphers off;
    ssl_stapling on;
    ssl_stapling_verify on;

    # Change to your upload limit
    client_max_body_size 80m;

    # Proxy to Node
    location / {
        proxy_pass http://127.0.0.1:3000;
        proxy_set_header Host $host;
        proxy_http_version 1.1;
        proxy_redirect off;

        # If it's behind another reverse proxy or CDN, remove the following.
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;

        # For WebSocket
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;

        # Cache settings
        proxy_cache cache1;
        proxy_cache_lock on;
        proxy_cache_use_stale updating;
        add_header X-Cache $upstream_cache_status;
    }
}

Webページに設置されたMisskeyで共有するためのボタンなどで、いちいちユーザーが所属するインスタンスのドメインを入力するのは面倒なので、あらかじめMisskey Hubに所属インスタンスを登録しておき、misskey-hub.net/shareなどのURLにアクセスさせることによって指定のインスタンスの共有ページにリダイレクトする機能があれば便利

Misskeyの機能とかスクショ付きで見せるページ

Vuepressのプラグイン機能使って実装することになりそう

要検討

• 引用
• 検索
• コード(ブロック)
• コード(インライン)
• 数式(ブロック)
• 数式(インライン)
• **寄せ
• small
• イタリック
• 打ち消し線

Currently the API page only covers Miauth. Because that does not work for some use cases (please see my comment: misskey-dev/misskey#6623 (comment)) it would be good to also document the legacy authentification.

Summary

docker buildがとにかく重いので、Docker Hubイメージを使う方法を推奨したほうがよさそう

i18n定義だけこっちで持つ

markdownの中にそういった変数を埋め込む方法がわからない

https://vuejs.org/about/team.html みたいなの

Here some missing documentation:

User interface

Name: AI Mode
Missing content: description of what it does

Name: This account is a cat
Missing content: description of what it does ("Adding furry ears shaped antennas on user avatar")

Admin documentation

Name: ServiceWorker
Missing content: what is needed to be put on public and private key? do I need a 3rd party service? if random should be put, at what format? etc.

Name: Pro account
Missing content: description of what it does

Also some documentation if, for example, we need to edit default.yml, what do we need to do for configuration to take effect: the whole docker-compose build or just docker-compose stop && docker-compose up -d ?

In order to better promote Misskey to Taiwanese, I'd like to contribute with Tradtional Chinese translation. How can I do it? By uploading translated files?

ディープリンク的なものを実装したい

例えばMisskey Hub上で「設定ページはここからアクセスできます」のようなリンクを押すと、まず「あなたのインスタンスのドメインを入力してください」的なダイアログが出て入力すると、他のタブでそのMisskeyインスタンスが開かれてたらそのタブ内で設定ページに遷移して、開かれてなかったら新しいタブでそのインスタンスの設定ページを開くようにしたい

どのように Misskey Hub <-> 任意のMisskeyインスタンス という全く別のサイト同士で通信するかが問題

https://misskey-hub.net/ トップページ部分をスマートフォンなど、横幅が狭い状態で表示した時に左上に表示されている ≡ が表示されますが、これを押してもメニューが表示されません。中の各ページでは正常に機能しているように見えます。

参考:
https://misskey.io/notes/99p986af2a

I wonder if we need to write instructions, about backing up safely a running instance. For disaster recovery 🤔

Cloudflare protection is probably unnecessary for the amount of traffic Misskey hub receives. There is also a possibility to block genuine users.

Also this:

Hello there :)

I found misskey a few days ago and I'm loving it, I saw that it has webhooks support so I'd like to know if it is safe to assume that the json used from the webhooks is compatible with the api endpoints?

(from here https://github.com/misskey-dev/misskey-hub/tree/main/src/docs/api/endpoints)

https://jamstack.org/generators/

hexoが良さそう

This is a feature suggestion.

To edit an existing theme i currntly have to manually copy code to Make a Theme, chang code ther and then save as a new theme (while i can't replace an existing theme).
This is quite tedious and leads to many iterations of half ready themes being saved under uniqu names before on is ready. So

I am missing an option to directly edit an existing and selected theme in Theme Management.

This could be done either by being able to change & save code straight in the code window in Them Management, with a Save button appearing before the Uninstall button.
Alternatively there could be an Edit button (see attachment) already in the same place, simply redirecting to Make a Theme with the selected them already open.

Thank you.

Currently, there is no Contribution Guide for misskey-hub repo.
To avoid duplicating issues and PRs and explain how to contribute, its guide has to be created.

In my opinion, it should be basd on misskey-dev's Contribution Guide.
https://github.com/misskey-dev/misskey/blob/develop/CONTRIBUTING.md

プラグインを公開できるようにしたい
プラグインを追加するときは、このリポジトリにPRを作成してもらうようにする。そうすればレビューが行われてプラグインに悪意のあるコードが含まれてないかなどを事前に確認した上で公開することができる
既に公開したプラグインのバージョンアップも同様のプロセスで行う

翻訳の予定はないのでしょうか…

メンテが面倒
ほとんどのユーザーはDockerで事足りそう