Thank you for this; it makes sense, and fits what I see from the outside. I don't know code & development, but I do know what it looks like when a company's owners/managers say "just put some duct tape on that and get back to the real, by which I mean revenue-producing, work." Eventually, you have so much duct tape that you can't get to the pipes, *and* the original problem is exacerbated by tape glue all over the place.
(Don't get me started on my job's data archiving policies & procedures. Just aaagh.)
I do understand that it's not easy. There is no anti-pigeon-net that lets parrots through. There is no poisoned pidgeon chow that parrots won't eat by accident. Kids with bb guns is the most *accurate* way to address the problem; it's just not effective, once your pigeon population reaches a certain level.
Part of me thinks they could fix something by requiring email verification; I thought that wasn't part of the LJ signup process. (Didn't need it when invite codes were around.) Or maybe requiring captcha verification for posts, or for the first post in a journal, or more than 5 in a day, or something. (Can't use captcha for post-by-mail, so I don't know how that would work. OTOH, I don't know if any of the spambots are posting by mail.)
I'd like to believe anything I could come up with has already been thought of by people who actually understand the code, and been considered by Those Who Make Important Decisions, and the reason they're not being done is because they won't work for some reason. However, after watching LJ's Important Decisions for the last few years, I'm a lot less convinced of this.
no subject
(Don't get me started on my job's data archiving policies & procedures. Just aaagh.)
I do understand that it's not easy. There is no anti-pigeon-net that lets parrots through. There is no poisoned pidgeon chow that parrots won't eat by accident. Kids with bb guns is the most *accurate* way to address the problem; it's just not effective, once your pigeon population reaches a certain level.
Part of me thinks they could fix something by requiring email verification; I thought that wasn't part of the LJ signup process. (Didn't need it when invite codes were around.) Or maybe requiring captcha verification for posts, or for the first post in a journal, or more than 5 in a day, or something. (Can't use captcha for post-by-mail, so I don't know how that would work. OTOH, I don't know if any of the spambots are posting by mail.)
I'd like to believe anything I could come up with has already been thought of by people who actually understand the code, and been considered by Those Who Make Important Decisions, and the reason they're not being done is because they won't work for some reason. However, after watching LJ's Important Decisions for the last few years, I'm a lot less convinced of this.