Earlier 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.
Simple. Fairphone doesn't want GOS. Forking GOS and porting it to a new device is a huge and unreasonable ask for an individual user. Even less so when you include the fact that you'll need to keep it up to date.
GrapheneOS' rewritten Messages app is released
91–100 of 258 posts
Re: GrapheneOS' rewritten Messages app is released
#92Earlier quoted context omitted.
I'm really hoping they're doing this to pave the way for an RCS implementation. If it can be done, GOS is in the best position to make it happen, and without RCS, chatting with normies is both extremely inconvenient (large group chats straight up do not work) and categorically insecure. If I could convince all my friends and family to use Signal I would, but they just think I'm on about some weird Edward Snowden shit…
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.
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 RCS server is mandated by your carrier)
Re: GrapheneOS' rewritten Messages app is released
#93Re: GrapheneOS' rewritten Messages app is released
#94So having a bare bones aosp messaging app was never an issue for me. Having said that, I find fossify messages pretty good.
Will try out the new GOS app too.
Re: GrapheneOS' rewritten Messages app is released
#95Earlier quoted context omitted.
No. RCS is still quite hard to actually implement. There's an open issue for it but the effort is mildly herculean. AFAIUI though GOS does intend on providing an RCS impl eventually even if it takes years to do.
I'm really hoping they're doing this to pave the way for an RCS implementation. If it can be done, GOS is in the best position to make it happen, and without RCS, chatting with normies is both extremely inconvenient (large group chats straight up do not work) and categorically insecure. If I could convince all my friends and family to use Signal I would, but they just think I'm on about some weird Edward Snowden shit…
Re: GrapheneOS' rewritten Messages app is released
#96Earlier quoted context omitted.
I'm really hoping they're doing this to pave the way for an RCS implementation. If it can be done, GOS is in the best position to make it happen, and without RCS, chatting with normies is both extremely inconvenient (large group chats straight up do not work) and categorically insecure. If I could convince all my friends and family to use Signal I would, but they just think I'm on about some weird Edward Snowden shit…
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.
Re: GrapheneOS' rewritten Messages app is released
#97Earlier quoted context omitted.
This is completely false. Tap the call, tap "call details" and its there. Took be 2 second to disprove. This is lazy to the point of being seemingly malicious commentary.
I'm just reading from the barrier here, and not knowing what it even looks like, but reading your description I can immediately agree that it is a bad design. There's only a handful of critical details in a call history, and absolutely no reason for any UI to implement them as secondary or tertiary details: Whether it was in- or outbound. To/from what contact. The date and time. 2 taps for some other extra info such…
Clearly.
>There's only a handful of critical details in a call history
And they're all there: profile pic, contact name, indicators that show incoming/outgoing + missed/connected, which SIM, a redial button, how long ago (which after about a week shows the date), Tapping the middle expands the row (no obstructive pop-up) to show Block, Message, & Details buttons.
The reason it has 'human times' is because multiple calls with the same contact are grouped, so a precise time doesn't always make sense. Tapping the Details will show all calls in that group, whether it's one or seven, with their full dates, times, durations, and further options. It's never been a difficult UX.
Re: GrapheneOS' rewritten Messages app is released
#98Re: GrapheneOS' rewritten Messages app is released
#99Everytime 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).
Re: GrapheneOS' rewritten Messages app is released
#100Earlier quoted context omitted.
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 demonstra…