@Christoph-Hart Is it possible for you to increase the amount on your end for future builds, or is there a significant performance impact for doing so?
@Lindon yeah you’re right! The eq module should just be enough since I was planning on using multiple filters to change slope of eq, but we’re not doing that anymore so we can just use the eq module, nice!
Have you tried to isolate the networks and build then in individual projects?
Which one is causing the issue?
Are others building fine?
What system are you on? Is it happening on other systems as well?
Have you tried eliminating nodes to see which one is causing the issue?
If none of that still works, consider posting a minimal project as a snippet.
Frankly, there is not much about obfuscation for now.
I think cracking the plugin depends on user demand. If it is a well-known company and it is a plugin that is really demanded by the users, the cracking of the plugins will take at most 1 week, sometimes 2 weeks.
(and using RSA stops that as they cant generate your private key)
unless 512 is "easily" hackable, right? Hence the 2048 size 🤷
because if a hacker can easily hack a 512 key there's no point in building the most protective code
yeah - EdDSA seems to be the way to go...if you want it secure - buit really the last hour has told me I know nearly nothing about asymmetric encryption...
@virtuscapeaudio another way if you’re interested could be using Shopify’s but buttons so all the products are hosted on their servers, but could be more expensive than something like aws s3