Live data from Hacker News

GrapheneOS' rewritten Messages app is released

github.com

81–90 of 258 posts

Re: GrapheneOS' rewritten Messages app is released

#81
post #70

Earlier quoted context omitted.

You're using software from an alpha channel. People sometimes.

Alpha lowers the expected level of polish and stability - it doesn't make every regression equally acceptable. It is a reasonable criticism even when released to the alpha channel. Further, I believe it's reasonable for users' expectations to be influenced by what the project itself communicates about the development process. > People sometimes. I have experienced many (relatively minor but some annoying) bugs in Gra…

This is somewhat true. I expect more regressions from released commercial software.

I suspect there are fewer regressions per release on graphenes alpha messenger than there are in googles message's app.

Re: GrapheneOS' rewritten Messages app is released

#82
post #56

Earlier 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.

also I think RCS is way to insecure for Graphene OS - they have no way of making sure the communication is actually 100% secure. In my experience, Graphene OS doesn't make compromises.

Why would they support SMS then?

Re: GrapheneOS' rewritten Messages app is released

#83

Everytime 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.

Every time Fairphone release new device I check width size. Still waiting for small device.

Re: GrapheneOS' rewritten Messages app is released

#84

Everytime 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).

Every fairphone I've seen to far the camera was kinda ass. Did it improve? Pixel phones usually have old Samsung sensors which are pretty damn decent.

Re: GrapheneOS' rewritten Messages app is released

#85
post #59
post #42

Earlier quoted context omitted.

You should search for the many times where GrapheneOS has stated they won't work with Fairphone

It's because Fairphone doesn't fulfil GOS's hardware requirements. If Fairphone addresses that, there's no reason for GOS to not support a Fairphone device.

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.

Re: GrapheneOS' rewritten Messages app is released

#86
post #84

Everytime 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).

Every fairphone I've seen to far the camera was kinda ass. Did it improve? Pixel phones usually have old Samsung sensors which are pretty damn decent.

The sensor of the Fairphone camera is good enough, the software processing is what's lacking. Imo, owner of an FP4.

Re: GrapheneOS' rewritten Messages app is released

#87
post #63

Seeing "Material 3/Material You" is a negative point for me, not a positive. It's almost comical just how atrocious the UI is. Yes let's make all phones 20% huge-er and all whitespace 40% wider, said no sane person ever.

It’s amazing that you don’t think any of this is based on real HCI. People prefer larger tap targets on touch screens.

> People prefer larger tap targets on touch screens.

Only in a completely stupid, nonsensically A/B tested notion of "prefer". I'll refer you to this ~~excellent piece of satirical writing~~ actual post from Google design team: https://design.google/library/expressive-material-design-goo...

Re: GrapheneOS' rewritten Messages app is released

#88
post #59

Earlier quoted context omitted.

It's because Fairphone doesn't fulfil GOS's hardware requirements. If Fairphone addresses that, there's no reason for GOS to not support a Fairphone device.

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.

Re: GrapheneOS' rewritten Messages app is released

#89
post #78
post #73

Earlier 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…

> design-wise this was already a "Done" thing in the golden Nokia days!

I might be mistaken but I seem to recall it being a done thing for android prior to several years ago when it was "improved" with an update. Although it's possible I'm confusing the call apps from AOSP and various vendors. Either way several of my past android devices had a significantly better address book, dialer, and call history.

Post reply on HN