Peace to a people unknown!

As the title says, what I'm trying to accomplish, God willing, is to upload refs and objects into steem using a main post's comment tree.

Usage would be git remote add origin steem://username@token/permlink but it just occurred to me that the steem username of the client may be different than the steem username of the repo's "owner" or "creator". Might have to update that once it's up on steem, God willing :)

God willing:

Should this create the post if it doesn't exist already? Would this be done on the first push?
Should we expect only two root posts, refs and objects, from the main posts, author?
Should the permlink structure be predictable or should we rely on crawling (eager or lazy?) and caching the results?

Initially, I'd like to store objects directly into steem and then add ability to store on IPFS (especially for larger commits) and reference these via steem and fetch them accordingly. Perhaps an algorithm or user defined configuration options could determine which to do. Hopefully though, God willing, the git-remote-helper can deal with both.

I've seen a similar project with Ethereum using something called snapshots, which is a map of git hashes to ipfs hashes, stored on an ethereum node/contract. Perhaps we could do something similar, so instead of a single comment for each object, allowing for a comment for a list of objects (whether to ipfs or directly?)

That's the deal so far. Peace and many blessings!

Topics