Firebase seems to suffer a similar problem of people not setting permissions right. The only major difference is that they seem to steer devs pretty aggressively to Google auth which won't leak password hashes.
While in theory your API can be the database it seems like a footgun for the inexperienced and AI.
AFAIK the C implementation is a kernel module that's not shipped in stock Android releases. The WireGuard Android app uses that module when available, but otherwise uses wireguard-go.
Good knowledge here, was unaware of this feature of the app. Would there be any case of the app defaulting to the wireguard kernel module if it's not included by any OEM Android release? I would assume that means most users are actually running wireguard-go.
I think your carrier hasn't approved it yet. T-mobile seems to lag on these things. I also can't seem to find a system update. A Google Play system update does seem to exist
We have an OS security update that is only release to users of a specific hardware, once approved by their mobile operator. It may be added to vendor-specific OS versions some time later (weeks, month or never). The vendor-specific may not be approved by a telco if the vendor doesn't have a relationship with that telco.
Now think that millions of people use the same OS on many different flavours, on different hardware, on multiple operators.
Is this true for updates that might affect the way it interacts with the network (eg baseband firmware updates)? I assume it's much easier for iPhones to decouple that layer from the rest of the OS, which isn't the case for Android/Linux.
Nope. When a new iOS update comes out, all supported devices may immediately install the update if they seek it out. Or it will usually auto update on its own, or at least nag the user to update.
It’s gotten slightly more confusing with the major updates now being optional. You get a choice between getting a feature update or just security patches. Unless I missed it, my phone never really asked me to update to the latest iOS 26. But I can, it’s there. I’m instead on the latest version of iOS 18. (They changed number schemes. 18 is last years major update)
Apple also does security updates for quite a long time. iOS 15, from 2021, got a security patch in September of this year, and works on the iPhone 6s from 2015.
No you can't. That study is comparing past estimates of the past and present to the lived in past and present not past estimates of the future to current estimates of the future.
Okay, but why then do the IPCC reports of the past present vastly different historical data than the present ones? History cannot change, but people can "reinterpret" it for political purposes.
Humans didn't exist since the beginning of time, and we only started to properly record temperatures in the last few centuries. That means we have to determine historical data through the effects it had on our planet. The methods to find this historical data from the effects keep changing and evolving, so it makes complete sense to me that historical data has changed throughout the reports.
Unfortunately you didn't specify where one can find this "vastly different historical data", so I can't get more specific than this.
When I was a child the front side displays on new Muni buses used to use these probably solonoid driven LED arrays. If you sat under one you could here this clattering sound that sounded kinda like rain each time the display changed. This discussion is bringing back old memories of those.
They certainly did. The SFMTA also showed these to me and explained that not only were they extremely temperamental, but it also cost about $3k to print one of the curtains with the special barcode that prompts the curtains to rotate.
The signs made quite a racket, but so did the buses (well, the first model I linked to).
Fun fact: When Muni first rolled out the digital signs on their newer Bredas the set the signs to rotate through three different pieces of information. So for 2/3 of the time you had no indication of where the train was headed.
Bonus fun fact: the cloth rolls have a variety of routes and destinations that never came to be.
When I was a kid, DART (a not-quite-metro rapid transit thing in Dublin) trains had printed maps with LEDs for each station; they were green until the train passed them, then turned red. This seemed like absolute magic to me at the time.
When a branch line was added, these displays were updated, though they weren’t put in the newer rolling stock. Then another station was opened on the existing line, and they just switched them off. They’re still present on some trains, but haven’t done anything in 15 years. They’ll finally presumably go away in the next year or so, as the ‘80s rolling stock they’re found in is due to be retired. I’ll kind of miss them.
My general experience with Waymos and safety is that while they are generally quite safe and communicative drivers (They have a pedestrian yeild indicator that should be required by law) they tend to create safety issues because people drive stupidly around them. A lot of SF drivers seem to see them, think I know better, and then proceed to do something dumb.
I'm not really sure how to fix this problem.
Also if any Waymo engineers are reading this please make the pedestrian yeild indicator icon visible on the front of the LIDAR. In narrow streets the front is much more visible to pedestrians than the sides as the LIDAR is pretty far back on the car.
North Korean state media (KCNA) used to use post requests for everything breaking hyperlinks and bookmarks in the process. I suspect this was to deliberately ensure a sort of memory hole process for everything that they had said in the past.
While in theory your API can be the database it seems like a footgun for the inexperienced and AI.
reply