In late March when we shipped Little Outliner, Mathew Ingram wrote a very nice piece about our startup in GigaOm. But the title was problematic. It said: "Watch out, internet: Dave Winer is back in the business of making blogging tools." I groaned. We had just shipped an outliner, a small one, and there were no blogging tools anywhere in sight. But somehow, looking at my outliner, Mathew saw blogging. I should have listened more carefully. Instead I wrote a post that claimed, boldly: "I'm not making blogging tools." I put a smiley after it to show there were no hard feelings. I wanted to get on the record quickly and clearly. Don't think this is a blogging tool. It's an outliner.

Then in April we shipped a much more ambitious product, Fargo -- whose name relative to Little Outliner was supposed to be kind of a pun. Little Outliner is little, but Fargo will Go Far(ther). How far it will go has not yet been revealed, but we're hard at work on a publishing platform that Fargo connects to. At the time I didn't think that the publishing side could or should be viewed as blogging. But now, as it's evolved, and I've met our first users (back in March we didn't know who they were), I can see that Mathew was right. We are in the business of making blogging tools. Did I know it at the time when I said we weren't? I didn't. Nothing changed except the product and the users. If they are changing, you have to go with them. You can't fight City Hall, and if your users say it's blogging, and a respected analyst says it's blogging -- it's blogging. ;-)

Another thing happened while all our development was going on -- Tumblr, a product which I have deep respect for, sold to Yahoo. What I admire most about Tumblr, as a product designer, is its templating system. It's a descendent of the ones we developed at UserLand in Manila and Radio, which in turn were descended from the templates used by designers in the desktop publishing era using Quark and Pagemaker.

Templating is at the core of blogging. The reach of a blogging system is determined by the richness and flexibility of its templating. And here's an interesting fact. If the content has structure, as outlines do, you can do a lot more for the user with templates. CSS is a nice beginning, but the outlines give you power flat text designers and authors can only dream of.

We can, and are, doing more. Tumblr has now been around for a long time. Our earlier work has been around even longer. It's time for a fresh look at tools for designers, writers and programmers, centered around web content. If people want to think of that as blogging, who am I to argue with them.

So I won't. :-)

PS: A good content tool should also be a workgroup collaboration tool, as Fargo is.

 5/25/2013; 10:27:52 AM.

There's a false argument about the national debt that goes like this.

We can't leave a huge debt for future generations to pay off.

It's false for a couple of reasons:

But even if you don't buy the math of it, consider the emotional argument. You're worried about future generations, but what about our debt to past generations that sacrificed for us so we could have good education, homes, health care, transport? Aren't we betraying them if we let the infrastructure they built for us crumble and disappear?

When do we think about our ancestors and what we owe them?

Of course that's what Memorial Day is for. To remember the people who came before, especially those who sacrificed so we could be propserous and healthy. We invest in our country because the only other option is to see the country crumble. And we invest because we hope for a better future for those who come next.

 5/25/2013; 9:43:14 AM.

You know how they have all these methods of development, agile, etc.

My method is whitewashing fences.

I'm Tom Sawyer and I have a great fence and some paint.

It's a beautiful day and I'm having the time of my life whitewashing this fence.

My friends want to know if they can do it too.

I don't know! I'm having so much fun...

I'll have to get back to you.

 5/24/2013; 9:51:57 AM.

The other day I suggested perhaps adding blocking to HN, mostly as a way of starting a discussion. And it led to some interesting ideas that I think are worth considering.

A lot of the personal attacks come from accounts created to post one message. The user has never commented before, or submitted a link to the site.

So here are some ideas:

What made me think of this idea was yet another one-off flame from a user named redmarx who created the account 13 hours ago, the exact same time his post was created. Now what do you think is going on there? A courageous whistle-blower, or a coward who doesn't want to own his or her own words? :-)

 5/23/2013; 11:59:33 AM.

Our users love icons.

I guess most users do, but people who write in outliners need a little more graphic relief because our work is totally text and structure. Adding a bit of graphics is like adding spice to a sauce. And they're fun!

We're lucky because Font Awesome is such a great collection of icons. And it keeps getting better. If you're developing web apps, you're nuts if you aren't using Font Awesome. Seriously.

Anyway, until Fargo 0.65 it was a lot of work to add an icon to an outline. What changed is that we created an icon chooser dialog that makes it easy and fun.

If you're using Fargo, you can try it out with the Icon Chooser command in the Outliner menu.

If you're not using Fargo, here's a little demo app you can try. It doesn't do much but allow you to browse the icons. When you click on one, an alert pops up saying which icon you chose.

If you're a programmer, the code is free to use under the GPL. That means any improvements you make must also be licensed under the GPL. And it would be nice if you said where you got it. :-)

https://github.com/scripting/Icon-Chooser

Enjoy!

 5/21/2013; 10:54:22 AM.

Yesterday someone at Hacker News thought to point to my piece about Marissa Mayer. It was a story I wrote in about 15 minutes. The point was at the end of the piece. As a preamble, I told a couple of stories from my personal experience. I figured it would get a few comments, maybe a couple of thousand reads, and that would be that. But the torrent of abuse on Hacker News was something that I haven't seen in a long time.

One of the main reasons it doesn't work is that people don't ask questions to clarify. They jump to conclusions, some of which are very wrong. For example, they assumed I was the only person who was concerned about the BlogThis! button. Not true.

They assumed that I was being "egotistical" for thinking that Google ever cared what I thought, and arrogant that I think they should care what I think now. It's a fact that at one point, early-on, Google did care. Their chief PR person was from Apple, Cindy McCaffrey, a class act in every way. She would routinely send emails to me and Doc Searls asking our opinions. Whether anyone else there cared, I don't know. But I was invited to a meeting with engineers to talk about blogging, RSS and XML-RPC at one point. I can't imagine why they would ask me to tell them what I think if they didn't care. I suppose it might have been a big conspiracy, like Mission Impossible. Hey I wouldn't put it past some of the trolls on Hacker News to argue that. :-)

On the other hand, I don't take it personally that Google doesn't care what I think these days, partially because I don't think they care what anyone thinks. That's a long story all by itself.

Now, we could have had an interesting discussion on HN if people would have asked questions for clarification instead of just piling on the abuse based on their impressions. That's taking them at face-value, assuming they really want an informative discussion. Probably the trolls in the thread, and their upvoters, wanted nothing like that.

There were some other ludicrous statements. Did any of them know that I started a new company in December, and we shipped our first two products in March and April? They said I thought JavaScript was a bad language. How funny, because I'm writing almost all my code these days in JavaScript. They say I'm old and out of date. Funny. They're the ones who are out of date! :-)

And if you say someone's old as a way of hurting them, the joke will eventually come back to hurt you. As one of the characters of Citizen Kane, Bernstein, said so eloquently, old age is the one disease you don't look forward to being cured of. It comes to everyone. I was young once. Now I'm middle-aged. Truth. And the sun rises in the east and sets in the west. I don't see what it has to do with the point of my blog post.

Now I think there's a solution to letting the assholes control the conversation...

As discourse has moved to Twitter, its big contribution has been to push aside the abuse that's common with discussion boards and mail lists. A very simple feature in Twitter, the block command, enforces decorum, by empowering the listener to turn you off if they find you offensive. People learn that if they say abusive things, they don't have to listen. The only people I listen to on Twitter are those who can make a point without getting personal. I learn from disagreement, but I can't stand people who use their freedom to speak as a way of hurting others.

Then I wondered -- if it works so well for Twitter -- why can't sites block Hacker News if the abuse gets too heavy? After yesterday's experience I probably would do it. I like the flow they deliver, but I hate the abuse.

So I have a suggestion for Paul Graham, the guy who runs Hacker News. Give sites the option of blocking links from Hacker News. I honestly don't care what the HN trolls, and the people who upvote them, supposedly "think" about me. None of it is based on anything real. A lot of it is anonymous. Sometimes people create accounts just for the purpose of dropping a big smelly turd in the middle of a discussion.

Let's learn a trick from Twitter, and cut off the trolls at the source.

PS: I subscribe to the Hacker News feed, which does not include comments. It's very useful stuff. So the links themselves are good.

 5/21/2013; 8:34:39 AM.

I went to dinner last night with the two Scobles, Robert and Patrick.

Robert is famous for the picture of him wearing a Google Glass while in the shower.

Last night, he was wearing the glasses most of the dinner, but took them off. He said I should try them. I did.

What you get is a sequence of cards, with recent tweets, emails, Google Now type stuff. You scroll through them by swiping on the stem of the glasses. It doesn't take any time to get the hang of it.

You can create tweets with voice. It happened so quickly I barely knew I had done it. I created a tweet on Scoble's account. It contained an expletive which they conveniently ***'ed out for me.

It was nice. However I don't feel any lust for having one of my own. I carry an Android phone and an iPad with me most places. The UI of Google Glass, while interesting, doesn't seem to be an improvement over the phone interface.

But it's early days. Maybe someone will figure this out. The Apple II wasn't much use before Visicalc, for example. The Mac came with a couple of demo apps, but didn't blossom until there were 20 or 30 useful pieces of software for it (it needed more of an ecosystem than an individual killer app).

 5/20/2013; 12:16:09 PM.

It was 2003. Google had just bought Blogger. On the acquisition, they said they wouldn't do anything to tilt the table in favor of Blogger. There was concern in the wider blogging community that Google might use its power in search to give people an incentive to use Blogger over other publishing platforms. They said this would never happen.

But a few weeks after the deal they broke the promise. They added a BlogThis! button to Google Toolbar. It only worked with Blogger. It would have been a simple matter to make it work with any blogging tool. But they didn't see why they should do that.

Back then Google cared a little about what I thought, so the result was a conference call between me and an exec at Google, Marissa Mayer. I was driving cross-country from California to Boston, so I stopped in Utah, in the parking lot of a 7-11 just east of Salt Lake City, and we had the call.

All I remember of it was there came a point in the conversation when Mayer had had enough. She just got up and left. I think the people remaining in the conference room were a little embarassed. Google didn't do anything to change the BlogThis! button.

All this is to say that the promises execs make on acquisitions are meaningless. They own the thing, they will do what they want to with it. It doesn't matter how many nice sounds Mayer makes on the deal. At the core she cares not one bit what the users of Tumblr think. She's saying what she needs to say to make the deal happen. To avoid a PR crisis on Day One. To make the team at Tumblr feel like their work has value to the new owners. That somehow this acquisition isn't actually an acquisition.

I have some intuition about this myself, because I sold a company. We were bought because we had a presence in the Mac market, which was highly coveted at the time. I negotiated for myself a role as the "Chief architect of Symantec's Mac strategy." A few weeks after the deal I made a presentation to the exec staff about what our Mac strategy would be. Only one person showed up, the president of the company, Gordon Eubanks. He watched a couple of slides and thanked me for the input. I asked What about my chief architect role? He told me that was something they told me to get me to do the deal.

He left the room. What was I going to do? What could I do? Nothing, that's what. :-)

Moral of the story: When you sell your company, no matter what promises were made, you sold it. It's theirs now. They will do what they want to with it. Promises don't matter.

 5/20/2013; 9:54:46 AM.

It looks like Yahoo is buying Tumblr.

I feel some sense of pride here because Tumblr is a descendent of products I made, Manila and Radio, that laid the groundwork for products like theirs. David Karp and Marco Arment will get rich (or richer) and that's cool because they're smart people who worked hard and made something real happened. I am in awe of systems that handle as much content as Tumblr. Their users should be in awe as well, imho.

Yet we still don't have a whole system for product development in this industry.

The rewards for digging the first holes that become the foundations for great systems like Tumblr and WordPress are minimal, if they exist at all. When you try to talk with investors about kicking back a bit of their proceeds in ventures that in addition providing good ROI, also create open formats and protocols that industries can be built on, you get blank stares. As if they don't understand. Of course they do understand, it's just easier to pretend they don't.

They profit from this work, but like the grasshopper in the famous fable, they aren't willing to participate in the investment that made the profit possible. Too bad, because if they did -- I think their companies would be stronger as a result. The better the foundation, the bigger the building you can make, and the more efficient it is to keep it running. Had we had a longer easier runway for Radio and Manila, Tumblr might have gone further on less investment.

Anyway, that's a small point right now. Get out the champagne and celebrate, because some of the good guys won. (Or at least appear to have, we'll find out for sure tomorrow.)

 5/19/2013; 1:55:21 PM.

I've been wondering lately why there has been so little useful stuff written about Fargo. It's an interesting product from a lot of angles.

So I've been asking questions, and this is what I've figured out.

1. There are great places to go for reviews of Mac products.

2. If you want to know about software that's sold on Amazon, you'll find lots of reviews from users. I understand that well because I depend on reviews for almost everything I buy on Amazon.

3. For IOS and Android apps there are the stores, which have reviews.

But there is no place, that I know for Dropbox users to find out what the great apps are and what users are doing with them.

Probably because Dropbox as a platform is so new?

It's like a fog here, because we're all operating with so little information.

So let's solove the problem. I started a mail list today for users of Dropbox who want to be in the loop on all kinds of new products. Obviously it's a chicken and egg thing. If enough users show up, the developers will follow, and vice versa.

https://groups.google.com/forum/dropbox-users

We'll probably need some rules of conduct at some point, or move to a blog or blogs, because mail lists always tend to flame out if there's no moderation, but for now, it's a good way for people to meet, if there's enough interest.

As a vendor of a Dropbox-based product, I can tell you I am highly motivated to see this work. Most people who use Dropbox, some of whom would love a great outliner, don't know my product exists. I want desperately to fix that. :-)

 5/18/2013; 3:12:17 PM.

Last night watching the NBA on TNT, new commercials for the YouTube comedy fest. The production was distinctly not YouTube. It was professional in every way. Nothing amateur about it. Google is now MSM. All that talk about Burning Man is sleight of hand. That guy has as much in common with you and me as Rupert Murdoch does.

It's not just Google, Twitter is also MSM. Facebook? Eh. Their presence on TV is mostly in URLs at the bottom of other peoples' ads. Their commercials are amateurish, awful imitations of other tech company commercials. Not to say they're the only ones with awful commercials, but theirs are awful in their amateurishness.

A blog post on Forbes suggests that Google is going to bring RSS back in a MSM-type way. You'll be able to follow Blogger blogs in Google Plus. Maybe they'll make a deal with Automattic and Tumblr to make it possible to follow their blogs too. Me and you? Well we can be followed, but only if we use one of the silos. We have to be locked in someone's trunk to participate.

The web is going to play the same role to all this crazy locked up stuff that it played to MSM in the 90s. We're going to be the oddballs. The ones with amateurish sites. We'll be the artisans, the local farmers of ideas. The ones that lack polish but speak from our experience. We'll do what Bulworth so famously did. I don't have access, and I don't want it. I'd much prefer to hear from other people who don't have access and don't want it.

The web keeps moving. If your attention has shifted and you can't see that, that's not the same thing as the web being lost. Maybe you got lost? :-)

 5/17/2013; 11:32:44 AM.

Over on our Community Feed for Fargo users, a conversation started about how people are loving writing code with Fargo. This really surprised me, because we haven't done much to encourage this. There's a simple feature in the app that allows you to run a single-line of JavaScript code. This means you can call any routine that's in Fargo, or in Bootstrap, jQuery or in the core JavaScript libraries.

We have it in there because it's useful for one-liners, for debugging the app. It's not meant to make it a programming environment. But some people seem to love it. I wanted to know why, so I asked. And what came back from Dave Wynn, a user who I had not met until this exchange, was a simple and eloquent explanation of why Fargo is a great product (I happen to agree with him of course, but then it's partly my creation). Here's what he said, of course in an outline (Fargo is an outliner).

It's as cross platform as it gets

It's file backed

I can inspect it much more easily than other software

Feedback is immediate

 5/16/2013; 11:55:16 AM.

One of our fetishes at Small Picture is getting cool stuff working with no servers.

You can get a lot done. For example -- Little Outliner. There's only one function it relies on a server for, the importing of OPML. And if you think about it, it's ridiculous that that function has to be done through a server. The code is running in a browser, which is perfectly suited to get a file over the Internet.

Many of the limits of the 2013 web are accidents of history. Someone at some time thought an operation was too powerful, that it could be abused, so they made it illegal. But they didn't close off the ability to call a server to do it for us, so we effectively can do anything we need to do.

A great example of that is the way Dropbox allows Fargo to save to the local file system.

This is something we're not supposed to be able to do. But we're doing it anyway. And nothing is breaking as far as I can tell. We're inside a very simple easy to understand sandbox, a sub-folder of the Dropbox folder.

And in addition to being able to write to the local file system, we get cross-device synchronization for free. That's a great deal. (Understatement.)

All this means things are shifting pretty radically. Who is the operating system vendor if my files are equally accessible on Windows, Mac, Android, Linux, IOS, etc? Dropbox is, that's who.

A couple of years ago I asked the guys at Automattic to add a feature to their API that would allow me to store a small XML file along with a blog post. Had they done this, and if we had followed where it would logically have led, today they would have the equivalent of Dropbox, along with content management. You'd be able to publish just by saving a file.

Today you have to figure Dropbox sees this opportunity. And that they will, eventually, navigate to roughly where WordPress is.

The server is moving. A fair amount of what used to be "up there" is now in JavaScript, in the browser. The network services are doing what only they can do, provide global access to published information. And unfortunately due to history, they are also acting as pointless proxies for things a browser app should be able to do for itself.

 5/15/2013; 11:14:23 AM.

My linkblogging tool, Radio2, has a connection with Twitter. You can establish a link between your feed and Twitter so that every item in your feed is also posted to Twitter.

Here's a screen shot. To create the connection you click on the blue bird. That starts an OAuth conversation where the user gives Radio2 permission to post to his or her Twitter account.

I've been hearing, peripherally, that some part of the old Twitter API is about to be turned off, or maybe has already been turned off. I can't pay full attention because it's a small feature, used by just a few people, and I have my attention elsewhere.

Late last night I tried clicking on the blue bird, and sure enough there appears to be some breakage. Twitter complains that there is "no request token for this page." Perhaps they changed something in their OAuth implementation?

I should investigate.

If you have any clues, please post a comment.

Thanks! :-)

 5/15/2013; 9:26:34 AM.

I did a house-cleaning on my river server on May 9. At that time some of the rivers stopped updating. Mostly the ones that no longer have tabs in the user interface because either I personally didn't have enough interest in the subject and not many other people were reading them. I didn't feel like paying for machine resources if only one or two people were reading the flow, or if there were only one or two new items a week.

One of the rivers that I turned off is the Apple river. I use a Mac, several in fact. And I have an iPad and an iPod. I am a long-time Apple shareholder. I am an Apple user, but I am not a dedicated member of the Apple community like some people I respect are. For example, Brent Simmons, Marco Arment, John Gruber, Daniel Jalkut or Michael Gartenberg. I see a tremendous value in the river, if only someone rooted in the community would take an interest. It's also a potential money-maker, imho.

It's really time for communities to spread out and become more inclusive. With a well-curated river, the Mac community can explore more niches, and grow in some interesting ways, perhaps.

So I offer to keep running the river...

1. If someone with a site with serious flow offers to display the river on their site, linked to from their home page.

2. It can be rendered in their template.

3. I will provide support on the technical process for getting the river to display well in another site. It involves using jQuery, something I'm not an expert in. But I got it to work here, so I presume we can get it working anywhere. If we need help I know where to ask for it. ;-)

4. The curator has to have the ability to edit an OPML subscription list, and make it available at a public HTTP address. Fargo, my outliner, does this very nicely, in conjunction with Dropbox. But you can use any tool you like.

5. The person doing the curating and the person doing the display can be different people, if you like.

6. Curating here means choosing feeds, not stories. We're looking for good sources of Mac news and opinion. But it's up to those sources to decide what goes in the river. It's just an RSS aggregator on the back-end.

7. All I want in return is a link from the page back to a page that shows people how to set up their own rivers, which I will write. It won't be hype-ish. I may ask for a little money for the software.

I think the Apple river is a great place to start. Now I'm looking for one of the leaders in the Mac blogging world to step up and work with me on this. I may not be a Mac insider these days, but I go back to the beginning. I was onstage at the Mac rollout in 1984. I had an ad in the first issue of MacWorld. My product won the top Eddy in 1986. I used to go to WWDC back when it was in San Jose. I even spoke at WWDC one year. Ask Guy Kawasaki. ;-)

Let's do this. I think it'll turn out to be an important step in the growth of the Mac blogosphere.

 5/11/2013; 7:16:00 PM.

This question came up in the Community Feed, which you can read in Fargo, by choosing the Community Feed command from the Docs menu. Or you can read it in the Small Picture Reader if you don't use Fargo. I wrote my answer there, but thought it would be interesting to also post it here. No I didn't use the fancy Blogging 2.0 protocol I described in an earlier post. Soooon!

Well of course it would be nice to have everything, if there were no cost.

It would take time to write the code and keep it running. It would be worth doing if there would be a lot of people using it. But right now the Community Feed a new feature. We're still at the point where we're introducing ourselves. If that's all it does it will have been worth it.

I'm an investor in software, and I have to make decisions as any investor would. I can't buy everything. And right now there are other projects that I think need more attention.

Also, and this is a key point, this is not something you need Kyle or me to do. The OPML feed is public. If you want to write the code to convert it to an RSS feed, you can do it.

But OPML feeds? Ahhh that's easy. Since I'm writing both ends I can make it work. And if I want to change things based on what I learn, I can do that too. That's why the early days on anything are important. And why you should go slowly enough so you can feed back what you learn into the protocol.

Anyway you see these questions sound simple, but when you actually start writing the code, they can become complex.

Bottom-line: My bet is that no one would use an RSS feed of this content. That makes it a bad investment. I've been wrong before, btw.

 5/10/2013; 11:33:03 PM.

Jay Rosen wrote me last week to say that the River of News concept had reached a tipping point. That led me to publish a brief email exchange with Brent Simmons about what a river is, from a design standpoint. But there's more to rivers than their form, there are a couple of other very important ways to look at them:

 5/10/2013; 12:07:48 PM.

I wrote a piece in August 2012 which I posted on Medium entitled We Could Make History, in which I proposed that we get together and create a new API to connect authoring tools to publishing environments.

At the time I thought it was a long shot, but worth putting it out there in case anyone was listening at Medium, or elsewhere. That's why I made it openly. And why I put the post on Medium.

Today I'm writing this post on my own blogging platform, which is more or less some scaffolding I put together to hook my outliner up to the web, so I could publish, before we had something real that others could use.

Now I can make a more concrete proposal because Fargo is visible, people can better imagine what I'm talking about.

1. I don't like the idea of writing something to have it visible in only one place.

2. Sometimes I find that a comment I wrote in one place is really a blog post, but why should it stop being a comment?

3. Copy/paste is an awful synch protocol. It's 2013. We can do better! In fact we live in a time of great progress in sychronization, thanks to Dropbox. Publishing should make the leap into the future as well.

4. Software now runs in the browser, written in JavaScript. It's indistinguishable from desktop software. So any protocol we come up with must work equally well with JS apps running in the browser.

5. Meanwhile there are a number of projects underway to bring blogging up to date. But they're doing it without APIs and without feeds. Why? That's not really progress.

6. We were able to hook up Fargo to WordPress, largely to show what's possible. But we had to set up a proxy server so that our JS app running in the browser could call their server. This is a waste of resources and does not scale.

7. We will have a for-real CMS running on a server. It will do things that are new, that none of the other publishing platforms do. But there will still be things they do that we don't. APIs are needed. But I'd prefer to work with others to come up with the API, rather than do both ends myself. If we do it that way we get there sooner, better.

8. I'm pretty sure there will be APIs here. But I'd rather there just be one. We had that worked out pretty well in Blogging 1.0. But let's do it even better in 2.0.

9. Who wants to go first? :-)

 5/9/2013; 2:10:12 PM.

More about Fargo 0.59.

 5/8/2013; 3:20:52 PM.

Levy: "To really think big, you can't be at a big company."

I was amazed that these words came from Steven Levy, former Newsweek tech reporter, and late of Wired. He's spent a career supporting the myth not just that big ideas can come from big companies, but that they only come from big companies.

He was paraphrasing Evan Williams, founder of Twitter and Blogger. But it's still an amazing transformation.

Now, I don't expect the press to all of a sudden start reporting on where big ideas actually come from. But it's nice to be able to point to the truth, just once, from such a source.

BTW, we're thinking very big at Small Picture. :-)

 5/7/2013; 5:54:04 PM.

On April 11, Brent Simmons sent an email, included below. My words are indented beneath his in italic.

I like the river of news style of feed reading, despite having once written an RSS reader that doesn't use that style.

But I'm not actually 100% sure what the technical definition is. I'm not trying to be obtuse about this -- I want to be sure I understand.

I think it's something like this, but I'm not sure which parts are optional, and I might be missing things.

1. It presents a list of articles from multiple feeds in a scrollable list.

2. There might be multiple scrollable lists -- tabs of some kind.

3. Items in the list are sorted in reverse-chronological order by arrival date (date the feed scanner saw the item) rather than by pubDate. (True?)

4. Items are presented with title, link, and an excerpt. The excerpt should be just long enough to be meaningful (around 280 characters).

5. It handles edited items by ____? (I don't know. Does it show them again?)

6. There is no notion of read/unread whatsoever, and thus no unread counts.

7. There is no notion of starred (or flagged, or saved) items whatsoever. (Users can blog, send to a read-it-later service, etc. as they normally would for any web page.)

8. A river of news feed scanner outputs river.js data. (Is this optional? Could it be RSS?)

9. Do river-of-news readers have to be web pages? Could an iOS or Mac app qualify, if it met all the criteria?

 5/7/2013; 12:49:25 PM.

Michael Wolff comments on the job ad that Twitter is running, looking for a manager of news.

He suggests existing news execs, and that's probably the kind of person Twitter is looking for for this job.

It's a head-fake. This guy is a figure-head. He or she will be working with media companies, speaking at conferences, talking about how Twitter is helping media companies succeed in the age of realtime Internet-delivered news. He or she is a feel-good ambassador to the news industry. A person handing out complementary samples of pasta and baked goods while the real action is elsewhere.

The job is a bedtime story. News will be as it always was, with familiar faces and jobs, just with a new delivery system.

Meanwhile, the news system of the future is booting up all around Twitter, which is and always has been a coral reef. They need a new shipwreck to build around, and this time the sunken ship is the remains of the news industry.

Even at this late hour, I have a recommendation to any player in the news industry.

1. Create a river of news and put it on your home page.

2. Include all the news from your own organization, but include news from bloggers in your community.

3. Include the feeds of your competitors.

4. Deliver the best news product you can with today's technology. You can link from the river to stuff behind your paywall, if you must, but the river itself must be freely accessible. Think of it as a river of ads for full-length stories.

5. No 140-char limit. Pick a higher number. There should still be a limit to the length of a synopsis. 500 characters is plenty. Most NYT synopses are much shorter than that.

6. Make nice with Twitter. You can do a head-fake too. :-)

 5/6/2013; 11:48:59 AM.

In software, mis-managed expectation can be as damning as it is in sports and politics.

For example, coming into a political debate, each side tries to portray the other as vastly superior, in every way. If you can get the expectation low enough for your guy, he or she might "win" just by showing up.

In sport, where the outcome is measured more definitely, in points on a scoreboard, you manage expectation to play with the mind of your opponent. An over-confident adversary might relax, and create openings. The Knicks almost lost to the Celtics that way.

In software, I've seen it happen over and over. I've never had to deal with too-high expectations, but my competitors have. The first time I encountered it, with competition from a much-bigger Lotus Development, I was scared. But when we survived the competition without a scratch, I learned that just because everyone thinks you're going to lose, don't necessarily make it so.

I wasn't happy to see the expectations so high for the vaporware product Diaspora. The kids behind it were too young and inexperienced to know how much work there is in creating a finished usable product. Academia, which generally doesn't have much respect for commercial development, doesn't help. The result was awful.

Coach Bill Walsh of the 49ers had this down. Before a big game he'd always pump up the skill and courage of his opponent. Why not? Maybe they'll get over-confident. Either way, if he wins, he just vanquished a superior adversary. And if they lost, he gets to shrug it off with an I-told-you-so.

In sport, politics or software, no one cares how great you think you are. What matters is what happens on the playing field. Did you win or lose? And did you do it with grace?

 5/4/2013; 7:31:13 PM.

I've had Markdown on my to-do list for a few months, and the other day, with a bit of blank space in my worklist, I decided to give it a shot.

It was amazingly easy to integrate into our JavaScript app. I just downloaded the source for Pagedown, the Markdown interpreter used by Stack Overflow. I put it into a file on our server, and included it in Fargo. Added a command to the File menu, and came up with a simple way to generate it for users. The whole thing was done in a couple of hours.

Now we need people who know Markdown and outliners to take a look at this, try it out and relatively quickly, before there's an installed base to break, figure out if there's anything special we need to do, because this is an outliner and not a straight text editor.

Here are a couple of considerations:

1. Should we generate one or two return chars at the end of every outline heading? At first we did one, then thought better and generated two, but now we're back at one. Pretty sure one is the right answer. We often think of a headline as a paragraph, but sometimes headlines are titles. Markdown views titles and paragraphs very differently.

2. Indentation. I thought at first that we should generate a tab for every level, but backed out of that idea quickly because Markdown treats tabs as very special characters. Everything deeper than level 0 would be seen as preformatted code. Not the desired outcome.

So I wonder if there have been any others who have integrated outlining and Markdown before? If so, what did they do here?

See the Fargo docs for an idea how it works from a user's standpoint.

I welcome any comments from Markdown experts (I am anything but that).

 5/4/2013; 4:43:42 PM.

A quick note about a new development with our Fargo outliner.

Fargo now has a Markdown processor baked-in. This means that a user can write a Markdown-formatted outline, and generate HTML from it, with a single command in the File menu.

Markdown and text go together, by design. Outliners are text editors, a special kind that understand structure. There is a structure to Markdown, as there is structure to HTML, but so far as we know, none of the Markdown editors have been outliners.

How the connection with outlines and Markdown will proceed is an unknown. By baking in Markdown we're asking a simple question. How does this work? We hope to hear from users and other smart people who have ideas.

This feature is available in Fargo 0.55, which is now released on the site.

Let's have fun! :-)

 5/3/2013; 4:40:18 PM.