I'm growing tired of LJ

[rekall]

From what I've been reading on metafandom, their latest move is going around and marking slash/femslash comms as explicit.

Sorry LJ, but just because a story (or image) involves people of the same sex, it doesn't automatically mean it's explicit.

I'm not leaving LJ since there's too many people/comms, but I'm going to be cross-posting from DW since they have a really simple feature of being able to cross-post to your LJ with just a click. On DW, I'm rekall, so if anyone has a DW account and want to follow me there, go ahead.

Comments

[rekallthegreat.livejournal.com]

LJ has been bothering me since the FFR incident. I really didn't like the way they handled themselves (changing it to 'explicit' without warning the mods/refusing to work with the mods so that a solution could be resolved).

I went through one of the comms that was recently changed. The NC-17 fics that I saw there were just linked, not directly posted. So a comm like hitman_reborn could get eventually get caught too if someone reports it.

[ceasefire.livejournal.com]

I think LJ has the right to protect their asses. I mean, they're going about it in a completely ass-backwards way, but I think they have the right.

Oh, brother. I know that you can change the setting from the default rating setting with ease, but what's the bet most people won't bother?

In other news, I conducted an experiment with regards to their "the mods are in charge of keeping an eye on content" thing. (http://galuxkitty.livejournal.com/1053431.html) I am not pleased by the results.

[rekallthegreat.livejournal.com]

I don't mind it when sites have to remove content because their sponsors are getting mad or for whatever reason. It happened with both Onemanga and Mangafox, but in those cases it wasn't just yaoi that was being targeted, it was all manga that dealt with a mature subject.

Right now with LJ though they seem to be specifically flagging comms with the word 'slash' in the title. Besides FFR (which was reported due to a wanky grudge), I haven't seen a non-slash comm get flagged without warning even though there are plenty of comms that it could happen too.