☆ Now Accepting BitCoin

As an experiment, I’ve set up BitCoin on one of the systems here at Webmink Central. BitCoin is a peer-to-peer digital currency, with no central bank or authority. Instead, it relies of a mesh of collaborating but independent computers sharing copies of a set of data.

Assuming it is secure and works, it’s exactly the kind of system we need to remove the bottleneck of online financial transaction needing to be translated into the terms and systems of the old economy. Not least, it overcomes the problems caused when an individual, company or government over-steps their authority and shuts down a payment bottleneck, as just happened to Wikileaks.

The idea of a digital currency is very appealing, but to get it bootstrapped some of us need to actually start using it in the fledgling economy. If you’d like to support my writing and speaking activity, please send BitCoin donations to address 1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3 and once there’s a modest balance I’ll start trying to use it to pay the bills. Thanks!

☆ Small Is Beautiful – wmk.me

New Forest DonkeyOn a whim I decided to go look for a domain name for my own link shortener. Within a few minutes I’d found that wmk.me was available, and even better that GoDaddy were selling it for $8.99 for the first year. I grabbed it and then went looking for something to do with it.

I have a Google Apps account for hosting some of my activities, and I discovered they have added a Google Labs link shortening service. It was very easy to set up, but its main drawback is they only allow link shortening using a subdomain. If you see any links for me on the domain l.wmk.me they are hosted by Google.

I then spotted that my current favourite link manager, bit.ly, offers a bit.ly Pro service which allows you to use your own domain with bit.ly – everything else is the same as the normal service and it gets used automatically. I requested access to the service and heard back from them within a few hours. It was extremely easy to set up as well – although one part took a day waiting for DNS to propogate changes that verified my domain ownership – and I’m very pleased with it. Any links on wmk.me are hosted there, and I’m able to use both it and Google’s service at the same time.

The one gap in both services is what happens if (when) I decide to migrate away. I don’t intend to use these short links in any non-transient context, but it would be good to know that there is a workable export option available on both services so that I am free to leave. But for now I have a new toy to play with. It’d the small things that provide the best entertainment.

☝ Defending Wikileaks’ Ability To Exist

Logo used by Wikileaks

Image via Wikipedia

Let me say up front that I am not a massive fan of WikiLeaks. It seems to me that taking stolen correspondence and publishing it for everyone to read is a fundamentally sociopathic act, whether it is a rival’s love-letters or a government’s diplomatic cables. There’s no doubt that there’s a role for whistle-blowing journalism, but each betrayal of trust and privacy needs to be justified by the greater good it delivers, and I remain unconvinced that the cloud of hacktivists at WikiLeaks has taken on board that the demand for great responsibility to accompany great power also applies to them.

For me, it falls into the same category as The Pirate Bay; there’s plenty to disagree with in what they are doing, but the crisis they provoke is fundamental to the operation of the Internet. In reacting to WikiLeaks and The Pirate Bay, both business and government have shown their true colours when it comes to citizen liberty and software freedoms. What’s disclosed is not pretty.

Read on over at ComputerWorldUK

☝ Crowdsource is not open source

I’ve heard a few conversations in the last week treating open source interchangeably with crowdsourcing. Despite sounding the same they are very different, and the key difference is the ownership of the outcome. Open source is not the same as crowdsourcing because open source community members are stakeholders whereas crowdsourcers get less than sharecroppers.

Read on at ComputerWorldUK

☆ The case for “rossio”

Raucous Currawong[Versão em português no final – Portuguese version at the end]

“When I use a word,” Humpty Dumpty said, in rather a scornful tone, “it means just what I choose it to mean — neither more nor less.”

In translating my article “Community Types” into Portuguese, Bruno, Ana and I ran into an interesting challenge. I frequently refer to the “free software commons” that is at the heart of any open source community, meaning the pool of software under an open source licence that community members collaborate to maintain. In English, I use the word “Commons” more as a reference to its American English usage, popularised for cultural artefacts by the Creative Commons movement, than to the original English usage which related to a resource shared by a privileged and select few.

But in every-day Portuguese, the concept seems to be largely absent. The most common practice is to take a phrase like mine and leave it untranslated (“Commons do Software Livre”), or to use a phrase like “bem comum” (“communal property”). Neither is satisfactory. The former lacks the cultural echoes necessary to give the term depth of meaning. The latter frankly sounds weird, both in Portuguese (“bem comum do software livre”) or English (“communal free software property”).

None of us knew what to do, but before the seemingly inevitable compromise I asked on Identi.ca. Fairly quickly FSF-LA’s Alexandre Oliva came up with a great answer. He pointed us to a paper by the late Professor Imre Simon proposing the adoption of a somewhat defunct term from European Portuguese, “rossio”. The word has a historical origin meaning exactly the same as “commons” and is used as the colloquial name for the central square in Lisbon, but seems unfamiliar to all the Portuguese-speakers I have asked. Indeed, the paper itself says:

Para começar, vale esclarecer nosso título, que sem dúvida soa enigmático. O que é o rossio não-rival? (Before we get started, we should clarify our title, which may appear somewhat enigmatic…)

We then heard from one of the co-authors of the paper, Miguel Vieira, confirming that the term “rossio” was indeed coined in this context for just the purpose I was suggesting. The fact that “rossio” is not understood by most Portuguese speakers today need not be an obstacle; the term “commons” used to describe a shared software repository or cultural asset was just as unfamiliar to many English speakers until Creative Commons repurposed it and indeed remains unfamiliar to many today. Language grows when people choose to attach meaning to a word.

Given the regard Professor Simon is held by the people I have spoken to, both as an educator and as a software freedom pioneer in Brazil, it seems highly appropriate to pick up his suggestion – as we hope others will do – and appropriate the term “rossio” to mean “commons” throughout my writing. So that’s what we intend to do in future.



Em defesa do “rossio”

“Quando eu uso uma palavra,” disse Humpty Dumpty, em um tom de desdém, “significa exatamente o que eu escolhi significar — nem mais nem menos.”

Traduzindo meu artigo “Community Types” para o português, Bruno, Ana e eu encontramos um desafio interessante. Eu frequêntemente me refiro ao “free software commons” que está no coração de qualquer comunidade software livre, e que significa o conjunto de software sob uma licença livre e que membros da comunidade colaboram para manter. Em inglês, eu uso a palavra  “Commons” mais como uma referência ao seu uso no inglês americano, popularizado para artefatos culturais pelo movimento Creative Commons, do que o seu uso original do inglês britânico que se refere a um recurso compartilhado por uns poucos privilegiados.

Mas, no português do dia a dia, esse conceito parece ser inexistente. A prática mais comum é manter uma frase como a minha e deixá-la não traduzida (“Commons do Software Livre”), ou usar uma frase como “bem comum”. Nenhuma das opções é satisfatória. A primeira perde os ecos culturais necessários para dar ao termo o significado profundo pretendido. A segunda parece estranha, tanto em português (“bem comum do software livre”) ou em inglês (“communal free software property”).

Nenhum de nós sabia o que fazer, mas antes de fazermos uma escolha aparentemente inevitável, eu perguntei na Identi.ca. Rapidamente Alexandre Oliva da FSF-LA nos trouxe uma ótima resposta. Ele indicou um artigo do falecido Professor Imre Simon propondo a adoção de um esquecido termo do português europeu, “rossio”. A palavra tem a origem histórica que significa exatamente a mesma coisa do que “commons” e é usado como nome coloquial da praça central de Lisboa. Infelizmente, é um termo desconhecido por todos os que falam português que eu contactei. Mesmo o artigo concede isso:

Para começar, vale esclarecer nosso título, que sem dúvida soa enigmático. O que é o rossio não-rival?

Nós entao recebemos a informação do co-autor do artigo, Miguel Vieira, confirmando que o termo “rossio” foi de fato usado nesse contexto exatamente para o propósito que eu estava sugerindo. A realidade de que “rossio” não é uma palavra conhecida pela maioria dos que falam português hoje não precisa ser um obstáculo; o termo “commons” usado para descrever um repositório compartilhado de software ou um conteúdo cultural também era desconhecido para muitos que falam inglês até que a Creative Commons aplicou o termo com esse novo propósito, e até hoje ainda é um termo desconhecido para muitos. A língua cresce quando as pessoas escolhem aplicar um significado a uma palavra.

Dado que todos com quem conversei tem grande respeito pelo Professor Simon, tanto como um educador, mas também como um pioneiro da liberdade de software no Brasil, nos parece altamente apropriado usarmos sua sugestão — como esperamos que outros farão — e passar a utilizar o termo “rossio” como significado de “commons” em todos os meus textos. É isso que pretendemos fazer no futuro.

☂ Open Source Monetisation Essay Posted

My essay asserting that open source projects aren’t about giving stuff away for free is now available from the Essays section.

☂ O Artigo “Tipos de Comunidades” Agora Disponível em Português

O artigo “Tipos de Comunidades” está agora disponível traduzido para o Português na seção Essays. Muito obrigado a Ana Whitby por doar seu tempo.

☂ Artigos em Português

Iniciando um esforço de disponibilizar o conteúdo dos artigos do Webmink em outras línguas, começamos hoje a postar as traduções para Português Brasileiro. O primeiro artigo, Liberdade de Software Significa Benefícios para as Empresas já está disponível.

Em breve, outros artigos serão disponibilizados!

☂ Essays Now Creative Commons Licensed

I had a request on Identica to make one of my essays available under a Creative Commons licence so it could be translated. I thought that was such a good idea I’ve now applied a Creative Commons licence to the whole Essays section. I’d welcome any translations and will gladly post them alongside the originals with attribution.

Sharp-eyed free-culture mavens will note I have used CC-BY-SA-NC. I’m actually perfectly happy for commercial uses, but past bad experience with a certain commercial user exploiting my work in a way I regarded as unethical have left me wanting to check each commercial use in advance. It’s entirely possible I can be talked out of this, but the distaste for that episode remains strong.

☂ H.264 Essay Posted

My essay unpacking the meaning of ‘free’ H.264 licensing is now available in the Essays section. It provides a case study in why apparently fair “Reasonable and Non-Discriminatory” (RAND) terms for licensing patents in standards actually have the potential to be costly and obstructive for software developers and a barrier to software freedom.