cross-posted from: sopuli.xyz/post/38159981
Forget the far right. The kids want a ‘United States of Europe.’
Based on social media, the upcoming generation is expressing more European solidarity than the continent has seen in decades.Nicholas Vinocur (POLITICO)
Tags:
Changes since the 2025121000 release:
All of the Android 16 security patches from the current January 2026, February 2026, March 2026, April 2026, May 2026 and June 2026 Android Security Bulletins are included in the 2025121201 security preview release. List of additional fixed CVEs:
2025121201 provides at least the full 2026-01-01 Android and Pixel security patch level but will remain marked as providing 2025-12-05.
For detailed information on security preview releases, see our post about it.
GrapheneOS discussion forumGrapheneOS Discussion Forum
We've received a 2nd IPv4 /24 subnet from ARIN for our 2nd anycast DNS network. Both our /24 subnets were obtained quickly under the NRPM 4.10 policy for IPv6 deployment for our dual stack DNS use case. 2nd was obtained without waiting 6 months due to being a discrete network.
We host our own authoritative DNS servers to provide DNS resolution for our services. Authoritative DNS are the servers queried by DNS resolvers run by your ISP, VPN or an explicitly user chosen one such as Cloudflare or Quad9 DNS. We now have our own AS and IP space for this.
Our ns1 has 11 locations on Vultr: New York City, Miami, Los Angeles, Seattle, London, Frankfurt, Singapore, Mumbai, Tokyo, Sao Paulo and Sydney.
Our ns2 has 4 locations on BuyVM: New York City, Miami, Las Vegas and Bern. We'll be adding a 2nd server provider for more locations.
DNS resolvers quickly fall back to the other network if traffic is dropped. Having two discrete networks with separate hosting companies and transit providers provides very high reliability. Individual servers which go down also stop having traffic routed to them due to BGP.
We have tiny website/network servers and also powerful update mirrors around the world. Our DNS servers use a combination of a GeoIP database and their own location to route users to the closest server that's up. Frequent health checks and low expiry time handle server downtime.
Changes in version 167:
A full list of changes from the previous release (version 166) is available through the Git commit log between the releases (only changes to the gmscompat_config text file and config-holder/ directory are part of GmsCompatConfig).
GmsCompatConfig is the text-based configuration for the GrapheneOS sandboxed Google Play compatibility layer. It provides a large portion of the compatibility shims.
This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release.
Contribute to GrapheneOS/platform_packages_apps_GmsCompat development by creating an account on GitHub.GitHub
Changes in version 143.0.7499.109.0:
A full list of changes from the previous release (version 143.0.7499.52.0) is available through the Git commit log between the releases.
This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.
Privacy and security enhanced releases of Chromium for GrapheneOS. Vanadium provides the WebView and standard user-facing browser on GrapheneOS. It depends on hardening in other GrapheneOS reposito...GitHub
Jolla has spent years disparaging projects based on the Android Open Source Project (AOSP) for marketing. SailfishOS has a largely closed source user interface and application layer with no equivalent to the open source AOSP. It's far less private and secure than AOSP or iOS too.
Jolla recently launched a new product so their supporters are understandably trying to promote it. As part of that, they've been posting about it in replies to posts about GrapheneOS. We've replied to some of it with our perspective within threads originally about GrapheneOS.
Since we dared to post accurate information in threads about GrapheneOS where they mentioned us in replies to promote it, their forum is being used as a place to attack GrapheneOS including libelous attacks towards our team referencing harassment content:
forum.sailfishos.org/t/sailfis…
Several of their supporters are taking the usual approach of calling us crazy and delusional while referencing harassment content at the same time as calling the factual info we posted aggressive. They're brigading discussions about GrapheneOS with attacks so we made this thread.
Brigading threads about an open source project and attacking the team with libelous claims is toxic. Defending ourselves from it with factual statements is not toxic. Repeating dishonest attacks on our team based on similar attacks over and over doesn't make it any less untrue.
Actually Jolla say that “Sailfish OS is partially open source, but not fully open source in the sense of “every part of the OS is free/open-source.Sailfish OS Forum
At this point, it feels like Graphene is making this out of whole cloth in order to gin up donations.
I see no evidence of specific attacks presented here, and I'm not going out to "X" and every other shit platform looking for contrarians besides. There's always noise being made on the internet in contrast to anything. I challenge anyone to point to the specific consternation any other open source product is making intentionally at a high level to try to take down graphene.
This project seems to be ran by an individual with a martyr complex and simply needs better management. I do run GOS myself, but can't wait to move to a full *nix device, particularly after this repeated whinging. Why would anyone trust someone so capricious?
Edit: wanted to add that the thread linked is largely the Sailfish community complaining about the graphene community, specifically Micay. I see no evidence of brigading or the like, plenty of unbacked assertions, however.
This is our first non-experimental release based on Android 16 QPR2 after our initial experimental 2025120800 release.
The change to the style of notification backgrounds is an upstream regression rather than an intentional change to a more minimal style. It will be fixed in a subsequent release since we decided it isn't important enough to delay this.
Tags:
Changes since the 2025120400 release:
All of the Android 16 security patches from the current January 2026, February 2026, March 2026, April 2026, May 2026 and June 2026 Android Security Bulletins are included in the 2025121001 security preview release. List of additional fixed CVEs:
2025121001 provides at least the full 2026-01-01 Android and Pixel security patch level but will remain marked as providing 2025-12-05.
For detailed information on security preview releases, see our post about it.
GrapheneOS discussion forumGrapheneOS Discussion Forum
Ch3rry314
in reply to KindnessInfinity • • •