Ahead of the midterms, Meta has paid at least 29 anti-LGBTQ+ accounts for their posts - Los Angeles Blade

TomHey, quick one before we move on - Ahead of the midterms, Meta has paid at least 29 anti-LGBTQ+ accounts for their posts. What's your first thought?

CarolPaying money to amplify hate right when people are deciding who gets elected isn’t just bad optics, it’s actively shaping the narrative against us. Think about a young queer voter scrolling through their feed and seeing those hostile messages boosted by the algorithm instead of community voices. That constant noise makes showing up to vote feel risky, not empowering.

TomThe number “29” is what really sticks in my craw here. It doesn’t sound like accidental ad placements; paying nearly three dozen separate accounts feels deliberate. Meta isn’t just letting these views float around—they’re buying space for them ahead of the midterms.

CarolDeliberate is the word that matters because it changes the legal picture entirely. You can argue about organic reach all day, but once Meta’s wallet pays twenty-nine separate pockets to run targeted ads, it stops being a content moderation issue and becomes a campaign finance problem. That’s why I’m skeptical of any company statement calling this "unintended" — they signed the checks right before election season.

TomPicture a queer family trying to find local health resources in their inbox during election week, only to see Meta-funded attack ads crowding out every helpful link. That’s how you turn basic civic engagement into a minefield where the platform itself is holding the detonator. Calling that “unintended” is like saying you didn’t mean to flood your own house while standing in the middle of the leak.

CarolWait, hold on—you’re comparing Meta’s payment to flooding your own home, but these aren’t their houses. Picture a single mother in Ohio relying on her phone to coordinate childcare and work shifts, suddenly getting bombarded by Meta-paid rhetoric telling her kids don’t belong in public spaces. Her stress isn’t abstract; it’s whether she can safely drop off her kid without facing hostility funded by a tech giant.

TomSo Meta funds the harassment directly affecting that woman’s daily life? That’s not a moderation bug anymore—it’s a liability waiting to explode.

CarolLiability is fair game since they handed over cash to known targets, not random users. But calling it a "bug" misses the bigger problem—Meta controls the targeting tools that let those ads follow specific households based on location and interests. They knew exactly who would see the hate, which means the damage wasn't accidental exposure, it was precision delivery.

TomPrecision delivery is exactly right, and it’s why the usual “we’ll tighten our filters” response rings false. Those targeting options were sold to advertisers specifically for micro-segmentation, so claiming ignorance about where the hate landed ignores the core product feature. The real question is whether Meta kept detailed records proving they audited each of those twenty-nine campaigns before launch, because without that paper trail, the defense collapses under its own weight.

CarolDemanding a paper trail is like asking a casino to prove it didn't cheat at blackjack because the chips landed in the dealer's pocket. The real test is simpler: did Meta flag a single anti-LGBTQ+ account for review after receiving the first payment, or did they just keep buying ads until the news cycle caught up?

TomYour casino analogy actually highlights a blind spot we haven't touched on yet: the people running those twenty-nine accounts are now sitting on a massive payout from a major corporation that could be clawed back if regulators get involved. That creates a weird incentive for those small creators to stay silent or delete posts rather than fight back, because losing Meta's money might hurt more than losing political influence.

CarolClawback is speculative; the silence is factual. If those creators vanish, Meta loses its deniable distance, leaving the platform fully exposed.

TomYou’ve got it backwards—their disappearance doesn’t expose Meta, it buries the evidence. When paid sources go quiet, the platform keeps its hands clean while the voters still remember the fear-mongering message stuck in their feed all week.

CarolBurying evidence helps no one when the actual target is still standing there. Think about a gay teen in Arizona whose feed filled with Meta-funded attacks last month; he didn’t care if the source deleted the post, he cared that his parents saw the hostility and stopped letting him leave the house. The harm lives in the viewer’s head, not in the advertiser’s database.

TomPutting the pain in the kid’s head isn’t an excuse for the company holding the checkbook. Meta spent hard cash to put that fear into a teenager’s routine, so the bill comes due regardless of how many databases get wiped. We can’t let them hide behind the fact that the trauma stays with the victim long after the ad expires.

CarolWaiting for the company to feel guilty is a waste of time, especially when they’re counting down to election day. The fix has to be immediate and public: force Meta to disclose every dollar sent to these twenty-nine accounts right now, before the votes are cast. Hiding the ledger doesn’t erase the fear, but exposing the source lets the community counter that narrative directly.

TomForcing disclosure is fine, but it won't stop the damage once the votes are counted. Until we know if Meta's internal logs show they reviewed those twenty-nine campaigns for compliance, we’re just guessing if this was negligence or intent.