Thank you! It uses D3js as-is for no other reason than being the one I'm more familiarized with.
I also had issues with node density. The way I solved them was by adjusting the forces between the nodes, particularly the repulsion and collision forces so that there is is no superposition. Values too high or too low can make the simulation chaotic or too dense, while others make it more fluid or faster to stabilize from an initial seed.
That being said, if it was a bigger simulation I probably would have had issues keeping the performance, and it's possible I would have considered a different engine.
So they're removing of opt-in consent for sharing personal data that is considered low-risk (what data is considered as such is not mentioned in the article, and as we all know it's too easy to deanonymize or extrapolate identities), and allowing the free face-scanning of people.
I hope the japanese people are aware of this and trying to fight it back, because sure as hell doesn't sound like a legal change like this is worth it.
While I can understand the rationale behind it, I can't imagine this being used for anything that requires low latency requests.
I imagine the flow would be something like (correct me if I'm wrong) [client request] -> [backend returns an error]/[accepts the request and waits for payment] -> [client sends the money] -> [backend accepts the transaction] -> [backend returns the requested data]. All of this sounds like a huge bloat over the current API key/token system.
As always, it's hard to implement child protection measures that don't impact the general population in any way. Either it doesn't need to know the age of the person and hides the contents by default (thus leaving the general population without access and serving as a way of censoring contents) or it resorts to privacy-invasive methodologies to try to know the age (which often involve behavioral analysis or personal data).
What politicians should be promoting are campaigns and tools that help educate children and their parents.