pauraque_bk (
pauraque_bk) wrote2010-09-01 10:04 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Entry tags:
heads up
I'm about to take some LJs off my flist here because the people are crossposting everything to DW, and I never post anything locked on LJ so it doesn't matter whether I've got you friended here or not. (Every time I do this, I think I've eliminated all the duplicates, and I'm always wrong.) If I screw up and take you off when I shouldn't, tell me.
This is something I was going to do anyway, and nothing to do with the recent unpleasantness, though it is certainly becoming more and more evident how ill-suited LJ is for fandom at this point. I mean, it never was "for" fandom -- we were never a majority or probably even a very significant source of their income -- but there was a time when it worked quite well. Or at least we could put slashes in our tags without breaking things, you know...
I've seen it pointed out today that if you have anyone on your flist who would be dumb or insensitive enough to repost something locked and/or connect your fannish identity to your real name when you told them not to, that person shouldn't be on your flist in the first place. Of course that's true, but it's not entirely the point. It's just something that would never even be suggested, let alone implemented, on a service meant for fandom. For us, it's pointless and has obvious potential for abuse. For the people whose business LJ wants, maybe it seems like a good and useful idea, I don't know.
This is something I was going to do anyway, and nothing to do with the recent unpleasantness, though it is certainly becoming more and more evident how ill-suited LJ is for fandom at this point. I mean, it never was "for" fandom -- we were never a majority or probably even a very significant source of their income -- but there was a time when it worked quite well. Or at least we could put slashes in our tags without breaking things, you know...
I've seen it pointed out today that if you have anyone on your flist who would be dumb or insensitive enough to repost something locked and/or connect your fannish identity to your real name when you told them not to, that person shouldn't be on your flist in the first place. Of course that's true, but it's not entirely the point. It's just something that would never even be suggested, let alone implemented, on a service meant for fandom. For us, it's pointless and has obvious potential for abuse. For the people whose business LJ wants, maybe it seems like a good and useful idea, I don't know.
no subject
no subject
It doesn't surprise me that LJ has gone this way, since everywhere else is going to this content-sharing between all social media model.
no subject
When LJ got started, what was innovative about it was the community aspect -- automatic aggregation of friends' posts, and a comment system that was much better than any other online journal service at the time (and is still better than the non-threaded comments on many blogs). It was clearly designed not for one person to talk at lots of other people, but for people to talk to each other. "True" blogging services have not gone in that direction, as far as I can see, so the separation has remained, until now I guess.
no subject
no subject
The return of real names has been creeping up for a while. Remember MySpace and Friendster? It seems to be reaching a real critical mass now. But there are still people who want the ability to keep separate identities -- lots of people. The company that runs WoW recently threatened to require real names on forum posts, but had to go back on it because the negative response was so overwhelming. People still do want to be able to compartmentalize.
no subject
As you say, I think this is the crux of the issue - current LJ management is embarrassed by the large, fannish part of LJ. They want to be Facebook and Twitter and roll around on giant piles of money while being constantly mentioned in the news.
no subject
no subject
no subject
saw someone comment:
"apparently the / debacle is unintentional and programmers are working to fix it - so said
fwiw
no subject