Hi all. I’m Dan. You can message me on Matrix @danhakimi:matrix.org, or follow me on Mastodon at @danhakimi.

You might want to check out my men’s style blog, The Second Button, and the associated instagram account

  • 1 Post
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle

  • If you are willing and able to enter a partnership like Samsung, you can do it fully (including encryption support etc).

    Samsung can interoperate. We cannot. We cannot enter into partnerships with Google. We are people, Samsung is a massive corporation. You understand the difference, right? Google will not let us access their servers. They’re not making it difficult, they’re not making it possible at all.



  • Matrix is the federated messaging network. It’s also end to end encrypted, although people have pointed out issues with server security and with metadata—which is why they’re working on peer to peer tech.

    RCS is not similar to any federated technology at all. It’s operated exclusively by Google in the US and most other countries. The technology was created, from the ground up, for carriers. But even carriers couldn’t actually make it work in practice, so they asked Google to take over. It’s a fucking albatross. We, as a society, need to drop it.


  • danhakimi@kbin.socialtoAndroid@lemdro.idIs RCS an open standard?
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    9 months ago

    Google is the exclusive RCS provider for all carriers in the US and many other countries. The desire for an AOSP android API is for developers to be able to write clients the way they do SMS clients, not to replace Google’s servers—that’s a pipe dream. IIRC, Google actually helped Samsung develop RCS support in their app. I’m not sure why it’s so difficult to implement.



  • It’s kind of open. It’s pretty much open for carriers to implement on the server side, and for OEMs to develop on the client side. There is an open source client in AOSP’s RCS Test App, but for one reason or another, as far as I know nobody’s attempted to implement it in an actual usable client app. I don’t believe there’s a server reference implementation. And, in the US, all the carriers’ RCS services are run exclusively by Google, so there’s no real point in attempting to set up your own server. Apple might be able to navigate the politics with carriers and with Google to make something work, if it wants to, but it’s really not a standard for us to play with.

    Use Matrix Instead.




  • I found, ages ago, that I never used the google app for something I couldn’t do in my browser. Like, this was back in the days just after Google Now died—all the features that almost worked just got scrapped because they really didn’t work. It allowed me to keep up with one college sports team, but other than that, opening the app was just a slower version of opening up my firefox and searching there.

    So that’s what I do now. I disabled the Google app, and I don’t miss it at all.


  • I disabled the google app years ago. I use my browser for search, and then when I get the results, the results actually show in my browser, and I don’t have to switch apps or anything to get to my browser.

    Plus, I don’t have to look at the vestiges of all the features the app used to have, which now just feel like they’ve left the UI cluttered and pointless.

    Plus, every time I open the app, I feel like I’m being spied on, because I am.

    Plus, Google Assistant sucks ass. The voice commands are super unreliable, and as for search, I don’t want AI to guess what I’m trying to search for, deterministic imperative searches are actually better.