Live data from Hacker News

GrapheneOS Overhauled Default Apps and Secure Clipboard

grapheneos.social

91–100 of 284 posts

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#91
post #55

Earlier quoted context omitted.

RCS allows higher resolution pictures than MMS.

Perhaps it's different in other countries, but I've never seen anyone use MMS. (Everyone uses WhatsApp nowadays, but even before WhatsApp existed, I never saw anyone use MMS.)

I've seen people try, only for it to never actually work (images either compress horribly, to the point there's no reason even sending it, or just fail to send).

MMS bring broken since day 1 in my experience is probably the reason I jumped on internet chat and email, since those actually work as advertised (sure, they has some practical limits, but they tell you about those!). I probably would have sent my mum that image over MMS if MMS actually every worked. Since it never did, using a difference service was a must.

Then again, this feels like an extension of the rest of the phone system. Anything beyond calls between two people, SMS and data that involves connecting to the phone system has always (in my experience) been either janky or broken. No wonder I try to use anything else given the opportunity.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#92

> RCS isn't an open platform in practice. It isn't even as open as SMS/MMS. It heavily depends on proprietary Google and carrier infrastructure in practice. We can start by replicating Google's approach and then we can work on only using carrier services for carriers where it's actually supported. What is the point of RCS though? It seems to be strictly inferior to Signal. It seems a Google product meant to serve Goo…

RCS was DOA from day one as far as I'm concerned. The carriers being involved in any capacity deeper than providing dumb pipes alone was enough to make it pointless, but no E2E in the base spec makes it extra pointless. They may as well have just extended SMS to be more capable, because that's what they've effectively created.

I don't know much about RCS other than that carriers need to be involved, but there's a way to not involve them, which Google did for a while using some kind of compat-service (jibe or something?), and then they stopped doing it.

Never seen RCS working on any carrier ever since. I don't understand why Google couldn't just continue doing what it was doing. Why require carriers?

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#93

Graphene is clearly bullish on Android, but I have no idea why. The writing is on the wall, Google is slowly asphyxiating AOSP.

There is no alternative. Apple isn't going to let them build on top of iOS, and anything except those two is dead in the water because it'll never have users because it is missing a bunch of critical apps, and will never have those apps because it doesn't have users.

> There is no alternative.

There have been several projects like Ubuntu Touch to create an open Linux for smartphones.

That would be an open alternative.

Android is not open.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#94
post #60
post #51

Earlier quoted context omitted.

The source is here: https://gitlab.futo.org/keyboard/latinime Featured prominently in the "Source Code" container on https://keyboard.futo.tech/ AFAIK everything FUTO makes is open source? I haven't seen a counter-example (I have not looked hard though!), and https://futo.tech/about claims the following: > All FUTO-funded projects are expected to be open source or develop a plan to eventually become so. No effort wil…

From the LICENSE file: https://gitlab.futo.org/keyboard/latinime/-/blob/master/LICE... >You may modify the software only for non-commercial purposes such as personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, all without any anticipated commercial application. Violates clause 3 (Derive…

Ah, yeah, agreed - "source available" fits that much better. I'm pretty sure that's the same for immich (which is also from FUTO).

Thank you for the details! That lays it out nicely for anyone else passing through.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#95

Graphene is clearly bullish on Android, but I have no idea why. The writing is on the wall, Google is slowly asphyxiating AOSP.

There is no alternative. Apple isn't going to let them build on top of iOS, and anything except those two is dead in the water because it'll never have users because it is missing a bunch of critical apps, and will never have those apps because it doesn't have users.

FuriLabs makes a Linux phone that is designed as a daily driver. Looking at it to replace Android.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#96

Earlier quoted context omitted.

There is no alternative. Apple isn't going to let them build on top of iOS, and anything except those two is dead in the water because it'll never have users because it is missing a bunch of critical apps, and will never have those apps because it doesn't have users.

> There is no alternative. There have been several projects like Ubuntu Touch to create an open Linux for smartphones. That would be an open alternative. Android is not open.

[deleted]

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#97

Earlier quoted context omitted.

RCS was DOA from day one as far as I'm concerned. The carriers being involved in any capacity deeper than providing dumb pipes alone was enough to make it pointless, but no E2E in the base spec makes it extra pointless. They may as well have just extended SMS to be more capable, because that's what they've effectively created.

The RCS spec has encryption in its documentation. I think the current spec version is 4.0?

It has it in its current documentation (maybe 3.0 too? I forget, but it's new this year), and Apple and Google have had messages to themselves encrypted for a while (but not to each other, which is what the RCS docs are intended to resolve). It took many years to get it documented though (despite loudly claiming RCS is more secure the whole time), and AFAIK none yet implement it. Definitely none with all the documented things it needs to show to be compliant with the spec I read, e.g. key verification - I certainly don't see any of that in Google's "Messages" app! Though hopefully that will all change.

But honestly, in a non-open ecosystem, can you really trust that the near-exclusive two major players are actually playing by the rules? Apple has been relatively protective of its users on privacy stuff, but I've lost all trust in Google at this point.

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#98
post #26

Ctrl+f clipboard, no results. What does "Secure Clipboard" in the title refer to? The release seems to be only the SMS/RCS app, rest is future: > We're also going to be overhauling or fully replacing the rest of the AOSP apps in the near future. AOSP Gallery is incredibly outdated and is being entirely replaced. AOSP Keyboard may be similar. We recently hired a bunch of new people and will be hiring more so our progr…

[dead]

Re: GrapheneOS Overhauled Default Apps and Secure Clipboard

#99
post #55

Earlier quoted context omitted.

RCS allows higher resolution pictures than MMS.

Perhaps it's different in other countries, but I've never seen anyone use MMS. (Everyone uses WhatsApp nowadays, but even before WhatsApp existed, I never saw anyone use MMS.)

It depends heavily on country, yes. USA is extremely light on WhatsApp, and MMS use is widespread (and has been free for a long time now, and SMS even longer). RCS is a mostly silent upgrade for USA.

I'm not sure which of the two is better tbh. Utterly dominated by a Facebook-owned system, or using something that's crappy enough that people spread out to a variety of systems?

Post reply on HN