e569668

As an update, this should be fixed now https://github.com/MbinOrg/mbin/pull/81 and looks to have been rolled out to this instance. The issue can still happen on user covers and magazine inline icons, which I hope to have a PR for soon™. realized it happens basically anywhere images with alt text appear so going to take more time auditing everything

Minor problem: there’s a new feature of 2fa, but at least for me, going to https://fedia.io/settings/2fa to set it up shows a broken qr code. looks like it’s returning an nginx 404 at the moment

It looks like their instance is having some issues https://programming.dev/post/4308156 granted that says outbound but I just joined their matrix and there are other issues being discussed as well, I might wait on this to see if it’s still happening once things get more sorted

edit: i posted in their matrix support channel to see if they noticed anything odd as well 🤞

That is very weird, their /instances page says kbin still… I wonder if they stopped federating / it got marked as an inactive instance by mistake? lemmy.world for instance shows fedia as mbin… I’m not quite sure what this means but they clearly haven’t gotten node info in a while

this might be https://github.com/MbinOrg/mbin/issues/35

it was fixed in the docs but requires manual change by instance owners that were affected, which this instance appears to be. tl;dr the docs recommended the nginx config add_header Referrer-Policy "no-referrer" always; which broke the style of redirects that were being used, it’s now been changed to recommend add_header Referrer-Policy "same-origin" always;

more info here

edit: I promise I can read… Your description is slightly different, so it might not be this, but still worth trying it out to see if it helps

Both servers are larger than the single server that infosec.pub runs on, yet infosec.pub has about 10x the traffic, and kbin is struggling under the load.

I wonder what the difference is. One thing I have always wondered is if the double comment / post issue is causing tons of double traffic, not to mention double storage / bandwidth / network costs. I really wish there was an easy solution but I haven’t been able to find any answers. The random thing I thought was like, it looks like everything federates with both fedia.io and www.fedia.io, so I was like maybe everything is double sending on its side? (E.G. if you look at lemmy.world or lemm.ee etc they all list fedia twice.) But people didn’t seem that was likely to be the cause, as hopefully everything is deduped by signing keys rather than hostnames. I don’t know enough to investigate further myself.

One thing I’m trying to keep an eye on is sup. Not much information at all besides a snippet of 1 to 1 encrypted messaging for activitypub, but the tidbit of working with any fediverse account is interesting. Potentially that could help deal with the different fediverse implementations of messaging. Of course, like I said, this is just me making up assumptions, it could not work the way I envision it at all. The creator just posted something 5d ago about it with “soon” though, so I’m hoping to read more about it

The short answer is no but the longer answer for what happens in each situation was detailed here: https://codeberg.org/Kbin/kbin-core/issues/1051

lemmy -> kbin = pretends to send but doesn’t

Maybe gremlins, looks like it’s working now. (I have noticed some 500s, but I assume jerry is still running his auto-null-image-fixer script and it will start working eventually). It’s empty though as is the case with federation they don’t automatically pull in things until added so the past content isn’t there

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.

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

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

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.

Just to follow up on this, contributors to kbin investigated and found that startrek.website appears to block user agents that contain “curl” in it now.

Example:

curl -v --user-agent "curl" https://startrek.website/pictrs/image/3ff1b940-75da-4e6b-8948-834ebd4b454c.jpeg

times out while:

curl -v --user-agent "anything-else" https://startrek.website/pictrs/image/3ff1b940-75da-4e6b-8948-834ebd4b454c.jpeg

works. kbin apparently sends User-Agent: Symfony HttpClient (Curl) in its requests for images, which is different than how it handles other fetch requests. they’ve made a PR to change kbin to send the user agent it uses elsewhere in those image requests https://codeberg.org/Kbin/kbin-core/pulls/1098 once that is approved / merged they should start working again as instances update. It’d be nice if, assuming this is all accurate, the block on curl could be removed so people don’t have to wait for the PR / instances to update but I understand if that is difficult

This isn’t really a me thing, this is kbin servers themselves. They all fetch the image from the posts and cache it to make thumbnails on their server which they host themselves. Ever since maintenance, the kbin instances appear to have trouble fetching the images to cache them. I’ll try to gather more data from instance admins, perhaps something changed with the request/response headers or something else that is causing them to get blocked.

It looks like ever since this maintenance, no kbin instances can get images from startrek.website:

https://kbin.run/d/startrek.website
https://kbin.social/d/startrek.website?p=3
https://kbin.cafe/d/startrek.website?p=3
https://fedia.io/d/startrek.website/newest?p=4

(the links atm go to ~3 days ago when maintenance happened but ofc will start to drift as more posts are made)

You can see the thumbnails disappear exactly at the mark of the maintenance and ever since then they’re gone. If you see thumbnails after that, they’re usually wrong ones that are being loaded from different posts (there’s a separate issue in for that now). I was wondering if you were aware of any issues or changes that happened because of this maintenance that would prevent kbin instances from fetching thumbnails? I’ve raised this in the kbin matrix chat as well

@HarkMahlberg I assumed it was a default ublock rule and not one you added so I imagine a lot of people might run into this. Well, “a lot” depending on how often a filename’s sha256 hash starts with ad. At the very least it’s probably good to know about it, even if nothing is changed. But perhaps there’s enough reason to use a different system to name image caches like the name generators a lot of image hosters seem to use. I guess it’s in the devs hands now :) thanks for sharing it

@HarkMahlberg I would consider adding a bug for this to the issue tracker as it seems like a gotcha https://codeberg.org/Kbin/kbin-core/issues

One thing to keep in mind is they don’t federate with kbin.social; so they can’t see your posts or replies, and can’t reply to you. I believe your upvotes won’t federate (maybe to other instances, but not to theirs at least). Downvotes work the same as they do for any other post as those don’t federate in kbin to begin with. One-sided federation in the fediverse seems like it can be a bit confusing to users, I’m not sure in what case it’s a good idea in since it can be like talking to a void.