51–58 of 58 posts
This would be interesting if combined with something like BAT or AdSense or Coinhive to earn revenue from viewing then use that revenue to pay for seeding via something like Sia/ Filecoin.
Never thought about it before. Sounds interesting. Let me see if I can integrate one of these easily :)
Earlier quoted context omitted.
Interesting question. I was also considering to use IPFS js while developing Peerdium. But it seems like it's not fully ready yet. For example, take a look at this > 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 a…
Nice app! Great work, you deserve all the HN attention. :D 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
Earlier quoted context omitted.
Gun looks pretty cool. I have not fully fixed the STUN/ICE problem. Some of the users on HN are still not able to see the articles. I think the problem reduced a bit after I started running a TURN server. But it's not full eliminated yet. Check out my tweet to Feross. Maybe he has some answers :) https://twitter.com/hackerkidx/status/996009992569274369
@vishnu_ks , I also recently found https://github.com/priologic/easyrtc which worked out of the box, and automatically connects to several public STUN/ICE peers. I'm planning on using it (when I get a chance to finish the WebRTC adapter), maybe we can tag team something? It worked super well on a P2P/decentralized 3D VR multiplayer game somebody had built.
Earlier quoted context omitted.
Never thought about it before. Sounds interesting. Let me see if I can integrate one of these easily :)
Maybe check out IPFS while you are at it.
https://news.ycombinator.com/item?id=17063374
This comment has some insights on why I decided to use WebTorrent over IPFS.
It would be better if you used #idhere instead of /id, so then you are not (as) responsible for user content.
Can you explain this a bit more? Also no content created by the user is stored in Peerdium server. Everything is stored in the browser of the user.
# 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 #.
Earlier quoted context omitted.
Can you explain this a bit more? Also no content created by the user is stored in Peerdium server. Everything is stored in the browser of the user.
Sorry for the late reply. Since the ID is not a # variable in the URLs, it is passed to the web server hosting the content, meaning even if the data/metadata is not stored on any server you own (it doesn't appear to be), you could still be expected to block URLs which someone wants to ban. # variables are not part of server queries, so they are better for user privacy as well (not stored in server logs). I'm not sayi…