Just wanted to mention that some of the issues may likely have been due to issues with Mbin rather than on fedia's side, and we put together an emergency hotfix last night / this morning. The issues had taken out another Mbin instance, so hopefully now that this instance has grabbed those fixes, there will be slightly less queue/db issues (I'd like to say all solved forever but I've learned my lessons).

A 404 just means it hasn't been added to the instance yet, I just added it now by doing https://fedia.io/search?q=%21asktransgender%40lemmy.blahaj.zone (though it'll need a local subscriber to get updates)

On my list is to try to make it clearer on how to add remote magazines. In regards to whether that message means it was a local or remote delete for remote content... From my experience the only time I've seen deletes federate is when it's a remote instance A moderator acting on a remote instance A user post. Meaning if a remote Instance A moderator acts on a remote instance B user, it does not federate.

OsaErisXero mentioned the issue for fixing that in the thread, but for some reason my reply didn't federate, so that's why I'm posting from your local instance

As an update, this should be fixed as of this PR
I was able to verify that I couldn't block before, and could after the change So it should get into the next tagged release version (which will likely be 1.5.0) and eventually be working on this instance

I think at least the first part of this is https://github.com/MbinOrg/mbin/pull/561

It was fixed a couple weeks ago but there hasn't been a tagged release in a while.

I'm not sure what the release plan is for 1.5.0, currently there's some very heavy migrations that require special upgrade instructions so I'd like to get a tagged release sooner rather than later to avoid instance admins running into issues, but I think there's still a lot of work in flight

Thanks, was able to get the logs for the error happening with some help. Seems to be related to their "allowlist" changes to lemmy (at least that's the error being thrown back). I'll try to track down in the code, as I believe I mentioned before I believe it sends a request to unfollow to remotes even when you aren't following, and make a patch soon(tm). (For jerry, this is an mbin bug, so feel free to move this to the mdev mag if you want or it can hang out here but isn't specific to your instance)

Can you describe the steps you're going through to attempt to block it and what you observe? For instance, if I go to https://fedia.io/d/hexbear.net and click block on the side, it instantly appears to work without any errors. I tried from other mbin instances as well and didn't see any errors.

I don't completely disagree, hopefully the PR I linked, once complete, will make it a lot more obvious to people when this scenario occurs. I think from an instance owner perspective, they wouldn't want to constantly be paying the overhead on communities no one has an actual interest in viewing (edit: this isn't worded well, so forgive me, obviously people may want to view it but not have it show up in their sub feed, so perhaps another action item is a way to split subscription lists, which I think was already requested), as it has a very real financial cost to them. But I will keep this in mind, I meant to investigate how lemmy works (whether they also require a subscriber, I mean they do because this is how AP works but they might make a fake user or something, I never had a chance to look, but I'd be curious what tools they have to stop incoming messaging for when an instance owner wants to save bandwidth)

I mentioned in the adjacent post but if you do see magazines acting oddly, it could be there are no local subscribers. Hopefully we get a UI fix in soon with the PR I had mentioned, because it's a bit of a bad user experience now. (I noticed world from lemmy world on debounced's instance was getting no posts, or rarely a post with no likes, and subscribed, and suddenly everything came in fine.) So probably a good idea for people, if you want to see posts from somewhere, make sure to subscribe.

(This was technically always true, but a while back admins were auto subscribed so a magazine would always have 1 subscriber. That changed, and that change was even backported to kbin by ernest, so it should be like that back in kbin too for new magazines.)

It looks like someone from the remote liked it recently, which, and I'm channeling Benti here because I'm not as good at the AP side of things, announced to subscribers which brought it in here. At least that's my best guess

Make sure to subscribe to communities you want. It's not just searching for it and loading it, but if there are no local subscribers it won't get updates (and the last subscriber unsubbing would put it in this situation).

This became a bit harder to tell ever since mbin switched to showing real subscriber numbers rather than local like kbin has. There is an active PR to try to address this issue so users are able to tell when data isn't coming in

@jerry there was a super fast follow up to 1.4.0 to fix a 500 that got introduced https://github.com/MbinOrg/mbin/releases/tag/v1.4.1 (the big warning at the top is to make sure people read the 1.4.0 upgrade docs since this release came in so quickly after it, in case they're running <1.4.0, but you should be all set since you already upgraded)

Fedia runs Mbin at the moment, not /kbin, issues can be reported on github

but assuming you may not have a github account or posting via the fediverse is easier, you can also try posting mbin specific, non-fedia instance questions, comments, or concerns to https://fedia.io/m/Mdev@kbin.run