I would expect more of this. Most of Iran's military infrastructure is deep under 500 to 800 meters of hard rock, heavily funded by US tax dollars bully lunch money and the oil industry. Most everyone else's military infrastructure is mostly on the surface just begging for attention.
My personal preference would have been that the US had built it's bases in the same manor is Iran or better. At least I think we could have possibly done better. Keeping most infrastructure under ground means less dependency on power for cooling, more surface land for other functions. Maybe put some earth-bermed greenhouses on the surface and grow some produce for the locals.
For sure no fast FOB but they can store planes underground and they can be towed out and prepped fast just as they are doing with their missiles today. The wings come off rather easily. My remote site ordered one by mistake from the old CAMS system. The driver was just as confused as we were.
I should add that one way to think of it is that Iran built those amazing underground missile cities just for the US to take over. It won't be easy and there will be mass casualties but I think that since we paid for them we should annex them. Some countries in northern Europe have similar underground bases. I would love to visit them. The closest to that I have been inside was NORAD.
So you are ready to sacrifice thousands of lives for that?
It's not up to either of us but to your point I suspect that will occur regardless of what you or I desire. We stepped into the bog of eternal stench that is country #7 Iran. This has been planned for a very long time but every president has been able to back out of it.
Trump started it and only has authorization for about another 5 business days but I suspect congress will begrudgingly approve bipartisan authorization to not only keep our soldiers on the ground but to send another 500k to 700k as anything less would likely be ineffective against their defenses. This can not be solved by technology alone. I can only hope that we undo what we created 50 years ago and give Iran back to it's people and stop the endless proxy wars. Since I can spend hope it's free and nearly meaningless I also hope we welcome our soldiers back with more dignity than we did for the Vietnam veterans this time.
Obviously not me personally but is absolutely up to the USA that created the current Iranian government to do so. We made the mess and should clean up the mess. Iran used to be one of the top five most technologically advanced countries and one of the most progressive countries in the middle east up until the point we twerked it up by putting zealots in power and repeatedly funding them.
From what I know the Islamic republic was founded in part as a reaction to US & British meddling in the internal Iranian affairs. Do you really think the US can achieve anything positive by putting troops on the ground? Have you learned nothing from Iraq, Afghanistan, Vietnam or Korea?
From what I know the Islamic republic was founded in part as a reaction to US & British meddling in the internal Iranian affairs.
Yes, exactly this. The US (CIA) and Britain (MI5) were playing let's topple a government and this was the outcome. Even if indirect the end result is that we created the current mess. What I stated holds true.
Do you really think the US can achieve anything positive by putting troops on the ground?
I did not say that. I said that is the only way the desired end result is going to happen and that toppling them through technology will not work such as air strikes, electronic warfare and such. There will be mass casualties, I said that.
Have you learned nothing from Iraq, Afghanistan, Vietnam or Korea?
It is not up to me to learn something. If it were up to me there never would have been any kinetic wars at all. I prefer to start with economic warfare and then use discreet covert operations until they succeed. It takes longer but people are impatient and greedy. That's not my fault as far as I know.
I've enjoyed our conversation but I must get back on the gaming machine and sink some pirate ships to get my reputation up with the Brethren. Perhaps we can pick this back up tomorrow.
That's a better title, as "Tesla discloses $2B AI hardware company acquisition buried" could also mean "Tesla disclosed that it buried an acquisition" or "Tesla disclosed that a hardware company buried an acquisition".
I think they should have also added a link no I am not doing it to the movie iRobot Will Smith, Bridget Moynahan, Alan Tudyk. Main character hates robots, calls them "canner". "Move out of my way, canner". The plot is predicated on his prejudice which was justified [1] but ends up solving a crisis and his perspective is changed by the end of the movie. In my opinion it's a great movie to watch and gives some interesting perspectives on both sides of AI vs anti-AI though they don't call it that, just robots. AI is just expected.
Once a person has their own DNA how do they analyze it to find known attributes like genetic dysfunctions, diseases and other characteristics without sharing said DNA with a third party?
This X post ultimately links to iwantosequencemygenomeathome.com [1]
You can go a very long way just mapping your DNA reads to a reference genome [0]. This reference will have associated annotations of different types, e.g. mutations, which automatically give you relevant information about your own genome by being present in it (or not).
Mapping is a fairly straightforward process where SOTA software is FOSS (as is most bioinformatics software). Accessing databases can be as simple as linking your data to the UCSC genome browser [1]. Of course, if you want to go the manual way, the sky is the limit.
>by far the most useful preventative medical advice that I've ever received has come from unleashing coding agents on my genome, having them investigate my specific mutations, and having them recommend specific follow-on tests and treatments.
NGinx, Kube-NGINX, Apache, Traefik all default to normalizing request paths per reference of RFC 3986 [1]. This behavior can be disabled when requests are proxied to resources on the back-end that require double-slashes. I only reference the RFC to describe what they are talking about, not why they default to merging. They all agreed on a decision as one was not made for them.
To generalize by saying "incorrect" is incorrect. The correct answer is that it depends on the requirements in the given implementation. Making such generalizations will just lead to endless arguing. If there is still any debate then a group must vote to deprecate and replace the existing RFC with a new RFC that requires that merging slashes MUST be either be always enabled or always disabled using verbiage per RFC 2119 [2] and optionally RFC 6919 [3]. Even then one may violate an RFC is there is a need to do so and everyone has verified, documented and signed off that doing so has not introduced any security or other risks in the given implementation and if such a risk is identified that it will be remediated or mitigated in a timely manor.
[Edit] For clarification the reason I am linking to RFC 3986 is that it only defines path characteristics and does not explicitly say what to do or not to do. Arguments will persist until a new RFC is created rather than blog and stack overflow posts. Even then people may violate the RFC if they feel it is safe to do so. I do not know how to reword this to make it less confusing.
Both you and the original author cite the same RFC to support your arguments. Passages from RFC 3986 comprise the bulk of the original post.
The difference between the support for your argument and theirs is that they call out the specific sections in the RFC that they claim are relevant to the issue at hand and your comment only broadly references the RFC by name. In any case, even if they, too, merely gestured to its existence, claiming that it supports their position, then appearing here with a bare claim that RFC 3986 supports the opposing side without further elaboration is not exactly strong candidate for a path to a fruitful resolution.
In any case, even if they, too, merely gestured to its existence
That is entirely my point. If the author wants to disable merge slashes then they need to replace the RFC I linked to with one that explicitly says what to do or not do using strong verbiage that is explicit as I explained. Blog articles and Stack Overflow threads will not set a standard.
If people interpret the RFC differently than I in that they feel it is explicit vs vague then please contact all of the web daemon maintainers to have them correct their default behavior. Just know ahead of time that two of them are quite challenging to have these discussions with.
> That is entirely my point. If the author wants to disable merge slashes then they need to replace the RFC I linked to with one that explicitly says what to do or not do using strong verbiage that is explicit as I explained.
That doesn't seem to be the case. You said, "NGinx, Kube-NGINX, Apache, Traefik all default to normalizing request paths per reference of RFC 3986". That's a strong claim, not an appeal to ambiguity.
> Blog articles[…] will not set a standard.
Blog posts absolutely have the power to influence future developments. That's historically how it has worked. "RFC" stands for "Request For Comments".
This development work is already completed. New web daemons would likely just follow the precident that has been set by the popular daemons as to not cause confusion, unexpected behavior and even more arguments.
If a notable sized group of developers would like to contact all the web daemon maintainers I can list all their contact information. In my experience these developers and F5 are not very open to making sweeping changes but there is mostly no harm in trying. The represenative should be someone thick skinned.
It really isn't up to me. If enough developers find this to be an important issue then the first step would be to replace the RFC with a new one and then work with the existing web daemon developers to change their defaults. There should also be an effort to communicate these changes to all the internet companies world wide long in advance as this will be a breaking change for many people. Perhaps I am just jaded but I think this will break a lot of stuff and cause a lot of really bad maintenance windows and other fallout. Who among the developers is willing to take the lead on this? You appear to be very articulate and astute. Are you taking the lead?
> It really isn't up to me. If enough developers find this to be an important issue then the first step would be to[…]
That's not what I asked. In one breath, you've said they need to take up that effort. In the next breath, you've said that it's a done deal. I'm asking: which is it?
Making up your mind (instead of perpetually moving the goalposts) is up to you.
I believe you misunderstood them. The way I interpreted it is: 1) the development is already done, so the developers have broad consensus on how it should work; 2) the only thing that can break that consensus is a new RFC that tells them in no uncertain terms to do it differently.
> Making such generalizations will just lead to endless arguing
But 80% of all programming blog posts on the internet rely on being able to make sweeping generalizations across the ecosystem! Without this, we basically have nothing left to argue about.
Caring about tradeoffs, contexts, nuance and not just cargoculting our way into a distributed architecture for a app with 10 users just sounds so 90s and early 00s. We're now in the future and we're all outputting the same ̶t̶o̶k̶e̶n̶s̶ code, so obviously what is the solution in my case, surely must be the solution in your case too.
Without this, we basically have nothing left to argue about.
My theory is that the codex [1] was created not to stop arguments but rather to shorten them so that we can find a path forward, get back to work and accomplish some mission.
My personal preference would have been that the US had built it's bases in the same manor is Iran or better. At least I think we could have possibly done better. Keeping most infrastructure under ground means less dependency on power for cooling, more surface land for other functions. Maybe put some earth-bermed greenhouses on the surface and grow some produce for the locals.
reply