Here's the column Meta doesn't want you to see: Read the Kansas Reflector's piece about Facebook's climate change ad policy
Here's the column Meta doesn't want you to see: Read the Kansas Reflector's piece about Facebook's climate change ad policy
Read the Kansas Reflector's piece about Facebook's climate change ad policy
Imagine my surprise when I attempted to “boost” a post on Meta’s Facebook to begin our online promotional efforts — and the company summarily rejected it.
Why? According to the automated response I received, the post “doesn’t comply with our Ads about Social Issues, Elections or Politics policy.”
Apparently, Meta deems climate change too controversial for discussion on their platforms.
I had suspected such might be the case, because all the posts I made prior to the attempted boost seemed to drop off the radar with little response. As I took a closer look, I found others complaining about Facebook squelching posts related to climate change.
I can imagine it started with climate change denialists, but its probably way too much benefit of the doubt for the company that knowingly swung opinion to trump based on russian assets in 2016.
What a nightmare of a person.
And people continue to say that defederating from Threads is premature/uncalled for...
I think there's room for philosphical differences here though. One can acknowledge Meta being evil but not advocate for defederation.
The standard federation analogy is to that of email. Google has shown themselves to be evil at times (prone to enshitification at the very least). But if my email provider drops support for any email from gmail.com, well... that's kinda not a good thing.
Obviously ActivityPub is not email, but still, I think it's a somewhat nuanced issue.
And with regards to the EEE issue, I'm personally not convinced of any threat. Slack embraced IRC then killed support, and no harm was done that I'm aware. XMPP always gets trotted out as an example, but I think it's a weak argument at best, disingenuous at worst.
I don’t want ads getting federated to my instance.
There’s not any room for philosophical debate on that point for me.
There’s a lot of other reasons to not federate with Threads, but that one is the only one I need to cite to realistically appeal to literally any and all fediverse users with at least a couple neurons in their skulls. And it’s definitely the only argument I need to cite to an instance admin who’s running a lemmy container on their home server.