[flagged]
So..next year?
I'll believe it when I see it.
GrapheneOS' rewritten Messages app is released
191–200 of 258 posts
Re: GrapheneOS' rewritten Messages app is released
#192Earlier quoted context omitted.
I don't understand the issue. If Fairphone wants GOS can't they just compile it themselves with whatever unsupported hardware based security features disabled? Ditto for any given end user. It's not as though we're talking about a device with hardware specs locked behind an NDA and drivers that only support outdated kernel versions.
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 with hardware specs locked behind an NDA and drivers that only support outdated kernel versions. Fairphone 5 and earlier have an end-of-life Linux kernel. Fairphone 6 is approaching the same fate. No…
Yes, I realize that the official stance is that it isn't grapheneos without the security features. That doesn't change the fact that someone who won't have the security features either way (and presumably doesn't care because otherwise he would switch to a different piece of hardware) might want the option of using a build of grapheneos that isn't officially condoned by the maintainers. (That's kind of the whole point of FOSS, right?)
I didn't realize fairphone was stuck on an EoL kernel. I guess that means that even if the build can be made to work right now (far from certain given an old kernel) it would likely break in the future.
Re: GrapheneOS' rewritten Messages app is released
#193Everytime I read GrapheneOS news I search for news related to Fairephone. It's such a shame that there's still no official plan for Fairephone to work on requirements for GrapheneOS. The combination of those 2 would be fantastic. It would also open a big new market (I assume) for Fairephone so not sure why there seems no clear sign in that direction at all (to my knowledge).
[flagged]
Re: GrapheneOS' rewritten Messages app is released
#194How about some screenshots?
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 more to improve before it will go to the Beta and Stable channels. It's the default SMS/MMS app for GrapheneOS and isn't available for use outside GrapheneOS so we aren't trying to promote it a…
[flagged]
Re: GrapheneOS' rewritten Messages app is released
#195Earlier quoted context omitted.
Why? Because of drivers? Don’t they already have Linux drivers for the fairphone? I wonder if fable or astra could wire everything up.
LLMs do not solve every problem. You are dependent on Qualcomm for hardware firmware updates and apparently they charge quite a bit extra if you want continuous monthly security updates [1]. This is possibly one of the reasons that smaller OEMs like Fairphone do not update firmware regularly and instead choose to keep their customers vulnerable to many known CVEs. [1] https://news.ycombinator.com/item?id=48079791
They're getting remarkably good at reverse engineering. I wonder if the relevant firmware updates can be provided by the user or OEM or if they're blobs that have to be signed by qualcomm?
Re: GrapheneOS' rewritten Messages app is released
#196Everytime I read GrapheneOS news I search for news related to Fairephone. It's such a shame that there's still no official plan for Fairephone to work on requirements for GrapheneOS. The combination of those 2 would be fantastic. It would also open a big new market (I assume) for Fairephone so not sure why there seems no clear sign in that direction at all (to my knowledge).
[flagged]
[deleted]
Re: GrapheneOS' rewritten Messages app is released
#197Some screenshots since the repo doesn't have any for whatever reason: https://imgur.com/a/C8yV83v
The reason is Waterluvian's Law:
> The more an article would benefit from photos, the less likely it’ll have them.
Re: GrapheneOS' rewritten Messages app is released
#198Earlier quoted context omitted.
SMS is a defacto carrier tech that people expect to work, people also don't expect e2ee or any kind of privacy scheme on SMS but it might be a place to hand communication off to a different tech. Whereas RCS leaks meta data to the goog or worse (I don't know the ins and outs of RCS) but by default I would trust it less then signal, who may also collect meta data leaked through the goog, so I guess the real solution i…
Signal > RCS > SMS. Just because RCS can't be done without metadata doesn't mean it's a fruitless endeavor. Why not have someone use RCS to then get on Signal? That is so much better than plaintext SMS to Signal. And for most people, RCS between Android iOS is the biggest advancement in encrypted communication for the layman that I've seen since Let's Encrypt.
That is a positive progression for sure. I guess it sounds like RCS is gatekept behind a play store API on the android side so there isn't an open source solution quite yet? Mostly I'm lamenting that even with signal there's meta-data you can infer behavior from. I know Session messenger has a bit of a network shuffle (is it garlic routing?) That blurs metadata collection a bit, but then they watered down several of Signals' security/privacy choices. I'm constantly curious and overwhelmed at the choice of text communication platforms, just so many!
Re: GrapheneOS' rewritten Messages app is released
#199Earlier quoted context omitted.
I'm thinking quite the opposite. I hope RCS can die fast. We already have chat apps WhatsApp, signal, telegram, you can even create your own. I'm quite happy that SMS for one are not something centralized by the giant US big corp. Would be the dream of Google to get all your messages as a gateway.
So I looked into this because my idea of RCS was that it was pretty decentralized direct encrypted communication. TIL that RCS was designed as a fairly decentralized protocol where every carrier could run their own RCS servers, but it didnt get adoption. So Google stepped in and built their own routing infrastructure, and now mostly all RCS is centralized on Google's servers (even if you use an iPhone, because the RC…
In my neck of the woods Google actually disabled some of that routing infra, breaking RCS, I guess wanting to force the carriers to build out parts of it? Needless to say the carriers wouldn’t have any of it, so as it stands RCS is fully broken, has been for some time, and will continue to be.
This just shows the fragility of the tech and why I wouldn’t want to rely on it for anything crucial.
Re: GrapheneOS' rewritten Messages app is released
#200Some screenshots since the repo doesn't have any for whatever reason: https://imgur.com/a/C8yV83v
The reason is Waterluvian's Law: > The more an article would benefit from photos, the less likely it’ll have them.
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 looking at static images of it.