IIRC, Apple implemented the original spec for RCS too, so none of the Google features like e2e will even work.
I’m disabling that shit day 1, I don’t need my messages sent over Google servers - not even if they were encrypted.
I don’t even know why telecoms in Europe even bothered, and neither do they. (I asked the RCS lead at one of them, and they agreed it was kind of pointless with signal, whatsapp, …. existing)
IIRC MySql inherits that behaviour when running on windows (or at least older versions do)
That was a real fun time when switching OS
I’m curious - if you want to listen high quality audio, why not get an actual audio player for that? Surely the DAC in some random android phone can’t be that good?
Also, the 1TB version is really only meant so they are actually somewhat usable for recording proRes or taking pictures in RAW
.eu and your local tld are often quite a bit cheaper too!
Wireguard (which is what tailscale is built on) doesn’t even require you to open ports on both sides.
Set up wireguard on a vps first, where it is accessible, then set it up from within your network. It’ll traverse NAT and everything, and you don’t have to open a port on your network.
Tailscale is the exact same thing, just easier because it does everything for you (key generation, routing, …). Their service replaces your vps, up to you if you think that’s acceptable or not. IMHO, wireguard is worth learning at least. I eventually (partially) switched to tailscale because I’m lazy, and all services I host have authentication anyway, with vpn just being a second layer.
Maybe technically, but in reality there’s just very few “good” tablets when it comes to hardware. Samsung has a few, but the rest’s just plastic trash.
No proper hardware, no sales, no tablet android users, no android apps for tablets.
I don’t see how this would fix that.
How? The sublinks devs started the project just because they didn’t want to work on Lemmy for whatever reason. If they did, they would have worked on Lemmy. It’s either Lemmy AND Sublinks, or Just Lemmy with the same developers.
Having multiple implementations is a good thing, regardless of what language they use. They all implement the same protocol, should be (mostly) compatible, and can learn from (and compete with) each other.
Look at other OSS. There’s so many Linux distributions, Why doesn’t everyone just work on a single one?
Because everyone has a slightly different view on things. This makes the OSS community stronger.
I have seen people wanting to do Java, and while I personally prefer rust, I do see why.
Outside of the entire Sublinks discussion, it’s important to note that Java is not just Java anymore either. Kotlin offers many of the same advantages syntax-wise that Rust does (including the lack of null), and has access to Java’s excellent ecosystem.
Ultimately, it is up to people to decide what they want to use. Regarding of your opinions on Java or Rust, it is a valid choice either way for this type of software. It’s a personal choice.
I’ve never really seen this in (Java/Rust/PHP) backend personally, only in client-side JS (the CORS preflight).
It’s a security feature for browsers doing calls (checking the CORS headers before actually calling the endpoint), but for backends the only place it makes sense is if you’re implementing something like webhooks, to validate the (user submitted) endpoint.
Even if that were true - does it matter?
Java is a perfectly valid choice for something like this.
Yes, Rust is “faster”, uses less memory, etc…
Java is fast enough, though. It offers a fantastic ecosystem and, seeing as these projects are ran by volunteers who do this in their free time, there’s a lot more people willing to chip in some work.
They don’t because it’s not true.
There’s a few things moving to quarkus, but a lot of that is being pushed by Redhat (whose own software was not even spring boot but JEE)
Kubernetes yes, but minikube is kinda meh as a way to install it outside of development environments.
There’s so many better manageable ways like RKE/Rancher (which gives you the possibility to go k3s),Kubespray or even kubeadm.
All of those will result in a cluster that’s more suitable for running actual workloads.
No, they’re not, but Google won’t get them (unless, as you state, they use google’s messaging app) Less Google, more better, in my opinion.
MMS hasn’t been a thing at my provider for years now, so want to send me an image? Use Signal or whatsapp (begrudgingly). I already rarely receive or send SMS, so not enabling RCS isn’t a big loss for me, I don’t get added to Google’s statistics (which they are so very proud off), and I won’t really miss any of its features.