Skip Navigation

‘Right to Repair for Your Body’: The Rise of DIY, Pirated Medicine

Sharing because I found this very interesting.

The Four Thieves Vinegar Collective has a DIY design for a home lab you can set up to reproduce expensive medication for dirt cheap, producing medication like that used to cure Hepatitis C, along with software they developed that can be used to create chemical compounds out of common household materials.

132 comments
  • OK, this is only tangentially related but it has been on my mind lately and I need to rant:

    I am T1 diabetic. Over the last decade, a LOT has happened to improve my life, especially in regards to no longer needing to check glucose levels with blood, as glucose sensors you wear on your arm have become ubiquitous.

    It started with a dedicated device that you needed to hold up to the sensor to get a reading (much nicer than pricking your finger) to that sensor being able to notify the dedicated device of high/low glucose values (yay! Sleep through the night, knowing you'll be woken up if something is wrong) to the sensor now constantly streaming glucose values to your phone.

    Which is fantastic.

    In theory.

    In practice, there are two companies making these sensors (OK, there's a couple more, but they suck way more and are much less commonly used).

    And both of their closed-source apps suuuuuuuuck. They do the bare minimum and nothing more. (Actually, it's worse than that. Ask me if you want to know. It's its own rant.)

    Then there's xdrip+, a FANTASTIC app made by diabetics for diabetics. Instead of just showing you "this is your glucose" and sounding an alarm, once, when it's required, you can (just off the top of my head): Set an arbitrary amount of alarms with their own behaviors, which can be configured to vary by time of day; show the glucose everywhere (notification, lock screen, home screen,...); mute alarms for a custom time; do not sound an alarm if you're trending in the correct direction fast enough; do not sound the alarm multiple times if your are jittering around the threshold; notify other people automatically in case of emergency; and roughly 1000 things more. The app is well maintained, and of course open source.

    Can you guess what the problem is?

    That's right, manufacturers disapprove of using this app. For the worse one of the two sensors mentioned, the community reverse engineered the communication and it is now working perfectly with the app. For the better sensor, they can't and won't due to fear of legal repercussions.

    It's my health. And I need to decide between worse hardware and useless software.

    There's no technical reason for this. I dream of the EU passing a law that requires manufacturers of wearable medical devices to publish the comm protocols and to legitimize use of third party software.

    Rant over.

    • . (Actually, it's worse than that. Ask me if you want to know. It's its own rant.)

      Mind enlightening us? It could be useful to compare against, for those of us who haven't used those kinds of apps before.

      • Sure!

        The two sensors and apps of the same name I'm complaining about are the Freestyle Libre 3 and Dexcom G7. IMO, absolute bare minimum for what is required in an app of this kind is:

        • get the glucose level from the sensor and show it in the app, incl. a history graph (even the old dedicated handhelds did this)
        • play an alarm when that value is below/above a low/high glucose threshold

        The Freestyle Libre 3 does this, and absolutely nothing more. They ported the software from their dedicated device to Android and called it a day. Frustratingly, this means that you don't even get your current glucose in the notification area, or the lockscreen, or anywhere else. You have to open the app. You can set the alarm thresholds arbitrarily, but only get 1 high and 1 low alarm setting. Disabling these means you need to go two levels deep into the settings menu. And you WILL be doing that, constantly. Why? Imagine this: You get woken by an alarm for high glucose. You check the app, and see that you've just barely crossed the threshold, but have been hovering below it for the past hour. You take insulin, but of course, that takes time to act. Since sensor measurements are a bit jittery, you can count on the glucose level to dip back below, then back above, below, above,... the threshold for the next 1-2 hours. The app will blare an alarm at the highest volume your phone is capable of every. single. time. Your (and potentially your partner's) sleep will be interrupted IDK how many times, unless you completely disable the alarm. Be sure to remember switching it back on in the morning, though! :) The fix would be incredibly simple: either allow muting alarms for a set period of time, or don't play an alarm if it has recently been played and the amplitude of glucose measurements is small.

        On the flipside, if you miss an alarm - say you are speaking in a meeting so you swipe away the blaring alarm - you will not be reminded again. My high glucose alert is/was set rather low (150 mg/dl) because that's the point where it makes sense for me to take additional insulin. If that alarm goes off and you dismiss it, it will not go off again (unless you first dip below, as discussed). Doesn't matter if two hours later you are at 160 or 380. Sure, it is also my responsibility, I am not denying that. But again, adding this feature would have been hugely helpful and so, so easy to implement.

        Let's take a quick sidebar and talk about hardware. The Freestyle Libre 3 is an AMAZING piece of hardware. It's incredibly tiny - about two pennies stacked, both in diameter and height. Still, it sticks to your skin very well, and measures and sends your blood glucose to your phone via Bluetooth every minute for two weeks straight before the battery gives out. As if that weren't enough, it's also so well-made that in the almost two years I was using it, I did not have a single unit that was defective or ran out of battery in less than the promised two weeks. It's fantastic.

        ...but sending glucose info every 60 seconds is also a drain on your phone's battery, especially if your app isn't, uh, made well. Take a guess as to where this is going. Ready? Wrong, it's worse. If I would go to bed with 100% battery, I would wake up with 40% left. I needed to charge my phone 4 times a day. Since switching to the Dexcom G7 (imperfect as it is - we will get to it, I promise), that is back down to once a day.

        Apart from draining the battery, the app is also slow, and gets really slow the longer you have it installed. This mainly shows itself in the glucose graph being slower to render over time. Deleting the apps data, i.e. starting fresh, makes everything run reasonably fast again. Over the course of a couple of months, a couple hundreds of megabytes of app data accrues, and the app starts to crawl instead of run.

        The next part is pure conjecture on my part, but I am still going to share it. My theory is that every time you open the app, the entire graph history is computed from scratch. That would explain the amount of data <-> slowness relation, and probably at least partially account for the battery drain.

        In short: Freestyle Libre 3 (the hardware) is fantastic, Freestyle Libre 3 (the app) does the bare minimum and sucks at it.

        You can not use it with xdrip+, except by installing a cracked version of the original which exposes the current glucose level through a webserver on your phone, and an additional app which grabs the values from there and passes them on to xdrip+. This is error-prone and does not exactly help with the battery drain.

        On to the Dexcom G7. In the next comment, because apparently there's a 10k character limit on comments.

    • It’s its own rant

      I sympathise with the state of diabetic sensor apps, but can I just say that it makes me so happy when people understand and use correct grammar.

    • That fucking sucks, and as someone who wears hearing aids it’s very relatable. Hearing aids are an investment that last about 5-10 years. As a teenager I got some demo units, then when I absolutely couldn’t keep them working anymore about a decade later and had the money I upgraded them.

      In practical terms this is about 15 years of advancement, and it shows. Gone are the days of molds of your ear, replaced by little domes that rest in the canal. But more relevant to the story, you used to have about a week per battery, and very little tech beyond some computation, volume adjustment, phone mode, etc. To turn them off you’d take out the battery.

      My current ones didn’t have options for removable batteries, only rechargeable, nor for if you have Bluetooth. You can control volume on the device and that’s it, the rest is in an app. Now overall this has been better than I thought it would be. Tv gets beamed into my ears, as do phone calls. My batteries never die unexpectedly.

      However, I hate that app. Partly it’s having to pull out my personal phone at my desk to turn my ears off (open offices are the root problem but sometimes I just can’t do sound at the moment, a common experience for the hard of hearing). I also dislike how there’s no custom naming for modes (meeting mode is called church mode because hearing aid manufacturers don’t understand that not all deaf people are elderly).

      But mostly it’s the damn Bluetooth, that wonderful terrible Bluetooth. There is no “search for new devices” option, it happens automatically when removing from the dock/charger as part of turning on. But worse than that there’s no “forget device” option. And any time a device sends messages to the hearing aids it prioritizes most recent. This is a dangerous combination with apartment living. It’s unlikely to go bad, but for me it did and holy hell it was frustrating to have less control over my medical devices than headphones. I couldn’t wear my hearing aids at home until my audiologist got in contact with the manufacturer and reset the devices because randomly my tv, audiobook, or amplification of my wife’s voice would cut to my neighbors device where they were clearly frustrated because they’d be turning it off and on and I’d be swapping my device in app and it’d get switched back as new device tries talking… It was clear that the designers were too afraid of the users breaking things by having control to allow us to fix things that “just worked” their way into a real problem. And if I weren’t a technologically skilled young woman I probably wouldn’t have been able to sufficiently describe the problem to get it solved

      • You just described every problem I've ever had with my Bluetooth headphones... I'm just about ready to throw them out because I take meetings constantly, and somehow my headphones are never connected to the right thing...

        I hate Bluetooth with a passion, and I'm so sorry you have to deal with that for your hearing aid.

    • My wife is T1 too and I wholeheartedly agree. The development in that area is outrageously slow and locked down (and then there's healthcare providers with whom you have to fight tooth and nails to get your ancient pump upgraded - another story and country-specific).

    • Can xdrip control the dispensing of medicine or just do monitoring and alerting?

  • By far one of the most interesting articles I've seen on Lemmy so far, thanks for the link

    • 404 Media is doing excellent work; if you like this kind of thing you might want to sign up for their newsletter.

132 comments