<jbenet>
pokeball99: it is legally, operationally, and systematically a fraught endeavor to FORCE readers to store content they do not wish to. This is solved at a different layer, as that answer describes
pfraze_ has quit [Remote host closed the connection]
Tera2342 has joined #ipfs
<achin>
(note that the google blog was written many months ago)
<deltab>
jbenet: which part of the post is that in response to? the last paragraph?
jedahan has joined #ipfs
<deltab>
"data added to IPFS is only stored locally until another interested party requests it from you. IPFS itself (the protocol) provides no guarantees of redundancy or remote storage."
<achin>
that's true!
<achin>
but if you visit an [ipfs] website that you want to make permanent, you can do this (just by pinning it)
pfraze has joined #ipfs
patcon has quit [Ping timeout: 250 seconds]
Whispery has joined #ipfs
TheWhisper has quit [Ping timeout: 256 seconds]
cleichner has quit [Read error: Connection reset by peer]
disgusting_wall has quit [Read error: Connection reset by peer]
cleichner has joined #ipfs
disgusting_wall has joined #ipfs
leer10 has joined #ipfs
survi has joined #ipfs
gnathonic has quit [Remote host closed the connection]
ulrichard has joined #ipfs
survi has quit [Quit: Leaving]
survi has joined #ipfs
Sriram has joined #ipfs
Sriram has quit [Remote host closed the connection]
tilgovi has joined #ipfs
sbruce_ has quit [Read error: Connection reset by peer]
sbruce_ has joined #ipfs
akkad has quit [Ping timeout: 240 seconds]
survi has quit [Quit: Leaving]
survi has joined #ipfs
tilgovi has quit [Ping timeout: 272 seconds]
mildred has joined #ipfs
akkad has joined #ipfs
Soohong has joined #ipfs
tilgovi has joined #ipfs
tinybike has joined #ipfs
disgusting_wall has quit [Quit: Connection closed for inactivity]
pfraze has quit [Remote host closed the connection]
tilgovi has quit [Ping timeout: 240 seconds]
<jbenet>
achin deltab really just the last line. It's not bogus just not fully released yet.
<jbenet>
(And needs to convolve with orgs' impetus to back things up)
ygrek_ has joined #ipfs
<Stskeeps>
jbenet: i'm not sure if you answered this in your devcon talk; but would ipfs do anything for transactions per second capability of ethereum, if their blockchain was stored in ipfs?
devbug has quit [Ping timeout: 240 seconds]
yaraju has joined #ipfs
slothbag has joined #ipfs
NeoTeo has joined #ipfs
computerfreak has quit [Remote host closed the connection]
<patagonicus>
Hi there. Just wondering: Is there a list of publically available sites on IPFS/stuff that you can get over IPFS? Things like Linux ISOs, docker containers, etc.
dignifiedquire has quit [Ping timeout: 250 seconds]
torpor has joined #ipfs
torpor has quit [Client Quit]
dignifiedquire has joined #ipfs
akkad has quit [Ping timeout: 250 seconds]
<dignifiedquire>
jbenet: can you give me write access for distributions, so I can keep my branches on there please
<jbenet>
dignifiedquire: done, you have admin
<dignifiedquire>
jbenet: ta
<jbenet>
(wish github had a "request access feature
<dignifiedquire>
yeah that’d be nice
<ulrichard>
What could be the reason that I can get some data through ipfs from one machine to others, but it always blocks for other data.
<jbenet>
ulrichard: nat traversal. ok we need to bump this up in prio-- it's biting users.
<jbenet>
(or biting a lot more now)
<dignifiedquire>
jbenet: would that solve the issues I’m seeing when using ipfs through a vpn as well?
<ulrichard>
The machine serving the file has the port forwarded, only the receiving machines are behind NAT. And the same direction works for other files.
<jbenet>
dignifiedquire: yeah likely. though getting perfect NAT traversal is hard, we can (a) improve it a lot, and (b) add relay. i'd be comfortable enabling relay as an opt in. most of it is already in the code
<jbenet>
(relay is "line switching" on top of ipfs connections. we'll have "packet switching" eventually)
<jbenet>
ulrichard: oh that's odd then
<ansuz>
if you're having NAT problems I feel bad for you son
<jbenet>
ulrichard: probably not nat then. ok question: is the file big and did you try to get it immediately after adding?
<ansuz>
I got 99 problems but cjdns fixed NAT
<jbenet>
ansuz: yes which is why we're headed that way too :)
<ansuz>
:D
<ansuz>
<3
<ansuz>
I've been pushing ipfs pretty hard at xwiki
<ansuz>
they're warming up to it
<ansuz>
the rest of the research team is *mostly* running cjdns
akkad has joined #ipfs
<jbenet>
ansuz: at some point will be good to convene a meeting with cjd anduz lgierth arceliar and whoever else relevant, about cjdns and libp2p
<ulrichard>
jbenet: No it's only a few log lines. I started trying fairly soon after adding. In the week since adding the file, I tried to get it many times. Images of a few MB worked, but I have the same problem with a 250MB movie file.
<jbenet>
(pls dont add noise to that issue though, it's got several CRDT researchers discussing interesting things)
<jbenet>
ulrichard: odd, im not sure what's up. maybe open an issue, or search around, others may have similar problem. (could be dht muckiness)
<dignifiedquire>
jbenet: are you joining us later for Jeromys Coffee Talk? :)
dignifiedquire_ has quit [Client Quit]
devbug has joined #ipfs
<jbenet>
maybe -- what's it on?
<dignifiedquire>
jbenet: not decided a 100%, david suggested files api yesterday
<jbenet>
ah that would be nice to cover. mfs + patch + maybe mounting it in the future :)
<dignifiedquire>
by the way, I’m curious what you think about rust as a language (been digging into it a bit more the last days and really enjoying it so far)
robcat has joined #ipfs
devbug has quit [Ping timeout: 240 seconds]
<fazo>
dignifiedquire: I gave it a try on a small project and it looked pretty nice. The compiler is very punishing about pointers, because it refuses to compile anything that may not work. I think it needs structure inheritance though
<dignifiedquire>
fazo: well that’s really the point isn’t it (full safety around working with pointers) which is why I like it so much
<dignifiedquire>
not sure what you mean with structure inhertiance?
<fazo>
yeah that makes it nice :)
<fazo>
the problem with struct inheritance is that I wanted to use it for a project when I had countless variations of the same structure, all with similar behavior but different implementations underneath
<fazo>
there is no comfortable way to do this in rust without duplicate code, at least as far as I know
<fazo>
if you have two different structure and they have a few methods in common (implemented using the same code) you have to copy paste the code...
<fazo>
there are solutions to this, like defining Object once then using ExtendedObject(s) that instead of being an extension of Object they contain an Object, but it's an ugly solution imho
Tera2342 has quit [Ping timeout: 250 seconds]
<dignifiedquire>
what about using traits with default implementations?
<dignifiedquire>
also there is inheritance for structs in the latest release
akkad has quit [Ping timeout: 250 seconds]
reit has joined #ipfs
<jbenet>
dignifiedquire: i think rust is one of the most important languages :) im so glad it exists. i may have started with rust-ipfs if rust had been much more mature, and go wasn't so wonderfully nice.
<dignifiedquire>
:)
<jbenet>
dignifiedquire: go is a fantastic prototyping language. it's so, so fast. hard to beat. though its type system is problematic. tbh, i will likely learn haskell deeply before rust.
<jbenet>
i've been putting off that adventure for far too long.
<dignifiedquire>
doesn’t everybody ;)
<jbenet>
mainly cause i know it will take >1yr and restructure my brain
<dignifiedquire>
I’ve started to learn haskell three times now, but until I do a serious project with it it will never properly stay :(
<jbenet>
dignifiedquire: so we need an asciinema for go-ipfs right?
<dignifiedquire>
yep
anticore has quit [Quit: bye]
pfraze has joined #ipfs
<jbenet>
dignifiedquire: do you ever see the progress bar on add?
<jbenet>
i dont see it anymore
<jbenet>
:/
<dignifiedquire>
jbenet: where? on the cli?
<jbenet>
eyah
<dignifiedquire>
jbenet: can’t remember I ever saw one, but then again haven’t added any large files really
zz_r04r is now known as r04r
rombou1 has quit [Read error: Connection reset by peer]
<fazo>
hey haadcode, what's up with anonymous-networks? :P
<haadcode>
jbenet: thanks, will take a look
<haadcode>
fazo: how so?
<fazo>
haadcode: just asking if you want to talk about what you've been working on
<fazo>
sorry, my figures of speech are not very optimized in english yet :(
<haadcode>
fazo: sure. been kinda slow the past couple of weeks, been busy. re-wrote the server component so it's a little more stable & faster now. adding/fixing stuff in the UI slowly, too.
<haadcode>
fazogive it a go and see for yourself what's new since you last time checked :)
<haadcode>
fazo: if you have any specific questions or problems with it, let me know!
<fazo>
yeah I'm going to try it out now :)
<jbenet>
works very well for me
<jbenet>
pushing me to figure out pub/sub too
<jbenet>
:)
<haadcode>
:)
<haadcode>
good ;)
<dignifiedquire>
haadcode: pulling latest code myself now :)
<dignifiedquire>
really excited for it to replace irc
<pokeball99>
Anything else like sloth's air locker that doesn't have Ethereum as a depentecy?
<fazo>
me too
<haadcode>
dignifiedquire: I just added something for the "multiple" channels thing you mentioned some time ago. still no view to multiple channels at one time but at least a small improvement to previous, hopefully.
<dignifiedquire>
haadcode: cool, something I can try out?
<jbenet>
haadcode: best thing about writing software libs is having users building things _you_ want to use, pushing you to make your lib better.
<dignifiedquire>
haadcode: I like orbit as a name :)
<haadcode>
dignifiedquire: yeah, just open a few channels and see the top-right corner :) let me know what you think.
<fazo>
IPFS Boards also needs a new name
<fazo>
haven't been able to come up with the right name yet
<dignifiedquire>
haadcode: working nicely
<dignifiedquire>
haadcode: what’s the state of bots?
<dignifiedquire>
haadcode: though if there are more than a couple a dropdown might be better
<dignifiedquire>
haadcode: or just limit it to the x recently used
<haadcode>
dignifiedquire: no work on those lately. did fix them so there's now one running that caches #ipfs on it. you can give it a try but no guarantees they'll work flawlessly.
<haadcode>
jbenet: I think that works both ways, ideally
<dignifiedquire>
haadcode: lool trying to send a message to you still results in a smilie :D
<haadcode>
haha, right yeah, haven't fixed that either :)
Encrypt has joined #ipfs
<fazo>
I'm trying it out but after I put my username in it's stuck at the loading animation
<haadcode>
fazo: pm -->
infinity0 has quit [Ping timeout: 256 seconds]
yaoe has quit [Ping timeout: 260 seconds]
yaoe has joined #ipfs
infinity0 has joined #ipfs
infinity0 has quit [Remote host closed the connection]
infinity0 has joined #ipfs
pfraze has quit [Remote host closed the connection]
ulrichard has quit [Read error: Connection reset by peer]
step21 is now known as step21_
infinity0 has quit [Remote host closed the connection]
infinity0 has joined #ipfs
chriscool has joined #ipfs
<daviddias>
dignifiedquire: I'm around :)
<dignifiedquire>
daviddias: welcome back
<dignifiedquire>
daviddias: did you see my pm about sleeping
<daviddias>
yes yes :)
leer10 has quit [Remote host closed the connection]
rombou has quit [Ping timeout: 256 seconds]
rombou1 has joined #ipfs
cemerick has quit [Ping timeout: 250 seconds]
infinity0 has quit [Remote host closed the connection]
infinity0 has joined #ipfs
rombou1 has quit [Ping timeout: 240 seconds]
<bret>
daviddias: didn't catch you after your talk, but that was awesome!
<daviddias>
thank you bret ! :D :D
<daviddias>
Hey, I'm still in Portland, will probably hack all day out of this coffee shop (Commissary), you are welcome to join me :)
<bret>
Your leaving Pdx Saturday?
<bret>
I have to work all day
<bret>
Or Sunday?
voxelot has joined #ipfs
voxelot has quit [Changing host]
voxelot has joined #ipfs
pfraze has joined #ipfs
<daviddias>
Saturday 8am (why do I keep scheduling flights so early :( )
<daviddias>
Leave Portland Saturday to arrive Sunday at Lisbon, it is like time travel done wrong
computerfreak has joined #ipfs
mildred has quit [Ping timeout: 240 seconds]
border0464 has left #ipfs ["sinked "]
devbug has joined #ipfs
Peer3Peer has joined #ipfs
gamemanj has joined #ipfs
<bret>
Oof. I don't think I can make it out today
<bret>
Oh man also just saw ipscend. Coooool
devbug has quit [Read error: Connection reset by peer]
rombou has joined #ipfs
<daviddias>
ok, no problem, it was great seeing you during the conf :)
Matoro has joined #ipfs
patcon has joined #ipfs
cemerick has joined #ipfs
jedahan has joined #ipfs
devbug has joined #ipfs
Not_ has joined #ipfs
<wao>
:D
<wao>
timetravelliing
<wao>
~O~
Not_ is now known as Guest27205
Guest27205 has quit [Client Quit]
Not_Jesus has joined #ipfs
Not_Jesus has quit [Remote host closed the connection]
<ipfsbot>
[js-ipfs-api] Dignifiedquire created greenkeeper-webpack-stream-3.0.1 (+1 new commit): http://git.io/v0qkI
<ipfsbot>
js-ipfs-api/greenkeeper-webpack-stream-3.0.1 79cf043 greenkeeperio-bot: chore(package): update webpack-stream to version 3.0.1...
Not_Jesus has joined #ipfs
Not_Jesus has quit [Client Quit]
Not_Jesus has joined #ipfs
robcat has quit [Quit: robcat]
devbug_ has joined #ipfs
jbrooker has joined #ipfs
devbug has quit [Ping timeout: 240 seconds]
Not_Jesus has quit [Client Quit]
Not_Jesus has joined #ipfs
<ipfsbot>
[js-ipfs-api] Dignifiedquire closed pull request #164: Update webpack-stream to version 3.0.1
<ipfsbot>
[js-ipfs-api] Dignifiedquire closed pull request #163: Update webpack-stream to version 3.0.0
Matoro has quit [Ping timeout: 256 seconds]
Matoro has joined #ipfs
Senji has quit [Read error: Connection reset by peer]
Senji has joined #ipfs
Not_Jesus has quit [Remote host closed the connection]
devbug_ has quit [Ping timeout: 272 seconds]
devbug has joined #ipfs
<daviddias>
whyrusleeping: any special thoughts on our lock file strategy?
<whyrusleeping>
for the repo lock?
Soft has joined #ipfs
<daviddias>
yep
<daviddias>
we are using a `file`, not a `dir`, right?
<whyrusleeping>
yeah
<daviddias>
nice
<whyrusleeping>
i wanted to rewrite the file locking lib we use
<whyrusleeping>
the one we have has a couple small bugs
<fazo>
Guest20592: you can try this command: chmod +x /usr/local/bin/ipfs
<fazo>
Guest20592: on what distro are you?
<fazo>
btw after the chmod command, try again with ipfs init
<Guest20592>
sitll
<Guest20592>
im on ubuntu gnome
<Guest20592>
i tried chmod and still get command not found
<fazo>
try opening a new terminal
<fazo>
if that doesn't work, I'm not sure
<fazo>
btw try using it like this: /usr/local/bin/ipfs init
<fazo>
I have to go, brb
<Guest20592>
still not working
<Guest20592>
why isnt there a repo for ipfs jbenet
Guest20592 has quit [Remote host closed the connection]
Soohong has quit [Read error: Connection reset by peer]
interangular has joined #ipfs
computerfreak has quit [Remote host closed the connection]
devbug has quit [Ping timeout: 240 seconds]
<ianopolous>
hi guys, Have there been any bugs fixed since 3.8 with holding too many open file descriptors? (whyrusleeping?)
<fazo>
ianopolous: I think 0.4 solves it (not released yet but you can run it from source)
<fazo>
but I'm not sure. Maybe some other fix made it in 0.3.9 or 0.3.10
<ianopolous>
thanks fazo
Encrypt has quit [Quit: Quitte]
jhulten has joined #ipfs
chriscool has quit [Quit: Leaving.]
chriscool has joined #ipfs
chriscool has quit [Client Quit]
chriscool has joined #ipfs
robcat has joined #ipfs
chriscool has quit [Client Quit]
chriscool has joined #ipfs
Matoro has quit [Ping timeout: 256 seconds]
chriscool1 has joined #ipfs
chriscool has quit [Ping timeout: 250 seconds]
<ianopolous>
should ipfs currently compile with go 1.5.2?
<whyrusleeping>
ianopolous: yeah, there are fixes for that in 0.3.10
<whyrusleeping>
and ipfs requires 1.5.2
<whyrusleeping>
(the fixes for file descriptors were probably actually in 0.3.9)
<ianopolous>
at the moment I'm trying to compile the latest ipfs with go 1.5.2 and it complains about C source files not allowed when not using cgo or swig.
<ion>
(Not just a joke, the dump might reveal useful information.)
jhulten has quit [Ping timeout: 240 seconds]
jhulten has joined #ipfs
tilgovi has quit [Ping timeout: 272 seconds]
tilgovi has joined #ipfs
devbug has joined #ipfs
domanic_ has joined #ipfs
ygrek_ has joined #ipfs
patcon has joined #ipfs
NeoTeo has quit [Quit: ZZZzzz…]
geoze has joined #ipfs
user24 has joined #ipfs
<user24>
I'm sorry for repeating this question, but I simply couldn't find information on this anywhere: Will libp2p functionality (opening/closing protocol channels/streams to other peers, sending and receiving data) be available over the IPFS node APIs?
geoze has quit [Ping timeout: 252 seconds]
NeoTeo has joined #ipfs
domanic_ has quit [Ping timeout: 250 seconds]
evanmccarter has quit [Quit: Connection closed for inactivity]
rombou has joined #ipfs
<fazo>
user24: I don't think so, but if you will be using the js implementation ipfs then yes, because to talk to that you won't need to use a socket or network protocol like http
<fazo>
just code
atrapado has quit [Quit: Leaving]
<fazo>
or you can write something in go to better integrate with go-ipfs and go-libp2p, but I don't think those are built with that in mind
<fazo>
go-ipfs is mostly used via the http api
tinybike has quit [Ping timeout: 256 seconds]
<user24>
Yep. For my use case, I need to utilize libp2p directly, as I want to build on top of it. The "make your own IPFS service" example requires a new node to be run for every service.
<user24>
This approach is also restricted to the go programming language.
chriscool has joined #ipfs
chriscool1 has quit [Ping timeout: 272 seconds]
<user24>
I'm also not sure if the devs will separate the APIs, as it would be nice to run a libp2p node as standalone (without IPFS).
rombou has quit [Ping timeout: 250 seconds]
user24 has left #ipfs [#ipfs]
user24 has joined #ipfs
rombou has joined #ipfs
rombou has left #ipfs [#ipfs]
<pokeball99>
user24: the ipfs api should be just the core specs of ipfs, so I would think so
<user24>
It would make a lot of sense ;)
<user24>
However, for performance reasons, it may make some sense to distribute them as one optimised binary (as it is now).
<pokeball99>
Fair enough
<fazo>
user24: they will surely be separated. The current go-ipfs doesn't use libp2p as far as I understand, but ipfs.js even though is not done uses libp2p, and libp2p is his own separate project
<fazo>
the point of making libp2p is so that it can be ripped out of ipfs
<pokeball99>
Again this protocol is anything but final,so anything could happen
<fazo>
not the only reason but looks like a big one
<jbenet>
user24 there's an open PR in go-ipfs to add services via io
<user24>
io as in iolang or I/O?
<jbenet>
user24 there is no name collision-- that doc is a result from my taking to vitalik and Gavin about our libp2p plans and inviting them to do the same. It's the same libp2p :)
<user24>
I just noticed that the gitter connection is only one way
<user24>
jbenet: AAAWWWW YES
<jbenet>
There will be more synthesis down the road
<user24>
nice
<jbenet>
But note that both groups will optimize for our use cases so we may end up reusing less than would be idea
<jbenet>
(Also that was nov 2014 I think :) -- devcon0)
<user24>
understandable, but still awesome. it seems I was a bit too pessimistic regarding cooperation
Encrypt has quit [Quit: Sleeping time!]
Matoro has quit [Ping timeout: 240 seconds]
evanmccarter has joined #ipfs
computerfreak has quit [Remote host closed the connection]