Yes, agreed!
This is the goal of IPFS[1], which provides a global distributed
namespace for content-addressable data. In terms of tooling,
ipfs-paste[2] provides this kind of functionality on top of it.
[1] https://ipfs.io
[2] https://github.com/jbenet/ipfs-paste
On 11/03 23:00, FRIGN wrote
Quoth FRIGN:
> On Tue, 03 Nov 2015 22:42:16 +0100
> Christoph Lohmann <2...@r-36.net> wrote:
>
> > the web has grown to be a big pastebin of URIs and short‐living content.
> > One good example for this are paste services which don’t guarantee any‐
> > thing. I came to the idea of having a paste
Christoph Lohmann wrote:
> the web has grown to be a big pastebin of URIs and short‐living content. One
> good example for this are paste services which don’t guarantee anything. I
> came to the idea of having a paste mailinglist: All history is stored, nothing
> will vanish and it’s easy to ref
On Tue, 03 Nov 2015 22:42:16 +0100
Christoph Lohmann <2...@r-36.net> wrote:
> the web has grown to be a big pastebin of URIs and short‐living content.
> One good example for this are paste services which don’t guarantee any‐
> thing. I came to the idea of having a paste mailinglist: All history
Greetings comrades,
the web has grown to be a big pastebin of URIs and short‐living content.
One good example for this are paste services which don’t guarantee any‐
thing. I came to the idea of having a paste mailinglist: All history is
stored, nothing will vanish and it’s easy to reference to p
