This happened to my phone, original battery but it had health around 81%. Installing public beta just dropped battery health to 0% and charge to 1% instantly, and 99% usage is suddenly credited to Settings. Charging does not work at all, and you have to restore from backup in DFU mode.
Readit Newsdz0ny commented on iOS 26 bricking phones (battery stuck at 1%, battery health at 0%) old.reddit.com/r/iphone/c... · Posted by u/dz0ny
dz0ny commented on Starlink is currently experiencing a service outage starlink.com/us... · Posted by u/throwmeaway222
https://radar.cloudflare.com/as14593?dateRange=1d shows a sharp drop in traffic, but no BGP changes before the drop. We can see BGP changes after the drop, so maybe some datacenter/control plane thing.
dz0ny commented on Former NTSB IG: Boeing 787 FADEC may have caused AirIndia crash sundayguardianlive.com/in... · Posted by u/dz0ny
The https://www.youtube.com/watch?v=CCFfibo9uR4 has interesting discussion about how FADEC had a bug in 2019 [https://avherald.com/h?article=4c2fe53a] and only five years later in 2024 [https://www.federalregister.gov/d/2024-21144/p-13] quote: The NPRM was prompted by incidents related to erroneous A/T behavior during a balked landing with the A/T engaged (FADEC), potential erroneous readings from the LRRA(radar altimeter), and possible deficiencies in low airspeed protections and crew alerting systems.
The only known fact is that both engines had shut down simultaneously, as confirmed by the Civil Aviation Minister. This either means a fuel problem or a software glitch; FADEC will not allow pilots to shut down engines in flight, but it has authority to do that on it's own.
Speculation: So you have a low-flying plane with electrical issues (blinking lights were reported by the survivor); it loses power after takeoff (survivor reported “plane hung in air”). RAM deploys and FADEC gets readings that are near the ground, it commands engine shutdown.
On Jun 29th 2025 India's Civil Aviation Minister said: "It has never happened that both engines shut down together." Investigators are analyzing the black boxes from every angle including engine issues, fuel supply problem or something else including sabotage. A preliminary report is to be expected in three months.
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
It was basically built so password manager extensions could communicate with password manager apps to do things like yubikey support etc. before browsers started handling webauthn
Oh wow, this is cool. Yep this would make USB Serial work on Firefox with a simple extension.
USB Serial is such a great thing, finally ending those annoying Electron apps that are only used for one thing. There’s a list of tools that now use the browser to set up devices, and it’s fantastic.
ESPHome(+ hundreds projects that use it as a base), Betaflight, ELRS, Flipper just to name a few.
I understand that WebKit lacks support since it’s developed by Apple, and I would also be cautious if it granted any access to peripherals.
But Firefox? Firefox has severely lacked support for hardware "connections" and has been unfriendly for developers for a long time, so I simply stopped using it (one of the reasons). Reason they state for not adding support it is that user consent is not enough to access the device, which is just nonsense, they could have made it enabled under the developer flag or similar. Blink proved that it can be made secure.
I have a filling they are stubborn for no reason and are not seeing use cases that would make their browser usable.
This is a issue that may also affect Airbus aircraft, but so far, it has only caused problems on two Boeing planes. Like MCAS, it was not disclosed to pilots, prompting the FAA to recommend design changes and notify flight crews.
https://simpleflying.com/boeing-cfm-international-update-737...