The Facebook Algorithm Mom Problem

POSSE

For quite a while now, I’ve been publishing most of my content to my personal website first and syndicating copies of it to social media silos like Twitter, Instagram, Google+, and Facebook. Within the Indieweb community this process is known as POSSE an acronym for Post on your Own Site, Syndicate Elsewhere.

The Facebook Algorithm

Anecdotally most in social media have long known that doing this type of workflow causes your content to be treated like a second class citizen, particularly on Facebook which greatly prefers that users post to it manually or using one of its own apps rather than via API. [1][2][3][4] This means that the Facebook algorithm that decides how big an audience a piece of content receives, dings posts which aren’t posted manually within their system. Simply put, if you don’t post it manually within Facebook, not as many people are going to see it.

Generally I don’t care too much about this posting “tax” and happily use a plugin called Social Media Network Auto Poster (aka SNAP) to syndicate my content from my WordPress site to up to half a dozen social silos.

What I have been noticing over the past six or more months is an even more insidious tax being paid for posting to Facebook. I call it “The Facebook Algorithm Mom Problem”.

Here’s what’s happening

I write my content on my own personal site. I automatically syndicate it to Facebook. My mom, who seems to be on Facebook 24/7, immediately clicks “like” on the post. The Facebook algorithm immediately thinks that because my mom liked it, it must be a family related piece of content–even if it’s obviously about theoretical math, a subject in which my mom has no interest or knowledge. (My mom has about 180 friends on Facebook; 45 of them overlap with mine and the vast majority of those are close family members).

The algorithm narrows the presentation of the content down to very close family. Then my mom’s sister sees it and clicks “like” moments later. Now Facebook’s algorithm has created a self-fulfilling prophesy and further narrows the audience of my post. As a result, my post gets no further exposure on Facebook other than perhaps five people–the circle of family that overlaps in all three of our social graphs. Naturally, none of these people love me enough to click “like” on random technical things I think are cool. I certainly couldn’t blame them for not liking these arcane topics, but shame on Facebook for torturing them for the exposure when I was originally targeting maybe 10 other colleagues to begin with.

This would all be okay if the actual content was what Facebook was predicting it was, but 99% of the time, it’s not the case. In general I tend to post about math, science, and other random technical subjects. I rarely post about closely personal things which are of great interest to my close family members. These kinds of things are ones which I would relay to them via phone or in person and not post about publicly.

Posts only a mother could love

I can post about arcane areas like Lie algebras or statistical thermodynamics, and my mom, because she’s my mom, will like all of it–whether or not she understands what I’m talking about or not. And isn’t this what moms do?! What they’re supposed to do? Of course it is!

mom-autolike (n.)–When a mother automatically clicks “like” on a piece of content posted to social media by one of their children, not because it has any inherent value, but simply because the content came from their child.

She’s my mom, she’s supposed to love me unconditionally this way!

The problem is: Facebook, despite the fact that they know she’s my mom, doesn’t take this fact into account in their algorithm.

What does this mean? It means either I quit posting to Facebook, or I game the system to prevent these mom-autolikes.

Preventing mom-autolikes

I’ve been experimenting. But how?

Facebook allows users to specifically target their audience in a highly granular fashion from the entire public to one’s circle of “friends” all the way down to even one or two specific people. Even better, they’ll let you target pre-defined circles of friends and even exclude specific people. So this is typically what I’ve been doing to end-around my Facebook Algorithm Mom problem. I have my site up set to post to either “Friends except mom” or “Public except mom”. (Sometimes I exclude my aunt just for good measure.) This means that my mom now can’t see my posts when I publish them!

Facebook will let you carefully and almost surgically define who can see your posts.

What a horrible son

Don’t jump the gun too quickly there Bubbe! I come back at the end of the day after the algorithm has run its course and my post has foreseeably reached all of the audience it’s likely to get. At that point, I change the audience of the post to completely “Public”.

You’ll never guess what happens next…

Yup. My mom “likes” it!

I love you mom. Thanks for all your unconditional love and support!!

Even better, I’m happy to report that generally the intended audience which I wanted to see the post actually sees it. Mom just gets to see it a bit later.

Dear Facebook Engineering

Could you fix this algorithm problem please? I’m sure I’m not the only son or daughter to suffer from it.

Have you noticed this problem yourself? I’d love to hear from others who’ve seen a similar effect and love their mothers (or other close loved ones) enough to not cut them out of their Facebook lives.

References

[1]
R. Tippens, “Drop the Autobot: Manual Posting to Facebook Outperforms Automated,” ReadWrite, 01-Aug-2011. [Online]. Available: https://readwrite.com/2011/08/01/manually_posting_to_facebook_significantly_outperf/. [Accessed: 11-Jul-2017]
[2]
“How to Increase Your Traffic from Facebook by 650% in 5 Seconds,” WPMUDEV, 02-Aug-2011. [Online]. Available: https://premium.wpmudev.org/blog/how-to-increase-your-traffic-from-facebook-by-650-in-5-seconds/. [Accessed: 11-Jul-2017]
[3]
J. D. Lasica, “Demystifying how Facebook’s news feeds work,” SocialMedia.biz, 11-Feb-2011. [Online]. Available: http://socialmedia.biz/2011/02/07/how-facebook-news-feeds-work/. [Accessed: 11-Jul-2017]
[4]
D. Hay, “Will auto-posting stunt the reach of your Facebook posts?,” SocialMedia.biz, 26-Jul-2011. [Online]. Available: http://socialmedia.biz/2011/07/26/will-auto-posting-stunt-the-reach-of-your-facebook-posts/. [Accessed: 11-Jul-2017]
You know it was an awesome Indieweb Summit for WordPress, when you log in and see all these awesome updates!

Just some of the WordPress related updates that were built and released at the Indieweb Summit this weekend in Portland.

Congratulations and Thank You to Matthias Pfefferle, David Shanske, Ryan Barrett, Michael Bishop, Asher Silberman, Brandon Kraft, Lillian Karabaic and all of the others in the Indieweb community who provided the setting, conversation, thinking, and underpinning that made all this possible!

Reply to Gutenberg: First Impressions | MattCromwell.com

Replied to Gutenberg: First Impressions by Matt Cromwell (MattCromwell.com)
Gutenberg is the future of content in WordPress. It will deliver the elegance of Medium but with far more power and flexibility of layouts and content types
I love how this looks and works and it’s certainly about time that WordPress had alternate means of publishing to its platform. (I miss the days when Twitter had thousands of different configurable apps to post to it, though these were far simpler.)

Not only does it remind me a bit of Medium.com’s interface, it is highly reminiscent of Aaron Parecki’s Quill editor which uses the open Micropub spec to publish to the Micropub endpoint on my blog. Though his isn’t as fully featured as the Gutenberg example, he could certainly add to it, but then it could be used to publish to any site that supports the spec.

A sample of the Quill interface for posting to WordPress via Micropub.

The nice part about Micropub (and the fact that there’s already a Micropub plugin for WordPress) is that developers can build multiple competing publishing interfaces to publish to any website out there. (Or developers could even build custom publishing interfaces for their clients.)

In fact, if they wanted to do a highly valuable pivot, Medium.com could add publishing via Micropub to their platform and really become the billionaire’s typewriter that some have suggested it to be.

👓 WordPress.com Announces New Importer for Medium Posts | WP Tavern

Read WordPress.com Announces New Importer for Medium Posts by Sarah Gooding (WP Tavern)
Medium started 2017 on uncertain footing, laying off a third of its staff in January after admitting that its ad-based business model was not working.

👓 WordPress’s owner is closing its San Francisco office because its employees never show up | QZ

Read Wordpress's owner is closing its San Francisco office because its employees never show up by Oliver Staley (Quartz)
Automattic, the technology company that owns WordPress.com, has a beautiful office in a converted San Francisco warehouse, with soaring ceilings, a library, and a custom-made barn door. If you like the space, you're free to move in. The office at 140 Hawthorne went on the market after CEO Matt Mullenweg came to the realization not...

📺 Domains2017 Conference: Tuesday June 6, 3:00pm with the OU Crew | YouTube

Watched Tuesday June 6, 3:00pm with the OU Crew from YouTube
For more information see the blog post for the event at http://virtuallyconnecting.org/blog/2017/05/31/domains17/

Indieweb for Education: Some thoughts after the Domains 17 Conference

There’s some interesting discussion of Indieweb-related principles in this live-streamed (and recorded) conversation (below) from the Domains 2017 conference for educators and technologists which covers a lot of what I’d consider to be Indieweb for Education applications.

In particular, some asked about alternate projects for basing education projects around which aren’t WordPress. Some suggested using WithKnown which is spectacular for its interaction model and flexibility. I suspect that many in the conversation haven’t heard of or added webmentions (for cross-site/cross-platform conversations or notifications) or micropub to their WordPress (or other) sites to add those pieces of functionality that Known comes with out of the box.

Another section of the conversation mentioned looking for ways to take disparate comments from students on their web presences and aggregating them in a more unified manner for easier consumption by the teacher and other students (as opposed to subscribing to each and every student’s RSS feed, a task which can be onerous in classrooms larger than 20 people). To me this sounded like the general concept of a planet, and there are a few simple ways of accomplishing this already, specifically using RSS.

I was also thrilled to hear the ideas of POSSE and PESOS mentioned in such a setting!

An Invitation to Attendees

I’d invite those in attendance at the Domains 17 conference to visit not only the Indieweb wiki, but to feel free to actively participate in the on-going daily discussions (via IRC/Slack/Matrix/Web). I suspect that if there’s enough need/desire that the community would create a dedicated channel to help spur the effort to continue to push the idea of owning one’s own domain and using it for educational purposes out into the mainstream. The wiki pages and the always-on chat could be useful tools to help keep many of the educators and technologists who attended Domains17 not only connected after the event, but allow them to continue to push the envelope and document their progress for the benefit of others.

I’ll admit that one of my favorite parts of the Indieweb wiki is that it aggregates the work of hundreds of others in an intuitive way so that if I’m interested in a particular subject I can usually see the attempts that others have made (or at least links to them), determine what worked and didn’t for them, and potentially find the best solution for my particular use case. (I suspect that this is some of what’s missing in the “Domains” community at the moment based on several conversations I heard over the past several days.)

If you’d like, please add yourself to the growing list of Indieweb related educators and technologists. If you need help connecting to any of the community resources and/or chat/IRC/Slack, etc. I’m more than happy to help. Just call, email, or contact me via your favorite channel.

http://youtube.com/watch?v=INB-h9eEcpY

📖 Read pages 106-114 of Professional WordPress: Design and Development 3rd Edition by Brad Williams, David Damstra, and Hal Stern

📖 Read pages 106-114 of Professional WordPress: Design and Development 3rd Edition by Brad Williams, David Damstra, and Hal Stern

Finishing up chapter 6

Professional WordPress: Design and Development 3rd Edition by Brad Williams, David Damstra, and Hal Stern

📖 Read pages 100-106 of Professional WordPress: Design and Development 3rd Edition by Brad Williams, David Damstra, and Hal Stern

📖 Read pages 100-106 of Professional WordPress: Design and Development 3rd Edition by Brad Williams, David Damstra, and Hal Stern

Chapter 6 is pretty important. After going over the rest of the text, I’ll be sure to come back and re-read this particular section.

Professional WordPress: Design and Development 3rd Edition by Brad Williams, David Damstra, and Hal Stern

Title-less Status Updates for Micro.blog

Micro.blog just launched in beta recently and one of the biggest things burning up the airwaves there is how to easily post content from one’s own site as notes without including titles. Why? If a post has a title, then micro.blog thinks it’s an article and just posts the title along with a permalink to it rather than the desired content of the status update.

In the long run and for easier mass adoption, I’m hoping Manton can figure out how to parse RSS feeds in a simpler way so that users don’t need to do serious gymnastics to import their microblog posts from other sources. I’d imagine it’s far easier for him to adapt to the masses than for the masses to adapt to micro.blog. At the very worst, he could create a checkbox on the RSS import feeds to indicate which feeds are status updates and which aren’t and this would quickly solve the problem for the average user as most CMSes allow users to define custom feeds based on content type.

While there are a number of people doing things from simply adding date/time stamps (which micro.blog ignores) to functions.php tweaks to to custom plugins, some of which I’ve tried, I thought I’d come up with my own solution which has helped to kill two proverbial birds with one stone. (Note: I’ve listed some of these others on the Indieweb wiki page for micro.blog.)

The other day, I’d had a short conversation about the issue in the Indieweb chat with several people and decided I’d just give up on having titles in notes altogether. Most people contemplating the problem have an issue doing this because it makes it more difficult to sort and find their content within their admin UI dashboard which is primarily keyed off of the_title() within WordPress. I share their pain in this regard, but I’ve also been experiencing another admin UI issue because I’ve got a handful of plugins which have added a dozen or so additional columns to my posts list. As a result the titles in my list are literally about four characters wide and stretch down the page while knucklehead metadata like categories needlessly eat up massively wide columns just for fun. Apparently plugins aren’t very mindful of how much space they decide to take up in the UI, and WordPress core doesn’t enforce reasonable limits on these things.

So my solution to both problems? If found a handly little plugin called Admin Columns with over 80,000 users and which seems to be frequently updated that allows one to have greater simple control over all of the columnar UI interfaces within their sites.

In just a few minutes, I was able to quickly get rid of several columns of data I’ve never cared about, expand the title column to a reasonable percentage of the space so it’s readable, and tweak all the other columns to better values. Even better, I was able to add the slug name of posts into the UI just after the title columns, so I can leave status update titles empty, but still have a field by which I can see at least some idea of what a particular post was about.

My first title-less status update with a descriptive slug