[Scotups]

yea, you're absolutely right! I am the author of that said animation lib, ngFx, from years ago. Was actually my first open source project. When we started tipe years ago, we sunsetted that project and used the stars to generate hype for tipe. We were way ahead of ourselves :). Because we're in private release, all of our open source is private on github right now. Once we're not longer in private release, it will be public.

[paulryanrogers]

> ... we sunsetted that project and used the stars to generate hype for tipe.

How common is this?

Seems like fraud to intentionally swap out a project within a repo for something very different to repurpose a reputation metric.

[woah]

Seems... questionable

[Scotups]

I agree. We didn't intend to post on HN until everything was public. Someone else posted it, so I'm here rolling with it.

[masonhensley]

I think you are missing the point.

Seems questionable to repurpose the repo to leverage the stars regardless of whether you posted it here or someone else did.

[ColoradoDev]

It seems like fraud.

[Scotups]

oh, yes, that was one of many mistakes we made early on. As we move to a public release, that is on our list to clean up.

[Ericson2314]

GitHub should tie stars to commit hashes to avoid this sort of crap. Your repos stars is calculated from the started commits that are in this repo but not any it's forked from, on the default branch.

Still prone to abuse from transferring repo to credit somebody else, but the original repo owner would have to sign off on the transfer at least.

[Scotups]

I am the original repo owner. I invite you all to try tipe for your selves. Signup

[sk5t]

But... you did this intentionally--when it would have been easier and simpler to not do so? Doesn't really fit the mold of "clean it up later" chores.