#dat

ogd: https://github.com/maxogden/linux/pull/1

ogd: how do i boot it?

oh its in the readme

ogd: works btw! :)

ogd: would it be possible to just have the root user?

mafintosh: i dunno about root user. tinycore defaults to tc user

ogd: check out http://linkeddatafragments.org/, they want to use dat at some point for a trust problem -- they want to know when clients pull new data, how that data was changed, etc. They're out of Ghent University, mostly semantic web stuff.

ogd: They sort of sold me on JSON-LD. I think there's a big opportunity when pushing JSON-LD to link datasets & columns together, do easy merging simply by linking via hypertext

ogd: @id is always used as the id... which is a nice abstraction. I like it better than how we use 'key' by default, imo

karissa: i am confused by that website but probably because i dont know that much about the existing linked data systems they are trying to improve

ogd: aye, yeah. that particular problem may not be interesting for dat, but the trust and provenance of linked data is super relevant

ogd: if you look at http://linkeddatafragments.org/data/ you can see the kinds of datasets that use this model

ogd: wikipedia being the big one

ogd: mostly, my interest comes when you try to relate dats to eachother.. like, how do I know that dataset is related to that other one? or what datasets are related to this one?

ogd: sounds like you got it working?

ogd: the university is working on route planning using this client-based architecture, see this https://github.com/linkedconnections. mostly written in node.

ogd: you around?

mafintosh: soon

mafintosh: ok am now

nlf: yea i stole your dhcp code + uuid method :D working great

awesome

ogd: just booted ubuntu inside tinycore over hyperfused

nlf: we wanna try and get a prototype working but i think ill switch to be more dhyve-os if/when we need to upgrade the kernel

(ran into a bug i'm fixing now)

yeah, that makes sense, if you've already got tinycore working no reason to change it just yet

nlf: tinycore has a kind of annoying dhcp process that autostarts on boot, i would prefer to do what you did by just writing the config to /etc/network/interfaces... but for some reason tinycore doesnt use /etc/network/interfaces. is that folder distro specific? did you have to do anything special to 'install' that?

it's distro specific

mafintosh: should i do the node cli then and make it npm installable?

mafintosh: im just gonna include an xhyve binary in there for the time being

ogd: yea that would be great

ogd: could you add fuse and hyperfused to the distro as well?

mafintosh: hmm so my plan was gonna be to make a vanilla one first with only openssh

mafintosh: but maybe thats not as useful

mafintosh: i guess folder sharing is generic enough we can include it