My blood glucose monitor is not on the play store. So one dy next year I'll wake up and no longer be able to get that data...?

The number of "why do influencers always film in public" that I've seen leads me to believe that if they were filming in a restaurant instead, this post would not exist, but a "Social Media brainrot. That's why. They think they can just film anywhere." post in some other community instead.

Look, I agree, "fuck cars"; but eating and filming in the car you own is just not problematic beyond owning the car in and on itself, at all. There's plenty of valid car criticism to be had, you don't have to go looking for things to be enraged by.

Eh. Would you rather they sit in the restaurant and annoy everyone with their filming and talking?

On many trackers, you get "paid" for time seeded. Usually in the forms of bonus points or the like. You can then exchange these for improving your ratio (or a freeleech token, or an invite,...).

It's a system that also rewards keeping media available even if you are not uploading to anyone.

Also, keep in mind that often, a large part of the available content is freeleech (meaning leeching it doesn't affect your ratio), but seeding those torrents usually still does improve your ratio.

What are you talking about. Please clarify if this is actually true:

I don’t plan to access it anywhere but home.

This would mean that you only want to access Jellyfin when you, and the device you are watching your show/movie on, are at home, where the Pi/server also is.

Is this correct?

If so, then questions about VPN, Certificates, DNS,.... do not matter.

1. host Jellyfin on the Pi, e.g. with IP 192.168.10.20 on your local network
2. open the Jellyfin app on your TV/Phone/PC, connect to http://192.168.10.20:8096
3. done

Now you can access it at home, and only at home. I honestly fail to see where a VPN would even come into the equation here (again, if you wish to ONLY watch when you are at home, as you've said).

No, you are right. In your situation, Linux is just not an option - yet.

I think these posts are meant for the 95% of people that use a browser, and maaaaybe a mail client on their PC.

Photoshop/Illustrator will only ever get ported if enough people have already made the move that Adobe can't afford to ignore Linux any longer.

That being said, if those requirements are just for work, what's keeping you on Windows on your private devices?

"Confused Jellyfin / Subsonic noises"

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.

Start with Linux Mint. It should be a very pleasant and straightforward experience right out of the box, and is just in general very beginner friendly. I recommend to create a live USB (basically, download the ISO from the Mint website, then use something like Balena Etcher to put it on a USB stick). You can then boot off that stick, and try Mint out to your heart's content, without risking your Windows install or data at all.

Can I ask, what are the programs you wager you'll have to emulate through wine?

Laughs in nixpkgs

What this person said.

~ sincerely, a German

(Seriously though, the situation here is intense. Our minister of education is currently under pressure to resign by the scientific community (which she refuses to do) because her ministry was looking for ways to defund / revoke grants to 400 university researchers who had criticized the way in which a pro-Palestinian protest was handled. That's all it takes.)

I FOUND A STACK OVERFLOW QUESTIONS RECENTLY THAT WAS LITERALLY THIS!

Nr. 1 accepted answer (lots of years ago): something something plenty of information available on Google, no need for this thread

Nr. 2 answer (way fewer years ago): seeing as this is now the first Google result for anything relating to this, here's how you do it.

(shame I can't remember what exactly the question was. Please still believe me? 🥺)