A practical approach to Privacy and Security
Joined July 2022
- Tweets150
- Following0
- Followers742
- Likes44
with even BASIC_INTEGRITY, let alone DEVICE_INTEGRITY or STRONG_INTEGRITY.
github.com/microg/GmsCore/is…
Oh, so now you have moved from just LineageOS with MicroG to needing to root to mess with Play Integrity, as if that is somehow better than just using Sandboxed Play Services.
This is not to mention the fact that there is an active issue where MicroG itself is having trouble...
> Make up quotes that do not exist
> Lie about everything possible
> Shifting the goal post
"You can't read"
What does this have to do with Google being "baked in" on stock Android? Why are you shifting the goal post now?
Play Services on GrapheneOS is optional and sandboxed. You made up claims that it has issues with X then shilled an alternative that is not any better if not worse.
> Its not up to X to fix an issue on users who making up probably less than 0.1% of the android world.
It is their choice to enforce the Play Integrity check.
> lineage *with* microG
Does not pass Play Integrity check in the same manner.
> Could I tell you why?
You made it up
> different than your own opinions
Oh, so an objective argument over app compatibility is an opinion now? Whether X works on GrapheneOS is an opinion and not a fact?
It's good that you "left" - people who make shit up and phrase it as "an opinion" do not belong here.
Using that as an excuse to claim that it is a problem on GrapheneOS that they need to "fix" instead of X's problem is disingenuous.
Using X's problem which also affects LineageOS to shill LineageOS and trash talk GrapheneOS is even more disingenous. 🤡
Actual quote:
> You're on X. You won't be able to use X on a graphene phone.
Date of post: May 25, 2026
> X wasn't working for login
There was a brief moment where X blocked logins because of Play Integrity, which would have affected LineageOS with MicroG in the same way.
> I strictly give feedback based on personal experience.
Doesn't seem like you have any "experience" at all when you just make everything up?
> They won't work to fix it
What is there to fix when X already works fine on GrapheneOS? 🤡
> None of my "nonsense" is "made up."
Claiming X doesn't work on GrapheneOS when it works just fine.
> tech industry for 15+
Is it actually 15 years of experience or just 1 year of dunning kruger effect repeated 15 times?
> Graphene "enhances" thermal issues
What?
That's fine. Just don't fall for whatever nonsense the @TechX1320 guy is saying.
He has some kind of ulterior motive and just spams any post mentioning GOS he can find with made up nonsenses like this.
> I was referring to having a desktop with hardware level stuff disabled
What?
> they absolutely are a backdoor though
Prove it. Just because you do not know how AMT works doesn't mean it's a backdoor.
> phones are out of the question when it comes to privacy
???
What on planet earth are you talking about? Are you using an LLM to generate text?
Desktop environments have nothing to do with the ME/PSP, and neither are a backdoor. Neither are the stuff with IMEI / IMSI.
PrivSec retweeted
It is actually possible to use Cloudflare Pages and DNS without CF messing with your CAA records.
The first step is to disable BOTH Universal SSL and AMP. If either is enabled, Cloudflare will override the CAA records for your apex.
Verify that your records are correct:
This is not to mention - on any normal device, RCS works through Google Messages, and you call that "cutting edge security". But on GrapheneOS, when RCS works through Google Messages, it suddenly becomes a problem? How much mental acrobat can you do?
If you are going to make a claim, do the bare minimum to prove it. If you can't, then stop making stuff up and pretending to be an expert.
In fact, this isn't far off of how you got caught backdooring your own "E2EE" services, because it is completely trivial to show that you...
Here is a clear instance of you saying complete and utter nonsense.
For one, it doesn't actually reveal an identity. Two, attestation doesn't inherently mean that it is to prevent users from running "unmodified Google Android", whatever that means. It can be used to verify...