bbcbackstage – Cubicgarden.com…

RIP to the wonderful force of nature Molly

I had no idea an old friend (I will call her that because she was such a warm and caring person to many) Molly Holzschlang died over a month ago. I only found out when an old friend Brendan tagged me and others into a Facebook post. Which linked to Eric Meyer’s blog.

It was a shock, because although I knew she has struggled with her mental health and last heard from her before the covid19 pandemic. I have such great memories of Molly. Being a declarative designer/developer, Molly’s work around the early web stood out. I still remember reading molly.com to understand early CSS and DHTML (remember that phase).

But it was when I ran London Geekdinners, I finally got to meet her for the very first time 24th November 2005 at the Hogs Head, Westminster, London. Then again on 20th October 2006 at the Bottlescrue, Holburn Viaduct, London and then 26th January 2007 at City Spice, Brick Lane, London. She also stopped in at the BBC for lunch on 31st January 2007.

Group photo in 2007 with Molly facing away from the camera

On and off we kept bumping into each other and remember there was things a lot of friends did including thank you Molly. She was loved by many and will be sadly missed.

Rest in peace Molly x

The next web peers around BBC R&D…

Perceptive Radio v2 — The second-generation experimental Perceptive Radio hardware. Credit: Martin Bryant / TNW

Its always great to have some of the work in the press, and see which bits they pick up on. But even better is when it gets framed along with other work, such as the ones happening around the same lab or similar fields.

In recent times, Ian Forrester has turned his attention to ‘Visual Perceptive Media.’ As we first reported late last year, this applies the same principles to video-based content.

For the first experiment in Visual Perceptive Media, the BBC worked with a screenwriter who created a short drama with multiple starts and endings. In addition to the variable plot, a number of different soundtracks were prepared, and the video was treated with a range of color gradings to give it different moods, from cold and blue to warm and bright.

Good to see the next web picking up on the effort we put into making all this very open. This comes from before my time at BBC Backstage but it certainly makes things easier to justify with us being a public organisation haven done things like Backstage.

One thing that struck me when talking to the people working on all of these projects was that they were using the Web browser as their canvas and working with free-to-use, open technologies like OpenGL, Web Audio, Twitter Bootstrap and Facebook React.

And what better end than…

Some of the most interesting ideas for how that might happen are coming out of BBC R&D.

BBC Backstage needed to close, for BBC Taster to happen

It is my opinion. BBC Taster could not happen if BBC Backstage was still running.

A long time ago there was BBC Backstage, it was great and did a lot for the BBC and the licence payers who didn’t quite fit in the SME/Company bracket but were also not just consumers of the BBC’s output. I would suggest they were the 9% (I don’t think this figure is correct but go with it as it fits the 1% theory) which the BBC had a harder time understanding.

BBC Backstage was a great success and lasted 5 years achieving some incredible things including the first UK hackday. It changed the relationship with the tech & media-savy 9%, who frankly had enough of being treated mere audience members.

But it had to end, for good reasons as explained in my blog about why I shutdown BBC Backstage.The BBC Connected Studio and the newly launched creative playground BBC Taster. Would have been a very different proposition if BBC Backstage was still around. It would also been an injustice to the changing and diverse 9%.

I said in a previous blog…

Things need to end (such as BBC Backstage, Innovation Labs, etc) for others to spark, grow and mature like BBC Connected Studio.

Well you can add BBC Taster to that list of others to spark, grow and mature… I know its not every-bodies cup of tea but change never is, but give it some time.

Why I shut down BBC backstage

BBC Backstage Meets the NW communities networking bash

George sent me a tweet saying how much Elizabeth Murdoch loved BBC Backstage, as she mentioned it in her speech to the Edinburgh TV Festival last year.

The BBC has been the market leader for building new relationships and services with creative’s from every sector. Be it the early ground breaking Backstage initiative for technology engineers.

Shes right and it does beg the question, why is there no more BBC Backstage?

I thought this was covered in the BBC Backstage ebook which was put together by the lovely Suw. But it looks like I may have been slightly mistaken. On top of this, I keep making reference to this blog post which I never seem to quite finish. So enough, its finished and out there for all to read…

First misconception: The BBC never shutdown BBC Backstage

Actually I did… When I first mentioned the possibility of closing down BBC Backstage to Adrian (my manager) he thought I had totally lost it. I remember a meeting with Adrian and Matthew (head of R&D) where I talked about shutting it down and I gave my reasoning which made soften the blow a little. I had thought long and hard about leaving BBC Backstage and passing it on to someone else younger and full of energy (I even had a number of names put forward to consider). But it didn’t make sense.

The problems with Backstage were not about who was running it but more about what was happening around it (as we will see in number 4)

Second misconception: The BBC sits on a ton of data.

The core of BBC Backstage was the backstage license which is founded on non-commercial reuse of data. This gave backstage the license to go around the BBC educating/persuading/convincing stakeholders about the benefits of open data at a time when data wasn’t a big thing. The problem is the data wasn’t ours. For example the Met Office would make the weather data available to the BBC under strict licensing. Deals were done for non-commercial use and it was always neigh impossible to reverse a deal without effecting the production side of the things.

Lots of people imagine most of Backstage was hacks. In actual fact lots of it was people experimenting.

Third misconception: Developers found new business models

This backs off the non-commercial problem. Because everything was under the non-commercial license, when things like the Apple App Store came along and offered developers clear ways to make money from their work. We had to shut down a lot of prototypes and tell people not to use BBC backstage data in there apps.

This was actually a issue from early on when Google Adsense, offered developers a nice way to make a small amount of money based on numbers of people who came to the site. It was argued that if developers made enough money to just cover the hosting of the prototype, we could turn a blind eye to. This wasn’t sustainable as it kept coming back to bite every once in a while. But it wasn’t till the App stores when the number of prototypes and services wanting to go commercial blew up.

Once developers learned it was actually against the terms and conditions, they naturally moved on to other platforms. We did talk to BBC Worldwide many times about working together but it just wasn’t to be.

Forth misconception: The Open Data Revolution passed it by

Backstage had a hand in getting this revolution going in the UK and beyond. 7 years later, we had influenced everyone from other companies to the government. We were there right at the start of this revolution and fundamentally changed the BBC’s thinking about data. However it was clear this was just the start and as a part of BBC R&D, it was right to move on and have the same impact in another emerging area. The developer network part of Backstage was tricky to balance with the push to drive forward.

We did think about splitting it off and working in partnership with others who were later to the scene but it just didn’t quite happen and in the era of cost cutting and doing the things which really have an impact for our audiences it was harder to justify.

Fifth misconception: It was all about DRM and the BBC wanted rid

Looking at the mailing list, its easy to imagine it being all about DRM and not a lot else. But in actual fact while the DRM debates rages on, there were lots of people creating and making lots of prototypes. Lots of them were documented on the website but there were some which were so illegal there was no way I could put them anywhere public. Those were more of a look what we could do…

Even though they were much more black/grey around the licensing terms, they drove the imagination and clearly got a number of us thinking what if…? One such example is the widely talked about blast from the past called Panadora PVR (now called Promise.TV) which lead to Tom Loosemore’s talk at Etech 2007, the Edinburgh TV unfestival and the building of the infamous BBC Redux.

The BBC gained a lot from having the debate and being rather open about it all.

Sixth misconception: There was no money or love for BBC Backstage

This is somewhat true and false. Yes it became more difficult to justify and we had gone through quite a difficult patch, while losing some key people to project. On top of that we had a new head of Future Media (Erik Huggers), moved into BBC R&D and was shifting the project up to the north of England to fit in with BBC’s increasing push to solve the London and South East bias.

Everything was changing and everytime we took BBC Backstage in a different direction, there was push back from the dedicated community. To me this is the way of the world (forever changing) but it certainly makes funding such projects difficult when you want a 3-5 year plan.

There was much love for BBC Backstage from Future Media and other departments in the BBC, there was lots of talk about setting up other Backstages in different areas as a outreach project alone it hit audiences the BBC was not so good at having conversations with. The formula was repeatable but should it be? We could have done Mashed all over the UK but was that a good idea? I certainly didn’t think so and ultimately my thoughts about driving forward were correct.

Seventh misconception: We ran out of steam

Ok this might be true to a certain extent. But not from the lack of trying… You only have to look at the new things I’ve been working on since, including Channelography, Perceptive Media, etc. There is still fire in myself and I still have a lot to give… During that time, I will admit I was well over worked and I was being contacted by many people on the off chance just because I was out in the open. This certainly slowed down daily looking through BBC emails. Hence why I now have a another BBC email.

Ultimately I want to thank everyone who has been involved in BBC Backstage in the past (too many to name). The decision was made under a ton of stress on my part but I felt I was making the correct decision for everyone including the founders, the BBC and the community. Then and even now. I mean can you imagine BBC Backstage in 2013!?

Things need to end (such as BBC Backstage, Innovation Labs, etc) for others to spark, grow and mature like BBC Connected Studio.

Big Data should be the word of the year

I heard Geoff Nunberg’s piece on NPR’s podcast and I got to say, although I’m pretty much big dated out from BBC Backstage (in a nice way) I’m in total agreement. Here’s a few key points… Well worth listening to in audio form…

Whether it’s explicitly mentioned or not, the Big Data phenomenon has been all over the news. It’s responsible for a lot of our anxieties about intrusions on our privacy, whether from the government’s anti-terrorist data sweeps or the ads that track us as we wander around the Web. It has even turned statistics into a sexy major. So if you haven’t heard the phrase yet, there’s still time — it will be around a lot longer than “gangnam style.”

What’s new is the way data is generated and processed. It’s like dust in that regard, too. We kick up clouds of it wherever we go. Cellphones and cable boxes; Google and Amazon, Facebook and Twitter; cable boxes and the cameras at stoplights; the bar codes on milk cartons; and the RFID chip that whips you through the toll plaza — each of them captures a sliver of what we’re doing, and nowadays they’re all calling home.

It’s only when all those little chunks are aggregated that they turn into Big Data; then the software called analytics can scour it for patterns. Epidemiologists watch for blips in Google queries to localize flu outbreaks; economists use them to spot shifts in consumer confidence. Police analytics comb over crime data looking for hot zones; security agencies comb over travel and credit card records looking for possible terrorists.

It’s the amalgamation of all that personal data that makes it possible for businesses to target their customers online and tailor their sales pitches to individual consumers. You idly click on an ad for a pair of red sneakers one morning, and they’ll stalk you to the end of your days. It makes me nostalgic for the age when cyberspace promised a liberating anonymity. I think of that famous 1993 New Yorker cartoon by Peter Steiner: “On the Internet, nobody knows you’re a dog.” Now it’s more like, “On the Internet, everybody knows what brand of dog food you buy.”

BBC Connected Studio/Social

I haven’t mentioned the BBC Connected Studio on my blog to date. However its about time…

So its a new (its been running since May) BBC project which is all about open innovation. Every month we put out a brief around a certain product area in the BBC. To date its been to redo the BBC.co.uk homepage, rethink the Weather and Travel services and this month its re-imagine services for the Cebeebies audience.

Every month theres one day of idea studio and the pitches at the end. The idea studio gives people a chance to come together and explore ideas against the brief. Of course you can just go into a corner and develop the idea with yourself or your pre-selected teammates. Its about what ever works to get the best ideas. I find people come with a rough idea and tend to combine the ideas together or build on each others ideas. Open innovation is the key here. After the ideas build up and you’ve had a chance to run through a series of workshops including a end user pitch (or not if you don’t want to). Your now working things up for the pitch to the commissioners and everyone else.

If everything goes well, you get selected and receive a email to say the commissioners would like to see it developed into a prototype. At which, about 2 weeks later, its build studio time.

The build studios are like hack days (our learning from hackdays, mashed and over the air) but they run over 2 days and the end presentation doesn’t receive some token prize, they receive a good daily amount for being there time while developing the prototype. However at the end there is the opportunity to pitch the prototype to the commissioners for more serious amounts of money.

The events take place in Manchester, Glasgow and London which means theres no reason not take part. And that applies to staff as well as externals. Actually theres something quite magically about seeing BBC staff collaborating directly with externals. I’ll be excited to see how things work when one such team go through to the later stages.

It sounds slightly complex but actually its pretty straight forward, and takes the best parts of Innovation labs and Hackdays on a ride.

The BBC is serious about Connected Studio and has pledged a million pounds behind the whole project.

Ralph director of Future Media talked about how he loved BBC Backstage and what we built back then. And to be honest theres a air of Backstage floating through the whole process. For example anyone can register there interest via the BBC Connected blog (no secret handshakes or secret buddy systems just apply). This means you have as much chance as those on the BBC’s official supplier list. Connected Studio has attracted SME’s, startups, hackers and early adopters. Unlike backstage were talking about things which are made for deployment on the live site, so generally theres shorter term innovation (aka less 2 years).

The majority of new BBC Online products are built according to long term product roadmaps and the published commissioning process. However, we believe there’s room here for more disruptive thinking – that is, more experimental ideas that can be pitched, built and delivered to audiences in a faster, smarter way. We would like to hear from agencies and individuals who have fresh, innovative ideas to bring to this event and to seek funding.

The process isn’t perfect (but what is?) but is adaptable and is always looking for feedback.

So whats my role in the connected studio?

Well thats still being worked out but I’ll have my R&D glasses on when watching the pitches and I’m very interested in the network of people who are doing innovative things and have been to a connected studio.

However, something I can talk about is BBC Connected Social, which are events linked to the BBC Connected studio process.

Like Connected Studio its still very early days and I’m expecting it to twist and change as it matures. But its a good chance for people external to the process because they can’t spare the time, never heard of it or didn’t make it into the process to learn more, network and pick up some really useful knowledge all at the same time. For those on the build studio, its a chance to take a break, network and consider a slightly different take on the prototype there building towards (if they wish).

The first one is Tuesday evening at Media City UK while future ones will also match the location of the Connected Studio (be it London, Glasgow or of course Manchester)

Its a chance to learn, debate and socialise on topics closely aligned to the BBC’s strategic themes.

The Build Studio for July is centered around CBeebies, and we are running a panel talking about building for the ages of under 13’s. With useful advice and tips from Mystic mobile & Lancaster’s Dr Paul Coulton, BBC’s Games grid Simon Lumb and BBC’s Children’s Jon Howard.

Hopefully we’ll see you at a BBC Connected Studio or Social soon… You know where to sign up and the next brief is around CBBC (Children’s BBC). Hopefully the next social will include a panel of young people talking about there media habits because that is always insightful.

Grassroots Innovation & Creativity

People have been wondering what am I up to since Backstage closed down.

Well its kind of hard to describe but generally I’ve become the resident troublemaker, breaking all types of rules and really etching a new kind of path for myself. If I was going to explain it in a buzz word compliant way, it would be something like… Senior Emerging and Disruptive Grassroots Specialist for BBC R&D.

Yeah feel free to be sick all over your screens.

But one aspect I certainly want to focus on is new types disruption and innovation from the edges or grassroots.

So part of my new job will be seeking the seeds of disruption and innovation before they get to the point of broad adoption.

I come with examples…

Most of the people reading this have been on Twitter at least 4 years, and we could see something interesting was going on with Microblogging but no one really knew what? About 4.5 years ago I met the guys from Twitter (Ev and Biz) and I did talk about what we (BBC) could do with Twitter. Unfortunately I working on Backstage, meant my focus was on data. Although we did talk about what the opportunities Twitter might give the BBC. Of course most of that went up in smoke and Twitter marched on to establish a business model (ok not a very good one but its still something) and a certain amount of dominance in the microblogging and social fields.

Just imagine what would have happened if things turned out different. The point is there was something there and with a good trial someone else could have identified it as something interesting that the BBC should look deeper into.

How I find interesting stuff?

I mostly rely on the people around me for pointers. Thats why I tend to only follow a small number of people on twitter. But I also look at what certain people are up to. In actual fact, its this aspect which bough me to the BBC. Seeing what Tom Coates, Paul Hammond, Matt Patterson, Ben Metcalfe etc were up to really got me going. I had no idea who they were originally but most of them were pretty accessible in person, which really helped.

But as I’ve noticed and you would expect the list of innovators changes all the time. Not that I’m not saying these guys are not doing anything interesting. Actually they may be but new people come along all the time.

I’ve ping’ed a few people about the idea of what I’ll be doing into the future and had various comments back. Some positive, some quite negative but all a great help with lots of ideas and thoughts. One of the most provoking has to be the idea of it being an inbreed network. It really got me thinking… How do you have a network of trusted people but not make it your friends and keep the signal strong?

The obvious example seems to be keep it open… But with openness comes the trouble of keeping the noise out. Its a challenge but I’m hoping to tackle it in a social sciency kind of way.

I really like what Mozilla has done with there Drumbeat projects. But there is a theme which means people are rally around an idea or concept at least. But its wide open, which means you can get right to the edge, no messing. The best way to get stuff from very left-field. Actually I’ve been thinking instead of copying Mozilla, maybe there’s a way to leverage or even work with Mozilla for the benefit of both organisations?

Documenting stuff no matter what

Theres lot of things BBC R&D does which it classes as a throw away experiment and then years later I see something which resembles the original concept or idea. Its critically important to document and I would say share the successes as well as the failures. In R&D right now, we tend to bury this in obscure papers which don’t get to see the light of day. I always wanted to get away from writing papers but have fallen into the trap of writing papers too.

There are better ways, be it prototypes, a series of detailed blog entries, whatever works to document experiments and projects. I don’t doubt a properly authored paper with many citations are a better that a blog post. But if the paper becomes the reason why documentation isn’t done, then maybe its a problem? Right?

I’ve noticed a whole bunch of new ways to document stuff, most of them are simply prototypes filmed and put on youtube. It won’t stand up to much scrutiny but at the point it needs to, then thats when the paper can be written. Its like that all too familiar innovation funnel. Things are cheaper at the start than the end. Maybe you don’t want to commit to writing a lengthy paper when a series of blog post will aid writing the paper at a later date. The blog post can also function as prior art too.

What I have to recognize is that I work in the Emergence stage of innovation.

Emergence – (also known as embryonic stage) shows little improvement in key performance characteristic. Technology operates far below its potential. Neither the characteristics of technology nor its applicability to market needs may be well understood. A long gestation period exists before attempts are made to produce a technology. This new invention period is characterized by a period of slow initial growth. This is the time when experimentation and initial bugs are worked out of the system.

Its ok to be wrong

its ok to be haphazard

Its ok to not have all the answers

its ok to bounce from one thing to another.

Just as long as the experiments are cheap, documented and understanding is formed and shared internally and sometimes externally.

So with all that, spilled out across the this blog entry… I’m coming around to something which is I think very impressive and fundamentally what the BBC really needs now and for the future.

I guess its exactly what the guys behind Backstage were thinking before backstage was formed in 2004.

Wish me luck…

BBC Backstage in the guardian again

So now the ebook is out there, this pretty much spells the end of the BBC Backstage project. The backstage site & blog will go into a deep freeze so none of the links will be broken. It was interesting to read the Guardian wrap up of backstage, there was some good quotes from our interview way back in December 2010. But what got me was after a while was the slideshow from Rainycat. She was so good at documenting things. Of course afterwards I spent about a hour or so going through my own photos tagged bbc backstage.

I’ll say it again, BBC Backstage was an amazing project to be part of and even run. Not just the big stuff but also the small stuff. The good times (the many events we did, the prototypes and finally getting our own backstage playground servers off the ground) and the times when I thought I might be sacked (such as undermining the podcast trial by launching our own using blip.tv or crossing the hacker/BBC divide by sympathising with the DRM protests).

Its been simply incredible and looking back through the pictures, I see a lot of really happy people. Theres no doubt I’ll be chasing the high of working on backstage for quite some time to come. I think I remember a conversation I had with Rain after her attachment came to an end.

"Working for the BBC should be that way, and anything we can do to make that happen is always a good thing."

As always thanks for tags hackers of the new world, hopefully what we do next will be even more exciting that backstage ever would have been.

The history of BBC Backstage (the ebook)

At long last the Book charting the highlights of BBC Backstage is available for everyone to download and read.

Download in [PDF] [print ready PDF] [EPUB] [MOBI] [RTF]

Originally I wanted to celebrate the 5th Anniversary of backstage in May 2010 with a book made up with the contributions of the actual people who made it work over the years. So I contracted Suw Charman Anderson back in early 2010 to start work collecting the material for the backstage book and newspaper.

By April 2010, she collected and started to write up whole sections of the book with help from Kevin Anderson (Suw’s husband and good friend of Backstage). The whole thing was done over Gmail, Google Docs, Basecamp and Dropbox. The plan was to go to print with the book by Thinking Digital 2010, which was also the time when I was going to announce the closure of BBC Backstage. Of course we all know what happened in May/June to me (I had the bleed on the brain if you don’t remember).

This of course put everything in a tail spin and so we missed all the dates for printing, publishing and announcing the end of Backstage.

So fast forward to the point when I’m out of hospital and things are shifting at work. It made sense to pick up the large body of work which was almost finished back in May and put it out in the public domain. Of course this was easier said that done.

Brendan Crowther, Ant Miller and Adrian Woolard worked there socks off collecting together all the bits which were floating on these different services. Not only that, they built a small team of professionals who helped manage the process of making the ebook (as it became).

One of the things which I never got around to doing before my bleed was the design of the book. We had planned to use the newspaper club’s default templates with a little fix here and there. But Nicole Rowlands has done a amazing job stamping her distinct style into the ebook.The copy also had a rethink and re-edit by Bill Thompson and Production editor Jim McClellan. Between all these people and of course Sarah Mines everybodies favorite BBC publicist and PR Lady…

….We finally give the world Hacking the BBC: A Backstage retrospective.

BBC Backstage was a five year initiative to radically open up the BBC, publishing information and data feeds, connecting people both inside and outside the organisation, and building a developer community. The call was to “use our stuff to make your stuff” and people did, to the tune of over 500 prototypes.

This ebook is a snapshot of some of the projects and events that Backstage was involved in, from its launch at Open Tech 2005, through the triumph of Hack Day 2007 and the shot-for-web R&DTV, to current visualisation project DataArt. We take a diversion to Bangladesh to see how a Backstage hacker helped the World Service keep reporting through the horrendous Cyclone Sidr, and look at the impact of the ‘playground’ servers, used inside the BBC.

Backstage’s mandate, throughout its history, was for change. It changed the way people think, the way the BBC interacted with external designers and developers, and the way that they worked together. So what remains, now Backstage is no more? The legacy isn’t just a few data feeds and some blog posts. Backstage brought about permanent change, for the people who worked there, for its community of external developers and for the BBC. What better legacy could one ask for?

Download in [PDF] [print ready PDF] [EPUB] [MOBI] [RTF]

BBC Backstage – The End of an Era

So there’s been talk about the end of BBC backstage for a while and in certain circles its been heavily discussed.

As has been discussed recently in the press and various channels online, the BBC has taken the decision to close BBC Backstage in December 2010. Given the report recently in the Guardian Tech blog this no doubt comes as little surprise to most. However, I thought I’d take the opportunity to explain why this decision was made and what it means for the BBC as an open innovator in the future.

BBC Backstage has been a great success. I am very proud to have worked with the team on numerous projects. It was the forerunner to many other emerging, successful initiatives and has made a valuable contribution in driving the BBC towards genuine open innovation. In many ways it has been very much of its time.

More details will follow over the next few weeks but I can say…

I am not out of a job instead I’ve been planning to do more research for a while
The BBC have not done this behind my back (I’m still off work on sick leave)
We had planned to shutdown BBC backstage since May but thats exactly when I had my bleed on the brain, so everything got pushed
I had planned to do an announcement at Thinking Digital 2010 in Newcastle
I’ve been behind backstage for about 4 years and I really do care about this amazing innovative project
I’m not the only person whos been involved in its success. James Boardwell, Ben Metcalfe, Matthew Cashmore, Rain Ashford, Ant Miller and Brendan Crowther all have worked for BBC Backstage.
Also Matt Locke, Tom Loosemore, Jem Stone, Huw Williams and Adrian Woolard have managed the slippery beast which is BBC Backstage. Oh and never forget Sarah Mines the BBC Publicist whos work life was changed when she got bbc backstage as her new project.
Although there was lots of events and large scale prototypes which will be talked about over the next few months. Please please don’t forget the small prototypes, events and sponsorship which bbc backstage was responsible for, as those matter as much as the big stuff.

Hopefully over the next few months, we’ll explain the impact backstage has had on the BBC as a whole and why all good things must come to a end.

The Data Visualisation Manchester Weekender

So as you may have already seen, Data.gov.uk, BBC Backstage and Manchester Digital Development Agency (MDDA) will be running an ‘unconference’ focussing on data visualisations. The unconference will team up 100 developers and 100 designers to create diverse and imaginative data visualisations from open data. The aim of the event is to facilitate an unusual opportunity allowing the diversity of the two traditional job roles to bring together imaginative use of open data sources.

The website for more information and to sign up is dvwm.weebly.com

Whats the schedule?

April 9th will see a pre-party get together at a central Manchester venue (TBA)

April 10th will be the first day of the event complete with open sessions to help get you inspired

April 11th will be the day when you can show off your visualisation on stage

This may also help answer your questions?

It will be a mix of hackday/mashed with a unconference type event, its the same format as we have used for Over the Air 2008
There will be lots of coding, designing and general hacking.
We have secured a venue in central Manchester which will allow over night stay, so theres no need to worry about hotels on the Saturday night.
A small but good amount of food and drink will be available, but if you ever feel hungry for more theres plenty of shops and restaurants in central Manchester.
The venue isn’t far from Piccadilly station, so getting to and from the South, East and West should be pretty easy.
Anyone coming into Victoria Station should change on to the tram heading to Piccadilly.
The event is totally free but requires signup beforehand and confirmation from the organisers.
Visualisations don’t have to be just virtual, they can be physical too.
You can use the hashtag or tag – DVWM to find related stuff
Yes its in Central Manchester not Central London
Yes we all love open data

Interested designers and developers can find out more and apply for an invitation via the DVWM website.

Is the BBC’s iplayer changes, pushing developers towards the dark net?

So to remind everyone, this is my blog and not the view of my employer (the BBC). If you’ve not seen the outbreak about the iplayer stream changes then I can recommend the BBC Backstage post and the internet blog post. You will see they both link to the register piece which highlighted the problems people are having.

Here’s the Register’s summary of the whole thing.

The BBC has quietly updated its hugely popular iPlayer with a verification layer that closes the door on open source implementations of RTMP (real-time messaging protocol) streaming, The Register has learned.

The Beeb applied the update to its online video catch-up service on 18 February, just four days after Adobe Systems penned a corporate blog post about its “content protection offerings”.

The tweak means that free RTMP plugins offered by the likes of the XBMC community – whose code is based on the GNU General Public Licence (sic) v2* – can no longer stream iPlayer content. The latest iteration of XBMC’s plugin was created in May last year and was being used by UK viewers to play TV and radio catch-up content from the BBC’s iPlayer service.

XBMC.org adds to this…

While we understand the BBC’s reasoning for the decision, we surely don’t agree with it. Add to that, a publicly funded media organization has far more obligations than a typical private one.

XBMC could easily be modified in a way that would allow playback of the streams, though it could never be included in the official binaries due to the wretched DMCA.

We hope that news of this change spreads quickly. Feel free to submit this story as well as the one from The Register to your favorite news sites. If anyone from the BBC would like to engage in a public discussion, we would very much welcome it; see our contact page for details. Also, be sure to take their online survey and tell them how you feel. Remember, this change affects far more than an XBMC plugin… all open-source BBC playback implementations are at stake.

*librtmp, the library used to access these streams, uses the lgpl license.

So to be clear, I also understand the reasoning but disagree with the need for this change. This change is easily fixable/hackable/reversed but doing so would break the DMCA or EUCD. So this is a very difficult position to be in because the change is forcing the hand of the developers to do something illegal. Now most of the developers don’t and won’t do it but there are those who don’t give a flying monkey for the law and will easily reverse whatever Adobe creates in the form of DRM. This is why there is such a outrage by most people who understand the situation fully. Verification layer protection is a joke, but a really bad joke which you can’t get rid off by simply shuffling it out the front door. Cory always says…

DRM only affects people who buy media honestly, rather those who nick, borrow or cheat their way to it. In turn that means that the people who ultimately bear the inconvenience, cost and insult of DRM are the paying customers, not the pirates.

And he’s right. The people who are most effected by Verification Layer are those who are the fans watching iplayer streams on their XBMC boxes at home with there friends and family. Worst still they are already license fee payers and early adopters who the BBC really should be spending more time with instead of marking them down as a irrelevant group. This group are very vocal and have the ability to really make the BBC’s future a living hell if its not very careful.

I’ve already seen evidence of a application which strips iplayer of all its content in a slightly questionable way being pushed as a replacement for XBMC’s iplayer script. Its worth noting this application which I won’t link to worked before the change and still works after the change, in actual fact there was no interruption to its service! And if you think thats questionable, I’m sure the usage of BBC content in Bit Torrent, Rapidshare, usenet, etc went flying through the roof as people scrambled back to the dark net to watch there shows. I do wish there was a way to prove this in numbers, just to show how much streaming from the BBC was having an affect on the dark net.

So where do we go from here?

Will the BBC ever turn off Verification layer? Honestly I doubt it and as Adobe creates even more technical hurdles they will also be added. Its a real shame because as we’ve already explored they only effect those who care enough to get there content from the BBC iplayer. Adobe’s measures have no ground in the dark net.

The Trust survey is very important, as that has a massive effect on what the BBC can and cannot do. So its very important that everyone takes part in the survey. Its also worth writing blog entries and telling more people about the issue. This doesn’t only effect xbmc but also all those mobile clients and other media centres. There’s been a lot of comments at the register, iplayer forums, internetblog, backstage forum and backstage blog but not nearly enough posts and twitters.

Finally the BBC needs to talk openly about this stuff, if it was announced this was coming and explained then I honestly I think the BBC wouldn’t get the kickback there getting now. Look at the iplayer forum, who on earth blamed the iplayer RSS terms and conditions for this problem? Yes I’ve been talking to the guys at XBMC and other projects, the BBC needs to build bridges with these communities and at least have a conversation about this stuff. No promises just conversation.

BBC.co.uk 2.0, why it will happen

So since my post in reply of Jason's post there's been a lot of discussion and conversation. Technorati as usual doesn't quite get as close as Google. Either way, its the emails and im's I've been getting which are also interesting. Most people have been really supportive, while others have been less that supportive. They felt I was slagging off the BBC and making things worst by talking about my own views. I mean how dare I express my own personal views on my own personal blog right? The same blog which has the subtitle, The views and thoughts of a dyslexic British designer/developer. Anyway, its late again but I'm going to finish what I was writing before as somethings were not explicit.

When out and about people ask me many things about the BBC, one of which is about the iplayer. Even in Boston, people once they know you work for the BBC wanted to know more about the decisions which formed to create the iplayer. They ask if I use it myself and I say no. Most ask why, and I try and explain my media consumption diet in a short period of time. But the main point is people ask, I'm sure all BBC employees get this? Its great, people are very interested in consuming BBC content and services but are very puzzled about the whole DRM issue. They ask why would a public broadcaster apply DRM to its content? Some more clued up people ask the same question and then point out that our analogue and dtv content has no such restrictions. Yes the BBC puts out press releases and has a official website with discussion boards (not indexed by google), but people still ask. So I put across the point of most of the content we play on TV, we only have broadcast rights to and that indies own a good proportaion of the content rights which goes out. However the question remains why DRM?

Some of my non-supporter, seem to think its just the geek world which are upset about this. Well we have to remember its the geeks which are fixing and installing stuff on their parents computer come Christmas time, geeks that are willing to test drive a beta service/product like iplayer and finally geeks who lead the way into the mainstream market. So thats a sure reminder not to just write off this stuff to geeks. However what also prompted my other post was this video by Robert Llwellyn. Its a rant and his own view but its interesting to note, like I have done up till now, Robert bundles the iplayer into one. Yes and that is the vision but has also wound people up royally. So to explicit here, when I say iplayer is a mess and I'm sure when most people say they hate the iplayer, its not because of the system behind it or the interface or the delivery system or even the quality of the video. No its all down to the DRM. The DRM is so attached to the iplayer, and because of it over 2mins of Roberts rant was about DRM in iplayer.

The iplayer team have worked damm hard on a good solid product/service and are hearing lots of negative comments about the iplayer when actually people mean the DRM. However, because the whole service is robustly built, I'm sure it will out live its current form and who knows whats around the corner?

Right to address, if I should be talking on my blog about this stuff. This seems to rub a lot of people up the wrong way., some seem to think I might be bigging myself up at the expense of the BBC. Well I'm not and I'm not going to let you guys bring me down. I love working at the BBC and love my job, its ground breaking and I go places and speak to people most never get a chance. So, I want to make meaning and I believe the BBC is capable of moving into the next curve with its unique funding model. Unlike Jason, I think its unique public funding model will be an advantage over the advertising or subscription models. Oh at the same time can I make it clear I was disagreeing with what Jason was blogging about. So why write anything at all? Its the Cluetrain effect. Things have changed. Take a look at the difference between the Newswatch and the editors blog. Its not so much about the layout but more the conversation or voice. So rather than talk any more, here's a few Cluetrains which sum up what I'm getting at.

#3 – Conversations among human beings sound human. They are conducted in a human voice.
#10 – As a result, markets are getting smarter, more informed, more organized. Participation in a networked market changes people fundamentally.
#12 – There are no secrets. The networked market knows more than companies do about their own products. And whether the news is good or bad, they tell everyone.
#14 – Corporations do not speak in the same voice as these new networked conversations. To their intended online audiences, companies sound hollow, flat, literally inhuman.

#34 – To speak with a human voice, companies must share the concerns of their communities.

Some good examples, Wikipedia entry on the iplayer, Imp's ultimate review of the iplayer, E-petition and Currybet's first 14 days.

So at the end of day, iPlayer is just the start (and in beta), over the next few months you will see a BBC which will silence its critics and launch a range of services which will impress. Transparency and conversation is important and it will take time for everyone to adjust but with time… BBC 2.0 it will happen. Look at projects like Backstage, Innovation Labs, TV Backstage, BBC Blogs, etc… to get a feel of the changes starting to happen.

Comments [Comments]
Trackbacks [0]

Is the BBC Backstage podcast the first CC licenced piece from the BBC?

Michela Ledwidge asks the question, and we racked our brains and did a lot of searching. I think it might be, but I can't say for sure. If thats not a first, using blip.tv is certainly a first. And to be honest, if it wasn't for the ability to…

Set the license (creative commons attribution 2.5 in this case)
Pipe content to Archive.org for permanent storage and to the benefit of generations to come

We would have never have consider it. Maybe we've been drinking too much of Lessig's kool aid. Although I was a little worried about the Blip.tv EULA. But Mike at Blip says,

As far as the EULA, we don't own all the rights. Don't want them. We need to find a way to make that even clearer. When you upload you give us the rights to create derivative works (for thumbnails and transcoding) and to distribute (i.e. make available for download). Those rights go away when you delete the content from blip.

Another reason why the archive.org angle is very important. If Blip.tv ever pulled a Yahoo/Flickr thing on its users. You could pipe them all to Archive.org and remove them from Blip. Metadata and all..

Comments [Comments]
Trackbacks [0]

The reaction to the first Backstage podcast

The first ever BBC Backstage podcast has caused a quite a stir. Some of it negative and some of it positive.

Generally the reaction to the podcast is positive but Ben did say he felt Backstage shouldn't be hosting such a debate. Its bigger that Backstage and should be taking place somewhere else. Fair enough, but till then backstage is where it will stay for now.

Before coming to Cory's thoughts on the BBC and DRM, I thought I'd better cover some of the other points from others first. Upyourego loves the podcast too and makes a good point about the lack of RSS like Tom Morris. Adam, Brian, Superfly
picked it up and so does Euan Semple, who is surprisingly quiet about it. But some of the comments left are interesting, including one from Cory. Weird Cory didn't post any comments to mine or Ben's
blogs entries.

Corys post to BoingBoing is over the top. I love Cory but he took a few points from the podcast and went to town on them. He threw out most of the other stuff which made it a much more balanced debate. For example,

You can hear the disappointment in the visionaries at the BBC, the betrayal at being sold out by management. The BBC is forcing Britons to buy an American operating system — Windows — in order to watch British programming, made in Britain. The free and open GNU/Linux — whose kernel is maintained in Britain — can't be used for British TV, because of DRM.

Well yes there was something in the air but we're positive about making things right and turning things around. Open DRM is one of many things discussed but Cory doesn't mention this. Tom has a comment which I don't quite get, but I'll ask him tomorrow.

Arstechnica does a much better job at reporting a more balanced view of the podcast. Although the title is misleading – BBC explains decision to go with Microsoft DRM.

The brouhaha surrounding iPlayer makes for some good reading, but more interesting is the podcast. The BBC engineers on the show come off as intelligent, affable folks who don't like content restrictions any more than consumers do. They're also fully aware of recent technologies like Ogg Vorbis, BitTorrent, and SlingBox. For those curious how DRM and rights decisions are made behind the scenes at a major public broadcaster, this is definitely worth a listen.

A couple of good comments follow too.

That's an amazingly insightful podcast! Thanks!

Which company has used DRM longer, the BBC or Apple? Just because Jobs uses DRM and then says “but we shouldn't” doesn't mean a thing. Well, depending on how gullible you are. It's about as meaningful as Google's “do no harm”. Actions speak louder than words.

Currently Digg and Slashdot have yet to pick up the podcast or its reactions. Oh it looks like we'll be uploading the video this week.

Comments [Comments]
Trackbacks [0]