Arne Babenhauserheide (2017-02-20 22:12:59 +0100) wrote:

> Hi Ivan, Dear Hackers,
> Aside from the web-apps part, Freenet can already provide everything
> you asked for.

Hi Arne, thanks for the insights and the links.  Please note that the
current CENO project is actually using Freenet as a signalling and
storage backend!`:)`

> Ivan Vilata-i-Balaguer <> writes:
> >   1. Content is available under censorship conditions, ideally even
> >      after connection to the Internet has been completely cut for a
> >      whole region.
> If you still have IP-based connections to people inside the region, this
> is the case, if you run a specialized darknet within that region (so
> content only gets replicated within the regional net).
> There are already tools to make automatic Freenet connections. Talk to
> Michael Grube (thesnark).
> For auto-spawning Freenet nodes when an application is started, see
> For communication with sub-5-minute latency from external programs, see
> (I submitted a project plan for improving this to NLnet which shows what
>  would have to be done for an uncensorable and attack resistant
>  news-network. It got into the short-list but wasn’t selected for
>  funding: )

That looks like a very interesting system!  CENO already includes some
RSS feeds from selected sites, I'm not sure how this would aling with
the particular requirement (we were focusing more in web sites), but
it's without doubt an innovative approach.  Thanks for sharing it!

> >   2. Censored content is made available within a reasonable time.
> Just ask someone to run
>     copyweb -d <folder> <URL>; freesitemgr add <folder>
> Or integrate that functionality into a program. You might want to use
> beautifulsoup to clean up the code for the Freenet content filter, i.e.:

CENO currently uses [bundler](,
which does a similar task.  Thanks for the hints!

> >   3. Access to censored dynamic content (i.e. web apps) is possible.
> That’s a hard one. You’d need to remodel the web apps to use Freenet as
> backend instead of the clearnet.
> I do not think that it is possible at all to provide anything which uses
> Javascript and at the same time preserve the anonymity of your users.

Yeah, that's a hard one, that's why we may probably end up combining
several tools.

> >   4. The system benefits from the user's participation, and is resistant
> >      to participants dropping off and to rogue nodes in the hands of the
> >      censor.
> Resilient yes, for absolute resistance, you need to replicate
> everything, which limits the amount of data you can provide.
> >   5. Users of the system are anonymous to someone observing their
> >      traffic, even if that someone is a participant in the system.
> Jepp. A weak yes for automatic connections, a strong yes, if they
> connect to people they know.
> >   6. Users' devices don't reveal the content that they or other users
> >      have accessed.
> Jepp (as long as you use a separate browser in incognito mode).
> >   7. The system is amenable to privacy-preserving analytics to check its
> >      impact.
> Jepp.
> i.e. — though it’s currently in sleep mode,
> there’s a new site for that in Freenet: 

Wow, these a very useful links, thanks!

> […] PS: I’m only a few more hours away from being able to do proper
>     Freenet releases, so we can finally deploy improvements to the
>     freenet core again.

Cool, good luck with that, and thanks again for the very informative

Ivan Vilata i Balaguer
Support mailing list
Unsubscribe at

Reply via email to