This is essentially what I did when I was laid off August last year. And it did take about that long to really be free of all the stress I’d racked up over the years in retail and other public customer-facing roles.

Marked as Spam, I’ll never see it again, and if enough people do they’ll get the entire email service blocked by your email provider since they’re actively hosting spam. And there’s not much more annoying and difficult than trying to remove a legitimate service from spam lists because some users abused it.

DLSS is an Nvidia technology, so of course it is.

A lot of those USB powered lights actually need 5v 2A chargers, which many older adapters aren’t capable of or could barely manage. So the light may work, but may be dimmer or end up slowly killing the adapter by trying to pull more power than it can really provide.

A good quality 5v 2A or higher adapter, like Anker, UGREEN, etc. is usually all you really need, not necessarily anything fancy with USB-PD support or multiple voltages.

Sounds that way to me.

Which means developers being expected by users to support installation and updating through systems they don’t use. Because we know that users have common sense and would never expect the unreasonable, especially from small devs.

They won’t, because the reason these are being implemented is because Google is considered a monopoly.

It’s not about making a fair playing field. Anti-monopoly stuff is about giving other companies advantages to help them compete.

Eh a lot of TOS bullshit is exactly that. And Apple is very far from perfect, especially with anything that could even think of threatening their walled garden. I assume everything Apple does is bad for the consumer, because 99% of the time that’s accurate.

So if I’m reading this correctly, this is only a change in One UI, which Samsung makes, and only affects their devices… So why is Google being sued other than for headlines?

Also, it’s still not blocked, just additional warnings educating users about security, or lack thereof with side loading.

Not really on Epic’s side here honestly.

I mean… This post literally includes the excerpt from the article about why. It’s literally the only thing in the OP other than the link itself.

So its not saving time, just costing money to increase surveillance.

So just like nearly everything the TSA does.

Makes sense. Most compromises aren’t brute force attacks. Allow all the characters and any brute force that is attempted will have to assume they’re part of it.

Removing required periodical changes means people are less likely to use the same password and just increment a number added to the end. A compromised password with a setup like that is still compromised, they can make an educated guess as to what the new number is based on when was compromised compared to now.

It’s also worth it to point out that, for people that care about supporting content creators but don’t want to or can’t afford to do so individually through services like Patreon, Youtube Premium views pay creators far more than a regular view.

If you’re impacted, it makes YouTube Premium more expensive than Spotify Premium and Apple Music.

I find this particular comparison interesting to bring up. A Youtube Premium subscription also includes a Youtube Music sub (at least in the US, not sure about everywhere else). Which theoretically makes those subscriptions unnecessary as well (ignoring differences in catalog, device availability, etc. of course).

Well we know for a fact that the US doesn’t even care about our own children dying. Why would we care about ones on the other side of the planet?

And we keep trying to reduce medical coverage and public funding for healthcare. Hospitals are being closed all over the US.

To be honest, it’s on brand.

We have seen the evidence for the things happening at places like the Chinese Uyghur internment camps directly, it’s not a claim where we have to trust a government without any proof.

Eh, no one else is doing anything to provide support apart from Google either. Anyone else could do their own thing, no one is prevented from their own support. But very few companies and carriers even began to develop support for RCS, even after the Universal Profile. That is why Google developed their own support and built that support into the native app.

Verizon had their own RCS support via a proprietary carrier-specific app that never worked with anyone outside Verizon as far as I remember, and they dropped it in favor of Google’s option as soon as that was available. Samsung had their own RCS support in their proprietary Messaging app, also dropped because Google provides the same support on all of their products and Samsung doesn’t have to do anything or support it in any way. Google now provides an option for all Android devices specifically because almost no one was adding support on their own.

Anyone can, no one else will, because they have no reason to. The average user doesn’t care whether it’s Google, their carrier, or the manufacturer providing support for sending high quality photos to their friend’s phone number as long as it works.

Samsung had support before Google and Jibe… but they have abandoned their own RCS support. Simply because Google’s works on all of their devices and they don’t need to do any development to support it going forwards. Why pay for development and support for a system you don’t have to and get nothing from? No one is buying a Samsung phone for the Samsung Messages RCS capability.

This isn’t done out of altruism.

I never said or even got close to claiming that it was.

But there is a distinct difference between Google taking a fragmented RCS implementation across carriers and manufacturers on Android devices, and providing a single universally supported option for Android (the operating system that they control, but don’t prevent others from modifying heavily)… and Apple actively trying to avoid RCS support entirely in favor of their own proprietary system that does not support any products they don’t make and sell directly. Verizon had their own RCS app on Android, and Samsung added RCS support to their Messaging app on their devices, among others prior to the Universal Profile and Google adding support directly in Android Messages. That’s not something anyone can do or offer for iPhones other than Apple

Google worked to add support for essentially all Android customers. Apple decided none of their customers should be able to use RCS, whether they want to or not, simply because they had their own thing that only their customers could use and won’t let anyone else use. You can’t possibly be trying to claim that Apple is in any way a good guy here. Comparing the two directly here, Apple is clearly worse with no good reasoning for it, it is entirely for selfish reasons.

And absolutely zero users care about the reasons. They only know that sending messages back and forth is dogshit.

The source of the lack of support across is Apple not wanting to even try because they want everyone to use their proprietary system on their devices instead. Google at least implemented a system to get RCS support to as many devices as they could, even when carriers didn’t do anything to help. Apple instead had to be threatened by regulators before they even began to consider looking at it.

Well I’ve been able to RCS with basically everyone on an android phone since 2019 with almost no issues. That’s 5 years now.

I don’t really care how Apple wants to try and justify it. The answer is they don’t want to add support for an alternative to their walled garden proprietary system that no one else can use. They want to force everyone onto an iPhone and iMessage if possible. The only reason they’re even looking at RCS support now is because of regulators starting to look at their glaring lack of support for interoperability.