- May 2019
Distributed content is any content that a publisher creates to live “natively” on an outside platform without directing any traffic back to your domain. This could mean allowing Facebook or Google to host your articles through Facebook Instant Articles or Google AMP. But it more generally means content you create specifically to live off-site on certain platforms.
This definition of distributed content seems tragically flawed to me. If it doesn't live natively on a publisher's platform, then how is it exactly "distributed"? This definition is really more like silo-specific native content.
It also seems predicate on publications entirely giving up all the agency and ownership of their own content. If they're creating content completely for silos, where's the value for them other than the diminishing returns of their brand recognition?
Concepts like POSSE or PESOS are much better and more valuable in my mind by comparison.
While the marketing idea of creating content that seems native to the platform on which it appears is valuable, publications still need to get eyeballs back to either their own platform or to places where their advertising, subscription, or other financial enterprise centers can directly benefit. Simply giving away the candy store without direct benefit to the publisher are only going to hasten their demise.
- Aug 2018
That said: I will try to work out using webmentions to reply to folks replies that get backfed to my site, using my site’s comments. We’ll see.
I spent some time trying to figure this out. It's not as hard as I would have presumed to thread comments between WordPress and Twitter. https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/
I do wish I had an automated way to write the comment on my site and syndicate it to Twitter automatically and have the threading work properly. For now I'm doing it manually--the few times I do do it.
- Jan 2016