• 0 Posts
  • 56 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle
  • 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.



  • 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.


  • krayj@sh.itjust.workstoTechnology@lemmy.worldA guide to a longer lasting Smartphone.
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    11 months ago

    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.












  • 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.