Would have been cool to have encrypted SMS messages like the SMSecure app while we wait for RCS
GrapheneOS' rewritten Messages app is released
41–50 of 258 posts
Re: GrapheneOS' rewritten Messages app is released
#42Everytime 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).
You should search for the many times where GrapheneOS has stated they won't work with Fairphone
Re: GrapheneOS' rewritten Messages app is released
#43Everytime 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).
You should search for the many times where GrapheneOS has stated they won't work with Fairphone
Given the state of Fairphone hardware, software and business, it is not surprising.
Re: GrapheneOS' rewritten Messages app is released
#44[flagged]
So..next year?
Re: GrapheneOS' rewritten Messages app is released
#45Earlier quoted context omitted.
You should search for the many times where GrapheneOS has stated they won't work with Fairphone
Given the state of Fairphone hardware, software and business, it is not surprising.
For those of us out of the loop, could someone summarize the situation?
Re: GrapheneOS' rewritten Messages app is released
#46I wish they prioritised the call app. It is beyond appalling. You can't even determine when a call happened, beyond the generic low fidelity "[time] ago". It also almost feels like tapping anything makes me accidentally call people. Abhorrent UI/UX to be completely honest.
Re: GrapheneOS' rewritten Messages app is released
#47Earlier quoted context omitted.
Given the state of Fairphone hardware, software and business, it is not surprising.
For those of us out of the loop, could someone summarize the situation?
> Fairphone has said they don't plan to add a secure element. It can be seen from their current devices that they don't fully keep up with privacy/security backports and lag a year behind on shipping yearly OS releases. They skip over the monthly and quarterly releases entirely. They replaced their own non-GMS Fairphone OS with a dramatically less secure /e/OS option in partnership with Murena. They clearly demonstrate that security and even privacy are not the priorities.
Re: GrapheneOS' rewritten Messages app is released
#48Everytime 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).
You should search for the many times where GrapheneOS has stated they won't work with Fairphone
[flagged]
Re: GrapheneOS' rewritten Messages app is released
#49Everytime 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).
Everytime I see Fairphone mentioned whenever there's news about GrapheneOS I'm confused as to why people keep on conflating both when they obviously have very different goals.
Re: GrapheneOS' rewritten Messages app is released
#50How about some screenshots?
I constantly see those projects that would benefit from a screenshot in a readme, but for some reason the thought about adding one doesn't even come to the authors' mind, even though it's pretty obvious. I'd really like to know what's going on.
I think the reason is that you can get quite much of a tunnel vision while developing. Everyone involved already knows what they're building and how it looks, so it's very easy to overlook it.
Case in point, I recently wrote a CLI to show which of your AWS infra is not captured in terraform, and you can either print the result as a json to consume by a machine or generate a dashboard with some charts. It took me an embarrassing while to realise that I should have included a damned screenshot in the README, in fact I think I only realised when I wanted to show it to my brother.