{"id":10229,"date":"2013-03-10T12:19:45","date_gmt":"2013-03-10T16:19:45","guid":{"rendered":"http:\/\/aforgrave.ca\/detritus\/?p=10229"},"modified":"2013-03-10T14:42:13","modified_gmt":"2013-03-10T18:42:13","slug":"blog-in-haste-redact-at-leisure","status":"publish","type":"post","link":"https:\/\/aforgrave.ca\/detritus\/2013\/03\/10\/blog-in-haste-redact-at-leisure\/","title":{"rendered":"Blog in Haste, Redact At Leisure"},"content":{"rendered":"

I don’t have time to sort this out now. Sorry.\u00a0<\/em><\/p>\n

And you should know that this post is on its THIRD title.<\/p>\n

\""<\/a>

” … but beyond that, it’s a Crap Shoot …”<\/p><\/div>\n

I changed the title post from its FIRST title:<\/p>\n

Can<\/strong> #%^&*@ You<\/strong> @%$#^*& Now<\/strong> ???<\/p><\/blockquote>\n

to the second title:<\/p>\n

Can (as in Terminate) You Now<\/strong><\/p><\/blockquote>\n

and from that to the current title\u00a0because my frustration is tempered by my respect for my ds106radio friends.<\/em><\/p>\n

But this morning I’ve noticed \u00a0some oddities in the recently launched ds106rad.io\/listen<\/a> page that I put together in support of the transition to the new Airtime backend. My motivation for doing so was driven by my desire to help keep us connected through the transition, and brought about by a little bit of frustration at some now-missing features that had been working in the original ds106radio technology.<\/p>\n

However, my experience this morning gave me a flashback to the days of the Coke\/Pepsi taste tests<\/strong>, or those wonderful childhood\u00a0Think And Do Activity Books<\/em> where you had to put a circle around all the little things that were different<\/strong> between two almost identical images.<\/p>\n\n\n\n
Can You Tell the Difference?<\/caption>\n
\n\n
\"Can<\/a>

Can You Hear Me Now? on aforgrave.ca<\/p><\/div><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

It appears the page that I put up has been slightly modified. Just a bit. And as a shared-community effort, that’s what we’re about here at ds106.<\/p>\n

However, the most significant difference is the oh-so-obvious missing HTML5 player<\/strong> in the safari-browser window — the reason I went to the page in the first place this morning! \u00a0I can’t hear my ds106radio!!<\/em><\/p>\n

Seeing this then brought a quick QA test in the Chrome browser, which initially resulted in the Aw, Snap<\/span> response that appears earlier in this post.<\/p>\n

Were I confident that I could listen to ds106radio in FStream<\/strong>, I would have turned there. But I fear that’s something that is on my list of things to sort out — why can’t I hear ds106radio in FStream?<\/em><\/p>\n

If I could simply fire up the Status Page<\/a> to see whether someone is streaming live or what I should be expecting to hear, I would do that — but the ongning Airplay — Offline<\/strong> and the limited connect between the inbound stream and the outbound metadata is sketchy at best.<\/p>\n\n\n\n
ds106radio is Offline? \u00a0Where is Otto?<\/caption>\n
\"Where<\/a>

Where is ds106rad.io ??<\/p><\/div><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Apparently with WinAmp, you get metadata. Or is it Laudiocast? It used to be great with Nicecast. And Papaya. I need to talk to Nigel about that.<\/em><\/p>\n

And the last time I was ‘casting on Papaya<\/span> — it seemed fully happy to continue, telling me that I was connected to the server and that the signal was going out — but who knows where the stream was going TO? It wasn’t getting to ds106radio (no metadata to confirm either way) (AFAIK — @DrGarcia<\/a> maintains SHE was on the radio then — not that the metadata indicated that, either — but I did hear her bang a utensil on some cookware at my request. Thanks, GNA!<\/em>)<\/p>\n

We all love our ds106radio — it helps to bind the ds106 community together.<\/p>\n

And I’ve been trying to sort out little bits and pieces along the way to help out where I can — knowing that the station is in a transition period with the new Airtime software.<\/p>\n