#dat

erikg: we actually already do almost exactly what you described

[dat] akoenig opened pull request #196: Extended response from '/api' route (description and publisher) (master...feature/rest-api/meta-extension) http://git.io/T-cfSg

[dat] akoenig opened pull request #197: Added charset to response 'Content-Type' header (json response). (master...fix/rest-api/json-charset) http://git.io/4m20MQ

ogd: oh boy, i should read dat source a bit more

ogd: thanks :)

dat is a reimagining of sed.

plus git, plus modules instead of sed snippits

[dat] mafintosh pushed 2 new commits to master: http://git.io/_rHd2g

dat/master 9e12933 André König: Added charset definition to the response 'Content-Type' header (json...

dat/master a309899 Mathias Buus: Merge pull request #197 from akoenig/fix/rest-api/json-charset...

donpdonp: how is git used in dat?

ogd: ahh, there it is in schema. sorry for the noise.

erikg: well i meant as far as sync'ing

its git-like, but doesnt use git

im still trying to wrap my head around the dat concepts

donpdonp: maybe we can help each other :) i am in the same boat

erikg: no worries at all. It's actually quite reassuring that you came to the same conclusion

erikg: also it's important that we make dat understandable so this is good feedback

ogd: yup, i think it's the right solution. has there been thought put to reading raw protocol buffers in rather than json or tabular data?

ogd: this would seem a little difficult to coordinate, but it could help where the native format is defined using protobuf

ogd: as an example, https://github.com/ekg/vg

as far as I know, there's the ability to import raw blobs. in cli usage, ```dat blobs put jingles jingles-cat-photo-01.png```

karissa: blobs are fine, and helpful, but it would be awesome if (when this feature matures) i could query the data based on given fields, and also control changes that occur on a record-by-record basis

karissa: in any case, converting to/from JSON will work

erikg: we have to improve the raw protobuf read/write APIs to the tabular store. I think there's an open issue for that somewhere

mhm it seems like when a module has "simple" in its name, that's a good indicator that it's too complicated

finnp: lol yea that external api is simple but in order to do it they had to make horrible abstractions

ogd: and sometimes it means "easy to use with express"