9 Matching Annotations
  1. Apr 2023
  2. Mar 2023
  3. Feb 2023
    1. Related here is the horcrux problem of note taking or even social media. The mental friction of where did I put that thing? As a result, it's best to put it all in one place.

      How can you build on a single foundation if you're in multiple locations? The primary (only?) benefit of multiple locations is redundancy in case of loss.

      Ryan Holiday and Robert Greene are counter examples, though Greene's books are distinct projects generally while Holiday's work has a lot of overlap.

  4. Dec 2022
  5. Jun 2022
  6. Oct 2020
    1. Perhaps we want to write but we feel comfortable with our phones and so we want to write on our phones. It’s like the best camera being the one you have on you. The best writing implement is the one you have on you. These days, it might be your phone.

      I often find the quickest and easiest writing implement I've got is the Hypothes.is browser extension.

      Click a button and start writing. In the background, I've got a tool that's pulling all the content I've written and posting it quickly to my own website as a micropub post.

    1. Create an IFTTT.com recipe to port your Hypothesis RSS feed into WordPress posts. Generally chose an “If RSS, then WordPress” setup and use the following data to build the recipe: Input feed: https://hypothes.is/stream.atom?user=username (change username to your user name) Optional title: {{EntryTitle}} Body: {{EntryContent}} from {{EntryUrl}} <br />{{EntryPublished}} Categories: Highlight (use whatever categories you prefer, but be aware they’ll apply to all your future posts from this feed) Tags: hypothes.is Post status (optional): I set mine to “Draft” so I have the option to keep it privately or to publish it publicly at a later date.

      Posting this solely to compare my Hypothes.is highlights and annotations on my website with Will's version.

      I'm still tinkering with mine and should have a Micropub based version using IFTTT and Webhooks done soon.

  7. 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.

  8. Mar 2019