#dat

jhand: notes from discussion on 'dat push'

jmazz: stream._readableState.objectMode

andrewosh: around? :D

dat.haus/ seems down? i thought it was working yesterday

im thinking it might be a cool idea to have a wrapper for a hyperdrive archive that mimics the hyperdrive archive api but instead does calls to dat.haus

juliangruber: jhand right now dat.haus returns the file list as an array instead of a json stream, what do you guys think about making it a stream?

nevermind i had an old version of hyperdrive-http

is there any reason why dat.haus is depending on 2.0.0

instead of 3.x?

juliangruber: can you add me to dat.haus so i can submit a pr for that?

karissa: done

no particular reason for that :)

karissa: just commit that to master and get mafintosh to redeploy

k

done

what time was the beer thing again tonight?

7pm yoshuawuyts

ohhh, it's almost 7 :D

come over whenevs

we'll be there, and if we move (unlikely) we'll tweet location

have fun!

TheLink: nice

ogd: I still hope they get webrtc into safari natively :/

pfrazee: saw you just made a hyperdrive-zip-stream repo, if a tar is okay karissa has a repo: https://github.com/karissa/archive-dat/

jhand: thanks for the heads up. This guy is already written, I'm just factoring it out

pfrazee: ah cool

pfrazee: we have a repo to go the other way too if you need =) tar->dat

nice!

https://www.npmjs.com/package/hyperdrive-to-zip... published

sweet! now we can do files -> tar -> dat -> tar -> dat -> zip -> files or something lol

lol

jhand: feel like pairing on the cli? im in forest grove but i can do screenhero

jhand: i just feel like actually coding lol

ogd: ya sure! give me like 10 min. did you want to work on some of the stuff we talked abou tyesterday

jhand: ya exactly

ogd: ok, im on screenhero

haha

am i shadowbanned? lol

ogd: ya we aren't contacts

oh ya weird

i see offline people

mafintosh: hey me and jhand are working on a thing using discovery channel and were trying to figure out why we werent finding peers with {dht: false} (only using DNS), and after debugging some i noticed here https://github.com/mafintosh/dns-discovery/blob... you never do on('response') which is where the DNS queries come back, on('query')

never gets called in our use case but on('response') does when using the DNS servers for peer discovery

mafintosh: our thing we're writing is here https://github.com/maxogden/dat-archiver if you wanna reproduce locally run the tests

ogd: hmm ok. i'm out right now but will take a look when i get to my laptop

(serapath) hi, it's a bit off topic, but i'm stuck with a little `yo-yo` snippet and wonder how to best deal with it.

(serapath) blue button is self-updating until i update the red button

(serapath) http://requirebin.com/?gist=642e42ee09a1acc2533...

(serapath) how should i use yo-yo to avoid this problem?

hi @serapath, should the red button only update itself?

When you create the second button, on line 9, ${Component2(counter)} you are passing the same counter to both buttons

(serapath) no, resetting the blue one

(serapath) so the red one should update both simultaneously - that's fine. i'm worring just, that the blue button doesnt update anymore after clicking the red one once

so the blue should update itself as well?

(serapath) the blue one does update itself when clicked

(serapath) but after clicking the red one once, the blue one doesnt update anymore

(serapath) when clicked

ah! I was just clicking the red first =)

Im a yo-yo novice so I am not quite sure. It looks like your counter and blue event still work.

There is a #choo channel in IRC. They may know a bit more about yo-yo

(serapath) really? but the blue button, after clicking the red one, doesnt increase itself anymore, right?

ya thats right. I added a console.log('blue', counter) to the component2 update function and that prints out fine

Do child components update their own templates?