For me that's a huge red flashing neon sign that your efforts will be directed to what top management considers the problem to be and not necessarily what you consider the problem to be.
The reality of that situation they're looking to change the perceptions of potential buyers. That may or may not involve much that you care about. Of course they'll say the two overlap, but when push comes to shove...
Unless you are the management.
You could still prevail. But these kinds of spats can get incredibly personal. You'll want bosses that understand this is coming and can ride it out. People outside of work that have your back, too.
They haven't addressed abuse in the past because the market has stupidly hitched their stock price to MAUs, which I think has caused them to take their eye off the ball and prioritize that metric over all else. Address abuse, and risk lower MAUs.
So if they've finally decided that sacrificing MAUs in the short term is worth it (focusing instead on revenue, cost control, and cleaning up the toxic abuse), they may be able to finally realize some of that discounted value.
It sounds like it could be a great opportunity at helping Twitter unleash some of that discounted value. Not the sole reason that the value will be reflected in the future market price, but a very important factor that at least gives them an option to sell out later at a good valuation if the growth in earnings is slower than expected and they feel the need to test the waters again.
Worst case, it's 100% focus on stemming abuse, they clean it up in a year, and you're working for Disney, Microsoft, Google, Amazon or some other acquirer.
Turning around a ship is really hard. I've made the mistake of working at a company with a hugely insurmountable problem (Bing) having viewed it as a big opportunity but I almost certainly pursued a job at the winner (Google) considering I had no experience as a professional engineer yet and would have learned much more. On the other hand if you already are the subject matter expert, it can be a huge opportunity to bring your skill set somewhere it is desperately needed.
Not that I really know first hand social networks that are great at solving the abuse problem but this is one way to look at a career choice.
Advice to the OP: don't be a martyr. If it looks like you can make a difference, go for it! Just don't pin your identity or sense of self on whether you succeed. The markets are a harsh mistress.
I took a job a little over a year ago at a company that I knew was struggling financially, but saw opportunity for a lot of personal growth. To give you some idea of how dysfunctional this place is, it rates a 0 / 12 on the Joel Test. There's no scale for negative, otherwise it might be negative.
After more than a year of working here, I think I've managed to get us to .5 / 12. And that's been a battle.
The biggest factor? I completely underestimated the social aspect of it. I failed to realize that, in any dysfunctional organization, the people there are either extremely tolerant of that dysfunction, or worse, worked to create it.
As I sit here writing this, my co-worker is at his desk rewriting swathes of code that I had working. We're 6 weeks past our delivery date, he says it's fixed, but he's still over there swearing, so that can't be true. He hasn't committed anything to the repo in over a month, so I have no idea what he's done (or how valid his complaints are). When he was doing this a few weeks ago, he rewrote a lot of my stuff only for it to turn out to be a small mistake in his code that was causing things to fail. I don't mind having my stuff criticized or rewritten, but logic would dictate if you write a bunch of new code and merge it in with stuff that was working, there's probably an error in the new code, or possibly the mating with the existing base. Sort of a look to the log in your own eye before you cast out the mote in your brother's.
And that's just how things go here. Projects that should take a few months have dragged on for years (before I got here). Untested changes get pushed into products. Nothing is documented. Comments in code are usually snarky quips directed at the compiler provider or Microsoft and littered with curses. And there are a million other things.
It's like that because he wants it like that, it likely won't change, and I should probably just leave.
I want to be careful to respect my NDA here, but I think I can fairly say that a) I was totally skeptical when I first started talking to them, and b) I now think there is a lot of reason for hope.
Private stuff aside, I think there are a couple of public reasons to think this may be the turning point. One is the enormous beating they've been taking in the press about this for the last year or so. The other is that their abuse problem was a big factor in them not getting offers from a couple of suitors during their attempt to sell themselves. I think it's safe to say their abuse problem cost investors literally billions of dollars. That is a pretty big learning opportunity.