Damn, that’s sad. Thank you for the info.

Worst hypothesis they just need to mess around a bit. For example I don’t think that queerasfu.ck would be registered.

They could get a .ck domain instead and move to queer.as.fu.ck, no?

To be fair with the above, even considering that he’s being disingenuous*, his [AFAIK incorrect] claim is not “anime is child porn”, it’s “that anime instance has child porn”.

*note how he’s trying to transform “is this CSAM?” into a subjective matter. That’s rather close to the moving goalposts fallacy.

Even in this thread there’s discussion of a show that blatantly tittilates the audience with underage characters that would absolutely qualify as csam in any other community except in the anime community, for some reason.

Emphasis mine. If what you are saying is indeed correct (is it? dunno), this is a sign that the acronym “CSAM” was completely derailed.

Originally the expression “child sexual abuse material” was coined to avoid implications of consent brought by the word “pornography”, and it boils down to “evidence of child sexual abuse”. Consent and sexual abuse are legal notions that only apply to real people, not to fictional characters.

In the meantime, at worst the instance in question depicts images of clearly fictional characters in suggestive poses and/or clothing. It does not classify even as pornography, let alone sexual abuse. (Note that not even hentai depicting clearly adult characters is allowed in that instance.)

I don’t care about what the maintainers’ view of the matter is, I make (and sometimes delete) my comments based on my own view of it.

Given that this is a touchy subject, I think that this matter is better handled neither by the maintainers’ views nor by our own views, but by 1) legal definitions of governments that might be relevant in the matter, and 2) explicit moral premises.

Yeah, but the admins, as the thread has shown, are mainly reining in violations of sitewide policy. Instance rules are mainly the job of mods.

So the admins are reining in violations of lemmy.ml-wide policy… while lemmy.ml rules are mainly the job of the mods??? Congratulations, that’s the dumbest thing that I’ve read today.

Couple the above with the backpedalling (from “This is what mods are for.” to “Instance rules are mainly the job of mods.”; emphasis on “mainly”) - a sleight of hand, while lying that I was the one using a sleight of hand - and I’m led to the conclusion that you have nothing meaningful to add to this discussion, and can be safely ignored as dead weight and noise.

Unlike the above, does anyone here have any decent counter-argument against “migrating this comm to that other instance would be sensible”?

I’ve seen even people in their 40s using them. I don’t think that it’s a big deal, or that it’s too late for that.

Removed by mod

Not just the mods. Admins can (and should) also moderate content in their instances, specially when it comes to the global rules. And it’s clear that lemmy.ml admins want to do so, otherwise this thread wouldn’t exist on first place.

Sorry for the double reply. Here’s a practical idea: what if the mods of this comm contacted lemmy.ml’s admins? Ideally doing two things:

1. Clarifying that the instance in question does not have child sexual abuse material, and requesting users to be allowed to link it.
2. Expressing desire to migrate !anime@lemmy.ml to the instance in question, and highlighting that this is convenient for both sides of the matter.

Among the admins I think that Nutomic would be the best to contact, given the github thread.

You’re talking about your thread about Mahou Shoujo ni Akogarete, right? It’s still in the modlog for me, even in private mode. I don’t think that they removed the entry.

Another important detail is that Digg v4 pissed off most of the userbase, so the impact was pretty much immediate. Reddit APIcalypse pissed off only power users instead; the impact will only come off later (sadly likely past IPO).

Lunix sucks so much that it got stuck into the version 2 for years.

Neither, but if I must choose it’s probably slightly more like muscle than like cartilage. If prepared properly it’s really soft and a bit chewy, distantly reminding me meat from stews.

(That reminds me a local pub that prepares some fucking amazing breaded and deep-fried tripe. Definitively not doing it at home - it spills and bubbles the oil like crazy.)

Removed by mod

In my opinion, the migration is sensible because:

1. You need to know a topic decently enough to be able to moderate a community about it. And yet it’s unreasonable to expect the admins of lemmy.ml - a community about free/open source and privacy - to know about anime.
2. There’s no inherent reason why this comm is the largest anime comm in Lemmy. It’s simply that this comm is three years old, from a time when “Lemmy” was mostly just lemmy.ml and lemmygrad.ml, there was no other place in Lemmy to discuss anime.
3. Lemmy as a whole benefits from redirecting traffic from larger instances to smaller ones. Specially instances unrelated to politics and tech. In fact, lemmy.ml’s admins asked users to use other instances not too long ago.

For me it says “admins”. I don’t know if it’s because I’m a mod of a few other lemmy.ml comms, or if it’s because of the different backend versions (SJW uses 0.18.5, lemmy.ml uses 0.19.1).

For context, I encourage people to check this discussion in the “join Lemmy” site github. Have in mind that both of the Lemmy developers in that discussion are also admins of the lemmy.ml instance, and they clearly disagree if the instance in question should be considered as “hosting CSAM” or not.

I think that this community should migrate, but for a different reason: topic.

The topic of lemmy.ml is privacy and free-as-freedom software. Most other content here is off-topic, including anime. It was fine when it was just lemmy.ml and lemmygrad.ml, as you’d have no other place to discuss anime in Lemmy, but now the situation is different.

And ideally, communities should be managed/moderated/administered by people who know well the topic of the community.

It isn’t “Hangul” that is saving the language, but the fact that it’s getting an orthography. That orthography could be theoretically in any writing system - not just Latin or Arabic (both already exist for Cia-Cia, contrariwise to what the video claims), but even a native one or Cyrillic or even, dunno, the Cherokee syllabary.

Abidin looks informed on the matter; the same cannot be said about whoever produced this video. I’ll highlight a few issues.

[0:33] - pretty much all languages are “syllable-based”. They organise sounds into syllables. The video is likely trying to convey that it’s a CV (consonant, vowel, repeat) language, unlike, say, Russian or English (that cram quite a lot of consonants in a single syllable).

[0:36] The video is trying to use “transliterated” as a posh synonym for “spelled”; both are not the same thing. Transliteration is to convert text from a script from another; for example, “Quis credis esse, Bellum?” (Latin, using the Latin script) → “Кўис кредис ессе, Беллум?” (Latin, using the Cyrillic script instead) is transliteration.

And you can spell pretty much any language in any writing system. The association between grapheme and sounds (or phonemes) is arbitrary.

You might say “but the Latin alphabet doesn’t have a letter for /ɓ/!” - well, it doesn’t have a letter for /ʃ/ either. Italian handled it by spelling it ⟨sci⟩, English as ⟨sh⟩, Polish as ⟨sz⟩, Portuguese kind of repurposed ⟨x⟩. And the current Latin spelling for Cia-Cia - that you can check here - handled /ɓ/ just fine, using a similar approach as the Hangul one.