Shine Get

  • 0 Posts
  • 108 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle







  • Only Google’s proprietary extension has encryption. The actual industry standard specification of RCS has no encryption defined at all.

    Edit: It turns out Apple have refused to use Google’s proprietary encryption implementation and are instead working with GSMA to update the RCS Universal Profile specification to finally have encryption defined and standardised so that any RCS client can handle encrypted payloads (whereas only Google Messages today can do encrypted RCS and requires other users to be exclusively using Google Messages otherwise messages are sent unencrypted).



  • Bingo. RCS is yet another proprietary protocol, one controlled by Google (GSMA who originally designed it have practically forgotten about it for a decade) and without an open specification. RCS also doesn’t have a standardised approach to encryption as it’s designed for lawful interception.

    So unless Apple have licensed Google’s implementation and extended version of RCS, this will be a shitty, insecure way to communicate between the Apple Messages and Google Messages apps and nothing more.

    Google did an impressive job applying pressure and suggesting RCS was a perfect solution when in fact it’s just putting more control in Google’s hands. RCS is not an open “industry” standard. You nor I as individuals can implement it without paying license fees to see the specification and fees to have our implementations tested and accredited.

    And Google have extended GSMA’s RCS with their own features (such as encryption) which is not part of the official standard and they haven’t made open either.

    If Apple had been pressuring Google to implement the iMessage protocol or whatever, we’d have been up in arms (and rightfully so).

    But instead of us all collectively hounding Apple and Google to ditch proprietary protocols and move to open ones such as Matrix, Signal, XMPP, etc (ones where we could all implement, use open source software clients, etc) we’ve got this shit:

    Proprietary, insecure, non-private communication protocols baked into the heart of hundreds of millions of devices that everyone is now going to use by default instead of switching to something safer, private, public, open, auditable, etc etc.










  • Linux has lots of flavors; and just like ice cream, you can have a scoop, see if you like it, and try another one later.

    I’ve been through so many Linux and Unix flavors over the years, it’s borderline absurd. But what was great is that I found a flavor just right for me and my needs, like finding your ideal car. Don’t worry about making the right decision on a flavor at the start, just dive in.

    Ubuntu, Fedora, Mint, Pop! OS, Manjaro, elementary OS, Zorin etc are great starting points. You’ll hear people bigging up Arch, Nix, Gentoo, Slackware, Void, etc. There’s are all great in their own way and very well might be the right thing for you but don’t feel pressured to jump in the deep end (unless you love that thing, then be my guest - Arch was a lot of fun getting it up and running for the first time).

    The best decision I can suggest is learning about mount points and having a drive dedicated to your files and simply mounting that drive inside your home directory. It means you can wipe and try another distro wherever you like without having to copy your files off and on over and over again.


  • I absolutely love this competition. Past submissions have been indispensable for adding excitement to campaigns in sessions I need a little help expanding when players go in a direction I didn’t anticipate (I love saying YES).

    I’m so glad to see this is back. I strongly recommend splashing out and buying past year’s compendiums - there’s so much gold in there you can easily tweak to fit into your games.