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.
if they can’t do what the board needs… They aren’t a good fit either
But does the board need it, or just want it to maximize profits, like boards usually do in their typical chase of infinite growth that isn’t sustainable?
And if the person won’t stick up for what they think is best for the company and the people (which they’ve deemed firing 50 people is that), maybe they’re not a good fit that way. But hey, they are sticking up for said company and 50 people, so maybe they are.
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?
and Signal were Google proprietary.
I’m pretty sure Signal is not Google proprietary, and the person you replied to didn’t say it was.
Yeah billy should be build IUDs not 3d printed guns
I see the /s but…The Ukraine war videos don’t show how to build IEDs, though. And even if they did, who would the parents sue? Ukraine, a nation at war? As opposed to 3D printed guns show you how to make them, and you could try to sue the gun company who it belongs to. And YouTube in both cases.
we didn’t do a good job transitioning from religious to secular values in that way.
A lot of religions were founded on and/or expanded by violence (Pilgrims to America, Knights Templar, Spanish Inquisition, etc), so I don’t remotely think “religious to secular” is the reason.
Other than Google pay…
Google Pay’s Tap to Pay does not work on GrapheneOS.
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
So is bullshitting. More so, only human minds can bullshit.
And a bull’s anus.
Unfortunately the fact that NFC can’t be used on anything that’s rooted anymore is kind of a deal breaker.
NFC can be used on GOS, and they frown on rooting.
If I could use google pay and my normal banking apps with GrapheneOS I would switch to it today.
It’s due to PlayIntegrity API wanting a “Google certified OS,” which is ironically less secure than hardware attestation that GOS supports. I doubt Google would change their model, but your bank might. Some banks do support GOS, and they have changed at the request of their customers before. Send them the GOS documentation and you might get lucky.
https://grapheneos.org/articles/attestation-compatibility-guide
We need hardware requirements so that not just pixel phones can get grapheneOS.
GOS has strict hardware requirements to increase security that currently only Pixels meet. They won’t, and shouldn’t, compromise their standards which would give you a weaker OS. Want GOS on other vendors? Convince those vendors to up their hardware game.
Sounds to me like you need an upgrade. I tried Jerboa, but it felt like it always lagged behind or was buggy for some reason. Then I switched to Voyager, which gets constant updates. Also, it’s a PWA, so I don’t need an app and it can thus be used on mobile, tablet, desktop, etc. Not to mention the theming is one of the best, in my opinion.
The ending period? Not for me on Voyager.
Pixel 8 Pro. Google’s current flagship device, arguably the most secure device on the market, and is first to include Memory Tagging Extension (MTE). As such, it is supported by GrapheneOS, which I highly recommend due to the increased security and control over your own phone (starting with sandboxing the Play Store if you use it, and not giving Google full system privileges like stock/OEM OS does).
When fully integrated into the compiler and each heap allocator, MTE enforces a form of memory safety. It detects memory corruption as it happens. 4 bit tags limit it to probabilistic detection for the general case, but deterministic guarantees are possible via reserving tags.
In hardened_malloc, we deterministically prevent sequential overflows by excluding adjacent tags. We exclude a tag reserved for free tag and the previous tag used for the previous allocation in the slot to help with use-after-free detection alongside FIFO and random quarantines.
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.”