flags and tags
Nov. 30th, 2007 03:24 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
substituteThe LJ "flag content" and age restriction policy isn't shocking or unusual. It's surprising that they've gone so long without it. If it's done properly, content flagging is the best way to deal with the problem of adult content and people who don't want to see it.
Note that online video sites, Craigslist, Flickr, and just about every other social network have mechanisms like this. It can be poorly implemented or need incremental improvement but I think outrage is misplaced.
Flagging can be misused, especially if it's done wrong, and Digg-like behavior ensues. If LJ fails to code this right there will be problems, and possibly very bad problems. Ideally it should work the way Craigslist does, or AIM's "zapping," where one person can't cause a lot of damage.
The tag problem is worse. They should have set an arbitrary limit when tags were launched, but they didn't think about scaling and now they have to do it retroactively and annoy people. I would guess (and hope) that their engineers will find a better way of handling tags and the limit will be raised or removed at some time.
I'm not talking out my ear here. I've been on both ends of this argument since 1991, on a variety of services that serve radically different audiences. The "flag content" system is imperfect and sometimes maddeningly broken, but top-down approaches are a far worse failure. Letting the community flag things based on their own biases and then sorting out the disagreements is the only think I've seen work, at all.
With the current U.S. legal environment I doubt LJ has many alternatives. If someone wanted to check out the LJ code and build one in Belarus or something, it might take off as a refuge from this kind of thing.
Note that online video sites, Craigslist, Flickr, and just about every other social network have mechanisms like this. It can be poorly implemented or need incremental improvement but I think outrage is misplaced.
Flagging can be misused, especially if it's done wrong, and Digg-like behavior ensues. If LJ fails to code this right there will be problems, and possibly very bad problems. Ideally it should work the way Craigslist does, or AIM's "zapping," where one person can't cause a lot of damage.
The tag problem is worse. They should have set an arbitrary limit when tags were launched, but they didn't think about scaling and now they have to do it retroactively and annoy people. I would guess (and hope) that their engineers will find a better way of handling tags and the limit will be raised or removed at some time.
I'm not talking out my ear here. I've been on both ends of this argument since 1991, on a variety of services that serve radically different audiences. The "flag content" system is imperfect and sometimes maddeningly broken, but top-down approaches are a far worse failure. Letting the community flag things based on their own biases and then sorting out the disagreements is the only think I've seen work, at all.
With the current U.S. legal environment I doubt LJ has many alternatives. If someone wanted to check out the LJ code and build one in Belarus or something, it might take off as a refuge from this kind of thing.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
(no subject)
Date: 2007-11-30 11:57 pm (UTC)(no subject)
Date: 2007-12-01 12:21 am (UTC)(no subject)
Date: 2007-12-01 01:35 am (UTC)(no subject)
Date: 2007-12-01 01:16 am (UTC)Is that what you're saying.
(no subject)
Date: 2007-12-01 01:36 am (UTC)(no subject)
Date: 2007-12-01 03:08 am (UTC)(no subject)
Date: 2007-12-01 03:16 am (UTC)(no subject)
Date: 2007-12-01 04:02 pm (UTC)(no subject)
Date: 2007-12-01 06:49 pm (UTC)(no subject)
Date: 2007-12-01 04:06 pm (UTC)