Live data from Hacker News

IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

ipfs.io

21–30 of 39 posts

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#21
post #11

Is there some kind of podcast or YouTube series about ipfs and similar technologies? I'd love to learn more about how they work, what they're working on, and what's next.

Check out the IPFS YouTube channel (https://www.youtube.com/channel/UCdjsUXJ3QawK4O5L1kqqsew) and Decentralized Web Primer (https://www.gitbook.com/book/flyingzumwalt/decentralized-web...) as starting points.

For a more overarching perspective, I'd suggest A Progress Report on the Decentralized Web: https://www.youtube.com/watch?v=WK4PIGr3RB8

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#22
post #6

So, botnet C&C with no takedowns and more efficient and lower risk than servers on Tor? Nice.

Maybe, but remember IPFS nodes can elect to blacklist any given channel, so any given static C&C site here is just as vulnerable as a DNS point or a given static IP address.

There's no blocking functionality in IPFS yet - the plan is to have customizable opt-in blocklists (and allowlists) for content and peers, though, so communities can govern themselves regarding what content is desired and what's not.

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#23

Earlier quoted context omitted.

The real challenge to this is negotiating pinning without it being exploitable by third parties.

Is there where a third party node can spoof (or lie about) the content belonging to a pin to clients that ask it?

Pins are something that's per-node, and whether a node has a specific piece of content pinned is not visible publicly (only that it's providing the content).

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#24
post #12
post #7

Pubsub is probably one of the lesser known features of IPFS right now, given that it's still marked as experimental. We're researching more efficient tree-forming and message routing algorithms, but generally the interface is pretty stable by now. Pubsub is supported in both go-ipfs and js-ipfs. A shining example of pubsub in use is PeerPad, a collaborative text editor exchanging CRDTs over IPFS/Pubsub: https://peerp…

Off-topic question for you. What language do you recommend developers build IPFS-backed apps with? I started building an app in Go (which is your reference language) but Javascript seems to have a lot more APIs available for it.

If you're looking for raw performance and/or large datasets, go-ipfs is for you. If you're​ looking for running within websites (and in browsers generally), then js-ipfs is for you.

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#25
post #6

So, botnet C&C with no takedowns and more efficient and lower risk than servers on Tor? Nice.

Maybe, but remember IPFS nodes can elect to blacklist any given channel, so any given static C&C site here is just as vulnerable as a DNS point or a given static IP address.

[deleted]

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#26

How does spam prevention work?

> Currently, any peer can publish to any pubsub topic. We plan to implement an authenticated mode for pubsub topics, where only authorized peers — those given a cryptographic key or capability — can publish messages. We are still working out the sharing and capability granting model.

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#27

Hey Everyone! IPFS dev here, If anyone is interested in the future of ipfs pubsub you can participate in the discussions in our research repo: https://github.com/libp2p/research-pubsub . One of the next big things we're planning to do is to implement a new routing algorithm, one proposal for this is here: https://github.com/libp2p/research-pubsub/pull/17 (feedback and review very welcome) We are also planning on impl…

When you're talking about a routing proposal, I think you are referring to this? https://github.com/vyzo/research-pubsub/blob/a6cfdd3fec9d595...

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#28
post #27

Hey Everyone! IPFS dev here, If anyone is interested in the future of ipfs pubsub you can participate in the discussions in our research repo: https://github.com/libp2p/research-pubsub . One of the next big things we're planning to do is to implement a new routing algorithm, one proposal for this is here: https://github.com/libp2p/research-pubsub/pull/17 (feedback and review very welcome) We are also planning on impl…

When you're talking about a routing proposal, I think you are referring to this? https://github.com/vyzo/research-pubsub/blob/a6cfdd3fec9d595...

Yes that's the document in https://github.com/libp2p/research-pubsub/pull/17

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#29

Hey Everyone! IPFS dev here, If anyone is interested in the future of ipfs pubsub you can participate in the discussions in our research repo: https://github.com/libp2p/research-pubsub . One of the next big things we're planning to do is to implement a new routing algorithm, one proposal for this is here: https://github.com/libp2p/research-pubsub/pull/17 (feedback and review very welcome) We are also planning on impl…

Any updates on filecoin integration?

Re: IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud

#30

Earlier quoted context omitted.

Sorry, the reference to Tor is misleading. I was not referring to anonymity but rather access to content from restricted areas like the Middle East or Asia.

In that sense, I would agree, ipfs can provide access to content that would otherwise be blocked.

Could ISPs throttle IPFS content the same way they did with torrents a while ago? (and probably will again once net neutrality falls).
Post reply on HN