Coevolving Innovations

… in Business Organizations and Information Technologies

Currently Viewing Posts in web tools

A federated wiki site on cPanel

Since my cPanel shared hosting provider supports node.js hosting, installing a federated wiki site beside the usual Softaculous packages is an option. The app requires node.js, and there is a variety of ways to deploy that.

In 2014, I had installed a federated wiki site on Openshift, but then didn’t maintain it as other priorities surfaced.  The site is now available at http://wiki.coevolving.com, and the prior content has been restored.

The installation isn’t a one-button procedure.  However, an administator comfortable with opening an SSH terminal onto your shared hosting account should be able to follow the steps below.  (If you have problems, the federated wiki community hangs out in a room on matrix.org).

A. Creating a Subdomain

(1) Through your browser, from cPanel … Domains … , create a Subdomain.

  • As an example, I can create a Subdomain wiki in the Domain coevolving.com, that will actually be stored in my Home (Document Root) as a wiki.coevolving.com directory.

Subdomain_CreateASubdomain

B. Installing Federated Wiki

(2) From cPanel … Software … Setup Node.js App.

  • In the Web Applications list, Create Application.  As an example, set:
      • Node.js version: 10.11.0
      • Application mode: Production
      • Application root: wiki.coevolving.com

Since my cPanel shared hosting provider supports node.js hosting, installing a federated wiki site beside the usual Softaculous packages is an option. The app requires node.js, and there is a variety of ways to deploy that.

In 2014, I had installed a federated wiki site on Openshift, but then didn’t maintain it as other priorities surfaced.  The site is now available at http://wiki.coevolving.com, and the prior content has been restored.

The installation isn’t a one-button procedure.  However, an administator comfortable with opening an SSH terminal onto your shared hosting account should be able to follow the steps below.  (If you have problems, the federated wiki community hangs out in a room on matrix.org).

A. Creating a Subdomain

(1) Through your browser, from cPanel … Domains … , create a Subdomain.

  • As an example, I can create a Subdomain wiki in the Domain coevolving.com, that will actually be stored in my Home (Document Root) as a wiki.coevolving.com directory.

Subdomain_CreateASubdomain

B. Installing Federated Wiki

(2) From cPanel … Software … Setup Node.js App.

  • In the Web Applications list, Create Application.  As an example, set:
      • Node.js version: 10.11.0
      • Application mode: Production
      • Application root: wiki.coevolving.com

From Flickr to Piwigo

As an alternative to relying on Flickr as my photo-sharing site, a migration to self-hosting Piwigo took less than 2 hours.  With the web-sharing functions of Flickr having remained stable for the past few years, I’ve discovered that Piwigo has all of the features that I need for Creative Commons sharing of my one-photo-per-day habit.

For some years, my larger private photo archives have been on self-hosted Zenphoto sites.  In 2013, the quality improvement on my smartphone cameras led me to change my practice of large-batch photographic essays, in favour of sharing more frequent (i.e. daily) images.  I had admired Flickr for their progressive licensing whereby community members could easily declare Creative Commons.  Further, even at the level of free accounts up to 1TB, their FAQ said (as memorialized from August 2013 on the Internet Archive):

Are my photos every deleted? No, your photos will not be deleted, unless you do it yourself, or fail to play by our Community Guidelines.

Are my photos ever deleted?

Not, your photos will not be deleted, unless you do it yourself, or fail to play by our Community Guidelines.

If I started with the a free account on Flickr, and reached the limit where a Pro Account was needed, I wouldn’t begrudge paying for the service.  My understanding was that if I stepped back down to an free account, not all photos would be directly accessible, but the images wouldn’t be deleted (as described in “Your photos and data on Flickr” | Zach Sheppard | May 26, 2011:

As an alternative to relying on Flickr as my photo-sharing site, a migration to self-hosting Piwigo took less than 2 hours.  With the web-sharing functions of Flickr having remained stable for the past few years, I’ve discovered that Piwigo has all of the features that I need for Creative Commons sharing of my one-photo-per-day habit.

For some years, my larger private photo archives have been on self-hosted Zenphoto sites.  In 2013, the quality improvement on my smartphone cameras led me to change my practice of large-batch photographic essays, in favour of sharing more frequent (i.e. daily) images.  I had admired Flickr for their progressive licensing whereby community members could easily declare Creative Commons.  Further, even at the level of free accounts up to 1TB, their FAQ said (as memorialized from August 2013 on the Internet Archive):

Are my photos every deleted? No, your photos will not be deleted, unless you do it yourself, or fail to play by our Community Guidelines.

Are my photos ever deleted?

Not, your photos will not be deleted, unless you do it yourself, or fail to play by our Community Guidelines.

If I started with the a free account on Flickr, and reached the limit where a Pro Account was needed, I wouldn’t begrudge paying for the service.  My understanding was that if I stepped back down to an free account, not all photos would be directly accessible, but the images wouldn’t be deleted (as described in “Your photos and data on Flickr” | Zach Sheppard | May 26, 2011:

Evolution of open source IBIS software

As a way to enable conversations about wicked problemsIBIS (Issue-Based Information Systems) software seems to have evolved over the past few years.  While the academic support of IBIS software has carried an open source license, part of the community has become independent of the university.

For those unfamiliar with how an IBIS might work, Jeff Conklin (at the Cognexus Institute) had done a lot of work on Issues-Based Information Systems (IBIS) based on Rittel and Webber‘s “wicked problems”. The open source software supporting this is Compendium.   See the “Limits of Conversational Structure” | Jeff Conklin | April 10, 2008 at http://www.youtube.com/watch?v=pxS5wUljfjE .

Simon Buckingham Shum, from the Knowledge Media Institute at The Open University UK, mapped the first UK election Tv debate in 2010 (or at least the few first minutes before his connection was interrupted).  “Dialogue Mapping election debate video” | Simon Buckingham Shum | April 23, 2010 at http://www.youtube.com/watch?v=WPF64UXFER0.

Paul Culmsee, an issue and dialogue mapper in Australia, shares some of his experience in facilitation based in three videos.

As a way to enable conversations about wicked problemsIBIS (Issue-Based Information Systems) software seems to have evolved over the past few years.  While the academic support of IBIS software has carried an open source license, part of the community has become independent of the university.

For those unfamiliar with how an IBIS might work, Jeff Conklin (at the Cognexus Institute) had done a lot of work on Issues-Based Information Systems (IBIS) based on Rittel and Webber‘s “wicked problems”. The open source software supporting this is Compendium.   See the “Limits of Conversational Structure” | Jeff Conklin | April 10, 2008 at http://www.youtube.com/watch?v=pxS5wUljfjE .

Simon Buckingham Shum, from the Knowledge Media Institute at The Open University UK, mapped the first UK election Tv debate in 2010 (or at least the few first minutes before his connection was interrupted).  “Dialogue Mapping election debate video” | Simon Buckingham Shum | April 23, 2010 at http://www.youtube.com/watch?v=WPF64UXFER0.

Paul Culmsee, an issue and dialogue mapper in Australia, shares some of his experience in facilitation based in three videos.

Want your eyes and hands free? Have this blog read to you!

As much as I read content from the web — either through a feed reader (I’m currently favouring RssOwl) or a browser (I read with Firefox, and post comments with Flock and Cocomment) — there are times when I want my eyes and hands to be free.  I maintain a queue of MP3 audio recordings on a Creative Zen V for listening when walking or driving, and subsequently report on lectures and interview worth noting on the Media Input Queue blog.

The content on this Coevolving Innovations blog is text intensive — people who prefer photos are better to follow the Distractions, Reflections blog — so I have sympathies for readers who find the length tedious.

I was following through on some dialogue on mentoring from Sacha Chua (@sachac) to a blog post by Brian O’Donovan on social software (@bodonovan).  I noticed he had a “Listen” button on the entry, so I pressed it … triggering an automated reading of the content in a woman’s voice. This experiment gave me a close-to-perfect reproduction of the text content (and I could guess the meaning of the mispronunciations).

Following through the links, I discovered ReadSpeaker webReader, which originated as a service for the visually impaired.  For personal web sites, webSpeaker Free is an ad-supported service (with pre and/or post audio, and banners in the player).  It took me less than ten minutes to install on this WordPress blog (as one of the benefits of self-hosting on my own domain).

I noticed that Brian preferred a female voice with a British accent.  I’ve tried that, and the American male voice, and somehow find the American female voice the easiest to my ear.

The structure of WordPress plugins makes adding and removing ReadSpeaker webReader easy, so the added function will be another natural experiment over time.

As much as I read content from the web — either through a feed reader (I’m currently favouring RssOwl) or a browser (I read with Firefox, and post comments with Flock and Cocomment) — there are times when I want my eyes and hands to be free.  I maintain a queue of MP3 audio recordings on a Creative Zen V for listening when walking or driving, and subsequently report on lectures and interview worth noting on the Media Input Queue blog.

The content on this Coevolving Innovations blog is text intensive — people who prefer photos are better to follow the Distractions, Reflections blog — so I have sympathies for readers who find the length tedious.

I was following through on some dialogue on mentoring from Sacha Chua (@sachac) to a blog post by Brian O’Donovan on social software (@bodonovan).  I noticed he had a “Listen” button on the entry, so I pressed it … triggering an automated reading of the content in a woman’s voice. This experiment gave me a close-to-perfect reproduction of the text content (and I could guess the meaning of the mispronunciations).

Following through the links, I discovered ReadSpeaker webReader, which originated as a service for the visually impaired.  For personal web sites, webSpeaker Free is an ad-supported service (with pre and/or post audio, and banners in the player).  It took me less than ten minutes to install on this WordPress blog (as one of the benefits of self-hosting on my own domain).

I noticed that Brian preferred a female voice with a British accent.  I’ve tried that, and the American male voice, and somehow find the American female voice the easiest to my ear.

The structure of WordPress plugins makes adding and removing ReadSpeaker webReader easy, so the added function will be another natural experiment over time.

Digital photos: capturing, archiving, printing, web sharing, photoblogging

Digital cameras have become so common that they’re often now a feature in mobile phones and audio players.  Pressing a button to capture a snapshot of time is so easy.  The workflow of storing, printing and sharing those images is complicated.  Many would like to return to the days when we would just take the film cartridge out of the camera, and drop it to a photo lab for processing (often in about an hour).

People take more photographs digitally than they did with film cameras.  In a six-month study in 2000, when digital cameras were relatively uncommon, subjects (aged 24 to 38) took 200 to 1000 (with an average about 500) photographs, compared to their prior non-digital accumulated collection of 300 to 3000 (with an average of about 1000) pictures (Rodden & Wood 2003).  This means that when digital cameras were relatively expensive — and camera phones didn’t yet exist — people were averaging about 1 to 5 photos per day!

People presumably use cameras because they want to be able to retrieve the images later.  In a study of 18 parents, the value of long-retrieval of family pictures was high (i.e. around 4.7 on a scale of 5).  On experiments of 71 retrieval tasks — finding birthdays, family trips, first pictures of a child, etc. — 61% were successful, taking about 2.5 minutes each.  On the 39% of unsuccessful retrievals, subjects gave up after about 4 minutes  (Whittaker et al. 2010).  This effectively means that, on average, nearly 40% of the digital photos taken last year are lost, and considerable persistence is needed for them to be refound.

I. What activities, platforms and artifacts are involved with managing digital photos?

Digitalization in photography has replaced trips to the photo lab with the copying of electronic files.  Industry standards have stabilized so that image files can be readily copied from cameras to personal computing devices, and onto web servers.  Here’s a diagram of some of the activities, platforms and artifacts in digital photography.

digital_photo_workflow

Based on this diagram, let me (a) pose some questions for reflection on the choices we implicitly make about managing photos, (b) outline some popular alternatives, and (c) describe the way I do it, myself.

II. What type of photographer am I?

Digital cameras have become so common that they’re often now a feature in mobile phones and audio players.  Pressing a button to capture a snapshot of time is so easy.  The workflow of storing, printing and sharing those images is complicated.  Many would like to return to the days when we would just take the film cartridge out of the camera, and drop it to a photo lab for processing (often in about an hour).

People take more photographs digitally than they did with film cameras.  In a six-month study in 2000, when digital cameras were relatively uncommon, subjects (aged 24 to 38) took 200 to 1000 (with an average about 500) photographs, compared to their prior non-digital accumulated collection of 300 to 3000 (with an average of about 1000) pictures (Rodden & Wood 2003).  This means that when digital cameras were relatively expensive — and camera phones didn’t yet exist — people were averaging about 1 to 5 photos per day!

People presumably use cameras because they want to be able to retrieve the images later.  In a study of 18 parents, the value of long-retrieval of family pictures was high (i.e. around 4.7 on a scale of 5).  On experiments of 71 retrieval tasks — finding birthdays, family trips, first pictures of a child, etc. — 61% were successful, taking about 2.5 minutes each.  On the 39% of unsuccessful retrievals, subjects gave up after about 4 minutes  (Whittaker et al. 2010).  This effectively means that, on average, nearly 40% of the digital photos taken last year are lost, and considerable persistence is needed for them to be refound.

I. What activities, platforms and artifacts are involved with managing digital photos?

Digitalization in photography has replaced trips to the photo lab with the copying of electronic files.  Industry standards have stabilized so that image files can be readily copied from cameras to personal computing devices, and onto web servers.  Here’s a diagram of some of the activities, platforms and artifacts in digital photography.

digital_photo_workflow

Based on this diagram, let me (a) pose some questions for reflection on the choices we implicitly make about managing photos, (b) outline some popular alternatives, and (c) describe the way I do it, myself.

II. What type of photographer am I?

Blogging, microblogging, webstreaming

While some of my activity on the Internet is recreational, I continue to play with web tools to learn about the ever-evolving technology.  While the average person has become comfortable with e-mail, web feeds are still pretty much a mystery to many.  The RSS and Atom specifications first used by newswires has become the principal form of web syndication for blogs and social media.

I’ve recently rearranged my pattern of web use (again).  To encourage readers to think about how they use the Internet, let me pose four questions.

  • 1. Which principles on web content do I have in mind?
  • 2. How do I post content, and flow it?
  • 3. Why have I recently changed my use?
  • 4. What consideration should web users have for their content?

With the way that technology continues to evolve, the specific web applications may change … but the pattern should remain the same.

1. Which principles on web content do I have in mind?

My attitude is reflected in two ideas:  (a) open content with attribution, and (b) open platforms with interoperability.

(a) Open content with attribution reflects that I like to share my learning with other people.   Posting the content on the Internet improves access and distribution.  I understand the workings of copyright — there’s a Creative Commons license on this blog — which means that I retain ownership of my words, on the condition that if someone wants to formally cite the work, he or she should cite me as the source.  I’m not an author who makes his living at writing, so simple acknowledgement is normally sufficient.

(b) Open platforms with interoperability means that I don’t want my content inappropriately trapped in places inaccessible to others.  I appreciate instances when content should remain private, respecting the needs of others and/or commercial conditions, but secrecy should be the exception rather than the rule.  The content should flow freely (i.e. free as in liberty), rather than having to stumble through technological obstacles.

2. How do I post content, and flow it?

With these principles in mind, I’m reforming the way that I interact on the web.  Here’s a diagram (linked to another page in an interactive map).

20091126_webstream-copy_475px

While some of my activity on the Internet is recreational, I continue to play with web tools to learn about the ever-evolving technology.  While the average person has become comfortable with e-mail, web feeds are still pretty much a mystery to many.  The RSS and Atom specifications first used by newswires has become the principal form of web syndication for blogs and social media.

I’ve recently rearranged my pattern of web use (again).  To encourage readers to think about how they use the Internet, let me pose four questions.

  • 1. Which principles on web content do I have in mind?
  • 2. How do I post content, and flow it?
  • 3. Why have I recently changed my use?
  • 4. What consideration should web users have for their content?

With the way that technology continues to evolve, the specific web applications may change … but the pattern should remain the same.

1. Which principles on web content do I have in mind?

My attitude is reflected in two ideas:  (a) open content with attribution, and (b) open platforms with interoperability.

(a) Open content with attribution reflects that I like to share my learning with other people.   Posting the content on the Internet improves access and distribution.  I understand the workings of copyright — there’s a Creative Commons license on this blog — which means that I retain ownership of my words, on the condition that if someone wants to formally cite the work, he or she should cite me as the source.  I’m not an author who makes his living at writing, so simple acknowledgement is normally sufficient.

(b) Open platforms with interoperability means that I don’t want my content inappropriately trapped in places inaccessible to others.  I appreciate instances when content should remain private, respecting the needs of others and/or commercial conditions, but secrecy should be the exception rather than the rule.  The content should flow freely (i.e. free as in liberty), rather than having to stumble through technological obstacles.

2. How do I post content, and flow it?

With these principles in mind, I’m reforming the way that I interact on the web.  Here’s a diagram (linked to another page in an interactive map).

20091126_webstream-copy_475px

  • Recent Posts

  • Archives

  • RSS qoto.org/@daviding (Mastodon)

    • New status by daviding May 19, 2019
      Fit the people around an organization; or an organization around the people? Working backwards, say @MitroffCrisis + #HaroldLinstone, from current concrete choices to uncertain futures, surfaces strategic assumptions in a collective decision, better than starting with an abstract scorecard to rank candidates. The Unbounded Mind is an easier-reading follow-on to The Design of Inquiry Systems […]
    • New status by daviding April 28, 2019
      Our house is on the edge of a flood plain. We know this, because the end of our street in Toronto Riverside was at Lake Ontario, before landfill in the early 1900s. Not everyone knows about what's under the place where they live. "Poor flood-risk maps, or none at all, are keeping Canadian communities in […]
    • New status by daviding April 26, 2019
      An open education system encourages scholarship that embraces perspectives from around the world. The Scholar Rescue Fund is a hopeful initiative that, in a perfect world, wouldn't have to exist. "Canada playing major role as safe haven for at-risk academics from strife-torn countries" | Danielle Edwards | April 23, 2019 | Globe & Mail at […]
    • New status by daviding April 25, 2019
      Moving from coal to green energy for Dong (nee Danish Oil and Natural Gas) started in 2008, leading to an CEO change in 2012, to a 2017 divestment of fossil-fuel bases businesses. Perseverance can pay off, but patience goes through trials. "A tale of transformation: the Danish company that went from black to green energy" […]
    • New status by daviding April 21, 2019
      Public libraries can become hubs for peer-to-peer learning. In the Let's Learn Teach Online program, #TorontoLibrary has partnered with #P2PU, #CiscoNetAcad, #TorontoESS, and #GBCollege to facilitate "Linux Unhatched" and "Introduction to IoT". Larysa Essex shared their experiences at the @gtalug meeting on April 9, 2019. https://daviding.wordpress.com/2019/04/20/2019-04-09-larysa-essex-linux-unhatched-learning-circles-at-toronto-public-library-web-video/
  • RSS on IngBrief

  • RSS on Media Queue

  • RSS on daviding.com

    • 2019/04 Moments April 2019
      End of a 23-day visit in Shanghai, readjusting to Eastern Time with the many lecture, meetup, friends and family distractions of Toronto.
    • 2019/03 Moments March 2019
      Month of intensive lectures and research meetings, in Toronto and then in Shanghai, with social breaks on local excursions to clear minds.
    • 2019/02 Moments February 2019
      Reduced exercise outside with a cold and snowy February, with excursions out of the house to warm places with family, friends and colleagues.
    • 2019/01 Moments January 2019
      January in Toronto has lots of intellectual offerings and artistic exhibitions to attract the curious out of warm homes, through cold and snow.
    • 2018/12 Moments December 2018
      Tried to have a normal month, with a busy social calendar of birthdays, a funeral plus Christmas season, while daily temperatures hovered just above freezing.
    • 2018/11 Moments November 2011
      Mentally busy month with a conference coming to town, and maintaining the regular pattern of local meetings, travel around town only by bicycle.
  • Meta

  • Creative Commons License
    This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License
    Theme modified from DevDmBootstrap4 by Danny Machal