<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for countably infinite</title>
	<atom:link href="http://www.countablyinfinite.ca/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.countablyinfinite.ca</link>
	<description>a dash of impossibility makes for more fun</description>
	<lastBuildDate>Thu, 17 May 2012 18:27:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Reflecting on This Is Our Stop by Todd Sieling</title>
		<link>http://www.countablyinfinite.ca/blog/2012/05/reflecting-on-this-is-our-stop/comment-page-1/#comment-118756</link>
		<dc:creator>Todd Sieling</dc:creator>
		<pubDate>Thu, 17 May 2012 18:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/?p=1085#comment-118756</guid>
		<description>A quick word on Twitter and SMS as well: these are not easy starters. 

We have a 200 character limit on our posts vs. Twitter&#039;s 140, and from that 140 we would have to direct the message to @thisisourstop (or a new account with a shorter name), identify the stop number (likely plus a space) and one or more categories. Assuming no categories we would be cutting down to 120 characters. The two models might be too different to integrate smoothly. But we have started posting links to the stops with the most interesting comments or conversations that we see happening, and will keep experimenting like that.

For SMS, the issues is not about character length as much as it is about communicating the feature to users. We can&#039;t really print instructions on the stickers, and putting it on the homepage would be odd as reaching the homepage on a phone browser means you can use the app as it is now. While technically possible, it falls apart because we don&#039;t have a huge communication pipe to get the word out to, and would have to think about how to differentiate getting a list of comments from posting one of your own. It&#039;s tricky stuff, but these ideas are good to explore just the same.</description>
		<content:encoded><![CDATA[<p>A quick word on Twitter and SMS as well: these are not easy starters. </p>
<p>We have a 200 character limit on our posts vs. Twitter&#8217;s 140, and from that 140 we would have to direct the message to @thisisourstop (or a new account with a shorter name), identify the stop number (likely plus a space) and one or more categories. Assuming no categories we would be cutting down to 120 characters. The two models might be too different to integrate smoothly. But we have started posting links to the stops with the most interesting comments or conversations that we see happening, and will keep experimenting like that.</p>
<p>For SMS, the issues is not about character length as much as it is about communicating the feature to users. We can&#8217;t really print instructions on the stickers, and putting it on the homepage would be odd as reaching the homepage on a phone browser means you can use the app as it is now. While technically possible, it falls apart because we don&#8217;t have a huge communication pipe to get the word out to, and would have to think about how to differentiate getting a list of comments from posting one of your own. It&#8217;s tricky stuff, but these ideas are good to explore just the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reflecting on This Is Our Stop by Todd Sieling</title>
		<link>http://www.countablyinfinite.ca/blog/2012/05/reflecting-on-this-is-our-stop/comment-page-1/#comment-118755</link>
		<dc:creator>Todd Sieling</dc:creator>
		<pubDate>Thu, 17 May 2012 18:23:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/?p=1085#comment-118755</guid>
		<description>When we made the decision to target smartphones in This Is Our Stop, we knew we would be leaving some people behind because of the technology divide that exists. That same divide was felt more severely when Translink started putting up fewer paper schedules after introducing SMS schedules, as there is a divide between people who do and don&#039;t have phones. 

This was never a project with ubiquity in mind, and we don&#039;t root our choice of technology in class divisions. We rooted that decision in the phones we see people using the most (we live right in Vancouver and what we see might be different from what others see in the burbs or elsewhere), in what we like working on, and in what we thought would produce the best overall experience. When we look at $99 iPhones at the lowest level, we see which way the future is going for phones and that&#039;s what we built for. 

We don&#039;t take Robert&#039;s criticism as negative, but rather as a validation of the core concept, that conversation among riders about their infrastructure is important. What&#039;s been so heartening about the project is that the vast majority of people posting are indeed talking about transit and the areas and people around their stops. They are, in other words, buying into the idea, and we think that&#039;s great. If Robert feels this kind of service should be ubiquitous, Translink is the one to talk to, and we really appreciate this token of support.</description>
		<content:encoded><![CDATA[<p>When we made the decision to target smartphones in This Is Our Stop, we knew we would be leaving some people behind because of the technology divide that exists. That same divide was felt more severely when Translink started putting up fewer paper schedules after introducing SMS schedules, as there is a divide between people who do and don&#8217;t have phones. </p>
<p>This was never a project with ubiquity in mind, and we don&#8217;t root our choice of technology in class divisions. We rooted that decision in the phones we see people using the most (we live right in Vancouver and what we see might be different from what others see in the burbs or elsewhere), in what we like working on, and in what we thought would produce the best overall experience. When we look at $99 iPhones at the lowest level, we see which way the future is going for phones and that&#8217;s what we built for. </p>
<p>We don&#8217;t take Robert&#8217;s criticism as negative, but rather as a validation of the core concept, that conversation among riders about their infrastructure is important. What&#8217;s been so heartening about the project is that the vast majority of people posting are indeed talking about transit and the areas and people around their stops. They are, in other words, buying into the idea, and we think that&#8217;s great. If Robert feels this kind of service should be ubiquitous, Translink is the one to talk to, and we really appreciate this token of support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reflecting on This Is Our Stop by Karen Quinn Fung</title>
		<link>http://www.countablyinfinite.ca/blog/2012/05/reflecting-on-this-is-our-stop/comment-page-1/#comment-118601</link>
		<dc:creator>Karen Quinn Fung</dc:creator>
		<pubDate>Tue, 15 May 2012 21:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/?p=1085#comment-118601</guid>
		<description>Robert,

While I agree with much of the content of your comment, I really have to take exception with the tone.

No one denies that most bus riders are not smartphone users. If it&#039;s not clear from my tweet, I don&#039;t own a smartphone myself, and my use of TIOS is limited as a result. That said, I&#039;ve also had the chance to interact with people who have developed tools involving SMS gateways (not Denim and Steel), so I&#039;m privy to the fact that the reality of building TIOS so that it would be usable for non-smartphone users is a &lt;u&gt;considerably&lt;/u&gt; expensive undertaking. Unfortunately, that&#039;s just the way the chips fall when it comes to the way these telecommunication decisions have been made (though I don&#039;t know if that&#039;s Canada-specific or international).

And I would take considerable exception to levelling any blame for this towards Denim and Steel, because they and their collaborators built TIOS in their spare time. That&#039;s time away from their community commitments, their friends and family, and they did it because they wanted to build something other people would enjoy. And they are also contributing the perhaps minor but definitely non-zero amount of money for the resources to run the service at all. Most of all, as I say in my post, it&#039;s just a start.

So as an alternative to your approach, I would rather ask the constructive questions for &lt;strong&gt;actually&lt;/strong&gt; making this happen, like: who benefits from the existence of TIOS that would be willing to put money towards making the service more broadly accessible to those without smartphones? In Portland, for example, local business sponsor specific bus stops. Or maybe piggy-back off Twitter, a service that already is accessible by SMS.

Is answering that question something you&#039;d be interested in contributing to, Robert?

Karen</description>
		<content:encoded><![CDATA[<p>Robert,</p>
<p>While I agree with much of the content of your comment, I really have to take exception with the tone.</p>
<p>No one denies that most bus riders are not smartphone users. If it&#8217;s not clear from my tweet, I don&#8217;t own a smartphone myself, and my use of TIOS is limited as a result. That said, I&#8217;ve also had the chance to interact with people who have developed tools involving SMS gateways (not Denim and Steel), so I&#8217;m privy to the fact that the reality of building TIOS so that it would be usable for non-smartphone users is a <u>considerably</u> expensive undertaking. Unfortunately, that&#8217;s just the way the chips fall when it comes to the way these telecommunication decisions have been made (though I don&#8217;t know if that&#8217;s Canada-specific or international).</p>
<p>And I would take considerable exception to levelling any blame for this towards Denim and Steel, because they and their collaborators built TIOS in their spare time. That&#8217;s time away from their community commitments, their friends and family, and they did it because they wanted to build something other people would enjoy. And they are also contributing the perhaps minor but definitely non-zero amount of money for the resources to run the service at all. Most of all, as I say in my post, it&#8217;s just a start.</p>
<p>So as an alternative to your approach, I would rather ask the constructive questions for <strong>actually</strong> making this happen, like: who benefits from the existence of TIOS that would be willing to put money towards making the service more broadly accessible to those without smartphones? In Portland, for example, local business sponsor specific bus stops. Or maybe piggy-back off Twitter, a service that already is accessible by SMS.</p>
<p>Is answering that question something you&#8217;d be interested in contributing to, Robert?</p>
<p>Karen</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Re-visiting co-design as participation in planning by Karen Quinn Fung</title>
		<link>http://www.countablyinfinite.ca/blog/2012/05/re-visiting-co-design-as-participation-in-planning/comment-page-1/#comment-118598</link>
		<dc:creator>Karen Quinn Fung</dc:creator>
		<pubDate>Tue, 15 May 2012 21:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/?p=1089#comment-118598</guid>
		<description>Hi Neil,

Thanks for the comment! You are far from the only person thinking about using iPads for planning in this way — in fact, while I was at the American Planning Association conference, I bumped into Darin Dinsmore of Crowdbrite who said his company&#039;s iPad app was close to or already in the App Store. Now that I look it up, I see that the &lt;a href=&quot;http://itunes.apple.com/us/app/crowdbrite/id422607875?mt=8&quot; rel=&quot;nofollow&quot;&gt;Crowdbrite app is indeed in there&lt;/a&gt;, although having just downloaded it myself and not being able to see any of their projects underway, I don&#039;t know if the augmented reality features he had mentioned when he was talking about the app last year have made it into the app as available just yet.

I don&#039;t know enough about scenario planning just yet to know if this sort of activity falls into scenario planning (my instinct is yes, although perhaps mostly on the urban design side of it) — &lt;a href=&quot;http://twitter.com/fkh&quot; rel=&quot;nofollow&quot;&gt;Frank Hebbert&lt;/a&gt;, during a session at the APA on Advancing Scenario Planning tools (blogging backlog ack!), said that it was very likely that by this time next year we&#039;d start seeing scenario planning in the palm of your hand, i.e. on mobile devices. I&#039;m fascinated and thrilled but also hesitant, mostly because I&#039;m always wondering who these kinds of tool would help, but also who they really wouldn&#039;t.

That said, if this is a tool that can help people looking at spaces like Lougheed Highway to begin considering what it could look like as a &lt;em&gt;place&lt;/em&gt; and not just a giant thoroughfare for cars, all the better! :)</description>
		<content:encoded><![CDATA[<p>Hi Neil,</p>
<p>Thanks for the comment! You are far from the only person thinking about using iPads for planning in this way — in fact, while I was at the American Planning Association conference, I bumped into Darin Dinsmore of Crowdbrite who said his company&#8217;s iPad app was close to or already in the App Store. Now that I look it up, I see that the <a href="http://itunes.apple.com/us/app/crowdbrite/id422607875?mt=8" rel="nofollow">Crowdbrite app is indeed in there</a>, although having just downloaded it myself and not being able to see any of their projects underway, I don&#8217;t know if the augmented reality features he had mentioned when he was talking about the app last year have made it into the app as available just yet.</p>
<p>I don&#8217;t know enough about scenario planning just yet to know if this sort of activity falls into scenario planning (my instinct is yes, although perhaps mostly on the urban design side of it) — <a href="http://twitter.com/fkh" rel="nofollow">Frank Hebbert</a>, during a session at the APA on Advancing Scenario Planning tools (blogging backlog ack!), said that it was very likely that by this time next year we&#8217;d start seeing scenario planning in the palm of your hand, i.e. on mobile devices. I&#8217;m fascinated and thrilled but also hesitant, mostly because I&#8217;m always wondering who these kinds of tool would help, but also who they really wouldn&#8217;t.</p>
<p>That said, if this is a tool that can help people looking at spaces like Lougheed Highway to begin considering what it could look like as a <em>place</em> and not just a giant thoroughfare for cars, all the better! <img src='http://www.countablyinfinite.ca/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Complexifiers and Simplifiers: some necessary nuance by Neil</title>
		<link>http://www.countablyinfinite.ca/blog/2011/11/complexifiers-and-simplifiers-some-necessary-nuance/comment-page-1/#comment-118594</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Tue, 15 May 2012 18:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/?p=1019#comment-118594</guid>
		<description>See also Ribbonfarm on literacy: exposition and condensation.</description>
		<content:encoded><![CDATA[<p>See also Ribbonfarm on literacy: exposition and condensation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Re-visiting co-design as participation in planning by Neil</title>
		<link>http://www.countablyinfinite.ca/blog/2012/05/re-visiting-co-design-as-participation-in-planning/comment-page-1/#comment-118590</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Tue, 15 May 2012 17:50:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/?p=1089#comment-118590</guid>
		<description>Given your technology interest, what do you think about the opportunity for iPad apps to help here (or better hardware in the future). The direct interaction of the screen seems to help people express themselves well. You could keep the real-life social context of course.

I&#039;ve imagined a &quot;simple&quot; app for a while, that lets you mark out perspective lines (&amp; horizon: the app could help snap to its own guesses of building lines etc.) on a street-scene (from gmaps, or one you&#039;ve taken yourself) and then drop in street features. Bike lane, trees, bench, 3-story with groundfloor retail. The results would clearly be uglier than a real artist, but a twitter/blogosphere of amateur quickly-hacked-together street visions would really help discussions, I reckon.

What would this street look like if narrowed? What if it had a streetcar down the middle? What if there were a row of townhouses instead of single family homes.

There are complicated apps that let you drop sketchup objects into a live virtual reality, but I&#039;m looking for something more like cut&amp;paste collage with perspective-smart scaling.

Once you&#039;ve drawn on the perspective grid, I&#039;d imagine you could also cut out elements from your original to add to the cloud or your own other scenes. e.g. what would this mount pleasant street look like with a row of kitsilano apartments?</description>
		<content:encoded><![CDATA[<p>Given your technology interest, what do you think about the opportunity for iPad apps to help here (or better hardware in the future). The direct interaction of the screen seems to help people express themselves well. You could keep the real-life social context of course.</p>
<p>I&#8217;ve imagined a &#8220;simple&#8221; app for a while, that lets you mark out perspective lines (&amp; horizon: the app could help snap to its own guesses of building lines etc.) on a street-scene (from gmaps, or one you&#8217;ve taken yourself) and then drop in street features. Bike lane, trees, bench, 3-story with groundfloor retail. The results would clearly be uglier than a real artist, but a twitter/blogosphere of amateur quickly-hacked-together street visions would really help discussions, I reckon.</p>
<p>What would this street look like if narrowed? What if it had a streetcar down the middle? What if there were a row of townhouses instead of single family homes.</p>
<p>There are complicated apps that let you drop sketchup objects into a live virtual reality, but I&#8217;m looking for something more like cut&amp;paste collage with perspective-smart scaling.</p>
<p>Once you&#8217;ve drawn on the perspective grid, I&#8217;d imagine you could also cut out elements from your original to add to the cloud or your own other scenes. e.g. what would this mount pleasant street look like with a row of kitsilano apartments?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reflecting on This Is Our Stop by Robert</title>
		<link>http://www.countablyinfinite.ca/blog/2012/05/reflecting-on-this-is-our-stop/comment-page-1/#comment-118528</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Tue, 15 May 2012 04:12:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/?p=1085#comment-118528</guid>
		<description>You mention non-smartphone users, surprisingly, since the existence of This is our stop, and m.translink.ca, depends on smartphones. I don&#039;t have a smartphone, can&#039;t afford it, and probably never will. When I take the bus every day, most people on the bus don&#039;t have smartphones, or are not using them, and most people don&#039;t seem to have a phone. In other words, This is our stop, and m.translink.ca, are for fairly wealthy people, which seems to be less than the majority of transit users in Vancouver, and probably most places. To be really useful, these two services have to be universal. Until that happens, they will remain niche services for a certain class of people.</description>
		<content:encoded><![CDATA[<p>You mention non-smartphone users, surprisingly, since the existence of This is our stop, and m.translink.ca, depends on smartphones. I don&#8217;t have a smartphone, can&#8217;t afford it, and probably never will. When I take the bus every day, most people on the bus don&#8217;t have smartphones, or are not using them, and most people don&#8217;t seem to have a phone. In other words, This is our stop, and m.translink.ca, are for fairly wealthy people, which seems to be less than the majority of transit users in Vancouver, and probably most places. To be really useful, these two services have to be universal. Until that happens, they will remain niche services for a certain class of people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Co-Design Workshop Demonstration by Participation by Design: Co-design as public engagement in planning</title>
		<link>http://www.countablyinfinite.ca/blog/2009/04/co-design-workshop-demonstration/comment-page-1/#comment-118159</link>
		<dc:creator>Participation by Design: Co-design as public engagement in planning</dc:creator>
		<pubDate>Wed, 09 May 2012 13:43:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/blog/?p=342#comment-118159</guid>
		<description>[...] blog post of a co-design demonstration from 2009 also contains some images of the consensus process where people vote on the features in the [...]</description>
		<content:encoded><![CDATA[<p>[...] blog post of a co-design demonstration from 2009 also contains some images of the consensus process where people vote on the features in the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Co-Design Workshop Demonstration by Re-visiting co-design as participation in planning</title>
		<link>http://www.countablyinfinite.ca/blog/2009/04/co-design-workshop-demonstration/comment-page-1/#comment-117887</link>
		<dc:creator>Re-visiting co-design as participation in planning</dc:creator>
		<pubDate>Fri, 04 May 2012 14:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/blog/?p=342#comment-117887</guid>
		<description>[...] blog post of a co-design demonstration from 2009 also contains some images of the consensus process where people vote on the features in the [...]</description>
		<content:encoded><![CDATA[<p>[...] blog post of a co-design demonstration from 2009 also contains some images of the consensus process where people vote on the features in the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Transit Pet Peeves: One person&#8217;s contest, another person&#8217;s social inclusion setback by Reflecting on This Is Our Stop</title>
		<link>http://www.countablyinfinite.ca/blog/2011/11/transit-pet-peeves-one-persons-contest-another-persons-social-inclusion-setback/comment-page-1/#comment-117808</link>
		<dc:creator>Reflecting on This Is Our Stop</dc:creator>
		<pubDate>Thu, 03 May 2012 17:21:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.countablyinfinite.ca/?p=1038#comment-117808</guid>
		<description>[...] North America) is seen extremely negatively in contrast to other modes of transportation — often because of other people. I don&#8217;t think that&#8217;s true, and I know that others don&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[...] North America) is seen extremely negatively in contrast to other modes of transportation — often because of other people. I don&#8217;t think that&#8217;s true, and I know that others don&#8217;t [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

