It honestly like the most knowledgeable people are the worst to get useful information out of. They may think certain things are obvious, or link things together in a way that you don’t, so you can’t follow their internal thought process to fill in gaps.

I wish they’d do the same with me. Customer Support wears on your soul in a way most other jobs don’t come anywhere near.

And technical support becomes this weird combination of accuracy for troubleshooting and diagnosis, combined with a client that lies to you (often they don’t know they’re lying, sometimes they do) about the issue or what their role is with the issue. Actually now that I think about it, seems a lot like medicine. House actually has a lot of parallels with technical support.

You haven’t worked a customer service or support position before have you? Not everyone has the same explicit definitions for things. You don’t know what they consider the “screen” on their device. I worked in retail repairing phones for over a decade and saw customers refer to “screen” for every different component of the touchscreen assembly. and sometimes things completely unrelated to the display or touch at all. And that doesn’t even get into the possibility of language differences when we’re talking in an online community like lemmy.

At a separate job handling insurance replacements and reimbursements, I had a customer one time argue when processing a replacement TV for their current one that wouldn’t turn on. They were extremely insistent that it wasn’t broken. It wouldn’t turn on, but it wasn’t broken. Their definition of “broken” only meant physical damage, something just not working at all wasn’t broken. Hell, people still refer to the computer monitor as the computer, or the tower/box as the CPU.

We also don’t know how bad the damage to the screen assembly is without a photo at least. It could be that the LCD/LED is damaged and not clearly visible, but enough of it is still visible to enter your PIN if you can find a way around the touch interaction. We’re missing information, and making assumptions about the situation based on explicit definitions that you know doesn’t necessarily translate to an end user.

A broken touchscreen doesn’t mean you can’t see what’s on the screen. OP said its “unusable”, but we don’t know if that just means just the touch is unusable or if the actual LCD/LED is damaged as well.

Most people have no idea you can use a mouse or keyboard on the phone at all, so they’d consider the touch not working to mean the entire phone is unusable since they can’t interact with it the one way they’ve ever used.

We just don’t really have all the information, we don’t need to be making assumptions that could easily be wrong as well and ignore possible easy solutions for their problem.

Hitler was a drug addict and the trains didn’t run on time.

German trains still don’t run on time. Can’t blame that one on the Nazis, that’s just a German thing.

There are plenty of step-by-step guides to run Deepseek locally. Hell, someone even had it running on a Raspberry Pi. It seems to be much more efficient than other current alternatives.

That’s about as openly available to self host as you can get without a 1-button installer.

Your point OpenAI? Weren’t you part of the group saying training AI wasn’t copyright infringement? Not so happy when it’s your shit being copied? Huh. Weird.

First rule, always have backups. Especially with an older drive, make sure anything you might need is duplicated somewhere else. Ideally off-site to prevent loss in case of things like burglary or a fire. Even something as simple as Google Drive or OneDrive.

Personally, I’d take a look at replacing it with an SSD if you can afford to, not only because of the age, but better performance. You may not notice slowness, but making the jump from a HDD to an SSD is still at least a little noticeable even on secondary drives from my experience.

See you say no apocalyptic event, but we’ve done almost nothing to slow climate change, and that will destroy humanity in less than a century much better than we can directly do ourselves. The event has already started, and we’re ignoring it.

App Pinning DOES NOT lockdown the device, even if you have it set to require a PIN to unpin, biometrics still work to unlock the device.

It also gives you a warning that personal data may still be accessible and the pinned app can open other apps. It specifically says “Only use app pinning with people you trust”… which is the exact opposite of the use case here. And app pinning is turned off by default, you have go go searching in the settings to enable the ability.

This is the biggest issue I have with them. The only way this will work in modern society where the police can’t be trusted, is if the ID is accessible while the rest of the device is locked down.

And that’s really only possible if Apple and Google integrate that directly into the OS.

Why didn’t they bring it out more often?

K…I’m sure nobody cares.

Well you’re objectively wrong, since clearly the one guy complaining cared enough to actually complain about it.

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.

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

So just like nearly everything the TSA does.

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.