Code push imminent!

[karzilla]

We're about to pull the lever on tonight's code push! Many of the changes we are making to the site are under-the-hood improvements, but these are the ones you are more likely to notice:

• New account setting option for RP accounts, for future feature development.
• Many more sites upgraded to use HTTPS links instead of relying on our SSL proxy.
• Moved the Manage Icons page to /manage/icons and modernized the underlying code.
• Increased the size limit for icon descriptions from 120 to 300 characters.
• Various requested fixes for the image upload/management pages.
• Improved processing of emailed entries for changes to entry security.
• Improved processing of emailed comments for removal of quoted text.
• Reading page with date filter now has previous / next day links.
• Banned users hidden by default on the Manage Circle page.
• Most importer failure messages will now include the name of the journal being imported, for the benefit of users running multiple imports.
• People who read the RSS/Atom feed of your journal will see correct entry links and embedded content.
• Whitelist embeds from: coub.com, airtable.com, mixcloud.com
• New <user> tag sites: medium.com, imzy.com, facebook.com, instagram.com
• New "other site" fields on user profiles: Imzy, Instagram

Once the code push starts, you may notice that the site is slow to respond, but it should remain available to use unless something goes badly wrong.

I'll update this post when the code push is finished. Stay tuned!

Update: All done! Let us know if anything seems more wrong than usual!

Comments

[denise]

Honestly, after 15 years of doing this shit, I don't even have to think about it very hard. When other sites release a new feature (*cough* I'm looking at you, Twitter *cough*) I usually have at least half a dozen "okay, this is how it's going to be a shitshow" things leap to mind immediately.

And, I mean, I say "argument", but it's less "argument" and more like just fifteen billion iterations of nitpicking the hell out of something to harden it against the immediately obvious abuse vectors until everyone's satisfied that we've thought of everything. It's not an unpleasant process! Just a loooooooot of work, heh.

[motherboxes]

I don't use Twitter but I imagine that and Facebook at least....yeah.

But no, I get it! Really. Things often sound simple on paper and then you go into more detail/security stuff surrounding the idea and I imagine it ends up more than we might anticipate in actually doing it. I'm just glad to hear it is actually something you guys have been considering officially already. It means I'm not totally off the mark on this idea/suggestion even if we have a work around already, unofficially.

[denise]

It was actually one of the things I had on The List before we even launched DW! ...eight years ago, heh. 

[motherboxes]

Hey, if it has been on the list that long, it's obviously something you still intend to do? You'll get there! I know something like this isn't necessarily as huge a priority with other bugs etc to deal with over time that come up. Honestly, I just like hearing each time on the improvements you guys do and that you take our suggestions into consideration and listen to us and what we think.

[impossibilities]

Linking to alt accounts of friends could be averted just by requiring the two accounts to have the same email address, but that'd mess up some of our rp gmail+character@gmail.com setups unless there's a way around that :|a

[denise]

Yeah, our "do these two accounts have the same email" check already deals with +filtering, but the problem with just a plain same-email check is it encourages you (generic you!) to confirm your friend's email address on your account, thus making it horribly insecure (since any confirmed email can receive a password reset link) -- that's what I mean by "perverse incentives"...