16 Matching Annotations
  1. Aug 2022
    1. Write once. Publish everywhere.Write in our simple editor and publish natively to Twitter, LinkedIn, Medium, and your very own Typeshare Social Blog.

      Syndication as a selling point.

      https://typeshare.co/

  2. Jun 2022
  3. Apr 2022
    1. How do you get your annotations into the rest of your workflow for notes and learning? How do you prevent that your social annotation tool is yet another separate place where one keeps stuff, cutting off the connections to the rest of one’s work and learning that would make it valuable?

      Where

      My annotations broadly flow into two spaces:

      Obsidian

      My private Obsidian-based vault is where I collect the notes and actively work on, modify, edit, and expand them if and when necessary. This is also the space where I'm broadly attempting to densely interlink them together for future use and publication in other venues. If I could, I would publish these all on the web, but I've yet to find a set up with a low enough admin tax that I can publish them inexpensively in a way I'd like them to appear (primarily with properly linked [[WikiLinks]]) while still owning them in my own space.

      I've been experimenting around with using Blot.im as a solution to display them here https://notes.boffosocko.com/, but at present it's a very limited selection of my extant notes and doesn't include Webmention or other niceties I'd like to add. As it's a very alpha stage experiment I don't recommend anyone follow or use it and it may disappear altogether in the coming months.

      WordPress

      My main website uses WordPress. To a great extent, this is (now) primarily a back up location and the majority of the annotations are unpublished to the public, but are searchable to me on the back end.

      I do, however, use it occasionally for quickly publishing and syndicating select annotations which I think others may find interesting or upon which I'm looking for comments/feedback and don't expect that the audience I'd like these from will find them natively on Hypothes.is' platform. An example of this might be a paper I was reading this weekend on Roland Barthes which discusses his reasonably well documented zettelkasten-like note taking practice. The article can be found here: https://culturemachine.net/wp-content/uploads/2019/01/373-604-1-PB.pdf with the annotations seen here: https://docdrop.org/pdf/The-Card-Index-as-Creativity-Ma---Wilken-Rowan-upq8g.pdf/. To tip off others in the space, I made a post on my site with a bit of a puzzle and syndicated it to Twitter. A few hours later I posted a follow up with some additional details and links to my notes on hypothesis which got some useful feedback from Matthias Melcher on the Barthes paper as well as on a related paper I mentioned by Luhmann, particularly about German translation, with which I have little facility.

      Another recent illustrative example was this annotation on the Library of Congress website about Vladimir Nabokov which was picked up by my website (though unpublished/not public) but which I syndicated to Twitter primarily to be able to send a notification to Eleanor Konik who I know is interested in the idea of World Building using historical facts and uses Obsidian in her work. (The @mention in the tweet is hiding in the image of the index card so that I could save text space in the main tweet.) Several others interested in note taking and zettelkasten for writing also noticed it and "liked" it. Not being on Hypothes.is to my knowledge much less following me there, neither Eleanor nor the others would have seen it without the Tweet.

      Nabokov used index cards for his research & writing. In one index card for Lolita, he creates a "weight-heigh-age table for girls of school age" to be able to specify Lolita's measurements. He also researched the Colt catalog of 1940. #WorldBuildinghttps://t.co/i16Yc7CbJ8 pic.twitter.com/JSjXV50L3M

      — Chris Aldrich (@ChrisAldrich) April 10, 2022
      <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

      How

      Obsidian

      Getting annotations from Hypothes.is to Obsidian is a short two-step process which is reasonably well automated so that I don't spend a lot of time cutting/pasting/formatting.

      I start with an IFTTT recipe that takes the RSS output of Hypothes.is and creates text files directly into my Obsidian vault. The results are quite rudimentary and only include the title of the document, the permalink of the Hypothes.is post, the highlighted text, and my annotation. It doesn't include the tags as RSS doesn't have a specification for these.

      Second, I've set up Hypothesidian which has a much higher fidelity dovetail with the Hypothes.is API to get all the data and even the formatting set up I'm looking for. A reasonably well laid out set of instructions with a low/no code approach for it can be found at https://forum.obsidian.md/t/retrieve-annotations-for-hypothes-is-via-templater-plugin-hypothes-idian/17225. It allows importing annotations by a variety of methods including by date and by document URL. I've also made a small modification to it so that tags on Hypothes.is are turned into [[wikilinks]] in Obsidian instead of #tags which I only use sparingly.

      All the IFTTT annotations will be ported individually into a specific Obsidian folder where I'll process them. I can then quickly use Hypothesidian to import the properly laid out version (using templates) of the notes with just a few keystrokes and then focus my time on revising my notes if necessary and then linking them to the appropriate notes already in my system. Finally I'll move them into the appropriate folder based on their content—typically one of the following: zettelkasten, wiki, commonplace, dictionary, or sources (for bibliographic use). Careful watchers will notice that I often use Hypothes.is' "page notes" functionality to create a bookmark-like annotation into which I will frequently post the URL of the page and occasionally a summary of a piece, these are imported into my system and are used as source/bibliographic information. I also have some dovetailing with Zotero as a bibliographic set up which feeds into this data as well.

      This version which I've cobbled together works well for me so that I'm not missing anything, but there are definitely other similar processes available out there both for Obsidian (with plugins or scripts) as well as for other platforms. If I'm not mistaken, I think Readwise (a paid solution) has a set up for note transfer and formatting.

      WordPress

      As there isn't an extant Micropub client for Hypothes.is I initially used RSS as a transport layer to get my notes from Hypothes.is into WordPress. The fidelity isn't great in part because RSS doesn't include any tags. To get some slightly better presentation I set up a workflow using RSS output from Hypothes.is as input into an IFTTT workflow which outputs to a webhook that stands in as a Micropub client targeting my websites Micropub server. Some of the display on my site is assisted by using the Post Kinds plugin, which I know you've been working around yourself. The details may be above some, but I've outlined most of the broad strokes of how this is done in a tutorial at https://boffosocko.com/2020/01/21/using-ifttt-to-syndicate-pesos-content-from-social-services-to-wordpress-using-micropub/. In that example, I use the service Pocket as an example, but Hypothes.is specific information could easily be swapped out on a 1-1 basis.

      A custom stand-alone or even an integrated micropub client for Hypothes.is would be a fantastic project if someone wanted to dig into the details and dovetail it with the Hypothes.is API.

      Why

      Ideally, I'm hoping that small pieces loosely joined and IndieWeb building blocks will allow me to use the tools and have the patterns I'm looking for, without a lot of work, so that I can easily make annotations with Hypothes.is but have and share (POSSE) my content on my own site in a way that works much the way many IndieWeb sites dovetail with Twitter or Mastodon.

      I'm doing some portions of it manually at present, without a lot of overhead, but it would be fun to see someone add micropub and webmention capabilities to Hypothes.is or other IndieWeb building blocks. (I suspect it won't be Hypothes.is themselves as their team is very small and they're already spread thin on multiple other mission critical projects.)

      In the end, I'm using Hypothes.is as a well designed and convenient tool for quickly making notes on digital documents. All the data is flowing to one of two other locations where I'm actually making use of it. While there is some social layer there, I'm getting email notifications through the Hypothes.is settings and the data from my responses just gets rolled back into my spaces which I try to keep open and IndieWeb friendly by default. At the same time, for those who want or need it, Hypothes.is' interface is a great way of reading, searching, sorting, and interacting with my notes in public, particularly until I get something specific and user friendly up to do it on my own domain.

  4. Feb 2022
  5. Nov 2021
  6. May 2021
  7. Feb 2021
  8. Oct 2020
    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)

    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.

    1. The concept is to publish first on your own blog and then later republish the same content on Medium.

      Example of encouraging the idea of POSSE.

    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.

    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.

    1. Alex Rushmer is a Cambridge-based chef, food writer and owner of the restaurant Vanderlyle. The original version of this article was published on his blog

      POSSE to newspaper!

      h/t Kevin Marks

  9. Jul 2019
  10. 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.

  11. Jan 2016