Live data from Hacker News

Show HN: I built a peer-to-peer publishing platform

peerdium.com

41–50 of 58 posts

Re: Show HN: I built a peer-to-peer publishing platform

#42
post #11

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.

Re: Show HN: I built a peer-to-peer publishing platform

#45
post #15

Was going to say, I remember https://news.ycombinator.com/item?id=9531265 that had the very same idea as this. The thing is, what's the benefit of an ephemeral page? What can I do better if someone else is seeding it for me? Is it that hard to centrally host these bits?

Yes. I think Peerdium is not at all necessary for 99% of the use cases. You can just use a normal publishing platform. Peerdium can become useful if you don't want a single point of failure. That is anyone can spin up Peerdium servers from source code and the links would still work as long as someone is seeding the content. Also nothing is stored in a server. So if you want to share some content that you don't want t…

One feature you might want to consider is adding support for RemoteStorage [0] to allow people to export a story to a data provider of their choice, so that they can easily access it later if they care to (and perhaps start re-hosting it?) :)

[0] https://remotestorage.io/

Re: Show HN: I built a peer-to-peer publishing platform

#46

This is pretty nifty! Out of curiosity, why did you choose WebTorrent over, say, IPFS? I considered doing something similar using their JavaScript client[0]. [0]: https://github.com/ipfs/js-ipfs

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

Re: Show HN: I built a peer-to-peer publishing platform

#47

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

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

Re: Show HN: I built a peer-to-peer publishing platform

#48

Earlier quoted context omitted.

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

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.

Re: Show HN: I built a peer-to-peer publishing platform

#49
post #45

Earlier quoted context omitted.

Yes. I think Peerdium is not at all necessary for 99% of the use cases. You can just use a normal publishing platform. Peerdium can become useful if you don't want a single point of failure. That is anyone can spin up Peerdium servers from source code and the links would still work as long as someone is seeding the content. Also nothing is stored in a server. So if you want to share some content that you don't want t…

One feature you might want to consider is adding support for RemoteStorage [0] to allow people to export a story to a data provider of their choice, so that they can easily access it later if they care to (and perhaps start re-hosting it?) :) [0] https://remotestorage.io/

This sounds super interesting. Let me read more about this. :)

Re: Show HN: I built a peer-to-peer publishing platform

#50
post #45

Earlier quoted context omitted.

One feature you might want to consider is adding support for RemoteStorage [0] to allow people to export a story to a data provider of their choice, so that they can easily access it later if they care to (and perhaps start re-hosting it?) :) [0] https://remotestorage.io/

This sounds super interesting. Let me read more about this. :)

You should also check out blockstack, offers similar storage functionality (the user choose where to store the data) and has easy to use js libs
Post reply on HN