You can set the default landing page here https://fedia.io/settings/general it's the first option for homepage. The options are all, subscribed, favorites, and moderated, make sure to click save near the bottom and not the delete account button.
The closest you can get is blocking those domains, it won't remove everything from them but there isn't a block instance option at the moment, so remote link posts will still appear from them.
I feel like I've been saying this for a while now but I'm hopeful full release will happen soon and that will hopefully make it easier to chase down bugs, at least different sites might be versioned so we get an idea of when problems manifest.
Just as an FYI there's a pretty bad bug right now https://codeberg.org/Kbin/kbin-core/issues/1019 that makes kbin.social users unable to see text and image posts to kbin.social if they have domains blocked. It seems to only be affecting kbin.social so I can't say for sure if it's in the develop branch or something specific to the setup ernest has. I've been basing my guesses off things like localization versions and, based on that, kbin.social is actually behind in commits compared to other kbins, so that makes me wonder if it's not something in the develop branch, but I could be mistaken, just a heads-up something to watch out for before updating in case of risks (at least there's a way to mitigate it, but as far as I can see it isn't happening on fedia.io)
Regarding image thumbnails, it is quite a mess :( There must be some bugs happening somewhere with the pipeline for caching, and they started being mixed up on kbin.social as well which is worrying
I posted a theory here https://fedia.io/m/kbinMeta@kbin.social/t/221067/-/comment/1196287 when I noticed that: it seems to happen a lot on instances that go down often or don't respond quickly, so my guess was it's having trouble getting a response, and then it just fails and, potentially, uses the next thumbnail value it gets. That's based off of the thumbnails for nearby entries being similar, as I posted in that comment the one that was wrong was using the same image as a post 31 seconds after it was made
As I posted here https://fedia.io/m/fedia/p/66268 I notice it's easier to browse with show thumbnails turned off, as that stops the 500s when the image thumbnail has issues. Sadly it still happens on some pages and I ~think that's because avatars for users, which are also cached, are shown on that page, like the notifications page, and there is no way to disable displaying user avatars on those pages
Just curious, are you still getting 500s? I left Fedia temporarily because the 500s just got unusably bad, but I've noticed I can view my profile and subscriptions without issues now, and the instance I moved to seems like their owner disappeared off the face of the earth, so I'm considering returning, but don't want to run into 500s anymore.
So my profile as you can see still 500s. There's also the duplicate thread / comments issue which persists.
jerry just updated to latest yesterday, so fedia now has a lot of the new changes which should hopefully make it a little more stable, though there was a big effort to fix a lot of the 500s riiiiggghhhhtttt as he updated so I'm not sure if he snuck in the middle of those updates or caught them all. Some times I might get a 500 looking at my sub list, but it will fix itself later. I assume jerry is still running scripts which basically try to resolve those issues on a cron job so it might not work for a bit but then work later.
If it's avatar uploads hopefully it's something simple like being caught inbetween it being broken and fixed for example https://codeberg.org/Kbin/kbin-core/issues/1022 and all it requires is an update
That explains why it was never fixed, the admin running the server seems to have disappeared a week or two before i joined the instance and I haven't seen hide nor hair of them, I even sent them a PM about that issue, but never heard anything back. Considering Fedia still has some issues and even testing the waters recently I've been logged out by the "invalid csrf token" problem, I think I'll just try a different instance again, kbin.run is seeming all right, relatively small, but the owner has been recently active and is updating the instance, even directly posting about the avatar upload bug.
It's surprising, actually, just how few truly active kbin instances there are, and I love the hell out of Jerry, but I think he's got too much on his plate to properly fix up Fedia at the moment, at least, not until kbin is less buggy and he has the time to spare from his many other projects, I hate to step away from Fedia, but since I quit reddit cold turkey and don't use any other social media whatsoever I'm really relying on a baseline level of usability for all features.
fedia
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.