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
jamiedubs[m]2 has joined #ipfs
<jamiedubs[m]2>
any IPFS-related events happening at NYC Blockchain Week?
aliassassin[m] has joined #ipfs
mindCrime has joined #ipfs
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
xcm has quit [Remote host closed the connection]
_nkls_ has quit [Remote host closed the connection]
xcm has joined #ipfs
abhiyerra has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
_nkls_ has joined #ipfs
mindCrime has quit [Ping timeout: 258 seconds]
mindCrime has joined #ipfs
_nkls_ has quit [Ping timeout: 245 seconds]
}ls{ has quit [Ping timeout: 246 seconds]
}ls{ has joined #ipfs
djdv has quit [Quit: lol IO driver bug brb]
ruby32 has joined #ipfs
}ls{ has quit [Client Quit]
shizy has joined #ipfs
_nkls_ has joined #ipfs
_nkls_ has quit [Ping timeout: 246 seconds]
mindCrime has quit [Ping timeout: 248 seconds]
_nkls_ has joined #ipfs
Fessus has joined #ipfs
verin0x has quit [Ping timeout: 246 seconds]
verin0x has joined #ipfs
mindCrime has joined #ipfs
user_51_ has joined #ipfs
Raed|Laptop has joined #ipfs
user_51 has quit [Ping timeout: 252 seconds]
RamRanRa has quit [Read error: Connection reset by peer]
ctOS has quit [Quit: Connection closed for inactivity]
kapil____ has joined #ipfs
_nkls_nkls_ has joined #ipfs
fauno has quit [Ping timeout: 250 seconds]
_nkls_ has quit [Ping timeout: 248 seconds]
dfs^ has left #ipfs [#ipfs]
shah^ has joined #ipfs
cyfex has quit [Ping timeout: 252 seconds]
cyfex has joined #ipfs
opal has quit [Ping timeout: 256 seconds]
opal has joined #ipfs
abhiyerra has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ruby32 has quit [Ping timeout: 250 seconds]
se7en has quit [Ping timeout: 258 seconds]
MrWimpy[m] has joined #ipfs
airwind has joined #ipfs
sfx2496 has joined #ipfs
Nd-969-M has joined #ipfs
ahve has joined #ipfs
}ls{ has joined #ipfs
Nd-969-M has quit []
snk0752 has quit [Ping timeout: 250 seconds]
snk0752 has joined #ipfs
_nkls_nkls_ has quit [Remote host closed the connection]
_nkls_ has joined #ipfs
woss_io has joined #ipfs
se7en has joined #ipfs
rtjure has quit [Ping timeout: 246 seconds]
clemo has joined #ipfs
rtjure has joined #ipfs
manray has quit [Ping timeout: 248 seconds]
Seb2100[m]1 has joined #ipfs
<Seb2100[m]1>
Hi, I am having trouble understanding exactly how IPFS uses the merkle dag? Does each node contain their own merkle dag or do nodes send a merkle dag when requested for a file or folder?
<olizilla[m]>
files and directories are stored as blocks and links to other blocks
<olizilla[m]>
links point to other blocks via the cid of the block
<olizilla[m]>
a cid is derived from the content of the block... it's content-id (CID)
rtjure has quit [Ping timeout: 250 seconds]
maxzor has joined #ipfs
<olizilla[m]>
where a block links to another block via it's cid, thats the "dag"
<olizilla[m]>
adding a large file to ipfs, it gets split up into many small blocks, each block gets its own CID
<olizilla[m]>
to calculate the CID for the whole file, a parent node is created that links to all the CIDs of those blocks
<olizilla[m]>
the CID for the parent block allows ipfs to go find all the blocks that make up the file
xcm has quit [Read error: Connection reset by peer]
manray has joined #ipfs
xcm has joined #ipfs
kapil____ has quit [Quit: Connection closed for inactivity]
_nkls_ has quit [Remote host closed the connection]
_nkls_ has joined #ipfs
mowcat has quit [Remote host closed the connection]
abhiyerra has joined #ipfs
griffinbyatt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vmx has quit [Remote host closed the connection]
_nkls_ has quit [Remote host closed the connection]
mauz555 has joined #ipfs
ZaZ1 has joined #ipfs
ZaZ has quit [Ping timeout: 246 seconds]
_nkls_ has joined #ipfs
griffinbyatt has joined #ipfs
detran has quit [Ping timeout: 248 seconds]
detran has joined #ipfs
Fessus has quit [Ping timeout: 248 seconds]
lidel` has joined #ipfs
lidel has quit [Ping timeout: 252 seconds]
lidel` is now known as lidel
detran has quit [Ping timeout: 245 seconds]
detran has joined #ipfs
souenzzo has joined #ipfs
mloki has quit [Ping timeout: 248 seconds]
mloki has joined #ipfs
souenzzo has quit [Client Quit]
mauz555 has quit []
test-foo-bar[m] has joined #ipfs
jesse22 has joined #ipfs
quijote has quit [Ping timeout: 245 seconds]
MDude has quit [Read error: No route to host]
tombusby has quit [Ping timeout: 256 seconds]
tombusby has joined #ipfs
Naughtylus[m]1 has joined #ipfs
<Naughtylus[m]1>
Hi all!
<Naughtylus[m]1>
I've recently come to notice that go-ipfs is using a constant 25% of my cpus for extended periods of time.
<Naughtylus[m]1>
Sorry if that's been asked before but, are you guys experiencing the same ? Is it expected behaviour? What is causing this? And what is the daemon actually doing with so much power?
MDude has joined #ipfs
clmay[m] has joined #ipfs
quijote has joined #ipfs
quijote has quit [Remote host closed the connection]
_nkls_ has quit [Remote host closed the connection]
_nkls_ has joined #ipfs
mindCrime has quit [Ping timeout: 255 seconds]
Oatmeal has joined #ipfs
mindCrime has joined #ipfs
MDude has quit [Ping timeout: 250 seconds]
pecastro has joined #ipfs
MDude has joined #ipfs
<lidel>
Naughtylus[m]1, do you have EnableAutoNATService or EnableRelayHop enabled? (check with: ipfs config --json Swarm)
tombusby has quit [Remote host closed the connection]
<lidel>
Naughtylus[m]1, ok. are you running v0.4.20 ?
<Naughtylus[m]1>
No 0.4.19
<lidel>
Naughtylus[m]1, update if possible. Another thing you can try is to run as dhtclient (ipfs daemon --routing=dhtclient) and see if it helped.
<lidel>
It is also possible your consumer router does not like too many connections. You can tweak connection limits by setting HighWater and LowWater to 200 and 100 (you can check current limits via: ipfs config --json Swarm)
<Naughtylus[m]1>
lidel: So I take it it's not standard. Then I wonder why it wasn't doing this before
<lidel>
Naughtylus[m]1, no network changes? OS updates? Maybe your ISP started blocking something?
ZaZ1 has quit [Read error: Connection reset by peer]
dwilliams has joined #ipfs
<dwilliams>
does anyone know why i would be able to add files but not be able to get them from public gateways? on the basic useage page, they give an example that looks like: `hash=`echo "I <3 IPFS -$(whoami)" | ipfs add -q` `curl "https://ipfs.io/ipfs/$hash"`. the curl just eventually times out
<dwilliams>
i'm assuming maybe this is a port forwarding issue?
<Naughtylus[m]1>
<dwilliams "does anyone know why i would be "> I've noticed this as well. Always attributed it to the gateway giving up on finding your node. Being the only node seeding content means your content is hard to find
fiws- has joined #ipfs
t33t3r has joined #ipfs
DavidPH has quit [Remote host closed the connection]
detran has quit [Ping timeout: 250 seconds]
MuffinPimp has quit [Ping timeout: 250 seconds]
sim590 has quit [Ping timeout: 250 seconds]
shanks8080 has quit [Ping timeout: 250 seconds]
raindrop has quit [Ping timeout: 250 seconds]
kivutar has quit [Ping timeout: 250 seconds]
raindrop has joined #ipfs
MuffinPimp has joined #ipfs
MrSparkle has quit [Ping timeout: 250 seconds]
arthur has quit [Ping timeout: 250 seconds]
Raed|Laptop has joined #ipfs
kivutar has joined #ipfs
<dwilliams>
Naughtylus[m]1: thanks. i'll keep digging. the basic example page does say that it can take a while, but doesn't say that it will timeout and fail
lassulus has quit [Ping timeout: 250 seconds]
p3t3r has quit [Ping timeout: 250 seconds]
aramiscd has quit [Ping timeout: 250 seconds]
lord4163 has quit [Ping timeout: 250 seconds]
fiws has quit [Ping timeout: 250 seconds]
brabo has quit [Ping timeout: 250 seconds]
lemmi has quit [Ping timeout: 250 seconds]
spossiba has quit [Ping timeout: 250 seconds]
<Naughtylus[m]1>
<lidel "Naughtylus, no network changes? "> I've been using ipfs for about a year now, and only noticed this activity recently, so yeah either it has to do with an update of either go-ipfs or an other component of my system, or it has to do with my activity on ipfs. As for the ISP, I don't see how that would explain increased processing power.
arthur has joined #ipfs
DavidPH has joined #ipfs
detran has joined #ipfs
aramiscd has joined #ipfs
spossiba has joined #ipfs
Novitsh has quit [Ping timeout: 246 seconds]
MrSparkle has joined #ipfs
mauz555 has joined #ipfs
<Naughtylus[m]1>
<dwilliams "Naughtylus: thanks. i'll keep di"> Maybe the gateway is a bit overloaded, or it has to do with the number of nodes currently online. I wouldn't worry too much about that. I guess you can always send me the hash of the test content, and I'll try to get it on my local node (can't timeout there)
shanks8080 has joined #ipfs
<Naughtylus[m]1>
If you really want to make sure it works
sim590 has joined #ipfs
Novitsh has joined #ipfs
lord4163 has joined #ipfs
<dwilliams>
Naughtylus[m]1: sure, its a picture of my son that I was using to test QmRsc2E1JzHofBSQkLB3QHcboNiYTNFcGiv1Ad7CtCLKay i was able to successfully get it from another computer using the ipfs cli so i do think it is working
ygrek has joined #ipfs
<dwilliams>
i am just unable to access it through any public gateway it seems
brabo has joined #ipfs
lassulus has joined #ipfs
lemmi has joined #ipfs
jon1012 has quit [Read error: Connection reset by peer]
jon1012 has joined #ipfs
rodolf0 has joined #ipfs
<postables1337[m]>
Is there any research being done into privacy preserving methods of using the DHT?
<postables1337[m]>
I've been working on some data gathering tools for a private network IPFS tool I'm writing for massive data sets and it's crazy how much data you can pick up about what people are looking for on the network just by sniffing DHT traffic
<aschmahmann[m]>
postables: There are some thoughts at, and linked from, https://github.com/ipfs/notes/issues/291. I'm sure there are other issues around with thoughts about this as well.
mindCrime has quit [Ping timeout: 246 seconds]
<postables1337[m]>
Cool thanks
gde33 has quit [Ping timeout: 258 seconds]
Kingsquee has joined #ipfs
rodolf0 has quit [Ping timeout: 248 seconds]
__jrjsmrtn__ has joined #ipfs
_nkls_ has quit [Remote host closed the connection]
_nkls_ has joined #ipfs
_jrjsmrtn has quit [Ping timeout: 248 seconds]
Ai9zO5AP has quit [Quit: WeeChat 2.4]
_nkls_ has quit [Remote host closed the connection]
cyfex has quit [Ping timeout: 248 seconds]
spinza has quit [Quit: Coyote finally caught up with me...]
rodolf0 has joined #ipfs
rodolf0 has quit [Client Quit]
seba- has quit [Remote host closed the connection]
seba- has joined #ipfs
Fessus has joined #ipfs
Fessus has quit [Remote host closed the connection]