Deprecated: Return type of Google\Model::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Model.php on line 256

Deprecated: Return type of Google\Model::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Model.php on line 261

Deprecated: Return type of Google\Model::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Model.php on line 268

Deprecated: Return type of Google\Model::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Model.php on line 278

Deprecated: Return type of Google\Collection::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Collection.php on line 22

Deprecated: Return type of Google\Collection::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Collection.php on line 38

Deprecated: Return type of Google\Collection::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Collection.php on line 30

Deprecated: Return type of Google\Collection::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Collection.php on line 43

Deprecated: Return type of Google\Collection::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Collection.php on line 14

Deprecated: Return type of Google\Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/vendor/google/apiclient/src/Collection.php on line 49

Deprecated: Optional parameter $column declared before required parameter $term_id is implicitly treated as a required parameter in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/php7/class-ahrefs-seo.php on line 559

Deprecated: Optional parameter $column declared before required parameter $term_id is implicitly treated as a required parameter in /home2/brianand/public_html/wp-content/plugins/ahrefs-seo/php7/class-ahrefs-seo.php on line 576

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/all-in-one-seo-pack/app/Common/Admin/Usage.php on line 154

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/all-in-one-seo-pack/app/Common/Migration/Meta.php on line 455

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/all-in-one-seo-pack/app/Common/Migration/Meta.php on line 455

Deprecated: Creation of dynamic property AIOSEO\Plugin\Lite\Admin\PostSettings::$integrations is deprecated in /home2/brianand/public_html/wp-content/plugins/all-in-one-seo-pack/app/AIOSEO.php on line 248

Deprecated: Return type of Pimple\Container::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 133

Deprecated: Return type of Pimple\Container::offsetGet($id) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 98

Deprecated: Return type of Pimple\Container::offsetSet($id, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 79

Deprecated: Return type of Pimple\Container::offsetUnset($id) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 143

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 60

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 66

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 72

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 76

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 56

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 578

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 585

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 606

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 613

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 620

Deprecated: Optional parameter $id declared before required parameter $old_user_data is implicitly treated as a required parameter in /home2/brianand/public_html/wp-content/plugins/sucuri-scanner/src/hook.lib.php on line 999

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 955

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 955

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 1528

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 2267

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 3112

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 3118

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home2/brianand/public_html/wp-content/plugins/updraftplus/class-updraftplus.php on line 3236

Deprecated: Optional parameter $operand declared before required parameter $then is implicitly treated as a required parameter in /home2/brianand/public_html/wp-content/plugins/wp-all-import/helpers/functions.php on line 78

Deprecated: Optional parameter $right_condition declared before required parameter $then is implicitly treated as a required parameter in /home2/brianand/public_html/wp-content/plugins/wp-all-import/helpers/functions.php on line 78

Deprecated: Return type of PMXI_Config::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/brianand/public_html/wp-content/plugins/wp-all-import/classes/config.php on line 85
The Fun of Being Censored on Facebook - Brian Anderson

The Fun of Being Censored on Facebook

Throwing money at education.

Last week, I was censored on Facebook after I blogged about the importance of the Constitution of the United States and the rule of law as a method of providing stability in society. Also, I mentioned that the word “conservative” has turned into a caricature and no longer reflects the idea that words can preserve a particular status quo, because they bind us to a certain ideal. I made other comments which you can view on the original post.

Then, I proceeded to post the short article to Facebook, as I normally do. What is the good of a blog if no one is reading it? Much like this blog, I should point out, the Anderson Law blog serves two functions: I get to write and explore ideas; and I can publicize myself or Anderson Law and the things we believe in generally. So, I published it on Facebook with the intro “One little known fact: you can be conservative and liberal at the same time.”

And then I decided to boost it.

Boosting Explained

Facebook is a very diluted platform. People don’t share as much as they used to, especially since the 2020 election cycle created more wedges and schisms between human beings with differing political viewpoints. And since people don’t share as much as they used to, the average feed has become dominated by advertisements. Some of these advertisements are based on previous searches (creepy cookies), some of these are based on pages or products that you like, and some of these are just general ads that are “boosted”, or highlighted through the payment of a small fee. It’s like stepping onto a really small pedestal and then selling your product, service, or message to passersby. It’s not like having a megaphone. It’s also not like traditional ads where people who you want to see your message see it. It’s pretty worthless, which is maybe why it doesn’t cost very much.

But, I do it anyway because the options in the brave new world of social media are seriously limited.

And then I get this message: ad rejected because it’s about social issues.

I’ve Got Issues

Yes, the post was about social issues like the law, the Constitution, and how we can “resolve to build our communities, to stand for the ideals of the Constitution, and [how we can] pay heed to our emotions without allowing them to destroy that which is good”. This seems like a natural point of dialogue for a lawyer and a law office. And promoting this sort of dialogue, without politicizing it, seems like a proper business objective and maybe even something that people who use Facebook would enjoy doing.

So, can someone explain to me why that is a post that Facebook should be censoring? Or how I should style the post so that it’s not in violation of Facebook’s community guidelines? Because I have a lot of legal issues that I would like to discuss, and I’d like them to be just a little more visible without trying to be salacious. Is that too much to ask? At least it wasn’t about religion, which may have been addressed in the Bill of Rights as another social issue. If you have any ideas, please comment below. Let’s make this as fun and creative as possible.

There is a silver lining, though. When I boosted a post today about the social issue of higher education, and even threw some cash into the air as part of my advertisement, I wasn’t blocked!

Throwing money at education.

Leave a Reply

Your email address will not be published.