How I keep myself alive using Golang
Living with Type 1 diabetes is pushing technically inclined patients to build their own monitoring and automation stacks around continuous glucose monitors, often in Go, to work around locked-down manufacturer ecosystems and unreliable official apps. Commenters share experiences with tools like Nightscout, xDrip, Loop, and open-source “artificial pancreas” projects, highlighting both the safety and legal constraints faced by device makers and the strong desire of patients to own and integrate their real-time health data. The thread also touches on broader issues such as workplace stigma, access to advanced treatments, and language choices (Go vs. Rust, TypeScript, Elixir) when rapidly prototyping health-related services.
CGM Data Access and DIY Ecosystem
- Many commenters highlight how locked-down commercial CGM systems (Libre, Dexcom, etc.) are, especially around raw data and APIs, despite being the user’s own health data.
- Some report success with patched/third‑party apps (BYOD, xDrip, Juggluco, Diabox, xdrip4ios) and Bluetooth features in Libre 2/3 to get continuous readings and export data.
- Others note vendors can break unofficial integrations at any time; for long‑term reliability, people advocate fully open‑source stacks and reverse‑engineered solutions.
- Nightscout emerges as a de facto standard backend, with many integrations and add‑on apps, though some see it as messy and not infinitely scalable.
Custom Tools, Go, and Frameworks
- Several people are building their own T1D monitoring stacks: custom alerting, visualizations, tmux status icons, watch integrations, and full management apps.
- Discussion of Go vs Rust for web services leans toward Go for faster onboarding, simpler mental model, and good ecosystem; some suggest sticking with TypeScript unless the goal is learning.
- Go community is described as preferring small libraries over heavy “Rails‑style” frameworks, though tools like Encore and Fiber are mentioned.
Devices, Pumps, and Closed-Loop Systems
- Multiple setups are compared: Libre + MiaoMiao, Dexcom + xDrip + Nightscout, Dexcom + Omnipod + AAPS/iAPS, and commercial closed-loop systems (TSlim X2 ControlIQ, CamAPS, CamDiab).
- Closed-loop pumps are seen as a major quality‑of‑life improvement but often “too conservative,” keeping glucose higher than users would like; manual corrections remain common.
- DIY closed‑loop solutions (OpenAPS, Loop, AAPS/iAPS) are praised for flexibility but raise safety, regulatory, and support concerns, especially for children.
Medical, Workplace, and Mental Health Aspects
- Experiences vary on disclosing diabetes at work: some warn of discrimination and advise hiding conditions; others say it’s hard to conceal CGMs and injections, or report supportive employers.
- Parents of very young T1D children share the stress of management, school/preschool coordination, and fear during lows, but also big improvements from tech.
- Several diabetics describe emotional swings, long struggles to achieve good control, and the psychological weight of constant monitoring; peer groups and data‑driven approaches help some.
Other Health Tech and Side Topics
- CPAP/OSA data is compared to CGM data; people share how tuning masks, pressures, and analyzing CPAP logs was “life‑changing,” though not trivial.
- One thread speculates on environmental triggers for T1D; others link autoimmune disease to pollution and oxidative stress.
- Various tips surface (diet patterns, melatonin, supplements), but their effectiveness is based only on personal anecdotes.
- Some criticize auto‑generated AI art in tech articles as ugly and irrelevant to the subject.