Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
grapheneos
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
31.
▲
by
grapheneos
1mo ago
Google considers VPN leaks to be valid bugs but unfortunately doesn't consider them security bugs. Internal issues are created for any issue report considered valid. The external one is only used to communicate with people. If it was f
32.
▲
by
grapheneos
1mo ago
Security issues considered outside the scope of what they consider a security vulnerability are closed regardless of what they plan to do about the issue. Google primarily uses internal issues to track issues with Android. Public issues and
33.
▲
by
grapheneos
1mo ago
They lag 1-2 months behind the Android Security Bulletins which are months behind when patches can first be shipped by vendors. Verifying their kernels for the FP5 and earlier are end-of-life can be done by looking at the code. It's st
34.
▲
by
grapheneos
1mo ago
There's nearly no information available on the working conditions, pay or environmental impact of Fairphones. T2Mobile is the company designing and making Fairphones since the Fairphone 4 and little information is available on them. Fa
35.
▲
by
grapheneos
1mo ago
> might want the option of using a build of grapheneos An OS without the core features and updates of GrapheneOS clearly isn't GrapheneOS. It's not permitted to refer to it as such. > That's kind of the whole point of F
36.
▲
by
grapheneos
1mo ago
RCS already works on GrapheneOS via Google Messages using sandboxed Google Play. We have an ICC authentication toggle for granting the required access to Google Play services. We want to provide our own implementation within our Messaging a
37.
▲
by
grapheneos
1mo ago
It may take a long time to make a fully standalone implementation and that may not be compatible with most carriers. However, we plan to provide it in the short term through support for using the Google RCS infrastructure. We can have it st
38.
▲
by
grapheneos
1mo ago
GrapheneOS already supports using Google Messages with RCS. Google Messages is essentially the only RCS app for Android and it's the only one supporting end-to-end encryption. There were other apps such as a Samsung one but they died o
39.
▲
by
grapheneos
1mo ago
We've announced our plan to add RCS with Messaging Layer Security (MLS) for E2EE compatible with Google Messages and iOS. SMS/MMS will only be a fallback once that's implemented.
40.
▲
by
grapheneos
1mo ago
We've announced our plan to add RCS with Messaging Layer Security (MLS) for E2EE compatible with Google Messages and iOS. SMS/MMS will only be a fallback once that's implemented. Google Messages is essentially the only remain
41.
▲
by
grapheneos
1mo ago
They're incorrect, see https://news.ycombinator.com/item?id=49669964 .
42.
▲
by
grapheneos
1mo ago
We've announced our plan to add RCS with Messaging Layer Security (MLS) for E2EE compatible with Google Messages and iOS. SMS/MMS will only be a fallback once that's implemented.
43.
▲
by
grapheneos
1mo ago
It's not an article but rather release notes for people who already use it. The app is only available to users on GrapheneOS as the default SMS/MMS app (eventually RCS). Our users try out the new version directly instead of lookin
44.
▲
by
grapheneos
1mo ago
A video would be needed rather than screenshots since those wouldn't show the new animations and UI flow. GrapheneOS users can update to it via the Alpha channel and try it out rather than looking at screenshots. There's still mor
45.
▲
by
grapheneos
1mo ago
We've announced our plan to add RCS with Messaging Layer Security (MLS) for E2EE compatible with Google Messages and iOS. SMS/MMS will only be a fallback once that's implemented.
46.
▲
by
grapheneos
1mo ago
https://news.ycombinator.com/item?id=49669636
47.
▲
by
grapheneos
1mo ago
An incredibly incomplete port without many of the core security features and decent updates is not GrapheneOS. It isn't possible to bring GrapheneOS to Fairphone devices. > It's not as though we're talking about a device w
48.
▲
by
grapheneos
1mo ago
> as far as SMS/MMS can be secure We've announced our plan to add RCS with Messaging Layer Security (MLS) for E2EE compatible with Google Messages and iOS. > GOS got a big donation We receive large donations on an ongoing ba
49.
▲
by
grapheneos
1mo ago
Our server infrastructure costs around $200/month. All of our dedicated servers are sponsored. If we had to replace all of the current sponsored servers then we could scale it back a bit and keep the cost around $2000/month for th
50.
▲
by
grapheneos
1mo ago
GrapheneOS is entirely funded by donations. We're not yet spending nearly enough yet relative to the amount of donations we're receiving.
51.
▲
by
grapheneos
1mo ago
Providing it via the built-in Messaging app is planned but not straightforward to implement since it's not an open platform. GrapheneOS has official support for using RCS via Google Messages rather than it requiring anything sketchy. I
52.
▲
by
grapheneos
1mo ago
They want to sell more devices by improving security and having official support for GrapheneOS. The main work that's being done is official GrapheneOS support. They're also going to integrate improvements from it into their own O
53.
▲
by
grapheneos
1mo ago
Motorola Mobility (Lenovo) isn't providing us with funding. They're improving the updates and security features for their devices, providing what we need to support them with proper updates and helping with the GrapheneOS port.
54.
▲
by
grapheneos
1mo ago
The post didn't say that it should happen in a single moment. It would likely take the form of heavily reducing the maximum duration across the board and then gradually decreasing it for anything new. For example, capping it entirely a
55.
▲
by
grapheneos
1mo ago
> GrapheneOS leadership is very against Copyleft We use GPLv2 licensing for substantial portions of our code beyond our Linux kernel changes. Vanadium is licensed as GPLv2. As long as copyright exists then there's a place for copyle
56.
▲
by
grapheneos
1mo ago
The issue isn't that GPLv3 applies to non-derivative OS components but rather that the terms apply to the overall redistribution of the OS. Including any GPLv3 component means GrapheneOS cannot be used in products where AOSP can be use
57.
▲
by
grapheneos
1mo ago
It does make a difference. GrapheneOS includes a lot of GPLv2 code from AOSP and we choose it as a license for several of own projects within GrapheneOS.
58.
▲
by
grapheneos
1mo ago
No, we do not recommend using the Play Store as a source of apps over other options such as Accrescent. We document how people can obtain apps from the Play Store via both the sandboxed Play Store and Aurora Store. We explain apps with stor
59.
▲
by
grapheneos
1mo ago
The amount of die space needed to support MTE is minimal. MTE is used for Android Advanced Protection Mode and will very likely be enabled by default in future Android versions. If the Pixel 11 doesn't enable support for it then it
60.
▲
by
grapheneos
1mo ago
That's disabled unless the firmware sets up MTE and doesn't disable it for the OS. The Pixel 11 shipped with MTE hard-wired to disabled via the firmware with no way to enable it. The initial August 2026 update and the early non-QP
More ›