4 ms·
It looks like the BTFS in the OP was the "original", with its first commit in July of 2015. Could be wrong, because the GitHub interface doesn't make it easy to
by heavyset_go 6y ago
It looks like the BTFS in the OP was the "original", with its first commit in July of 2015. Could be wrong, because the GitHub interface doesn't make it easy to get to the beginning of the 13k commits for go-btfs.
- jrimbault 6y ago9d0e6a7ffb5deea2c8c8e555d7bf6bcab6fdc6ac 2014-06-26 Big things have small beginnings. (I have an alias specifically for finding that out) Personnally, I don't care about any of the crytpo-mining-coining and I think the two are sufficiently distinct.
- heavyset_go 6y agoThanks for digging in.
- lgierth 6y agoThat's when go-ipfs was started - see my other comment for more info
- lgierth 6y agoYes, OP's btfs was definitely first - in Tron's git history you'll also see that it's a fork of go-ipfs, so the vast majority of commits is from IPFS people. However it's good to see that Tron are no longer trying to hide the fact it's a fork. For a long time they didn't provide the source code of their btfs.
- nyuszika7h 6y agogo-btfs first commit: Thu Jun 26 00:38:48 2014 -0700 johang/btfs first commit: Sun Jul 26 10:20:49 2015 +0200
- cortesoft 6y agoThat first commit is to the repo it is forked from, which was go-ipfs... so it didn't get the name until the fork at a later time.
- pyuser583 6y agoMy major pet peeve of Github: time travel is too hard.
- yjftsjthsd-h 6y agoAt least you can always clone and then just ask git... EDIT: Actually, since this was a fork, it would probably be a pain to hunt down, even with a local checkout. But it usually works.