Code push happening tomorrow!

[karzilla]

We are planning to do a code push within the next 24 hours, around 7:30pm PDT / 10:30pm EDT. (timezones)

You can see what's new in the code tour that was posted earlier this week, but here are the highlights:

• Google Analytics v4 support
• adding the legacy RTE to the beta Create Entries page
• adding draft autosave to the beta Create Entries page
• more UI improvements for the beta Inbox
• some more aggressive measures for discouraging SEO spam accounts
• miscellaneous modernization updates for various journal styles
• many newly added sites for content embeds and username styling
• new color picker for the journal style customization page
• new CSS wrappers to allow styling of entry cut links

We'll update here once the new code is live!

Comments

[denise]

I will caution you that it's the same autosave that exists on the old page, which is very old and very buggy! We were holding off on integrating it into the new page in hopes that we'd have the time to modernize it and make it not a "very old and very buggy" disaster, but obviously it's taken this long for us to get to it so we just said fuck it, we'll put the old one in for now until we can make the actual modernized version.

[havocthecat]

It's a start? For which I am pleased? Hooray!

[chemicalcain]

Old and buggy autosave still autosaves my work more reliably than no autosave at all! I do manually save posts-in-progress by posting to a private drafts tag, but unexpected browser crashes can happen. My laptop likes to live on the edge (of its battery life) so I do sometimes end up completely losing a post. If autosave keeps 50% of those, that's much better than nothing, haha.

[jesse_the_k]

posting to a private drafts tag is brilliant! May I boost this?

[chemicalcain]

Yes absolutely! I use the tag ##drafts (symbol makes it easy to find in an alphabetical list) and post privately until the post is finished, then when I'm ready to publish I update the date/time and make it public under the correct tags.

[cesy]

Though note that means it won't trigger a notification for anyone who has that set up on your posts - for that, you'd need to repost as a new entry. And if someone's reading page is very fast-moving, it will appear further down as when you first posted it rather than at the top.

[chemicalcain]

Hmm, thanks for the warning. My understanding was that updating the date/time when editing a post would move it up the Reading Page unless I select for the post to not appear on the Reading Page at all.

[cesy]

I believe Reading page is by server time to avoid timezone issues, so it won't move.

[denise]

That's correct -- the reading page always goes by server timezone to avoid issues. (Your journal page will show it in the correct order. Communities go by server timezone because they can have multiple people posting.)

[denise]

cesy is correct -- people's reading pages always go by server timestamp at the time the entry was originally posted, and edits don't bump it on people's reading pages. Your individual journal will slot it into the correct time order display-wise, although communities also go by server time (since there can be different people posting from many different timezones).