elendirx/web2web

How to host a full-scale website?

Closed this issue · 5 comments

gigix commented

I assume some website owners/editors are looking for a solution which allows:

  1. web pages being linked to each other through relative addresses (e.g. <a href='another.html'>see more</a>) without involving blockchain or magnet.
  2. similarly, assets (javascripts, images, stylesheets, etc.) being linked through relative addresses.
  3. infrastructural utilities/scripts to initialise/publish/update a whole website.

Is there any plan or design yet?

elendirx commented

Yes, I too think that these should be the next steps. 1 & 2 are possible and people have done that - take a look at peerweb. 3 is something I'd like to see if only for the sake of saving my own time while experimenting. There's no timeline though.

eduardonunesp commented

1 - You can achieve that with SPA applications, when everything are contained in a single bundle, see: webpack

2 - It's possible to create another bundle with assets, it can be embed or distributed in bundles of images, which can be used by many projects at the same time

3 - Trick point, due the technology still relatively new, there are many tools and ideas which can be leverage, but it's needs a work to create sort of "framework" to make the development task easier

gigix commented

Had a look around. As @elendirx said, peerweb seems to be an interesting approach - you can always wrap a complete website as one single torrent file, then use the same blockchain mechanism as version tracking.

It might make sense to check the progress of Maelstrom. I reckon the downside of Maelstrom is it requires a new browser. But might be valuable to learn how they support website owners.

eduardonunesp commented

Requires to download a new browser is a little intrusive, we don't want to change too much to using torrent base site, maybe an extension can help a lot

fogoat commented

@gigix Maelstrom doesn't work very well. The torrents they use have very basic structure and even then the response time is very slow. Bittorrent is not a good base for serving specific files. There is a Bittorrent Enhancement Proposal 47 - Padding files and extended file attributes that may help retrieve files faster by aligning files along torrent piece boundaries. Unfortunately, this is a DRAFT and who knows when it will be adopted if ever.

I think webseeding in torrent should be considered as a backup, leveraging some sort of persistent URL within webseeding.