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).
Same here. For multiple posts, if I click on them I only get an error page that says "504 Gateway Time-out." It seems to happen mainly to recent posts.
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
Report at least one of the posts from any spam account you see. I try to suspend and delete them as I see them, but alas I am not omniscient and don’t know where all the spam accounts are
Kbin and Lemmy don't seem to federate admin activity. I get a lot of spam from the various Kbin instances whereas Lemmy spam seems to be dealt with already.
I think fixing this requires dev work on both the Lemmy side and the Kbin side.
I wonder if there is a way for federation to not bring over comments from federated accounts under a certain age to give the admins a chance to remove them?
fedia
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.