@nasser whenever i use github i always wish the discussion were in *a* repository but i feel like having it in the same one could get messy? (i.e. switching between discussion and in progress code might be more of a pain). that's kind of just a UI sort of thing so i guess it could be in the same repository either way
@eq that's really good feedback. yeah my current prototype stores them in the same repo but on their own orphaned branch, one branch per conversation. UI is undetermined, but i was imagining you wouldnt really interact with the conversation branches directly (though you certainly could) but is instead would use (cli/editor/web) tools to do it for you? like i said, totally undetermined.
@nasser just doing it via git logs was one silly idea i had running through my head when writing the first post. i think i tried something similar for some project a while back
@eq yeah it *basically* just works because git is a remarkable piece of software. this was me messing around a few days ago. the messages are stored in the commit messages, and attachments work by storing files in the object store.
@nasser oh i didn't think about that being useful for attachments but it makes a ton of sense! that's clever
@abrahms @eq I was thinking new conversation branches could get temporary names and then after the first commit be renamed to the hash of that commit, because you really want to refer to a conversations by some kind of unique hash and at the first commit works as well as anything. current prototype doesn't do anything like that yet.