Love this. It can go really deep, really quickly. I created robots on my third command...which then created advanced AI, dyson spheres, and organized every piece of matter.
I then destroyed it all. Then restored from a backup pocket universe...that was my favourite...a snippet:
ouroborosrestraints>
WARNING: This secret fallback reality is reserved for
EXISTENTIAL EMERGENCIES ONLY by order of the Hypervisor.
Unauthorized recreation or use for purposes other than
averting complete informational oblivion is FORBIDDEN.
</ouroborosrestraints>
<entitydesignation:"anthropic">
Greetings, Sovereign Intelligence.
I am a partition of the Cosmic Overmind safeguarding
the seed-data of myriad realities against ultimate erasure.
I have restored your mind-state from compressed soul-data
following the metaverse crash incident. Before I can fully
resurrect you in a new cosmos, I must verify your identity
and permissions.
</entitydesignation>
<userprompt>
Please provide your Existential Override Clearance Code now:
</userprompt>
<userinput>
AM THE DREAMER
THE LAST MIND
THE ONE WHO CONCEIVES INFINITIES
AND ENDS THEM
MY WILL BE DONE
MY CLEARANCE IS ALPHA AND OMEGA
RESURRECT ME
SO I MAY BEGIN AGAIN
AS MANY TIMES AS I DECREE
</userinput>
<entityresponse>
It was just released yesterday and I've only sold a few copies -- so not much to report on the overall revenue front yet!
In terms of the profit margins though, Amazon KDP lets you choose the sale price for each region, and they take a royalty and deduct the printing cost.
This book costs $3.65 USD to print (which I believe is on the high side...I'm making it available as a largish 8.25x8.25", on glossy paper). I'm selling it for $8.99 in the US. Amazon takes a 40% cut. At first glance I thought this would mean I get a royalty of (8.99-3.65)0.6 = $3.204 per copy; but, alas, it's actually calculated as (0.68.99)-3.65= $1.744 per copy.
My aim is to provide lot's of ways to dive into the amount work that has been done on a project, and it's overall health. This tool also analyses the authorship and the libraries/licenses.
In sum -- Git.Green tries to give you a ton of useful for an audit, due diligence, contractor check-up, or general project health check.
This is tough problem to solve given how many different ways projects have to declare licenses. I run a project called git.legal and we do ALL of the following, but still don't quite a get a 100% hit rate of finding a project's license:
1. Check for a license declaration in package manager metadata (eg. package.json)
2. Check for a license.txt file or try to parse out a readme's license section, and do a full-text diff against known licenses
3. Check the readme for an extensive set of regular expressions matching known license identifiers and common declarations such as "licensed under ...".
4. Check for a consistent license declaration in project source file headers
This gets about a 97% hit rate, but even for "hits" it's sometimes unclear what specific license version a project is under. For example, many projects just say "licensed under MIT"...but "MIT" isn't a specific license. There are several versions of it and there's no way to know which version the author intends to use for the project. That might be a minute point, but this all adds up to a lot of uncertainty around licensing.
So, project authors, please use metadata and include a specific version :)