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
erratic_ has quit [Ping timeout: 246 seconds]
_whitelogger has joined #ipfs
deadsec has left #ipfs [#ipfs]
xcm has quit [Remote host closed the connection]
cthorley4 has quit [Ping timeout: 245 seconds]
xcm has joined #ipfs
Biopandemic has quit [Ping timeout: 252 seconds]
^andrea^0 has quit [Quit: Ping timeout (120 seconds)]
^andrea^0 has joined #ipfs
merethan has quit [Ping timeout: 250 seconds]
shizy has joined #ipfs
merethan has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
The_8472 has joined #ipfs
merethan has quit [Remote host closed the connection]
zeden has joined #ipfs
Kingsquee has quit [Remote host closed the connection]
mdrights has joined #ipfs
Kingsquee has joined #ipfs
sz0 has joined #ipfs
<jamiew>
DarkDrgn2k[m]: wow nice find
quijote_ has joined #ipfs
kyan has joined #ipfs
quijote has quit [Ping timeout: 252 seconds]
mdrights has quit [Quit: WeeChat 2.3]
quijote has joined #ipfs
quijote_ has quit [Ping timeout: 246 seconds]
<Caleb[m]2>
+filecoin:matrix.org <-- cool
cthorley4 has joined #ipfs
mdrights has joined #ipfs
zeden has quit [Quit: WeeChat 2.4]
Belkaar has quit [Read error: Connection reset by peer]
mowcat has quit [Remote host closed the connection]
Belkaar has joined #ipfs
Belkaar has joined #ipfs
shizy has quit [Quit: WeeChat 2.4]
_whitelogger has joined #ipfs
mauz555 has quit [Remote host closed the connection]
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
The_8472 has joined #ipfs
zeden has quit [Quit: WeeChat 2.4]
sz0 has quit [Quit: Connection closed for inactivity]
The_8472 has quit [Ping timeout: 240 seconds]
lanlink[m] has joined #ipfs
The_8472 has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
The_8472 has joined #ipfs
xcm has quit [Remote host closed the connection]
ricekrispie has joined #ipfs
xcm has joined #ipfs
ricekrispie2 has quit [Ping timeout: 245 seconds]
The_8472 has quit [Ping timeout: 240 seconds]
The_8472 has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
random_yanek has quit [Ping timeout: 250 seconds]
The_8472 has joined #ipfs
random_yanek has joined #ipfs
The_8472 has quit [Ping timeout: 240 seconds]
The_8472 has joined #ipfs
random_yanek has quit [Ping timeout: 246 seconds]
mikaela[m]6 has joined #ipfs
random_yanek has joined #ipfs
<postables[m]>
when you lookup an IPNS record through a gateway, is there any kind of caching system in place similar to how if you view a regular file, the gateway temporarily caches it?
<mikaela[m]6>
I think there is at least as a experimental feature
<postables[m]>
interesting 🤔any idea how that can be enabled
joecool_ has quit [Remote host closed the connection]
kapil____ has quit [Quit: Connection closed for inactivity]
<postables[m]>
ah ok i have that enabled on the node thats running the gateway, perhaps theres some other issue why its not resolving via a cache, ill do some more digging
Pulse2496 has joined #ipfs
<mikaela[m]6>
According to that link, maybe the IPNS host/owner doesn't have it enabled?
<postables[m]>
im not sure, i published from one of my other nodes. However, i think it would only work if i subcribed to the pubsub topic thats its being publisehd on?
<postables[m]>
if something like this were used with DAG generation on folders it could in theory lead to improved performance
<savantgarde>
`ipfs get zdpuAyyGtvC37aeZid2zh7LAGKCbFTn9MzdqoPpbNQm3BCwWT` (this should be a tiny JSON document) just hangs for me, is there a way to debug?
<savantgarde>
I'm on OS X BTW and the ipfs version is 0.4.19-dev
<savantgarde>
I'm quite new to IPFS so I'm not sure what could be going wrong here
<savantgarde>
IPFS is installed via homebrew
random_yanek has quit [Ping timeout: 255 seconds]
woss_io has joined #ipfs
woss_io has quit [Read error: Connection reset by peer]
tobs` has joined #ipfs
tobs has quit [Quit: o/]
tobs` is now known as tobs
seba- has quit [Remote host closed the connection]
seba- has joined #ipfs
erikj_ has quit [Ping timeout: 245 seconds]
D_ has quit [Remote host closed the connection]
linear_ has quit [Ping timeout: 245 seconds]
erikj has joined #ipfs
D_ has joined #ipfs
DickClarke has left #ipfs [#ipfs]
linear has joined #ipfs
random_yanek has joined #ipfs
SchrodingersScat has quit [Ping timeout: 252 seconds]
linear has quit [Ping timeout: 245 seconds]
linear has joined #ipfs
rendar has joined #ipfs
kyan has quit [Ping timeout: 255 seconds]
SchrodingersScat has joined #ipfs
nimaje has quit [Killed (rajaniemi.freenode.net (Nickname regained by services))]
ylp has joined #ipfs
nimaje has joined #ipfs
Cavedude has joined #ipfs
Cavedude_ has quit [Ping timeout: 245 seconds]
eof has quit [Ping timeout: 245 seconds]
Anduck has quit [Ping timeout: 245 seconds]
Anduck has joined #ipfs
eof has joined #ipfs
kapil____ has joined #ipfs
<postables[m]>
savantgarde: its hanging for me as well, where did you find this hash?
<savantgarde>
Might it be hanging because the document isn't actually published? I.e. it might just be symbolic of the empty Radicle machine
<savantgarde>
Will `ipfs get` just hang if the content in question isn't found?
<postables[m]>
usually when im trying to debug this kind of stuff i'll run a `ipfs dht findprovs <hash>` to see if any providers of the hash can be found. If not, then you're basically SOL because nobody is storing the content.. If there are providers there then you know that nodes are hosting the content and are online.
<postables[m]>
You can then find `ipfs ping <peer-id>` of whatever provider(s) show up, that way you can measure latency of the connection to see if that could be causing the slowness.
<postables[m]>
ah i see, well I ran `ipfs dht findprovs <hash>` and nothing showed up
<postables[m]>
So `Might it be hanging because the document isn't actually published` seems like it would be the cause
<savantgarde>
OK, interesting, do you know if it's documented everywhere if ipfs will wait if a hash isn't found?
<savantgarde>
When trying `ipfs dht findprovs zdpuAyyGtvC37aeZid2zh7LAGKCbFTn9MzdqoPpbNQm3BCwWT`, it seems to hang as well
<savantgarde>
Sorry I meant to say if it's documented anywhere
anseladams has quit [Ping timeout: 246 seconds]
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
<savantgarde>
It keeps dialing peers so I guess it keeps looking until something shows up
<savantgarde>
(I tried with verbose mode)
mischat has joined #ipfs
dharwin[m] has joined #ipfs
ZaZ has joined #ipfs
xcm has quit [Remote host closed the connection]
mischat has quit [Ping timeout: 258 seconds]
xcm has joined #ipfs
kishansagathiya_ has joined #ipfs
mischat has joined #ipfs
<kishansagathiya_>
`ipfs tar add tar_file` always gives me invalid tar header, Is this a bug? Or am I missing something here?
<kishansagathiya_>
I meant it errors with `Error: archive/tar: invalid tar header`
anseladams has joined #ipfs
chiui has joined #ipfs
alexgr has quit [Ping timeout: 246 seconds]
alexgr has joined #ipfs
mdrights has quit [Ping timeout: 255 seconds]
xcm has quit [Ping timeout: 258 seconds]
mischat has quit [Ping timeout: 240 seconds]
xcm has joined #ipfs
kishansagathiya_ has quit [Ping timeout: 256 seconds]
ZaZ1 has joined #ipfs
<postables[m]>
savantgarde: your node will timeout if it doesnt find the file eventually
ZaZ has quit [Ping timeout: 250 seconds]
Pulse2496 has quit [Ping timeout: 250 seconds]
<ylp>
kishansagathiya[: do you create the tar on the same computer ?
<ylp>
a common problem can be ftp transfert in ascii mode for instance
lordcirth_ has quit [Remote host closed the connection]
lordcirth_ has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
mowcat has joined #ipfs
airwind has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
mischat has joined #ipfs
i1nfusion has joined #ipfs
mikaela[m]6 has left #ipfs ["User left"]
mikaela[m]6 has joined #ipfs
<postables[m]>
also the hanging during `ipfs dht findprovs` is because you cant find anyone providing the hash. If you tried against `QmS4ustL54uo8FzR9455qaxZwuMiUhyvMcX9Ba8nUH4uVv` you would get a lot of hosts back right away.
<savantgarde>
postables[m]: Thanks, is it possible to configure the timeout?
<postables[m]>
`ipfs --timeout=....` so `ipfs --timeout=1h` or `ipfs --timeout=24h`
<savantgarde>
Ah thanks
m_tadeu has joined #ipfs
m_tadeu_ has quit [Ping timeout: 252 seconds]
mauz555 has joined #ipfs
mischat has quit [Remote host closed the connection]
mischat has joined #ipfs
Soo_Slow has joined #ipfs
Steverman has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
i1nfusion has quit [Remote host closed the connection]
quijote has joined #ipfs
Xeyame has joined #ipfs
Wioxjk has joined #ipfs
mikaela[m]6 has left #ipfs ["User left"]
mikaela[m]6 has joined #ipfs
spinza has joined #ipfs
rendar_ has joined #ipfs
rendar has quit [Ping timeout: 244 seconds]
griffinbyatt has joined #ipfs
crimastergogo has joined #ipfs
gmoro_ has joined #ipfs
gmoro__ has quit [Ping timeout: 246 seconds]
gmoro__ has joined #ipfs
gmoro_ has quit [Ping timeout: 246 seconds]
crimastergogo has quit [Quit: crimastergogo]
KempfCreative has joined #ipfs
crimastergogo has joined #ipfs
crimastergogo has quit [Client Quit]
crimastergogo has joined #ipfs
crimastergogo has quit [Remote host closed the connection]
crimastergogo has joined #ipfs
Steverman has quit [Ping timeout: 264 seconds]
Wioxjk has quit [Ping timeout: 245 seconds]
Steverman has joined #ipfs
KempfCreative has quit [Ping timeout: 255 seconds]
Wioxjk has joined #ipfs
Steverman has quit [Ping timeout: 246 seconds]
Steverman has joined #ipfs
mikaela[m]6 has left #ipfs ["User left"]
crimastergogo has quit [Quit: crimastergogo]
mischat has quit [Remote host closed the connection]
malaclyps has quit [Read error: Connection reset by peer]
mischat has joined #ipfs
malaclyps has joined #ipfs
mischat has quit [Ping timeout: 245 seconds]
<kishansagathiya[>
ylp: One was created on the same computer, one was downloaded(tar for go installation), I got same result on both
crimastergogo has joined #ipfs
crimastergogo has quit [Remote host closed the connection]
spinza has quit [Quit: Coyote finally caught up with me...]
<drbh[m]>
why do you think it couldnt resolve my own multiaddr?
mikaela[m]6 has joined #ipfs
vmx has joined #ipfs
ygrek__ has joined #ipfs
mischat has quit []
Steverman has quit [Quit: WeeChat 2.4]
<drbh[m]>
If you can always find a files host's IP address is this not a security concern? Couldn't somone do targeted DDOS attacks to that IP address if they want to take down the person hosting that file?
Steverman has joined #ipfs
quijote_ has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
quijote has quit [Ping timeout: 246 seconds]
The_8472 has joined #ipfs
Pulse2496 has quit [Ping timeout: 246 seconds]
matt-h has joined #ipfs
mdrights has joined #ipfs
mauz555 has joined #ipfs
mauz555 has quit [Remote host closed the connection]