Here are the basics:
The nice part about this setup is that it's all automatic: the only action I take is posting my idea onto my site. The feeds take it the rest of the way.
Analytics are pretty crude at this point. Any clicks on the feedburner-based feed should offer some basic analytics. If I really wanted details, I think I'd need to generate a separate feed for each microsyndication destination if I wanted to measure twitter clickthroughs vs. facebook clickthroughs (though google analytics should offer a hint about the source of clicks to greacen.com)
Here's the Graphviz drawing of the flow I described above. digraph BlogPost {
size="5,6";
ratio = fill;
node [style="rounded,filled,bold" shape="box" fillcolor="skyblue"];
/* Set up specific shapes */
"RSS Aggregators" [style="rounded" shape="box3d"];
"URL Shortener" [style="" shape="invisible" label="URL Shortener"];
"Analytics" [style="" shape="invisible"];
"greacen.com" [label="greacen.com Publish blog article"];
"feedburner.com" [label="feedburner.com Analytics and scaling"];
/* Box in those 3rd party things */
subgraph cluster_c1 {"Analytics"; "URL Shortener";
label="Other Parties"; style= "dashed";}
/* Show and label relationships */
"greacen.com" -> "feedburner.com" [label="GET RSS" dir="back"];
"feedburner.com" -> "twitterfeed.com" [label="GET RSS" dir="back"];
"feedburner.com" -> "Analytics" [];
"twitterfeed.com" -> "URL Shortener" [label="GET URL" ];
"URL Shortener" -> "twitterfeed.com" [];
"twitterfeed.com" -> "twitter.com" [label="POST twitter api"];
"twitter.com" -> "facebook.com" [label="facebook/twitter bridge"];
"feedburner.com" -> "RSS Aggregators" [label="rss feed" color="darkorange"] ;
"twitter.com" -> "RSS Aggregators" [label="rss feed" color="darkorange"] ;
"facebook.com" -> "RSS Aggregators" [label="rss feed" color="darkorange"] ;
}
Here's what those instructions become with a click:
This is different from my surf report post. The surf report is the content, whereas with a blog post, my site holds the real content. The RSS feeds publish a pointer to the original content.
Make sense?
I sent a message from my phone this morning. Even though the surf was lame. The message was published all over the place (microsyndication). Here's how it worked:
Guess what? Most of these nodes along the way have their own RSS feeds for others (services or people) to slurp & read.
Thinking about this plinko-esque publishing flow is a little dizzying. I've been working on web site flows for a few weeks now. It's often helpful to map out a flow to see what's really going on. Graphviz is an open source tool for producing network diagrams and flow charts that I've been using for mapping high-level flows. Here's what a map looks like for the publishing flow I described earlier:
digraph TwitterSurf {
size="6,6";
ratio = fill;
node [style="rounded,filled,bold" shape="box" fillcolor="skyblue"];
/* Set up specific shapes */
Phone [style="rounded,filled" shape="oval" fillcolor="grey"];
"RSS Aggregators" [style="rounded" shape="box3d"];
/* relationships */
Phone -> "twitpic.com" [label="Email with attachment"];
"twitpic.com" -> "twitter.com" [label="twitter api"];
"twitter.com" -> "facebook.com" [label="facebook/twitter bridge"];
"twitter.com" -> "stokereport.com" [label="if post contains 'SMLM'" style="dotted"] ;
"twitpic.com" -> "greacen.com" [label="widget/embed" color="red"] ;
"twitter.com" -> "RSS Aggregators" [label="rss feed" color="darkorange"] ;
"facebook.com" -> "RSS Aggregators" [label="rss feed" color="darkorange"] ;
"stokereport.com" -> "RSS Aggregators" [label="rss feed" color="darkorange"] ;
}
If you ignore the []
s, it looks like a terse version of our list up above. Here's the flowchart those instructions produce:
Kinda neat, huh? I find the way this goes from text to sitemap really intriguing. This -> that; that -> next; other -> next;
makes sense to me. Graphviz does a great job of putting this all together in an easy-to-digest graphic.
There are a few rails front ends to graphviz (demo) that might make a web tool for this possible. I could see this becoming a handy planning tool for our organization.
Questions:
Thanks for reading.
I got about 28 songs up there, a few are even keepers. Of my stuff, I feel good about these:
This URL will take you to all my songs.
This player has everything that was uploaded. Steal the embed code if you want this on your site.
Here are some of the most listened-to songs from the month: 247 0203_bruce_2nd_time.mp3
196 0204_bruce_3rdwave.mp3
192 0201_derek_a_song_a_day.mp3
190 0205_bruce_shouldabeenalespaul_.mp3
176 0201_greacen_oh_hell_oh.mp3
173 0203_greacen_istanbul.mp3
163 0202_derek_jury_duty.mp3
163 0202_bruce_timesup.mp3
160 0204_greacen_trouble_sleeping.mp3
159 0215_bruce_base.mp3
158 0203_derek_where_is_walt.mp3
158 0201_peter_all_that_i_can_feel.mp3
157 0206_bruce_thank_you.mp3
152 0204_bruce_whatthe.mp3
149 0202_greacen_2wo.mp3
147 0204_derek_disneyland.mp3
146 0203_ryan_in_to_the_night.mp3
146 0201_seth_the_best_place_in_the_world.mp3
145 0131_seth_the_day_before_song.mp3
143 0209_greacen_master_of_the_mall.mp3
142 0203_peter_twothreeohnine.mp3
140 0213_derek_hawaii.mp3
140 0205_greacen_bring_it_back.mp3
139 0216_greacen_watching_all_the_good_ones_go.mp3
139 0202_peter_all_of_them.mp3
136 0212_bruce_alone.mp3
132 0208_greacen_wafflepalooza.mp3
129 0212_derek_taxonomy.mp3
Pretty evenly distributed. I remember Bruce's stuff got a lot of attention last year too, but it seems like the earlier songs are still getting plenty of play.
We're almost to 13000 song streams at this point and if the traffic followed last year's pattern, people will still be listening for a few more days.
Starting to think about Song-A-Week for the rest of the year. Email me if you want in on this.
For me, it's time to turn to other instruments, other family members, more wine, plagarism... you get the idea.
I have a few comments in no particular order.
If you know anyone else interested in playing along for the rest of the month, invite them over.
Finally, I made a few changes to the RSS feeds on the site. There are actually 4 feeds worth knowing about. Here's the skinny:
What sort of nefarious things can one do with feeds (nefeedarious?) like this? Well, that MRSS feed will now work with more flashy mp3 players that take RSS feeds as playlists. Like this: