Hi, it is so wonderful you have made this.
Briefly listing other similar projects: git-ssb, gittorrent, git-remote-bsv (hacked up by me, unaware of dgit). dgit looks very refined compared to these othet options.
Do you have time to answer any of these questions? I'm afraid I don't speak golang well.
-
Are there quick instructions anywhere for running a tupelo node?
-
Does the protocol provide for someone to write software that enumerates all dgit repositories?
-
Are username conflicts already handled by the tupelo protocol?
-
Does dgit connect to a local tupelo node, speak the tupelo network protocol itself, or connect to a remote api?
-
What digest algorithm(s) are used to verify the skynet-delivered git repo is correct?
-
Does tupelo protect that git repository hashes are unchanged in public history if all nodes using them are compromised by an adversary? (i.e. is a hash sustained by peers who don't use dgit?)
Hi, it is so wonderful you have made this.
Briefly listing other similar projects: git-ssb, gittorrent, git-remote-bsv (hacked up by me, unaware of dgit). dgit looks very refined compared to these othet options.
Do you have time to answer any of these questions? I'm afraid I don't speak golang well.
Are there quick instructions anywhere for running a tupelo node?
Does the protocol provide for someone to write software that enumerates all dgit repositories?
Are username conflicts already handled by the tupelo protocol?
Does dgit connect to a local tupelo node, speak the tupelo network protocol itself, or connect to a remote api?
What digest algorithm(s) are used to verify the skynet-delivered git repo is correct?
Does tupelo protect that git repository hashes are unchanged in public history if all nodes using them are compromised by an adversary? (i.e. is a hash sustained by peers who don't use dgit?)