3 ms·

Orbit used to use a Redis server for pubsub messaging but it's not anymore as IPFS has implemented a peer-to-peer pubsub. Totally serverless.

by carolc 10y ago

fizzbatter 10y ago
Are you familiar with IPFS pubsub? Would you be able to link some information about the implementation/usage? I'm quite surprised to hear what you said. I've been following multiple Github Issues on IPFS pubsub, and none of them (that i followed) announced success/etc. I thought it was still in the planning phase.
- diggan 10y ago
  There is some prototype work done in master already (if you build go-ipfs from source). $ ipfs pubsub --help USAGE ipfs pubsub - An experimental publish-subscribe system on ipfs. SYNOPSIS ipfs pubsub DESCRIPTION ipfs pubsub allows you to publish messages to a given topic, and also to subscribe to new messages on a given topic. This is an experimental feature. It is not intended in its current state to be used in a production environment. To use, the daemon must be run with '--enable-pubsub-experiment'. SUBCOMMANDS ipfs pubsub ls - List subscribed topics by name. ipfs pubsub peers - List all peers we are currently pubsubbing with. ipfs pubsub pub <topic> <data>... - Publish a message to a given pubsub topic. ipfs pubsub sub <topic> - Subscribe to messages on a given topic. Use 'ipfs pubsub <subcmd> --help' for more information about each command.
  - fizzbatter 10y ago
    Wow, thank you! Very interesting! Quite odd that none of my follows mentioned this going live, must be an issue of too many github issues. Time to dig into this a bit! edit: For anyone else perplexed and surprised by me, seems `floodsub` is their moniker for the new tech, and it was (in part) merged in here: https://github.com/ipfs/go-ipfs/pull/3202 https://github.com/ipfs/go-ipfs/pull/3202 This is really, really cool! Also, if this implementation is robust and performant, this is huge for IPFS.
    - lgierth 10y ago
      Yes we haven't been very vocal about it yet because it's not yet part of a go-ipfs release -- it'll be in the next release, go-ipfs v0.4.5. Note on the name: floodsub is one specific implementation of pubsub. There are many ways to do pubsub, and we chose to go with a naive and simple flooding implementation for now. In the future there will be more, and you'll be able to use different implementations simultaneously.

Orbit used to use a Redis server for pubsub messaging but it's not anymore as IPFS has implemented a peer-to-peer pubsub. Totally serverless.

by carolc 10y ago

Orbit used to use a Redis server for pubsub messaging but it's not anymore as IPFS has implemented a peer-to-peer pubsub. Totally serverless.

fizzbatter 10y ago

Are you familiar with IPFS pubsub? Would you be able to link some information about the implementation/usage? I'm quite surprised to hear what you said. I've been following multiple Github Issues on IPFS pubsub, and none of them (that i followed) announced success/etc. I thought it was still in the planning phase.

diggan 10y ago
There is some prototype work done in master already (if you build go-ipfs from source). $ ipfs pubsub --help USAGE ipfs pubsub - An experimental publish-subscribe system on ipfs. SYNOPSIS ipfs pubsub DESCRIPTION ipfs pubsub allows you to publish messages to a given topic, and also to subscribe to new messages on a given topic. This is an experimental feature. It is not intended in its current state to be used in a production environment. To use, the daemon must be run with '--enable-pubsub-experiment'. SUBCOMMANDS ipfs pubsub ls - List subscribed topics by name. ipfs pubsub peers - List all peers we are currently pubsubbing with. ipfs pubsub pub <topic> <data>... - Publish a message to a given pubsub topic. ipfs pubsub sub <topic> - Subscribe to messages on a given topic. Use 'ipfs pubsub <subcmd> --help' for more information about each command.
- fizzbatter 10y ago
  Wow, thank you! Very interesting! Quite odd that none of my follows mentioned this going live, must be an issue of too many github issues. Time to dig into this a bit! edit: For anyone else perplexed and surprised by me, seems `floodsub` is their moniker for the new tech, and it was (in part) merged in here: https://github.com/ipfs/go-ipfs/pull/3202 https://github.com/ipfs/go-ipfs/pull/3202 This is really, really cool! Also, if this implementation is robust and performant, this is huge for IPFS.
  - lgierth 10y ago
    Yes we haven't been very vocal about it yet because it's not yet part of a go-ipfs release -- it'll be in the next release, go-ipfs v0.4.5. Note on the name: floodsub is one specific implementation of pubsub. There are many ways to do pubsub, and we chose to go with a naive and simple flooding implementation for now. In the future there will be more, and you'll be able to use different implementations simultaneously.