kewde

@g1itch I doubt it. The ASICs operate under a very specific format that I doubt is applicable to BitMessage.

Has there been any progress on this issue?

If you're storing a cache of the node modules, then try clearing it (node_modules).

Sandboxing will means deprecrating the IPC architecture in favor of [ProtocolHandlers](https://www.electronjs.org/docs/api/protocol). I've read reports that IPC can fail under high loads, see [slack.engineering](https://slack.engineering/interops-labyrinth-sharing-code-between-web-electron-apps-f9474d62eccc)

It's implemented & available in many releases, just marked as experimental.

I have used it in production for over two years and haven't had any issues. At this point I'm willing to believe it's marked as experimental just because they don't...

I would suggest using moving away from any IPC-based design as it does not scale very well for large applications. The protocol handlers are likely a better option as they...

I referred to the article to explain that IPC does not perform well for a lot of data, therefore protocol handlers are a better alternative. Write a ProtocolHandler for example...

My 2 cents, do the above but write a generic variant. in main process: ``` function whitelistFS(call, args) { if (call !== "writeFileSync){ return false; } return true; } const...

This dereferences the code behind the require function, making it potentially eligible for garbage collection? The gc isn't automatically triggered tho, so something like this would be required. https://simonmcmanus.wordpress.com/2013/01/03/forcing-garbage-collection-with-node-js-and-v8/