9 ms·

Meh, it's a distributed static website thing. Of course if one doesn't need transactions, everything is easier even today -- I mean, who doesn't use a CDN? It'

by sklivvz1971 11y ago

Meh, it's a distributed static website thing. Of course if one doesn't need transactions, everything is easier even today -- I mean, who doesn't use a CDN? It's a very similar concept. The problem is much tougher when the content is personalized or when there needs to be a transaction. This makes distribution a huge huge problem no one has solved yet (even a blockchain, IIRC can't really scale up in transactions...)

_prometheus 11y ago
(IPFS dev here) Hey! Yeah, we're focusing right now on "distributed static websites" because those are really easy to get right and make work all over the network. However, what's _really_ interesting about IPFS is making completely distributed applications which can do their process unhinged from a single origin -- websites/webapps without an origin server. Posted more about this elsewhere on this thread, take a look: https://news.ycombinator.com/item?id=10329221 https://news.ycombinator.com/item?id=10329221 Also see the Neocities + IPFS blog post: https://ipfs.io/ipfs/QmTVcD87Ecjps6wv9jMaGhvMuzZ2BgP6NyXDcnMU74RELx/ https://ipfs.io/ipfs/QmTVcD87Ecjps6wv9jMaGhvMuzZ2BgP6NyXDcnM... Take a look also at this talk, which presents different use cases for this: https://www.youtube.com/watch?v=skMTdSEaCtA https://www.youtube.com/watch?v=skMTdSEaCtA Can also see some of the random crazy things we're planning in https://github.com/ipfs/notes/issues/ https://github.com/ipfs/notes/issues/ + https://github.com/ipfs/archives/issues/ https://github.com/ipfs/archives/issues/ + https://github.com/ipfs/apps/issues/ https://github.com/ipfs/apps/issues/ (Edit: fix links)
- supdog 11y ago
  Link to .../ipfs/notes/ appears to contain 37 bytes of nothing. Is the content available elseware? Would love to see the random crazy things you're planning.
  - lgierth 11y ago
    Yep sorry, it's in the issue tracker: https://github.com/ipfs/notes/issues https://github.com/ipfs/notes/issues
- deleted 11y ago
  [deleted]
- venportman 11y ago
  For some reason the links in the Neocities blog on IPFS don't work. Is there a working version of the Neocities blog on IPFS? [Edit: this seems to be a problem with the route names on the Neocities blog, not IPFS itself]
- 21echoes 11y ago
  Are you working with https://unhosted.org/ https://unhosted.org/ at all on the unhinged apps concept?
  - _prometheus 11y ago
    not yet, but we should! will email them, thanks for ptr!
marknadal 11y ago
Distributed static content is absolutely critical and shouldn't be ignored. Juan's work is excellent. If you are looking for distributed p2p dynamic data sooner though, have a look at (disclosure: I'm the author) https://github.com/amark/gun https://github.com/amark/gun which already works.
- _prometheus 11y ago
  Thanks mark! gun is really cool! Would love to talk about it, actually. I'd love to make gun a transport for IPFS objects, and viceversa. send me an email! Also, IPFS works today too, https://ipfs.io https://ipfs.io is served directly via IPFS :)

_prometheus 11y ago

(IPFS dev here) Hey! Yeah, we're focusing right now on "distributed static websites" because those are really easy to get right and make work all over the network. However, what's _really_ interesting about IPFS is making completely distributed applications which can do their process unhinged from a single origin -- websites/webapps without an origin server. Posted more about this elsewhere on this thread, take a look: https://news.ycombinator.com/item?id=10329221 https://news.ycombinator.com/item?id=10329221 Also see the Neocities + IPFS blog post: https://ipfs.io/ipfs/QmTVcD87Ecjps6wv9jMaGhvMuzZ2BgP6NyXDcnMU74RELx/ https://ipfs.io/ipfs/QmTVcD87Ecjps6wv9jMaGhvMuzZ2BgP6NyXDcnM... Take a look also at this talk, which presents different use cases for this: https://www.youtube.com/watch?v=skMTdSEaCtA https://www.youtube.com/watch?v=skMTdSEaCtA Can also see some of the random crazy things we're planning in https://github.com/ipfs/notes/issues/ https://github.com/ipfs/notes/issues/ + https://github.com/ipfs/archives/issues/ https://github.com/ipfs/archives/issues/ + https://github.com/ipfs/apps/issues/ https://github.com/ipfs/apps/issues/ (Edit: fix links)

supdog 11y ago
Link to .../ipfs/notes/ appears to contain 37 bytes of nothing. Is the content available elseware? Would love to see the random crazy things you're planning.
- lgierth 11y ago
  Yep sorry, it's in the issue tracker: https://github.com/ipfs/notes/issues https://github.com/ipfs/notes/issues
deleted 11y ago
[deleted]
venportman 11y ago
For some reason the links in the Neocities blog on IPFS don't work. Is there a working version of the Neocities blog on IPFS? [Edit: this seems to be a problem with the route names on the Neocities blog, not IPFS itself]
21echoes 11y ago
Are you working with https://unhosted.org/ https://unhosted.org/ at all on the unhinged apps concept?
- _prometheus 11y ago
  not yet, but we should! will email them, thanks for ptr!

marknadal 11y ago

Distributed static content is absolutely critical and shouldn't be ignored. Juan's work is excellent. If you are looking for distributed p2p dynamic data sooner though, have a look at (disclosure: I'm the author) https://github.com/amark/gun https://github.com/amark/gun which already works.

_prometheus 11y ago
Thanks mark! gun is really cool! Would love to talk about it, actually. I'd love to make gun a transport for IPFS objects, and viceversa. send me an email! Also, IPFS works today too, https://ipfs.io https://ipfs.io is served directly via IPFS :)