icedterminal

Think outside the box. Get a previous generation. Pixel 8 was about to be released. To move inventory, Google discounted the 7 series by like 30-40%. I got the 256GB 7 Pro for $600. Without the sale, $600 is the same price as the 128GB 7. I got a top of the range flagship phone for the cost of a midrange. My mom did something similar with a Samsung phone. She got an S20 when the S22 released. Huge discount when Verizon offered it for $449.

Exactly. The alias just points to the script which is executed.

I’m finding it hard to believe this statement.

System wide DNS over TLS (DoT) as it’s called “Private DNS” was introduced in Android 9. Which was released in 2018. I’d genuinely like to know what Android device today ships with 8 or older, or, ships with 9 and later but has it intentionally removed. If you’re still using an Android device running 8… Why?? It has not received security updates since 2021 and is officially unsupported.

iOS devices can import certificates to enable system wide DoT. This was introduced in iOS 14. Which was released in 2020. Given how Apple has a 7 year track record for device support, the oldest Apple device to get 14 was the iPhone 6. Which shipped with iOS 9 on release.

After the user mentioned it , I looked it up. It’s all over Apple’s supper threads. Hilariously, there’s an old reddit thread about it

https://discussions.apple.com/thread/253838180

https://superuser.com/questions/317900/eliminate-macbook-capslock-delay

https://www.reddit.com/r/macbook/comments/o6q52c/mba_m1_caps_lock_key_delay/

That’s even worse IMO. Lol.

macOS has a caps lock timeout? The fuck…

At one point they offered unlimited storage for Play Music only. You could literally upload your entire collection. They changed it later to consume your Drive storage. Cheap enough plans so I subscribed. Then they killed off Play Music. I’m still salty about that.

As of 2020, Chromium was made more permissive in accepting additional code. Before this, Chromium rejected a lot of outside code. Microsoft is now the biggest contributor outside of Google. Samsung, Intel, ARM and Apple are other notable contributors. There are several features found in the code that aren’t used by Google at all. Chrome is 100% Google’s agenda. Chromium does include Google services that Google rejects the removal of. Of course Google would rather you use them. Microsoft just removes them. As do others. But the features others have submitted to the Chromium code are of course used in their forks and possibly others. I would say Chromium is less of Google’s agenda than it used to be. As it’s not entirely neutral, there is still Google influence behind it.

If you’re interested at all:

Google Chrome is a fork of the open source Chromium with several Google proprietary features. Chromium uses the Blink engine. Blink is a fork of a large component of WebKit called WebCore. Apple primarily develops WebKit (and by proxy WebCore), itself being a fork of KHTML and KJS which were actually discontinued this year.

Alternatively, put it across a doorway. I did this to some devious children (6 and 12). They eventually got me back.

“VPN user voting is not allowed”

Lol.

When Knox is tripped it sets off the root check. Your banks misleading statement is due to their own confusion. Knox is no longer active so it can’t guarantee there is no root access. The OS basically says it’s untrusted/insecure due to lack of Knox and always says it’s rooted regardless of that actually being true. You can hide root for all apps that check. Do note that while you can return the functionality of third party apps, Samsung baked in apps can be hit or miss. It’s a game of cat and mouse. I speak from experience.

Additionally here are some other conversations about it:

https://forum.xda-developers.com/t/tripping-knox-and-banking-apps.4390167/#post-86279609

https://forum.xda-developers.com/t/knox-efuse-and-banking-apps.4565143/

Knox is used by Samsung own functions. Your bank app only does a root check. Which can easily be hidden with Magisk. If you trip Knox, you lose the Samsung exclusive security features baked into the OS. That’s it. Google Pay and USAA both complained about root access and refused to work with Magisk hiding off. With it on, they function as normal.

Integration into Knox requires enterprise device management and a custom app.