I advice you all to read about IPFS at

https://ipfs.io/

and

https://techcrunch.com/2015/10/04/why-the-internet-needs-ipfs-before-its-too-late/

A D frontend is lacking... :)

More details at:

https://github.com/ipfs/papers/raw/master/ipfs-cap2pfs/ipfs-p2p-file-system.pdf

On Sunday, 14 August 2016 at 21:21:25 UTC, Nordlöw wrote:
> I advice you all to read about IPFS at
>
> https://ipfs.io/
>
> and
>
> https://techcrunch.com/2015/10/04/why-the-internet-needs-ipfs-before-its-too-late/
>
> A D frontend is lacking... :)
>
> More details at:
>
> https://github.com/ipfs/papers/raw/master/ipfs-cap2pfs/ipfs-p2p-file-system.pdf

I mentioned IPFS here some time ago and said it even has JavaScript, Go had front-end, apparently no one saw the potential just like no one respondent to your thread. Too bad though :( IPFS is the future.

Always chasing after mainstream ...

On Sunday, 14 August 2016 at 21:21:25 UTC, Nordlöw wrote:
> I advice you all to read about IPFS at
>
> https://ipfs.io/
> ...

It sounds interesting but what concerns me is the lack of attention given to privacy and anonymity, two things that should be core values and top priorities for any protocol that intends to supersede the HTTP protocol. If that wasn't bad enough, this protocol would archive everything on the web and the idea of an internet that "never forgets" is very disconcerting.

On Sun, 14 Aug 2016 21:21:25 +0000, Nordlöw wrote:
> I advice you all to read about IPFS at

When you're trying to sell something to people, it makes sense spend at least one sentence describing the thing you're selling.

Quick description:

* IPFS is a distributed peer-to-peer file store.
* Files are addressed by hash rather than name.
* There's an HTTP interface so you can host websites with it.

Obvious points:

* When you request data, the request is routed to a random set of
strangers.
* It shares your request history with others by telling them that you
have data on your computer that they are interested in.
* sha1 collision attacks are bad news for IPFS.

What's so compelling about it? It's basically bittorrent that can fetch data in order.

sounds suspiciously like FreeNet.

On Sunday, 14 August 2016 at 22:07:31 UTC, Karabuta wrote:
> On Sunday, 14 August 2016 at 21:21:25 UTC, Nordlöw wrote:
>> I advice you all to read about IPFS at
>>
>> https://ipfs.io/
>>
>> and
>>
>> https://techcrunch.com/2015/10/04/why-the-internet-needs-ipfs-before-its-too-late/
>>
>> A D frontend is lacking... :)
>>
>> More details at:
>>
>> https://github.com/ipfs/papers/raw/master/ipfs-cap2pfs/ipfs-p2p-file-system.pdf
>
> I mentioned IPFS here some time ago and said it even has JavaScript, Go had front-end, apparently no one saw the potential just like no one respondent to your thread. Too bad though :( IPFS is the future.
>
> Always chasing after mainstream ...

How is this mainstream?  I agreed with you then that p2p is the future, but I think the web stack will not make it into that future, similar to how mobile apps are currently displacing it.  Making the web stack p2p is sort of like adding an engine to your horse-drawn buggy. ;)