You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
💡 功能建议与反馈从这里开始 / Feature ideas and feedback start here
#814
New features you want, opinions on what exists, anything awkward to use - Discussions is the place. A few rules:
One idea per discussion, in the Ideas category, with a title that says what you want, such as "Post list for a Douyin collection". One topic per thread is what lets people vote on it and discuss it, and an accepted idea can be turned straight into an issue.
Search first. If someone has already suggested it, upvote that one (the ⬆ button beside it) and add your own use case instead of opening another. Votes are one of the things that set priorities.
Say what problem you are solving rather than only proposing a solution: "while doing Y, I get stuck at Z". Often what you need already exists and is just hard to find.
Small, one-line feedback - a doc page that did not make sense, a default that gets in the way - can go as a reply to this post.
To be upfront: this is a project maintained by one person. Not every idea will be built, and there are no promised dates. Votes, how widespread a problem is, and fit with the project's direction decide the order. The direction is self-hosting and reading data; engagement actions - liking, following, messaging, automating accounts - are out of scope. If you would like to build something yourself, Contributing walks through adding an endpoint or a console page.
On a lite version: feedback was collected in #784 (closed, still readable). What people asked for is a light deployment that keeps only the parsing endpoints, stores nothing and needs no PostgreSQL, to sit behind plugins such as koishi. To add to it, reply here or open a discussion in Ideas.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
中文 · English below
想要的新功能、对现有功能的意见、用起来别扭的地方,都欢迎在 Discussions 里提。规则只有几条:
不放在这里的:
先说在前面:这是个人维护的项目,不是每个想法都会做,也不承诺时间。投票多少、问题是否普遍、和项目方向是否一致,决定先后。项目的方向是自部署、读取数据;点赞、关注、私信、自动化账号这类互动操作不在范围内。愿意自己动手的,参与开发 里有新增接口和页面的步骤。
关于精简版(lite):之前在 #784 收集过意见(已关闭,内容仍可查看)。大家要的是只保留解析接口、不需要存储、不依赖 PostgreSQL 的轻量部署,用来接在 koishi 这类插件后面。还想补充的,回复这个帖子或在 Ideas 开帖都可以。
English
New features you want, opinions on what exists, anything awkward to use - Discussions is the place. A few rules:
Not here:
To be upfront: this is a project maintained by one person. Not every idea will be built, and there are no promised dates. Votes, how widespread a problem is, and fit with the project's direction decide the order. The direction is self-hosting and reading data; engagement actions - liking, following, messaging, automating accounts - are out of scope. If you would like to build something yourself, Contributing walks through adding an endpoint or a console page.
On a lite version: feedback was collected in #784 (closed, still readable). What people asked for is a light deployment that keeps only the parsing endpoints, stores nothing and needs no PostgreSQL, to sit behind plugins such as koishi. To add to it, reply here or open a discussion in Ideas.
All reactions