zz1

Alternative links:

http://www.takepart.com/internets-own-boy

https://www.youtube.com/watch?v=vXr-2hwTk58

https://freedocumentaries.org/documentary/the-internet-s-own...

The CCC built a distributed CDN, so nope, that wouldn't help: my video is loading from netcologne.de, for instance (in a 'video' element, which is appreciate, from my point of view).

Just keeps spinning.

Sounds like what happens to me when opening the page. Did you try to click on 'Video' tab or on the 'Play' button? It started the video for me.

/* And here are the download options: https://media.ccc.de/v/32c3-7435-replication_prohibited#down... */ That doesn't translate well. Click on the download tab, you'll find video and audio, direct download and torrent.

I use Tor for regular use. Could you provide more detailed instructions for #3? I would like to consider setting up this option.

Not everyone has the same threat model, not everyone needs all of that. Johnny can encrypt.

https://twitter.com/AlecMuffett/status/608006725040365568

The arguments made by Alan Eliasen seem worth considering to me. And his tutorial is great.

http://futureboy.us/pgp.html

Pay developers millions of dollars internally then they release what they work on as open source code.

What do they release as open source code, apart from TextEdit? I am really surprised by your comparison since it seems to me that the two (bash, vim, top, netcat… and Apple's open source code) do not compare at all.

Also available:

DietPi http://dietpi.net/

Minibian https://minibianpi.wordpress.com/

Both Raspbian-based

And, in just 80MB, Slitaz-ARM http://arm.slitaz.org/

Though I don't know if the latter has SSH enabled by default.

Except that isn't Sorrentino's last film. And both Youth and La grande bellezza are beautiful movies.

You could also catch BadUSB...

Which isn't bad: your method works against lexical analysis (which as Bill Binney said is terrible because it buries analysts under too much material), while this method is against the three hops policy.

Please, do not forget that encrypted e-mail should not be predictable: https://futureboy.us/pgp.html#GoodPractices

They should register here: http://db.ffdn.org/ !

The UX is not the biggest issue, but rather the buggy library it is based on. There is an alternative: https://jitsi.org/

https://fix-macosx.com/

You are right, but for that to happen, AOO should ship code, which is not doing at the moment, AFAIK.

In order to be easier to pwn!

Seeing who is building this project, reading their quotes, I see more reason for concern than for rejoice.

For some reason, I can't navigate to the linked URL (http:// https://itunes.apple.com/us/app/jam-on-music-player-play-+/i... )

Oh, well, now I see: you might want to take out http://

https://itunes.apple.com/us/app/jam-on-music-player-play-+/i...

Same purpose: http://localflow.co/

This whole T-agreements are way beyond madness.

Great example of the importance of diversity!

I hope it gets funded!

Good choice: I can second this opinion, since I was too under the impression that OTR was used.

But is still a close ally of the US when it comes to intelligence.

But certainly the water is filtered before reaching homes, considering it rests a long time in a open reservoir. So you could remove the dead algae. Still, they certainly have a "better dead" approach, wanting the reservoir to be a dead pool instead of a living ecosystem where they'd have to monitor what is growing and how dangerous it might be.

They have space, and they conceived this system, like many others, thinking of what was the easiest thing to do, disregarding a low-maintenance approach.

Well, there is a difference from "we do this" and "we have been mandated to do this", whatever the reason "to do this" might be. I guess that explaining they were forced to cover the reservoir makes me appreciate the solution even more: given an order, they found an intelligent and efficient solution.

I guess that the area to cover is very wide, and having a tarp that size can be expensive. And then you still have to manage it in order to tolerate the weight of rain water, leaves and sand that would eventually gather upon it.

I wonder who is to blame: big players too interested in harvesting more data (clearly not thinking about Facebook and Google here), or lazy developers?