• 0 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle





  • You’re welcome for the details.

    So I see ‘they were ready to surrender’ a lot in this thread, and while that’s not… false, it’s not exactly what it sounds like. They were ready to come to the table, yes, absolutely, but the problem was that they wanted to dictate their surrender - they wanted to keep their military, they wanted their industry rebuilt, they wanted the current government to stay in power- it was less of a surrender or more of a cessation of hostilities. Japan was ‘ready to surrender’ in much the same way Russia was ‘ready to come to the peace table’ about a year ago.

    This was geopolitically not realistic, for a number of reasons- for one, allowing that kind of conditional surrender with Germany is directly what lead to WW2 in the first place, and nobody had any intentions of repeating that mistake. There was concern, given the view on surrendering, that it wouldn’t actually be peace, or a surrender, merely a delaying tactic to build up forces and entrench. For another, Russia was bearing down on Japan, and the Allies wanted to limit Russia’s geopolitical influence by preventing another East/West Germany. While the extra troops would have undoubtedly help save American lives, it would have ended in significant Russian and Japanese deaths, as well significant geopolitical issues long-term (East/West Germany worked so well, after all :P )

    Long story short, the Allies absolutely wanted an unconditional surrender, exactly the kind of thing the Emperor and the military refused to contemplate, even after a single bomb was dropped. The military still refused to consider it even after the second, so seeing the a-bomb in action once would likely, I feel, not have done much.

    RE: hitting civilians in large numbers, my understanding is less that they were deliberately targeting civilians, and more that they were looking for military targets that were geographically located in a position that would enhance the bomb’s effects without considering civilians too much. You could argue in a very real way that they were deployed as terror weapons, or perhaps ‘shock and awe’ weapons if you want to be slightly less confrontational. Civilian casualties were, much like the entire rest of WW2, not much of a consideration- WW2 was considered a total war, and the Geneva Convention would not be signed for another 4 years, directly as a result of the atrocities of WW2. At the time, civilians were not considered something to inherently avoid unless you had some sort of political reason to do so (hence the leaflets). The most obvious example of this is the firebombings of Tokyo, which killed far, far more civilians in arguably far more painful ways, but there’s plenty of example in the European front from all sides as well. Again, they were making decisions with the knowledge and viewpoints of the time. Doesn’t excuse it, but trying to moralize decisions made in the past with current morals is always kind of a waste of time, in my opinion.

    Regarding the third shot, there was, at the time, no bombs available when the uranium Little Boy bomb for Hiroshima was dropped, but they had prepped for another. They immediately turned towards trying to prepare another (Nagasaki’s plutonium-based Fat Man), and managed to rush it to completion in just a week, but keep in mind that these were highly dangerous, experimental one-off prototypes being produced- it’s why all of the planned subsequent bombs were of the fat man design, which was significantly safer, and America was completely out of uranium at that. It was only able to be rushed to completion so much because General Groves always planned to use two, and a lot of the logistics were already worked out and prepped beforehand. Before more plutonium bombs could be made, Woodrow Wilson called off the production. So yes, America was technically out of bombs, and completely out of uranium.

    Arguably, America could have created more plutonium bombs, but was limited by the availability of plutonium (which is lengthy to turn into weapons grade), the speed at which they could be safely produced (and Fat Man was, frankly, very unsafely produced, it should have taken nearly 3 weeks to create), and America only had a small amount of weapons-grade plutonium stockpiled. So technically, both positions are correct- America only had two bombs, and they certainly could have made more, but they were limited by time and materials, and lack of willingness. They had, perhaps, one or two more fat mans they would be able to drop, with perhaps 3+ week production times for each (because no logistics were prepared for it), before it would have dropped to something like iirc 6 months per bomb due to lack of prepared plutonium.

    So yes, one could argue there could have been more bombs after the first two, but it was generally considered by the American military and also the President that two was the ‘magic number,’ so there wasn’t any setup for them, so they would not have been cranked out anywhere near as fast. Nobody believed that one bomb would trigger a surrender (because of, again, the cultural viewpoints on surrendering) as well the implicit belief that it would be a one-off prototype that could not be repeated.

    If two did not, and it was widely considered it would, nobody believed 3 would be any more likely to trigger a surrender than two did, and might even convince them to fight harder. In addition, due to the effects of radiation, America would have limited to how they could use the bombs one the land invasion started- with Russia from the north, America from the south-east, and most of central Japan firebombed, there’s not a lot of good targets without hitting allies.


  • He’s not theorizing, he’s summarizing decades of historians’ research. We know, for example, with the benefit of hindsight, that your idea would not have worked- it would have lead only to countless deaths via nuke, and then a long, slow slog through the meat grinder for troops and civilians.

    How do we know this? Because we have Japanese communications from the time- and they basically sum up to something along the lines of “They don’t have the balls to use the bomb against people again.” with a side dash of “they don’t have more bombs to throw at people.”

    Exploding the first one over water, the second one over a city on people, and then NOT dropping a third one because we didn’t have anymore would have proved them right, and without a surrender it would have lead to millions of dead Americans and Japanese. They made so many purple hearts preparing for that invasion in 1945 that we still haven’t gone through the backlog, 80 years later.

    Now think about it without the benefit of hindsight. You know that culturally, they refuse to surrender. You know they see massive losses as completely acceptable, civilian, military, and suicide bombers. You know they want to try and grind the US down, make them give up because of the sheer number of troops dead. You know they’re trying desperately to negotiate a favorable surrender where they can save face, maintain their ‘experiments’, and maintain their military, which is exactly the sort of thing that lead to WW2 in the first place. Finally you know you only have two bombs. Use them wrong, and the deaths, crippling, and wounding of millions of your own country’s soldiers is directly on your head. Use them right, and you might get some surrenders.

    Frankly speaking, dropping the two bombs on Hiroshima and Nagasaki almost didn’t end the war. The second bomb was what finally changed the mind of the emperor, because he bought the bluff that if we had two we would throw at people, we had more. Even then, there was instantly a coup to try and halt the surrender process- and they thought this guy was literally an incarnation/speaker/appointed of god. That’s how much the military hated the idea of surrendering.

    And finally, do keep in mind- every time the US bombed a Japanese city, they dropped leaflets warning the civilians to get out. By all accounts, they were actually highly effective.

    To make it clear, dropping the bombs was a horrible thing. That it killed so many civilians who wouldn’t- or more likely couldn’t - get out in time, even if warned, is horrific. Leaflets are good and all, but that doesn’t meanyou have anywhere to go, or the infrastructure, and beyond that, the Emporer was executing anyone who tried to leave bombing areas. (Seriously, possession of a leaflet was grounds for immediate execution.) But the alternatives to dropping the bombs were judged, at the time, to be worse. And I believe that their decision to do so were understandable with the knowledge they had, the options they had, and the consequences to their own troops if they didn’t.


  • ysjet@lemmy.worldto196@lemmy.blahaj.zonerule
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    The funny thing is, their fees aren’t high. You just got duped by Epic’s propaganda that 30% was high.

    In fact, it’s vastly lower than the previous alternative, which was in store and took almost twice as much more of the cut.

    Even today, 30% is standard for a digital eshop (Nintendo, Sony, Microsoft, Apple), except Valve offers more services and benefits than all of them combined.


  • Because they can use the phone company records to say “We think you were here when this “violent riot” happened (actually just a protest that police started shooting at protestors because they know they’ll get away with it), you’re arrested”. And cops don’t care if you’re recording, they’ll either break your phone or shoot you anyway and then claim it was self defense.




  • ysjet@lemmy.worldtoProgrammer Humor@lemmy.mlC++ Moment
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    4 months ago

    https://wiki.ubuntu.com/Apport

    It intentionally acts as an intercept for such things, so that core dumps can be nicely packaged up and sent to maintainers in a GUI-friendly way so maintainers can get valuable debugging information even from non-tech-savvy users. If you’re running something on the terminal, it won’t be intercepted and the core dump will be put in the working directory of the binary, but if you executed it through the GUI it will.

    Assuming, of course, you turn crash interception on- it’s off by default since it might contain sensitive info. Apport itself is always on and running to handle Ubuntu errors, but the crash interception needs enabled.




  • Really dude? I never once devolved to name calling, I stated that s/he lied when s/he made false statements. What else am I supposed to say there?

    I also don’t understand how saying they doesn’t know what the subject matter s/he’s taking a stance on is ‘know-knowing’ either? S/He’s straight up said they doesn’t know what a CVE is, doesn’t know what experimental means, and while they claims to be in this field of work, they doesn’t know what a web worker is and confused a web transaction with a database transaction.

    Sure, I could have been nicer about it when they started escalating, but I never made it personal, and have no intentions of doing so either.

    EDIT: realized I was assuming their gender.


    1. I’m glad we agree a DoS is a vulnerability.
    2. CVE best practices state that CVEs are required to be assigned to experimental features. F5’s company policy is that CVE best practices are followed. F5 is the company that owns nginx. Therefore, it was required. Nice ‘legal requirement’ strawman. Also, ‘Common’ in this situation is not defined as ‘Widespread; prevalent,’ it’s defined as ‘Of or relating to the community as a whole; public.’
    3. That was a typo regarding ‘stable,’ my bad. I meant to say ‘It is just not available on stable, but is both via commercially and via the open source version.’ However, it’s still available on commercial versions and open source, and ‘non-stable’ versions are not inherently unstable, they’re just called ‘mainline’. Proof: https://nginx.org/en/download.html Stable is basically just ‘long term support/LTS’ versions of nginx.
    4. Again, you are intentionally misusing the definitions of the word common. Lets see what MITRE has to say about it, hmm?

    Common Vulnerabilities and Exposures (CVE) is a dictionary of common names (i.e., CVE Identifiers) for publicly known information security vulnerabilities. CVE’s common identifiers make it easier to share data across separate network security databases and tools, and provide a baseline for evaluating the coverage of an organization’s security tools. If a report from one of your security tools incorporates CVE Identifiers, you may then quickly and accurately access fix information in one or more separate CVE-compatible databases to remediate the problem.

    Source: https://cve.mitre.org/about/

    1. Yes, I would consider notifying the development mailing list as ‘quietly’ fixing it, as most all companies using it will not be on the development mailing list. It’s meant to be an area for developers to discuss things. They didn’t inform the public, they informed the devs.
    2. Where are you getting database from? You’ve randomly pivoted into talking about database transactions then started babbling about how you somehow think using a production mainline release with production options on a fully supported commercial binary is somehow inherently unsafe, as though it wouldn’t still be in dev or test.

    Since you seem to have no idea about how web servers work, or indeed, experimental features, I’ll let you in on a secret- The only difference between a non-experiemntal option in nginx and an experimental option is that they’re unsure if they want that feature in nginx, and are seeing how many people are actually using it/interested in, or they think that usage patterns of the feature might indicate another, better method of implementation. “Experimental” does not mean “unfinished” or “untested.”

    If you know nothing about programming, CVEs, or even web engines, please stop embarrassing yourself by trying to trumpet ill-thought out bad takes on subjects you don’t understand.


  • ysjet@lemmy.worldtoOpen Source@lemmy.mlNginx gets forked by core developer
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    3
    ·
    edit-2
    5 months ago

    There is an astounding number of lies in your post, good lord.

    1. It is an issue. A DoS is a fairly serious vulnerability, and very much is a vulnerability.
    2. Experimental features are explicitly defined to require their vulnerabilities to be assigned CVEs.
    3. It is not just available on the stable version, but both commercially and via the open source version.
    4. CVEs are not just for serious issues, they are for vulnerabilities. All vulnerabilities. It is a number that allows you to reference an vulnerability, nothing more, nothing less.
    5. Mentioning a CVE on the mailing list is the absolute least they should be doing.
    6. ‘workers can just be restarted anyway’ shows a deep misunderstanding of what a worker does. Any pending or active transactions that worker had now hangs, meaning that the service is still being denied. Trying to recover automatically from a DoS does not mean the DoS is not happening- it just means that the DoS is slower to get rolling, or intermittently seems to work mid-DoS.

  • ysjet@lemmy.worldtoOpen Source@lemmy.mlNginx gets forked by core developer
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    4
    ·
    5 months ago

    Experimental features are explicitly defined as requiring CVEs. You are supposed to run them in production, that’s why they’re available as expiermental features and not on a development branch somewhere. You’re just supposed to run them carefully, and examine what they’re doing, so they can move out of experiment into mainline.

    And that requires knowledge about any vulnerabilities, hence why it’s required to assigned CVEs to experimental features.

    And I’m not sure why you think a DoS isn’t a vulnerability, that’s literally one of the most classic CVEs there are. A DoS is much, much more severe than a DDoS.