Hi Richard, Since you seem to be ahead on the learning curve, these are the questions that occur to me ...
How do you know what hash to ask for, and what happens when the original content (aka "site") changes? How many different versions of the hashed site would you retain? If "pulling" members of the ipfs don't retain early versions of the content, then how is it significantly different than what we have now, where content may be replaced at any time. Lot's of sites these days are database-driven. Which means there's really no "site" to be saved, captured, and shared. Each individual has a unique experience (think Amazon). Can the problem the ipfs was supposed to fix (e.g. "We're losing the internet") even be fixed in a world in which static sites are rapidly disappearing? With twederation, does the hash imply that each tiddler should get it's own unique ID (something that I think is going to be necessary somehow to avoid title crashes). Thanks, Mark On Saturday, June 25, 2016 at 7:17:18 PM UTC-7, RichardWilliamSmith wrote: > > And as for using ipfs for a distributed node-like implementation online, >> that would be awesome. There would unfortunately be problems with >> read-write privileges and the like. I imagine it would be easiest to make >> something that could dynamically build a wiki from a set of distributed tid >> files on page load, but you could do the same thing using http. >> Fundamentally http(s) is also a way to access a distributed file system so >> that aspect of it doesn't necessarily allow any novel applications. >> > > The novel applications come (imo) from the fact that ipfs is > content-addressable - you ask for tiddlers by their hash, not a location. > It also has signed namespaces that you can use as a pub location for > pub/sub and built-in versioning. As far as I understand it, the best way to > explain ipfs is something like "bit-torrent, with git on top, with the web > on top of that" and there are no servers, only peers in a swarm. If you > publish something, then I view it and then you go offline, other people can > still get what you published from me, and yet there's no way I can tamper > with it. There are also proposals for an incentivisation layer (filecoin) > that would let you pay a small amount to guarantee your content to remain > hosted, though in practise anything of interest to more than a few people > will remain live anyway. All of this, of course, is far from ready for > widespread adoption and, as I say, I have a lot to learn about it all. > > RR > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2932540b-1799-4442-ac60-5ea54e62b56b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
