Change the region. Not time and date, that can be blocked by screentime. Change the region. Sometimes takes multiple attempts but it does work. I had to pay a bug bounty to my child to get them to tell me how they did it
That's true. I came off too dismissive. I like the advice, I was just disagreeing with:
> it’s clear to me why they rarely work: ...
and
> boring old discipline is much more sustainable approach
I like the idea of trying a more holistic approach, but grayscale doesn't have to contradict with that. Some people (myself included) can use grayscale as a tool alongside other things.
100%. This person is a very specific anti-* hater, for something that was such a rampantly popular hatred 10 years ago. But the FUDites rarely bother with bona-fides, with real argument.
We should feel bad for them, those decoupled folks who needs help. It's sad pathetic and remarkable how these weird software enmities crop up, are let to grow and never addressed. Their time of their outrage being popular & hip fades but the disdain-without-argument sticks around.
Thankfully container hatred is a pretty tiny frakking force, of very disparate widely scattered eccentrics these days. But there's so many weird FUD proclivities folks can opt into, can find to stoke their lifelong hatreds against. Theres just so few warnings: such audience acuity is required to parse, realize the windmill tilting, & move along.
That isn't a bug; it's working as intended. I do wonder if that could be mocked up easily in html to see what it feels like though. Sounds like a cool idea
I'd believe it. Not sure when this is, but if it's a few years old and business software, they could probably asume everyone uses java, which doesn't even have unsigned integers.
True, but it does seem like the best alternative here. If it's a SOAP API in 2005 for business customers, for example, then it sounds like the least bad option of the four (tell consumers to update, hold up the whole company's deployment, push negative ints, or push longs). I'm just saying that to me, it isn't hard to believe this was the best option here.
One interesting aspect of this is that when using a personal Android with a work profile, developer options and ADB is (or at least can be) disabled. BYOD will then imply you can't sideload at all.
And nothing of value was lost. BYOD means Corporate can push whatever spyware they want onto your personal phone. I tell any employer I work for, if you really need me to be reachable by phone via an app, you can supply me a work phone. Otherwise I'll do without. I keep a bright-line distinction between personal devices and work devices, and never mix the two. My boss knows this explicitly.
That's great for you, but not everyone has the ability to do that. Android has a massive markershare. What are the odds that all of them can force their employer to get them a new phone?
Maybe that's something employers shouldn't do, but that doesn't change the fact that it's a reality and google is overstepping with this change.
Please. This is an event up there with Sony taking Other OS away: tinkering nerds and pirates most affected, the vast majority of consumers won't even notice. I don't think it reaches that level of impact. And I think most Android devs working professionally already have developer accounts, or their employers have one, and are already verified.
That's what this really is about. If you want to distribute Android apps, be a professional or at least act like one. Take accountability for what you produce, under your real government name.
Do you see the direction they're heading? They're now making it so maybe .5% of android users know how to sideload. They're clearly chipping away at it, even though they might not be making all the changes at once.
What fraction of users do you think have a legitimate need to sideload apps on Android? I would imagine it's much less than 0.5%. Developers and technically-minded power users must be a tiny minority amongst Android users given that it has an install base in the billions.
Right now, not many. My point is that they aren't flipping a giant switch from an open platform to a closed platform. They're boiling the frog -- slowly removing features until all choice is gone.
A few more years in this direction and Android can be as locked down as iPhone before Apple was forced to allow sideloading
reply