Interesting choice over there to close the issue so quickly rather than asking for more info, although you didn't give them much to go on.
I wonder what was the resolution of the previous problem that frequently caused this sort of thing? Was the error handling improved such that we might reasonably expect the processing to keep going when it hits something it doesn't like, or was it just a quick fix for the one specific thing that happened to be breaking it at the time? Did that one make it to the github tracker?
That GitHub tracker is for problems with mbin code, not with instances running Mbin software. The problem that Fedia experienced is very likely caused by a bug of some sort in mbin (or something that Mbin is depending on), but we don’t know for sure what it is yet. Once I’m unemployed in a week, I hope to have more time to debug issues like this and get them resolved.
It's a small instance with fairly low activity (322 monthly active users reported). [edit: excluding this one] The only two local magazines I know with semi-consistent activity and >100 subs are @floatingisfun and @firefox and even the latter seems to be only sporadically active right now. The head mod of the former mag (hitstun) has done some cool local CSS stuff though!
The thing about federation is that you can subscribe just fine to communities on remote instances, so that's where you'll probably end up getting most of your feed from.
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).
The server is busily processing the 1,200,000 messages that queued up over the past 20 hours. It’s died 3 times in the past few minutes, so I’m not optimistic about how long this will take
It has? They had problems with a spammer months ago, but that has been dealt with. If anything, the mods on sh.itjust.works were quicker to remove CP when it came on from other instances, than those instances themselves.
I will lift the ban again. This has happened twice in the past, and each time within ~12 hours, I've had more child porn landing on the server from them. If it happens again though, I will likely leave it that way.
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
if there's anything people can help with don't hesitate to ask in matrix!
One thing I wanted to raise to your attention was asdfzdfj's change to persist logging for docker setups which might make it easier to debug if your logs aren't persisted between container restarts
I mentioned in matrix but just in case since it's a bit of a gotcha for people that run in docker:
as a headsup for anyone running docker, there was a recent change to persist storage of logging just merged. it requires creating a directory and changing permissions on it. the admin guide was updated here but you may need to mkdir -p storage/logs and sudo chown $USER:$USER storage/logs where you run docker from by next sync/release
this may or may not be relevant to you depending on if sync'ing would change your compose setup
I am going to apply this upgrade this weekend. I spent a few hours looking through logs this morning but didn't see anything obvious (there are a breathtaking amount of logs) so gave up and restarted the containers. Will look again when it fails after I make log storage persistent
It's also possible there are no local subscribers, or weren't until now. It's one of the things we need to fix after updating subscriber counts to show accurate information rather than just local information, as it's unclear if a magazine has no local subscribers anymore
Hmm... looking at their instance list and stuff, I get the feeling they might consider fedia an "inactive" instance (based on the information being out of date), which is a bug lemmy has where after upgrades it marks instances as inactive and never updates it again. I will try to get in contact with their admins to confirm
Edit: quick edit, speaking with another german instance owner they said they have the same problem with feddit.de right now and have already spoken to the admins and already taken steps to reset active state but it isn't happening, perhaps more debugging is needed or maybe this is the lemmy federation issue people have been discussing
There is no option to add blocks of any sort (mag/user/domain) from settings, so it's more likely to be intentionally designed that way, i.e. you cannot add nor see a note on a user by going to their page either, you can only hover.
From how I understand it, you cannot block an instance entirely by blocking a domain i.e. fedia.io/d/lemm.ee, what's blocked would be hosted content like lemm.ee/pictrs/..../[file] and not some link posted to lemm.ee/c/abc, you will have to block from the magazine page i.e. fedia.io/m/abc@lemm.ee to get rid of them one by one. Domain blocking is probably intended for sites i.e. fedia.io/d/www-bbc-com.cdn.ampproject.org
EDIT:
I still want to see comments from lemmy.world users.
I think this is achievable via visiting fedia.io/d/lemmy.world/comments if you're looking for a stream of any and all comments (not just replies to your own threads/posts), not completely certain though!
fedia
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.