<witten>
I've got a browser-only js-ipfs gateway that's now almost usable.. it uses service workers to intercept IPFS content requests
Mateon3 has joined #ipfs
Mateon1 has quit [Ping timeout: 264 seconds]
Mateon3 is now known as Mateon1
fredthomsen has quit [Quit: Leaving.]
dfcnvt has joined #ipfs
<dfcnvt>
Is ipfs strictly a protocol that works the same model as block-chain but is a web interface?
<witten>
no, it doesn't work like a blockchain
<Fess>
ipfs and blockchains are unrelated technology
<witten>
there is a separate blockchain called filecoin that the same company makes to ultimately use with ipfs
<witten>
but if you want to invest, I'd be happy to take your money
<ion>
Blockchains could be implemented on top of IPFS but it's a different concept.
espadrine has quit [Ping timeout: 256 seconds]
<dfcnvt>
I just learned this ipfs in an half hour ago. So, I'm not quite fully understand it but can make some assumptions on what ipfs really is. My guess is whenever there is an original content (raw plain file) being added to the system -- it will keeps the same content to the single server for anyone out there wish to request that file. And if somehow someone created a new file that is assumed to be an orginal
<dfcnvt>
one but learned there is an original one already exist in the server -- it save them space and time and all they had to worry about is the hashes to be viewed as a file?
<dfcnvt>
I'll save you all the time and headache - I will research on my own time to fully understand it.
robattila256 has quit [Ping timeout: 264 seconds]
robattila256 has joined #ipfs
<witten>
that's a pretty good approximation actually
ygrek has quit [Ping timeout: 248 seconds]
<walle303>
Well that's just nice
<walle303>
`ipfs add` segfaulted while mirroring english wikipedia
robattila256 has quit [Ping timeout: 264 seconds]
<walle303>
Time to start over I guess
<dfcnvt>
...Question, can you set permission toward to the content...preventing anyone to use it unless expressed in permission?
<dfcnvt>
with*
<witten>
dfcnvt: not to my knowledge.. you can encrypt it..
<witten>
walle303: you should file the segfault if you have a repro
<walle303>
It looks like it was gdbus that segfaulted
<walle303>
So it's unlikely an ipfs bug
<witten>
ah ok
<walle303>
It did take out the ipfs add command with it
tdeo has joined #ipfs
<ion>
A blockchain is a single Merkle DAG (with a specific node format) and every user is expected to hold a full copy. IPFS lets you store and transfer nodes (with arbitrary contents) of independent Merkle DAGs and nobody is expected to have all of them. Blockchains involve a consensus protocol which is not relevant for IPFS.
<witten>
the main consensus in IPFS is that if it hashes to the expect hash, then it's the right content :)
robattila256 has joined #ipfs
tdeo has quit [Quit: WeeChat 1.9.1]
<witten>
s/expect/expected/
tdeo has joined #ipfs
sz0 has joined #ipfs
Rusty78 has joined #ipfs
<Rusty78>
I heard JS-IPFS is interoperable with Go-IPFS now, does anyone know if that's true?
<witten>
if that happened, I missed it
<witten>
I know it's a goal
<witten>
if content happens to be loaded on gateway.ipfs.io, it will load in js-ipfs
<Rusty78>
witten: but not the other way around right?
<witten>
so you can hamfist content from go-ipfs to js-ipfs that way
<witten>
I haven't tested if it's the other way around or not
<witten>
would be easy to try with one of the js-ipfs examples that add content
<Rusty78>
I will try that. Do you happen to know if they make JS-IPFS interoperable with GO-IPFS will that officially make a browser node/daemon possible?
larpanet has quit [Ping timeout: 256 seconds]
<witten>
it's already possible.. it just may not pull content from go-ipfs
<witten>
but that would make it even possible-er
larpanet has joined #ipfs
<Rusty78>
I'll try it out to stop bothering you but from memory I believe you needed to still run the IPFS dameon via node.js and then you could connect to it via your browser
<Rusty78>
I was asking if it was possible to run a full node and connect to other peers from your browser (without an external daemon running)
<witten>
and at prototype-level it actually works pretty well
<Rusty78>
Fantastic, reading the docs right now, thank you for the link
<witten>
"docs" are putting it strongly
<witten>
still gotta finish the README
<Rusty78>
haha, gotta start somewhere
<witten>
yup
whatevz has joined #ipfs
larpanet has quit [Ping timeout: 265 seconds]
whatevz has left #ipfs [#ipfs]
rendar has joined #ipfs
lght[m] has left #ipfs ["User left"]
onikuma has joined #ipfs
kvda has joined #ipfs
Fess has quit [Quit: Leaving]
kvda has quit [Max SendQ exceeded]
<keks[m]>
lgierth: in epidemic-broadcast-tree-lingo that's called lazy push, in contrast to eager push. they have a different tradeoff in terms of bandwidth and latency, but the optimum seams to be to build a spanning tree (or one per sender) that is embedded in a more densely connected graph and eager push along the tree edges and lazy push along the non-tree edges. that way you'll see if the tree broke (because you'll be told about a
<keks[m]>
message you haven't seen) and can rebuild the tree
<keks[m]>
the trade-off is bandwith vs latency vs code complexity I guess
erictapen has joined #ipfs
edulix has joined #ipfs
HPH^ has joined #ipfs
erictapen has quit [Ping timeout: 264 seconds]
sz0 has quit [Quit: Connection closed for inactivity]
modrone[m] has joined #ipfs
larpanet has joined #ipfs
HPH^ has quit [Ping timeout: 264 seconds]
ilyaigpetrov has joined #ipfs
sz0 has joined #ipfs
Rusty78 has quit [Ping timeout: 265 seconds]
larpanet has quit [Ping timeout: 240 seconds]
robattila256 has quit [Ping timeout: 248 seconds]
robattila256 has joined #ipfs
engdesart has quit [Quit: yes]
engdesart has joined #ipfs
Neomex has quit [Read error: Connection reset by peer]
Neomex has joined #ipfs
talonz has quit [Remote host closed the connection]
talonz has joined #ipfs
clickjack has quit [Quit: clickjack]
clickjack has joined #ipfs
sz0 has quit [Quit: Connection closed for inactivity]
edulix has quit [Ping timeout: 248 seconds]
DYM[m] has left #ipfs ["User left"]
ralphtheninja has joined #ipfs
edulix has joined #ipfs
A124 has quit [Read error: No route to host]
A124 has joined #ipfs
nope_23 has quit [Read error: Connection reset by peer]
JayCarpenter has joined #ipfs
<JayCarpenter>
502 Bad Gateway nginx/1.10.1 is what I'm getting for IPFS.io right now.
nope_23 has joined #ipfs
zautomata has joined #ipfs
nope_23 has quit [Remote host closed the connection]
nope_23 has joined #ipfs
}ls{ has joined #ipfs
newhouse has joined #ipfs
nope_23 has quit [Remote host closed the connection]
nope_23 has joined #ipfs
nope_23 has quit [Ping timeout: 248 seconds]
IntelHD has joined #ipfs
apiarian has quit [Read error: Connection reset by peer]
apiarian_ has joined #ipfs
<IntelHD>
can someone help me. I'm looking for the go-ipfs windows pre-built binaries, but ipfs.io is down. -any mirror(s) or something?
Encrypt has joined #ipfs
apiarian_ has quit [Read error: Connection reset by peer]
apiarian has joined #ipfs
zautomata1 has joined #ipfs
nope_23 has joined #ipfs
zautomata has quit [Ping timeout: 263 seconds]
apiarian_ has joined #ipfs
apiarian has quit [Ping timeout: 260 seconds]
apiarian_ has quit [Read error: Connection reset by peer]
nope_23 has quit [Remote host closed the connection]
nope_23 has joined #ipfs
apiarian has quit [Read error: Connection reset by peer]
zautomata4 has joined #ipfs
apiarian has joined #ipfs
apiarian has quit [Read error: Connection reset by peer]
<victorbjelkholm>
sorry folks, our gateways were being a bit over-capacity. problem has been fixed now :) We really need a decentralized web!
wild1337 has joined #ipfs
<JayCarpenter>
Thanks to the team at Protocol Labs and the rest of the IPFS Community. Looking forward to 2018 and what is possible with the decentralized web.
apiarian has joined #ipfs
JayCarpenter has quit [Quit: Page closed]
fredthomsen has quit [Quit: Leaving.]
apiarian has quit [Ping timeout: 260 seconds]
zautomata4 has quit [Ping timeout: 264 seconds]
IntelHD has quit [Quit: Page closed]
zautomata2 has joined #ipfs
newhouse has quit [Ping timeout: 260 seconds]
zautomata3 has joined #ipfs
zautomata2 has quit [Ping timeout: 264 seconds]
zautomata3 has quit [Quit: WeeChat 1.7]
kaotisk has quit [Ping timeout: 252 seconds]
anewuser has joined #ipfs
kaotisk has joined #ipfs
sim590 has quit [Ping timeout: 240 seconds]
ONI_Ghost has joined #ipfs
bomb-on has quit [Quit: SO LONG, SUCKERS!]
nope_23 has quit [Remote host closed the connection]
<alain[m]>
newbie question: I'm trying to access the ipfs wikipedia snapshot through my local gateway and I get "invalid ipfs path: selected encoding not supported".
<alain[m]>
clues anyone?
ONI_Ghost has quit [Remote host closed the connection]
kaotisk has quit [Ping timeout: 248 seconds]
ONI_Ghost has joined #ipfs
kaotisk has joined #ipfs
SunflowerSociety has joined #ipfs
ONI_Ghost has quit [Ping timeout: 268 seconds]
brabo has quit [Ping timeout: 260 seconds]
nope_23 has joined #ipfs
brabo has joined #ipfs
Ronsor has joined #ipfs
<Ronsor>
hey, on dist.ipfs.io, why is there no 32-bit windows binary?
nope_23 has quit [Remote host closed the connection]
<alain[m]>
so this must be something firefox doesn't like.
newhouse has joined #ipfs
<alain[m]>
tried again, works now. go figure...
Steverman has joined #ipfs
bomb-on has joined #ipfs
larpanet has quit [Ping timeout: 272 seconds]
<Steverman>
Am I out of options for js-ipfs if I want some other network topology other than a star network?
<Steverman>
with webrtc version being a little more than that
Encrypt has quit [Quit: Quit]
<Ronsor>
hey guys
<Ronsor>
so I've created a new cryptocurrency that uses ipfs pubsub for communication
<Ronsor>
i need some help testing how well it works
<Ronsor>
outside of my home network...
Jesin has joined #ipfs
<Steverman>
Latency?
<Steverman>
Or testing outside a homogenous network
<Ronsor>
latency
<Ronsor>
I'm unsure how well it handles it
<Steverman>
What are you sending?
<Ronsor>
blocks, transactions
<Ronsor>
as needed
<Steverman>
Okay, I've been using it to send JSON for messaging. Kinda like content base pubsub within topic based pubsub
<Steverman>
Haven't seen a huge noticable delay
<Ronsor>
I'm using msgpack
<Steverman>
content based*
<Ronsor>
so far I haven't had issues locally
<Ronsor>
so maybe it's fine
<Steverman>
But I am pretty sure your network will receive duplicate data due to "flooding"
<Steverman>
That's why I am asking what you are sending
<Ronsor>
duplicate data is easily taken care of
<Ronsor>
it's just dropped
<Steverman>
Floodsub does it for you, no?
<Steverman>
Or does it just ignore it
<Ronsor>
I'm not sure if floodsub handles duplicate data actually
<Ronsor>
I just drop it because you may get the same block sent from multiple peers
onikuma has quit [Ping timeout: 272 seconds]
<Steverman>
Ah yes, that is you sending it further am I right? A single call will flood the network with the message, and floodsub will just ignore it if it has seen it before. go-ipfs or js-ipfs?
<Ronsor>
go-ipfs
<Steverman>
Don't know how go-ipfs does it
<Steverman>
But thanks for mentioning msgpack :)
HPH^ has joined #ipfs
anewuser has quit [Read error: Connection reset by peer]
tdeo has quit [Quit: WeeChat 1.9.1]
edulix has joined #ipfs
nope_23 has quit [Remote host closed the connection]
tdeo has joined #ipfs
arpu has quit [Remote host closed the connection]
<Steverman>
Now to see if that's the case for js
atrapado_ has joined #ipfs
jaboja has joined #ipfs
Neomex has quit [Remote host closed the connection]
robattila256 has quit [Ping timeout: 256 seconds]
robattila256 has joined #ipfs
tdeo has quit [Quit: WeeChat 1.9.1]
larpanet has joined #ipfs
tdeo has joined #ipfs
nope_23 has joined #ipfs
larpanet has quit [Ping timeout: 260 seconds]
nope_23 has quit [Remote host closed the connection]
jaboja has quit [Ping timeout: 260 seconds]
marigenous has quit [Ping timeout: 264 seconds]
robattila256 has quit [Ping timeout: 260 seconds]
robattila256 has joined #ipfs
talonz has quit [Quit: Leaving]
robattila256 has quit [Ping timeout: 252 seconds]
larpanet has joined #ipfs
robattila256 has joined #ipfs
jaboja has joined #ipfs
mog has quit [Ping timeout: 264 seconds]
Encrypt has joined #ipfs
shizy has joined #ipfs
rendar has quit [Quit: std::lower_bound + std::less_equal *works* with a vector without duplicates!]
larpanet has quit [Ping timeout: 260 seconds]
ilyaigpetrov has quit [Quit: Connection closed for inactivity]
espadrine has joined #ipfs
erictapen has joined #ipfs
atrapado_ has quit [Quit: Leaving]
atrapado_ has joined #ipfs
atrapado_ has quit [Max SendQ exceeded]
atrapado_ has joined #ipfs
witten has quit [Ping timeout: 272 seconds]
SunflowerSociety has quit [Ping timeout: 240 seconds]
atrapado_ has quit [Ping timeout: 252 seconds]
ygrek has joined #ipfs
tdeo has quit [Quit: WeeChat 1.9.1]
tdeo has joined #ipfs
tdeo has quit [Client Quit]
bomb-on has quit [Quit: SO LONG, SUCKERS!]
shizy has quit [Ping timeout: 256 seconds]
atrapado_ has joined #ipfs
atrapado_ has quit [Max SendQ exceeded]
atrapado_ has joined #ipfs
atrapado_ has quit [Client Quit]
h0p3 has joined #ipfs
HPH^ has quit [Ping timeout: 260 seconds]
witten has joined #ipfs
_whitelogger has joined #ipfs
Encrypt has quit [Quit: Quit]
sim590 has joined #ipfs
jaboja has quit [Quit: Leaving]
A124 has quit [Quit: '']
tdeo has joined #ipfs
astrofog has quit [Quit: Quite]
h0p3 is now known as h0p3-AFK
astrofog has joined #ipfs
larpanet has joined #ipfs
h0p3-AFK is now known as h0p3
lupi has joined #ipfs
roygbiv has joined #ipfs
larpanet has quit [Ping timeout: 248 seconds]
tdeo has quit [Quit: WeeChat 1.9.1]
astrofog has quit [Quit: Quite]
h0p3 is now known as h0p3-AFK
h0p3-AFK is now known as h0p3
roygbiv has quit [Quit: ™]
h0p3 is now known as h0p3-AFK
h0p3-AFK is now known as h0p3
Mateon1 has quit [Remote host closed the connection]
Mateon1 has joined #ipfs
h0p3 is now known as h0p3-AFK
h0p3-AFK is now known as h0p3
perohig has joined #ipfs
h0p3 is now known as h0p3-AFK
h0p3-AFK is now known as h0p3
h0p3 is now known as h0p3-AFK
shizy has joined #ipfs
h0p3-AFK is now known as h0p3
perohig has left #ipfs [#ipfs]
h0p3 is now known as h0p3-AFK
h0p3-AFK is now known as h0p3
h0p3 is now known as h0p3-AFK
<whyrusleeping>
Ronsor: hey, that's a usecase that I really like
h0p3-AFK is now known as h0p3
<whyrusleeping>
h0p3: could you please not do the auto AFK rename thing?
h0p3 is now known as h0p3-AFK
newhouse has quit [Read error: Connection reset by peer]