<computerfreak668>
i have a question about the ipfs
<computerfreak668>
is there a hole blockchain with all the data inside, or do nodes only save what they accepted to save/share, like on bittorrent ?
ygrek has quit [Ping timeout: 265 seconds]
astrocyte has joined #ipfs
<__mek__>
pong M-davidar
<ansuz>
the latter
<ansuz>
computerfreak668
<ansuz>
that's the short answer
<computerfreak668>
the latter?
<ansuz>
the long answer is that you might store even less than the files themselves, as some deduplication is liable to take place if the data contains duplicated blocks
<ansuz>
the latter => your second option, like bittorrent
<computerfreak668>
so its not a big-block everyone stores right?
reit has quit [Read error: Connection reset by peer]
<ansuz>
correct
<ansuz>
you store whatever files you add, and whatever you pin
<computerfreak668>
and my node needs to be running or my content is away?
<computerfreak668>
aah pinning means to store someone elses data ?
* jbenet
Not_ thanks for posting. we should definitely fix all that. would you be willing to describe the concrete issues in https://github.com/ipfs/support or https://github.com/ipfs/faq ? definitely the slowness -- strongly think it's NAT reachability problems
<Not_>
what concrete issues?
<jbenet>
Not_ the thread sounds like there's several issues: finding each other, things becoming slow, etc
<Not_>
oh, on notjesus.xyz/Not/400 ?
<Not_>
ill post that github link so they see it too
<jbenet>
M-davidar __mek__ the original goal was to use the discussions to reach a concrete answer (update the first post on the issue) and then use a script to dump it into markdown and show it at https://ipfs.io/docs/faq
<jbenet>
M-davidar __mek__ but open to other ideas to make it more discoverable. the thing though is that i do want to keep it as a github issues discussion because github issues is the best communications tool we have (allowing identity, hypermedia linking/embedding, subscribing, notifications, listing, tags, etc). ---- we all already have way too many comm
<jbenet>
channels and dont want to add more-- i'm drowning in notifications as it is, and i do want to be able to respond to FAQs very easily. (hence not moving to something like discourse, etc)
jhulten_ has joined #ipfs
jhulten_ has quit [Ping timeout: 260 seconds]
ricmoo has quit [Ping timeout: 246 seconds]
<computerfreak668>
how hard would it be to make a little gui controling ipfs?
<computerfreak668>
like on Qt or smth
pfraze has quit [Remote host closed the connection]
<jbenet>
computerfreak668 not hard-- there's an api already.
doublec has quit [Read error: Connection reset by peer]
doublec has joined #ipfs
Seka has quit [Ping timeout: 244 seconds]
reit has joined #ipfs
fingertoe has joined #ipfs
fingertoe has quit [Ping timeout: 246 seconds]
jry has joined #ipfs
Tv` has quit [Quit: Connection closed for inactivity]
Matoro has quit [Ping timeout: 276 seconds]
<Not_>
jbenet, for noscript users what should we do to make sure its not interupting ipfs?
fingertoe has joined #ipfs
<fingertoe>
is there a cool tool to sync ipfs nodes? When I add something to my repository on one machine, I would like my other machines to automatically pin it.
<Not_>
fingertoe, that would be useful
<jbenet>
Not_ what do you mean "not interupting ipfs" ?
<fingertoe>
Yes, When I pin something on my laptop and share it - it would be pretty handy if one of my full time machines knew about it and pinned it before I shutdown and wandered off..
<Not_>
jbenet, noscript stop localhost from running scripts
pfraze has joined #ipfs
Matoro has joined #ipfs
<jbenet>
Not_ oh-- i would add a special /etc/hosts entry and use that. noscript will likely not pick up it's localhost.
<jbenet>
but yeah that defeats noscript :)
<jbenet>
:S*
fingertoe has quit [Ping timeout: 246 seconds]
prosodyCagain is now known as prosody
<whyrusleeping>
.
<jbenet>
..
<M-mistake>
.
<strongest_cup>
Does the web server not respond to external requests on port 5001? I can only interact with the webui when I'm on the machine, it's refusing connections from other devices. Any way to modify this?
srenatus has joined #ipfs
sbruce has quit [Read error: Connection reset by peer]
ygrek has joined #ipfs
<ipfsbot>
[go-ipfs] whyrusleeping pushed 1 new commit to master: http://git.io/vBTm4
<haadcode>
jbenet: +1 on the community discussion post. especially agreed on the data silos part and looking forward to what we can come up with the POST.
chriscool has joined #ipfs
<haadcode>
.tell fazo the reason I went with a linked list is exactly what you mentioned last night: having all post in one would require to update the full "database" on every update. having it in a linked list, you can move between current time and history very easily. I also ended up caching all messages seen by a user to their local node so that one doesn't have to fetch the content over the wire everytime but can just pull it out from the local cache. it works fairl
<multivac>
haadcode: I'll pass that on when fazo is around.
doublec has quit [Read error: Connection reset by peer]
doublec has joined #ipfs
jry has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
jhulten_ has joined #ipfs
Qwertie has quit [Ping timeout: 272 seconds]
jhulten_ has quit [Ping timeout: 252 seconds]
Qwertie has joined #ipfs
amstocker has joined #ipfs
Qwertie has quit [Ping timeout: 272 seconds]
nham has quit [Ping timeout: 252 seconds]
Not_ has quit [Ping timeout: 246 seconds]
Qwertie has joined #ipfs
computerfreak668 has quit [Quit: Leaving.]
Qwertie- has joined #ipfs
Qwertie has quit [Ping timeout: 255 seconds]
chriscool has quit [Read error: No route to host]
chriscool1 has joined #ipfs
chriscool1 has quit [Client Quit]
chriscool has joined #ipfs
__mek__ has quit [Ping timeout: 272 seconds]
mildred has joined #ipfs
doublec has quit [Ping timeout: 264 seconds]
Senji has quit [Ping timeout: 250 seconds]
pfraze has quit [Remote host closed the connection]
doublec has joined #ipfs
e-lima has joined #ipfs
<daviddias>
mornin' :)
Senji has joined #ipfs
<ipfsbot>
[ipfs] mekarpeles created I92/refactor/updating-docs (+1 new commit): http://git.io/vBT4i
<ipfsbot>
[js-ipfs-api] diasdavid deleted ref/api-split at ebd915e: http://git.io/vBT0O
<daviddias>
dignifiedquire you made the js-ipfs-api so professional (which is great), I'm using it as a guide when I need to point other people how to structure stuff
<ipfsbot>
[js-ipfs-api] diasdavid deleted release at ac65107: http://git.io/vBTEN
<ipfsbot>
[ipfs] mekarpeles force-pushed I92/refactor/updating-docs from d1421f7 to 573a5cf: http://git.io/vBTuT
<multivac>
fazo: 2015-11-23 - 07:18:28 <haadcode> tell fazo the reason I went with a linked list is exactly what you mentioned last night: having all post in one would require to update the full "database" on every update. having it in a linked list, you can move between current time and history very easily. I also ended up caching all messages seen by a user to their local node so that one doesn't have to fetch the content over the wire everytime but can just pul
<jbenet>
.tell haadcode you'll want to separate the data from the index structure-- i.e. sometimes a list, sometimes trees, are better datastructs to access. you can have many!
<multivac>
jbenet: I'll pass that on when haadcode is around.
<haadcode>
jbenet: got it. that's actually how my LL is atm, separate object for the data structure and one for the content.
<multivac>
haadcode: 2015-11-23 - 10:07:38 <jbenet> tell haadcode you'll want to separate the data from the index structure-- i.e. sometimes a list, sometimes trees, are better datastructs to access. you can have many!
<jbenet>
haadcode: yeah and can have many indices, depending on access patterns.
<haadcode>
absolutely
<jbenet>
__mek__ and nicolagreco: take a look at https://github.com/ipfs/pm since you're coming to some of the hangouts.
<haadcode>
jbenet: I merely went with LL due the trackability of hashes in a distributed way. once ipfs has pub/sub and some other features, tracking the hashes becomes much easier and allow way more use cases. on that note, I reckon trees should be possible with a LL too, haven't tried it but been wanting to prototype it.
<haadcode>
*should=could
<dignifiedquire>
fazo: just trying the demo link for your boards but it’s telling me that it can’t connect :(
<fazo>
dignifiedquire: can you see the landing page though?
<dignifiedquire>
fazo: I can see the “connection to IPFS not available"
<fazo>
do you have a local go-ipfs daemon running?
<dignifiedquire>
and the landing page “social platforms are broken"
<dignifiedquire>
yes local daemon is running with the api headers as advised
<fazo>
it tries localhost:5001 by default, but you can change it if you click it on the little gear in the top bar
<__mek__>
jbenet: When you said everything in README.md... Do you mean project-directory.md as well?...
<fazo>
dignifiedquire: also you need to run the daemon allowing other origins to talk to it. Like this should work: 'API_ORIGIN="*" ipfs daemon'
<fazo>
dignifiedquire: the hard part is over after you do that though :) it should start working
<fazo>
yeah, the API doesn't talk https yet I think
<fazo>
load it over localhost:8080 (local gateway)
<fazo>
that's http, it will work
<dignifiedquire>
yes and the gateway doesn’t allow http acces, it redirects to https immediately
<fazo>
well, the plan is to eventually have it run using ipfs.js
<dignifiedquire>
fazo: aren’t all the great things waiting for that :D
<fazo>
it's being built with that in mind. go-ipfs support is just a workaround
<fazo>
I have great hope for this platform :)
<dignifiedquire>
not only you :)
<fazo>
viewing profiles and posts already works
<jbenet>
__mek__ yeah-- i think you're right that the readme should be the landing place for all the things. we can put them wherever makes sense-- i dont care much about section order.
<fazo>
dignifiedquire: keep in mind IPNS resolution is suuuuper slow and unreliable right now, so profiles will take even minutes to load and multiple refreshes
<haadcode>
__mek__: hold on, did we wanna have the hangout tonight or tomorrow (today == Monday for me)
<dignifiedquire>
fazo: okay, still waiting on it to open in my local gateway
<fazo>
dignifiedquire: yeah it's slow, but I already have a working version that is half the size
<fazo>
dignifiedquire: with webpack I managed to get it to load stuff asynchroniously
<dignifiedquire>
fazo: webpack rulezzz the world
<fazo>
dignifiedquire: lol yes, I probably lost like 20 hours waiting for browserify to recompile
<fazo>
how can webpack be 10 times faster?
anticore has joined #ipfs
<dignifiedquire>
I have not looked at the exact details of browserify under the hood but my guess is that webpack just is much more mindful in checking if work needs to done again
<dignifiedquire>
but if you don’t put in anything it will default to localhost:5001
<jbenet>
ok sweet thank you
<__mek__>
M-davidar: Yeah.. 1:30p PST is 8:30a australia time
thrillingly has quit [Ping timeout: 240 seconds]
<M-davidar>
__mek__: can you just use UTC times? converting from PST is confusing me :p
rombou has joined #ipfs
<M-davidar>
But yeah, still a bit too early, 9am is about the earliest I'm willing to agree to :)
<jbenet>
dignifiedquire i take it "//localhost:5001" doesnt work?
<dignifiedquire>
jbenet: no
<dignifiedquire>
jbenet: but you can make a PR so it works :)
<jbenet>
kk, i'll file an issue-- will want to let users not force the scheme
<jbenet>
yep
<dignifiedquire>
jbenet: any idea why I can’t get any peers with 0.3.9 on my machine this morning?
<jbenet>
dignifedquire: huh
<dignifiedquire>
tried different versions as well, but no peers for me
<dignifiedquire>
and I’m on my home network where it worked fine a couple of days ago
<__mek__>
M-davidar: Yes. The mtg is scheduled for 9:30pm UTC
<dignifiedquire>
jbenet: any idea how to debug this?
<jbenet>
dingifiedquire: im seeing the same, i think its our infra.
<srenatus>
hi there. peer ids are case-sensitive, right?
<jbenet>
dignifiedquire: i'll reboot things
<dignifiedquire>
jbenet: still not as decentralised as we would like to be :
<dignifiedquire>
:(
<dignifiedquire>
fazo: that explains why it wasn’t loading for me
<dignifiedquire>
fazo: no peers no fun
<fazo>
dignifiedquire: you don't have any peers? are you running 0.4?
<jbenet>
dignifiedquire: actually no thats not the problem i had-- i had removed my bootstrap list :]
<dignifiedquire>
fazo: nope see above infrastructure ha issues
<dignifiedquire>
jbenet: lol
<jbenet>
infra seems to be fine
<dignifiedquire>
hmm :(
<dignifiedquire>
my bootstrap list is empty
<fazo>
lol that would be it.
<dignifiedquire>
but why Oo
<jbenet>
dignifiedquire: i had the same thing.
<jbenet>
this is off.
<jbenet>
odd*
<dignifiedquire>
I didn’t touch it
<jbenet>
me neither. maybe a bug.
<fazo>
anyway doesn't the daemon cache all addresses? So that even with the bootstrap list down it should manage a few connections unless it's the first time it runs?
<fazo>
anyway just pushed huge update to ipfs-boards. It now loads module in an async way, keeping the initial required download down and having way better UX while loading stuff.
<computerfreak668>
btw, someone working on an Qt 5 App already?
fazo has quit [Ping timeout: 246 seconds]
<M-davidar>
__mek__ (IRC): I'm in the state without daylight savings, so that's 0730
fazo has joined #ipfs
<M-davidar>
computerfreak668 (IRC): I've thought about writing a qml app, and somebody else was talking about something similar in here recently, but nothing exists yet afaik
<fazo>
computerfreak668: there's a wip desktop app called station. It's built using electron though
rombou has quit [Ping timeout: 264 seconds]
<dignifiedquire>
fazo: computerfreak668 figured out the issue, running 0.4 and 0.3.9 on the same ipfs home repo might cause issues :D
<__mek__>
Where is the spec for ipld?
<__mek__>
I see the go implementation
<fazo>
dignifiedquire: cool. Well, when the files api gets merged in ipfs-api, I'll migrate my app to 0.4
<computerfreak668>
haha oke
<computerfreak668>
well i maybe try my luck soon if i get deeper into gt-creator ;)
<fazo>
dignifiedquire: I'm actually working on other parts of the app because the files api isn't available yet :P
<computerfreak668>
qt
<jbenet>
dignifiedquire: ipfs add doesnt always return an array?
<jbenet>
dignifiedquire: im guessing --wrap doesnt work on aurl
<dignifiedquire>
what does wrap do?
bedeho_ has quit [Ping timeout: 276 seconds]
<jbenet>
tru it in the fs -- ipfs add file.jpg and ipfs add -w file.jpg
<fazo>
dignifiedquire: wraps an object in a folder
<dignifiedquire>
jbenet: it should pass it along fine to go-ipfs, as the url stuff just downloads the file and then sends a regular add request
<dignifiedquire>
fazo: your profile is working, mine isn't
<jbenet>
dignifiedquire: yeah but does not preserve the filename, does it/
jhulten_ has joined #ipfs
<fazo>
dignifiedquire: woah my profile works? That's very good lol
<jbenet>
basically, "ipfs.add("site.com/foo.jpg", {wrap: true}, cb)" should add two objects, and thus preserve the filename "foo.jpg"
<fazo>
dignifiedquire: it's expected that your profile doesn't work. I need the files api to implement actually writing stuff. The only way to create a profile is to manually make the directory structure of one then adding it with ipfs add -r then publishing it to ipns
<dignifiedquire>
fazo: I see :)
<fazo>
if you want you can download mine with ipfs get then modify it :)
<fazo>
in my ipfs-boards repo there's a script. you give it your profile folder and it publishes it. It has to be named exactly "ipfs-boards-profile" though or it won't work
hoony has joined #ipfs
<dignifiedquire>
jbenet: no we are not doing any filename detection magic at the moment
jhulten_ has quit [Ping timeout: 272 seconds]
dignifiedquire_ has joined #ipfs
<dignifiedquire_>
jbenet: are you building something fancy with the js-api? :)
guest234234 has joined #ipfs
<M-davidar>
__mek__ (IRC): I'm not sure there is a spec yet :/
dignifiedquire_ has quit [Quit: dignifiedquire_]
ilyaigpetrov has quit [Quit: Connection closed for inactivity]
infinity0 has quit [Remote host closed the connection]
infinity0 has joined #ipfs
computerfreak668 has quit [Remote host closed the connection]
<dignifiedquire>
jbenet: not working cause cors :(
<dignifiedquire>
arrrr I hate cors
<dignifiedquire>
making life on the internet so much harder
<M-davidar>
jbenet (IRC): what is the current status of ipld, speaking of?
<M-davidar>
dignifiedquire (IRC): yeah, cors has been causing problems for me in matrix land too :/
<M-davidar>
The whole cross origin issue is kind of a ridiculous hack around security problems in browsers IMO
<dignifiedquire>
for sure
<dignifiedquire>
and the fact that you have modify the server makes me angry everytime, if I just put a proxy in front of your server it works, so why not just allow it by default -.-
<multivac>
[WIKIPEDIA] Cross-Origin Resource Sharing | "Cross-Origin Resource Sharing (CORS) ist ein Mechanismus, der Webbrowsern oder auch anderen Webclients Cross-Origin-Requests ermöglicht. Zugriffe dieser Art sind normalerweise durch die Same-Origin-Policy (SOP) untersagt. CORS ist ein Kompromiss zugunsten größerer Flexibilität im Internet unter Berücksichtigung…"
<multivac>
[WIKIPEDIA] Cross-origin resource sharing | "Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources (e.g. fonts) on a web page to be requested from another domain outside the domain from which the resource originated.A web page may freely embed images, stylesheets, scripts, iframes, videos and some plugin content..."
<M-davidar>
lol
<dignifiedquire>
they make it sound like a good thing..
<M-davidar>
dignifiedquire (IRC): the whole thing could be avoided if browsers didn't use cookies, etc for scripted requests
<fazo>
jbenet: cool :)
<M-davidar>
Also, since when do you need cors for images and such? :/
<M-davidar>
dignifiedquire (IRC): although, restricting access to the local network is problematic :/
<dignifiedquire>
you need the headers if you are requesting from one domain to another
<M-davidar>
Personally I think a "this webpage wants to use your location/microphone/etc" pop-up would make more sense
<M-davidar>
dignifiedquire (IRC): yeah, don't strip all the headers, just any user-specific ones
<dignifiedquire>
I’ll just build my own browser with blackjack and ignoring cors
anticore has quit [Ping timeout: 250 seconds]
<M-davidar>
dignifiedquire (IRC): of cors you will...
<dignifiedquire>
jbenet: I know, but it’s still sad because nice tools like you are building have to have a server part if you want to be able to fetch everything
<dignifiedquire>
M-davidar: :D:D:D
computerfreak668 has joined #ipfs
<ipfsbot>
[ipfs] mekarpeles force-pushed I92/refactor/updating-docs from 81d47a0 to 0d2768e: http://git.io/vBTuT
<ipfsbot>
[js-ipfs-api] Dignifiedquire created greenkeeper-karma-mocha-reporter-1.1.2 (+1 new commit): http://git.io/vBkyj
<ipfsbot>
js-ipfs-api/greenkeeper-karma-mocha-reporter-1.1.2 cd0a9ba greenkeeperio-bot: chore(package): update karma-mocha-reporter to version 1.1.2...
joshbuddy has quit [Quit: joshbuddy]
bielewelt has joined #ipfs
<ipfsbot>
[js-ipfs-api] Dignifiedquire deleted greenkeeper-karma-mocha-reporter-1.1.2 at cd0a9ba: http://git.io/vBk9Z
gunn has quit [Ping timeout: 255 seconds]
<bielewelt>
I have a TAR file containing 77,000 gzipped XML files, totalling 23 GB. Can I just push it into IPFS or should I split it or create smaller portions?
<fazo>
dignifiedquire: something changed after 2.9.0: some stuff in my app doesn't work anymore
<fazo>
seems to be related to how data is returned from ipfs cat
<fazo>
(I'm talking about js-ipfs-api)
<bielewelt>
OK, another question: Does IPFS work behind a corporate firewall?
<fazo>
bielewelt: depends on the firewall, it needs to connect to the outside on port 4001
<dignifiedquire>
fazo: what was the last working version for you?
<fazo>
dignifiedquire: I jumped from 2.9.0 to 2.9.8. I'll try to narrow it down
<dignifiedquire>
fazo: thanks
<fazo>
I've got really old code handling answers from ipfs.cat, it needed a refactor anyway :)
<multivac>
dignifiedquire: I'll pass that on when daviddias is around.
arpu has joined #ipfs
<fazo>
dignifiedquire: sorry! the bug is also in 2.9.7
<fazo>
webpack tricked me and probably didn't recompile the asset.
<fazo>
going back until I find where it's introduced
<dignifiedquire>
fazo: so there should not be any changes actually between 2.9.2 and latest
<dignifiedquire>
those were only refactorings on the code
<fazo>
dignifiedquire: yeah just tried 2.9.2 and it doesn't work. it was introduced in 2.9.1 I guess since 2.9.0 works.
jry has joined #ipfs
<dignifiedquire>
yes that makes sense as the handling was changed in there
<fazo>
dignifiedquire: nope, 2.9.1 works actually
<fazo>
the change that breaks my code was introduced in 2.9.2 I guess
<fazo>
don't worry too much, it's probably my fault
<dignifiedquire>
well the docs aren’t that great so someone has to tell you ;)
<dignifiedquire>
if you can get me the expected and the real output I might be able to tell you the issue
<fazo>
it returned a json originally
<fazo>
it now returns a buffer?
<fazo>
my code expected a json
compleatang has quit [Quit: Leaving.]
<fazo>
the content of the object requested by cat was just a valid json string, but js-ipfs-api automagically returned me the json object
<fazo>
I just went with it and now it returns a buffer
<fazo>
instead of using "answer" I need to use "JSON.parse(answer.toString())" and it works
compleatang has joined #ipfs
jhulten_ has joined #ipfs
<fazo>
fixed it :) no dramatical changes needed. However now ipfs.cat returns a Buffer instead of string/object like it did before.
jhulten_ has quit [Ping timeout: 265 seconds]
gatesvp has quit [Ping timeout: 246 seconds]
devbug_ has joined #ipfs
<dignifiedquire>
fazo: right, yes there were two changes, 1) do not parse unless the content-type is set to json 2) return a stream or a buffer depending on the headers
<dignifiedquire>
if it works for you consistent now then
<dignifiedquire>
ideally with the pr above it will return a stream in the future, or if you pass in {buffer: true} buffer that stream into a Buffer
<fazo>
it works fine now :) I guess it will go back to working like before when go-ipfs is updated to actually set the content-type and headers
devbug_ has quit [Ping timeout: 264 seconds]
anticore has quit [Ping timeout: 250 seconds]
elima_ has joined #ipfs
e-lima has quit [Ping timeout: 240 seconds]
Encrypt has joined #ipfs
<fazo>
Yay, more progress! Permalinks to posts now work
<fazo>
damn I can't wait for that sweet files api.
guest234234 has quit [Ping timeout: 250 seconds]
anticore has joined #ipfs
<dignifiedquire>
fazo: you know there is a branch of js-ipfs-api that implements the file api?
<fazo>
yeah but since I've got other things to implement I'm waiting until 0.4 is out :P
<dignifiedquire>
fazo: fair point
<fazo>
when I'll run out of stuff to do I'll get the ability to write stuff from the webapp going
<fazo>
for example I'm implementing comments now :)
<ipfsbot>
[js-ipfs-api] Dignifiedquire pushed 2 new commits to master: http://git.io/vBI3L
<ipfsbot>
js-ipfs-api/master 65d8c32 dignifiedquire: test(add): add is working consistent now
<ipfsbot>
js-ipfs-api/master 9fd8ced dignifiedquire: fix(request): Return on parsing error
<computerfreak668>
howto publish on ipfs.io/Address ?
jry has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
arpu has joined #ipfs
<fazo>
computerfreak668: you mean like ipfs.io/ipfs/hash ?
<computerfreak668>
yes
<fazo>
computerfreak668: do you have go-ipfs installed?
<ipfsbot>
[go-ipfs] lgierth deleted seccat-context at 0b50080: http://git.io/vBIDS
<computerfreak668>
yes
<fazo>
ok, start your daemon with "ipfs daemon" then just use "ipfs add file"
<computerfreak668>
done
cemerick has joined #ipfs
<fazo>
ipfs add tells you the hash. You can now see the file at ipfs.io/ipfs/hash
<fazo>
you can also see it at localhost:8080/ipfs/hash
<fazo>
when you use ipfs.io, the server at ipfs.io downloads it from your computer
<fazo>
after you add a file, anyone can see it, they will download it from someone that already has the file
anticore has quit [Ping timeout: 252 seconds]
<computerfreak668>
ty ;)
Not_ has joined #ipfs
cypher_ is now known as cypher
cypher has quit [Changing host]
cypher has joined #ipfs
jhulten_ has joined #ipfs
jhulten_ has quit [Ping timeout: 250 seconds]
<fazo>
computerfreak668: you're welcome :)
nham has joined #ipfs
<daviddias>
lgierth: I'm trying to make sure that castor knows at least one other Node at all times, IIRC pluto is running 0.4.0 too, but I don't have access to Pluto to get its peerId, is there another place I can find that? Or can you help me getting this peerId
sseagull has joined #ipfs
voxelot has joined #ipfs
voxelot has joined #ipfs
pfraze has joined #ipfs
Matoro has joined #ipfs
simonv3 has joined #ipfs
jcd has joined #ipfs
cemerick has quit [Ping timeout: 246 seconds]
<Not_>
any dates to when ipfs is updated?
<Not_>
also when will ipfs update command work?
<daviddias>
Not_: with the next release of IPFS, the update command will start working
<Not_>
sweet any eta on when that will be?
<daviddias>
early/mid December
<daviddias>
probably* :)
devbug has joined #ipfs
<achin>
i started up an ipfs0.4.0 daemon, but it didn't connect to any peers. any ideas why?
devbug has quit [Ping timeout: 250 seconds]
anticore has joined #ipfs
<dignifiedquire>
daviddias: safe flight
<daviddias>
Thank you :)
dgits has joined #ipfs
jhulten_ has joined #ipfs
<whyrusleeping>
achin: you should have at least connected to pluto
jhulten_ has quit [Ping timeout: 272 seconds]
mildred has quit [Ping timeout: 276 seconds]
amade has joined #ipfs
Matoro has quit [Ping timeout: 255 seconds]
<whyrusleeping>
hrm... somebody subscribed me to 'Marketing Information from the Cornell Lab of Ornithology'
jhulten_ has joined #ipfs
<whyrusleeping>
Also, is the sprint checkin now?
<dignifiedquire>
whyrusleeping: sounds like the detected your interests ;)
<whyrusleeping>
or an hour from now?
<dignifiedquire>
whyrusleeping: I thinks so
<dignifiedquire>
(now
<whyrusleeping>
okay, its strangely quiet
<richardlitt>
Lol
<richardlitt>
I was in the #javascript room
<richardlitt>
I was wondering why I recognized no one.
<richardlitt>
Hi everyone!
<dignifiedquire>
richardlitt: hey :)
<richardlitt>
The sync should be now
<richardlitt>
YUou all ready?
<dignifiedquire>
I’ve not been to #javascript yet but I expect it’s pretty full
Matoro has joined #ipfs
<whyrusleeping>
ready isnt a word i would use
<whyrusleeping>
but i am capable
<richardlitt>
whyrusleeping: The Cornell Lab is actually really awesome.
<dignifiedquire>
whyrusleeping: you can type
<dignifiedquire>
that’s all we need ;)
<richardlitt>
Alright. Well, David Dias isn't here, so, thanks
<whyrusleeping>
i havent had coffee yet <.<
<richardlitt>
Everyone should be able to hit him up later.
<richardlitt>
So, next up we have @whyrusleeping
amade has quit [Quit: leaving]
<jbenet>
daviddias ping Pluto.i.ipfs.io -- that ip in te bootstrap list
<richardlitt>
why, are you ready to c&p?
<whyrusleeping>
yeah, i can
<whyrusleeping>
- [ ] fs-repo-migrations (complete and working)
<whyrusleeping>
- [x] libp2p vendored
<whyrusleeping>
- [x] merge flatfs nosync
<whyrusleeping>
- [x] wire contexts into libp2p new-stream
<whyrusleeping>
- [ ] debugging close notify
<whyrusleeping>
- [x] gx work
<whyrusleeping>
spend a good amount of time benchmarking add stuff for @rht's PRs
<whyrusleeping>
and also working through figuring out why Go's close notify stuff isnt working
<whyrusleeping>
ipfs update is also pretty fun to use now. i use it for switching between 0.3.10-dev and 0.4.0 whenever i need to
<dignifiedquire>
uhh so you can update and downgrade with it?
devbug has joined #ipfs
<dignifiedquire>
nice
<whyrusleeping>
yeap!
<whyrusleeping>
it stashes your old version, and lets you revert
<dignifiedquire>
niiice
<dignifiedquire>
does it stash configs as well, in case there are changes dependent on the version?
<whyrusleeping>
its kindof become a 'version manager' program now
<lgierth>
sorry folks, i'll be with you in just a sec
<whyrusleeping>
unfortunately no
<richardlitt>
Cool.
<dignifiedquire>
cause jbenet and I got a scare this morning when the bootstrap list config was empty
<dignifiedquire>
because we had used 0.4 on the same ipfs_home
<whyrusleeping>
did you run the fs-repo-migrations?
<whyrusleeping>
or did you manually remove all the bootstrap peers?
<dignifiedquire>
neither
<dignifiedquire>
I never touched the config with anything
<jbenet>
I still think that shouldn't have modified the config -- not sure why it would.
<whyrusleeping>
yeah, it wont modify it
<whyrusleeping>
0.4.0 wont run if your repo isnt a version 3
<dignifiedquire>
ah no maybe run init with 0.4, so that was the reson proabably
<dignifiedquire>
*I ran
<whyrusleeping>
did you do 'init -f'?
<dignifiedquire>
yes
<whyrusleeping>
mmm, that would be a problem
<whyrusleeping>
anyways, enough about my stuff. next up?
<dignifiedquire>
which is fine, really it’s just a development issue and me not being careful
<richardlitt>
dignifiedquire: you're next
<dignifiedquire>
okay
<dignifiedquire>
incoming
<dignifiedquire>
## Sprint Update
<dignifiedquire>
#### WebUI
<dignifiedquire>
- [x] Add new labels
<dignifiedquire>
- [x] Clean up issues list
<dignifiedquire>
- Start preparations for stats dashboard
<dignifiedquire>
richardlitt: my thinking was to let it grow in the js-ipfs-api repo, together with common gulp task etc, and when we feel they are working well pulling them into that repo
<richardlitt>
dignifiedquire:
* lgierth
should add highlights for lars and larsg
<lgierth>
- [ ] build a prometheus exporter using :5001
<lgierth>
- [ ] my todos for 0.4.0 migration
Matoro has quit [Ping timeout: 255 seconds]
<lgierth>
that secio issue is really annoying. i'm pretty sure i'm doing exactly what seccat is doing, but then the other end only gets "short buffers"
<jbenet>
richardlitt hey-- how's the api docs coming? any progress?
<richardlitt>
jbenet: worked on it, go nowhere near as far as it looks like dignifiedquire got using apiary
<jbenet>
lgierth: interesting-- have code to look at?
<lgierth>
jbenet: yep i'll post something right after sprint
<jbenet>
sgtm
<richardlitt>
will see if I can back seat myself and help him out, will be on the http api talks later during ipfs apps
<richardlitt>
not sure if "back seat myself" is a phrase, actually; will see if I can take more of a secondary role, I think I'm holding stuff up at the moment.
<dignifiedquire>
jbenet: whyrusleeping and everyone writing go code, would be great to have you on that hangout as well, as this will involve the go-ipfs implementation as well
<jbenet>
brb writing my update
<whyrusleeping>
dignifiedquire: sounds good
<richardlitt>
dignifiedquire: yep. tried my hand at go this week, too. got some tutorials I'm going through.
<richardlitt>
@mappum @kyledrake @VictorBjelkholm: are you here?
<richardlitt>
If not, wait until jbenet's update, and then we can close out for today
<dignifiedquire>
richardlitt: :D submitted my first PR to go-ipfs as well this week, but it was hardly go code, more config things
<richardlitt>
dignifiedquire: woot!
<richardlitt>
hmm. actually, good point.
<Not_>
jbenet, what do you think of morphis?
<richardlitt>
Only Juan left today.
<Not_>
morph.is
<Not_>
its a lot like ipfs
<Not_>
with a email replacement
<Not_>
that already works and has a great ui
<Not_>
main developer vanished though
<whyrusleeping>
main developer is also a little crazy...
<whyrusleeping>
you should have read his writings before morphis actually came out
<dignifiedquire>
whyrusleeping: who is to say that jbenet isn’t a little crazy as well ;)
<dignifiedquire>
but on a serious not, crazy in what direction?
<dignifiedquire>
*note
<dignifiedquire>
Oo the white paper is an odt document????
<Not_>
whyrusleeping, what do you mean by crazy?
<jbenet>
### @jbenet
<jbenet>
- [x] QCon SF talk
<jbenet>
- [x] talked with cmeik
<jbenet>
- CR
<jbenet>
- [ ] ipfs-update -- still on it
<jbenet>
- [ ] @rht's PRs -- still on it
<jbenet>
- spec work
<jbenet>
- [x] fix repo spec for @masylum
<jbenet>
- [x] update ipld spec PR addressing CR
<jbenet>
- [x] update overviews spec PR
<jbenet>
- [x] sync with @kyledrake re permance + confs
<richardlitt>
All that's left is to say good work, jbenet
<Not_>
whats "open-access" knowledge?
<lgierth>
jbenet: what's the discussion re: POST?
<Not_>
refer to
<lgierth>
HTTP POST?
<jbenet>
richardlitt: i appreciate moving fast through these, but i think we need a bit more spacing for feedback.
<richardlitt>
jbenet: cool. I tried to wait until it seemed like the conversation died
<jbenet>
dignifiedquire: POST is a data structure for communications -- think of it like a common way to represent {posts, tweets, blogs, articles, messages, IM, ...}
<richardlitt>
normally daviddias has a lot of feedback, too, and he wasn't here today. :)
<richardlitt>
jbenet: will keep in mind for next week.
<dignifiedquire>
yeah it’s pretty quite today
<dignifiedquire>
*quiet (I really can’t type today)
<richardlitt>
yep.
<fazo>
I'm really interested in POST. Mostly because I've been trying to figure out my own way to store user content but I really want to see different ideas about it
<richardlitt>
Alright. Hangouts start in an hour.
<dignifiedquire>
alright, will be afk then for a bit, commence IPFS APPS Hangout in an hour from now, please everyone join for discussion on (HTTP) API spec
<Not_>
dignifiedquire, link?
<jbenet>
fazo let's discuss post later today, __mek__ and i are having a hangout for it
<amstocker_>
kandinski, I think that would make sense.
amade has joined #ipfs
<kandinski>
I can comment on issues, but not on lines of code. Is that normal for github? Is commenting on code only possible for commits?
<dignifiedquire>
kandinski: yes
<kandinski>
I'll open issues then
<amstocker_>
you can link to lines of code
<kandinski>
or cut and paste
border0464 has quit [Ping timeout: 250 seconds]
voxelot has quit [Ping timeout: 250 seconds]
jhulten_ has quit [Quit: WeeChat 1.3]
Matoro has quit [Ping timeout: 255 seconds]
simpbrai1 has quit [Quit: Leaving]
leer10 has quit [Ping timeout: 265 seconds]
simpbrain has joined #ipfs
* daviddias
home :)
<daviddias>
because I was unable to be on time for libp2p today, let's start with libp2p on js-ipfs and try to fit the two hangouts in one
<dignifiedquire>
daviddias: go-ipfs was switched libp2p
<dignifiedquire>
it’s about to wrap up
<dignifiedquire>
so we can do js-ipfs as scheduled
<dgits>
for go-ipfs are any os x 10.11 (el capitan) users employing the plist setup in misc/ with success? https://github.com/ipfs/go-ipfs/tree/master/misc/launchd I had to employ a different setup so was wondering if that was true for anyone else.
leer10 has joined #ipfs
<kandinski>
amstocker_: this philosophical thing I have about canonical values for stuff.
<ipfsbot>
[go-ipfs] nham opened pull request #2000: Add newline to end of `ipfs object put` text output. (master...object_put_newline) http://git.io/vBtDU
<kandinski>
remember my thing with multihash values being bytestrings, which you can either encode into different encodings, or decode into a tuple with (code, name, length, digest).
filwisher has quit [Ping timeout: 276 seconds]
<jbenet>
whyrusleeping: maybe assign items in https://public.etherpad-mozilla.org/p/nov-23-go-ipfs if relevant? i noted a couple for me-- the CR. once you post it on the sprint, can you comment on relevant issues related to this stuff? (there's many out there -- and interested people may help implement)
<kandinski>
I think multiaddr should be structured similarly. Maybe have a multiaddr/multiaddring split, where multiaddr is just a series of functions that operate on multiaddr bytestring values, and multiaddressing (or a better name) has a python object with many initialisers (from_bytestring(), from_ b58()) and digesters(as_bytestring(), as_b58())
<kandinski>
amstocker_: I'm somewhat of an API nazi. But I also think that this kind of uniformity would do users of py-ipfs well.
<kandinski>
most programmers would use the Multiaddressing object, and those who don't can use the multiaddr module for underlying tinkering.
<jbenet>
Oh sorry i think some people joining the go-ipfs hangout were looking for libp2p -- if you were, join us now, daviddias posted links above o/
<jbenet>
anybody from py-ipfs want to join us?
Not_Jesus has quit [Ping timeout: 260 seconds]
Senji has joined #ipfs
<kandinski>
(amstocker: and sorry for doing the IRC drive-by I said I wouldn't)
<kandinski>
(I'll just write it up in the issue)
<amstocker_>
jbenet, unfortunately I have class D:
<amstocker_>
i will be starting to join after the semester is over
<amstocker_>
kandinski, no worries, I'm just not able to browse IRC right now
<kandinski>
nw, issue will have everything
<kandinski>
jbenet, what is procedure for contributing? Do I need to send a CLA?
<amstocker_>
kandinski, I also agree that it should be bytestrings
<kandinski>
or it's all ok, since it's MIT-licensed anyway?
<fazo>
Not_: uhm it doesn't look like a static website
<fazo>
Not_: yeah you can load all the files you want through ipfs except index.html. just change the url. You can do it manually or try with the scraper :)
<fazo>
Not_: the problem is that if the website needs to make http requests to the backend they wouldn't work if the website is loaded from ipfs.io
<ogzy>
which issue is the one that is being discussed about dynamic content and serbig wordpress like sites with ipfs
<fazo>
Not_: sorry, but I don't know why it does that. I haven't wrote the script. It's probably incompatibility between the BSD version of wget and the GNU version or something like that.
<jbenet>
Not_ needs to be enabled. if you run your own gateway, you can do it today. we should enable it on ipfs.io sometime in the next week or two
<jbenet>
idk follow that issue o/ (105)
<Not_>
how do i run my own gateway?
<ion>
run “ipfs daemon”, it will run a daemon on port 8080 by default.
<ion>
uh. run a gateway
jry has joined #ipfs
rendar has quit [Ping timeout: 240 seconds]
wiedi has quit [Quit: ^Z]
<jbenet>
thansk everyone
rendar has joined #ipfs
roguism1 has joined #ipfs
computerfreak668 has joined #ipfs
harlan_ has joined #ipfs
<__mek__>
jbenet: a few of us had a mtg sch'd for "POST" @ 1:30p PST but it looks like davidar and haadcode won't be able to make it at that time. It looks like it would be you, me, and enrico. Should we reschedule or go for it?
<jbenet>
__mek__ would be nice to have davidar. would you be able to do 14:30 PT? -- we have a "data structures" hangout allocated we can use. though not sure if davidar will be around at 14:30
<jbenet>
harlan_ no no, i just havent been pushing those-- i'll join!
<jbenet>
whyrusleeping if you have a moment,-- lgierth will want to talk about heisentests in go-ipfs
<jbenet>
o/
<jbenet>
daviddias: i cant right now, what's up?
<daviddias>
I thought you wanted to talk (re: testing stuff)
<daviddias>
we were talking about API stuff on the same hangout
roguism1 has quit [Ping timeout: 252 seconds]
kord has joined #ipfs
roguism has joined #ipfs
<jbenet>
daviddias: oh we've been talking about testing in the ci hangout
<daviddias>
aaaah the channels
<ion>
dignifiedquire, daviddias etc: Re: RPC vs. REST, REST is great if you want to really embrace everything about HTTP. On the other hand, if the goal is to have an RPC API that can work over any transport out of whom HTTP is just one, you probably don’t even want to have request paths. Just POST to an endpoint with the entire request as a payload in the same format you would use over every other transport.
devbug has quit [Ping timeout: 250 seconds]
<daviddias>
voxelot: just read now, it seems I misunderstood and there is already a proposal to unite forces on the thread, I think that sounds great and probably all we need is to sync up, start a project all together and merge all the ideas
devbug has joined #ipfs
wiedi has joined #ipfs
<dignifiedquire>
ion: yes exactly my thoughts
<voxelot>
daviddias: thanks for taking a look! excited to work on that so let me know if you spearhead a project and open up a repo that we can collab on. Would be more than willing to help organize that too if you
Nokius has left #ipfs ["Leaving"]
<voxelot>
are too busy. I think fazo wanted to talk about it in about an hour if you're around
<daviddias>
I'm learning that Wordpress has made the move to be a complete front end API built with REACT and move Wordpress core to a Node.js API http://ma.tt/2015/11/dance-to-calypso/
<dignifiedquire>
daviddias: wtf???
<dignifiedquire>
that’s amazing
* M-davidar
checks calendar, not april 1st
<daviddias>
It would be easier than ever to start pointing "calypso", the codename for Wordpress frontend, at an API that is just a proxy to IPFS :D :D
<daviddias>
dignifiedquire: I had a similar reaction, controlling myself on the camera :D
<dignifiedquire>
daviddias: :D:D
guest234234 has joined #ipfs
qgnox has quit [Quit: WeeChat 1.3]
<richardlitt>
go-ipfs has 1337 stars. That is all.
<daviddias>
ahah, richardlitt good catch! :)
NeoTeo has quit [Quit: ZZZzzz…]
jedahan has quit [Quit: My Mac has gone to sleep. ZZZzzz…]