shiftenter
- 6 Posts
- 35 Comments
I think they said there weren’t any ex-Twitter employees working on Threads.
I’m calling for a Lemmy blackout until the bean content returns!
1·1 year agoNearly agree with everything you said.
But maybe Reddit is okay with a few 3rd party apps surviving if it means they can charge such a ridiculous premium on API requests. Perhaps they didn’t think any dev would be crazy enough to take them up on their offer. But at that point, they’re raking in so much money that they might not care those users are on a 3rd party app.
2·1 year agoYeah, Millennial here as well. I was lucky enough to have been able to pay off my loans. But I’m still pissed at the decision.
I hope Gen Z never forgets this.
That concept is already used regularly for training. Check out Generative adversarial network.
Yeah, I’ve read how experts stated that the point where the dissimilar materials meet would be the most likely location of the failure. Titanium and carbon fiber will certainly behave differently under that pressure.
I think it’s far less likely to be the root cause, but I do wonder if the 380mm acrylic viewport had anything to do with the failure. It wasn’t rated for anywhere near that depth.
At the meeting Lochridge discovered why he had been denied access to the viewport information from the Engineering department—the viewport at the forward of the submersible was only built to a certified pressure of 1,300 meters, although OceanGate intended to take passengers down to depths of 4,000 meters. Lochridge learned that the viewport manufacturer would only certify to a depth of 1,300 meters due to experimental design of the viewport supplied by OceanGate, which was out of the Pressure Vessels for Human Occupancy (“PVHO”) standards. OceanGate refused to pay for the manufacturer to build a viewport that would meet the required depth of 4,000 meters.
12·1 year agoI remember the art of crafting the perfect google search query and knowing you’d eventually find that obscure bit of info. Now I have to quote nearly everything in my query and if a single result in the first 100 results is tangentially related, I’m grateful.
01·1 year agoSo much floof, so little time!
Not the same thing, but an older site/service where they would just randomize various automated responses during gaps in the conversation to keep the person on the phone. They have a bunch of recordings.
8·1 year agoI think this would be considered Self-serving bias.
4·1 year agoHe specifically stated he didn’t want to hire older and experienced employees.
If y’all haven’t seen Louis Rossmann’s video on this topic, it’s a good and simplified explanation of why this is happening.
Just saw what the AP reported:
The Navy went back and analyzed its acoustic data after the Titan submersible was reported missing Sunday. That anomaly was ‘consistent with an implosion or explosion in the general vicinity of where the Titan submersible was operating when communications were lost,’ according to the senior Navy official. The official spoke on condition of anonymity to discuss a sensitive acoustic detection system. The Navy passed on the information to the Coast Guard, which continued its search.
Seems like a more accurate analysis.
I’m guessing it was just a coincidence between the 96 hour mark and when the capable ROVs finally arrived on site. They deployed the ROV that discovered the debris in the early AM today. Based on the fact that info was already leaking prior to the coast guard announcement, it was probably known for several hours before being made public.
Edit: Yeah, they probably had reasonable suspicion that the sub was gone. But until they had evidence, continuing search and rescue seems like the prudent thing to do.
Yeah, I thought that was confusing as well. I’d be shocked if the navy wasn’t always recording. If the point of the system is defense, I’m sure it’s not down to Frank to flip the switch on when they think there’s going to be an attack.
Maybe by “listening” they meant reviewing the recorded data around that time?
Down to about 30 hours now.
I bought a 13" SurfaceBook 2 with the official Microsoft dock when it came out. I figured buying hardware from the company that makes the software would’ve given me the best experience.
After beginning to use the machine, I discovered that Microsoft’s own dock can’t even keep the machine powered under heavy load. The battery was discharging WHILE PLUGGED INTO THE WALL. I had to take breaks so that my computer wouldn’t shut down and could recharge.
I had been on Macs for years but decided to give MS a chance because Windows Subsystem for Linux looked pretty awesome. Needless to say, I’m back on a Mac.