<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for mattgillooly</title><link>http://disqus.com/by/mattgillooly/</link><description></description><atom:link href="http://disqus.com/mattgillooly/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 06 May 2009 02:16:02 -0000</lastBuildDate><item><title>Re: David Berube &amp;raquo; Future of Local News</title><link>http://blog.daveberube.com/2009/05/general/future-of-local-news/#comment-9048380</link><description>&lt;p&gt;Sorry, but I have to disagree.  Paid subscriptions for online news content have typically failed.  The exception is in financial news, because those subscribers have an incentive not to share that content freely.  PT could try it, but I suspect they'd still lose money on the project.&lt;/p&gt;&lt;p&gt;I think there's a certain class of news that will be served well by UGC, but since that's precisely the kind of news that an abundance of people are willing to write up for free, I'm extremely skeptical of any play to make money off of it.  Aggregation can be handy, but once you throw enough ads up to make money, people will take their UGC elsewhere, and we'll just keep coming back to blogs and RSS feeds.  The only money is going to be in news that no one wants to/is able to work on for free.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Gillooly</dc:creator><pubDate>Wed, 06 May 2009 02:16:02 -0000</pubDate></item><item><title>Re: David Berube &amp;raquo; Future of Local News</title><link>http://blog.daveberube.com/2009/05/general/future-of-local-news/#comment-9047644</link><description>&lt;p&gt;I think you're right that newspapers which don't adapt will eventually be in big trouble, but I disagree about the order in which things will happen.  As long as there's a demand in Pawtucket for local news and no one else providing it, the Pawtucket Times is relatively safe.  It's only after someone finds an answer to your question ("What comes next?") that the PT is in real trouble.&lt;/p&gt;&lt;p&gt;It's pretty clear that the old newspaper model is too bloated to keep working for long, and the fact that the newspapers haven't yet figured out what to do with themselves suggests that no single model will replace the entire news industry.  Instead, the information that we've come to expect from newspapers will likely come from a variety of sources.  Amateur bloggers will be sufficient for some of it, while other stories will always need professional journalism and therefore some kind of a business model.  Check out &lt;a href="http://spot.us" rel="nofollow noopener" target="_blank" title="http://spot.us"&gt;http://spot.us&lt;/a&gt; (funded by the Knight Foundation, who also funded EveryBlock) for one example of how that might work out without the bloat of a newspaper.&lt;/p&gt;&lt;p&gt;The fact that we don't currently know what's next means that perhaps the PT is smart not to abandon the only model that's ever made them any money.  How much money can they make off their web traffic?  Probably not a ton.  The future may not even have a spot for organizations that resemble the Pawtucket Times, so why not make some money selling old-fashioned papers while they still can?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Gillooly</dc:creator><pubDate>Wed, 06 May 2009 01:12:36 -0000</pubDate></item><item><title>Re: The Exciter - Why You Should Deploy Your Next Application on Ruby 1.9 and a Rant in General</title><link>http://theexciter.com/articles/why-you-should-deploy-your-next-application-on-ruby-1.html#comment-6718700</link><description>&lt;p&gt;I see the problem a little differently.  Maybe the ideas of repository hosting and authority over a project have become a little too tangled up in our heads, and some separation of concerns is in order.  I don't see any reason why a RubyForge-like site can't serve as a hub for project status and "ownership" while remaining totally agnostic about where you host the repo.   The project's home can remain stable while pointing to whatever fork-du-jour the community/project managers are keen on at the time.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Gillooly</dc:creator><pubDate>Fri, 27 Feb 2009 23:32:31 -0000</pubDate></item><item><title>Re: FuseCal Beta Release</title><link>http://localhost:8888/?p=3#comment-4538614</link><description>&lt;p&gt;test, buddy&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Gillooly</dc:creator><pubDate>Sat, 20 Dec 2008 03:59:21 -0000</pubDate></item><item><title>Re: FuseCal Beta Release</title><link>http://localhost:8888/?p=3#comment-4538617</link><description>&lt;p&gt;yup&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Gillooly</dc:creator><pubDate>Sat, 20 Dec 2008 03:59:01 -0000</pubDate></item><item><title>Re: FuseCal: Fuse All Your Calendars in One Place</title><link>http://www.rev2.org/2008/03/27/fusecal-fuse-all-your-calendars-in-one-place/#comment-270903</link><description>&lt;p&gt;Thanks a lot, Sid!  This is probably one of the most accurate and thorough writeups I've seen so far about what FuseCal is all about.&lt;/p&gt;&lt;p&gt;We'd love to hear your feedback (there's a form on &lt;a href="http://fusecal.com" rel="nofollow noopener" target="_blank" title="fusecal.com"&gt;fusecal.com&lt;/a&gt;) about what we can do to make FuseCal more useful for you.  Let us know what you think!&lt;/p&gt;&lt;p&gt;cheers,&lt;br&gt;Matt Gillooly&lt;br&gt;Product Manager, &lt;a href="http://FuseCal.com" rel="nofollow noopener" target="_blank" title="FuseCal.com"&gt;FuseCal.com&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt Gillooly</dc:creator><pubDate>Thu, 27 Mar 2008 12:59:59 -0000</pubDate></item></channel></rss>