MDude has quit [Quit: Going offline, see ya! (www.adiirc.com)]
MDude has joined #ipfs
ashark has joined #ipfs
ashark has quit [Ping timeout: 264 seconds]
Aranjedeath has quit [Quit: Three sheets to the wind]
ericxtang has joined #ipfs
ashark has joined #ipfs
ashark has quit [Ping timeout: 260 seconds]
BZ55 has quit [Ping timeout: 248 seconds]
ashark has joined #ipfs
ashark has quit [Ping timeout: 240 seconds]
colatkinson has joined #ipfs
reit has quit [Ping timeout: 268 seconds]
athan has quit [Remote host closed the connection]
ericxtang has quit [Remote host closed the connection]
Oatmeal has joined #ipfs
<Mr0grog>
coyotespike: If you are trying to connect from a browser to another node, that other node has to have the websockets transport turned on. You can see a bit more about it here (which also covers browser-to-browser with a desktop node in the middle): https://github.com/ipfs/js-ipfs/tree/master/examples/exchange-files-in-browser
ericxtang has joined #ipfs
<Mr0grog>
If you are trying to connect two browsers, you have to either use websocket-star (which means there is an intermediary node as in that example), or use circuit relaying (still with an intermediary; see this example: https://github.com/ipfs/js-ipfs/tree/master/examples/circuit-relaying). The only way to connect directly is using webrtc, which I am not fully up on the details of. It's also kind of unstable as far as I know.
ericxtang has quit [Ping timeout: 276 seconds]
MDude has quit [Ping timeout: 240 seconds]
MDude has joined #ipfs
brknlink has joined #ipfs
brknlink has quit [Client Quit]
ONI_Ghost has quit [Read error: Connection reset by peer]
leeola has quit [Quit: Connection closed for inactivity]
tglman has quit [Ping timeout: 276 seconds]
vivus has joined #ipfs
vivus has left #ipfs [#ipfs]
ckwaldon has joined #ipfs
tglman has joined #ipfs
detectiveaoi has quit [Ping timeout: 240 seconds]
rendar has quit []
Encrypt has joined #ipfs
tglman has quit [Ping timeout: 255 seconds]
robattila256 has joined #ipfs
kupad has quit [Ping timeout: 264 seconds]
tglman has joined #ipfs
espadrine has joined #ipfs
Jo[m] has joined #ipfs
stekke[m] has joined #ipfs
jes[m] has joined #ipfs
bomb-on has quit [Quit: SO LONG, SUCKERS!]
bomb-on has joined #ipfs
abourget has joined #ipfs
mtodor has joined #ipfs
lnostdal has quit [Ping timeout: 276 seconds]
jonnycrunch has quit [Ping timeout: 256 seconds]
jonnycrunch has joined #ipfs
hryniuk has quit [Quit: Leaving]
lldd_ has joined #ipfs
Kalvo has joined #ipfs
<Kalvo>
Hey everyone. I am having a strange issue. It seems like I cannot remove a file from my node. I added a 500MB or so video to my ipfs node. As far as I know add also does a pin by default right? So I try to do pin rm to remove the hash. Says its not pinned. So I do a gc on the repo but the file still exists. I can play it through my node but cannot if I shut off my node and use the pulbic gateway. So It looks like its not cached by
<Kalvo>
anyone else, not pinned, gc doesnt remove it but somehow I can still play it over ipfs?
lnostdal has joined #ipfs
<Kalvo>
This repo is quite large. over 20GB, 100,000+ files.
<Kalvo>
Any diagnostic commands or something I can run to see if the file exists on my node? Because it seems to persist no matter what I do.
<Kalvo>
Running version 0.4.14
lldd_ has quit [Quit: Leaving]
tglman has quit [Ping timeout: 240 seconds]
stekke[m] has left #ipfs ["User left"]
domanic has joined #ipfs
tglman has joined #ipfs
kn0rki has joined #ipfs
runiq[m] has joined #ipfs
arthuredelstein has quit [Ping timeout: 264 seconds]
leolrrj has quit [Remote host closed the connection]
leolrrj has joined #ipfs
leolrrj has quit [Remote host closed the connection]
leolrrj has joined #ipfs
mtodor has quit [Remote host closed the connection]
mtodor has joined #ipfs
kn0rki has quit [Ping timeout: 260 seconds]
kn0rki has joined #ipfs
mtodor has quit [Remote host closed the connection]
leolrrj has quit [Remote host closed the connection]
leolrrj has joined #ipfs
leolrrj has quit [Remote host closed the connection]
leolrrj has joined #ipfs
kn0rki has quit [Ping timeout: 260 seconds]
OS-27110 has quit [Remote host closed the connection]
OS-27110 has joined #ipfs
abourget_ has joined #ipfs
<abourget_>
hey guys.. if I call the /api/v0/name/publish endpoint .. will it go through the `namesys` pubsub propagation ?
kn0rki has joined #ipfs
<abourget_>
I'm currently orchestrating the launch of EOS .. perhaps you guys have heard about that..
<abourget_>
ipfs + ipns does *all* we need with the right semantics..
<abourget_>
but the slowness of `ipns` is killing us..
<abourget_>
I wasn't able to see the super fast ipns resolution and publishing..
Neomex has quit [Remote host closed the connection]
<abourget_>
with the `--enable-namesys-pubsub` ..
Mateon3 has joined #ipfs
Mateon1 has quit [Ping timeout: 260 seconds]
Mateon3 is now known as Mateon1
lnostdal has quit [Ping timeout: 260 seconds]
mtodor has joined #ipfs
Caterpillar has quit [Quit: You were not made to live as brutes, but to follow virtue and knowledge.]
leolrrj has quit [Remote host closed the connection]
leolrrj has joined #ipfs
leolrrj has quit [Remote host closed the connection]
leolrrj has joined #ipfs
lnostdal has joined #ipfs
mtodor has quit [Remote host closed the connection]
sz0 has joined #ipfs
leolrrj has quit [Remote host closed the connection]