BitTorrent support
Clear and concise description of the problem
有很多BitTorrent资源站也采用RSS进行资源分发,例如 https://www.tokyotosho.info/
我个人认为 BitTorrent 目前较难纳入现在的分类方式,即归纳为 Articles, Social Media, Pictures, Videos, Podcasts, and Notifications 中的一种,所以,可以考虑将 BitTorrent 单独开一列。
当然,如果考虑让 BitTorrent 可以在线播放,那么列为 Videos 或 Podcasts 也是合理的。
Suggested solution
增加一个新的 BitTorrent 分类作为 application/x-bittorrent 类型附件订阅源的分类。
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.
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Clear and concise description of the problem
There are many BitTorrent resource sites that also use RSS for resource distribution, such as https://www.tokyotosho.info/
I personally think that it is difficult for BitTorrent to be included in the current classification method, which is summarized as one of Articles, Social Media, Pictures, Videos, Podcasts, and Notifications. Therefore, BitTorrent can be considered to be a separate column.
Of course, if you are considering making BitTorrent available for online streaming, it would also make sense to list it as Videos or Podcasts.
Suggested solution
Added a new BitTorrent category as a category for application/x-bittorrent type attachment feeds.
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.
I am very interested in this requirement, but I am curious if you want to play this BitTorrent directly, download it locally, or send it to some service to download it.
I am very interested in this requirement, but I am curious if you want to play this BitTorrent directly, download it locally, or send it to some service to download it.
从用户的角度来讲,直接播放 BitTorrent 体验会更好。 但从技术实现上讲,在线播放 BitTorrent 可能会有点麻烦,在现有的 actions 中加一个发送到 bt 下载器的 webhook 可能会更简单。 当然,如果是这样的话似乎不值得单开一列,因此,我个人期望能实现直接播放 BitTorrent(并保存到本地)
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!