June 25th, 2006

animated bunneh icon
  • burr86


And again!

FAQ104: Moved validation into the summary, removed half the links in the "what can I do now??" to pare 'em down to the bare minimum sort of thing.

FAQ245: Removed the "you must be logged in" (the page errors and tells you to log in, our users aren't THAT stupid). Removed the "this has no relation to invite codes" bit. Removed the "you can customize the message or c/p the link; LJ doesn't store this info" bit, because it's on the page itself.

FAQ11: Removed the lecture in the summary, pared it down to "you get an email, click the link, or have another email sent". Toned down the "omg!functionality" paragraph. Removed the "you'll get an email when you change your email" para, since it's in the summary now. Reorganized the "troubleshooting" section.

FAQ19: Split it into summary/answer, of "change email" vs. "email mgmt".

FAQ71: removed the redundant "look at our requirements" sentence.

FAQ127: Removed the "caps and hyphens are lowercase/underscore" (we said a-z0-9_, so that statement is overkill). Removed the "here's all the reserved usernames" -- ex_, lj_, s_, ext_ -- to keep the FAQ simple. Removed "once a username has been registered, you can't register a new one with that username" explanation; overkill. Removed the "explanation" for inactive accounts -- they've never convinced me. *g* -- protected entries would show up on the updated time, prolonged access without internet doesn't fly for an account that's five years inactive, and using it only for comments/communities is generally ... you can tell. *g*

FAQ18: Reorganized information, nothing lost.

FAQ16: simplified the summary.

FAQ17: cleaned up the "validated or unvalidated" redundancy. (current email means current email, period). Nuked the "comment anonymously on your account" suggestion; there's no point in offering two ways to do exactly the same thing. Simplified the "omg!update!password" paragraph to one sentence. Removed the "omg!validate!" warnings everywhere, since they're in the FAQs they link to (and if they don't read those FAQs, they'll get error messages in the action they're trying to do).

FAQ167: ... has this FAQ been used at all in the past year? In any case, cleaned up the text a bit (eg, whereami.bml never listed problems with clusters)
animated bunneh icon
  • burr86


FAQ7: Updated to refer to the new /customize/
FAQ168: Ditto
FAQ145: Ditto ditto.
FAQ205: Ditto ditto ditto
FAQ96: Ditto ditto ditto ditto
FAQ13: Ditto x 5

FAQ14: Updated the FAQ title to be the most common use cases rather than "let's encapsulate anything and everything". Cleaned up summary. Removed "tell us if you know of a safe way to do this!" because I can't see us going 'oh wow, a safe way to add JS! let's get right on that'. And because video support is coming soon. :P Also removed the "usernames and passwords are stored in your cookies" line -- they aren't. :)

FAQ192: simplified the summary text. cleaned up the "support can't help you" para. Am going WTF over the "make sure you have permission to use this" text; tweaked it around a bit and moved it, though I'm considering nuking it entirely (as it's not our place to lecture people about that)

FAQ251: Cleaned up S1 text, did a style/layout swap in S2

FAQ12: /customize/ cleanup, minor text scrubbing, nothing major.