<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Igniter - Latest Comments</title><link>http://igniter.disqus.com/</link><description>ventures | systems | investment | change</description><atom:link href="https://igniter.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 01 May 2013 17:45:25 -0000</lastBuildDate><item><title>Re: http://igniter.tumblr.com/post/33716758905</title><link>http://igniter.tumblr.com/post/33716758905#comment-881650493</link><description>&lt;p&gt;What an outstanding photo!  And, that's what the "Welcome Dinner" really looks like for those who spend time with us in PROVENCE PARADISE.   Looks good?  You bet!  Our way of saying "Welcome to our 'hamlet.'"&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">William, the old innkeeper  </dc:creator><pubDate>Wed, 01 May 2013 17:45:25 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-569015106</link><description>&lt;p&gt;fun and useful discussion indeed. I think the process will involve a bit of work from the user side to get build their communities and conversations. There is not easy way around this and perhaps there shouldn't be :) There are great tools to help such as disqus and engagio but but relationships through meaningful conversations which lead to communities should involve a bit of work. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Abdallah Al-Hakim</dc:creator><pubDate>Wed, 27 Jun 2012 11:54:16 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-568985592</link><description>&lt;p&gt;Another solution to the fragmentation problem -&amp;gt; &lt;a href="http://www.livefyre.com" rel="nofollow noopener" target="_blank" title="http://www.livefyre.com"&gt;http://www.livefyre.com&lt;/a&gt; (ht @phillipadsmith  )&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Wed, 27 Jun 2012 11:15:03 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-568975057</link><description>&lt;p&gt;I'm sure it is in the mindset of Disqus. I know the team and have been pushing this for awhile.&lt;/p&gt;&lt;p&gt;On the roadmap...I'm not privy to that.&lt;/p&gt;&lt;p&gt;But...parsing social data to create a semantically implicit web is really hard. Disqus has the dataset, it is just a question of whether they have a model.&lt;/p&gt;&lt;p&gt;My sense is not...D12 is a huge undertaking and includes monetization. If you are going to undertake what we are discussing, that itself needs to be the focus.&lt;/p&gt;&lt;p&gt;Fun discussion. I think and blog and consult on community. Obsessed actually a bit with it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">awaldstein</dc:creator><pubDate>Wed, 27 Jun 2012 11:01:16 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-568856039</link><description>&lt;p&gt;Yes, I do think @disqus is closest to handling the fragmentation problem, will be interesting to see if/when it shows up on the roadmap. Do you think it will?&lt;/p&gt;&lt;p&gt;And yes, well said about engagement. It's more about the people.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Wed, 27 Jun 2012 08:29:55 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-568849638</link><description>&lt;p&gt;Thanks @Abdallah Al-Hakim . I was thinking first about aggregation and display which are not - as far as i can tell - handled by Engagio.  They do however address the point of fragmentation from the perspective of the content author and commenters.  Might be interesting if that could be embedded in the clog like disqus is, allowing comment streams from all instances of that content to be displayed if appropriated.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Wed, 27 Jun 2012 08:20:40 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-568711094</link><description>&lt;p&gt;Thnx for alerting me to this post.&lt;/p&gt;&lt;p&gt;I agree with the steps but the dynamics are more complex, less distinct.&lt;/p&gt;&lt;p&gt;The connecting thread is Disqus actually, the discovery mechanism Engagio at least in your scenario.&lt;/p&gt;&lt;p&gt;But Engagement is less the subject of each of them, it is the human factor. You can create the environment but it always beyond the mechanics of the tools.&lt;/p&gt;&lt;p&gt;As far as community building as a platform. No cookie cutter exists but Disqus, more than any other has the potential for this if that is the direction they choose to go in.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">awaldstein</dc:creator><pubDate>Wed, 27 Jun 2012 05:17:25 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-568418207</link><description>&lt;p&gt;very intriguing. I think it is a three step process - a)discovery b)engagement and c)community building. The first two steps of the process are already being managed by Engagio (at least for me) - actually it was through Engagio that I discovered this interesting post and got engaged in the conversation. The third point is regarding community building around these conversations and making them discoverable. This is where no such product exist yet but I think Engagio is moving along the right track. Both  @awaldstein and @William Mougayar:disqus should be interested in this post&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Abdallah Al-Hakim</dc:creator><pubDate>Wed, 27 Jun 2012 00:03:29 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-567964290</link><description>&lt;p&gt;From a community vibrancy perspective I think that is the ideal scenario - I also think it is a very tricky thing implement that needs some deep thinking and grounding in online social dynamics - which I don't think we really do understand yet - and probably more often misinterpret. &lt;br&gt;Where this question also leads is to ask which audience is the most important - the organization or the community.  The answer to that would definitely suggest some different pathways and starting points I think.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Tue, 26 Jun 2012 18:09:36 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-567949491</link><description>&lt;p&gt;let's even extend it further - what if by default it was open to anyone - inside and outside the org, and then the community regulates itself?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">aweissman</dc:creator><pubDate>Tue, 26 Jun 2012 17:55:28 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-567941335</link><description>&lt;p&gt;I think that could be really interesting... particularly if it were community members that had established themselves in some way within the community already. Perhaps manually selected, perhaps informed by participation dynamics such as comments, likes, flags etc. &lt;br&gt;Of course, it would also depend on the application of something like this and the culture of the 'organization' implementing it. Some might want just a small subset of the official team participating, where others may choose to very nearly open it to all but those who the community actively rejects. This is where selecting the initial use case will be particularly important as they complexity/possibilities can quickly complicate things.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Tue, 26 Jun 2012 17:47:40 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-567934048</link><description>&lt;p&gt;What about letting people from outside the organization contribute too?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">aweissman</dc:creator><pubDate>Tue, 26 Jun 2012 17:40:53 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-567729540</link><description>&lt;p&gt;1. My initial instinct is that this would work best for new teams or groups and those of smaller e.g. &amp;lt;20 size.  I think it could scale but the magic in that will be how is content curated and surfaced in a way that strengthens the community and conversation rather than drowning it in noise. &lt;br&gt;2. As for write privileges, I see that about about selecting people as contributors (e.g. founders/employees/members) and then authorizing some specific sources (e.g. blog and twitter).  To limit/focus content perhaps it would only pull posts/tweets with #clogxyz tags. &lt;br&gt;3. Probably both :-) But I'm not sure it's 'forcing' a single aggregator but rather introducing an 'aggregator' that serves to represent the company (replacing conventional website) &lt;br&gt;4. For filtering - see 1 - for discussion, dunno.&lt;/p&gt;&lt;p&gt;5. What are you thinking of here? Had been thinking yet of discovery dimension.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Tue, 26 Jun 2012 12:59:27 -0000</pubDate></item><item><title>Re: Clog with me! The future of websites.</title><link>http://lewwwk.com/post7512#comment-567720216</link><description>&lt;p&gt;Interesting. Lots of angles and questions:&lt;/p&gt;&lt;p&gt;– what's the right size team for this? Does it work for a team of 10? 100? 1000?&lt;br&gt;– what happens when you consider write privileges&lt;br&gt;– are you fixing a problem or causing another one by forcing a single aggregator onto the team&lt;br&gt;– if you cut the discussion from the post, how do you filter for noise across the platform&lt;br&gt;– what's the discovery model for both content and people?&lt;/p&gt;&lt;p&gt;10,000 more questions. Beer and scheming. &lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Flaschner</dc:creator><pubDate>Tue, 26 Jun 2012 12:46:36 -0000</pubDate></item><item><title>Re: Your Activity is Your Currency</title><link>http://lewwwk.com/post7450#comment-280463799</link><description>&lt;p&gt;Well, ultimately, we're building this to help humanity build a better future, sooner. But that's a bit big for anyone to begin, so we're starting with something simple. If you use online tools to do what you do, this is for you. Epic helps you track and compare your activity on the web. We've heard it described "Like Mint for your life" and in the coming weeks we'll take it further… ultimately helping you accomplish more of what matters, to you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Mon, 08 Aug 2011 11:25:42 -0000</pubDate></item><item><title>Re: Your Activity is Your Currency</title><link>http://lewwwk.com/post7450#comment-280448399</link><description>&lt;p&gt;And why would I want to sign up for something like this? I don't get it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeremy Mansfield</dc:creator><pubDate>Mon, 08 Aug 2011 11:00:29 -0000</pubDate></item><item><title>Re: Your Activity is Your Currency</title><link>http://lewwwk.com/post7450#comment-233460840</link><description>&lt;p&gt;Thanks @Taylor Davidson  - glad you're already building your currency. Looking forward to seeing how you put it to use!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Thu, 23 Jun 2011 13:26:35 -0000</pubDate></item><item><title>Re: Your Activity is Your Currency</title><link>http://lewwwk.com/post7450#comment-233458596</link><description>&lt;p&gt;Already using @epichq, intrigued by the credit system.  Looking forward to seeing it in action!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Taylor Davidson</dc:creator><pubDate>Thu, 23 Jun 2011 13:24:25 -0000</pubDate></item><item><title>Re: Summit on the Future</title><link>http://lewwwk.com/post7451#comment-220040829</link><description>&lt;p&gt;That's a summit I'd attend.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Taylor Davidson</dc:creator><pubDate>Tue, 07 Jun 2011 11:30:23 -0000</pubDate></item><item><title>Re: You are a&amp;#8230;</title><link>http://lewwwk.com/post7423#comment-155384555</link><description>&lt;p&gt;Agree. @flashlight's and this thread's comments on context are important considerations.&lt;/p&gt;&lt;p&gt;We used 'Guest' in the restaurant industry because it drew on the context of "welcoming" and "special event".&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Denis Carr</dc:creator><pubDate>Thu, 24 Feb 2011 11:14:25 -0000</pubDate></item><item><title>Re: You are a&amp;#8230;</title><link>http://lewwwk.com/post7423#comment-155327533</link><description>&lt;p&gt;I'm not sure, but it does have a better connotation than member in that it implies more action/agency.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Thu, 24 Feb 2011 09:06:24 -0000</pubDate></item><item><title>Re: You are a&amp;#8230;</title><link>http://lewwwk.com/post7423#comment-155022988</link><description>&lt;p&gt;Is "participant" too formal? It does describe people who choose to participate in something. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jerry Michalski</dc:creator><pubDate>Wed, 23 Feb 2011 17:15:57 -0000</pubDate></item><item><title>Re: You are a&amp;#8230;</title><link>http://lewwwk.com/post7423#comment-154854558</link><description>&lt;p&gt;Well said.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Wed, 23 Feb 2011 14:37:37 -0000</pubDate></item><item><title>Re: You are a&amp;#8230;</title><link>http://lewwwk.com/post7423#comment-154839680</link><description>&lt;p&gt;Member means you got picked or met some criteria so it can sound&lt;br&gt;disingenuous unless you're really are member.  I'm a member of&lt;br&gt;the Olympic team sounds cool but I'm a member of my credit card company&lt;br&gt;sounds lame.&lt;/p&gt;&lt;p&gt;David R Verchere&lt;br&gt;CEO&lt;br&gt;PostHelpers&lt;br&gt;&lt;a href="http://apps.facebook.com/posthelpers" rel="nofollow noopener" target="_blank" title="apps.facebook.com/posthelpers"&gt;apps.facebook.com/posthelpers&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Fisher</dc:creator><pubDate>Wed, 23 Feb 2011 14:23:59 -0000</pubDate></item><item><title>Re: You are a&amp;#8230;</title><link>http://lewwwk.com/post7423#comment-154816609</link><description>&lt;p&gt;It is language UI for sure. @flashlight's breakdown was excellent. For &lt;a href="http://epic.io" rel="nofollow noopener" target="_blank" title="epic.io"&gt;epic.io&lt;/a&gt; I'm considering 'member' and 'user'. The interesting difference to me is that member feels more like the person is part of the 'epic' community while user clarifies the distinctions that &lt;a href="http://epic.io" rel="nofollow noopener" target="_blank" title="epic.io"&gt;epic.io&lt;/a&gt; is a tool that they are using. The former feels like it's more about the service while the 'user' ironicly communicates that its more about the person.&lt;/p&gt;&lt;p&gt;All very interesting. &lt;br&gt;... sent while mobile.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Wed, 23 Feb 2011 13:59:05 -0000</pubDate></item></channel></rss>