Sherlock is changing the way SaaS businesses understand and operationalize their product engagement data. Built by a team of SaaS veterans, we are the only product engagement scoring application on the market today. We have found success with our early customers and are ready to expand the team to accelerate our growth. We offer a competitive salary and benefits and are excited to build out the team further.
I think it's referring to the fact that certain details (traffic, DNS requests, timestamps, IP addresses) are logged. Ideally you want a service that does not log anything, that's why "Yes" is red.
Tagging would be the next addition. I added the ability to search for keys by prefix quite efficiently, so provided one stored keys like "requests:server1", "requests:server2", one could easily run the following
requests = 0
for key in gauged.keys('requests:'):
requests += gauged.aggregate(key, Gauged.SUM, start=-Gauged.WEEK)
Generators are provided by V8, don't require an external fibers extension (i.e. hack), and will be available in the next node stable via `node --harmony-generators`.
It's pretty negligible in the scheme of things. I was abusing PHP reflection a while back to add decorator support (https://github.com/chriso/Request) and used this pattern to reduce the cost:
switch (count($args)) {
case 0: $method(); break;
case 1: $method($args[0]); break;
case 2: $method($args[0], $args[1]); break;
//etc
default: call_user_func_array($method, $args); break;
}
It's a project created and maintained entirely in my free time. I provide free support when someone needs help and I fix bugs when someone files an issue. I've written documentation and a guide in the project's Github wiki. This is all done outside of full-time work. Forgive me if I don't spend more time improving the website and uptime when it's an endeavour that brings me no income whatsoever. You're the type of person that makes me hate open-source sometimes.
Of course it has a backend, but so do the Firebase apps that this entire thread is talking about. Referring to a JS app as "client-side" doesn't imply that there's no backend logic.
My point is that you can't just de-obfuscate a primarily client-side JS app and replace the Firebase (or whatever) endpoints. Proprietary obfuscation is more than just variable name munging and minification..
The allocator may yield to the OS when requesting or releasing memory (e.g. sbrk, mmap, munmap)?