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/privacy@lemmy.ml/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/test1006@karab.in/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
Is it possible that it's because of something on Lemmy's end?
Edit: forgot to switch to the "new", but the newest visible posts are also 2days old
Very weird, considering federation with Mastodon is working. But it seems there are systematic problems with the federation communities, not only to lemmy but also to mbin (or, at least, fedia.io).
Here's a tiny overview of delays as of the time of writing:
Kbin.social:
!Ukraine_UA (last thread 20 minutes ago) :
!tech (last thread 2 hours ago):
!news (last thread 12 hours ago):
Fedia.io:
!FloatingIsFun (I have no idea what this is, but it's the most active fedia.io magazine with the last thread 9 hours ago):
So, based on this limited sample, it seems like Kbin/kbin.social is currently struggling to federate its communities to both Lemmy and mbin, and that it has been having these problems at least since this weekend. Mbin/fedia.io is not having the same problems, or at least not to the same degree.
Also having the same thing happen over on /m/SquaredCircle for what it's worth. Just noticed last night after a particularly slow day. Logged into my lemmy.zip alt and noticed nothing for near 48h had come across from kbin. Checked another alt on another lemmy instance and it was more or less the same there too.
Fixed, thank you for pointing it out. During the night or in the morning, when there is less traffic, I will try to resend all unsuccessful requests.
This week, I will be setting up test environments for other platforms, so I will try to catch such issues more quickly.
https://lemmy.zip/c/music@kbin.social
@sab @e0qdk
You remain, as always, the best. <3
Works well now, thanks!