7 Matching Annotations
  1. Last 7 days
    1. What I dwell on the most regarding syndication is the Twitter stuff. I look back at the analytics on this site at the end of every year and look at where the traffic came from — every year, Twitter is a teeny-weeny itty-bitty slice of the pie. Measuring traffic alone, that’s nowhere near the amount of effort we put into making the stuff we’re tweeting there. I always rationalize it to myself in other ways. I feel like Twitter is one of the major ways I stay updated with the industry and it’s a major source of ideas for articles.

      So it sounds like Twitter isn't driving traffic to his website, but it is providing ideas and news. Given this I would syndicate content to Twitter as easily and quickly as possible, use webmentions to deal with the interactions and then just use the Twitter timeline for reading and consuming and nothing else.

  2. Jan 2020
    1. A version of this piece originally appeared on his website, davidbyrne.com.

      This piece seems so philosophical, it seems oddly trivial that I see this note here and can't help but think about POSSE and syndication.

  3. Jul 2019
    1. The architecture of the platform where I published allowed authorial control of content but could not control context collapse or social interactions.

      These are pieces which the IndieWeb should endeavor to experiment in and attempt to fix. Though I will admit that pieces of the IndieWeb layers on top of platforms like WordPress can help to mitigate some context collapse and aggregate social interactions better. (eg: reply context and POSSE)

    2. The comments are most contentious, violent and personal on posts that have platform jumped (as one might expect, see: Davis and Jurgenson 2014).
  4. May 2019
    1. 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.

  5. Aug 2018
    1. 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.

  6. Jan 2016