chiisana

Google did not make RCS; RCS is made by GSM consortium as succession of SMS, Google extended it to add some extra features such as end to end encryption (but only when messages are routed through their servers).

China mandated 5G sold in China must support RCS, hence why Apple added support for this. Since Google is basically banned in China, you can pretty much bet RCS going into/out of China is going to be unencrypted.

So you’re basically stuck between getting inferior unencrypted messages, or routing everything through Google.

Avoid RCS like the plague.

It is easier to think of the SSL termination in legs.

1. Client to Cloudflare; if you’re behind orange cloud, you get this for free, don’t turn orange cloud off unless you want to have direct exposure.
2. Cloudflare to your sever; use their origin cert, this is easiest and secure. You can even get one made specific so your subdomains, or wildcard of your subdomain. Unless you have specific compliance needs, you shouldn’t need to turn this off, and you don’t need to roll your own cert.
3. Your reverse proxy to your apps; honestly, it’s already on your machine, you can do self signed cert if it really bothers you, but at the end of the day, probably not worth the hassle.

If, however, you want to directly expose your service without orange cloud (running a game server on the same subdomain for example), then you’d disable the orange cloud and do Let’s Encrypt or deploy your own certificate on your reverse proxy.

Looking great! I think it would be amazing if there are filters for processor generations as well as form factor. Thanks for sharing this tool!

If anyone is responsible to keep things around for 100+ years, they’d have a job to do… and even then, cloud providers will still make their life significantly easier than juggling a bunch of storage mediums that goes in and out of storage medium fashion.

You’ll be very hard pressed to find anything else that’d out last the day when all three of AWS, Azure and GCP shutdown and take their data offline.

I get it though, Lemmy doesn’t want to admit these services exist other than to dunk on them in the most anti-corporate fashion… so continue to pretend such is the case!

Upload it to the cloud and make it someone else’s problem to deal with keeping up with the physical medium changes. Then your descendants only have to worry about figuring out how to deal with an outdated file format they can no longer open… and even when they can finally open it, it’d be super low quality… just like how we have to squint really hard at videos from VCDs now days.

It was not an EU thing, it was a China thing.

It’s quite obvious as well looking back at it; if course China will mandate one of the weakest protocol with no end to end encryption.

Avoid RCS like the plague and use something more secure!

Yep :(

The only reason Apple had gotten traction with it is because they focused all of their users’ purchase power in one unified place. Which became a powerful driver to drive for change. Samsung/Android/Google Pay/Wallet thing never gained traction despite having access to the chip is exactly what we’ll see if the chip just get opened up free for all. All the larger players will push for their own standard, demand for the coveted hardware invocation sequence, while no one else wants to adopt theirs, and ultimately get no where while littering our phone with useless apps.

¯\_(ツ)_/¯

If you didn’t read the article, Apple Pay is the ubiquitous one; Google floundered, flip and flopped but can’t get traction until Apple came around with it. Old or not, having a feature that no one cares about so you can’t use it anywhere makes it pretty useless.

Also, that’s exactly what I’m saying. I don’t want PayPal to launch one, then Walmart decide to push theirs, then local transit authority one, and all of them compete for the coveted hardware invocation. Instead, all of them should consolidate into one unified place via standard set of API + UI so none of them can make a mess. Guess that’s something Android users wouldn’t understand, judging from the piss poor IOT ecosystem and all ¯\_(ツ)_/¯

Opening up the chip is great, but there needs to be a standard way to consolidate them all into one app/interface. Much like how HomeKit brings everything into one place, the Wallet (or some updated API based variant) needs to remain the central place, so we don’t end up getting littered with vendor specific apps for different payment systems.

So just because they don’t know technology like you do, they should be left behind the times instead of taking advantage of advancements? A bit elitist and gate keeping there, don’t you think?

Everyone have their own choices to make, and for most, they’ve already decided they’d rather benefit from advancements than care about what you care about.

And here’s the reason why layman should not: they’re much more likely to make that one wrong move and suffer irrecoverable data loss than some faceless corporation selling their data.

At the end of the day, those of us who are technical enough will take the risk and learn, but for vast majority of the people, it is and will continue to remain as a non starter for the foreseeable future.