HybridStatAnim8

6 ms·

1.
by HybridStatAnim8 4d ago
I have no role in the project and that has been stated many times on social media.
2.
by HybridStatAnim8 4d ago
Asking for support is not brigading. The vouch button exists for a reason.
3.
by HybridStatAnim8 5d ago
Yeah it is. Their infrastructure costs are super tiny, the biggest percent of funding goes to pay the dev team, and many are paid a wage comparable to where they live, they dont get inflated US software dev wages or anything. Most of what t
4.
by HybridStatAnim8 5d ago
GrapheneOS makes 100% of their money off of donations, and have made quite a lot of it. The bottleneck is not funding, but finding talented developers to pay with that money.
5.
by HybridStatAnim8 5d ago
The notification the Messaging app produces should have the option to copy the one time code directly.
6.
by HybridStatAnim8 5d ago
At least it is now consistent with the rest of the OSs UI.
7.
by HybridStatAnim8 5d ago
GrapheneOS has made a big push to hire a bunch of experienced, talented app devs, and they have been slowly chipping away at Messaging for a few months. They now have the resources to take on the AOSP apps and resume with the GrapheneOS app
8.
by HybridStatAnim8 5d ago
GrapheneOS wants to eventually support RCS in the default chat app. It may take a lot of time for it to work without google components/google services but it is the eventual plan.
9.
by HybridStatAnim8 5d ago
Not yet, but they do plan to add support for it.
10.
by HybridStatAnim8 5d ago
It will get ported to kotlin, material 3, and jetpack compose, just like Messaging.
11.
by HybridStatAnim8 5d ago
Good news! GrapheneOS has ported Messaging to kotlin, jetpack compose, and material you. The same is planned for the Contacts app, Dialer app, and more. Dont quote me but it seems Contacts and Dialer are up next after Messaging. Also, Graph
12.
by HybridStatAnim8 9d ago
GPLv2 and Apache 2.0 are not incompatible licenses when bundled together. GPLv3 is the problematic license as it requires all code it is bundled with be GPLv3 as well. When it comes to AOSP/GOS, bundled apps are not aggregated together
13.
by HybridStatAnim8 9d ago
Whether or not you tolerate using RCS is up to you. Not supporting it for the sake of having a worse default option on the off-chance you can use the to convince them to use a better option is not a good reason to not support RCS. Either
14.
by HybridStatAnim8 9d ago
Florisboard.
15.
by HybridStatAnim8 9d ago
Unsure what you mean by link against it. GPLv3 requires making the entire project it is bundled with GPLv3 as well. GrapheneOS would need to relicense the entire OS and bundled apps as GPLv3 to allow them to use any app with that license.
16.
by HybridStatAnim8 10d ago
That is not true. AOSP can run all modern android apps, and google play APIs are provided as alternatives, but not replacements, for AOSP functionality.
17.
by HybridStatAnim8 10d ago
Android and IOS encrypt your device. Most modern phones do, that is not specific to GrapheneOS and is an important, generic part of data safety that has been used for decades. GrapheneOS offers a duress PIN/password, not button, that i
18.
by HybridStatAnim8 10d ago
GrapheneOS has ~500000+ users and climbing. It is getting rapid mainstream awareness and appeal and is partnered with a top 10 OEM.
19.
by HybridStatAnim8 10d ago
I assume many people would use it due to SMS concerns and difficulty having people move to other platforms. I would personally use it as a fallback to Signal since my current fallback is SMS, which I dont like. If the protocol is properly e
20.
by HybridStatAnim8 10d ago
Yes, the GPLv2 license does not have the same restrictions GPLv3 does, it does not necessitate making the code it is bundled with GPLv2.
21.
by HybridStatAnim8 10d ago
It is true, and if Ubuntu is shipping apps as a part of the OS with incompatible licenses, that is a crime.
22.
by HybridStatAnim8 10d ago
The Refra gallery fork would replace the current ancient gallery app. That would be bundled with the OS. Doing the same with the fossify suite or similar would be illegal. These licenses do not treat apps or libraries differently. GPLv3 cod
23.
by HybridStatAnim8 10d ago
What? The Messages overhaul has been going on in the background for months. They announced it near the end of the port rather than the start. What is wrong with that? It has nothing to do with AI. You can check github and see this developme
24.
by HybridStatAnim8 10d ago
If you are referring to Heliboard as an AOSP board replacement, that cannot work, GrapheneOS cannot use GPLv3 projects. If you mean it as a user installed app, please disregard.
25.
by HybridStatAnim8 10d ago
Maybe, but there are better candidates GrapheneOS is more interested in.
26.
by HybridStatAnim8 10d ago
They cannot. The license FUTO uses is not open source and is incompatible with being bundled with GrapheneOS.
27.
by HybridStatAnim8 10d ago
The AOSP is fully open source. What you suggest is a significant step back in terms of privacy and security.
28.
by HybridStatAnim8 10d ago
If you have used GrapheneOS, you know Messaging is positively ancient and bitrotting. The overhaul makes it look like the rest of the OS and uses standard material 3. Its not something to fear.
29.
by HybridStatAnim8 10d ago
The point is to access an e2ee protocol bundled by default on many devices, and is cross-platform. GrapheneOS does recommend using superior platforms like Signal, but that is 3rd party, and thus has adoptability issues in convincing people
30.
by HybridStatAnim8 10d ago
The RCS spec has encryption in its documentation. I think the current spec version is 4.0?

More ›