> DHT (automatic content discovery) and Circuit Relay (pierce through NATs and dial between any node in the network) are two fundamental pieces that are not finalized yet.
Another reason was that I had to still run an IPFS node if articles should be made available for more than 8 hours. I didn't want to do anything with storing articles.
How were you able to make WebTorrent work reliably? I was trying to write a WebRTC adapter for https://github.com/amark/gun (I'm the author) but kept on having STUN/ICE problems.
I'd love some tips! And awesome project. Somebody in our community just made a decentralized reddit clone, so it is exciting to see new P2P projects popping up every day! :D
off topic, I wish one of these peer-to-peer schemes caught on, if only because it will incentivize people to buy a desktop computer which will serve as network node. There's so many interesting things that can be done if people can be convinced that they are part of the network and not just "tablet users".
I wonder if anyone is trying to build home routers that double as ipfs/torrent nodes.
> Peerdium would not have been possible with WebTorrent, QuillJs and Vue.js
I think you meant "Peerdium would not have been possible WITHOUT WebTorrent, QuillJs and Vue.js"
Are you running a server hosting 1 instance of each document so that there is always at least 1 other person hosting the page?
Edit: Oh wait, think we're back on.
Assuming the number in the right side are the spectators. Could you show on the left side how many peers are seeding?
This comment has some insights on why I decided to use WebTorrent over IPFS.
If there is demand for the service I will try renaming the project :)
# variables are not part of server queries, so they are better for user privacy as well (not stored in server logs). I'm not saying you won't ever get takedown requests with #, but it is easier to argue to authorities that Peerdium is merely a user-ran software you are not in control of when using #.
Oh the irony.