5 ms·

very unfortunate indeed as there's another project with this name: https://github.com/TRON-US/go-btfs https://github.com/TRON-US/go-btfs I dont know whether th

very unfortunate indeed as there's another project with this name: https://github.com/TRON-US/go-btfs https://github.com/TRON-US/go-btfs I dont know whether the maintainer is a supporter of crypto (as in tokens) but having a common name with a Tron product (or cryptocoins in general) can backfire.

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 ago
  9d0e6a7ffb5deea2c8c8e555d7bf6bcab6fdc6ac 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 ago
    Thanks for digging in.
  - lgierth 6y ago
    That's when go-ipfs was started - see my other comment for more info
- lgierth 6y ago
  Yes, 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 ago
  go-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 ago
    That 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 ago
  My major pet peeve of Github: time travel is too hard.
  - yjftsjthsd-h 6y ago
    At 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.
tomc1985 6y ago
What's Tron and why should I care about them? :)
- ifdefdebug 6y ago
  a brilliant sf movie from the early 80s, should definitively watch it :)
  - WorldMaker 6y ago
    There's also an amazing full length Daft Punk music video that sometimes is considered a sequel to the 80s film, but you'll likely want to watch the spin-off cartoon for a lot of the necessary plot. In the plot of the cartoon the titular character (program) Tron is assumed dead, and then corrupted by a corrupt system. I can only assume this is why his name is being bad mouthed by some sort of crypto-currency scheme, as Tron was a good program, a security program built to defend the users and would never stand silent on for-profit exploitation of users.
- freemint 6y ago
  The TRON Project is also a 1980-1990s project in Japan to develop IoT infrastructure. They even made their own CPUs and developed 3 different flavours of Operating Systems: - an embedded real-time kernel ITRON - an soft real time single user desktop OS called BTRON - CTRON a server operating systems with real time guarantees for packet/phone line switching In addition they also developed an true international character encoding before Unicode. It wasn't ASCII backwards compatible which is why it wasn't picked by Unicode committee. A good resource to learn about it is here: http://tronweb.super-nova.co.jp/homepage.html http://tronweb.super-nova.co.jp/homepage.html

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 ago
9d0e6a7ffb5deea2c8c8e555d7bf6bcab6fdc6ac 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 ago
  Thanks for digging in.
- lgierth 6y ago
  That's when go-ipfs was started - see my other comment for more info
lgierth 6y ago
Yes, 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 ago
go-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 ago
  That 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 ago
My major pet peeve of Github: time travel is too hard.
- yjftsjthsd-h 6y ago
  At 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.

tomc1985 6y ago

What's Tron and why should I care about them? :)

ifdefdebug 6y ago
a brilliant sf movie from the early 80s, should definitively watch it :)
- WorldMaker 6y ago
  There's also an amazing full length Daft Punk music video that sometimes is considered a sequel to the 80s film, but you'll likely want to watch the spin-off cartoon for a lot of the necessary plot. In the plot of the cartoon the titular character (program) Tron is assumed dead, and then corrupted by a corrupt system. I can only assume this is why his name is being bad mouthed by some sort of crypto-currency scheme, as Tron was a good program, a security program built to defend the users and would never stand silent on for-profit exploitation of users.
freemint 6y ago
The TRON Project is also a 1980-1990s project in Japan to develop IoT infrastructure. They even made their own CPUs and developed 3 different flavours of Operating Systems: - an embedded real-time kernel ITRON - an soft real time single user desktop OS called BTRON - CTRON a server operating systems with real time guarantees for packet/phone line switching In addition they also developed an true international character encoding before Unicode. It wasn't ASCII backwards compatible which is why it wasn't picked by Unicode committee. A good resource to learn about it is here: http://tronweb.super-nova.co.jp/homepage.html http://tronweb.super-nova.co.jp/homepage.html