fuoqi
Joined 6 years ago
Joined 6 years ago
It seems you do not know anything about Puerto Rico and its history of shameful US meddling.
Ideally, you need a "pipeline" with one reactor being built every 2-5 years and streamlined regulatory environment where you can use the same project "template" with minimal adjustments. This way building expertise is not lost (i.e. the industry does not need to re-learn everything for every project, which is very costly) and even can be accumulated to reduce costs further. It applies not only to the building part, but also to regulatory bodies.
The problem is that you need to operate ~100 reactors for this, so it can work only for large economies able to provide the "baseline" demand. China and to a lesser extent Russia do this, which does result in significantly lower nuclear plant building costs for them. Europe, SK, and US have dropped the ball hard here.
Completely agree with this and IMO it's how the system should've operated from the very start. Unfortunately, I highly doubt that the CA cartel will let go of the power (and associated cash flow) voluntarily.
Nope, they do it primarily out of necessity, because of the mounting pressure on the previously used CAs. The MitM capability is just a nice side bonus.
>So I empathize with the sarcasm, but best not to offer MitM proponents (whether in Russia or the U.S. or elsewhere!) an argument that could be used against your viewpoint.
If browsers truly cared about user security they would've provided reasonable conditions for supporting national CAs:
- Limit its authority only to respective national domain zones.
- Mandate use of Certificate Transparency handled by an independent third party to prevent MitM.
But this debacle only shows that western-controlled (especially financial) systems can be and will be used as a pressure tool, so any large sovereign nation will not trust them as they would in the past. And the taken actions only contribute to further fragmentation of the Internet across national and block borders.
Surely this will improve user security and trust in the existing Web PKI system in non-Western countries. /s
Not quite. The "petrodollar" deal has helped to bootstrap and anchor the USD strength at a somewhat critical moment of history after the gold peg was "temporarily" suspended, which was effectively a default of the US government (second in the 20th century!).
Sure, today trade of oil in USD no longer plays a significant role in supporting its dominance, but it still plays a role. Together with other factors (such as increased weaponization of the USD-led financial system) rise of alternative settlement systems corrodes the network effects on which USD relies. Each blow in isolation may be insignificant, but their accumulation could become critical owning to the extreme non-linearity of the network effects.
I will not be surprised if China has a constellation of such satellites to track US carriers and it's why Pentagon keeps them relatively far from Iran, since it's likely that China confidentially shares targeting information with them.
[0]: https://www.esa.int/Applications/Observing_the_Earth/Coperni...
It's related to it, but not "literally modeled" on it. This number is from experiments where people are asked to equalize perceived brightness of two lights with different colors. The results are than averaged out and interpolated using polynomials to create a color model [0].
Most of the world is perfectly fine with 12:00 not being synchronized with high noon [0]. And some jurisdictions still semiannually f*k with it further using DST. Generously assuming the current time keeping system will survive for ~6k years (looking at the leap seconds accumulation rate for the last 50 years) we can just shift timezones by one hour.
[0]: https://64.media.tumblr.com/4a9a4613f057d3b5f17ec548e6ac06d1...
>We convert timestamps to and from date+times all the time.
If you do not account for time zones during this conversion, then you are not qualified to implement such conversions.
It's fine to use 86400 seconds for durations (e.g. "this computation will finish in 1d 8h 20m 34s"), but it's absolutely not fine to use it while dealing with datetimes.
[0]: https://en.wikipedia.org/wiki/Leap_second#Phase-out_and_futu...