mafintosh: does the "fix all the things" commit in hyperdrive-hyperdb fix the file storage stuff?
dat-gitter
(RangerMauve) So, once hyperdb support comes for hyperdrive, and there's something figured out for differentiating between hyperdb and old hyperdrive instances, would it be possible to have a utility to "convert" a dat that you own to use hyperdb?
mafintosh
jhand: yuh :)
jhand
yay, thanks
will try it out in dat-next
mafintosh
jhand: still bugs for sure! let me know tho
dat-gitter
(RangerMauve) I assume that when a two peers using different protocols meet, they'll just ignore each other. So that means you can have the same key used for two dats at the same time.
Reading the git wikipedia page: "As a distributed revision control system it is aimed at speed, data integrity, and support for distributed, non-linear workflows." - lucky for us!
noffle
millette: on buying github? yeah, I think it's a done dela
deal*
millette
on hyperdb-git-repo I meant ;-)
noffle
ah
dat-gitter
(RangerMauve) noffle: Have you considered basing it on the DatArchive API from beaker so it can work in the browser?
noffle
RangerMauve: I don't know much about how that works tbh. would that prevent it from working on cli apps?
having web + cli + beaker support together would be great
but I don't want to get locked into beaker only
dat-gitter
(RangerMauve) middle: You can use node-dat-archive for node support and I could use it with Dat-polyfill to make it work in browsers
(RangerMauve) It's basically a wrapper for hyperdrive.
noffle
RangerMauve: is hyperdrive using hyperdb now?
does DatArchive have multiwriter and hyperdb's auth mechanism?
dat-gitter
(RangerMauve) Not sure. Also the DatArchive API doesn't support multiwriter yet
noffle
ah
dat-gitter
(RangerMauve) I guess that's be a deal breaker then. 😅
noffle
I know hyperdb the best right now, so I think I'll hack on that. not opposed to using datarchive though once it's ready!
luckily the two aren't mutually exclusive projects
dat-gitter
(RangerMauve) The approach I was planning was going to be to use hyperdrive like an FS to store all the git refs and stuff, and have remotes be dat archives that are treated like folders.
(RangerMauve) I wouldn't really need multiwriter for that, and once it does come out I could use it for collaborating on a single dat or something
(RangerMauve) Gonna read your source for inspiration 🙏
noffle
RangerMauve: that's more or less what I'm doing on hyperdb: treating it like an fs store for git objects
but all in the git/ prefix
so you can extend on issues and prs into their own hyperdb prefixes too