April 17th, 2002


Off Topic Posts?

I'm not really sure who is in charge of this community, but I notice frequent posts by newbies are completely off topic and get loads of "this belongs in support" comments.... In other lj communities like lj_art they handle this partly by having a detailed list of what the community is and is not for, along with useful links, support in particular. I'd really like to see this community follow their lead and make it more clear to everyone what this community is for. Who is in charge of keeping this community's info updated?

I also noticed when I went to the lj_dev page, I couldn't even find the link to the community description. Perhaps it's there and i'm overlooking it, but making this more prominent would be nice. Particularly if you want people to know what the community is about before posting.... =)

Any thoughts? (well, aside from all the related comments on this thread about why people come here before support...)


support.patch now combines the previous two patches, and attempts to fix a previous bug regarding the auth codes:

Auth codes are used so that the creator of a support request can identify themselves as the owner of that request, regardless of whether or not they are logged in, whether or not they are a user, etc. However, the existing code rejects non-users (people who file requests but don't have accounts on the system) from being authorized because they're not setting the $remote variable. The patch changes the logic a bit, which enables non-users to append information to their requests by way of comments. Also, it allows non-users, who have filed their requests in non-public support categories, to view their requests.

Since I'm not sure I fixed that the best way, any other suggested changes are welcome :-)

Example is here.


Here's an idea:

Can we add extra color variables to the list available for styles under Modify Journal?
There aren't enough available for users to customize when they select a pre-written style.
How about adding something like: UserColor1, UserColor2, UserColor3, etc.
That way we can use those for things like menus, credits, or whatever else we choose to add to our new styles, and users of our styles can change those colors without having to do overrides.

Just a thought.

Yes I know - this is not the right place for it. Bah!
  • Current Mood
    curious curious

kidproofing LiveJournal - proposed changes

I have a project that I would like a developer to tackle soon, if possible. I would normally bring such an idea up in feature requests, but under the circumstances, I think we need this done right away. It's long overdue.

Recently, I have been thinking about how to avoid a lot of the issues that LiveJournal has been having regarding things like naked userpics, nude pictures in journals, etc. Basically, we don't want to be branded as censors, nor do we want all the extra work that it takes to deal with these issues. Basically, we need some degree of kidproofing.

Currently, random searches will deliver you to any old journal. It could deliver you to a page full of porn. Take the community homosexuals, for example, which has gay porn. On a strict legal stance, is this any worse than delivering you to nakedparts? In most places, no. Still, it's not where most mothers would want their kids to go by random circumstance.

What would be better would be something like this.

Note that the new design for Random, though taking away a bit of the immediacy of the previous random feature, is actually more friendly than before for skimming through several random sites in order to find one that is of interest. Also, I added the idea of searching for random communities, as it would be a nice additional feature for users to find random communities. (Finding good communities is tough if you can't do a full directory search.)

Likewise, we can add a disclaimer box / disclaimer text on all interest searches and directory searches. Also, we may want to consider making directory searches default to not displaying user pics... Presumably, this will reduce the burden on the servers, as well as reduce the chance of anyone being offended by someone else's user pic.

That's the whole plan in a nutshell. It's not foolproof, and it certainly doesn't prevent minors from seeking out adult-themed content, but it does warn them, which seems to be the standard online requirement. This reduces LiveJournal's liability risk. It also decreases the workload for the Abuse team while protecting the freedom of expression allowed by the users of LiveJournal.

Anyone want to work on it?!