I'd imagine you can triangulate the sound with an array of sonar buoys if it is on the same ocean layer?
Edit: commented before reading the article. That's exactly what they're planning. 🤦♂️
I'd imagine you can triangulate the sound with an array of sonar buoys if it is on the same ocean layer?
Edit: commented before reading the article. That's exactly what they're planning. 🤦♂️
I seriously can't believe they don't have at least an EPIRB. If they had one, the entire "they might be on the surface" idea could pretty much be ruled out.
Are you on mobile by chance? It happens to me too, but only on mobile. I noticed it worked as expected when I was on desktop earlier today.
I might be in the minority here, but I feel this is actually a step back.
In the 5 years I've had my phone, there have been two times I've ever really needed to pull the battery, and still the hard reset sequence still eventually worked in both cases.
Anyone remember how some phones had issues with the battery door becoming somewhat loose over time, causing any slight bump to turn the phone off? Many have already commented on how they explode into multiple pieces when dropped. Traditionally the battery covers are incredibly flimsy plastic, even on flagship devices (cough Samsung). Waterproofing is a common concern too, however it actually can be done with a removable battery (e.g. Galaxy S5).
What really needed to be addressed here was how cumbersome it is to get into these devices to replace the battery, and how often people are price gouged to replace them. I believe this could have been better written to allow for either a removable battery, or a standardized and affordable built-in battery replacement process.
Yeesh I hope not.
Yeah, I'm probably going to bite the bullet and start working on Kbin too. I've avoided PHP for my entire career just by chance, so all I know are the memes and what I've read of (usually older) codebases. From what everyone says, modern PHP isn't really that bad, and from what I can tell when perusing the Kbin source, the implementation is pretty clean.
This exactly. I'm a software engineer and I'm itching to contribute to one of these systems, but I do not agree with some of the stuff I've seen posted by one of the developers of Lemmy. It just leaves a sour taste in my mouth about the whole thing.
One of the things I'm really enjoying about this jump to the fediverse is watching everyone try things to get a better understanding. Gives me first telephone call vibes. Lots of "does this work?" "HEY it does work!"
These are garbage collected languages and come with the overhead of such a process. Rust has no GC process and instead relies on reference counters to statically track live memory.
That's interesting. What happens if a lemmy user replies to a beehaw user's comment from a lemmy instance? Does the beehaw user just never see it?
This makes sense. The only thing I put spinning disk storage in anymore are large storage arrays where part of the overall goal is to keep the disks cheap.
Guess I won't bother after all.