By the way you do realise that Samsung's most major marketing feature is Bixby right? The thing I agreed with you is a cancer in this world? (How contrarian of me agreeing with you). And you think that means I work for Samsung?
Please don't use Slashdot drunk. Have some respect for intelligent conversation.
And yet I described a system. You should read the entire dictionary so that you're able to parse basic English.
Do you work for Samsung or are you just performatively being a contrarian?
I know it may be difficult for you to understand that everyone in the world is not you. Unfortunately for you some of us just have Samsung phones and devices, (and in my case a Huawei fitness tracker) and using Samsung apps is the path of least resistance for many.
One man's bloat is another man's important feature. I'm happy for you that you don't want to use these apps. Don't. It's your prerogative. However I'm less happy that people like you think your personal opinion and personal use case is the only one in the world.
So yes, I am a contrarian to you, I have a brain and recognise other people exist in the world.
It's not confusing at all. You said yourself it's a superset. And again it has a specific set of features that are fully backwards compatible. Google has zero control over RCS. Everyone can implement RCS as per the GSMA standard and send messages to and from Google devices with no issue. The fact that it doesn't support Google's end to end encryption has nothing to do with the standard and is of no impact to developers nor does it affect functionality of users.
False. The main problem was that Apple was deliberately degrading any message and capabilities related to RCS. It wasn't anything to do with encryption. They didn't implement some of the basic standard functionality, and when they did they also did client side degradations as well: e.g. auto-resize images to a significantly lower quality before sending them as an RCS vs an iMessage for absolutely no reason what so ever.
Just safer, not necessarily faster. OpenWRT is a great package, but the reality is that cutting edge routers do not support it. You want a top of the line 802.11be WiFi network expanded through your house with 802.11s mesh points, then good luck finding something that runs OpenWRT.
Don't worry though, in about 6 months
You are very optimistic regarding his or the government life expectancy, whichever comes first.
It appears that three AI companies are neck and neck: GitHub, Claude, and Cursor. https://www.cbinsights.com/res...
My experience is a bit different from yours. I personally use GitHub Copilot, which lets you use models from all the major companies, including Claude. Whenever I've tried Claude models, I get good results, but the execution is *S*L*O*W*. Like, 3-5 times slower than, say, GPT-5.4. So I keep reverting back (for now) to GPT.
At least Gemini is *trying* to tell the truth!
Isn't it???
And these are apparently huge ones, at that!
That sounds like sales gobbledygook to me!
This was literally my point about how security was built into Android and IOS. Neither one lets installers do anything to the OS, the package can only be unpacked in ways that are specifically designed by the installer mechanism. It's not a user permissions thing, it's an installer capability thing. In the phone world, you don't write an executable to do your install, you create a package, which the OS itself unpacks.
By contrast, a Windows or Mac OS or Linux installer, is just an ordinary executable under the hood, that can do anything the user running the code, has permission to do. Because you the developer provide the executable to do the installation, this is inherently a less secure installation mechanism.
And yet, microplastics (or any plastics) are not soluble in water and peroxide. So the body's ability to remove microplastics, as observed in this study (or at least as observed in the lack of buildup), doesn't seem to be related to solubility.
Nothing is finished until the paperwork is done.
