I lean right (fiscally) and sometimes my comments are perceived as unwelcome in group chats. Such topics include afghanistan, covid statistics, are seemingly discouraged.
Comments talking about how terrible, racist, and sexist the company is are totally cool. In fact creating a woman's right's channel where the whole purpose is to bash our own employer is also cool. @hereing #general with stories about sexism and how it is rampant in society and white males are no problem. But not afghanistan. Not ok. I imagine most people must hate the obnoxious BS but nobody wants to shout back in 2021.
This should have the citizens mass protesting in the street. DNA and iris samples to get / maintain a phone number.
This biometric data that cell phone users will be forced to turn over to the Government includes; fingerprints of the users; the iris of his eyes, the features of his face (facial recognition data), voice recognition, the signature and the DNA.
I can only speak for the first gen zen. There's a bug with most motherboards that cause a hard lockup every day or so.
Changing the power state fixes the problem with an updated bios but disables boost.
Thread: https://bugzilla.kernel.org/show_bug.cgi?id=196683
It's possible that nobody was on the bridge. Loads of tankers are driven by autopilot. Additionally, the USN ship wasn't transmitting AIS so they were essentially invisible.
Not sure about the firing squad... people make mistakes, I can certainly see how she was focused on trying to avoid a collision and forgot to sound the alarm. There must have been at least 5 other people on the bridge who could have done it as well.
There were multiple failures that allowed the situation to get this out of hand. Ideally, she would have had forceful backup from the CIC.
Of course it should go up the chain, it should go as high as the people making the tasking to the ship Captains when they know the ships aren't ready to execute. Blaming the crew in this situation is discounting the factors that force the crew to operate like this.
Excellent question.
I'd love to go into detail to paint a clearer picture but I don't think it would be prudent. So let's work with this thought experiment which is definitely not out of the ordinary:
We're in a condition where half of the watch team has to be standing watch at a time. As a result, we have a rotation of 5 hours on, 5 hours off, 7 hours on, 7 hours off. In addition to standing watch, training has to be conducted, the ship has to be swept, maintenance of equipment needs to get done. As a result during your 5 hours off you try to get this all taken care of so you can sleep during you 7 hours off.
But wait! According to the 3M Navy planned maintenance system you have a spot-check with the Captain in the middle of your 7 hours off. Too bad. But wait! The XO has recently been displeased with the cleanliness level of the ship, so as a result during sweepers all people not on watch have to be sweeping the passageway. Too bad. But wait! The berthing has been dirty lately so when your people are supposed to be sleeping they are being woken up by the cleaning. Too bad. But wait! Half the team is on watch, and conducting flight operations requires us to realign a vital system on the ship. Too bad, looks like the people who are supposed to be sleeping are going to be woken up. But wait! We have to have a division-wide meeting and training for reason X, Y, and Z. Ideally you would schedule this at watch turnover but if it's something involved we can have our watchstanders being distracted so just do it in your offtime.
I think the high operational requirements expose a culture/procedural/values problem of the shipboard Navy overall, it's just particular visible in 7th fleet because of the unsustainability of the workload.
Navigating with other ships in close proximity is pretty common -- mostly when transiting into port, out of port, and through shipping lanes.
It is pretty silly that they didn't seem to realize that the radar wasn't tuned correctly. I wasn't a surface watchstander so I can't comment on the radar aspect in more detail. Normally inputs are taken from a variety of sensors, not just one busted radar.
I spent 5+ years on a ship in 7th fleet and am all too familiar with what was described above.
I would attribute it to a few things. Mostly the over-extension of resources and people. The operational tempo in 7th fleet is absolutely ridiculous, so everything that isn't "mission accomplishment" gets pushed to the wayside. Training, making sure equipment is properly fixed.. our days were so jam packed full of bullshit that this important stuff suffered.
I considered myself lucky if I got 5 hours of unbroken sleep a night while at sea, and most of the people I worked with were the same way. Walking around functionally drunk doesn't lend itself to good problem solving skills. Do you know after these incidences there was massive effort to train people about the importance of sleep? Guess what, this mandatory training forced people to interrupt their sleep to attend.
All in all 7th fleet suffers badly from undermanning based on the operational requirements. Ask anybody. AMA I guess.