by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Apr 29 01:12
    martinheidegger commented #77
  • Apr 28 17:33
    serapath commented #77
  • Dec 20 2019 12:00
    jmatsushita commented #77
  • Nov 29 2019 16:12
    jmatsushita commented #77
  • Nov 29 2019 16:07
    jmatsushita commented #77
  • Sep 19 2019 09:33
    deepakedayillam opened #89
  • Jul 06 2019 11:46
    devxpy commented #69
  • Jul 06 2019 01:18
    RangerMauve commented #69
  • Jul 05 2019 22:08
    devxpy commented #69
  • Jun 24 2019 20:57
    joehand commented #88
  • Jun 24 2019 20:56
    joehand commented #88
  • Jun 24 2019 20:55
    joehand commented #88
  • Jun 24 2019 20:55
    joehand commented #88
  • Jun 24 2019 20:54
    joehand pinned #88
  • Jun 24 2019 20:54
    joehand closed #88
  • Jun 24 2019 20:54
    joehand commented #88
  • Jun 24 2019 20:47
    RangerMauve commented #88
  • Jun 24 2019 20:39
    todrobbins commented #88
  • May 31 2019 16:11
    RangerMauve commented #88
  • May 31 2019 08:14
    decentral1se commented #88
Dat
@dat_project_twitter
mafintosh ah it's private
mafintosh stream.state._split
mafintosh but we can make that public
mafintosh substack: you need the dh keys or the session hash?
mafintosh the session hash is unique as well
substack haha if i sign the shared secret instead of the noise key i should change the name
Dat
@dat_project_twitter
jboy I just realized I'm away on vacation during the Dat conference, so I'm not submitting anything after all. I was going to propose a presentation on using Beaker Browser in the classroom.
substack one issue with an extension is that i can't have the extension wait until after the handshake has occured
substack so _split is defined by the time the first onmessage ocurrs, but i don't see how i can send that data after _split becomes available after the handshake
substack some sort of onready handler for extensions would be really nice for this
Dat
@dat_project_twitter
substack figured out a hack. i can do ext.local.handlers.on('handshake', f) inside the extension function
Dat
@dat_project_twitter
substack ok, i can almost get at the handshakeHash, but the handshake object is set to null by the ping() function before there's any option to copy it
substack er, in _onhandshake() rather
Dat
@dat_project_twitter
substack send a PR to expose the handshake hash in simple-hypercore-protocol, which i can get at from the hypercore-protocol object mafintosh/simple-hypercore-protocol#4
substack *sent
mafintosh substack: excellent!
mafintosh at lunch, will merge after
substack thanks for all the tips!
substack this should be much better for the signing extension
Dat
@dat_project_twitter
igel[m] damn, have i been under a rock https://peermaps.org
Dat
@dat_project_twitter
deka Hi 👋 Friendly reminder, tomorrow we have a new comm-comm meeting, propose a topic! datproject/comm-comm#160
Evaristo Rojas
@evaristor
Hi. Is this a good place to ask for help?
I can't share the files in a directory
dat share
dat v14.0.2
dat://xxx
Sharing dat: (empty archive)

0 connections | Download 0 B/s Upload 0 B/s

Checking for file updates...
But the directory is not empty:
ls -la
drwxr-xr-x - evaro  2 Jul 16:52 .dat
.rw-r--r-- 6 evaro  2 Jul 16:52 hola.txt
Any ideas?
shikhars371
@shikhars371

Frando shikhars371: what modules and versions are you using?

Im using dat version 13.13.1

its sharing on same system
but on different system when im trying to clone its not connecting
Dat
@dat_project_twitter
Frando shikars371: the dat cli is still using the previous version of the whole hypercore stack. the new version improved many things in the networking stack. the easiest way to use it as a cli at the moment is to install hyperdrive-daemon and if possible use its fuse feature, and there's import and export commands otherwise
Frando evaristor: the last reply could also apply to you i think
Frando the dat cli is basically unmaintained at the moment and would need funding or volunteers to be updated to the new version of the stack (or missing features added to hyperdrive-daemon and the dat cli then being deprecated)
Dat
@dat_project_twitter
cblgh karissa updated it i think?
cblgh Try the next version of dat! This version (14.0.0) is not compatible with older versions (13.x) and below, and works on node v12.
cblgh npm install -g dat@next
Frando ah cool! i didn't know this is already there :D
Dat
@dat_project_twitter
cblgh can't get it to work tho
cblgh tryin various hyper:// links i find on ssb
Dat
@dat_project_twitter
rangermauve cblgh dat@next is using hyperswarm but it's also using the old hyperdrive. 😅
Dat
@dat_project_twitter
cblgh aaah
Dat
@dat_project_twitter
okdistribute cblgh don't use npm to install dat, it is broken
okdistribute cblgh the executable works though. some lower-level package broke compat and npm fetches the newer broken patch
okdistribute maintainers wanted.. actually the dat open collective could be used to fix this if anyone has some time :)
Dat
@dat_project_twitter
TheLink wasn't there some rust port in the making?
TheLink would be nice if this would be the future
TheLink real native binaries + webassembly
TheLink npm was never really nice as a distribution platform for non-dev stuff
okdistribute yes there is a rust port in the making! see #datrs
Martin Heidegger
@martinheidegger
1h30 until next dat comm-comm datproject/comm-comm#162 :tada: - come to join for light conversations