this post was submitted on 30 Mar 2024
56 points (100.0% liked)

Blahaj Lemmy Meta

2304 readers
2 users here now

Blåhaj Lemmy is a Lemmy instance attached to blahaj.zone. This is a group for questions or discussions relevant to either instance.

founded 2 years ago
MODERATORS
56
submitted 7 months ago* (last edited 7 months ago) by -Emma-@fedia.io to c/main@lemmy.blahaj.zone
 

Hey, so I'm on a different instance, and I hope it's not out of place for me to post here. I really like Mbin for its design and features, and I made this account specifically for interacting with LGBTQ+ posts.

Anyway, there are a few things I'd like to discuss, if that's okay.

First, I'd like to know if it's necessary for me to report posts if they've already been reported on Blahaj. Like, is it just a federation delay that causes the bad posts to still be visible for a while, or is my reporting necessary to get them removed?

I've noticed that the recent troll posts are coming from lemmy.today and eviltoast.org, and I'm wondering if these instances should maybe be considered for de-federation from Blahaj. It seems like one or two users are ban-evading by making new accounts on these two instances. Are there any legit users that would be affected by this de-federation?

Also, I wonder if I made a mistake by boosting a few threads recently. Like did I accidentally get the attention of these transphobes? Should I refrain from boosting?

Again, I hope it's okay for me to post this here.

you are viewing a single comment's thread
view the rest of the comments
[–] e-five@kbin.run 8 points 7 months ago* (last edited 7 months ago) (1 children)

If you can give me any more details, let me know. Looking at your instance, I only see two communities from lemmy.today, and one looks like it was deleted, so should only be their announcements one. Is the one you're having trouble interacting with the potentially deleted one?

Or do you mean users rather than communities? If you're trying to report threads or comments, are they potentially already removed from blahaj and then it won't let you interact with them?

To sum up some things about cross instance interaction as of this date:

  • reports do propagate to lemmy
  • moderator actions do not propagate back
  • direct messages don't work cross instance
[–] -Emma-@fedia.io 4 points 7 months ago (1 children)

I browsed the communities on their instance using mlmym so I could see the full list. Then I tried to access the lemmytoday community from my Mbin account, and I got a 404 error.

So that's what I meant when I said I can't report things to the admins on lemmy.today, since I can't post on their dedicated community.

I've noticed recently that my instance can't fetch new communities anymore. For instance, I fetched all of the good LGBTQ+ accounts months ago without an account, and they all eventually federated across. But I can't fetch asktransgender@lemmy.blahaj.zone or any other communities that aren't already federated. I was thankfully able to fetch trans@lemmy.blahaj.zone before this issue.

On another note, if moderator actions don't federate across instances, does that mean when I see this:

[Thread, post or comment was deleted by the moderator]

the comment was deleted by a moderator on my Mbin instance, rather than a moderator on Blahaj? In that case, I would think my reports are working.

[–] e-five@fedia.io 6 points 7 months ago* (last edited 7 months ago)

A 404 just means it hasn't been added to the instance yet, I just added it now by doing https://fedia.io/search?q=%21asktransgender%40lemmy.blahaj.zone (though it'll need a local subscriber to get updates)

On my list is to try to make it clearer on how to add remote magazines. In regards to whether that message means it was a local or remote delete for remote content... From my experience the only time I've seen deletes federate is when it's a remote instance A moderator acting on a remote instance A user post. Meaning if a remote Instance A moderator acts on a remote instance B user, it does not federate.

OsaErisXero mentioned the issue for fixing that in the thread, but for some reason my reply didn't federate, so that's why I'm posting from your local instance