#dat

TheLink: no keep it closed. you are our test case

mafintosh: I will :)

ogd: mafintosh jhand pfrazee The past few weeks talking to users and stuff I've been demoing and listening to people say they are really excited about versions/history/log/commits .. I say 'dat has that' but really we don't yet. It'd be nice to make some headroom on this!

'reverting to a point in history' (checkout) also

TheLink: when you get a chance, could you try using dat 11.3.1 and hyperdrive-archive-swarm 3.1.0?

jhand: hoe do I do that?

*how

TheLink: is your dat installed with npm or do you have running with npm link?

installed via npm

I'm still on 11.1.2 which works but I can install whatever you need me to

TheLink: ya try latest

install via npm?

TheLink: then delete node_modules/hyperdrive-archive-swarm

TheLink: ya

ok

TheLink: then npm install hyperdrive-archive-swarm@3.1.0

ok, will do

jhand: stupid question – where do I delete the node_modules/hyperdrive-archive-swarm?

TheLink: from /usr/local/lib/node_modules/dat/node_modules probably

ok

jhand: still doesn't connect; file count seems correct now though (1 file); displayed size still grows endlessly

ok, nm re file count

just went up, too :)

TheLink: ok I'm gonna make a fork for you we can start testing with

ok :)

TheLink: try this: npm install -g joehand/dat#TheLinkNet

thats just 11.2.1, just making sure it works =)

joehand/dat - 11.1.2 - passed - https://travis-ci.org/joehand/dat/builds/165303865

ok

jhand: it works but it took a while till they connected

TheLink: ok cool, thanks! let me hack on this fork a bit

ok

just wanted to mention this paper again https://people.csail.mit.edu/sperezde/pre-print... the section 4 has some good distilled 'purposes' of a vcs

TheLink: okay, wanna try to install that fork again?

TheLink: oh wait, gotta push

lol

:)

TheLink: good now!

ok

\o/

jhand: it works!!

it's quite slow but it works

there seems to be some visual issue though

dat seed on my vps says it's uploading but dat receiver locally doesn't show progress anymore

only that it's connected to 1 peer

but overall that's great progress

!!

thank you jhand

TheLink: ya was a bit hacky on the peer stuff. but it worked so thats cool

TheLink: which part was slow? the connection or the trasfer?

both

TheLink: so, just to make sure, all the files got downloaded? =)

takes a while till the connection is established

ok

and transfer is slow considering I'm loading from my vps

heh, now I got the emfile error on my vps again

TheLink: thanks so much for being patient and helping us find this! We

'll try to figure out how to solve this in the CLI and let you know when its released

jhand: np, I'm really fine with testing :)

should the mtime on files' hypercores be the mtime of the file read from the OS, or the time of the write to the hyperdrive?

pfrazee: same i guess

mafintosh: if you create the archive after the files, then time-of-write to the archive would be later than the mtime reported by an os-stat on a file

[dat] joehand created fix/swarms (+3 new commits): https://git.io/vPnhQ

dat/fix/swarms 05591b1 Joe Hand: use dat-js fork and remove discovery modules

dat/fix/swarms 2b8be2e Joe Hand: use conneciton length

dat/fix/swarms 776089d Joe Hand: remove webrtc

datproject/dat - remove webrtc - passed - https://travis-ci.org/datproject/dat/builds/165...

[dat] joehand pushed 1 new commit to fix/swarms: https://git.io/vPcec

dat/fix/swarms 40b1d77 Joe Hand: use new dat-js branch

TheLink: whenever you get a chance, can you try npm install -g joehand/dat#fix/swarms

want to make sure its not a regression (added back in the options around swarms/discovery)

TheLink: oops, its on datproject: npm install -g datproject/dat#fix/swarms