cm0002

Here's another French journalist participating in fearmongering about GrapheneOS. That article is not measured. It provided a platform to make both unsubstantiated and provably false claims about GrapheneOS while providing no opportunity to see and respond to those claims.

https://bsky.app/profile/gabrielthierry.bsky.social/post/3m62ewf5mvs2q

The claims the article platforms are conflating closed source products from European companies infringing on our copyright and trademarks with GrapheneOS. GrapheneOS doesn't have the features they claim it does, isn't distributed in the ways they claim and they don't understand open source software.

GrapheneOS is obtained from https://grapheneos.org/install/web and https://grapheneos.org/releases. There are a bunch of legitimate companies in Europe selling devices with real GrapheneOS including NitroKey. We aren't partnered with those companies and don't get funding from it but there's nothing shady about it.

Products using operating systems partially based on our code are not GrapheneOS. There's no such thing as a fake Snapchat app wiping the device in GrapheneOS. It has no remote management or remote wiping built into it. It does not have a subscription fee / licensing system built into it either.

Vast majority of the code for those products comes from elsewhere: Android Open Source Project, Linux kernel, Chromium, LLVM and other projects. Of course the non-profit open source project writing a small portion of the code being used by those companies being targeted rather than IBM, Google, etc.

Both Android and iOS try to defend users from the same attack vectors we do. We developed far better protections against exploits which we release as open source code. Open source means anyone can freely use it for any purpose, exactly like the Android Open Source Project used by GrapheneOS itself.

Open source is why we can build GrapheneOS based on the Android Open Source Project. It doesn't make Linus Torvalds, IBM, Google, etc. responsible for what we do. Similarly, others can make their own software based on GrapheneOS. A fork of GrapheneOS contains a small portion of code written by us.

France supposedly has a right to reply which we intend to exercise to respond at length to these articles containing libel from the French state.

We're going to be ending the small amount of operations we have in France as we don't feel the country is safe for open source privacy projects anymore.

GrapheneOS doesn't host services storing sensitive user data. We have signature verification and downgrade protection for updates to the OS, apps and app store metadata. We're going move our website and discussion server away from OVH. Our update mirrors and authoritative DNS are already elsewhere.

Our discussion forum, Matrix, Mastodon, etc. in OVH Bearharnois can be moved to local or colocated servers in Toronto instead. We can use Netcup (owned by Anexia, both German) as one of the main providers for website/network service instances. The majority of our servers are already not on OVH.

We won't travel to France including avoiding conferences and will avoid having people working in the country too. A simple heuristic for the EU is avoiding countries supporting Chat Control. We genuinely believe we cannot safely operate in France anymore as an open source project privacy project.

Our pinned post on this platform shows a great example of why they're actually upset with us:

https://grapheneos.social/@GrapheneOS/113961075324902277

It almost makes us willing to contribute to AOSP again to try to wipe out their ability to exploit a subset of non-GrapheneOS Android devices too. Google is welcome to reach out.

Please read this thread and the linked articles:

https://mamot.fr/@LaQuadrature/115581775965025042

FEX 2511 is out today for this open-source emulator akin to Apple's Rosetta that allows running x86/x86+64 applications on ARM64. But in the case of FEX, for ARM64 Linux devices and akin to other open-source projects like Box64.

FEX 2511 is out today for this open-source emulator akin to Apple's Rosetta that allows running x86/x86+64 applications on ARM64. But in the case of FEX, for ARM64 Linux devices and akin to other open-source projects like Box64.

Recently, we introduced updates that increase the XP earned in official matches and reduce the XP needed for the first 20 attachment ranks. As we continue to build on the improvements we mentioned previously, we are also delivering a major overhaul of Challenges and Assignments, guided by gameplay data and your feedback. Some of the adjustments in this update are substantial, and we wanted to share more context on how we arrived at them. This update makes significant reductions to challenge requirements, cutting down on time investment while maintaining a focus on skill-driven progression that rewards consistent play. Challenges and Assignments are tuned around defined playtime targets, and these changes bring their requirements in line with those goals to make them more achievable within a reasonable session length. Assignments will continue to range from goals you can complete through regular play to a few that reward true mastery, particularly those tied to cosmetic items. Some of the original criteria did not fully reflect that intent, and we have updated them to make their difficulty and purpose clearer.

The first set of changes went live today through a server-side update and are available immediately. Any progress you’ve already made will automatically be applied when you enter a match, unlocking any challenges or assignments you now meet based on the updated criteria.

As previously indicated, the scale of our plans for Challenges and Assignments are large and will take place over multiple server-side and client-side updates, expect additional updates in the future. We wanted to get the first set of changes into your hands as soon as possible while we prepare further game updates. We’ll follow-up with more details on the rollout in the future. In this first set of changes we made a total of 90+ adjustments to Challenges and Assignments. Below we’ve highlighted a few examples. Class Challenges Assault, Engineer, Support, and Recon challenges now complete much faster.

Assault 2: Have Squadmates deploy on your Spawn Beacon.
Reduced from 50 deploys to 5.
Support 2: Revive teammates as Support.
Reduced from 200 revives to 60.

Weapon Assignments All weapon-type assignments (ARs, SMGs, LMGs, Shotguns, DMRs, Snipers, Carbines) have been significantly simplified.

Rapid Fire 1/Assault Rifle: Inflict damage with Assault Rifles.
Reduced from requiring 10000 inflicted damage to 3000.

Mode & Unit Assignments The majority of our mode-specific assignments (Conquest, Rush, Breakthrough, Domination, and others) have been standardized to require two wins per tier. This change makes it easier to pursue these challenges with clear intent.

Conquest 2: Wins in Conquest.
Reduced from 5 wins to 2.
Conquest 3: Objective kills in a round of Conquest.
Reduced from 30 objective kills in a round to 10.

Gameplay & Mastery General “Expert” and “Master” assignments that require multi-kills, headshots, kill streaks, or revives have been adjusted to better match the natural rhythm of gameplay. For example, multi-kill and streak goals now align with average round performance rather than rare, outlier achievements.

Explosives Expert 2: Get Multi Kills (2+ Kills Onwards) with explosives.
Reduced from 20 Multi Kills to 5.
Adaptable 2: Repair damaged Vehicles in a life.
Reduced from requiring 3000 damage to 500.

We value your ongoing feedback around Challenges and Assignments as we continue to roll out further improvements. Please continue to report bugs on our EA Forums, and join the community on the Battlefield Discord server.

See you on the Battlefield.