Seems ok here.
still dead for me. Perhaps they are quietly blocking Tor.
Just tried, looks like you’re right.
Sorry for the late response, but we don’t do anything active to block Tor or VPNs. We do block certain user agents (only the Chrome with version <120 should be relevant here) and IP ranges.
This is the second time this has come up and I’m genuinely confused about how it’s happening. It works consistently for me through Tor.
I am using Ungoogled Chromium older than 120, so apparently that’s the issue. Does that also explain the problem of feddit.uk comments not being seen?
It shouldn’t. For whatever reason mbin can’t seem to resolve Chris’ profile, that’s why the comment isn’t showing up:
I’ll try and see if it’s anything from our side, but it’ll be hard to do without mbin’s logs.
Hi. fwiw I can’t see my own comment when I log on Fedia either. I know there was an issue with comments on other instances getting back to K/MBin and then not propagating further, but (a) I think that got fixed and (b) that isn’t the issue here - it doesn’t appear to have reached Fedia. I can possibly force it to federate by searching for the URL in Fedia, but I’d rather flamingos-cant had a look first.
Regarding my user not being found, that looks like an MBin bug with underscores in usernames. I have a bot with an underscore in the name and it does the same thing. Hmm, I’ll raise it on the issue tracker if it hasn’t been already.
I was able to get an Mbin dev server set up and can confirm it’s nothing on our end:
<my IP address> - - [10/Oct/2025:18:55:06 +0200] "GET /u/i_am_not_a_robot HTTP/2.0" 200 1133 "-" "Mbin/1.8.4 (+https://localhost:8443/agent)"I couldn’t tell you what’s actually going wrong in Mbin as the server isn’t actually processing the requested object.
