stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.5.1 and js-ipfs 0.43.1 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of Conduct: https://git.io/vVBS0
<AkhIL[m]>
How to model multiple producers single consumer queue with IPFS?
digitalnomad91 has joined #ipfs
XORed has quit [Ping timeout: 256 seconds]
XORed has joined #ipfs
<AkhIL[m]>
With IPNS, I can publish a record that can be read by several consumers. I need exactly the opposite, create one sink into which any peer can send messages. Is it possible? How can it be done?
digitalnomad91 has quit [Ping timeout: 246 seconds]
hqdruxn08_ has joined #ipfs
hqdruxn08 has quit [Ping timeout: 256 seconds]
<aschmahmann[m]>
@ AkhIL a few questions.
<aschmahmann[m]>
How are the multiple producers defined? Are they known in advance? How do you plan to combine the inputs from different producers (e.g. if multiple producers send messages at the same time, what do you do)?
<aschmahmann[m]>
Perhaps using pubsub (either via IPFS, or directly via libp2p) or textile threads/buckets might make your life a bit easier here.
<AkhIL[m]>
As an example, a chat room, in which each person is a message producer, and the room itself is written in IPNS.
<AkhIL[m]>
The task is to make the person find each other using a some room identifier published with IPFS.
<AkhIL[m]>
Each person has his own event log, also published in IPNS.
<AkhIL[m]>
Oh. Well, the pub / sub API seems to be good enough for peer advertising.
<AkhIL[m]>
Thanks.
<aschmahmann[m]>
No problem. I'd be a bit careful with the pubsub semantics and making sure you know what you want to build. pubsub does not guarantee delivery of any particular message, nor does it have any notion of persistence (e.g. a peer that joins a topic late will not learn about older messages). If you care about those semantics though you can try building them on top of pubsub as https://github.com/libp2p/go-libp2p-pubsub-router
<aschmahmann[m]>
btw if it's helpful a while ago I wrote up some thoughts about the equivalence of different naming systems here https://github.com/ipfs/notes/issues/379. The text is still a bit raw, but the basic idea is that once you define the actual requirements of your system it makes it easier to figure out which components you might need.
<EthanWilliamDisc>
> Ethan William write a microservice to listen to the request action to pin?
<EthanWilliamDisc>
thienpow Thanks for the reply. Is there any tutorial for it?
ThereIwas has quit [Ping timeout: 246 seconds]
ThereIwas has joined #ipfs
xcm has joined #ipfs
ThereIwas has quit [Ping timeout: 260 seconds]
mikkel has quit [Ping timeout: 256 seconds]
drathir_tor has quit [Ping timeout: 240 seconds]
ThereIwas has joined #ipfs
fazo96 has joined #ipfs
KempfCreative1 has joined #ipfs
KempfCreative has quit [Ping timeout: 264 seconds]
KempfCreative1 is now known as KempfCreative
drathir_tor has joined #ipfs
fazo96 has quit [Ping timeout: 240 seconds]
KempfCreative1 has joined #ipfs
KempfCreative has quit [Ping timeout: 264 seconds]
KempfCreative1 is now known as KempfCreative
drathir_tor has quit [Ping timeout: 240 seconds]
kn0rki has joined #ipfs
jesse22 has quit [Ping timeout: 260 seconds]
drathir_tor has joined #ipfs
satchmo has quit [Ping timeout: 240 seconds]
vlnzt[m] has left #ipfs ["User left"]
Sajesajama has joined #ipfs
PyHedgehog has joined #ipfs
codepy69 has quit [Quit: Quit..]
JackK has quit [Ping timeout: 240 seconds]
D_ has quit [Ping timeout: 240 seconds]
bengates has quit [Remote host closed the connection]
JackK has joined #ipfs
D_ has joined #ipfs
codepy69 has joined #ipfs
codepy69 has joined #ipfs
codepy69 has quit [Changing host]
frhs has joined #ipfs
jesse22 has joined #ipfs
frhs has quit [Remote host closed the connection]
lord| has quit [Ping timeout: 240 seconds]
lord| has joined #ipfs
jokoon has quit [Quit: Leaving]
frhs has joined #ipfs
jokoon has joined #ipfs
jokoon has quit [Quit: Leaving]
cipres has joined #ipfs
<spheres[m]>
hi, I'm trying to use go-ipfs-http-client to connect to a remote ipfs node, and I'm wondering if anyone has an example of doing so with Go similar to the example provided in the readme for https://github.com/ipfs/go-ipfs-api
fazo96 has joined #ipfs
dethos has quit [Ping timeout: 256 seconds]
ThereIwas_ has joined #ipfs
user_ has joined #ipfs
user_ has left #ipfs [#ipfs]
user_ has joined #ipfs
user_ has quit [Client Quit]
vindelschtuffen has joined #ipfs
kn0rki has quit [Quit: Leaving]
fazo96 has quit [Ping timeout: 265 seconds]
drdee has quit [Remote host closed the connection]
Ecran has joined #ipfs
vindelschtuffen_ has joined #ipfs
vindelschtuffen has quit [Quit: vindelschtuffen]
vindelschtuffen_ is now known as vindelschtuffen
vindelschtuffen is now known as vindelschtuffen_
vindelschtuffen has joined #ipfs
vindelschtuffen has quit [Client Quit]
KempfCreative has quit [Ping timeout: 264 seconds]
dethos has joined #ipfs
hsn has quit [Ping timeout: 264 seconds]
LinusCDE has quit [Ping timeout: 260 seconds]
LinusCDE has joined #ipfs
branjam has quit [Ping timeout: 260 seconds]
aaaaaa has joined #ipfs
aaaaaa has quit [Max SendQ exceeded]
aaaaaa has joined #ipfs
aaaaaa has quit [Max SendQ exceeded]
aaaaaa has joined #ipfs
aaaaaa has quit [Max SendQ exceeded]
<vindelschtuffen_>
are there any best practices/standard conventions for using ipfs/orbitdb in a browser-accessed web application for multi-user dynamic content?
<vindelschtuffen_>
things to know about that might not be explicitly mentioned in documentation?
drathir_tor has quit [Ping timeout: 240 seconds]
Jesin has quit [Quit: Leaving]
Adbray has joined #ipfs
digitalnomad91 has joined #ipfs
digitalnomad91_ has joined #ipfs
xcm has quit [Remote host closed the connection]
D_ has quit [Quit: No Ping reply in 180 seconds.]
drathir_tor has joined #ipfs
D_ has joined #ipfs
xcm has joined #ipfs
coniptor has quit [Ping timeout: 265 seconds]
drathir_tor has quit [Ping timeout: 240 seconds]
digitalnomad91 has quit [Read error: Connection reset by peer]
digitalnomad91_ has quit [Remote host closed the connection]
g2anj has quit [Ping timeout: 264 seconds]
g2anj has joined #ipfs
coniptor has joined #ipfs
drathir_tor has joined #ipfs
cipres has quit [Quit: leaving]
<postDiscord[m]1>
Read the test files
<postDiscord[m]1>
They'll show you how to use the client
<postDiscord[m]1>
If there's an undocumented code base that has tests, you can almost always learn how to use it by reading tests
xcm has quit [Read error: Connection reset by peer]
xcm has joined #ipfs
jcea has joined #ipfs
satchmo has joined #ipfs
dethos has quit [Ping timeout: 256 seconds]
endvra has quit [Read error: Connection reset by peer]