GrapheneOS on Nostr: nprofile1q…yc807 nprofile1q…mrhum Anyway, that's only the current format used by ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqry8and0vr5kq6m4nxwd4tswquef8k80k9fca0am0rt7tgxtdj9aqryc807 (nprofile…c807) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq9dxzvzpewcce5zkqtupqqypju4y2p5je6k7zq6wzme7gnkv0ja4smmrhum (nprofile…rhum)
Anyway, that's only the current format used by the stock Pixel OS. They have regularly changed the values of both fields over the years. It would be completely incorrect to hard-wire expecting specific values in any of these fields. Google can do that for the Play Integrity API because each build has data uploaded before release. Others are in no position to do anything like that. We know they blocked GrapheneOS specifically, likely through an SDK which did it.
Anyway, that's only the current format used by the stock Pixel OS. They have regularly changed the values of both fields over the years. It would be completely incorrect to hard-wire expecting specific values in any of these fields. Google can do that for the Play Integrity API because each build has data uploaded before release. Others are in no position to do anything like that. We know they blocked GrapheneOS specifically, likely through an SDK which did it.