stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.19 and js-ipfs 0.34 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS, the InterPlanetary FileSystem: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of
musoke[m] has joined #ipfs
clemo has quit [Ping timeout: 246 seconds]
nighty has quit [Ping timeout: 240 seconds]
dub[m]1 has joined #ipfs
cthorley4 has joined #ipfs
nighty has joined #ipfs
ekardnam_ has joined #ipfs
ekardnam has quit [Ping timeout: 264 seconds]
nighty has quit [Quit: Disappeared in a puff of smoke]
nighty has joined #ipfs
Kingsquee has joined #ipfs
standard[m]1 has joined #ipfs
<standard[m]1>
Hi guys
<standard[m]1>
I have a question regarding IPFS propagatoin
<standard[m]1>
I have a question regarding IPFS propagation
<mikaela[m]2>
<Guest9382 "The simple answer is: everything"> I have to ask, have you tried XMPP?
Arwalk_ has joined #ipfs
Arwalk has quit [Ping timeout: 246 seconds]
ulrichard has joined #ipfs
ahiknsr has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in]
daMaestro has quit [Quit: Leaving]
M011000100111010 has joined #ipfs
AuHau[m] has joined #ipfs
blallo has quit [Quit: Gotta go]
blallo has joined #ipfs
<Guest9382>
Yes. Lost messages and stupid multiple device support. Also, I've never had file transfer or calls supported on the devices I wanted.
<Guest9382>
(The latter two aren't IRC features, no, but they're another reason for my switch away from XMPP after 5 or so years using it with my family…)
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #ipfs
farhad312[m] has joined #ipfs
taaem has quit [Changing host]
taaem has joined #ipfs
taaem has joined #ipfs
clemo has joined #ipfs
mauz555 has quit []
quijote has quit [Ping timeout: 246 seconds]
NastyEbilPiwate[ has joined #ipfs
merethan has joined #ipfs
arpit has joined #ipfs
arpit has quit [Max SendQ exceeded]
arpit has joined #ipfs
arpit has quit [Max SendQ exceeded]
arpit has joined #ipfs
arpit has quit [Client Quit]
Igutin[m] has joined #ipfs
DavidPH has quit [Ping timeout: 250 seconds]
vmx has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
user_51 has quit [Ping timeout: 246 seconds]
deepitmatrixorg[ has joined #ipfs
user_51 has joined #ipfs
sfx2496 has quit [Ping timeout: 250 seconds]
francis[m]3 has left #ipfs ["User left"]
ctOS has joined #ipfs
spinza has joined #ipfs
Soo_Slow has joined #ipfs
sfx2496 has joined #ipfs
mowcat has joined #ipfs
griffinbyatt has joined #ipfs
arpit has joined #ipfs
Fessus_ has quit [Quit: Leaving]
arthuredelstein has quit [Ping timeout: 244 seconds]
arthuredelstein has joined #ipfs
arpit has quit [Quit: Leaving]
arpit has joined #ipfs
arpit has quit [Max SendQ exceeded]
arpit has joined #ipfs
arpit has quit [Max SendQ exceeded]
arpit has joined #ipfs
arpit has quit [Max SendQ exceeded]
arpit has joined #ipfs
arpit has quit [Quit: Leaving]
cylu[m] has joined #ipfs
ZaZ has quit [Read error: Connection reset by peer]
zeden has joined #ipfs
zeden has quit [Client Quit]
spinza has quit [Quit: Coyote finally caught up with me...]
merethan has quit [Remote host closed the connection]
zeden has joined #ipfs
KempfCreative has joined #ipfs
kapil____ has quit [Quit: Connection closed for inactivity]
LoveMiku[m] has joined #ipfs
spinza has joined #ipfs
lord4163 has quit [Quit: Gotta go cya!]
Ai9zO5AP has joined #ipfs
DavidPH has joined #ipfs
zeden_ has joined #ipfs
woss_io has quit [Ping timeout: 246 seconds]
zeden has quit [Ping timeout: 244 seconds]
lassulus has quit [Ping timeout: 264 seconds]
placer14 has joined #ipfs
lassulus has joined #ipfs
zeden_ has quit [Ping timeout: 268 seconds]
mdrights has quit [Remote host closed the connection]
clemo has quit [Ping timeout: 246 seconds]
TH0Ryn[m] has joined #ipfs
agentofuser has quit [Quit: Connection closed for inactivity]
quijote has joined #ipfs
RaphaelLullis[m] has joined #ipfs
appa has quit [Quit: WeeChat 1.9.1]
appa has joined #ipfs
mowcat has quit [Remote host closed the connection]
Soo_Slow has quit [Remote host closed the connection]
woss_io has joined #ipfs
KempfCreative has quit [Ping timeout: 245 seconds]
boboril[m] has joined #ipfs
ulrichard has quit [Remote host closed the connection]
KempfCreative has joined #ipfs
<c0c00n[m]>
hi everyone, I can't find out how to do that, so maybe someone could have an idea or help me. When using a libp2p custom protocol handler with my ipfs node instance, I would like to be able to find/list nodes also handling the same custom protocol (for future dial). Something like "findProvs" when searching for nodes hosting a certain hash would be awesome but it doesn't seem to exist. I could do it using a pubsub room
<c0c00n[m]>
related to the custom protocol...but that's not really efficient/elegant. Does someone know a way to list nodes handling a specific protocol? through DHT querying or other way?
CocoonCrash[m]1 has joined #ipfs
clemo has joined #ipfs
kapil____ has joined #ipfs
<aphelionz[m]1>
@c0c00n Not sure how but I do know via the IPFS whitepaper that data below a certain number of bytes can be stored directly in the DHT
<aphelionz[m]1>
You'd have to look into how to write metadata to the DHT and then query it on the other end, as you suggest
sfx2496 has quit [Ping timeout: 246 seconds]
ZaZ has joined #ipfs
<c0c00n[m]>
hum... and how would I use those metadata? I mean, would it differ from sharing a specific file hash meaning that if my node host it it handle that custom protocol ?
<aschmahmann[m]>
aphelionz,c0c00n: I don't think you can arbitrarily dump data into the DHT (there are verifier functions tied to namespaces like for public keys, ipns keys, and provider records). If I recall correctly, the solution pubsub uses is to basically do a fake IPFS put of a block "floodsub:channelName" into the DHT. Then users can look for the providers of that block and find other people interested in the channel. You could
<c0c00n[m]>
+1 thx ashmahmann, didn't thought about diging that way (pubsub implementation), gonna try
<aphelionz[m]1>
+1 aschmahmann
<aschmahmann[m]>
c0c00n: one thing to be careful of is I don't know how many provider records the DHT will hold, so unless users of your protocol naturally connect to each other (e.g. pubsub) you're going to run into issues cramming your whole network into a DHT entry :p
libre_shoes has joined #ipfs
<c0c00n[m]>
if I follow the pubsub implementation it should provide the same reliability. My goal is to have browser nodes running my protocol, so as for pubsub, if they can't reach each other they will keep confined in their network corner I guess
<aschmahmann[m]>
seems reasonable at least to start. to clarify what I'm trying to point out is that with pubsub as long as the network is connected (A knows B and B knows C) things are fine because messages will propagate. Depending on what your protocol is for you might require the network to be more densely connected (A knows B and C) which could be tricky using just provider records.
<Reality[m]>
Not sure about this but it seems you can put some data on dht?
<aphelionz[m]1>
thats what I thought - i think it needs to be below 32 bytes or something i.e. smaller than a hash
<aphelionz[m]1>
that's what the whitepaper at least suggests
zeden_ has quit [Ping timeout: 246 seconds]
<c0c00n[m]>
I thought I may also use the put/provide and get/findProvs functions, creating/sharing a hash from my protocol name. I haven't tried yet as I thought it was not elegant, but maybe that can be a quick win to test
<aphelionz[m]1>
Storing stuff in the DHT seems the simplest, if not the most elegant. Every peer makes exactly one put and then other peers look for that when they connect via get. One get / one put at its core
<c0c00n[m]>
Yes. And it'll benefit the same reliability as current node can expect. I'm going to give it a try and let you know.
ZaZ has quit [Read error: Connection reset by peer]
<postables[m]>
sounds like private ipfs networks are up your alley
quijote_ has joined #ipfs
NooooooWayyyyy[m is now known as NooooooWayyyyy07
NooooooWayyyyy07 is now known as NooooooWayyyyy[m
<NooooooWayyyyy[m>
Hi everybody. I am designing/implementing a data centric secure file sharing app for a company which is mainly will be use in their internal network, but it must be connect to internet as well. My system do not have a central server because I wants to decrease the chance of losing control of system even though a bad actor have a complete access to one of our servers. I'm currently using MongoDB/gridFS with tons of
<NooooooWayyyyy[m>
cryptographic hacks to store files but I just heard about IPFS and after a bit of research I thought It could help me to achieve this goal a lot easier. I'm very new to IPFS and I have lots of confusions. Do you think that I can use IPFS for this purpose? If yes where can I start learning about IPFS internals? ( I looked at docs but it wasn't deep enough, I still don't know what is happening inside IPFS )
quijote has quit [Ping timeout: 246 seconds]
<shokunin[m]1>
Probably. Ipfs won’t store your data. It’s just a protocol for you to distribute it. Best place is to read the docs and ask people here 😃
<NooooooWayyyyy[m>
Oh, I guess it will do that "cryptographic hacks" for me. Am I right?
zeden__ has joined #ipfs
quijote has joined #ipfs
zeden has joined #ipfs
quijote_ has quit [Ping timeout: 245 seconds]
plexigras has joined #ipfs
zeden__ has quit [Ping timeout: 255 seconds]
bin_y has quit [Ping timeout: 256 seconds]
<RaphaelLullis[m]>
postables: I looked into private networks before, but my understanding is that private networks assume that I have control over all nodes, right?
<RaphaelLullis[m]>
My use case would be more along the lines of "My friends and I all have their own IPFS node. I would like to share some of my data with some of my friends, and my friends would like to share some of their data with their friends, etc"
placer14 has quit [Ping timeout: 245 seconds]
<RaphaelLullis[m]>
Some of this data will be "common": let's say that most of my friends are into e.g collecting manga. In my view, whatever data I have pinned I could access directly, and the data I am *not* hosting I could only get by requesting the data from those peers that consider my node "trusted".
ekardnam_ has quit [Remote host closed the connection]
ekardnam_ has joined #ipfs
jesse22 has quit [Ping timeout: 252 seconds]
<RaphaelLullis[m]>
Of course, if some node I trusted requests the data and shares the hash with someone else, then the data would leak outside of my circle of trust. But personally I wouldn't worry about this because (a) I am not the one fulfilling the request and (b) my assumption is this type of data is protected but not private/secret. If it were completely private, then I would have to encrypt the data before storing and sharing the
<RaphaelLullis[m]>
key off-band.
<Kolonka[m]>
Update for anyone who remembers / cares about my 'peers connecting painfully slowly' problem: I added a couple more of the default bootstrap IPs and my peer count rapidly shot up, so a dodgy bootstrap list was likely the issue.
<Kolonka[m]>
As it happens, the bootstrap system is one of my main concerns for the protocol.
mowcat has joined #ipfs
_whitelogger_ has joined #ipfs
_whitelogger has quit [Ping timeout: 240 seconds]
quijote has quit [Remote host closed the connection]
<stebalien>
However, `ipfs swarm connect /dnsaddr/bootstrap.libp2p.io` _will_ now work. The only issue was that the peer IDs in the bootstrap list are wrong.
<stebalien>
Ah. It looks like the story is: "we may choose to deploy the correct nodes here in the future".
merethan has joined #ipfs
Ai9zO5AP has quit [Ping timeout: 246 seconds]
stebalien is now known as Stebalien
Stebalien is now known as stebalien
vmx has quit [Remote host closed the connection]
gmoro has quit [Quit: Leaving]
mowcat has quit [Remote host closed the connection]
cthorley4 has quit [Ping timeout: 246 seconds]
cthorley4 has joined #ipfs
denzuko[m] has joined #ipfs
Jerbs[m] has joined #ipfs
cthorley4 has quit [Ping timeout: 245 seconds]
<denzuko[m]>
glad you guys finally got a bridge with discord 😃
ErCiccione[m] has joined #ipfs
ngamboa[m] has joined #ipfs
cthorley4 has joined #ipfs
<shokunin[m]1>
Yeah. Whew 😃
dqx_ has joined #ipfs
<shokunin[m]1>
I’m glad it’s boosting discussion across all channels
gmoro has joined #ipfs
Ai9zO5AP has joined #ipfs
manray has joined #ipfs
ad87657[m] has joined #ipfs
Mitar has quit [Ping timeout: 264 seconds]
Jesin has quit [Quit: Leaving]
Mitar has joined #ipfs
can has quit [Ping timeout: 264 seconds]
can has joined #ipfs
Jesin has joined #ipfs
cthorley4 has quit [Ping timeout: 268 seconds]
cthorley4 has joined #ipfs
Fessus has quit [Ping timeout: 246 seconds]
manray has quit [Ping timeout: 246 seconds]
gmoro has quit [Read error: Connection reset by peer]
gmoro has joined #ipfs
ONI_Ghost has joined #ipfs
kapil____ has quit [Quit: Connection closed for inactivity]
mischat_ has joined #ipfs
Fessus has joined #ipfs
Fessus has quit [Remote host closed the connection]
mowcat has joined #ipfs
merethan has quit [Ping timeout: 268 seconds]
RDeckard[m] has joined #ipfs
manray has joined #ipfs
RDeckard[m]1 has joined #ipfs
ErCiccione[m] is now known as erciccione_[m]
merethan has joined #ipfs
erciccione_[m] is now known as ErCiccione[m][m]
manray has quit [Ping timeout: 246 seconds]
mischat_ has quit [Ping timeout: 246 seconds]
mischat has joined #ipfs
gmoro has quit [Ping timeout: 245 seconds]
iczero has quit [Remote host closed the connection]
mowcat has quit [Remote host closed the connection]
iczero has joined #ipfs
manray has joined #ipfs
appa has quit [Ping timeout: 268 seconds]
appa has joined #ipfs
placer14 has joined #ipfs
manray has quit [Ping timeout: 268 seconds]
D_ has quit [Ping timeout: 268 seconds]
D__ has joined #ipfs
jesse22 has quit [Ping timeout: 240 seconds]
mischat_ has joined #ipfs
jesse22 has joined #ipfs
woss_io has joined #ipfs
mischat has quit [Ping timeout: 268 seconds]
The_8472 has quit [Ping timeout: 240 seconds]
The_8472 has joined #ipfs
woss_io has quit [Ping timeout: 246 seconds]
Tiez has quit [Quit: WeeChat 2.4]
cyfex has quit [Ping timeout: 250 seconds]
The_8472 has quit [Ping timeout: 252 seconds]
detran has joined #ipfs
cyfex has joined #ipfs
nartir[m] has joined #ipfs
The_8472 has joined #ipfs
iarp[m] has joined #ipfs
jesse22_ has joined #ipfs
jesse22 has quit [Ping timeout: 264 seconds]
manray has joined #ipfs
manray has quit [Ping timeout: 250 seconds]
ilyaigpetrov has quit [Quit: Connection closed for inactivity]