General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] decentralized web conference next wed-thur in San Fran
Date: Wed, 8 Jun 2016 09:54:15 +0000	[thread overview]
Message-ID: <82AB329A76E2484D934BBCA77E9F5249AF322C78@PALLENE.office.hd> (raw)
In-Reply-To: <CAA93jw51TQZrfYNtSMjb-CcOQE-2hUMyDv4hxzvCM17FJ6yauA@mail.gmail.com>

Hi Dave,

> LF is also co-ordinating a significant investment into blockchain technology.
> 
> http://www.linuxfoundation.org/news-media/announcements/2016/02/linux-
> foundation-s-hyperledger-project-announces-30-founding
> 
> But I don't think the blockchain is core to distributing the web.

Yes, I agree. The word "blockchain" in the URI is a relict from a meeting where distributed Internet/Web was discussed in a blockchain application context (assuming that digital contracts between non-trusting parties would be useful).
 
> Brewster has a vision that he articulated here:
> 
> http://brewster.kahle.org/2015/08/11/locking-the-web-open-a-call-for-a-
> distributed-web-2/
> 
> and things like ipfs are running code today, and things like ccn continue to
> evolve. People are using bittorrent to distribute all the science articles in the
> world, also, (from scihub, which is fighting takedown issues left and right) - I was
> surprised to see so many seeders of 36TB of data - but I suppose some really,
> really do want to have their own copy of all the published knowledge of the
> world.

Yes, interesting developments. We are currently planning for another meeting around these topics (distributed/federated web, links to ICN) at the Berlin IETF (will be announced on din@irtf.org).

Cheers,
Dirk


 
> https://news.ycombinator.com/item?id=11093779
> 
> Should be a fun conference!
> 
> > Best regards,
> > Dirk
> >
> >> -----Original Message-----
> >> From: Bloat [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of
> >> Dave Taht
> >> Sent: Samstag, 4. Juni 2016 00:10
> >> To: bloat
> >> Subject: [Bloat] decentralized web conference next wed-thur in San
> >> Fran
> >>
> >> It looks like there is still room for more attendies.... Vint Cerf,
> >> Cory Doctorow, Brewster Kahle sharing a stage... and me in the back,
> heckling.
> >>
> >> http://blog.archive.org/2016/05/19/join-us-for-the-first-decentralize
> >> d-web-
> >> summit-june-8-9-in-sf/
> >>
> >>
> >>
> >> --
> >> Dave Täht
> >> Let's go make home routers and wifi faster! With better software!
> >> http://blog.cerowrt.org
> >> _______________________________________________
> >> Bloat mailing list
> >> Bloat@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/bloat
> 
> 
> 
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org

      reply	other threads:[~2016-06-08  9:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 22:10 Dave Taht
2016-06-07 12:03 ` Dirk Kutscher
2016-06-07 15:11   ` Dave Taht
2016-06-08  9:54     ` Dirk Kutscher [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=82AB329A76E2484D934BBCA77E9F5249AF322C78@PALLENE.office.hd \
    --to=dirk.kutscher@neclab.eu \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox