e569668

I don't want to give false information, but on fedia the majority of 500 pages seemed to stem from the image media cache causing issues (our instance admin detailed the issue here). People were able to mitigate it by disabling images everywhere they could, but one place they can't be disabled is the user avatars on the notification page. I could be wrong, but it's my belief it's those images causing the 500s, and that pushed me to add https://codeberg.org/Kbin/kbin-core/issues/1039 in hopes that if it was possible to disable them the 500s would stop. All this could be wrong though, maybe it's something else like deleted messages or anything else, or maybe there's a better way to solve issues with cached images

Appreciate the level-headed reply in this thread. There's a lot of fingerpointing and hostility going on and I'd appreciate it if people would make less assumptions / jumps to attack people. I'm not sure if you or anyone else can confirm, but I agree with ernest that federation of mod actions was working once before. Without knowing exactly why it stopped, it's hard to say what is going on.

For instance, I just coordinated with the admins of startrek.website as their latest maintenance started blocking user agents with curl in it, which is what kbin sends, meaning all kbin instances stopped being able to get images from their instance. It seems like this is true for multiple other lemmy instances. I didn't follow up with any other admins at the moment, but I think from that, and the fact that back when I originally signed up people would constantly complain kbin federation was broken when it was lemmy.ml that was blocking kbin, it's not a good idea to jump to assumptions on why something isn't working.

Not just on the roadmap, already in :) (fingers crossed no bugs, no promises ><) example

he’s eventually going to make sure abandoned instances have admins

I think he meant magazines on kbin.social in this context. I don't think he has any way to control another instance and change who runs it, besides a kindly worded letter.

I do try to keep track of kbin instances and how up to date they are and their admins, but I can't really advertise in their place. One thing I've kind of been thinking about is it'd be nice if nodeinfo had information next to current user count of like: desired user count, max user count. Otherwise you have no idea what an instance admin is hoping for, whether it's just their personal instance or they're willing to support tens of thousands of users. Without that I don't want to send people to x instance and suddenly the admin being in for a surprise. But I just looked up nodeinfo and it looks like there's plenty of worms in that can about it being too complex already, so maybe I'll avoid opening my mouth about it... for now.

It looks like all the spam I've seen are from newly registered accounts. Perhaps this is something you've already considered, but would shutting off registration on kbin.social and pointing people to other instances until things are more manageable help?

In hindsight I remember why I filter newest to a timespan, so wanted to make note of it. Right now:
https://fedia.io/m/[email protected]/microblog/newest 500s for me but
https://fedia.io/m/[email protected]/microblog/newest/1w is able to load. so cutting off some of the older posts helps me run into less 500 issues, and I generally don't care too much about old posts unless I'm searching for something. that might be a fedia specific thing though, not sure how 500s are on other instances

In the last week a bunch of the API PRs have been merged into the mainline branch. There's still a few to go (and I imagine a lot of testing / refactoring after), but at least seems promising that the work is still in progress

You filed the issue on it! xD

I remember this happening before so it might be the same thing, auto media preview basically: https://kbin.social/m/kbinMeta/t/77143

https://codeberg.org/Kbin/kbin-core/issues/446

I'm not sure if this is a good suggestion, are you able to delete it via moderation as you're the magazine owner? Someone mentioned having issues deleting their own posts but still could via moderation recently, but I'm not actually sure what that difference means as I haven't moderated any magazines myself.

Definitely, you're right that new timeframe doesn't matter, I meant to type hot all time xD I would expect that to potentially grab like whatever was boosted most in the past but then again the algorithm does tend to show newer things even under hot.

Yea the tag system might need a bit of work. It works great for some magazines, but for others not so much. For example m/help is supposed to be a magazine for kbin help but it pulls in everything under #help which can be anything in the fediverse. I did see someone suggest a way for a magazine to remove it defaulting to using the tag of its name, which doesn't seem like a bad idea to me

Interesting, I've heard people say the same before. I do always sort by newest myself, but I sub to a bunch of magazines and also, say, three mastodon accounts, and that page is basically just solely the mastodon posts, very rarely do I see microblog posts in lemmy/kbin. I guess a filter of magazines vs users would be useful

Edit: Also, is the default view all time for you? I could see that causing a problem as well if it's hot / all time. I mainly have three bookmarks: /hot/12h, /sub/newest/24h, /sub/microblog/newest/1d. Getting all results for all of time by default seemed a bit weird to me, especially for microblog posts

You should be able to see microblog posts of accounts you follow at https://kbin.social/sub/microblog