[-] smiletolerantly@awful.systems 2 points 21 hours ago

journalctl -fu servicename

If I am concerned about a specific service, and can trigger the problematic behavior.

In my head it stands for "fuck you" ☺️

[-] smiletolerantly@awful.systems 35 points 1 month ago

"Confused Jellyfin / Subsonic noises"

[-] smiletolerantly@awful.systems 40 points 2 months ago

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.

[-] smiletolerantly@awful.systems 171 points 2 months ago

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.

40

Basically, the title. After years of inactivty, I'll be taking music (cello) lessons again, with my teacher of yesteryear, from whom I've moved half a country away.

She has suggested Zoom but is open to alternatives. I don't particularly like Zoom, plus I have a feeling better quality can be had through a custom solution - but I'm at a bit of a loss as to what exactly would be a good fit for this project.

Maybe Jitsi? Does someone here have experience with it and could tell me if it's possible to set something like a "target" audio quality?

For hardware, I basically have two options. Both are already in use, for different things, and have sufficient processing capabilities - albeit no GPU:

  • host everything at home. Plus: lowest possible latency from me to the server. Not sure how much that is worth though.
  • root server in the Hetzner cloud: much faster network speed. Again though, not sure how beneficial that is, the ultimate bottleneck will always be my upload speed (40Mbit)

OK, I realize that this post is a but of a random assortment of thoughts. I'd be really happy about suggestions and / or hearing about other's experiences with similar use-cases!

194
[-] smiletolerantly@awful.systems 88 points 4 months ago

Define "inside me"

[-] smiletolerantly@awful.systems 31 points 4 months ago* (last edited 4 months ago)

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?

[-] smiletolerantly@awful.systems 42 points 4 months ago

Laughs in nixpkgs

[-] smiletolerantly@awful.systems 33 points 4 months ago

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

28
submitted 5 months ago* (last edited 4 months ago) by smiletolerantly@awful.systems to c/selfhosted@lemmy.world

Hi,

not sure where else to post this. For a while now, I've unsuccessfully been trying to get WireGuard to work with Crunchyroll.

Setup is as follows:

  • dedicated server hosts a wg-quick instance in [neighboring country]
  • OPNSense acts as peer on a single IP
  • I have a rule for routing the entire traffic of some source device via that IP

This works just fine. Handshake successful, traffic is routed via the server. traceroute shows the server as the hop immediately after my device's local gateway. The connection is stable, and fast.

...except for Crunchyroll. The site / app itself is fine, but I can not, for the life of me, get a video to play. It just keeps loading forever.

I don't think this is an issue with CR recognizing that I'm not where I say I am - looking online, it seems pretty easy to use CR with a VPN. I've also tried from multiple other devices, all with the same symptom.

If anyone has suggestions, I'd love to hear them 😅

EDIT: ~~It was MTU. Had to manually set it to 1500 on both devices.~~

Nope, still the same issues. I was using the fallback interface there briefly.

EDIT: It WAS MTU related, I had to enable MSS clamping on the OPNSense.

[-] smiletolerantly@awful.systems 60 points 5 months ago

tar -xzf

(read with German accent:) extract the files

[-] smiletolerantly@awful.systems 64 points 5 months ago

Oof yeah. Finding a reddit thread with your exact query as the title, getting excited to see a comment, aaaaand... It's "This comment was deleted by EliteUltraEraser Premium TM. I value my privacy,...."

(I do get it though. And who knows, maybe this will actually help in the long run ~~and not just lead to increased usage of Discord communities so ask the same thing over and over and over again because they aren't fucking publicly searchable god I hate what Discord has done to the searchability of issues in the tech space~~?)

[-] smiletolerantly@awful.systems 31 points 5 months ago* (last edited 5 months ago)

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? 🥺)

[-] smiletolerantly@awful.systems 70 points 5 months ago

Racist. That's the adjective describing the father that's - somehow, miraculously - missing from the quoted excerpt.

view more: next ›

smiletolerantly

joined 7 months ago