Bo Jones. Or maybe Dennis. (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
nookiepowered) wrote in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
fandomhigh_ooc2012-04-13 01:02 pm
nookiepowered) wrote in fandomhigh_ooc2012-04-13 01:02 pm
Entry tags:
LJ Release Update
Good Morning, Fandom! It's time for another round of our favorite livejournal game, Good News, Bad News!
Livejournal Release 91 is live: News | LJ Releases.
Good News
* The "multiple keywords = default icon" bug in the default comment style has been fixed. Sort of.
* Thread expansion should be working better... in the default comment style.
Neutral News
Otherwise known as "This doesn't affect FH but we're noting it for you just in case you use it elsewhere."
* Community moderators can now edit the tags of posts while they're in the moderating queue, before they go live. (FH doesn't moderate posts, so n/a for us.)
* Posts that have been approved from said moderating queue (which FH doesn't use) will now have a little stamp showing which mod approved them, in the default comment style (which FH comms don't use).
Bad News
* No fixes for any existing custom/classic comment issues yet.
* That fix for "multiple keywords=default" was accomplished by LJ removing all alternate keywords from your options in the default style only except the one that comes first alphabetically. No big deal for the visual browser since you see the picture anyway, but if you're using the Stylish script that gives you back a dropdown text list, all of those additional keywords will be missing from your list. (i.e. I have a (worksafe) icon whose keywords are "kink" and "porn" -- in default style with the Stylish script, "porn" is missing from the list.) This does not affect custom comment pages, which still show all keywords.
* Release 91 seems to have broken the Greasemonkey script that fixes the comment entry box to give you back the opportunity to add a subject line. LJ's not likely to fix that, since other people's scripts aren't their problem; it's highly likely that the author will put out an update, though. Again, this does not affect custom comment pages, just those using the default pages with scripts. ETA: Yup, that script has been updated - thanks for the heads up, Jara!
* All custom comment pages (including classic comments) are now displaying comment timestamps in UTC (Greenwich Mean Time) instead of your personal settings. That one's a bug LJ probably will fix, but we bring it up so you don't have to WTF like we did, and because it does affect custom comments, which includes the FH comms.
WDEK News
That stands for "We Don't Even Know."
* LJ has changed how LJ cuts display. They now look like this
Your cut text here instead of like this: ( Your cut text here )
*Except it's not an image, it's a unicode symbol which means that it changes with your text size and some people whose browsers/computers don't display that symbol just see [] Your cut text here.
It looks okay in some styles and not quite so okay in others, but doesn't actually break anything. It's just some aesthetic WTFery, this who knows where it falls in the Good News, Bad News game.
In conclusion, there is no goat-punching thread because that's what the whole post is for. There's only an OOC thread because it's Friday the 13th and we're notquite dumb enough to invite that kind of trouble.
Livejournal Release 91 is live: News | LJ Releases.
Good News
* The "multiple keywords = default icon" bug in the default comment style has been fixed. Sort of.
* Thread expansion should be working better... in the default comment style.
Neutral News
Otherwise known as "This doesn't affect FH but we're noting it for you just in case you use it elsewhere."
* Community moderators can now edit the tags of posts while they're in the moderating queue, before they go live. (FH doesn't moderate posts, so n/a for us.)
* Posts that have been approved from said moderating queue (which FH doesn't use) will now have a little stamp showing which mod approved them, in the default comment style (which FH comms don't use).
Bad News
* No fixes for any existing custom/classic comment issues yet.
* That fix for "multiple keywords=default" was accomplished by LJ removing all alternate keywords from your options in the default style only except the one that comes first alphabetically. No big deal for the visual browser since you see the picture anyway, but if you're using the Stylish script that gives you back a dropdown text list, all of those additional keywords will be missing from your list. (i.e. I have a (worksafe) icon whose keywords are "kink" and "porn" -- in default style with the Stylish script, "porn" is missing from the list.) This does not affect custom comment pages, which still show all keywords.
* Release 91 seems to have broken the Greasemonkey script that fixes the comment entry box to give you back the opportunity to add a subject line. LJ's not likely to fix that, since other people's scripts aren't their problem; it's highly likely that the author will put out an update, though. Again, this does not affect custom comment pages, just those using the default pages with scripts. ETA: Yup, that script has been updated - thanks for the heads up, Jara!
* All custom comment pages (including classic comments) are now displaying comment timestamps in UTC (Greenwich Mean Time) instead of your personal settings. That one's a bug LJ probably will fix, but we bring it up so you don't have to WTF like we did, and because it does affect custom comments, which includes the FH comms.
WDEK News
That stands for "We Don't Even Know."
* LJ has changed how LJ cuts display. They now look like this
Your cut text here instead of like this: ( Your cut text here ) *Except it's not an image, it's a unicode symbol which means that it changes with your text size and some people whose browsers/computers don't display that symbol just see [] Your cut text here.
It looks okay in some styles and not quite so okay in others, but doesn't actually break anything. It's just some aesthetic WTFery, this who knows where it falls in the Good News, Bad News game.
In conclusion, there is no goat-punching thread because that's what the whole post is for. There's only an OOC thread because it's Friday the 13th and we're not
OOC
Re: OOC
Re: OOC
Re: OOC
no subject
no subject
test test
ETA: I just remembered that
Re: test test
I'm referring to the fact that your first comment I replied to has the existing 'OOC' subject line in the header stripped from it. I thought if the script was working it should have preserved the subject line. Is that not part of the functionality of the script? Because if it isn't that may also explain why subject lines keep getting stripped in things like sign-in threads in classroom posts, which has been a problem.
no subject
no subject
I know it's asking for extra work, but as a courtesy to other players, if you're going to keep 'display all in my own style' turned on so you're using the default form to post to communities, do you think you could try to remember to c/p existing comment subject lines into the script-y subject lines? Because it really messes up comment notifications and, to me, just generally looks odd to have one thread with no subject line in the middle of everything else.
no subject
no subject
Re: OOC
Re: OOC
Re: OOC