Hi all, so it has been a couple weeks since the initial launch of kbin.run and I'm curious to hear what people's opinions are and how they like the overall experience here vs. other kbin instances. Generally speaking, I think kbin's stability has greatly improved since launch as the first turn on was a very haphazard attempt at...
But what happened to part 1 and 2? I guess we'll never know.
I spent a fair amount of time this weekend optimizing the interaction between NGINX, PHP, Symfony framework tuning handles, Postgres and Cloudflare before I give up on this server and move kbin.run to a more powerful machine. The big change that will improve performance: I'm force rewriting the caching headers on images that are...
At least 1 user needs to be subscribed to a magazine in order for it to receive federated updates, so keep that in mind after searching for a new magazine/community. I get subscribed to everything by default (hopefully Mbin will change this behavior in the future), so if it's not a magazine I want to see in my feed I will...
I've offloaded the image processing to a separate process/server and I've been wondering, has anyone noticed any improvement in image loading over the past few days? I don't like overcomplicating the site's configuration, but I was hoping this change boosts the performance at least a little....
I’m on mobile right now. I tested and this does not happen on other kbin instances. It also seems to happen with some magazines but not others and I’m not sure why—best guess is some of the magazines are totally new to this instance and some are not.
Latest kbin code update has temporarily broken the search feature, waiting for a fix from @ernest; kbin.social is suffering from the same issue as a result....
I'm trying to debug what's going on with federated content from beehaw.org instances. There are a deluge of payload errors in the logs, so it's not yet clear to me what the problem is since I think they were working at one point or another....
There was a server-side permissions issue that was causing federated cached images to not load correctly; the issue should be resolved now.
When I search for magazines my results are mostly empty and never includes magazines from other instances.
It was brought to my attention that avatar uploads are causing 500 errors and upon further investigation, it appears to be related to a bug in the latest code release. I've created an issue in Codeberg for those interested and will update once the issue has been resolved....
I'm temporarily disabling a server-side feature that allows for dynamic client-side content refreshing (push updates). It seems as though this capability has been causing unintentional session timeouts making the site appear frozen/super slow, sorry for any inconvenience... but let me know if you notice any performance...
I'm not signing up for Facebook to use their OAuth service, so please ignore that button to login/register until it is removed from the interface, otherwise you will see a 500 error generated....
I forgot to update the URL for the media storage location in the production .env file, clicking on photos to enlarge should work now.