Posts by GrapheneOS@grapheneos.social
(DIR) Post #B21zRcbu4wNEXaRd8i by GrapheneOS@grapheneos.social
2026-01-03T11:04:36Z
0 likes, 0 repeats
@NewDay14 @Tutanota @PaintedDurian Each of those products has American and Chinese components. Fairphones are built in China, not Europe, and they use an American designed CPU. How are you avoiding either America or Europe by using a company selling you a white labelled Chinese device? It's not Fairphone designing or manufacturing the hardware but rather Fairphone's ODM partner in China. Fairphone has very little input into the device and has a tiny engineering team not capable of doing much.
(DIR) Post #B21zRdPt56M92bpY36 by GrapheneOS@grapheneos.social
2026-01-03T11:31:59Z
0 likes, 0 repeats
@NewDay14 @Tutanota @PaintedDurian It's Europe going after end-to-end encrypted messaging apps and secure operating systems including GrapheneOS. Europe passed Chat Control and is moving forward with bringing stricter terms. France and Spain have both had their law enforcement agencies attack GrapheneOS by trying to brand it as being for criminals and somehow tied to crimijnals for providing much more private and secure mobile devices. We see none of this stuff from the US, only from Europe.
(DIR) Post #B21zRf3yxW1S9Fb5BQ by GrapheneOS@grapheneos.social
2026-01-06T23:20:34Z
0 likes, 1 repeats
@NewDay14 @Tutanota @PaintedDurian @signalapp We didn't change the subject.EU states are the only ones targeted GrapheneOS with attacks. It's not being attacked by the US, Brazil, Iran, China, etc. but rather France, Spain, Sweden and the Netherlands.EU states and the EU itself are leading the charge among western countries to ban encryption and secure devices. The sovereignty you talk about is largely about governments having access to data and the ability to force companies to do things.
(DIR) Post #B29O9AZ9SxehJKAuaO by GrapheneOS@grapheneos.social
2026-01-10T18:08:59Z
0 likes, 0 repeats
@meles @ahalam No, that's absolutely not true. It's a server in Toronto but we used IP space loaned to us by a Romanian LIR so some GeoIP data incorrectly refers to it as Romanian. It seems that app wrongly thinks RO refers to Russia rather than Romania if they're showing you that, which is completely incorrect and always was. You should enter the IP into a GeoIP query site yourself which will show Toronto or Romania depending on whether they updated the data using the geofeed that's provided.
(DIR) Post #B29O9BYplczmOd2AjI by GrapheneOS@grapheneos.social
2026-01-10T18:10:32Z
0 likes, 0 repeats
@meles @ahalam Which app is it? We can determine which GeoIP provider they use and check there. It's likely that the app used the wrong flag for Romania but their GeoIP data source should be showing Canada rather than Romania now which is something we can get fixed with the GeoIP provider. We submitted our geofeed to multiple GeoIP providers already but didn't bother exhaustively submitting it to all of them instead of just letting them discover it and update Romania to Toronto themselves.
(DIR) Post #B2LOQvTidEQfcucV72 by GrapheneOS@grapheneos.social
2026-01-16T11:12:06Z
0 likes, 0 repeats
@BrennpunktUA GrapheneOS faces an enormous amount of inaccurate attacks towards our project and team on this platform from your communites. We'll continue defending ourselves from it. Non-hardened operating systems failing to provide basic privacy/security protections are not competition for GrapheneOS. We wouldn't be talking about them if the project members and their supporters were not attacking us relentlessly. GrapheneOS is a Linux distribution and Linux does not mean systemd/glibc/GNOME.
(DIR) Post #B2LOR1KiranXmkSOvI by GrapheneOS@grapheneos.social
2026-01-16T13:16:32Z
0 likes, 0 repeats
@MathieuP @Zahox_ We're engaging in a discussion with people in threads where our account has been mentioned. Disagreeing with statements people have made is not abusive. Posting accurate information about GrapheneOS and products people are bringing up is not abusive. What's abusive is responding to that with personal attacks on our team including joining in with harassment towards our founder baselessly claiming he's insane, delusional, schizophrenic, unhinged, etc. as multiple people here did.
(DIR) Post #B2LOR1LQoxMhowmy1o by GrapheneOS@grapheneos.social
2026-01-16T11:14:17Z
0 likes, 0 repeats
@BrennpunktUA It doesn't make sense for GrapheneOS to support insecure devices where it's not possible to properly protect users due to lack of important hardware-based security protections we use as part of our core feature set and driver/firmware patches. The purpose of GrapheneOS is not providing a sidegrade from the stock OS on devices people already have but rather a highly private and secure option. You're better off using an iPhone for privacy and security than other AOSP-based options.
(DIR) Post #B2LOR2G9Q4jeerKGR6 by GrapheneOS@grapheneos.social
2026-01-16T13:19:32Z
0 likes, 0 repeats
@MathieuP @Zahox_ Engaging in discussion on a discussion platform is not abusive. People can always opt-out of it. In this case, the author of the thread went out of the way to mention the @GrapheneOS account. Their post was explicitly directed towards our account. The idea that somehow us responding to that is in any way harassment or abusive is ridiculous. The only abuse in this thread were typical personal attacks towards our team because we disagreed with a post sent to us via mentioning us.
(DIR) Post #B2MAdOY5Ac1Z3sfkQ4 by GrapheneOS@grapheneos.social
2026-01-11T17:34:47Z
0 likes, 0 repeats
@TagHunt It uses a MediaTek Dimensity 7300 with an OS based on the initial yearly release of Android 15.It doesn't have hardware memory tagging, pointer authentication, branch target identification and other CPU security features. It doesn't have a secure element. It's not going to have proper privacy/security updates. It doesn't come close to meeting our hardware requirements.It's not running an operating system that's privacy and security hardened. Standard AOSP 16 QPR2 would be better.
(DIR) Post #B2MAdPwE0KvjN2yXgm by GrapheneOS@grapheneos.social
2026-01-11T17:36:30Z
0 likes, 0 repeats
@TagHunt We're working with a major Android OEM. It's one of the top 10 Android OEMs by sales. It's a definitely company you know already. They're hard at work on developing GrapheneOS support for one of their upcoming 2026 devices but it won't be possible to meet the requirements until the next generation, likely in 2027. Snapdragon Elite 8 Gen 5 is currently the only SoC meeting our requirements for non-Pixel devices but that doesn't mean any device using it meets our requirements at all.
(DIR) Post #B2MAdS0YJDa1n311iC by GrapheneOS@grapheneos.social
2026-01-12T22:46:34Z
0 likes, 0 repeats
@aab93e8e3fa6a8974e1c1f3199e5f3d9afb7aaa70b8236e93a5b2fafeafcbd3a @TagHunt @ba5115c37b0f911e530ed6c487ccbd9b737da33fd4b88a9f590860378c06af62 GrapheneOS is entirely funded by donations from our userbase. Our userbase includes people like Vitalik Buterin who are providing significant donations. You should read our response:https://grapheneos.social/@GrapheneOS/115884539052244771https://grapheneos.social/@GrapheneOS/115884550027291115/e/ is a non-profit based in France heavily funded by France and the EU despite their issues with secure devices and E2EE...
(DIR) Post #B2MAdSbm4pM1eUQkjI by GrapheneOS@grapheneos.social
2026-01-12T22:48:27Z
0 likes, 0 repeats
@aab93e8e3fa6a8974e1c1f3199e5f3d9afb7aaa70b8236e93a5b2fafeafcbd3a @TagHunt @ba5115c37b0f911e530ed6c487ccbd9b737da33fd4b88a9f590860378c06af62 GrapheneOS does not receive any government funding and is not receiving funding from business partners. Our partnership with a major Android OEM does not involve them sending us money but rather having their engineering teams work on GrapheneOS support. They'll likely end up helping to improve GrapheneOS by publicly submitting improvements to it upstream.
(DIR) Post #B2MAdTkfpE4DCNbNEu by GrapheneOS@grapheneos.social
2026-01-13T12:51:12Z
0 likes, 0 repeats
@ba5115c37b0f911e530ed6c487ccbd9b737da33fd4b88a9f590860378c06af62 @aab93e8e3fa6a8974e1c1f3199e5f3d9afb7aaa70b8236e93a5b2fafeafcbd3a @TagHunt Our OEM partnership started in June 2025 and work towards meeting the requirements began several months later. We said from the very beginning that the expected launch date was late 2026 or in 2027. We can now be more specific about the date because we know the new Qualcomm SoC platform will come out in Q4 2026 and the devices come out months later.
(DIR) Post #B2MAdUKTg6hszQLy2y by GrapheneOS@grapheneos.social
2026-01-13T12:56:55Z
0 likes, 0 repeats
@ba5115c37b0f911e530ed6c487ccbd9b737da33fd4b88a9f590860378c06af62 @aab93e8e3fa6a8974e1c1f3199e5f3d9afb7aaa70b8236e93a5b2fafeafcbd3a @TagHunt The reason the devices in 2026 can't meet the requirements is because Qualcomm only finished hardware memory tagging support for the Snapdragon 8 Elite Gen 5 at the last minute but doesn't have it working for the non-Elite variants of the SoC. It's the first SoC they've made with official support for it and there are likely also many issues to resolve.
(DIR) Post #B2n3LeEW6R5f8T7pvE by GrapheneOS@grapheneos.social
2026-01-29T21:54:34Z
1 likes, 2 repeats
We've built our own text-to-speech system with an initial English language model we trained ourselves with fully open source data. It will be added to our App Store soon and then included in GrapheneOS as a default enabled TTS backend once some more improvements are made to it.
(DIR) Post #B2pOjLip46d21mMbLc by GrapheneOS@grapheneos.social
2026-01-29T22:04:57Z
0 likes, 0 repeats
We're going to build our own speech-to-text implementation to go along with this too. We're starting with an English model for both but we can add other languages which have high quality training data available. English and Mandarin have by far the most training data available.
(DIR) Post #B2pOjMpawPdjT4XWXg by GrapheneOS@grapheneos.social
2026-01-29T22:06:37Z
0 likes, 0 repeats
Existing implementations of text-to-speech and speech-to-text didn't meet our functionality or usability requirements. We want at least very high quality, low latency and robust implementations of both for English included in the OS. It will help make GrapheneOS more accessible.
(DIR) Post #B2pOjNV4SCohXhweBs by GrapheneOS@grapheneos.social
2026-01-29T22:11:00Z
0 likes, 0 repeats
Our full time developer working on this already built their own Transcribro app for on-device speech-to-text available in the Accrescent app store. For GrapheneOS itself, we want actual open source implementations of these features rather than OpenAI's phony open source though.
(DIR) Post #B2pOjO8Q5uIBVkM4WW by GrapheneOS@grapheneos.social
2026-01-29T22:18:39Z
0 likes, 0 repeats
Whisper is actually closed source. Open weights is another way of saying permissively licensed closed source. Our implementation of both text-to-speech and speech-to-text will be actual open source which means people can actually fork it and add/change/remove training data, etc.