e-five

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

Everything about your post is slightly indicative to me of javascript failing, for some reason.

So many actions taken, upvoting / boosting / replying, do javascript actions. However, all of these things have fallbacks in the case either: javascript hasn't fully finished loading on the page yet or javascript requests failed.

For instance, if javascript had failed when I clicked reply to your message, instead this page would've loaded for me https://fedia.io/m/fedia/t/552719/Request-for-errors-on-fedia-io/comment/3937344#add-comment but since it worked, all it did was add a text box under your reply

As I said this is true for all other actions, so when you vote or boost there are also http GET routes that handle those requests.

It's hard for me to guess more than that, it could be the JS is loading a bit slow and you click before the page finishes loading, or it could be a different error like maybe the request fails. There might also be something else involved, I'd have to double check but mercure might involve itself in dynamic page updating as well... Do you happen to notice if pages are still loading when you take actions, or in fact just browse with javascript disabled? There's also that, last I checked, all the JS files had defer on them so don't block page loads, which is what makes this more likely to happen. Whether that's good or not, I can't say, it's been like that since I first looked but might require more research to know whether it can be split between JS that should block page load and JS that can be deferred

@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)

Just to follow up on this a bit I took a look at the code to try to understand why this has always been a problem in /kbin/Mbin. It seems like from cursory reading it will try to send out unsub/unfollow requests on blocking magazines/users even if you aren't subbed or following them. Assuming this is accurate, this has some benefits to make sure the remote removes you, but has the downside of calls to the remote needing to be working in order for a block to happen. I'll try to take a look at making it only send those unsub/unfollow requests if you currently are according to local and see if that makes sense to others

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

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

Edit edit: they say they're waiting for https://github.com/LemmyNet/lemmy/issues/4288#issuecomment-1879052639 to be merged which looks hopefully soon

I wouldn't exactly say mbin is behind kbin, as things have diverged much since the fork. For example, mbin has moderators from lemmy, and lemmy shows mbin moderators. As of latest, mbin gets moderator reports from lemmy (and maybe the other way, I didn't closely review that PR), things like sensitive groups are marked correctly, subscriber and follower counts come from source... Still, there's a lot of work to do for the user experience, many people have made that clear lately, so I'm hoping mbin will be able to gain the contributors needed to make the changes people want to see

Also, yea a lot of /kbin tweaks won't work. I do want to make an eye toggle button to make visible all nsfw on a page, but that might be hindered a bit due to infinite scroll (as well as a user setting to just have it shown by default). In the meantime though, it's just the structure of data changing from javascript to css, so it's always possible to do. I wrote a tampermonkey script able to do so as an example:

// ==UserScript==
// @name         Mbin tweak
// @namespace    http://tampermonkey.net/
// @version      0.1
// @description  Unhide NSFW entries automatically
// @match        https://fedia.io/*
// @require      https://greasyfork.org/scripts/12228/code/setMutationHandler.js
// ==/UserScript==

checkThem([].slice.call(document.querySelectorAll('input[type="checkbox"].sensitive-state')));

setMutationHandler(document, 'input[type="checkbox"].sensitive-state', checkThem);

function checkThem(nodes) {
    nodes.forEach(function(n) { n.checked = true });
}

based on this answer on how to check all checkboxes on a page

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

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