no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
15 comments in c/technology@lemmy.world view that post
[–] 15 points 2 months ago

The current messaging app doesn't even have a search function. This is well overdue.

  • source
  • [–] 14 points 2 months ago

    Implementing RCS properly and reliably is what I need to finally get my wife to switch. Hope this happens soon and would be amazing.

  • source
  • [–] 37 points 2 months ago* (8 children)

    These are welcome changes but I hope they will address the elephant in the room sooner or later. They can't go on depending on Pixels and hardware memory tagging. They need a roadmap for opening up the project to more phone models and they need it yesterday.

    They've drummed up some publicity with the journalist debacle so it's a good time to use that. But people who hear about Graphene will want to have some phone choices. "Get an old Pixel" is about to age like milk.

  • source
  • hideshow 8 child comments
  • [–] 31 points 2 months ago (6 children)

    Well good new is that they've already partnered with Motorola to make GrapheneOS available on (at least some) of their phones

  • source
  • parent
  • hideshow 6 child comments
  • [–] 17 points 2 months ago

    Which is better than nothing but I can't help but see it as walking into another exclusive partnership. Also, none of those phones are out yet so I'll believe it when I see it.

    Even if it pans out and there will be one Motorola phone supporting GrapheneOS out of the box in 2027, there's the issue of how much it will cost (I think it's supposed to be a "flagship"), what markets it will be available in, what the unlock process and conditions will be like etc.

    Last but not least I doubt Lenovo's commitment to "seven years of proper updates", which I will also believe when I see. Their track record for Android updates is notoriously poor. They claim 3-5 major Android updates for most of their models but the best I've actually seen them do is one update (13 to 14) – and that's for phones released 2-3 years ago. If that's the pace they wanna go we'll be lucky to get two updates in those 7 years.

  • source
  • parent
  • [–] 3 points 2 months ago (3 children)
  • [–] 4 points 2 months ago* (1 child)

    Blame the manufacturers for not including hardware security on cheaper phones. It would be nice to not have to pay a premium for sufficient security, or to have sandboxed Play Services on a less secure phone for example, but it's simply not GrapheneOS if you gut a lot of features that make people trust in it. That's not GrapheneOS's fault.

    Same principal as Privacy Guides. They're not going to recommend something that's doesn't meet their requirements. You will not see them recommend Windows no matter how many people comment "but how do I use Windows privately?" You can't. That's why it isn't recommended.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 months ago

    Blame people unwilling to pay for security for cheaper phones not having hardware security features.

    Blame the other manufacturers for not letting GrapheneOS unlock and relock the bootloader on their good phones with hardware security.

    Blame Graphene for not making a lesser version "CharcoalOS" (or something) for other phones, so now I have to use the even less secure, beginner-friendly /e/OS on my Sony phone.

  • source
  • parent
  • [–] 2 points 2 months ago

    If I remember correctly they didn't say that no other phones would never be supported, but yeah unfortunately for now the ability to put graphene on lower end phones is still quite far away

  • source
  • parent
  • [–] 11 points 2 months ago

    Yep. I value my privacy and would pay some for it.

    But I'm not paying 1000 bucks for any phone. Even half as much is hard to swallow for me.

    My phone is a privacy issue for me. I try to do what I can but between bad or no support of GrapheneOS or LineageOS for my devices, it's already a bad start.

  • source
  • parent
  • [–] 18 points 2 months ago (3 children)

    I don't mind finding alternative apps for my gallery and etc but RCS would be amazing. And I'm not sure it's feasible for a third party app right now so Graphene itself doing it will be awesome!

  • source
  • hideshow 3 child comments
  • [–] 6 points 2 months ago (2 children)

    I agree but how does RCS actually work? My understanding is that it is particularly difficult to implement.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 2 months ago

    Yeah it probably will be pretty difficult. Google has a chokehold on it but I trust Graphene devs to find the minimum possible surface to j trace with Google while having functional RCS. And just not needing Google's messenger app will be a huge plus for me.

  • source
  • parent
  • [–] 5 points 2 months ago

    The Mastodon thread linked in the most said they are planning to get an implementation that requires sandboxes Play Services first, then they should have a better idea of how to implement it solely with the carrier. It is an open standard in theory, just not in practice, since it is secretive.

  • source
  • parent
  • 14 comments in c/android@lemmy.world view that post
    [–] 23 points 2 months ago (4 children)

    RCS planned, I'm all for it

  • source
  • hideshow 4 child comments
  • [–] 8 points 2 months ago (3 children)

    I'm surprised it took this long, given how insecure SMS and MMS are.

    On the other hand, I don't think I know anyone that uses SMS regularly, so maybe it just wasn't a priority? Pretty much the only SMS messages I get are automated. It's more common to see people using either Messenger, WhatsApp, Signal, or Telegram (or iMessage in the USA but that's mostly an outlier compared to the rest of the world).

  • source
  • parent
  • hideshow 3 child comments
  • [–] 15 points 2 months ago (2 children)

    From one linked thread:

    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.

    So yeah, probably why it took so long

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 months ago

    It heavily depends on proprietary Google and carrier infrastructure in practice.

    This is the same as practically every carrier feature though. Carriers are a pain to deal with and all their infra is proprietary, so usually only the big companies like Google and Apple have the motivation to integrate with them and build out new services.

  • source
  • parent
  • [–] 7 points 2 months ago* (1 child)

    If I'm reading the clipboard part right, and seems people on the forms are thinking the same;

    If an app can only access clipboard content that it set, does that mean we can't copy/paste between apps? That would be ridiculous. Does the act of pressing "paste" over right the block, and GrapheneOS will only block the background access apps have?

    I like IOS approach, where it asks you before pasting "this app is trying to copy from another app", and you can allow or decline it. But it is really annoying sometimes.

  • source
  • hideshow 1 child comment
  • [–] 2 points 2 months ago*

    They mention permissions so my guess, without seeing it in action, is the permission is to be able to access the global clipboard, otherwise you're just using an isolated clipboard.

    Also they mention the keyboard having a paste button as a fallback for misbehaving apps, but IDK if that locks you into using GOS' very mediocre keyboard.

  • source
  • parent
  • [–] 5 points 2 months ago

    This is good news

  • source
  • [–] 4 points 2 months ago

    In the longer term, we plan to add support for RCS including support for the standard end-to-end encryption (E2EE)

    thank god i can finally ditch google messages if i want rcs

  • source
  • [–] 1 point 2 months ago

    The important distinction to me is whether clipboard access is user-initiated or happens silently in the background. Explicit paste should stay frictionless, while background reads are where tighter controls make sense. If GrapheneOS can enforce that boundary without adding an iOS-style prompt every time, that seems like a strong compromise.

  • source
  • [–] 1 point 1 month ago

    I am reading through lines and I seem to be stuck confused. Why isn't the whole clipboard partitioned?

    Example: Youtube - separate array(whatever) holding its clipboard Facebook - separate array(whatever) holding its clipboard

    When trying to copy-paste between apps, simply link its containers and provide cross-access for said apps. This way you keep it modular and as secure as possible while not allowing other services to access a specific container.

    I have yet to use GrapheneOS, sadly past phones I had did not support it.

  • source
  • [–] 1 point 2 months ago (1 child)

    So, apparently there's a new UI, but no screenshots?

    🤦

  • source
  • hideshow 1 child comment
  • when can I get the motorola flagship

  • source
  • 5 comments in c/android@lemdro.id view that post
    [–] 11 points 2 months ago

    Lenovo desperately needs to collaborate with Graphene to rebuild its reputation after being exposed for secretly collecting data on Moto phones at the system level.

  • source
  • [–] 4 points 2 months ago

    The RCS addition to messages would be lovely, it is unfortunately one of the few features keeping me reliant on Google messages.

  • source
  • [–] 3 points 2 months ago (2 children)

    Hm feels a bit like wasting resources. There are plenty of replacements available for the apps they plan to rewrite.

    On the other hand there are areas where we have no good at all or parts of the OS where apps don't cut it. Focus on these gaps instead.

  • source
  • hideshow 2 child comments
  • [–] 4 points 2 months ago (1 child)

    Are there plenty of replacements? The only RCS implementation on Android that I know of is Google's. The gallery and keyboard are practically unchanged in about a decade. Finding good keyboards is difficult, especially if you need languages besides English. I ended up installing a keyboard with too many permissions from Google Play and just blocking the extra permissions.

  • source
  • parent
  • hideshow 1 child comment