Anytime. Thank you for reaching out.

The admin of startrek.website reached out to me - guessing because of this thread? And seems responsive enough so I’ve removed the block and will work with them on any new issues that arise. Apologies for the trouble.

I’m certainly willing to give startrek another shot - the reports about them were getting overwhelming at one point, which led me to blocking the instance.

I think about this sometimes…

Thanks

Can you send me the ip address for a device that is not working?

I’ll take a look. Apologies for the trouble

The problem is related to a periodic denial of service caused by lots of hits to the login page, which is an extremely expensive operation and exhausts php processes for other things like what you’re seeing.

I will investigate tomorrow. My apologies.

I’ll raise it with the mbin team. My apologies

As far as I can tell, it’s a use case that mbin isn’t handling. I’ll open a GitHub issue when I have some time.

Thanks for tagging me. That account is banned/suspended now.

That one is written for lemmy, and there is no real compatibility between mbin and lemmy. I’m not aware of such a thing for mbin, unfortunately. (Note: I also have a lemmy instance and it doesn’t even work that well there)

I just pulled and applied the latest code. fedia.io was already on v1.8.0, so if the fix was released after that, we should be good to go.

I’m working on it. fediseer is complaining that it can’t communicate with fedia.io so trying to sort that out

Microblogs are basically all the regular fediverse posts (from mastodon et al) that are tagged with the hashtag(s) associate with the magazine.

If you hit the accept button on a report, it will remove the thing that was reported (post, thread, comment, etc), and if you hit reject, it just closes the report.

Btw, Fedia.io is running on a latest gen AMD Epyc with 96 CPUs, an nvme ssd, and 256gb of ddr5 exc memory. And Fedia is the only thing running. So it’s not a capacity issue, but rather some challenges with the code we keep bumping into because (I think) we are pushing it harder than other instances.

I think there is a lag - I see this post reflected on lemmy.world: https://lemmy.world/c/FloatingIsFun@fedia.io?dataType=Post&sort=New

@ryujin470@fedia.io It looks like your post is there: https://lemmy.world/c/nostupidquestions?dataType=Post&sort=New

Apologies - i kicked it and it’s working again :(