By the way, here's an excellent technical blog post about the difficulties of making a distributed HTTP:
https://www.mnot.net/blog/2015/08/18/distributed_http Best wishes Jeremy -- Jeremy Ruston [email protected] http://jermolene.com > On 14 Jun 2016, at 16:42, Jeremy Ruston <[email protected]> wrote: > > Hi Richard > >> Hi Jeremy, >> >> Worked for me without complaint - >> http://elsewhere.neocities.org/tiddlywikicom.html and I find that I am able >> to access it at both http and https immediately - >> https://elsewhere.neocities.org/tiddlywikicom.html > > Excellent news, thank you. > >> Initially it seems that the daily ipfs cache of neocities sites will store >> each one as an archive blob (I'm not sure of this) but if, eventually, they >> archive individual files, then it would be very easy to get the power of >> ipfs working for us. I am excited about the possibility of having a 'tiddler >> manifest' document which then pulls all of the tiddlers from IPFS >> individually. To me the idea of distributed/permanent/versioned content >> (including code) and Tiddlywiki as a trusted personal tool for authoring and >> consuming that content is very interesting; ipfs is the ultimate way to 'set >> the tiddlers free' and tiddlers may even prove to be a useful paradigm in >> themselves for thinking about truly distributed content. > > Well put; there's a great appeal to assembling the wiki from individual > tiddler files. I did some experimentation with Dropbox's JavaScript API a > couple of years ago and concluded that performance was a bit of an obstacle: > the trouble is that HTTP is an expensive protocol, hence all the various > hacks (like image sprites) that are designed to help pack multiple resources > into a single network request. There is also an issue with atomicity of > writing to multiple files; it's hard to cope elegantly with the browser tab > being closed (or network connectivity being lost) in the middle of a > save/sync operation. > > Meanwhile, and somewhat orthogonally, one of the characteristics of > TiddlyWiki that makes it particularly interesting for experimenting with > distributed webby stuff is actually that it (can be) a completely self > contained single file. For systems like Tahoe-LAFS and (possibly IPFS) the > problem of serving a single file is a bit easier than serving multiple files > while maintaining the same relative addressing. > > Best wishes > > Jeremy. > >> >> Regards, >> Richard >> -- >> 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/7f5c7679-a029-4e70-80a9-6f9781b3de78%40googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. -- 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/439BD910-3489-4546-B81E-1FB25B427DAE%40gmail.com. For more options, visit https://groups.google.com/d/optout.
