I don't like the fact that the beta test cookie didn't work the next time I started galeon - I was back to the old boring LJ.
There's one definite thing I liked about the beta LJ - that the old blue options menu that occupies 25% of my 800x600 screen is gone, leaving the real content a larger space to work with.
Also, I think I like the fact that talkread and talkpost have been eliminated...... but the cryptic HTML page names should also perhaps be changed. Since they seem to have created a restriction on number of posts per LJ user per day, maybe they can start identifying the posts and entries by, say,
That's because post ids are not per journal. They are per cluster. So your username identifies what cluster your data is on, and then the post id is a sequentual number for all users on that cluster.
I'm just guessing this though. I haven't seen the database schema.
And IIRC, the limits on posts never came into effect.
Me too no like LJ's new non-talkread/talkpost system
ReplyDeleteI think I'll now go beta test :-).
The existing site definitely looks better than the beta.
ReplyDeleteNot bad from what I've seen so far. Don't see any woohoo-ness about it, but not exactly a step lower either.
ReplyDeleteSame here buddy
ReplyDeletesomehow I'm too used to the existing interface and I wish I could just stick to that
More improtantly, its not as functional as the present one.
ReplyDeleteMe like the cleaner URLs.
ReplyDeleteMe no like the colours in the beta.
I don't like the fact that the beta test cookie didn't work the next time I started galeon - I was back to the old boring LJ.
ReplyDeleteThere's one definite thing I liked about the beta LJ - that the old blue options menu that occupies 25% of my 800x600 screen is gone, leaving the real content a larger space to work with.
Also, I think I like the fact that talkread and talkpost have been eliminated...... but the cryptic HTML page names should also perhaps be changed. Since they seem to have created a restriction on number of posts per LJ user per day, maybe they can start identifying the posts and entries by, say,
20030322_2.html
or some such decodeable name.
That's because post ids are not per journal. They are per cluster. So your username identifies what cluster your data is on, and then the post id is a sequentual number for all users on that cluster.
ReplyDeleteI'm just guessing this though. I haven't seen the database schema.
And IIRC, the limits on posts never came into effect.