mukesh610

HTML5 History API allows for modifying the URL too.

If an attacker leverages an XSS they can exactly replicate the login page, URL and all, only limited by payload size and modern protections like CSP.

If my understanding is correct, IPFS provides a way to only store files. Wayback Machine archives entire webpages, along with any CSS or JS (?) included. So building a webpage archival service over IPFS needs significantly more development effort.

Well angular repositories tend to have tons of dependencies.

How is that relevant?

IMO multi-line lambdas are unnecessary; they can't be easily documented or better maintained than a named function. If your anonymous function needs more than a statement it makes perfect sense to define it as a separate named function. Faster to find, document and maintain.

> elsewhere in the project is PII

Servers holding PII should be firewalled off. Necessary traffic should be explicitly granted. That would remedy the issue a bit.

So?

Synchronization primitives AFAIK don't need to transfer huge amounts of data in a short time. One bit for every "okay" signal would suffice. At the given speed you can perform 8 million syncs per second between two threads.

Please be mindful of the other person. Some parts of your comment do not exactly stand as a good example of this website.

That's exactly the opposite of what the initial comment of this thread suggests.

Is there any disadvantage to limiting the emulator's JVM heap size to match the original execution environment (in this case what seems to be 128k), instead of explicitly disabling GC?

While that's a better way to do that, if the canary had a null at the beginning it would effectively render string off-by-one errors useless, since now they can't even be exploited to crash a program. Again, this should not be used as an excuse to ignore string off-by-one errors since these errors might be triggered in other architectures where the canary isn't guaranteed to start with a null.