219 Matching Annotations
  1. Oct 2017
  2. Aug 2017
  3. May 2017
  4. Jan 2017
    1. Intuitively, an explanation is a local linear approximation of the model's behaviour

      LIME and Explanation

      Questions: Is LIME really resemble human's approach to understand black box of machine learning?

  5. Jun 2016
  6. Mar 2016
    1. Client<->Server API - defines how Matrix compatible clients communicate with Matrix homeservers. Server<->Server API - defines how Matrix homeservers exchange messages and synchronise history with each other.

      Given the data model (which allows merges) forkdb could be a close candidate to substitute a Client <-> Client API (also called peer to peer).

      Play with it.

  7. Sep 2015
  8. Aug 2015
    1. Check out the code on GitHub.

      Notenotenote. Notenote. Cool.

  9. Jul 2015
  10. Jun 2015
  11. Apr 2015
    1. Do I own my content on The Grid? Yes, you own your content. The engine AutoDesigns your site, publishes it, and stores it on Github. Your source content will live in a Github repository that you can access and download anytime.

      Is access private/public?

    1. The blog post in which Ben Balter proposes that term was unpublished when I read it. But since the blog is hosted on a public GitHub repository I could not only read the post in draft form but also follow the discussion with invited reviewers and observe how that discussion influenced the draft.

      With Hypothesis this kind of thing becomes available for /any web page/.

  12. Mar 2015
  13. Nov 2014
  14. Feb 2014
    1. Github As The Central Presence, Definition, Configuration, And Source Code For Your API Posted on 02-05-2014 It is easy to think of Github as a central repository for your open source code—most developers understand that. I have written before about the many ways to use Github as part of your API management strategy, but in the last few months I'm really seeing Github playing more of a central role in the overall lifecycle of an API.