There's a limit to open mindedness. Ukraine is not "luring [the Russian military] into [its] cities," they're defending their cities from an invading force.
> Surprisingly, Facebook is among friends. Every payroll period, Amazon, Microsoft, and Oracle also provide an electronic feed of their employees’ hourly work and wage information to Equifax. So do Wal-Mart, Twitter, AT&T, Harvard Law School, and the Commonwealth of Pennsylvania. Even Edward Snowden’s former employer, the sometimes secretive N.S.A. contractor Booz Allen Hamilton, sends salary and other personal data about its employees to Equifax Workplace Solutions.
University starts with the 'y' sound, hence "a university." On the other hand, "an unimpressive fact" uses "an" because "unimpressive" starts with the 'u' (vowel) sound.
US federal civilian pension (FERS) is 1.1% per year after 20 years, so roughly 27-33% of your final 3 years of salary. They also took out the hacks for overtime, bonuses, etc. to prevent the games you sometimes see with state and local pensions.
The caveat to that is as of today you contribute 4.4% of your salary / year into the pension fund, in addition to 401K savings + social security. The Obama administration raised it from 0.8%.
In my experience, the benefits of microservices are primarily better delineated responsibilities and narrower scope, and secondary benefits tend to fall out from these. There are downsides, but the "harmful" effects do not reflect my experience. I fully grant more things on a network invite lower availability / higher latency, but I contend that you already need to handle these issues. Microservices do not tend to grossly exacerbate the problem (in my experience anyway).
The other callout is clean APIs over a network can just be clean APIs internally. This is true in theory but hardly in practice from what I've seen. Microservices tend to create boundaries that are more strictly enforced. The code, data and resources are inaccessible except through what is exposed through public APIs. There is real friction to exposing additional data or models from one service and then consuming it in another service, even if both services are owned by the same team (and moreso if a different team is involved). At least in my experience, spaghetti was still primarily the domain of the internal code rather than the service APIs.
There's also a number of benefits as far as non-technical management of microservices. Knowledge transfer is easier since again, the scope is narrower and the service does less. This is a great benefit as people rotate in and out of the team, and also simplifies shifting the service to another team if it becomes clear the service better aligns with another team's responsibilities.
The client in this case should be the web-browser; it shouldn't be custom Javascript. There should be an attribute on the password field that says if the password should be hashed before sent to the server. It could also be salted by the browser to reduce reuse across sites similar to any password manager today.
Primarily to get around arbitrary password rules that do not enhance the security of the password but serve to weaken it, e.g. only use special characters from this list: !@#, or sorry your password is TOO LONG (?!)
Hard to rely on voting when the voting is rigged re: gerrymandering...
As for how to fix it, I'm no expert but off the top of my head
1. Allow public submissions for districts to prevent rigging choices
2. Create an objective set of measurements for scoring districts with the , e.g. maximize compactness, minimize perimeter, other measures that would help combat gerrymandering
3. Highest score wins? Top N finalists are voted on by legislature?
Hardly perfect, and I'm sure someone's thought about this harder and could do better. But nearly anything has got to be better than "the party in power every 10 years is given a carte blanche opportunity to further solidify their power"
Implementations of RSA have suffered from all sorts of problems that have led to real world attacks irrespective of the hardness of factoring prime numbers. The intuition behind RSA being hard is alluring in its simplicity, but it's deceptive. https://blog.trailofbits.com/2019/07/08/fuck-rsa/
It's like a consent form for a medical procedure. At the end of the day, you're not a medical professional. Is the average person really informed when they do or don't provide their consent?
Nevertheless, consent is still paramount. Removing consent on the basis that most users are incapable of being informed is a poor excuse.