it may be related to the ongoing federation problems. https://fedia.io/m/french@sopuli.xyz is working now for me. there are no posts in it yet on our instance because no one had subscribed to it until now.
Thanks for the investigation and tips. I was able to see it by querying the substring you mentioned.
I didn’t even think this thread herein posted. Got the 500 error a couple times when posting here and in mdev, and gave up. I forgot that error 500 often happens /after/ the task executes, hence some dupe threads.
I've noticed that a large number of communities on Lemmy.world aren't visible here. You only get a 404. I've noticed this when looking at US state communities:
Ok. I don’t know why this works, but if you search for the magazine (ie search for oregon@lemmy.world) it’ll return a result. After that, the links you posted starts working.
It should receive data from any activity at the other community. The problem seems to be Fedia not receiving data from certain communities.
It's not just the state communities. There's a lot of communities that are missing posts. Even ones that happened recently. For instance: https://fedia.io/m/netsec@lemmy.world
I am not sure what is going on with some of the lemmy.world communities - some do seem to be having issues like netsec, while others like https://fedia.io/m/news@lemmy.world are humming along very well. I'll keep poking at it.
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.)
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
Thanks. That seems to resolve the issue. Though, for a lot of smaller communities, no one is going to subscribe to them here, effectively making them invisible here.
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)
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
To get to another instance there is the "Magazines" link at the top of the page, or just go directly to the one you want such as https://fedia.io/m/anarchychess@sopuli.xyz
To create a new one is under that '+' icon at the top of the page. Looks easy but I haven't tried it yet.
Oh, so I can get an existing community on another server to show up here by subscribing? That sounds ideal as long as the other server has decent uptime.
I'm not sure what goes wrong, assuming kbin.social didn't block fedia, then I suspect some kind of issue at fedia.io. I believe we need to debug this issue on the server-side. Hopefully @jerry can have a look at his logs when trying to execute the search query above and maybe find the root-cause that way.
ok - just looked through logs and I am not seeing anything that looks related to this issue. There are a good number of error 500's coming from kbin.social, but none appear to be around the time of these posts, nor associated with the referenced magazine.
I thought I was logged in but I can’t remember now. I don’t see a 404 now though, just “empty”. There are posts in that magazine though, on its 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.
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)
If you use ublock origin adding the following to the filter list should help.
fedia.io##article.entry:has(aside.meta > a.magazine-inline[href$="@hexbear.netl"])
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
Blocking instances on kbin / mbin does not work though. You will still see the communities threads & users (and getting to that page in the first place is a hassle too since there's no link to it).
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
Oh do you use compact mode? If so, sadly another thing that was fixed a while back that hopefully will be fixed for you next release https://github.com/MbinOrg/mbin/pull/544
The post you showed in the screenshot does look fine to me both in classic and compact view on an instance with latest.
But I'd agree not all of your concerns have been addressed. I don't believe redgifs work (well), so will try to look into that if possible, but might be out of my depth.
The playback continuing is interesting. I had made a change long ago to not download every time it was expanded / collapsed as before it would make a request every single time, instead I changed it to just hide and show it after the first load, so that sounds like a side effect of that. Perhaps there's some way for me to also indicate to pause media, I will check
fedia
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.