The Stupidly Simple Open Media Network

A common database of media metadata exchanged by RSS in and out, using open industrial standards and neutral unbranded widgets.

2. Is anyone doing something like this now and how is your project different? (30 words)

There are many aggregators of news (eg http://daveriver.scripting.com/, or http://ignoregon.com) but they aggregate with whole rss feeds not tags, and new tag feeds cannot be created out of them. Closed-source project vodpod works by tag only as a premium feature.

3. Describe the network with which you intend to build or work. (50 words)

visionOntv (a project for distributing social change video) already smart-aggregates 18,000 videos by RSS. Working with this already curated database we can build an exemplar node with de facto open standards.

The project is a distributed database of the human-moderated metadata of user-generated subject areas, making the choice of this exemplar database appropriate.

4. Why will it work? (100 words)

  • Aims to build a big network, but starts small.
  • Has multiple redundancy by sharing data via RSS in/out.

Incentives for users

  • they can publish once on their own site and the content appears on a range of other appropriate subject sites.
  • No single hub, no single owner, but rather a horizontal network of nodes. Every node can be a hub (an aggregator). This social/psychological understanding of the need to give people ownership means the project can spread easily.
  • Spam is user-policed out of networks.

Open industrial standards

  • RSS and atom are used as the database exchange format, as it is almost universally implemented. The leveraging of existing open standards means that 3/4 of the web can already talk to it. Thus we can build a scalable, common, decentralised database.
  • We implement both of the realtime RSS standards PubSubHubbub and RSSCloud
  • End-users view videos through auto-updating video player widgets driven by boolean logic.
  • In the future, it would be possible to radically decentralise where the content is itself hosted, using p2p media-serving in parallel with traditional corporate streaming.

5. Who is working on it? (100 words)

6. What part of the project have you already built? (100 words)

We already have the content and much of the metadata for exemplar node visionOntv. There is a database of 18,000 curated and tagged films. Beginning with this node which we control, we can test solutions to UI / security / spam etc issues. And have a practical outcome with embedded media players. We already have one on every page of UK based New Internationalist magazine’s sitehttp://newinternationalist.org

7. How would you sustain the project after the funding expires? (50 words)

Flattr is implemented on every page. As a distributed project, it has very low running costs. It would be up to the individual nodes to solve this for themselves. We have a micro-(hyperlocal) advertising model for funding the visionOntv node.

Old UPS battery for solar setup

Published Date 3/10/12 10:16 PM

Am testing out a load of solar gear in my back garden, have a old 17AH lead acid battery from a UPS, trying to find out if it will hold a charge. You have to keep batteries topped up with power otherwise they deteriorate over time.

UPDATE: it did not hold a charge I had to go out and buy a new battery from maplins, which works fine.

UPDATE2: I damaged the new battery so have to replace that, by charging it with out a charge controller, was using a volt meter to keep an eye on its level manually, but it only took one time forgetting and leaving it out in the sun to damage the battery – get a charge controller as human beings are prone to fail (:

Why indymedia has the site is untrusted message

Published Date 3/8/12 9:13 PM

Have you always wondered why IMC sites have the horrendous go away this site is dangerous message in most web browsers. Its because of this:

—– START Explanation from ****, **** —–

Security is a two-way street. When I go to a web site I have to prove to the web site that it’s really me before the web site gives me access to anything private or restricted (such as access to my email). The most common way that is done is via a login in which I provide a username and a password. Because I supply the correct password, the server knows it really is me, because I’m the only one who knows my password.

But how do I know that the server I’m going to really is the server I want to go to? Just because I type https://docs.indymedia.org/ into my browser, doesn’t mean that the server really is the Indymedia server that I think it is. Any number of things can happen via the Internet between my computer and the server I’m connecting to that might fool my computer into thinking I’m connecting to docs.indymedia.org when in fact I’m connecting to someone else’s server specifically setup to look like the Indymedia server. If that were to happen, I might type in my username and password on this stranger’s server that is acting like docs.indymedia.org, essentially handing over my identity to a stranger.

The purpose of security certificates is to ensure that the site I’m connecting to really is the one run by Indymedia.

Unfortunately, the technology for setting up this system is fundamentally flawed. It works like this:

* most major browsers, even free/open source ones like Firefox, are pre-configured to trust a pre-defined set of for-profit corporations to verify the identity of all web sites on the Internet.

* web site maintainers are expected to pay $75 or so to these corporations in exchange for a digital certificate verifying that we are who we say we are.

* once this digital certificate is installed on the web server, browsers will access the secure web site without any errors.

If you don’t pay $75 for the certificate, then most people will get a security error. There’s a word for a setup like this. It’s called a “racket.”

Rather than play this racket, Indymedia uses cacert.org to sign it’s security certificates. cacert is a nonprofit organization that signs certificates for free. cacert is not pre-installed on most browsers, however, you can install it by following the directions here: http://wiki.cacert.org/BrowserClients If you install the cacert certificate, your browser will automatically trust all indymedia web sites that have been signed by cacert, so you will no longer get any error messages when you access them. However, in addition, your browser will trust *all* web sites signed by cacert (which could be a good thing or a bad thing depending on how cautious you are).

—– END Explanation —–

So, this addresses the “problem” that many of us experienced for many years. Its actually a nice opportunity for political education!

However, my understanding is that since last summer, even this explanation won’t completely address the problem with the global site… I consulted with a few people offlist before responding to this because I didn’t want to add to the confusion. It appears that our security certificate for the global server has explicitly been revoked – see: https://lists.indymedia.org/pipermail/imc-tech/2011-June/0602-g4.html It appears that this may have taken place in conjunction with the conflicts in the UK group. So, even if you import the cacert certificate to your browser (following the instructions below), you may still get a problem connecting to the site. I’m not sure if this means that we can never again have a viable certificate through cacert or whether we have to purchase one from the racket that **** refers to?

Hope this is helpful, ****

Turning off the comments

Published Date 2/28/12 1:34 PM

This is a video response to Dave Winer’s post on Scripting News about why he has turned off commenting on his blog.

Winer was using the comment platform Disqus and discussed with the developers to have some options implemented. He got frustrated at the end when he realised he could never get from them the right functionalities and turned off the comments.

At visionOntv we have ideas about how to deal with comments and we’ll give practical proposals very soon in the videos to come.

Meanwhile we’d like to hear from you on this subject. Is it still a blog if no comments are allowed? Where is the conversation and debate then supposed to happen? What solutions have you tried on your blogs? Are you using an external comment platform or any form of moderation? And do you have a specific strategy for Youtube comments to bypass the daily abuse, auto-promotion and trolling?