Posts by [email protected] | |
Post #AuSZhZp1sNnN4pajAG by [email protected] | |
0 likes, 1 repeats | |
@sukiletxe @fireborn If you want to read GrapheneOS's side, you should read… | |
Post #AuSafRPsG1HMNkN3JI by [email protected] | |
0 likes, 1 repeats | |
@alisynthesis The project has responded with this thread explaining things from… | |
Post #AuSatjrqSA6Bf4Gtuq by [email protected] | |
0 likes, 1 repeats | |
@midtsveen See the project's response here: https://grapheneos.social/@Grap… | |
Post #AuSbEJT9nQWls0XCaW by [email protected] | |
0 likes, 1 repeats | |
@schrotthaufen You should see the project's response here before making a d… | |
Post #AuSf73DIEibdF7uI6q by [email protected] | |
0 likes, 1 repeats | |
@jonathonbarton I'd suggest reading the project's response here: https:… | |
Post #AwGgVElIoO9lfVQI1w by [email protected] | |
0 likes, 1 repeats | |
@gael @GrapheneOS It is kind of ironic to use that as an example of keeping you… | |
Post #AwGjV5vJyLw47RjUwK by [email protected] | |
0 likes, 1 repeats | |
@karazicos @gael @GrapheneOS keep in mind that GrapheneOS was only responding t… |