they can harass you by continually sending you replies for WEEKS and WEEKS at a time (this actually happened to me twice, once with hexbear.net and another time with lemmygrad.ml).

Honestly you really shouldn’t be on an instance that federate with those places to start with.

You may be interested to read some of the ways that PieFed is advancing democratization of moderation.

Personally I’m not a fan of the way PieFed uses upvotes and downvotes to basically do statistics on users in order to profile “bad actors”. That feels like karma from Reddit all over again.

There can be many legitimate reasons why a user might downvote a lot, and a user being downvoted a lot is not necessarily problematic. They may just not be following the “hive mind”, and honestly we could use more of those users.

You too? I’ve had more users sign up this month than for many past months!

When a fediverse app wins, the whole fediverse wins. A rising tide lifts all ships or however it goes.

The cool thing is that it’s not like versus, it’s like co-op!

Well, in theory sure. But you always lose people during migrations, it’s inevitable. And it’s cumbersome for users. It’s not a nice experience. The fediverse has enough bad UX as it is, I’d prefer if we didn’t pile on more.

If the fediverse actually held true to the promise of easy migrations, then maybe it wouldn’t be a big deal. But unfortunately it’s still not really that easy.

but they haven’t released anything yet

And with their current pace, it seems likely they never will. There’s been no major development on it for months as far as I can see.

Unfortunately migrating from one fediverse application to another on the same domain is actually basically impossible, due to the way ActivityPub works. It’s very unfortunate.

automated solution

On the other hand, any automated solution will be possible to work around. Such a system would be open source like the rest of Lemmy and you’d know exactly the criteria you need to live up to to avoid getting hit by the filter.

Email verification is super easy to get around. It’s practically not a barrier at all.

I’m not a native speaker so I don’t hear the fart association so much. But isn’t tooting also just what a trumpet or elephant does? In that way it makes sense. But I do think the terminology is a bit silly. Why not just “post” instead of toot? Why not just “repost” or “share” instead of “boost”? It feels a bit too much like corporate social media where every feature needs a “wacky and fun” name.

Yep exactly, it also leads to Mastodon instances only seeing local likes for remote posts. You’ll never see remote likes on remote posts as they wouldn’t be sent to your instance. I honestly don’t understand how this hasn’t been a bigger problem for Mastodon, but I guess Mastodon is more about boosts and chronological timelines and less about sorting stuff based on likes.

Mastodon doesn’t support groups so it’s maybe not a “bug” per se, but it is at least a missing feature.

Consider also that if Lemmy shared upvotes the same way, you would only see the upvotes on posts from your own instance, i.e. upvotes would only appear on the local feed. The all feed would be pointless and in general it would be pointless to try to sort posts across the whole fediverse, as you only receive upvotes for your local posts.

Lemmy simply would not function if it shared votes like that. So in that sense, it’s a bug kind of. And as mentioned above, I think it’s a bad way of doing it, as it encourages centralization.

Interesting. Seems like Photon attempts to do some kind of clever (and entirely non-standard) hack and tries to load the comment from your own instance? But obviously you need to see it from Feddit.dk to see the votes. This is a bug with Photon I would say.

Weird, what client are you using?

All interactions are recived by the instance hosting the community

Exactly - but Mastodon doesn’t do it like that. Mastodon sends the upvote directly to the instance with the user receiving the Like. So the community never sees the Like at all. So this is Mastodon not supporting groups, it is not a bug in Lemmy.

Group support would fix it for Lemmy, but it doesn’t fully fix the problem as I see it with this way of sharing the Like objects. For toots outside of any group (in Lemmy terms: comments/posts outside a community), presumably it would continue to function like this, i.e. only the receiving instance is aware of the Like. This still encourages centralization if you ask me.