Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 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
  • May 30 2019 21:59
    todrobbins commented #88
  • May 30 2019 21:56
    todrobbins commented #88
Dat
@dat_project_twitter
fleeky any ideas on how to do symlinks to hyperdrive mounts or .. some other solution to meet this issue?
Dat
@dat_project_twitter
andrewosh hey fleeky -- mind describing the situation a bit more? you're looking to create a symlink at /mountA/my-link that points to /mountB/my-dir?
fleeky no
fleeky its outside of the hyperdrive mount directory
fleeky so there is ~/Hyperdrive
fleeky within that i would like to symlink to an outside directory
andrewosh oh I see, yeah currently we're sandboxing symlinks within ~/Hyperdrive so that they can't reference external files
Dat
@dat_project_twitter
andrewosh just because you'll likely be mounting drives that were created by others, and it seems like a dangerous path to allow someone to ask people to create a beaker site that symlinks to ~/.private/my-secret-keys` say
andrewosh symlinking between mounts inside of ~/Hyperdrive should be supported. beyond that keeping your external directory synced through other means (or through a yet-to-be-written hyperdrive sync command) is the way to go
Dat
@dat_project_twitter
fleeky ok
fleeky thanks for the explanation
andrewosh yeah if you hit bugs with the rsyncing ping me or open an issue. don't want that part to be giving you trouble
okdistribute serapath good news, i think for your project. multifeed might be adopting the 'discovery-key' event from corestore
Alexander Praetorius
@serapath
oh interesting. was that ever mentioned? i'm not sure i even looked into that already. what's the discovery-key event for?
Dat
@dat_project_twitter
okdistribute its in corestore to get other cores
okdistribute multifeed right now does a manifest feed but there's movement on also supporting the discovery-key method
Alexander Praetorius
@serapath

yeah, i'm just reading it. found it in the source code, but i did look deep into the kappa core down to multifeed and mux code and i looked into hyperdrive and got an in-depth explanation from mafintosh too, but didn't spend much time yet to check out the details of corestore.

...i thought the way hyperdrive works is having a feedkey from which you derive a discoverykey and thats basically for the metafeed and the first message gives you the feedkey for the contentfeed and the rest of the metafeed is a hypertrie where you get additional feedkeys via the 'mounts' key

...but then again - i saw that hyperdrive is using corestore now? ..i think i saw that in the code somewhere if i'm not confused
how does the discovery-key method work and where is it used in practice? does hyperdrive make use of it?
Dat
@dat_project_twitter
mafintosh corestore uses it to see if has a specific feed someone requested over the wire protocol
Dat
@dat_project_twitter
rangermauve andrewosh: Are derived private keys in corestore persisted?
rangermauve Like, once I create a hypercore with a derived key, will I be able to write to it if I load the key without re-deriving
andrewosh rangermauve: the keys are derived from a master key and a name (which is stored on disk in a file called name). the private key is regenerated at runtime from those two things, but you don't need to pass the name in any subsequent time you load the core
rangermauve As long as it's the same namespace, right?
Dat
@dat_project_twitter
rangermauve So if the first time I use store.namespace('foobar').default() to get the core. if I save the key and use store.get(key) the second time, it won't have the private key populated, right?
rangermauve And even if I use the namespace, it'll deduplicate to the existing feed that isn't writable?
andrewosh nah the namespacing won't affect the writabililty of the core. it's really just a convenience around the default function and also replicating sub-groups of cores, but it doesn't affect write permissions currently
andrewosh as in the store.get(key) case will still generate the correct key
rangermauve Cool, thank you!
andrewosh sure thing!
Dat
@dat_project_twitter
fleeky andrewosh: ok different questoin , can there be more than one easy location for hyperdrives?
Dat
@dat_project_twitter
nettle mafintosh or andrewosh: is there a write-up somewhere of how hyperswarm works?
Dat
@dat_project_twitter
deka oh that would be super nice to have
deka Hello folks, comm-comm meeting happening in ~1hr. Stay tuned => datproject/comm-comm#136
Dat
@dat_project_twitter
deka comm-comm meeting starting in ~5min
Dat
@dat_project_twitter
rangermauve andrewosh: mafintosh: Renamed .destroy to .destroyData. How does that sound? Also, gonna update my hyperdrive PR to match
Dat
@dat_project_twitter
rangermauve Updated Hyperdrive PR: mafintosh/hyperdrive#271
Dat
@dat_project_twitter
okdistribute andrewosh pfrazee how easy would it be to hack cabal in there?
okdistribute cblgh: o/
pfrazee hmm probably need a hypercore api and a way to hook into the hypercore replication
pfrazee which you could do in the short term with a browserified copy
pfrazee could look into (finally) tackling the hypercore api though
Dat
@dat_project_twitter
okdistribute that would be great. cool that browserify could work short-term with peersockets
pfrazee yeah. If anybody’s trying it hmu if you hit issues
Dat
@dat_project_twitter
okdistribute we were testing hyperswarm in cabal earlier today, seems to work, planning on upgrading to that in both desktop and cli. mapeo & peermaps will be using it too. would be great to have a compatible beaker client
okdistribute ...and not having to run so many electron apps simultaneously 🤪
Dat
@dat_project_twitter
cblgh :o