Karzilla, Destroyer of Bugs (
karzilla) wrote in
dw_maintenance2017-04-30 08:48 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Code push imminent!
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!
no subject
Tying accounts together/quick-switch between main/alt accounts like that has been On The List for a while, but every time we dig into it to start thinking about how to implement, we run into a bunch of "how should it work" scenarios that people disagree really hard on. It's not impossible, we just gotta have the extensive, exhaustive, knock-down-drag-out argument once and for all first. ;)
(Also, we have to be REALLY CAREFUL that we don't incentivize security risks -- like, if we allow an alt account to have access to certain paid features if the main account is paid, that motivates people to add their account as an alt to a friend's account to share certain features, etc.)
no subject
...Yeah I can see how this might take some back and forth now. :la
no subject
(I like to joke to Mark that he's in charge of spotting technical problems before they happen and I'm in charge of spotting social problems/bad incentives/how people will abuse a thing before it happens)
no subject
But even if this takes a while it is good that you are considering potential security measures around it! Even if that might also be frustrating and I'm sure you don't...want to have to sit there and think 'okay but here is how people can abuse this feature, guys!'
no subject
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.
no subject
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.
no subject
It was actually one of the things I had on The List before we even launched DW! ...eight years ago, heh.
no subject
no subject
no subject
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"...