Since this is on Android, this policy should only apply to the version of the Messages app within the work profile, right? If it didn't and could access personal messages, that would be crossing a line.
Reading the post makes it sound like this only happens on managed devices; whether that means "owned and provided by work", "within the confines of the work profile on a BYOD devices", or both, I'm not 100% sure.
I had a very different reaction to this, because I just released a Rust library called ironbeam [0] without knowing anything about this. It was intended to be a pun on Apache Beam and the fact that iron can rust... I guess I'll have to live with it for now because it's way too high-effort to rename it after a stable release.
ah, thanks, good to know.. but does that make it optional? I kind of like how ocaml requires a letrec annotation on any recursive definition and I don't know when you wouldn't want to add tailrec
From PCB perspective, LPDDR5(X) interface is quite different from regular DDR5. Same with DDR4 and LPDDR4. Source: have designed few boards with different memory interfaces.
Any tier of Google Support is 100% a black hole. I had an extremely unusual issue with a service in Google Cloud, tried to debug it and failed. I filed a ticket and waited because P1 was only for “production” issues, but our issue was for development.
A few days later, the Google engineer assigned notes to us that we can escalate to P1 if this is blocking our workflow, even when not in production. I take this to my manager and they agree that it’s time to move it to P1.
We move it to P1 and immediately get traction, only to be stonewalled by a support engineer confidently asserting that the code throwing the error, which only existed in a private Google-maintained container, which only interfaced with our app through launching a cloud job through their platform, was actually our responsibility.
No joke, they actually said “As stated in my prior message, this issue is due to your code”, despite our code being a thin wrapper around their demonstration code to run it from the command line.
In my most business professional tone, I tell them off for lying to us about them debugging on their end and inform them that I will be immediately escalating because of this dissatisfactory response. This finally gets the ticket moving and a few weeks later, a bug fixed version of the entire platform is deployed.
Total time from start to finish:
- P2: 2.5 weeks of daily updates
- P1, until we’re told that it’s our fault: 8 hours
- P1 escalated until issue was completely fixed: 5 weeks
We paid for premium support. I cannot imagine how bad free support is.
Reading the post makes it sound like this only happens on managed devices; whether that means "owned and provided by work", "within the confines of the work profile on a BYOD devices", or both, I'm not 100% sure.
reply