infinity0 has quit [Remote host closed the connection]
infinity0 has joined #ipfs
infinity0 has quit [Remote host closed the connection]
qqueue has joined #ipfs
infinity0 has joined #ipfs
infinity0 has quit [Remote host closed the connection]
Tallgeese has joined #ipfs
infinity0 has joined #ipfs
jmill has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
infinity0 has quit [Remote host closed the connection]
<qqueue>
hey, I walked through the ipfs tutorial, and started up the daemon. about a minute after that though, the daemon stated using a ton of cpu and bandwidth (>1GB transfered) and according to ipfs swarm peers, opened ~500 connections despite me not doing anything. is that expected? What's the daemon doing? participating in other filesharing? my ~/.ipfs local dir is still relatively small <10MB
Tallgeese_ has quit [Ping timeout: 272 seconds]
nivekuil has quit [Quit: q]
nivekuil` has joined #ipfs
Tallgeese_ has joined #ipfs
jmill has joined #ipfs
<lgierth>
it announces hashes to the network when you add or fetch data
<lgierth>
it needs a bit more optimization to be more resource friendly
<lgierth>
we have a pretty good plan for that
<lgierth>
qqueue: you can try to start it with `ipfs daemon --routing=dhtclient` to turn off the announcements (provider records)
<lgierth>
then it should be much better
<qqueue>
ok, thanks
<qqueue>
is there more documentation on the "announce hashes" part and diffeence with '--dhtclient=routing'? I'm familiar with bittorrent and i've followed ipfs on and off
Tallgeese has quit [Ping timeout: 272 seconds]
droman has quit []
<qqueue>
i guess I can see participating in the DHT by default, but the amount of cpu/bandwidth it was using seemed really high compared to mainline dht
Tallgeese_ has quit [Ping timeout: 240 seconds]
<lgierth>
whyrusleeping: do you remember in which issue we discussed the various possible new --routing modes?
<tangent128>
enable the configuration option, but as I understand it the actual command to add filestore files only exists in a fork right now.
<sonata>
aha
ygrek has quit [Ping timeout: 246 seconds]
<sonata>
i did `ipfs pubsub sub --discover -- ipfs` several minutes ago and it's just sitting there unresponsive, is this normal?
gmcabrita has quit [Quit: Connection closed for inactivity]
<sonata>
s/unresponsive/doing nothing/
engdesart has quit [Quit: yes]
Mitar has quit [Ping timeout: 260 seconds]
robattila256 has joined #ipfs
JayCarpenter__ has quit [Quit: Page closed]
onabreak has joined #ipfs
infinity0 has joined #ipfs
cxl000 has quit [Quit: Leaving]
sonata has quit [Remote host closed the connection]
cxl000 has joined #ipfs
kvda has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sein has joined #ipfs
sein is now known as Guest57029
archpc has quit [Ping timeout: 255 seconds]
dignifiedquire has quit [Quit: Connection closed for inactivity]
treaki__ has joined #ipfs
<whyrusleeping>
tangent128: no, filestore stuff is all in the lastest versions
<whyrusleeping>
just enable the config, and use --nocopy with your adds
treaki has quit [Ping timeout: 255 seconds]
<tangent128>
Ahhh, I was reading outdated docs, I thought the command was still "ipfs filestore add"
martinBrown_ has joined #ipfs
<whyrusleeping>
yeah, that was how it worked when it was still unmerged
martinBrown has quit [Remote host closed the connection]
martinBrown_ is now known as martinBrown
Guest57029 has quit [Quit: Alt-F4 at console]
archpc has joined #ipfs
kvda has joined #ipfs
reit has joined #ipfs
reit has quit [Client Quit]
anewuser has quit [Quit: anewuser]
_whitelogger has joined #ipfs
jaboja has quit [Quit: Leaving]
tilgovi has joined #ipfs
kvda has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
onabreak has quit [Ping timeout: 260 seconds]
rendar has joined #ipfs
kvda has joined #ipfs
espadrine has joined #ipfs
kvda has quit [Client Quit]
HoloIRCUser2 has joined #ipfs
Mitar has joined #ipfs
reit has joined #ipfs
reit has quit [Read error: Connection reset by peer]
kvda has joined #ipfs
mildred4 has quit [Ping timeout: 268 seconds]
stoopkid has quit [Quit: Connection closed for inactivity]
Caterpillar has joined #ipfs
stoopkid has joined #ipfs
tilgovi has quit [Quit: No Ping reply in 180 seconds.]
john2 has joined #ipfs
tilgovi has joined #ipfs
john2 has quit [Ping timeout: 245 seconds]
kvda has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jleon has joined #ipfs
jleon has quit [Client Quit]
maxlath has joined #ipfs
HoloIRCUser2 has quit [Ping timeout: 260 seconds]
maxlath has quit [Quit: maxlath]
pratch has quit [Remote host closed the connection]
onabreak has joined #ipfs
pratch has joined #ipfs
spm_draget has joined #ipfs
<spm_draget>
A few quick questions. :)
<spm_draget>
What kind of caching strategies are there, if any? If I am node A and connect via B to C… and B had served files from C before, but now C is down, will I get the file anyways?
<spm_draget>
How much effort had been put into auditing the protocol and testing against existing attacks?
<spm_draget>
The hash identifies a file - so there are no dynamic resources? Have you heard about freenet before? It followed a similar approach for a lot of years.
maxlath has joined #ipfs
neurrowcat has quit [Ping timeout: 245 seconds]
droman has joined #ipfs
fzzzr has joined #ipfs
reit has joined #ipfs
_whitelogger has joined #ipfs
reit has quit [Ping timeout: 260 seconds]
tilgovi has quit [Quit: No Ping reply in 180 seconds.]
fzzzr has quit [Quit: WeeChat 1.7.1]
sein has joined #ipfs
sein is now known as Guest31760
archpc has quit [Ping timeout: 240 seconds]
john2 has joined #ipfs
ZaZ has joined #ipfs
ZaZ has quit [Read error: Connection reset by peer]
steefmin has quit [Ping timeout: 260 seconds]
steefmin has joined #ipfs
gmcabrita has joined #ipfs
onabreak has quit [Ping timeout: 260 seconds]
btmsn has joined #ipfs
kvda has joined #ipfs
maxlath has quit [Ping timeout: 258 seconds]
dignifiedquire has joined #ipfs
maxlath has joined #ipfs
maxlath has quit [Ping timeout: 258 seconds]
Encrypt has joined #ipfs
Caterpillar has quit [Quit: You were not made to live as brutes, but to follow virtue and knowledge.]
todder has quit [Quit: is such a quitter...]
todder has joined #ipfs
daviddias has quit [Quit: Connection closed for inactivity]
ZarkBit has quit [Quit: Going offline, see ya! (www.adiirc.com)]
ZarkBit has joined #ipfs
Encrypt has quit [Quit: Quit]
Foxcool has joined #ipfs
bedeho has joined #ipfs
dimitarvp has joined #ipfs
mildred4 has joined #ipfs
JayCarpenter has quit [Ping timeout: 260 seconds]
onabreak has joined #ipfs
maxlath has joined #ipfs
HostFat has quit [Quit: Leaving]
Foxcool has quit [Ping timeout: 240 seconds]
vgeds has joined #ipfs
Muis has quit [Quit: Connection closed for inactivity]
<Atrus[m]>
It is similar, but ipfs has some stronger guarantees on what files end up on your system.
<Atrus[m]>
If B has pinned the file, it'll have it for sure, otherwise B may have garbage collected the file and you can't get it
rendar has quit [Quit: std::lower_bound + std::less_equal *works* with a vector without duplicates!]
vgeds has quit [Quit: quit]
<Kubuxu>
lidel: again great job with the ipfs-firefox-addon and porting it to webext, thanks for your time and contributions
Soulweaver has quit [Remote host closed the connection]
vgeds has quit [Ping timeout: 240 seconds]
m3lt_ has quit [Quit: leaving]
maxlath1 has joined #ipfs
maxlath has quit [Ping timeout: 240 seconds]
maxlath1 is now known as maxlath
Foxcool has joined #ipfs
Foxcool has quit [Ping timeout: 240 seconds]
steefmin has quit [Ping timeout: 260 seconds]
steefmin has joined #ipfs
espadrine has quit [Ping timeout: 245 seconds]
Encrypt has quit [Quit: Quit]
shizy has joined #ipfs
eater has quit [Ping timeout: 268 seconds]
asyncsec has joined #ipfs
eater has joined #ipfs
mildred4 has quit [Ping timeout: 272 seconds]
ikpunk[m] has joined #ipfs
bedeho has quit [Remote host closed the connection]
Encrypt has joined #ipfs
petroleum has joined #ipfs
elkalamar has quit [Ping timeout: 240 seconds]
Boomerang has joined #ipfs
btmsn1 has joined #ipfs
pratch has quit [Remote host closed the connection]
btmsn has quit [Ping timeout: 240 seconds]
btmsn1 is now known as btmsn
jmill has joined #ipfs
pratch has joined #ipfs
Caterpillar has joined #ipfs
Akaibu has quit [Quit: Connection closed for inactivity]
jsgrant_om has quit [Ping timeout: 240 seconds]
<benhylau[m]>
What's the recommended way to expose the http gateway to public? Are the `ipfs gateway` commands in the plans?
elkalamar has joined #ipfs
<jamesstanley>
I just added config to nginx to reverse-proxy to it
<benhylau[m]>
Yea I have the same setup, wondering if that's the suggested way or ipfs has some built-in config
bedeho has joined #ipfs
<tangent128>
If IPFS is the only HTTP daemon running, you could probably set the Addresses.Gateway config to "/ip4/0.0.0.0/tcp/80" or something like that (plus IPV6 address as that's probably applicable these days)
<tangent128>
(On a related note, are there security implications to hosting a public gateway in writeable mode? Or is it just a bandwidth concern?)
achin has quit [Quit: WeeChat 1.7.1]
<tangent128>
Though with that setup visitors would get a 404 if they visited just the root of the domain.
<lidel>
tangent128, someone could perform denial of service eg. by pinning a lot of stuff, and learn a lot about internals which could provide attack vectors
<tangent128>
I don't think the REST API pins? Point about timing attack though.
<tangent128>
Wait, no, a GET exposes whether you've cached content anyways.
<lidel>
Yes, you can pin via API. They also could also upload content to your node which could be later used against you "see, this illegal content originated from this node"
<tangent128>
To be clear, I'm talking about the mode supporting PUT and POST, not the full API which is a different listening socket.
<lidel>
Exposing API without access control -- vary, vary bad idea.
<lidel>
*e
<tangent128>
Ahh, point-of-origin.
<tangent128>
(the API can be configured as a separate port from the gateway, so I think you can expose POSTing content without the rest of those options. But if you become an open relay to originate content you might be liable for, I can see that issue.)
<lidel>
tangent128, yeah, HTTP API is quite powerful: https://ipfs.io/docs/api/#index so if you really want to expose parts of it, you probably want to introduce an abstraction layer on top of it, which takes care of ACL etc
jmill has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ZarkBit has quit [Ping timeout: 260 seconds]
bedeho has quit [Remote host closed the connection]
kvda has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rcat has quit [Remote host closed the connection]
patcon has joined #ipfs
elkalamar_ has joined #ipfs
elkalamar has quit [Ping timeout: 245 seconds]
neurrowcat has joined #ipfs
espadrine has joined #ipfs
maxlath has quit [Ping timeout: 245 seconds]
maxlath has joined #ipfs
m3lt has joined #ipfs
robattila256 has quit [Quit: WeeChat 1.7.1]
robattila256 has joined #ipfs
Martin____ has joined #ipfs
chris613 has joined #ipfs
donuts has joined #ipfs
anewuser has joined #ipfs
<lidel>
tangent128, ah, you mean writable-gateway, not actual API
<lidel>
thats probably a lot "safer"
mildred4 has joined #ipfs
<lidel>
Kubuxu, do we have a doc describing "writable gateway" feature somewhere?
jmill has joined #ipfs
<Kubuxu>
not really
<Kubuxu>
I am not sure off the head to what it refers to
shizy has quit [Ping timeout: 245 seconds]
<Kubuxu>
90% it is allowing to PUT stuff as in add files
<Kubuxu>
from the gateway prot
<Kubuxu>
port
neurrowcat has quit [Read error: Connection reset by peer]
neurrowcat has joined #ipfs
xyendor has left #ipfs ["WeeChat 1.7.1"]
chris613 has left #ipfs [#ipfs]
<tangent128>
What I've determined from earlier questions in this channel, the source code, and experimenting:
neurrowcat has quit [Read error: Connection reset by peer]
neurrowcat has joined #ipfs
<tangent128>
- a POST to /ipfs will let you add (but not pin) a file and get back its has (via the "ipfs-hash" HTTP header)
JayCarpenter has joined #ipfs
jmill has quit [Client Quit]
<tangent128>
- a DELETE to /ipfs/QMHashGoesHere/path/to/file will return the ipfs-hash of that file tree, removing the indicated path
<tangent128>
- a PUT to /ipfs/QMHashGoesHere/path/to/file will, if the path does not exist in the referenced tree, return the ipfs-hash of that file tree with the put file at the indicated path
<Kubuxu>
tangent128: could you document your findings on discuss.ipfs.io? That would be awesome.
<tangent128>
*However*, if a file already exists at that path in the tree, it returns the raw ipfs-hash of the file you PUT, instead of an updated file tree. I am 90% that is a bug and not intended behavior, but my pastebin experiment had to issue a DELETE before PUTing an updated html file..
<Kubuxu>
yeah, that might be a case
<Kubuxu>
it is quite an old, under documented, under tested feature
<Kubuxu>
we have plans for gateway rewrite and extraction for a long time
<Kubuxu>
currently it is huge monolithic mess
<tangent128>
I would eventually like to see an ability for a writable gateway to publish an IPNS record you upload to it (not using the gateway node's key(s); it should be possible for the private key to never leave the client browser)
<tangent128>
What's the "official" name of the feature? "REST API"? "Writeable Gateway"?
<Kubuxu>
Writeable Gateway Flag
Akaibu has joined #ipfs
neurrowcat_ has joined #ipfs
neurrowcat has quit [Ping timeout: 255 seconds]
<Martin____>
hello. i don't know if this is the right place to ask a such a generic question. I try to understand the structure of a dht. It's a table with 2 attributes one with the key (block id) and the other with the value (peer info)? Am i correct?
neurrowcat has joined #ipfs
donuts has quit [Ping timeout: 260 seconds]
neurrowcat_ has quit [Ping timeout: 255 seconds]
vgeds has joined #ipfs
bedeho has joined #ipfs
<Kubuxu>
for the most part yes
vgeds has quit [Remote host closed the connection]
<Martin____>
for the most part? when would it be different?
elkalamar_ has quit [Ping timeout: 260 seconds]
vgeds has joined #ipfs
<Martin____>
is there a record as well like IPFS NODE ID -> PEER Info?
vgeds has quit [Ping timeout: 240 seconds]
<Kubuxu>
yes
<Kubuxu>
and there are IPNS records too
<Kubuxu>
PeerID=>signed IPNS record
<Martin____>
but its all store in one dht... i mean there are not like 3 dhts floating around?
<Martin____>
thanks for the answer :) that really helps me alot
<jamesstanley>
I'm trying out the js-ipfs, and I find if I publish a file using js-ipfs (in the browser), connected to libp2p-webrtc-star peers, I can fetch it using other js-ipfs apps connect to libp2p-webrtc-peers, but not using go-ipfs; is the network basically split because there is nothing to connect go-ipfs to libp2p-webrtc-star peers?
<Kubuxu>
Martin____: yes but iirc keys are namespaced