On Wednesday, 13 January 2016 at 20:07:01 UTC, Wyatt wrote:
On Wednesday, 13 January 2016 at 19:17:00 UTC, karabuta wrote:
when they do
This is... remarkably optimistic.
-Wyatt
Mark my words
On Wednesday, 13 January 2016 at 00:00:17 UTC, israel wrote:
On Tuesday, 12 January 2016 at 23:26:07 UTC, karabuta wrote:
Anyone has the fuel and time to take the initiative? It will
probably take over HTTP.
Currently implemented in Go with JavaScript and Python on the
way. However it seems
On Wednesday, 13 January 2016 at 08:19:01 UTC, Joakim wrote:
On Wednesday, 13 January 2016 at 00:00:17 UTC, israel wrote:
On Tuesday, 12 January 2016 at 23:26:07 UTC, karabuta wrote:
Anyone has the fuel and time to take the initiative? It will
probably take over HTTP.
Currently implemented
On Wednesday, 13 January 2016 at 19:17:00 UTC, karabuta wrote:
when they do
This is... remarkably optimistic.
-Wyatt
On Tuesday, 12 January 2016 at 23:26:07 UTC, karabuta wrote:
It will probably take over HTTP.
Not in your life time.
This sounds like a glorified mesh network.
Anyone has the fuel and time to take the initiative? It will
probably take over HTTP.
Currently implemented in Go with JavaScript and Python on the
way. However it seems most other programming languages have API
Client Libraries. Sup? :)
http://ipfs.io/
https://github.com/ipfs/ipfs
On Tuesday, 12 January 2016 at 23:26:07 UTC, karabuta wrote:
Anyone has the fuel and time to take the initiative? It will
probably take over HTTP.
Currently implemented in Go with JavaScript and Python on the
way. However it seems most other programming languages have API
Client Libraries.
On Wednesday, 13 January 2016 at 00:00:17 UTC, israel wrote:
On Tuesday, 12 January 2016 at 23:26:07 UTC, karabuta wrote:
Anyone has the fuel and time to take the initiative? It will
probably take over HTTP.
Currently implemented in Go with JavaScript and Python on the
way. However it seems