![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Further on LJ's code shenanigans
Oct. 29th, 2011 08:42 amAccording to LJ, the problem with their code has now been fixed. Touchingly, they have also promised to institute radical new measures like testing changes before rolling them out.
Less amusingly, they do not seem to recognise that their mistake had any kind of negative implication for the security of users' information. Judging by the comments, this is a combination of tech lingo pedantry, and silliness.
Meanwhile, at the same time this was going down at LJ, Dreamwidth went offline for an hour. At the time I didn't think that really called for a long entry explaining the problem, why it wasn't fixed immediately and how processes have been changed to ensure faster response-time, but on the whole I'll take a service that over-communicates over one which didn't acknowledge the problem for 24 hours, and then failed to see why it was a potentially serious issue.
Completely related: I happen to have 23 unused DW codes, if anyone wants one. Leave me a comment or PM me with your email address.
Less amusingly, they do not seem to recognise that their mistake had any kind of negative implication for the security of users' information. Judging by the comments, this is a combination of tech lingo pedantry, and silliness.
Meanwhile, at the same time this was going down at LJ, Dreamwidth went offline for an hour. At the time I didn't think that really called for a long entry explaining the problem, why it wasn't fixed immediately and how processes have been changed to ensure faster response-time, but on the whole I'll take a service that over-communicates over one which didn't acknowledge the problem for 24 hours, and then failed to see why it was a potentially serious issue.
Completely related: I happen to have 23 unused DW codes, if anyone wants one. Leave me a comment or PM me with your email address.
