I kinda thought that but wouldn't a better way to solve this problem be at
the protocol layer and not the infrastructure?

i.e. httpf or httpfs, smtpf, imapf, dnsf, etc.

I care more about my message (and communications) being "free" (as in beer
and speech) than the hardware (and OS) it traversed.

So in a world where you had a mix of "free" and commercial infrastructure
(which seems realistic), my "free" data (communication) would be routed
accordingly.

???


On Tue, Jul 5, 2011 at 3:10 PM, Gustin Johnson <[email protected]> wrote:

> We are talking about building a free as in speech alternative to facebook
> and twitter.  We have the low cost hardware, we have a free as in speech OS
> as well as a solid free (again as speech) stack on top of that.
>
> The problem was that the protests in the Arab world were largely organised
> on Facebook and Twitter.  These represent single points of failure and
> censorship.  The idea is to have a federated, free and open solution to
> replace this that can't be as easily taken down.  Think Identi.ca but for
> facebook.
>
> It is not just Facebook, there are all sorts of hosted (aka "cloud")
> solutions that we have little ultimate control over.  It just makes sense to
> have an open and federated alternative.  There are a lot of pieces already
> in the works, like Identi.ca and Feng office, and so on.  There just is no
> co-ordinated platform to compete with Google Apps/Google+, Facebook etc.
>
> Sent from my Android device.  Please excuse my brevity.
> On Jul 5, 2011 2:15 PM, "Greg Saunders" <[email protected]> wrote:
>
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
>
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to