There's nothing at all suspicious about the 172.16.0.0/12 address block.
Correct. However the 172.16.42.0/24 block is the default for a WiFi Pineapple. Any other range is usually ok, but the 42 on a /24 specifically would make me (and most people who actually know what a WiFi Pineapple is) avoid that network.
Do they all really? I know GrapheneOS does, and I think DivestOS even says "use my OS to stay as up to date as possible, but if you have a current/supported Pixel, use GrapheneOS instead for superior security." But I don't recall other OSes really going "we're more secure than GrapheneOS and here's why."
if used for work...Features? Don't care.
Most organizations care about maintaining document compatibility, especially formatting, and that usually means Office365. Microsoft is notorious for publishing a standard and then ignoring their own standard, making it exceedingly difficult to use other office suites.
I've heard OnlyOffice does the best at maintaining compatibility.
It's doomed to become a nazi bar...you can just go to an instance with admins you trust better or make your own instance
Ok, how is that different than Nostr? Don't like your Lemmy instance admins rolling against your Nazi views? Join a different instance. Nazi sympathetic instance gets defederated by everyone else? Make your own instance.
But generally I'm not a fan of the stuff I've heard and read about the Nostr protocol so far.
Can you elaborate?
That's the joke.
I'm hoping for a Pixel Tablet 2 with this (Pixel Tablet doesn't have it, but the Pixel 8 does for some reason) and MTE security capability, and I'll transition to that with GrapheneOS over a laptop.
I haven't tested it personally, but I think GrapheneOS (easily the best Android OS for Pixels, in my opinion) has had it for Pixel 8s since the end of October 2023. Here's a quick guide I saw: https://discuss.grapheneos.org/d/9775-pixel-8-desktop-mode-guide-and-personal-experience
Other than Google pay...
Google Pay's Tap to Pay does not work on GrapheneOS.
Just did a super quick glance, but are you really considering QKSMS maintained?
Startpage, which is still recommended over at privacyguides.org
For now. There is an open pull request to remove it due to Startpage fingerprinting users (I didn't delve into it to see if it's true, but that was the reason given). And just because it's been suggested doesn't mean it will be removed, so time will till.
https://github.com/privacyguides/privacyguides.org/pull/2577
New Donation/IAP has missing background. Looks like it should have a background, but doesn't, so some words are on top of each other. This is on light mode, whereas dark mode doesn't have this issue.
v1.23.1
Edit: v1.23.2 fixes this.
Sure, it's one of many, but how often do you see ithay specific (42) block used? I honestly don't think I ever, outside of a pentest lab. The 172.16.42.0/24 (not just any 172.16 like you're saying) block is the default for a WiFi Pineapple. Any other range is usually ok, but the 42 on a /24 granting WAN access specifically would make me (and most people who actually know what a WiFi Pineapple is) avoid that network.
You clearly don't know what a WiFi Pineapple is, because we're zeroing in on the 42 and you liken it to the entire 172.16 block. And linking every .xyz domain to a specific block (42) that is used by default for a pentest device is even more misleading.