The feed authentication description is not clear enough

[hexWars]

Clear and concise description of the problem

follow中，校验订阅源所有权时，描述感觉不够清晰

Suggested solution

可以考虑加上更完整的例子，例如可以将示例修改一下

<rss version="2.0">
  <channel>
    <title>网站名</title>
    <description>这里替换成描述</description>
    <link>https://网络链接</link>
    <item>
      文章信息...
    </item>
  </channel>
</rss>

或者是旁边有一个?问号，鼠标移上去浮现具体的例子，不然觉得现在这样不太通俗易懂

另外，关于翻译，其实可以考虑用power来激励翻译者

Alternative

No response

Additional context

No response

Validations

• [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[linear[bot]]

FOL-402 订阅源认证描述不够清晰

[github-actions[bot]]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

FOL-402 The description of feed authentication is not clear enough

[github-actions[bot]]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Clear and concise description of the problem

In follow, when verifying the ownership of the subscription source, the description is not clear enough.

Suggested solution

You can consider adding a more complete example, for example, you can modify the example

<rss version="2.0">
  <channel>
    <title>Website name</title>
    <description>Replace with description</description>
    <link>https://network link</link>
    <item>
      Article information...
    </item>
  </channel>
</rss>

Or there is a ? question mark next to it. Move the mouse up to display specific examples. Otherwise, I feel that it is not easy to understand now.

In addition, regarding translation, you can actually consider using power to motivate translators

Alternative

No response

Additional context

No response

Validations

• [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[follow-reviewer-bot[bot]]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Follow or in the beta—please include it with your comment!