I think it’s too late for this to be useful. Number spoofing is ultra-common these days and most of the unwanted calls I receive are from spoofed numbers that appear to come from local areas.
If we start blocking the spoofed numbers then eventually we’ll just be blocking every possible combination of digits that can exist.
What we really need first is better detection and blocking of calls using spoofed numbers.
I tried a similar scenario: The phone has a nfc reader built in, so I put the tag on the charger and tried letting the phone read it, but quickly discovered that android can’t/wont read nfc tags unless the phone is unlocked, which defeated the elegance of the solution. I hadn’t considered buying a standalone reader and attaching the tag to the phones, that sounds a lot more complicated.
Using an Automation APP like Tasker to turn off a Home Assistant-controlled smart plug when the battery exceeds a reprogramming threshold, might be a more reliable method & works for any device.
This is the method I have been using for years and it works great. I use Home Assistant to manage the automation, the Home Assistant client app for Android (you could use tasker for this) to collect the device telemetry to send to Home Assistant (how it knows when the battery hits 85% or drops below 70%).
I do want to point out there is one small downside to this method: your device charger (and I’m using an Anker wireless phone charging stand as my charger) only works for one device. Example, say my personal phone is charged up to 85%, so I take it off the charger, but my work-issued phone needs to be charged, but when I put my work phone on the charger nothing happens and it doesn’t charge because the charger is connected to a smart plug that’s turned off because my personal phone is charged up.
As much as I would LOVE to see them waste their money on this, we know they are all talk and no action and won’t actually contribute anything.
Not only did they NOT do a recall, they also did NOT execute any kind of customer outreach program to advise about the very real possibility of data loss. And then to just shit all over everyone, they put all the affected products on sale with deep discounts - presumably to sell them as fast as possible before the bad bress became more widely heard.
Yeah, this was predicted by everyone, long in advance. The surprising thing here is how long they’ve managed to cling to life. I expected them to be deceased by now. I didn’t think they’d last another three years, let alone five.
In the US, copyright is implicit. All work is instantly protected by copyright the moment it is created. Registering with copyright office is optional/voluntary. I think the judge’s comments that you are referring to was probably referring to the works where copyright protections were waived by the artists for works placed into public domain (which, on Deviant Art, covers a vast amount).
My system significantly exceeds all the performance requirements for Win11, but it doesn’t have the Trusted Platform Module 2.0…and therefore cannot run Windows 11. It’s disappointing that my system can run circles around a lot of newer devices but can’t upgrade because it’s running on an older motherboard. It’s dumb that Microsoft made TPM 2.0 a deal-breaking requirement for Win11.
76 down, ten thousand more to go.
I have a designated-remote job, but I’m also in a role that’s periodically customer-facing. For accounting purposes, the time I spend working from home in my home office is considered ‘remote’ and my time on-site at customer premises is considered an off-site event. Not sure how they do it at Dropbox, but that gives you an idea of how the time categorization goes.
This article desperately needs video.
Here’s the official video from Adobe. Bump to 45s into the vid to see the dress in action:
That’s the part of the point of the comment you are replying to. The fines are neither a deterrent nor an inconvenience to those wealthy enough to cover the cost. They use their money, power, and influence to continue to violate law without any other consequences other than pulling out their checkbook. The fines are meaningless to people that wealthy.
When Jerboa was having their version number problems, all of Lemmy was having version numbering problems
Well, not really. This was JUST a problem for Jerboa. There were some other 3rd party apps available for Lemmy and they didn’t suffer from the same problems. In fact, it wasn’t even a technical limitation of Jerboa itself… if you had previously installed and configured Jerboa when the instance version and the jerboa version matched, and then upgraded your jerboa app when your instance didn’t upgrade their version, it magically worked. The problem was when you installed Jerboa fresh and tried connecting it to a slightly outdated instance version - or if you wrecked yourself by clearing your jerboa cache/data folder without realizing that it would behave like it was starting fresh and break. The problem was solely in over-aggressive version checking during Jerboa startup…a total rookie mistake.
That’s about the time that half of all Lemmy users suddenly learned about the availability of some competing apps that didn’t have the same problems.
No, you’re not paranoid. I’d call it diligent.
The premise of the statement you quoted is faulty to the core. A device internal to your home network knows a lot about the design of your home network and it knows a lot about the other devices on your network, and it can be used to facilitate/relay malicious access to your other devices if it becomes compromised.
Wyze has always struggled with security problems…and I’ll admit that I do have several wyze cameras…but long ago decided their security was not trustworthy and created an entirely new virtual lan to run just my IOT stuff from. That, at least, reduces the exposure for some of their security issues. I certainly would never have interior cameras built by wyze - that’s too risky even with robust network security on my side of it.
It may have been rock-solid in the last few months since, but back when they were having their version numbering issues, I was a very new lemmy user and didn’t understand what the problem was (not that I should have had to)- the only thing I knew at the time was that other clients that I’d just learned about somehow didn’t have the same finicky version number problems as jerboa. It kind of wrecked my entire new-lemmy-user experience - especially since (as far as I know) Jerboa is kind of the semi-official client for Lemmy - it doesn’t need to have all the bells and whistles baked into more robust 3rd party clients - it just needs to be rock solid and run reliably as its only job, and it failed.
Jerboa used to hilariously break every time it was updated if your home instance was even a minor-sub-dot version number behind absolute latest. I couldn’t get rid of it fast enough. Connect and Liftoff are both great clients, I just happen to like Sync more. But, I do still keep Liftoff installed beccause it’s got some outstanding diagnostic tools if you are trying to see all pieces of data related to a post or comment.
Let me install my own third party apps w/o the App store (I know altstore exists, but needing to renew apps every few days is super janky). If I spend my money on a device, I should be allowed to put whatever I want on it, however I want. Let me, the consumer accept the risks of doing so.
This is THE reason I switched from Apple to Android in 2017 and never looked back.
It would also affect already sold units. They are giving apple 2 weeks to come up with a software fix to remediate already sold units and if apple fails to comply, they will force apple to recall all the iPhone 12s still in use.
The article says:
The French agency that regulates radio frequencies, the ANFR, has notified Apple of its decision to ban iPhone 12 sales after tests showed the Specific Absorption Rate (SAR) was above the allowed limit.
Followed by this quote:
The ANFR said it would verify that the iPhone 12 models were no longer being offered for sale in France starting today.
That sounds a lot like “banned” to me. Considering those two quotes, I don’t think the article title is misleading. It sounds like they are banning sales effective immediately, and will force apple to conduct a recall if they can’t retroactively fix the already sold units.
I’d never heard of STIR/SHAKEN…but after looking into it, supposedly T-Mobile was one of the first mobile carriers to implement it…and I’m on T-Mobile…but for the past several years, I keep getting unwanted spam calls to my cell phone that appears to be originating from very regional local numbers (area codes and number prefixes that are local to my area)…because of that I just assumed that they had to be spoofed since the calls are always an unwanted telemarketing robo call and never involve an actual business that is local to me.
So I don’t know how they are still doing it, but somehow telemarketers are causing calls to route through exchanges that are completely local to me.