easrng 

@easrng.net did:plc:7prhbuf5izwc7xlbitgpt3sn

she/her • js witch • https://easrng.net

En Bluesky desde el 29 mayo 2023

Seguidores: 578
Siguiendo: 149
Posts: 2.184
Días en rankings: 0

Resumen

easrng  (@easrng.net) es un usuario de Bluesky que se unió el 29 mayo 2023. Tiene 578 seguidores, sigue a 149 cuentas y ha publicado 2.184 posts.

Apariciones en rankings

Los mejores días en que los posts de esta cuenta entraron en la lista diaria de Debya.

Esta cuenta aún no ha aparecido en un ranking diario.

Posts que le gustaron recientemente

Me gusta públicos de la red Bluesky.

GrapheneOS@grapheneos.org02-11-2026 00:42
App Store v37 is in Beta/Alpha. To try it out, select the Beta channel via the menu in App Store's page for itself. Vanadium in GrapheneOS 2026102100 was 2 versions old so you can uninstall WebView updates and update again via a small delta update. WebView has no data to lose via uninstall updates.
Ver post
GrapheneOS@grapheneos.org02-11-2026 00:42
There are similar savings for the Vanadium WebView. Until recently, the Vanadium browser and WebView shared a browser engine library via Trichrome builds. Chromium deprecated Trichrome due to bugs and Chrome stopped using it so we did too. We highly prioritized App Store delta updates due to this.
Ver post
GrapheneOS@grapheneos.org02-11-2026 00:42
The latest arm64 Vanadium browser APK is 325MB. It was previously downloaded as a 131MB gzip file created with zopfli. It's now downloaded as a 17MB update for users who were on one of the most recent 2 Vanadium releases. It's down to 95MB via Brotli for users on older versions without deltas.
Ver post
GrapheneOS@grapheneos.org02-11-2026 00:42
The latest version extends the cryptographic hashes to covering the compressed APKs and deltas to verify those prior to decompression. This means a compromised update server can't use the new Rust Brotli decompression library and Rust delta library as additional attack surface to exploit the client.
Ver post
GrapheneOS@grapheneos.org02-11-2026 00:42
Our App Store has always used a signed JSON file for metadata with a timestamp for downgrade protection. That has cryptographic hashes of each APK for verification. There's also the standard OS package manager verification via whole file signatures in each APK and version code downgrade protection.
Ver post