undefined | Better HN

0 pointsilliac7861mo ago0 comments

You are assuming it will not be possible to add support to other OS. Why?

What would be “knowing it can work on grapheneOS” for example, in your view?

0 comments

subscribed1mo ago

It will be possible but simply won't be done.

And as of now it won't work on GrapheneOS, it doesn't pass anything except MEETS_BASIC_INTEGRITY

illiac786OP1mo ago

That’s not what the parent wrote though.

And why is it so bad that they start with a smaller subset of feature and target the 99% of the population using either google or apple?

subscribed1mo ago

This is a misleading way to put it.

Re: Android.

Goggle can supports AOSP attestation like any other vendor who wants to support it. They invented it.

So instead of immediately locking down everyone using android to ONLY Google-dependent method, I'd developers could go the vendor agnostic way, but consciously decided not to.

It's untrue to claim that supporting AOSP attestation only serves GrapheneOS and leaves out everyone using Google-surveiled handset.

Nb, mixing it up with Apple is a conscious way to further the false claim, and I believe it's not accidental since these ecosystems are naturally completely separate.

illiac786OP1mo ago

You are misleading in fact, you use terms such as:

“it won’t work on GrapheneOS” “locking down everyone using android to ONLY Google-dependent method”

which make it sound like it’s a permanent and definitive limitation.

It is not, they can add support later, as they stated already.

> It's untrue to claim that supporting AOSP attestation only serves GrapheneOS and leaves out everyone using Google-surveiled handset.

hmmm, what do you have in mind? Publish it to F-Droid but not to the google app store?

1 more reply

j / k navigate · click thread line to collapse

0 comments

subscribed1mo ago

It will be possible but simply won't be done.

And as of now it won't work on GrapheneOS, it doesn't pass anything except MEETS_BASIC_INTEGRITY

illiac786OP1mo ago

That’s not what the parent wrote though.

And why is it so bad that they start with a smaller subset of feature and target the 99% of the population using either google or apple?

subscribed1mo ago

This is a misleading way to put it.

Re: Android.

Goggle can supports AOSP attestation like any other vendor who wants to support it. They invented it.

So instead of immediately locking down everyone using android to ONLY Google-dependent method, I'd developers could go the vendor agnostic way, but consciously decided not to.

It's untrue to claim that supporting AOSP attestation only serves GrapheneOS and leaves out everyone using Google-surveiled handset.

Nb, mixing it up with Apple is a conscious way to further the false claim, and I believe it's not accidental since these ecosystems are naturally completely separate.

illiac786OP1mo ago

You are misleading in fact, you use terms such as:

“it won’t work on GrapheneOS” “locking down everyone using android to ONLY Google-dependent method”

which make it sound like it’s a permanent and definitive limitation.

It is not, they can add support later, as they stated already.

> It's untrue to claim that supporting AOSP attestation only serves GrapheneOS and leaves out everyone using Google-surveiled handset.

hmmm, what do you have in mind? Publish it to F-Droid but not to the google app store?

1 more reply

j / k navigate · click thread line to collapse