Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://social.sanfranciscan.org/objects/c6db431e-da1c-41b3-8f7f-a9e9a3d96673">Chema Hernández Gil :sf: (chema@social.sanfranciscan.org)'s status on Thursday, 17-Apr-2025 12:14:09 JST</a><a href="https://social.sanfranciscan.org/users/chema" title="chema@social.sanfranciscan.org"><img src="https://gnusocial.jp/avatar/29088-48-20221117050844.webp" width="48" height="48" alt="Chema Hernández Gil :sf:" style="position: absolute; left: 0; top: 0;">Chema Hernández Gil :sf:</a><div><ul><li></ul></div></section><article>Back in January, <a href="https://social.sanfranciscan.org/tag/google" rel="tag">#Google</a> pushed an update that broke my working <a href="https://social.sanfranciscan.org/tag/pixel" rel="tag">#Pixel</a> 4a. Support failed. I didn't upgrade. I switched to <a href="https://grapheneos.social/@GrapheneOS">@GrapheneOS</a> <br><br>Here's my experience.<br><br><a href="https://blog.sanfranciscan.org/2025/04/16/If-Google-Can-Break-My-Pixel-They-Can-Break-Yours/">https://blog.sanfranciscan.org/2025/04/16/If-Google-Can-Break-My-Pixel-They-Can-Break-Yours/</a><br><br><a href="https://social.sanfranciscan.org/tag/technology" rel="tag">#technology</a> <a href="https://social.sanfranciscan.org/tag/privacy" rel="tag">#privacy</a> <a href="https://social.sanfranciscan.org/tag/smartphone" rel="tag">#smartphone</a> <a href="https://social.sanfranciscan.org/tag/android" rel="tag">#Android</a></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4907234#notice-9613718">In conversation</a><time datetime="2025-04-17T12:14:09+09:00" title="Thursday, 17-Apr-2025 12:14:09 JST">Thursday, 17-Apr-2025 12:14:09 JST</time> <span>from <span><a href="https://social.sanfranciscan.org/objects/c6db431e-da1c-41b3-8f7f-a9e9a3d96673" rel="external" title="Sent from social.sanfranciscan.org via ActivityPub">social.sanfranciscan.org</a></span></span><a href="https://social.sanfranciscan.org/objects/c6db431e-da1c-41b3-8f7f-a9e9a3d96673">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: blog.sanfranciscan.org</div><h5><a href="https://blog.sanfranciscan.org/2025/04/16/If-Google-Can-Break-My-Pixel-They-Can-Break-Yours/">If Google Can Break My Pixel, They Can Break Yours</a></h5><div></div></header><div>Google pushed an update that broke my working Pixel 4a. Support failed. I didn't upgrade. I switched to GrapheneOS. Here's why it matters.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Chema Hernández Gil :sf: (chema@social.sanfranciscan.org)'s status on Thursday, 17-Apr-2025 12:14:09 JSTChema Hernández Gil :sf:
- GrapheneOS
Back in January, #Google pushed an update that broke my working #Pixel 4a. Support failed. I didn't upgrade. I switched to @GrapheneOS

Here's my experience.

https://blog.sanfranciscan.org/2025/04/16/If-Google-Can-Break-My-Pixel-They-Can-Break-Yours/

#technology #privacy #smartphone #Android
In conversationThursday, 17-Apr-2025 12:14:09 JST from social.sanfranciscan.orgpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: blog.sanfranciscan.org
  If Google Can Break My Pixel, They Can Break Yours
  Google pushed an update that broke my working Pixel 4a. Support failed. I didn't upgrade. I switched to GrapheneOS. Here's why it matters.

Public

Embed Notice

HTML Code

Corresponding Notice