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
I'm not sure what ernest is referring to with that, but something definitely does seem to be up with federation of content from kbin over to lemmy.
e.g. in /m/anime_irl the last three threads posted have not federated out. I commented here with a list of 5 lemmy servers I checked on a 24 hour old post that hasn't shown up elsewhere (after noticing my own post wasn't showing up).
There's also something going on with comments added by lemmy users on threads that have federated not going out to other lemmy instances. e.g. on this thread from 5 days ago only my first comment has federated widely; the other comment chain (starting with the user from lemmy.world) are only visible on kbin.social and lemmy.world, as far as I can tell. Not sure if that's exactly the same issue or not, but seems plausible for it to be related if something isn't working correctly with federation right now.
Comments that I've made on lemmy threads have gone through today though.
I will look into this. I will also gradually address federation issues. However, I'm not sure if the problem is on the kbin side. Currently, there are no performance issues; all queues are being cleared in real-time. Communication on my test instances with kbin.social takes a matter of seconds.
Thanks ernest!
A few more data points:
this is an activitypub thing in general and not specific to kbin. if nobody is following you from that instance your posts won't get sent to that instance (as there's no real point!)
the posts of yours that do get sent there are likely there because you commented on a group that someone had been following.
ps: hey @[email protected], attempting to view a comment on it's remote instance (
https://kbin.social/m/kbinDevlog/t/642285/-/comment/3689397for example) redirects me to the login page, whereas doing so on the first post on the thread itself works fine.is this a known issue? it's a bit inconvenient when following kbin content outside kbin (want to make sure i'm not missing any replies and writing the same thing someone already did, which happens fairly often on single user instances such as mine)