NEW! Subscribe to our email newsletter » NEW! Subscribe to our FREE email newsletter to receive updates »

MailChimp Banned Over Censorship Concerns

November 19, 2020

Starting immediately, SlickStack has begun warning WordPress sites that have MailChimp software installed that we will begin banning it by default at some point in the near future.

(Note: users are always free to install their own plugin blacklist.txt file, instead of using the default one.)

This is in accordance with our official goals of maximizing free speech and website portability, and helping users to avoid implementing services or extensions that will likely present conflicts later on in their website’s life cycle, esp. regarding stability, security, or portability.

Over the past few years, MailChimp’s “leftist” activism and Orwellian censorship has gotten more and more bold. Among many others who have been arbitrarily banned for political reasons include Stefan Molyneux, March for Trump, VICE founder Gavin McInnes, and Alex Jones, and even a random women’s issues blogger named Emma.

Ironically after Alex Jones was banned, his InfoWars emails are now being powered by the Amazon AWS cloud, meaning that the smaller independent MailChimp is literally just pushing users into Big Tech services instead, or creating totally new IaaS services from the ground up, like Parler, Gab, and many others.

In the past few months surrounding the 2020 US Presidential Election, MailChimp’s far-left founder Ben Chestnut, stepped up these efforts drastically by announcing they would be deplatforming any newsletter or organization that was distributing information that they personally believed was inaccurate, esp. politically. In essence, it is yet another effort of online tech platforms to silence and destroy conservative or right-leaning publications and ideas.

Almost immediately the affects were seen as the Northern Virginia Tea Party was permanently banned from MailChimp in November 2020.

Obviously, this unpredictability is horrible for online business.

For example, if your team spent months or years perfecting your website’s lead generation system and opt-in features to grow a newsletter or community, and then you got banned overnight for political reasons, it would throw not only your backend software into immediate disarray but also require redesigning your frontend and entire “funnel” from the top to bottom in certain cases. This could end up costing a small company not only thousands of hours of their time, but thousands of dollars in web development services as well.

Since helping users avoid lock-in to certain stack services or products is one of our main objectives, and allowing websites to switch to a new hosting cloud or WordPress theme/plugin on a moment’s notice with minimal technical debt is of top concern to SlickStack, we felt this decision couldn’t wait any longer.

Foolishly, MailChimp doesn’t seem to realize that newsletters especially are an easily-replicated IaaS commodity.

MailChimp Banned Over Censorship Concerns

Starting immediately, SlickStack has begun warning WordPress sites that have MailChimp software installed that we will begin banning it by default at some point in the near future. (Note: users are always free to install their own plugin blacklist.txt file, instead of using the default one.) This is in accordance with our official goals of […]

How we maintain both HTTP and HTTPS mirrors

GitHub Pages is an awesome feature that came out a few years ago on GitHub to allow for basic, static-file HTML websites to be hosted free of charge on GitHub. It can be a bit confusing to understand in the beginning, because you must connect one of your repos to be used for a given […]

Native Staging Sites (Optional) In Subdirectory

For the past several weeks, SlickStack has been testing our new Staging Site feature and it is now live on all SlickStack installations. If you use another staging service or simply don’t use staging at all and wish to disable staging sites, simply change your ss-config options to be STAGING_SITE=”false” and it will later remove […]