Thurstylark

Open source nerd

Reddit refugee. Sync for Reddit is dead, all hail Sync for Lemmy!

https://thurstylark.com/

  • 0 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • I think this might be a “yes, but no” kind of thing.

    Yes, these are test strips. Yes, they change color to indicate a reading. Yes, they use chemical reactions to cause that color change.

    AFAIK: No, these aren’t for testing blood. No, these don’t seem to be for consumption by an electronic meter. And no, I don’t think this is what OP was asking about.

    Like, there’s probably some good info, but not for this thread specifically :P

    Source: Pulling it straight out of my ass, but it is informed by my limited experience with medical test equipment, and much less limited experience with electronics.





  • I mean, random NFC tags, I can understand. But, isn’t advising someone to avoid QR codes obsolete by now? It was a pretty worthwhile attack vector at one point, but nowadays most phones will ask “Do you want to <handle> <contents in full>?” before actually doing anything with it…

    Although, now that I think about it, it is best practice to advise to the lowest common denominator… Sometimes I overestimate users’ ability to avoid doing stupid things…



  • Thurstylark@lemm.ee
    cake
    toLinux@lemmy.mlItag alternative?
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 month ago

    There’s probably a better way to do this, but I’ve just started using BLE Radar (F-Droid, Play Store), which can be set up to (among other things) tell you where your phone last saw a particular bluetooth address.

    You don’t get the benefit of the tracking network that iPhones, and now Androids, are a part of, and it’s not built into the base system, but it’s FOSS, and your location data stays local.


  • I agree that if there was enough space in the recovery partition to begin with, this wouldn’t be a problem, but the user isn’t the party that specified that size or the party that decided to add enough stuff to the recovery partition to exceed that spec.

    MS knows that this is a widely-deployed configuration (they deployed it), but they’re going ahead with an automatic update that is incompatible with that configuration anyway, failing to communicate to the user why the failure occurred, and refusing to automate a fix to the thing their automation broke in the first place.








  • They get paid when the least amount of people they insure use their services. They’re not incentivized to help those they’ve insured. The less they have to pay out to providers, the better the executive bonuses. Thus, they are diligent in collecting premiums, but can just sit on their hands when it comes to paying out.

    The more the system denies and delays a claim, the fewer insured people are willing or able to put themselves through the bureaucracy gauntlet, the fewer pay outs.

    They’re not in the business of insurance, they’re in the business of making money from the business of insurance. It’s over-complicated on purpose.





  • Ya know, this thread has inspired me. I’m a sound engineer, and find myself yelling “check one two three four” in the michrophone to test it all the time. I’m gonna start reciting the digits of Pi instead, and then as I learn them, I’ll progressively advance how many numbers of Pi that I use in my everyday job :D

    I work at a library, though. I should probably just go with poetry or Douglas Adams or something, but this makes me sound much more impressive