GPL v3. It's aite for my purposes, since this isn't intended to be a library.
Just need repo changes and such.
Eh2406 reported back that the slowest resolver times were not reproducible, I expect that they were outliers spending a lot of time on disk I/O or something. Would still like a note if we discover something consistently taking >10 seconds. The current setup is really optimized for throughput though, not timing analysis.
Decide on a license. GPL would prevent people from walking off with it and running their own version without at least contributing the useful bits back, so I'm honestly leaning towards that. To do for this:
- Find the right heckin' version of GPL to use.
- Stick license in right place
- Update my repos to make srht the canonical source
- Update readme
Ideas trawled and divvied up into separate issues.
REPORTED RESOLVED FIXED
Good suggestions in #45. Takeaways:
- There are multiple services that do similar things to this already, on a paid basis, and they presumably make a living off of it.
- Nobody's going to trust the code if it stays closed-source
- Companies should theoretically donate to this if they find the information useful. But I have little faith that they will.
- I don't want to sell privileged access or early access to tools, and that isn't really feasible with open-source development anyway. But what I can do is sell privileged availability and notification. Doing this stuff routinely is going to take significant amounts of storage and compute power, and so even if it's open source, selling notifications and faster turnaround time seems to be the most hopeful prospect.
Related: #47 #48 #49