{
  "title": "Digest 2014-08-20",
  "story": [
    {
      "type": "paragraph",
      "id": "b5d49ba6f7820360",
      "text": "Welcome to weekly Federated Wiki hangout on August 20, 2014<br><br>On today&#x27;s call<br><ul class=\"bullet\"><li>Ward</li><li>Allen</li><li>David</li><li>Paul</li><li>Nick</li></ul><br>Hashtags<br><br>In wiki, page names serve the role of hashtags<br><ul class=\"bullet\"><li>Then need disambiguation?</li></ul><br>Group configuration, people using different words<br><br>Meetups, with groups that don&#x27;t crosstalk<br><br>David is working on Service Systems Thinking<br><br>Paul has been catching up on Express<br><br>Txtzyme plugin<br><ul class=\"bullet\"><li>A board with a character display</li><li>Has USB hardware on the chip, so can do flow control with C</li><li>Run an interpret -- text with enzyme -- twiddle bits, LED glows</li><li>Write Perl or Java or Ruby scripts to stream data to interpreter</li><li>Has a repeat loop, e.g. do something 10 times</li><li>Series of pulses</li><li>Streaming of programs goes into separate hardware, invoke it, throw it away</li><li>Macro that runs in plugin, formulates programs, send to the microcontroller</li><li>Broke it in refactoring</li><li>Added ability for &quot;string backs&quot;;&nbsp; send a string, plugin then checks if it has a macro with that name</li></ul><br>Demo:&nbsp; federated wiki for OSCON hardware showcase<br><ul class=\"bullet\"><li>From fed wiki in browse, can make hardware blink and beep</li></ul><br>[Fire drill for Ward!]<br><br>Compatibility of Paul&#x27;s code with Ward&#x27;s code?<br><ul class=\"bullet\"><li>Nick wrote a Javascript version of the server, sitting in a folder inside the Ruby project</li><li>Had SFW on Github that had the Ruby server, the node server, and the client and the plugins, in separate directories</li><li>Nick split the Node server onto a separate project, about a year ago -- at that point, the versions were the same</li><li>The Ruby version signs in with OpenID, the Node version now signs in with Persona, which seems to be an better solution at the time</li><li>Ward was having problems with OpenID providers disappearing</li><li>At some point, ended up two versions of the client: after the node server was moved to separate project, moved the client server at the same time?</li><li>Some divergence</li><li>Then did massive refactoring with plugins into separate repo</li><li>Ward then started working with NPM to do a separate Ruby-Gems</li><li>Client version has moved on with time, the server versions haven&#x27;t changed much, it&#x27;s convoluted</li></ul><br>Difference in client versions?<br><ul class=\"bullet\"><li>Just different versions</li><li>When a feature is added, e.g. drag and drop between pages, it won&#x27;t be on any server that was installed a while ago</li><li>When logging in, the version gets downloaded to the client</li><li>Should have a page that tells what version of the server and client is connected to -- it&#x27;s not obvious</li><li>There&#x27;s a server command that does this, but it doesn&#x27;t do a check</li><li>Could check with Git&nbsp; if there&#x27;s a new version</li></ul><br>OpenID vs. Persona?<br><ul class=\"bullet\"><li>OpenID, when save the identity, saves the URL</li><li>Persona saves the e-mail address</li><li>Ward had been have problems with the OpenID provider</li><li>A risk that Persona could disappear?&nbsp; It hasn&#x27;t been taken up more widely</li><li>Current problem with people who use Google identities, the OpenIDs won&#x27;t work</li></ul><br>[Fire drill over for Ward!]<br><br>Timebomb will be people who signed up with Google IDs on fed.wiki.org<br><ul class=\"bullet\"><li>No SLA, not in trouble if they can&#x27;t log in</li><li>Ward erased all of the identity information and reclaimed</li></ul><br>[Nick joined]<br><br>Speed bump of being technologically savvy to use federated wiki?<br><br>Claim a cookie, instead of claiming a site?<br><br>HTML5 browser local storage retains the content across reboots<br><ul class=\"bullet\"><li>WebRTC data channels</li><li>A way to open up binaries</li><li>Still need some server to handle the connection details</li><li>There are people working on not having a server connection</li></ul><br>What behaviour should we expect if there&#x27;s content in the local browser storage?<br><ul class=\"bullet\"><li>Try a variety of ways, and then enable the affordance that works</li><li>Original sponsors insisted on the ability to edit in private, and then publish when a group of aticles is approved</li><li>Can do this by having a local version -- a pain in the butt</li></ul><br>When publishing, is there a way to subscribe?<br><ul class=\"bullet\"><li>To subscribe, add a site that you care about, it will cause all of the sites to be collected</li><li>You have to ask for it</li><li>Not RSS, call it sitemaps</li></ul><br>How to a control-Z?<br><ul class=\"bullet\"><li>Go to the ghost page, fork the page, and then it clears the journals</li><li>Varies between implementations, not all servers do that</li><li>Journal is the undo buffer, visualized</li><li>In the Node version, doesn&#x27;t do the annotation</li></ul><br>Recent refactoring in the Page Handler<br><ul class=\"bullet\"><li>Depending on the fork, different types of behaviours</li><li>Should be unified sometime</li></ul><br>Working with Txtzyme, need to find on pages, have to drag in more frequently<br><ul class=\"bullet\"><li>Not meticulous about IDs, could end up with two things with the same ID</li><li>Need to make samples about events</li><li>Shift-and-drag, drop</li><li>Complicated ways to remember original IDs, with aliases -- but too complicated</li><li>Theory:&nbsp; when you finally learn what to do when the software becomes simple, then the design becomes simple</li><li>Luxury to have a few powerful features, and learn what they can do over time?</li></ul><br>Simple versus easy:&nbsp; simple isn&#x27;t easy to do<br><ul class=\"bullet\"><li>Can make something simple to use, but not easy to use</li><li>Wiki was successful because it was simple and awkward to get around the cheesiness that Ward had written</li></ul><br>Archtectural programming?<br><ul class=\"bullet\"><li>David has been working backwards from pattern language to understand the context of architectural programming, as used by built environment architects</li><li>Ward doesn&#x27;t follow a methodology</li><li>Good fortune and trusting colleagues to make something work, surprisingly, and then make it worth of study</li><li>Might be successful only after someone takes the code away from Ward, and makes it valuable</li><li>Research prototype? Wouldn&#x27;t complain, would be a little hurt</li><li>Nick would do this?</li></ul><br>Agile has worked well when you have a well-defined customers<br><ul class=\"bullet\"><li>Works well when you have a good project manager that adds as a surrogate for a customer</li><li>However, there are a lot of good things that can from not agile?</li></ul><br>Domain-driven development?<br><br>Nick is getting close to feature-freeze<br><ul class=\"bullet\"><li>No official freeze, but have an announce date, can&#x27;t add much</li><li>Do work with visual designers (user experience), have a lot of influence</li><li>Didn&#x27;t have much room for that in agile</li><li>Have elevated computer programming from dysfunctional to average</li><li>Now when people report fantastic gains, it was because they weren&#x27;t getting anything done, now getting things done</li><li>First, physicists, they were used to making things done</li></ul><br>Domain-driven design as agile that is closer to object-oriented design<br><ul class=\"bullet\"><li>Ubiquitous language</li><li>Important that developers use the language they&#x27;re coding, especially if they have a customer using a language</li><li>Eric Evans found this in Smalltalk when doing container shipping -- whole team had to learn a lot of business practices</li><li>Nothing in the book that Ward disagrees with</li><li>More social interaction practices</li><li>The place to begin is on ddd.fed.wiki.org -- the patterns are there</li><li>The best is to buy the book, could ping Eric</li></ul><br><br><"
    }
  ],
  "journal": [
    {
      "type": "create",
      "item": {
        "title": "Digest 2014-08-20",
        "story": []
      },
      "date": 1408558087347
    },
    {
      "item": {
        "type": "factory",
        "id": "b5d49ba6f7820360"
      },
      "id": "b5d49ba6f7820360",
      "type": "add",
      "date": 1408558093673
    },
    {
      "type": "edit",
      "id": "b5d49ba6f7820360",
      "item": {
        "type": "paragraph",
        "id": "b5d49ba6f7820360",
        "text": "Welcome to weekly Federated Wiki hangout on August 20, 2014<br><br>On today&#x27;s call<br><ul class=\"bullet\"><li>Ward</li><li>Allen</li><li>David</li><li>Paul</li><li>Nick</li></ul><br>Hashtags<br><br>In wiki, page names serve the role of hashtags<br><ul class=\"bullet\"><li>Then need disambiguation?</li></ul><br>Group configuration, people using different words<br><br>Meetups, with groups that don&#x27;t crosstalk<br><br>David is working on Service Systems Thinking<br><br>Paul has been catching up on Express<br><br>Txtzyme plugin<br><ul class=\"bullet\"><li>A board with a character display</li><li>Has USB hardware on the chip, so can do flow control with C</li><li>Run an interpret -- text with enzyme -- twiddle bits, LED glows</li><li>Write Perl or Java or Ruby scripts to stream data to interpreter</li><li>Has a repeat loop, e.g. do something 10 times</li><li>Series of pulses</li><li>Streaming of programs goes into separate hardware, invoke it, throw it away</li><li>Macro that runs in plugin, formulates programs, send to the microcontroller</li><li>Broke it in refactoring</li><li>Added ability for &quot;string backs&quot;;&nbsp; send a string, plugin then checks if it has a macro with that name</li></ul><br>Demo:&nbsp; federated wiki for OSCON hardware showcase<br><ul class=\"bullet\"><li>From fed wiki in browse, can make hardware blink and beep</li></ul><br>[Fire drill for Ward!]<br><br>Compatibility of Paul&#x27;s code with Ward&#x27;s code?<br><ul class=\"bullet\"><li>Nick wrote a Javascript version of the server, sitting in a folder inside the Ruby project</li><li>Had SFW on Github that had the Ruby server, the node server, and the client and the plugins, in separate directories</li><li>Nick split the Node server onto a separate project, about a year ago -- at that point, the versions were the same</li><li>The Ruby version signs in with OpenID, the Node version now signs in with Persona, which seems to be an better solution at the time</li><li>Ward was having problems with OpenID providers disappearing</li><li>At some point, ended up two versions of the client: after the node server was moved to separate project, moved the client server at the same time?</li><li>Some divergence</li><li>Then did massive refactoring with plugins into separate repo</li><li>Ward then started working with NPM to do a separate Ruby-Gems</li><li>Client version has moved on with time, the server versions haven&#x27;t changed much, it&#x27;s convoluted</li></ul><br>Difference in client versions?<br><ul class=\"bullet\"><li>Just different versions</li><li>When a feature is added, e.g. drag and drop between pages, it won&#x27;t be on any server that was installed a while ago</li><li>When logging in, the version gets downloaded to the client</li><li>Should have a page that tells what version of the server and client is connected to -- it&#x27;s not obvious</li><li>There&#x27;s a server command that does this, but it doesn&#x27;t do a check</li><li>Could check with Git&nbsp; if there&#x27;s a new version</li></ul><br>OpenID vs. Persona?<br><ul class=\"bullet\"><li>OpenID, when save the identity, saves the URL</li><li>Persona saves the e-mail address</li><li>Ward had been have problems with the OpenID provider</li><li>A risk that Persona could disappear?&nbsp; It hasn&#x27;t been taken up more widely</li><li>Current problem with people who use Google identities, the OpenIDs won&#x27;t work</li></ul><br>[Fire drill over for Ward!]<br><br>Timebomb will be people who signed up with Google IDs on fed.wiki.org<br><ul class=\"bullet\"><li>No SLA, not in trouble if they can&#x27;t log in</li><li>Ward erased all of the identity information and reclaimed</li></ul><br>[Nick joined]<br><br>Speed bump of being technologically savvy to use federated wiki?<br><br>Claim a cookie, instead of claiming a site?<br><br>HTML5 browser local storage retains the content across reboots<br><ul class=\"bullet\"><li>WebRTC data channels</li><li>A way to open up binaries</li><li>Still need some server to handle the connection details</li><li>There are people working on not having a server connection</li></ul><br>What behaviour should we expect if there&#x27;s content in the local browser storage?<br><ul class=\"bullet\"><li>Try a variety of ways, and then enable the affordance that works</li><li>Original sponsors insisted on the ability to edit in private, and then publish when a group of aticles is approved</li><li>Can do this by having a local version -- a pain in the butt</li></ul><br>When publishing, is there a way to subscribe?<br><ul class=\"bullet\"><li>To subscribe, add a site that you care about, it will cause all of the sites to be collected</li><li>You have to ask for it</li><li>Not RSS, call it sitemaps</li></ul><br>How to a control-Z?<br><ul class=\"bullet\"><li>Go to the ghost page, fork the page, and then it clears the journals</li><li>Varies between implementations, not all servers do that</li><li>Journal is the undo buffer, visualized</li><li>In the Node version, doesn&#x27;t do the annotation</li></ul><br>Recent refactoring in the Page Handler<br><ul class=\"bullet\"><li>Depending on the fork, different types of behaviours</li><li>Should be unified sometime</li></ul><br>Working with Txtzyme, need to find on pages, have to drag in more frequently<br><ul class=\"bullet\"><li>Not meticulous about IDs, could end up with two things with the same ID</li><li>Need to make samples about events</li><li>Shift-and-drag, drop</li><li>Complicated ways to remember original IDs, with aliases -- but too complicated</li><li>Theory:&nbsp; when you finally learn what to do when the software becomes simple, then the design becomes simple</li><li>Luxury to have a few powerful features, and learn what they can do over time?</li></ul><br>Simple versus easy:&nbsp; simple isn&#x27;t easy to do<br><ul class=\"bullet\"><li>Can make something simple to use, but not easy to use</li><li>Wiki was successful because it was simple and awkward to get around the cheesiness that Ward had written</li></ul><br>Archtectural programming?<br><ul class=\"bullet\"><li>David has been working backwards from pattern language to understand the context of architectural programming, as used by built environment architects</li><li>Ward doesn&#x27;t follow a methodology</li><li>Good fortune and trusting colleagues to make something work, surprisingly, and then make it worth of study</li><li>Might be successful only after someone takes the code away from Ward, and makes it valuable</li><li>Research prototype? Wouldn&#x27;t complain, would be a little hurt</li><li>Nick would do this?</li></ul><br>Agile has worked well when you have a well-defined customers<br><ul class=\"bullet\"><li>Works well when you have a good project manager that adds as a surrogate for a customer</li><li>However, there are a lot of good things that can from not agile?</li></ul><br>Domain-driven development?<br><br>Nick is getting close to feature-freeze<br><ul class=\"bullet\"><li>No official freeze, but have an announce date, can&#x27;t add much</li><li>Do work with visual designers (user experience), have a lot of influence</li><li>Didn&#x27;t have much room for that in agile</li><li>Have elevated computer programming from dysfunctional to average</li><li>Now when people report fantastic gains, it was because they weren&#x27;t getting anything done, now getting things done</li><li>First, physicists, they were used to making things done</li></ul><br>Domain-driven design as agile that is closer to object-oriented design<br><ul class=\"bullet\"><li>Ubiquitous language</li><li>Important that developers use the language they&#x27;re coding, especially if they have a customer using a language</li><li>Eric Evans found this in Smalltalk when doing container shipping -- whole team had to learn a lot of business practices</li><li>Nothing in the book that Ward disagrees with</li><li>More social interaction practices</li><li>The place to begin is on ddd.fed.wiki.org -- the patterns are there</li><li>The best is to buy the book, could ping Eric</li></ul><br><br><"
      },
      "date": 1408558098020
    }
  ]
}