Code push scheduled for Sunday night-ish

[karzilla]

We are planning to do a code push late this weekend, at approximately 9pm PST / 12am EST / 5am UTC on either Sunday, Feb 12 or Monday, Feb 13, depending on whether you live east or west of midnight. (Time is an illusion anyway, right?)

Here's a partial list of changes that will go live with this push, apart from the usual minor tweaks and bugfixes:

• HTTPS Everywhere beta! Users can opt-in to have all Dreamwidth content automatically served over HTTPS. We'll post the instructions for this after the feature goes live.


• New and improved design for the file management pages, which we were hiding from you because we were so embarrassed about them before. Thanks to momijizukamori for making them prettier and more functional!


• Backend fixes to resolve problems using the aforementioned file management pages. (Did I already mention the embarrassment?)


• At long last, international character support for journal search! Our systems guru alierak finally cracked this long-standing bug.


• Support index page converted to Foundation styling, for your mobile viewing pleasure.


• For users of the Practicality style: color properties now sort properly in the customization wizard.


• For users of the Drifting style: the QuickReply box will now appear in the appropriate location, instead of wandering off somewhere unexpected.


• Improved handling of word break (<wbr>) elements in user entries.


• Allow embeds from: Facebook, CNN, 4shared.com, playmoss.com, onedrive.com, jsfiddle.net, scratch.mit.edu

We'll update again to let you know when the code push is in progress!

Comments

[denise]

1) To add a new embed source, we need a sample of the embed code. You can open a support request requesting that it be added -- just give us the code for a sample embed. For security purposes, we have to be careful about what embeds we allow, so we might not be able to add it, but we do add everything we get a request for that we can.

2) Not 'complicated' so much as 'for long and boring reasons that would take me forever to explain, comments have to be held to a stricter security standard than entries', alas.

[bytebuster]

1. Thanks, I will do so.
2. I totally understand. May I ask you to write a line at FAQ for LJ users?