Showing posts with label collaboration. Show all posts
Showing posts with label collaboration. Show all posts

Saturday, August 18, 2018

Random thoughts on replacing Twitter

  1. Twitter will become a blend of home shopping network, daytime TV, and tabloid news. That might be quite profitable.
  2. There is money in sane social communication, but there isn’t big money. In particular there isn’t publicly traded corporation money.
  3. With current software and hardware stacks a base social network doesn’t have to be very expensive. I suspect without video storage and without advertising it could be done for $20/user a year and perhaps less.
  4. A consortium of newspapers, foundations, and universities with some grant money is enough to develop and support a standards based solution. Remember USENET* was basically supported by universities. USENET was also an open standard.
  5. USENET didn’t have to support a billion users though. A sane social communication network will require either an ad model similar to 1980s newspapers or user fees. I like the idea of free read access for all, contribution requires subscription ($20/year), people can donate subscriptions (free pool).

And that’s all the time I have to think about this for now …

* Still around, by the way. Searchable too.

Sunday, March 18, 2018

How to build a safe and sane social network

This is how to build a safe, sane, and sustainable social network.

  1. Build it to be viable on $1/user year.
  2. Sell memberships for $25/year. Each buyer gets one user license and contributes 24 to the free pool.
  3. Donors can buy an unlimited number of free-pool memberships at $1/year apiece.
  4. Donors who give over $1000 a year get an optional sustainer badge.
  5. Anyone can join for free if there are free memberships available.

That’s about it. Essentially it’s the public radio model.

Sunday, August 28, 2016

Last days at the best of social networks: app.net (aka Alpha, ADN).

My (@johngordon) App.net services are beginning to fail - including PourOver. Post counts are gone. I still find some great discussions; the community will outlast the infrastructure.

I joined ADN/app.net Alpha in 8/2012, I’ve paid yearly since. I was a fan in 2013, still am. App.net filled the void left when Google Reader Shares died. It was better than Posterous, Tumblr or Twitter.

Four years isn’t a bad run. I’m not sure Twitter will be here in four years. On the other hand, “the Well” is 31 years old now (and funded by memberships). The Well is private, so I’ve no idea how active it is, but that’s probably a record.

There’s no obvious replacement for App.net on the horizon but I’m keeping my eyes open …

Sunday, May 22, 2016

Beyond Simplenote: I still want a graph layer (concept map) overlay for my memory augmentation notes collection

I still want a graph layer atop my notes.

Yes, I want my personal locally stored data unlocked memex. Since the passing fad of the web is now, you know, passing, maybe I’ll get one.

Maybe someone will play with this now that there’s not much point in doing another searchable memory augmentation app. Apple and Google each have their “good enough” solutions. Those solutions have scary data lock issues, but for their vendors that’s a feature, not a defect. (For the record, I’m still on Simplenote/nvAlt, despite the extremely very insanely annoying search bug in the Simplenote Mac client. [1])

The idea is as old as time. Each open data format note has a title, a body, tags, and a unique identifier. The app maintains a separate data store of noteID pairs (relationships, no directionality or additional relationship attributes necessary).  When viewing a note one sees titles of related notes. There’s a UI for viewing the graph that also treats tags as nodes [3], and a UI for editing relationships.

The key is that the individual notes remain separate files and the note-note store is plaintext/rich text as well. [2]

One day…

PS. I think this was kind of what Gopher did

- fn -

[1] My own extended memory collection has moved through DOS text files, FileMaker Pro text base, PalmOS Notes, DateBk MemoAvantGo files, Outlook Notes, Evernote, Google Notes (killed!), Toodledo Notes/Appigo Notebook,  and Simplenote/ResophNotes/NotationalVelocity/nvAlt. No wonder I’m a nut on data lock issues and distrust Cloud solutions for extended memory even as I use them. Also: Before Simplenote, Palm Notes, iOS Notes, Keep, EverNote and OneNote there was Tornado for DOS

[2] Remember when Mac Classic gave every file its own unique ID? Those were the days. How to get the unique ID for the notes is the trick for a plaintext implementation especially across platforms. With rich text one can bury the unique ID in the metadata. Unique ID could be an IP6 URI.

[3] Remember when graph data visualization was a thing? That was the early 90s I think, around the time of VRML and MCF/RDF.

See also: 

(This is started out as a tiny post but I kept finding more old material I wanted to think about …)

Friday, October 17, 2014

Blogging is definitively back - the NYT has redone their Zombie RSS page

My feeds (Feedbin/Reeder) have never gone quiet — but there’s no doubt it was getting harder to find links to feeds over the two years since Google tried to kill RSS to boost G+.

Then came signs of a turnaround. Apple very quietly added RSS reading back into Safari — after removing RSS from both Safari and Mail.app [2]. Google, fairly quietly, backed away from G+ — I don’t get any G+ social invites at all any more. More interestingly, Google blogs all became more active. Microsoft kept RSS features in IE 11. Facebook never removed RSS from Pages. Old blogs started lighting up in my feed reader. Rosenberg has started writing about a blog revival amidst disaffection with Twitter and Facebook [1]. 

All significant developments, but they pale next to the very biggest sign of them all — the New York Times has updated their RSS - Feed Page! It no longer recommends use of Google Reader! [3] The NYT has even added Topic Feeds:

Times Topics feeds collect news, reference, photos, graphics, audio and video on thousands of subjects, covering material published since 1981 … Search 10,000+ Times Topics Feeds

 Dave Winer should be a happy guy today.

[1] Not directly related, but fairly suddenly, and for no obvious reason, many of my friends and family have stopped posting on Facebook.

[2] Apple needs to update it’s RSS Feed page though — it doesn’t mention use of Safari.

[3] It does mention AOL Reader. I thought that was a bad sign, but, and this shocks me, AOL really does have a Feed Reader with its own spiffy web site: "Moving from another RSS reader? You can upload your subscriptions in standard OPML format and start reading right away!”. It even has its own friggin’ API. Turns out this was launched a year ago. It’s still in beta, but there’s an active development blog and they released an iOS app in August that has few ratings but seems well liked. Best of all, it supports OPML export as well as import. So this is a real contender.

Saturday, May 03, 2014

Thinking tools 2014 - holding steady but future unclear

Revisiting something I wrote 14 years ago reminded me of the tools I use to think about the world. Once those tools were conversation, paper diaries and notebooks — even letters. Later came email, local BBS, FidoNet [1] and Usenet [3]. In the 90s we created web pages with tools like FrontPage and “personal web servers” [2] — even precursors to what became blogs.

In the 00s we had the Golden Age of Google. My thinking tools were made by Google — Google Blogger, Google Custom Search Engine, Google Reader (RSS/Atom) and Google Reader Social. We loved Google then — before the fall.

From 1965 through 20011 my thinking tools continuously improved. Then things got rocky.

These days I still use Blogger [4]. Blogger is old but seems to be maintained, unlike Google Custom Search. I’m grateful that Daniel Jakut continues to update MarsEdit — I wish he’d use Backer to charge me some money. There are features I’d like, but most of all I’d like him to continue support.

I still rely on RSS, even as it fades from memory (but even new journalism ventures like Upshot still have feeds). Feedbin (20$/yr) is almost as good as Google Reader [6], Reeder.app is still around (but unstable), and Pinboard ($10 lifetime) has turned out to be a “good enough” de facto microblogging platform — with a bit of help from IFTTT (0$) [5].

App.net Alpha ($36/year!) [7] powered by PourOver and consumed in part through Duerig Root-Feeds has filled out the rest of the microblogging role — and replaced the intellectual feedback of Reader Social.

So as of 2014 I’ve cobbled together a set of thinking tools that are comparable to what I had in 2009. It feels shaky though. Few people under 30 know what RSS is, app.net is not growing (even Twitter is dying), and I’ve recently written about the decrepit state of Google Custom Search. Of Google’s twitter-clone, the less said the better.

I wonder what comes next? I don’t see anything yet. I’m reminded of the long fallow time between the end of Palm @2003 and the (useful) iPhone of 2009 (transition hurt). Expect turbulence.

—fn— 

[1] FidoNews was last published July 1999.

[2] FrontPage 98 was a prosumer tool; the closest equivalent today would be MarsEdit or Microsoft’s forgotten Live Writer (2009).

[3] I used to tag Usenet posts with a unique string, then search for them in DejaNews and later Google Groups. So a bit of a micro-blog.

[4] I do use WordPress on Dreamhost for my share archive.

[5] Pinboard is about $10 for lifetime use. That’s so low it worries me. There’s a $25/yr option for a full text archive for every bookmark, but I don’t need that; it would just confuse my searches. Maybe Maciej should seek Backer funding for new features?

[6] Speaking of Backer funding, I’d fund a feature that gave me in-context editing of Feedbin feed titles.

[7] App.net is by far the most expensive of the services I use, but if you visit the site the yearly subscription fee is undiscoverable. You only see the free signup, without mention of follower limitations. This bothers me

See also

Saturday, September 28, 2013

The corporate wiki I want

The modern publicly traded corporation is to data as water is to iron. It is a challenging environment for use of anything but the most corrosion-resistant materials: .doc, .ppt and .xls. It's not a good home for things like Wikis.

So we need a corrosion-resistant Wiki. This is what I think we need:

  • Minimal dependencies, maximal configuration simplicity. This probably means file based, no database dependencies.
  • No expertise for setup and operation - if you can use basic Word and files you can implement and move the Wiki in under 1 hour.
  • Rapid and perfect portability. Rapid moves, no broken links.
  • WYSIWYG (roughly) and a native syntax that works. Probably markdown.
  • Strong search API
  • Cross-platform (shudder. Does this mean Java for the environment?)
  • Low cost or open source/free. (Freemium model ok for scale)
  • Maximal link preservation (Confluence, I can't believe how readily you break external links. This is simple stuff.)
There are probably other requirements, but I only have five minutes. Those are a good start.
 
This wiki doesn't exist today, but I am certain it could be built. The next time I'm unemployed it's on my list (along with a lot of other things, alas)

See also

Sunday, May 19, 2013

Stock prices - resorting to another dumb hydraulic analogy

Stocks are overpriced again. It's probably not too much of a bubble (yet), but we continue to be significantly above "trend".

Market 85 to 2013

Whatever the heck that means. Economists no longer have rational models for stock prices, Apple's share price alone makes efficient market theory seem silly.

It is at times like this that barbers stock talking about stock picks, insider traders get arrested, deficit figures improve, and people notice that BlackRock holds 4 trillion dollars in US stocks. Yeah, trillion. Soon we'll see headlines, if Time is still around, declaring "America is back".

Inevitably, people who know nothing compare post-1995 to pre-1995 stock behavior. Around the time that IT started to transform the world, and China and India became more-or-less industrialized nations, share prices became wavy over a five year timeline ....

Wavy

Kind of like a roller coaster, which is what the last fifteen years have felt like. (Note roller coaster is "normal" to most people who read this, only old folks remember something more linear.)

We'd all love to know why this has happened, and if it's really going to go on like this for the next 30 years or so. So, in the last stage of desperation, amateurs like me resort to a hydraulic analogy.

Remember those trillions and trillions? It's as though they were a 10 liter bucket in the hands of BlackRock and the rest of us. The bucket is trying to hit the 1L mark in a 2L cylinder. It pours over the mark or under the mark. It's really hard to hit the mark. There's just too much money, and the market is too small.

We need a bigger market.

Update 5/26/13: I've been playing with this intuition, though I'm far from convinced it means anything. An obvious question is -- bigger compared to what? I think it's 'compared to the productive capacity of global economies. At this time, given the still underutilized potential of the educated populations of China and India, the potential of the post-AI era, and the unused capacity of recession-bound Europe, the global productive capacity is very large. Our public markets have grown over the past two decades, but my hunch is that this growth has been far exceeded by the world's productive capacity. Hence the need for bigger markets.

Wednesday, January 09, 2013

Why I love app.net (ADN)

I joined App.net ($5/month or $36/year) about five months ago. Although it's fundamentally a messaging infrastructure it's currently marketed as an ad-free social network.

I paid $50 at launch, and my account was extended when the cost dropped. That was money well spent; I expect to subscribe as long as they are in business. I love App.net because ...

  • It has a very robust ecosystem of tools and services including multiple Mac and iOS clients and multiple web apps. I use Wedge, Netbot, NoodleApp and Appnetizen and will soon try Felix. There are multiple integration points to my Pinboard feed, including IFTTT support. Most of my posts start with Reeder.app [1] then go to Pinboard and turn into App.net posts via IFTTT.
  • The community I interact with on app.net is exceptional. More on that below.
  • I love the mission: a public (pay) communications infrastructure and related services that I purchase. I love paying for things I use.
  • The app.net development team is delightful. I mean that literally; it's a joy to see them play and build on the platform - like @duerig's early stage Google Reader Share alternative, Patter-app rooms and private messages (EdChat) and vidcast shared video commentary.
  • 128 characters is stupid. 256 is not twice as good, it's eight times better. (Though URL characters count, so I use URL shortener services)
  • I'm 50+ and this is a relatively young community (though plenty of 40+ too). I'm old enough to enjoy that. The only young people I otherwise interact with are my kids (10-15) and their friends.
  • I have the (illusion) of helping build something good without, you know, actually having to do anything. (Hence the illusion bit.)
  • No advertising. Of course that doesn't mean no marketing; it means I choose the marketing I want)
The real hook for me, however, is the community. I follow a very smart and mutually respectful group of people. The conversation reminds me of Google Reader Shares, some of the BBS forums I joined via packet switching networks before there was public net access, but most of all it reminds me of my undergraduate conversations.
 
During my undergrad days I got to know 4 institutions, partly because I wanted to escape from the one I graduated from, partly because in Quebec everyone went to "junior college" (CEGEP) after grade 11. Whether they were elite or accessible I found great conversations everywhere.
 
There were good conversations at graduate school, medical school and residency as well (I spent a long time in school), but the undergrad conversations were the most interesting. App.net reminds me of the best of those. It is, for example, the only place I can learn from the insights of a (gasp) republican.
 
The group I follow is a pretty tough bunch. If I'm sloppy, I get called on it. I love that -- it makes my thinking better. I learn things.
 
App.net won't last forever -- nothing does. But it's a good place now; it succeeds where Twitter failed me. 
 
If you'd like a free trial let me know at jgordon@kateva.org or in comments below -- I can share 3 invites.

[1] Alas Reeder.app may have been sunset. It's very unstable on the iPhone 5. Fortunately there are alternatives I can explore.

See also:

Saturday, April 28, 2012

Microblogging 2012 - Pinboard?

Once every few days to weeks I write a short essay, from a few paragraphs to a few "pages" (remember the page?).  Every few minutes to hours I share a link and a comment from a few words to a pair of paragraphs.

Both forms of writing almost always involve links; they point to a linkable entity.

I have to call the first blogging and the second microblogging because I can't escape the b-word (is there a language in which the name is less painful?).

Whatever the format, I do the writing for same reasons. It's primarily a way for me to learn, think, and remember. I do it publicly because I have the hive-mind communicator gene-set. I want to share the ideas and things that I like.

I want to share -- but sharing has a very important side-effect. Sharing enables indexing.

My extended memory relies on Google Custom Search (oh Google, why has thou forsaken me? I forget too much without you.) Everything I share has an entry in a Custom Search Engine I use several times a day, though recently the embedded ads have become oppressive.

I do the blogging using Google Blogger. I wanted to move to WordPress, but I decided the quality and security issues of an independent WordPress site were too severe for me; I don't have the time. I'm now evaluating a paid account on WordPress.com.

The micro-blogging is a bigger problem. I used to use Google Reader Share - one of the lesser known but most beloved products of the days when Google was Anakin. Reader Share died when Google became you-know-what.

Twitter is too constraining and I don't trust Tumblr. After trying several options I settled on Pinboard because of its business model (I pay), sharing/export options, RSS support and, especially, Reeder.app and Instapaper integration. I use IFTTT to republish my Pinboard 's' stream to my Twitter stream, and I'm now experimenting with using IFTTT to repost them to an archival and indexable WordPress or Blogger repository.

The indexable bit is a Pinboard problem. Pinboard's developer does not love microblogging; he wants to have a bookmarking service. Pinboard posts are NOINDEX by design.

Pinboard has other microblogging limitations. I use tags to create routable streams of shared information. Almost all are part of my primary share stream, but some are special sub-streams for my colleagues or for my own reference and actions. Because of the way Reeder.app works many of these are single character tags. This isn't how Pinboard is supposed to work; tags are supposed to be global - not personal. I can't, for example, show only my own tags in the Pinboard UI.

Lastly Pinboard isn't as reliable as Reader Share was - though almost nothing is. Sometimes, when I post, Reeder.app hangs waiting for Pinboard to respond. (The hanging behavior is a Reeder.app design flaw).

I'd be delighted if Maciej Ceglowsk's Pinboard.in were more of a microblogging platform. I wish I could see only my own tags for example. Above all, I wish Pinboard included an option to use the Atom publishing protocol to create an indexable and persistent post on a blog. I'd double the amount I pay Maciej for that feature.

I don't hold out too much hope. Pinboard is known to geeks, but it's not a big revenue stream. In a crazy world where a small photo sharing site can be worth a billion dollars, Pinboard is almost an anachronism...

... I wrote Pinboard in the spring of 2009 as a personal project, partly out of frustration with a redesign of Delicious that I felt removed a lot of utility from the site, and partly because I had long wanted to have a bookmarking site that would archive my bookmarks...
... The service has stored about 45 million bookmarks as of January 2012, and has just over 20 thousand active users....

... Pinboard is written in PHP and Perl. The site uses MySQL for data storage, Sphinx for search, and Amazon S3 to store backups....

As a bookmarking service Pinboard is a labor of love. It probably wouldn't do better even if it were extended to be the front end to a standards-based microblogging service - but I hope Maciej will consider the option. There might be some money from current subscribers, and perhaps referral fees if Maciej recommends an optional WordPress service (ex: Dreamhost, WordPress.com).

Someday we'll get back to the original Google Reader Shares vision. It might take a while though. After Palm died we were lost in the desert for a decade before we returned to a handheld calendar, tasks, contacts and notes solution. I hope this trip will be a bit shorter.

Update 4/30/12: Maciej is exploring how Pinboard might be a better microblogging profile, and whether it would work to enable Pinboard indexing. In the meanwhile I've turned off IFTTT posting to Blogger and disabled indexing of that test blog. I'll go forward with archiving my Pinboard posts to WordPress - http://www.kateva.org/sh/.

Monday, December 12, 2011

Organizing human cognition: Lessons from CERN

There's a hierarchy in big time science schools, and physics holds the crown. (Math majors are in a different league.) Physicists are, face it, smarter than the rest of us -- and they know it.

Our only consolation is that they often work for a pittance.

So, from my perspective as a corporate ant, it's fascinating to read John Conway's description of how physicists organize their collaboration on history's biggest physics project (emphases mine)...
Making the (Higgs) Sausage | Cosmic Variance | Discover Magazine
For the past year, physicists at the LHC experiments CMS and ATLAS have been analyzing ever–increasing data samples from the huge machine. Rumors are now circulating about what the experiments might announce at next week’s presentations at CERN regarding the search for the Higgs boson.
... As you probably know, each of the two big experiments has over 3000 physicists participating, from all over the world. Many, but by no means the majority, are resident at CERN; most are at their home institutions in Europe, North America, and Asia and elsewhere.
The main thing that allows us to collaborate on a global scale like this is video conferencing. We used a system called EVO, developed at Caltech, which allows us to schedule meetings and connect to them from a laptop or desktop computer, or even dial in by phone ...the experiments have gravitated toward having meetings in the late afternoon, Europe time, which makes it early morning for people like me in California.
.., In CMS, our whole system of producing physics results has a sort of pyramidal structure. Each experiment has a number of physics analysis groups which meet a weekly or biweekly, typically, and have two “conveners” who set the agenda and run the meetings. These convener positions are typically held by senior people in the collaboration such as professors or senior lab scientists, for two years at a stretch, one convener changing out each year. They report to an overall physics coordinator and his or her deputies.
Within the physics analysis groups are subgroups devoted to sets of analyses which share common themes, common tools, or similar approaches. Each of these subgroups in turn is led by a pair of conveners who establish the ongoing analyses and guide them to eventual approval within physics analysis group.
We have what I think is a pretty impressive internal website devoted to tracking the progress of each physics analysis. From a single website you can drill down into a particular physics group find the analysis you want get links to all the documentation, and follow what’s happening. In parallel, there is a web system for recording the material presented at every meeting.
The goal of every analysis is to be approved by its physics group, so it can be shown in public at conferences and seminars. This requires having complete documentation including internal notes with full details of the analysis, and a “public analysis summary” which is available to the public, and which often serves as the basis for a peer–reviewed paper which soon follows.
Every analysis is assigned an analysis review committee of three to five people with experience in the topic, who act as a sort of hit squad, keeping the analyzers on their toes with questions and comments at every stage of the analysis, both on the actual analysis details and on the documentation. After all, if we are not our own worst critics, someone else will gladly fill the role!
In parallel with processing the data that we record, we run full simulations of well–known standard model collision processes which represent our background when we are doing searches for new particles. There is a big organizational challenge in doing these simulations, which run on a worldwide grid of computers devoted to CMS data analysis. We make use of the Open Science Grid for this in the US, the EuroGrid in Europe, and other clusters scattered all around the world, comprising tens of thousands of computing nodes.
I'd love to see comparisons to organizational structures used in aerospace projects. There's nothing like this large scale organization in the industry I work in.

This framework for harnessing cognition reminds me of the original "computers" - humans who did large scale arithmetic calculations prior to the development of log tables. It's easy to imaging who this would map onto a cognitive unit made up of, initially, humans and AIs.

PS. Historical footnote: CERN was where Tim Berners-Lee, working as an independent contractor, led the development of the first web site and browser.

Sunday, November 06, 2011

The sharing challenge: access, topic and identity. Why G+ fails.

Setting aside the act of mass datacide that moved Google up my corporate evil scale, G+ suffers from a fundamental Circle problem. It may be an attempt to work around Facebook patents rather than a misguided design, but either way it doesn't work.

G+ provides these tools for publication and subscription:

  • A single identity. (In this case, identity is equivalent to a maximal set of Identity-Circles + Public)
  • Circle: both Access Control and Topic definition and Subscription-filter option
  • Person level blocks

These aren't sufficient. They put far too much of a burden on the publisher to create and maintain a multitude of Circles that pre-coordinate Access Control and Topic definition [1]. The pre-coordination work fails due to combinatorial explosion [2].

A full set of controls looks like this.

  • Multiple identity: where identity is a set of access controls and topic definitions.
  • Access controls: who can see what.
  • Topic definitions: what are the topics, so subscribers who can see a stream can choose what they follow within that stream
  • Person blocks: hide all comments from a person

A full set of controls seems more complex, but the workload largely falls on the Publisher, not the consumer -- and the combinatorial explosion problem is resolved. Subscribers choose which topic to follow. Unfollowing all topics is equivalent to blocking a person's posts but not their comments.

Google Reader Social had no access controls (that I remember), but it did allow multiple identities (an identity is equivalent to a subset of topics). The topic controls were very weak (subscribe to tags - almost never used), but the UI made it very easy to pick items of interest from a large stream. The G+ UI makes the combinatorial problem much more significant.

Google has promised pseudonym support. That will be roughly equivalent to a subset operation on Circles. Boolean operations on Circles would also somewhat alleviate the publisher combinatorial problem.

Alleviate, but not eliminate. Sooner or later, G+ will need to separate access control from topic definition.

(I'm grateful to a G+ comment from Peter C that helped me think this through.)

[1] Note too the 3 people on earth who'd probably appreciate this. This is identical to the pre- and post-coordination problems that bedevil anyone who works with concept based knowledge representation ontologies, including clinical terminologies/vocabularies like SNOMED and (yech) ICD-10-CM and ICD-10-PCS.
[2] A Sept 2011 WSJ post on "injury by falling turtle" in ICD-10-CM causes of injury illustrates this also. See #1.

Wednesday, November 02, 2011

How to replace Google Reader

Google Reader Social is dead. Thanks to its creators for showing what could be done, and thanks go Google for leaving room in the market to do this right.

Fortunately, it's not hard to do it right. At least, it's not hard for Reeder or NetNewsWire to do it right.

Even better, there's money in this market. We Google Reader infovores are ... different. Ok, not quite human. Whatever. We'll pay to reestablish what was lost.

The solution has the following components:
a. The shared item store: Posterous, Blogger, Wordpress, Tumblr (any blog-like thing will do)
b. The shared item data: Title and any one or none of: annotation, excerpt, url (all editable).
c. The tweet: Title, url (short), annotation.
d. Optional: A G+ pointer to the persistent shared item.
e. Optional: A Facebook pointer to the persistent shared item.
f. The platform: Reeder, NetNewsWire or a non-Google web based feed reader.
g. Bookmarklet to invoke the platform
This is how it works:
  1. Using NetNewsWire or Reeder.app (iOS) or Reeder.app (Mac) I see an item I want to share.
  2. I click a button or swipe, etc.
  3. I get a Google Reader style data entry area - title, url, excerpt, annotation. (Note I can simply share a note).
  4. On submission Write to the persistent store and create the Tweet.
  5. Note the minimal action set is two clicks. One to show the data entry area, one to submit it. Optionally provide a secondary 1 click action that shares title, url, annotation.
That's it. That's all we need. The rest is details. This implementation meets my replacement criteria. If I use Wordpress on Dreamhost as my persistent store, for example, I have the data and I'm paying for the service and for the platform. That's what I want.

No rights reserved for any of this. It's all public. Anyone can use it. Do whatever you want.

Friday, October 21, 2011

Google Reader: This is going to hurt

Let's get the good news out of the way.

Google has stepped back from their Buzz/G+ nymwar policy. Google will support pseudonyms. So they listened after all.

More good news. As promised, Google Reader lives.

That's enough of the good news. Don't want to overdose.

The bad news is that Google will be ripping out a lot of GR in favor of G+, even though G+ lacks a mechanism for subscribing to aspects of a person's stream. Much of the functionality I love, such as the feed for GR shares, the web page created from GR shares and notes, the ability to follow my trusted curators shares -- it's all at risk. In my case, tens of thousands of annotations, a vast amount of Cloud data, is at risk. Reeder.app, by far my most heavily used iPhone app, is at risk.

The worst news is that Google is giving us 1 week's warning. It's almost as though they want to get this over with before they get a nymwar level of feedback.

Happily, we bereaved GR users are not alone. There are 357 comments on Alan Green's G+ announcement, and the last few hundred are a tad ... unhappy. Please feel free to add your comments one way or another.

My primary comment is that Google needs to stop and think - carefully. Sure, there aren't many GR power users. What we lack in numbers, however, we more than make up in geekery. We are uber-geeks and/or journalists, and we have a long memory. Apple can blow away data, but we don't mind. We never trusted them with our data. Google though, Google's not Apple. We expect different failures from Google.

There's a tsunami of hurt building in the obscure little GR community. We may be small Google, but we're rabid little buggers. E.D. Kain, Sarah Perez, Skeptic Geek, Jesse Stay, Incidental Economist, Martin Steiger, Brett Keller, me... We're coming out of the woodwork.

There is a right way to fix GR. That would be to clean up and fill out the current feature set, and replace Reader's dead Buzz functionality with similar G+ functionality. Offer us the option to share via G+ in addition to GR -- assuming G+ gets its interest streams working.

Google's making the same kind of mistake they made with the nymwars. That one they're fixing. Maybe they'll fix this one too.

So we're gonna yell. One week isn't much, but it may be enough time to get Alan Steel and his colleagues to put the brakes on. Stop, then think.

Update: My companion G+ stream post (restricted).

Update 10/21/11: There's a petition expressing user concerns about Google's plan.

Wednesday, August 31, 2011

Communication and collaboration: We have the pieces, but not the puzzle

The geeks of my tribe share two obsessions.

We are obsessed with managing and extending our knowledge.

We are obsessed with communication and collaboration (C&C).

These are good times for us, but they could be much better. We've seen the pieces of the C&C puzzle come and go, almost coming together than spinning away.

Things have gone better on the discovery/notification/subscription side of C&C. We have had email lists and usenet newsgroups (yes, I am old); now we have Atom/RSS Pub/Sub standards, Google Reader (tragically dying), Facebook, Twitter and Google+. There's even Yammer, a corporate clone of Facebook with some G+ thrown in.

Alas, the publication side of C&C has stalled. We have had these pieces wax and wain:
It's frustrating to have the pieces, but not the puzzle. We want a solution that has these features
  1. The power and authoring speed of Windows Live Writer/FrontPage 98 client.
  2. Content display that support both item based and web-like navigation. We had much of this with FrontPage 13 years ago and you can see much of this in Sharepoint 2007's odd wiki. It's very easy to imagine a set of articles appearing as both a blog and a wiki.
  3. Change notification.
Incidentally, we also want this publishing platform to be easily used as a personal platform and a public platform, and we want to the two to optionally synchronize via Dropbox or the equivalent.

Oh, yeah, and it needs to have a published and open API (though it doesn't need to be open source).

This isn't so hard, really. Give me $30 million and I'll make it happen. I promise.

See also:
Update: Since writing this I decided to install the latest version of WLW, which is version 2011. It's dead. I feel the pain of the original Onfolio team. Seeing quality software die is a bit like watching a good kid turn into a career criminal.

Tuesday, July 19, 2011

Jon Udell on G+'s distracting chatter

Jon Udell has been testing G+. He nails it in two words ...

Distracting chatter is useful. But thanks to RSS (remember that?) it’s optional. « Jon Udell

... I came to accept a lot of distracting chatter as the price of discovering things to read. But Google+ seems to be the camel’s-back-breaking straw. The price has gone too high. So I’m rediscovering what made the blog network so thrilling to me a decade ago: unmediated access to people writing for the love of it in their own online spaces. Distracting chatter has its uses. But it’s optional.

G+ reminds Jon, and me, of why feeds aren't dead yet ...

... Last night’s 17-course meal was a selection of recent essays by Gardner CampbellBrian Dear,Lorianne DiSabato .... Paul FordCliff GerrishNed GulleyEugene Eric Kim,Adina LevinHugh McGuireCameron NeylonJohn QuimbyAntonio RodriguezScott RosenbergDoc SearlsEd Vielmetti, and Ethan Zuckerman... [2]

G+ needs to become useful. If iG+ were integrated into Google Reader, so Google Reader Shares became G+ shares, I'd go back to using it. To do that though, Google would have to support topic stream subscription as well as access controls (circles). Likewise, if G+ replaced Blogger Comments I'd definitely use it.

At the moment however, G+ is an inferior version of Facebook (no group/org Pages) without the (shrinking) number of my friends and family who post on FB [1].

[1] My experience of FB is changing. At first friends and family were sharing and it was useful for that. Most have stopped though. On the other hand, "Pages" for clubs and schools and local kid teams are more important. It's moving away from being a social network to a pub/sub group sharing network -- which starts to look like a simplified version of the web with much less anonymity. Rather a lot like late 1980s AOL and CompuServe.
[2] Great list of new names. I'm exploring each of them.

Saturday, July 02, 2011

The state of blogging - dead or alive?

Today one of the quality bloggers I read declared blogging is dying. Two weeks ago, Brent Simmons, an early sub/pub (RSS, Atom) adopter tacked the RSS is dead meme. Today I discovered Google Plus Circles don't have readable feeds.

Perhaps worst of all, Google Reader, one of Google's best apps, is getting no Plus love at all -- and nobody seems upset. The only reference I could find shows in an Amil Dash post...

The Sparks feature, like a topic-based feed reader for keyword search results, is the least developed part of the site so far. Google Reader is so good, this can't possibly stay so bad for too long ...

That's a lot of crepe. It's not new however. I've been reading about the death of blogging for at least five years.

Against that I was so impressed with a recent blog post that I yesterday raved about terrific quality of the blogs I read.

So what's going on? I think Brent Simmons has the best state-of-the-art review. I say that because, of course, he lines up pretty well with my own opinions. (Brent has a bit more credibility I admit).

This is what I think is happening ...

  • We all hate the word Blog. Geeks should not name things.
  • The people I read are compulsive communicators. Brad, Charlie, Felix, Paul and many less famous names. They can't stop. Krugman is the most influential columnist in the US, but he's not paid for his non-stop NYT blog. Even when he declares he'll be absolutely offline he still posts.
  • Subscription and notification is absolutely not going away. Whether it's "RSS" (which is now a label for a variety of subscription technology standards) or Facebook's internal proprietary system there will be a form of sub/pub/notify. There are lots of interesting sub/notification projects starting up.
  • Nobody has been able to monetize the RSS/Atom/Feed infrastructure. Partial posts that redirect to ad-laden sites rarely work. (A few have figured out how to do this, but it's tricky.)
  • Blogs have enemies with significant economic and political power. That has an opportunity cost for developers of pub/sub solutions and it removes a potential source of innovation and communication.
  • Normal humans (aka civilians) do not use dedicated feed readers. That was a bridge too far. They don't use Twitter either btw and are really struggling with email.
  • Even for geeks, standalone feed readers on the desktop were killed by Google Reader. Standalone readers do persist on intermittently disconnected devices (aka smartphones).
  • Blog comments have failed miserably. The original backlink model, was killed by spam. (Bits of Google Reader Share and Buzz point the way to making this work, but Google seems to be unable to figure this out.)
  • The quality of what I read is, if anything, improving. i can't comment on overall volume, since I don't care about that. I have enough to read. It is true that some of my favorites go quiet for a while, but they often return.

Short version - it's a murky mixed bag. The good news is that pub/sub/notify is not going away, and that compulsive communicators will write even if they have to pay for the privilege. The bad news is that we're probably in for some turbulent transitions towards a world where someone can monetize the infostream.

Sunday, March 27, 2011

Naked Emperors: where are all the connected people?

A NYT headline says half of all American adults have Facebook accounts [4]. Twitter-like valuations are leading to tech bubble denials. Social networks, we are told, led to the Egyptian revolution [1].

Except, I don't see it here among school parents, sports team families, tech company colleagues, and upper-middle-class neighbors.

True, I live in the midwest, but by all metrics Minneapolis is a snowier version of Seattle-Portland. If not here, then where?

I don't see feed readers in use outside our home [3]. Almost nobody subscribes to calendar feeds. Very few of my sample [5] use Twitter. Most of my friends who once used Facebook have stopped posting or even reading. Even texting isn't universal. Everyone has 1-2 email addresses and can use Google, but that's as far as it goes. Forget Foursquare.

I see more iPhones every day, but they're not used for location services, pub/sub (feeds) or even Facebook's user-friendly pub/sub. Around here iPhone communication change has been limited to faster email responses.

There is change of course, but it lags about 5-10 years behind the media memes. Dial-up connections are mostly gone, though I still see AOL addresses [2]. Texting is becoming common. Old school email is now universal, though many (unwisely) still use office email for personal messaging.

It's frustrating for me; all of the school, sport, community organization and even corporate collaboration projects I work with would go better with pub/sub in particular. I've learned the hard way to dial back my expectations, and to focus on 1990s tech.

So is Minneapolis - St. Paul strangely stuck in the dark ages? Or is there a gulf between the media portrayal of American tech use and reality --  a gulf that will lead to a big fleecing when Facebook goes public?

My money is on the fleecing - and a faint echo of the 90s .com bubble.

[1] The same nearly-free-to-all worldwide communication network that Al Qaeda used effectively in 1999-2000 is now celebrated by us for its benefits in Egypt. Technology has no values, only value.
[2] I assume about half those are dial-up. 
[3] Google Reader is astounding. Just astounding. Nobody mentions this, everyone talks about Twitter (not useless, but weak). Weird.
[4] Not actually using FB mind you, just have accounts.
[5] Ages 8-80.

Update: An hour after I posted this I thought of one remarkable exception: LinkedIn. Unlike Facebook, LinkedIn has a non-predatory business model. They have been relatively careful not to infuriate their users. LinkedIn continues to grow, and I don't see any true attrition. It will be interesting to compare their valuation to Facebook's.

Wednesday, January 05, 2011

The not-so-vast readership of Gordon's notes - and why I keep posting

I get emails when a reader (infrequently) comments. The author deleted this comment, so I'll keep it anonymous ...

Say, is it not odd that you don't have a bunch of readers reading your blog? You have been writing this since 2003 and nobody comments or reads it? Is this even real?

Oh and I figured out how I reached your blog. I was looking for "nobody reads your blog" on google and a comment from your blog showed up on the 47th page.

Its sad and funny at the same time...

I wasn't able to replicate his search results, but unless we're post AI this was a bio post, not a bot post.

It's a good question [4], but there are a lot of blogs that go unread. So mine is not that unusual. What's unusual is that it's been persistently unread for 7 years. So the real question is - "why would anyone write 5,494 posts that nobody reads?" (@9,000 if you add Gordon's Tech) [1]

The short answer is that I read both of Gordon's Blogs. As I wrote back in 2007 ...

... my own very low readership blogs are written for these audiences in this order:

1. Myself. It’s how I learn and think.

2. The GoogleMind: building inferential links for search and reflection.

3. Tech blog: Future readers who find my posts useful to solve a problem they have that I've solved for myself.

4. Gordon's Notes: My grandchildren, so I can say I didn't remain silent -- and my tiny audience of regular readers, not least my wife (hey, we don't get that much time to talk!) ...

Later, when I integrated Google Custom Search, my history of posts began to inform my Google searches. My blogs extend my memory into the wider net.

So that explains why there are 9,000 "John Gordon" posts.

As to why their aren't many comments/readers, I can imagine several reasons ...

  • There's no theme. Gordon's Notes follows my interests, and they wander. At any given time there will posts that most people find boring, repetitive, or weird.
  • I'm writing for someone like me, Brad DeLong, Charlie Stross, Emily L and others of that esoteric sort. That's an uber-niche audience.
  • I have no public persona (I write using a pseudonym)
  • I like writing, but I don't work at writing. I'd have to work a lot harder to write well enough to be truly readable.
  • I don't market the blog.
  • I update my blog at odd hours, and I'm slow to respond to comments.
  • I have an irregular posting schedule.
  • I don't right about areas where I'm really a world-class expert because I keep my blogging and my employment separate.
  • I often write about the grim side of reality (that is, most of it).

That covers the bases I think. Except ...

Except, it's not quite so simple. It turns out I do have a few readers -- I'm guessing about 100 or so [3], not counting a larger number who come via Google [2], but certainly counting Google itself. Some of my readers are bloggers with substantial readership, and sometimes they respond to what I write.

So I do have an audience after all, it's just very quiet.

See also:

-- fn --

[1] Why do I share thousands of items via Google Reader? Because that's a searchable repository of things I find interesting. Another memory extender.
[2] I don't have a stellar Google ranking, but it's not bad 
[3] About 80 via Google Reader alone, where I share these posts.  There's also Emily, who comments over breakfast. A lot of my posts come out of our discussions.
[4] It wasn't clear when I first posted this that I like the question. I think it's a good question and I think it was meant well. Sorry for not making that clear. I've added this footnote.

Update 1/6/11: Based on comment response I probably have more regular readers than I imagined.

Tuesday, March 09, 2010

Reimagining realtime focalcast communication – Buzz and Twitter 2.0

Google, and Buzz, are flailing. Facebook is evil. Twitter is annoyingly limited [1].

We need to reimagine focalcast realtime communication [1].

As a first pass we can think of a realtime communication message channel as having two key properties: Audience and (primary) Purpose.

Audience is the set of permitted subscribers. Example: “Family” or “Public”.

Purpose is a single sentence definition of what the the channel is used for. Example: “Location sharing” or “Political opinions” or “Mate attraction”.

The resemblance of Audience and Purpose to century old definitions of printed media marketing is not accidental.

To be truly useful Buzz or Twitter 2.0 need to allow any message (not length limited) to be characterized by Audience and Purpose [2]. We can imagine these as two metadata elements [3] represented in a user interface as “drop down” or select boxes.

On the client side users subscribe to a channel defined by Author and Purpose for which they have access rights (Audience).

Since some Audience-Purpose pairs are far more common than others (“Location sharing”+”Family” or “Location sharing”+”Mate attraction”) combining these in a user interface would increase usability.

A single “identity” or “account” should own the definitions of Audience and Purpose, though it may be useful to associate Audience-Purpose pairs with a “persona” [4]

When I see a solution emerging that uses open data standards without data lock (Buzz API?) and that supports Audience and Purpose in a useable way, I’ll know it’s time for me to fully engage. Until then, I’m just playing.

[1] Geezers will remember email lists as the original focalcast medium. Since list communication was not realtime messages resembled postal letters; they often resembled exchanged essays. Twitter’s accidental length limit (determined by the quirks of the text (SMS) message hack) makes Twitter exchanges either staccato status updates or metadata pointing to discussions held elsewhere. Neither realtime length limited Twitter nor slowtime unlimited length email are adequate focalcast communication technologies.

[2] A third attribute of “archive” would cause the communication to become the equivalent of a blog post, but that’s a nice-to-have. Author is an implied attribute; it’s used by subscribers.

[3] Ontology strictly optional, though many will emerge.

[4] As of a few weeks ago I thought that persona management was a key component of Buzz/Twitter 2.0, but now I think the combination of Audience/Purpose pairs makes persona management less critical. One could handle other persona issues through separate accounts (identities).

See also