


@neohysteria @admin hi! Please provide the domain for the instance and we'll take a look. Can you also let me know what software is being run? Is it just Mastodon or something else.
By default, any instance should be able to federate with us UNLESS it's a domain we know to be violating our rules (such as permitting hate speech) or being poorly moderated, etc. Can't imagine we'll need you to verify anything (though we certainly wouldn't complain about a cute dog pic)!
However, that doesn't mean there won't be technical issues at times, particularly if it's not a Mastodon <-> Mastodon connection.
@neohysteria @admin Version shouldn't matter, but that's good info to have!
We'll take a look and let you know what we find.
@neohysteria @admin Okay, from our side we aren't imposing any limitations on the domain, however it does look like there's some kind of communication issue between the aforementioned server and ours.
I see you mention the instance limited media from us. Can your instance admin double check what blocks are in place? If the instance ONLY rejects media, I think there shouldn't be any communication failures (for example, we reject media from aethy but we don't have any errors logging for them).
Attached is a screenshot of the basic summary of the instance from blorbo's POV. Feel free to share it with your instance admin, it's nothing sensitive.
@neohysteria @admin oh! That's very odd then because as you can see, there's no blocks whatsoever on our end.
Can you link me an example post where the media isn't loading on the Blorbo side?
Has the media issue ALWAYS been an issue or did the problem started more recently?
Do let me know what your admin finds on their side as far as domain blocks for Blorbo.social go!