/kbin RTR#19 Summary of current work and plans for the near and somewhat distant future
/kbin RTR#19 Summary of current work and plans for the near and somewhat distant future
Today, I am addressing several ongoing issues that prove troublesome in the daily use of the instance. In the coming days, I will be working on several things slated for the next instance update:
- Implementation of a "Support Us" page, listing individuals supporting the project.
- Fix photo management during post/thread editing.
- Improved handling of +18 content, ensuring proper image concealment.
- Exclusion of blocked people and magazines from the sidebar's related/latest posts/entries.
- Implementation of a spoiler system compatible with Lemmy.
- Resolution of several bugs causing the failure to display certain content (error 500).
- Public release of the API, with everything seemingly operational, remaining tasks involve building assets for documentation, which, with multiple nodes, requires additional configuration. Kudos to @rideranton for a job well done!
In the immediate future, I plan to take a break from coding to focus on global kbin.social moderation and work on the new instance setup from Adam:
https://codeberg.org/Kbin/kbin-core/pulls/132
Looking further ahead, I intend to refine the /sub feed by segregating it into observed users, magazines, and both simultaneously, as illustrated here:
https://kbin.social/m/[email protected]/t/638986/Why-Bluesky-over-sth-like-Activitypub#entry-comment-3664917
Additionally, I aim to enhance the tag page with additional filtering options:
https://kbin.social/m/[email protected]/t/641047/this-is-a-bloody-test-bc-i-don-t-know-what#entry-comment-3666758
The first release is anticipated in ? days.
You can track changes in the official repository
https://codeberg.org/Kbin/kbin-core
or on Github
https://github.com/ernestwisniewski/kbin
You're viewing a single thread.
That sounds good, for /kbin seems to generally have troubles with federating to the outside Fediverse. For example, formatted posts or posts with embedded links go out as raw Markdown code, implying that everything else can and will parse it, rather than standard Rich Text.
Also, I sometimes see posts from /kbin with a summary (the same as a content warning on Mastodon; I don't know what /kbin uses that field for), but the post in the summary is the same as the summary, only without hashtags which only appear in the summary.