...is live. There's no
news post for it yet, but the
lj_releases post is now up. We don't know all the changes it brings, bad or good, but what we do know is this:
If you have a Paid or Plus account (at this point it doesn't work for Basic, but we don't know if that will change because see above per staff,
that's a bug and will be fixed), then
1. Go
here and
(
Read more... )
Comments 53
Also, I don't know if it's some sort of thing y'all have done or just weirdness, but in the trips comm, the timestamp is displaying under and to the right of the userpic, eating vertical space1. I was about to go into the lj-releases post and start shouting file a complaint, but it wouldn't load for me, and then I noticed that on another post I was looking at that wasn't happening at all. So I thought it might be a loading thing and refreshed like five times and it's still happening, but just in trips.
1Speaking of eating vertical space, go check out what this release has done to your profile. I really don't like that, but that's another story.
Reply
(I'm not seeing the profile issue? Bo's seems ok. But I also don't really mind vertical space on profiles in general, so I may just not be noticing it because it's not something my eyes are conditioned to register.)
ETA: Ah, the layout of the stats at the top? I agree it's aesthetically dumb, but in the scheme of things, it doesn't bother me, unlike comment and entry display issues.
Reply
Yeah, that's what I meant. It's not the last straw or anything, but it was unobtrusive and not obnoxious before and now it's just THERE and wasting space that you have to scroll past before you get to the parts of the profile anyone cares about. Sigh.
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Additionally the very first thing I did when I discovered I couldn't comment the day 88 was released was turn off all my scripts and addons--which, I don't use DisConnect in the first place--and I still couldn't comment. I don't doubt that some people's problem was caused by DisConnect, but considering my personal experience, I cannot believe it's the only cause of the problem.
Reply
I don't agree on the script, though. They've messed up third party's before (like ljarchive and ljlogin), but I don't think it's fair to expect them to support all user scripts out there. That script was to remove a feature people didn't like (posting to twitter/fb), LJ decided to remove the feature (one of the few things I was not sorry to see going) which is their right. That it broke the entire page is painful, though, I agree there but it's also a risk you take when using user scripts that inject JS.
Reply
Leave a comment