Typical roads are not effective firebreaks in dense, tall forests. The general rule is that you need 1.5X (minimum) to 3X the height of the surrounding vegetation. In a forest with 100-foot trees that means you need firebreaks 300 feet wide. In areas that are sloped or often windy, the width needs to be increased.

Hire that one. Proofreading AI output is quickly becoming the core skill a college grad requires.

never enter the US. Works great

Works great for all of us indeed.

Do be sure to take your phone to China with you, though. It just might heal your delusions about "multipolar world" and all that.

So any interaction with the Brownshirts of Fatherland Security?

That was true even before Germany's surplus WWI uniforms were distributed to adherents of a certain party...

IBM's instructions? Of course they said the licensed compiler is required :-)

Those are all part of gcc.

My guess is he read the first half of the first sentence of my response and concluded that I was just repeating what Google says about the issue, that I mindlessly believed the company line.

Never mind that I personally designed and implemented the feature, so if there's any official Google PR on the issue, it's based on what I told "them", not what "they" told me.

Thanks. There were good reasons to move on from Android, but it was pretty cool being able to work to improve the world's most-used operating system. Relatively small impacts get multiplied by a big number.

Also 100 miles from any international airport. This covers huge swathes of the country.

Atlanta, GA isn't US soil?

But even if this were one of the overseas CBP checkpoints (the ones that do pre-clearance, so you don't have to go through CBP after landing), I think those are considered US soil as well, under an agreement with the host nation.

Maybe. There are multiple SCOTUS rulings that basically declare border checkpoints to be a 4th amendment-free zone. If that means that the agents are "authorized to make such search or seizure", then 18USC2232(a) looks like a problem for him to me.

I was the TL for hardware-backed cryptography and associated bits. No, I didn't always follow every detail of what others on the large (hundreds of engineers by the time I left, though I was #13 on the team when I joined in 2014) team was doing. However, I do quite fully understand the context in which they were doing it. If you'd actually like to understand more about the thinking that likely underlay whatever you're talking about, please elaborate.

I do know about the planned requirement to require all app developers to identify themselves and pay a $25 fee if they want their apps to be installable via any route (sideload, third-party app store), indeed I even explained in my prior post why that benefits anti-malware efforts. I'm not aware of any 24-hour delay associated with it. If you weren't being such a pissy asshole about it, I might go google it, but you've burned pretty much all of my goodwill, so unless you care to actually explain what your problem is, I'm done here.

I think the most plausibly-deniable strategy is to put the phone into a state where it shows the OS setup wizard when powered on, making it look like you wiped it and powered it down just before going through the border checkpoint. Then to reactivate it you have to go through the "setup" process and when you get to the password configuration if you enter the correct password it unlocks and returns to normal. If not, it boots to an apparently freshly-setup state. I think this would be much easier to correctly simulate than an apparently in-use device.

Of course, the safest strategy is to actually wipe it and power it down before going through the border checkpoint, then restore from cloud backup after clearing the checkpoint.

better to not have that data on you when you cross certain borders

How about any border? Even more generally, at any situation, when the ordinary rights do not obtain...

Could you elaborate? What 24 hour delay?

What have "they" convinced me of?