-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
picovoice #18
Comments
No I have not and likely never will¹. The intent of this repository was to provide a way to build the snowboy infrastructure from source and thus allow usage on newer platforms without doing crazy linker stunts or container stuff. I did this because the company behind it ceased to exist (at least in a form that supports snowboy). Picovoice on the other hand is still a very much alive company, that is reliant on its tech to generate income and supports their codebase. They offer a free forever plan with reasonable limits for individuals (25h/month for request based apis, 3 concurrent users for continuous) and industry standard pricing² for companies. If you just slightly cross the free limit, theres not much stopping you from just registering multiple accounts and switching the access key on demand. If you like their product, support them. The issue with this kind of projects is that reverse engineering technically violates the Terms of service and might even be legally problematic. If you feel like you want to take the risks of reversing something that has monetary value behind it, feel free to do so and I am happy to give you tips on what to look for and how to go forward. However I don't have the time to reverse something where reversing it does not really provide a benefit. ¹ I might look into reversing/removing the license check, if they ever go out of business or discontinue one of the products with no adequate replacement, but looking at their portfolio and customers I wouldn't expect that to happen any time soon. |
Have you every tried to apply reverse engineering to picovoice?
The text was updated successfully, but these errors were encountered: