Republishing question about go-textile HOT 2 CLOSED

Heya @drwasho! I remember seeing that listed as a change on your go-ipfs fork, but haven't dug into determining if we'll need that as well. Are your nodes designed to not republish very often? Our mobile nodes currently make no attempt to be the sole source of any particular content (they are purely leaches, capable of traversing the DHT, and pin some local light content). We use the HTTP API on an IPFS cluster to remotely pin mobile content until a Filecoin solution is available. Desktop nodes function pretty much like a normal IPFS daemon, and users will have the option to sync mobile->desktop instead of / in addition to using our pinning service.

Just for some extra context, we have this concept of "threads" which is really just a key pair used to encrypt+decrypt shared files/photos. Threads are composed of updates, which form a git-like chain. Members of a thread need to know about these updates. Currently we use Floodsub for this, but it's not the right mechanism. I'm planning on using another DHT in addition to the public IPFS DHT which will share the burden of broadcasting these updates in a manner similar to the Bitcoin Network protocol.

from go-textile.

@drwasho I think I misunderstood your question - you're asking about these pointers, right? I didn't adopt that piece of OB in Textile originally, although now am looking to as we move away from the pubsub hack I mentioned above.

from go-textile.