Moderator here. While it’s reasonable to post your anime podcast here once, making a post for each episode is an excessive amount of self-promotion, at least for the activity level that we’ve currently got here. I’ll leave your existing posts up, but please refrain from making any more of them.

Huh, I wasn’t expecting more Gundam Seed after almost 20 years. MyAnimeList link for English speakers.

I imagine they’d also want to have something you can click that shows how many votes were local, how many were from other instances, how many were blocked, etc.

Actually, that would be really cool and worth doing regardless. Have a voting statistics view for each post where upvotes and downvotes are broken down per instance, and maybe by other criteria too. @ernest

Might be interesting to have per-instance weighted voting. So local votes would count as 1x, votes from other instances could count as 0.5x, and votes from that one instance that has a lot of vote brigading would count as 0x. Would be useful for smaller, specialized instances that tend to get harassed by outsiders.

Back in the day facebook only had a like button and people demanded a dislike button. I don’t know what facebook thought internally.

😆

You can use the boost feature. Your boosts are public, but that’s usually a good thing. Things you want to save are often things you want to promote, and vice versa.

Sure thing. :)

One day maybe we can have both options

Click on the gear icon in the upper right corner of the page, underneath your username.

From the PR comments:

Maintainers MAY merge incorrect patches from other Contributors with the goals of (a) ending fruitless discussions, (b) capturing toxic patches in the historical record, © engaging with the Contributor on improving their patch quality.

I asked around and asked in the C4 specification matrix room.
And the reason is actually simple. If you merge bad code, have a record of proof in git (pull requests aren’t forever it’s only a github/gitlab thing).

So the idea is if you merge bad code you have proof in the git record that there is a bad actor. You can always revert the commit again or fix it. And the record can act as a proof in case the community want to get rid of bad actors.

Hmm, that seems like not such a good look from Ernest. According to google translate:

I know, honestly it was on purpose. I noticed that forks sync changes immediately with /kbin. I wanted to check how they deal with this much-announced community-based qualitative code review. Answer: they can’t cope. Quite an obvious bug was accepted in PR and domerged into the main branch :P It now works properly on the rifle ;)

Hopefully everyone can play nice and work together productively.

It looks like they’re still working out what they want their process to be:

https://github.com/MbinOrg/mbin/pull/34

Seems like your concern is addressed there:

Pull Requests require at least one (1) other maintainer approval before the PR gets merged (built-in peer review process).

The mbin fork happened when kbin development was looking a lot less active. In any case, it’s not necessarily bad to have a diversity of approaches. Due to their differing organizational structures, mbin will likely tend to have more features and more rapid development, but also potentially more bugs, while kbin remains more stable.

Ah, fair point. Either way, it doesn’t make sense for it to be optional.

That’s because of a bug in the hot sorting. It was working fine for a while, and then broke. Upvoting your own post also fixes it. We should probably have our posts self-upvoted by default anyway, like on reddit and lemmy.

Sure thing. Blocking individual communities does still work.

If you’ve blocked any domains, try unblocking them. Domain blocking is buggy and will hide random stuff from you.

I’ve got the photo post bug too, but it only seems to affect me on @anime_irl, while @animemes seems to still work fine.

Also, you posted this multiple times, may want to delete the other ones. Whenever you make a post, check the “newest” sort order to make sure it went through, and then upvote your own post to make sure it’s visible for everyone on the default “hot” sort order.

I think especially Lemmy.ml should rather focus more on cleaning up their Tankie & moderator issues

As much as I would love to see it, I don’t think the lead devs of lemmy, who own both lemmy.ml and lemmygrad.ml, are going to ban themselves.

What are you on about? Dessalines said “No, that is full of CSAM.” I would like to know how they came to that conclusion.

or do the .ml admins have a more broad definition of csam?

Their definition seems to be “I don’t like anime”.

OP is lying through their teeth, nothing was found.

Literally any evidence at all beyond “dessalines said so” would be a good start. Hell, even dessalines specifically describing what he saw would be great.