Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Serverless Sync in Web Apps Using Bit Torrent

paul.kinlan.me

Post reply on HN
Print view View original

21–30 of 57 posts

Re: Serverless Sync in Web Apps Using Bit Torrent

#21

Post by toomuchtodo »

niftich wrote: post #19
kinlan wrote: post #16

Earlier quoted context omitted.

I didn't know about it. I chose webtorrent because I potentially also wanted to have content created from the app to be long term on the torrent network if people are seeding the content.

There was a discussion about the world's oldest torrent, where others and I mused about solutions to the problem of ephemeral seeds: https://news.ycombinator.com/item?id=10962305 I suggested that one could maybe bridge Bittorrent and IPFS, then someone suggested that IPFS would be ideal for being the 'canonical' source of the file while the other protocols (HTTP, BT, WT) are merely ways to access the file.

> then someone suggested that IPFS would be ideal for being the 'canonical' source of the file while the other protocols (HTTP, BT, WT) are merely ways to access the file.

Hey! That was me! I still believe its a great idea ;)

Re: Serverless Sync in Web Apps Using Bit Torrent

#22

Post by kodablah »

stirner wrote: post #15

Why not use IPFS, which is specifically designed for this sort of usage and will be more resilient?

Seems js-ipfs[0] is not quite ready for prime time (though it's close) and the author had a requirement to do everything from a browser.

https://github.com/ipfs/js-ipfs/

Re: Serverless Sync in Web Apps Using Bit Torrent

#23

Post by greglindahl »

niftich wrote: post #19
kinlan wrote: post #16

Earlier quoted context omitted.

I didn't know about it. I chose webtorrent because I potentially also wanted to have content created from the app to be long term on the torrent network if people are seeding the content.

There was a discussion about the world's oldest torrent, where others and I mused about solutions to the problem of ephemeral seeds: https://news.ycombinator.com/item?id=10962305 I suggested that one could maybe bridge Bittorrent and IPFS, then someone suggested that IPFS would be ideal for being the 'canonical' source of the file while the other protocols (HTTP, BT, WT) are merely ways to access the file.

The Internet Archive seeds all of our items' torrents since 2012. IPFS is a more straightforward way for us to be sure we've got independent seeds of all of our content. Got 25 petabytes of disk?

Re: Serverless Sync in Web Apps Using Bit Torrent

#24

Post by mdjeu »

Maybe this a bit tangential, but I was just thinking lately how it would be nice to use some decentralized communication backend to word processing software to enable shared collaborative editing of documents. Sort of like Google Docs, but without a centralized server.

Re: Serverless Sync in Web Apps Using Bit Torrent

#27

Post by niftich »

greglindahl wrote: post #23
niftich wrote: post #19

Earlier quoted context omitted.

There was a discussion about the world's oldest torrent, where others and I mused about solutions to the problem of ephemeral seeds: https://news.ycombinator.com/item?id=10962305 I suggested that one could maybe bridge Bittorrent and IPFS, then someone suggested that IPFS would be ideal for being the 'canonical' source of the file while the other protocols (HTTP, BT, WT) are merely ways to access the file.

The Internet Archive seeds all of our items' torrents since 2012. IPFS is a more straightforward way for us to be sure we've got independent seeds of all of our content. Got 25 petabytes of disk?

Uhhh, 20 GB free...

I'm just a third-party, but if you were to get in touch with the IPFS team to host a limited amount of IA content as a proof-of-concept, I'm sure it would be a great publicity for both of your organizations.

Re: Serverless Sync in Web Apps Using Bit Torrent

#28

Post by greglindahl »

niftich wrote: post #27
greglindahl wrote: post #23

Earlier quoted context omitted.

The Internet Archive seeds all of our items' torrents since 2012. IPFS is a more straightforward way for us to be sure we've got independent seeds of all of our content. Got 25 petabytes of disk?

Uhhh, 20 GB free... I'm just a third-party, but if you were to get in touch with the IPFS team to host a limited amount of IA content as a proof-of-concept, I'm sure it would be a great publicity for both of your organizations.

We're in touch with them, yes, and we have a proof-of-concept node.

Re: Serverless Sync in Web Apps Using Bit Torrent

#29

Post by rictic »

chj wrote: post #25

It's great to share data, however, how can a torrent solution support services like web API?

(This is a good question, but as asked it's so broad that it's akin to asking "What kinds of things does P2P work for?" and we're still discovering more answers to it every year.)

Re: Serverless Sync in Web Apps Using Bit Torrent

#30

Post by toomuchtodo »

greglindahl wrote: post #23
niftich wrote: post #19

Earlier quoted context omitted.

There was a discussion about the world's oldest torrent, where others and I mused about solutions to the problem of ephemeral seeds: https://news.ycombinator.com/item?id=10962305 I suggested that one could maybe bridge Bittorrent and IPFS, then someone suggested that IPFS would be ideal for being the 'canonical' source of the file while the other protocols (HTTP, BT, WT) are merely ways to access the file.

The Internet Archive seeds all of our items' torrents since 2012. IPFS is a more straightforward way for us to be sure we've got independent seeds of all of our content. Got 25 petabytes of disk?

I've always wanted to write a distributed ArchiveTeam torrent server that, instead of distributing crawlers for ingestion, equally distributed IA torrents to distributed end-user storage (in a VM most likely). If seeding for a torrent dropped below a threshold, that torrent would be advertised to other client nodes to download and then serve themselves. Client VMs could come and go, and the announcer would always ensure remote storage was handled in an orderly fashion.

Perhaps this year is the year!

Post reply on HN