using a cookie that is essential for non-essential purposes, is not allowed. So using a load-balancer cookie is fine, as long as it's only used for load balancing.
Once it's used for other (technically non-essential) needs as well, one needs to find another basis for processing or ask permission for that second purpose(consent basis).
Also, if the LB cookie can be non-identifying, while fullfilling the stated technical purpose, it must not allow identifying users. So for LB cookies, one must not use a unique ID per user, but an LB ID instead. Something like "node1", "node2" etc...
When the permission is withdrawn, the other party cannot collect more data. And the existing data that they collected would need to be deleted if the user asks them to. If the withdrawal of permission also involves permissions regarding data storage and processing, it would mean that the company would need to destroy any personal data that they have.
If withdrawing is meant to be “undo consent”, how would you make that as easy as the initial “one click to consent”? Would you not have to show a banner on every page view, with a one click option to “withdraw”?
You'll have to go and ask the legislators what they were imagining. Thankfully it's not being interpreted quite as literally. Sometimes pragmatism saves the day.
Pixel 5 is "small" in android parlance, but still bigger than the Pixel 4a for instance, which is already slightly bigger than the SE.
I think parent could have been fine with a Pixel 4a if it wasn't for it starting to age (using the lastest OS on it, feels definitely slower at times , especially when starting the camera which is a bummer)
I was adding info on how app use in it is when the edit-window closed...
Most apps are actually fine, if a bit cramped. The exception is dialogs. I usually have to scroll to see all options. You get used to it, but it isn't great.
Webpages are alright, but I do occasionally need to hide the keyboard while filling out forms to see feedback provided below the input (e.g. username already taken, passwords don't match, invalid CC #).
I've never really gamed on my phones, so can't speak there.
The one thing I did with a larger phone that I don't do on my Jelly2 is read things like textbooks and comics where images and text need to be laid out like print. It's too small to fit a whole page of legible text and images at once. 720 horizontal pixels and a 5" screen is the minimum there IMO, though really this is what e-ink tablets were made for.
Does it run a non-Google/free OS? My primary qualm about switching to a budget Android phone from an iPhone is the security and privacy aspect, which seems okay under Apple but atrocious under Google/Android.
I think the Samsung Galaxy S10e and some of the Google Pixel models are nearly hand-size, but I don't know of any that rival the (now unsupported) Xperia XZ1 Compact. The XZ2 Compact is (AFAIK) still supported by LineageOS, but it's chunky.
I have read rumors that a new Xperia Compact model is likely within the next year. I don't want to get my hopes up too high, because this is unconfirmed and because the definition of "compact" seems to be expanding over the years, but I am optimistic.
I doubt that we'll ever see the likes of the Xperia Mini Pro again.
Nearly impossible, and I'm saying this as a lifetime Android user.
Your best bet would be boutique OEMs like Unihertz, who have a 3.1-inch Jelly phone (underpowered) and a Blackberry style Titan Pocket with a hardware keyboard and 4-inch screen.
Neither of these sound like what you want. In the Android world, one can only hope that another small-time OEM will swoop in to fill the gap, before inevitably disappearing.
Since pocketability is a large component of the size question, the foldable Motorola Android phone is worth taking looking at (if you can afford it). Unfolded it's modern-sized but folded up it fits in more places.
It's the other way around for me. Usability trumps everything. Trying to use my phone one-handed is extremely frustrating, even with a rear grip, and I have what is considered a "small" phone (Samsung Galaxy S10e).
I wish phones had thumb trackpads like BlackBerry phones had. The BlackBerry Classic (2014) had one and it worked incredibly well, even in Android apps, surprisingly (it works by moving the focus, not a mouse pointer, except in the browser, where the pointer means desktop mode is actually usable). Being able to reach the entire screen just by twitching your thumb a few millimetres is sadly probably never going to be possible again.
I used to use a Motorola phone I got off Amazon for like $200. It was great, but various factors have caused me to return to using an iPhone. Looking online a bit maybe it was the G7 plus?
My favorite "feature" of these Android phones is the price. It's like having insurance on your phone. If you lose or break it, it's not $1500 down the tubes.
> My favorite "feature" of these Android phones is the price
Honestly that's my favorite feature of iPhones too. I've always bought used iPhones 2-3 generations behind. And they're often supported for many years.
Current iPhone is 1st generation SE 2016, probably worth less than $80 and runs latest iOS.
I’ve usually bought 1-2 generations behind, often at the $250-400 price point, and then run them for 3-4 years or so. I just replaced the battery on my wife’s X and that looks like it’ll now go well past the 4 year mark.
Having spent a good amount of time looking at potential JavaScript malware that ended up being repackaged GTM, I'm pretty confident anyone who says they're "blocking Google Tag Manager" has their head in the sand.
Atleast in my country, to send legitimate marketing e-mails, a user has to be given a choice to opt-out *before* the first e-mail.
So it's not enough to allow them to opt-out with an e-mail exchange or an unsubscribe link, you must allow the user to opt out when you initially gather the contact information.
If that wasn't done, it's illegal (and unethical) to send marketing e-mails, even from a paid service.
