Inital version of this edition

loopandlearn · Jun 2, 2024 · 659ea23 · 659ea23
1 parent ae2dde2
commit 659ea23
Show file tree

Hide file tree

Showing 3 changed files with 104 additions and 41 deletions.
diff --git a/docs/edition/2024-06-02.md b/docs/edition/2024-06-02.md
@@ -0,0 +1,80 @@
+## Welcome to News from&nbsp;_<span translate="no">Loop and Learn</span>_
+
+_Master Your DIY Closed-Loop Insulin Delivery System_
+
+Published on 2 June 2024.
+
+## In this edition:
+
+* [*Zoom* Sessions](#upcoming-zoom-sessions)
+    * [Omnipod 5: Panel Discussion](#omnipod-5-panel-discussion)
+* [WatchOS 10 Tips](#watchos-10-tips)
+* [Cautions to Keep in Mind](#cautions-to-keep-in-mind)
+* [Helpful Links](#helpful-links)
+
+## Upcoming *Zoom* Sessions
+
+_<span translate="no">Loop and Learn</span>_: Informal Discussion in 2024 is normally scheduled on the second Thursday of each month; but will happen one week early in June.
+
+###  _<span translate="no">Omnipod 5</span>_: Panel Discussion 
+
+The second Thursday in June is a special panel discussing Omnipod 5, one year later.
+
+*Zoom* Sessions use this link:
+
+* [https://us06web.zoom.us/j/89085412738?pwd=eXpTN2M5V3M0TEVJQktmVldBTVRYUT09](https://us06web.zoom.us/j/89085412738?pwd=eXpTN2M5V3M0TEVJQktmVldBTVRYUT09){:target="_blank"}
+
+| Topic | Recorded? | Time | Date |
+| - | - | - | - |
+| _<span translate="no">Loop and Learn</span>_: Informal Discussion | no | 18:00 UTC | 6 June |
+| _<span translate="no">Omnipod 5</span>_: One Year Later: Panel Discussion | yes | 18:00 UTC | 13 June |
+
+#### Time Zone Converter
+
+Need help figuring out when an event happens in your time zone? Try the [SavvyTime: UTC Converter](https://savvytime.com/converter/utc){:target="_blank"}.
+
+## WatchOS 10 Tips
+
+Some people report trouble getting their app to show on their *Apple* watch.
+
+A page was created on the _<span translate="no">Loop and Learn</span>_&nbsp;website. Head over to [WatchOS 10](https://www.loopandlearn.org/2024/05/30/watchos-10){:target="_blank"} for help.
+
+## Cautions to Keep in Mind
+
+### Beware of AI Hype for T1D Management
+
+Recently, there's been excitement about using artificial intelligence (AI) to help manage Type 1 Diabetes (T1D). Some companies even charge around $20/month for these services, which are being advertised on various platforms, including Facebook.
+
+### Beware of YouTube Infotainment videos
+
+We've also seen videos by DIY "experts" who really aren't experts. Their videos contain inaccurate information even though the presenter seems knowledgeable. In contrast, our videos may not be sexy or entertaining, but they are always hosted by experts and content is always reviewed before it gets posted.
+
+### What should you do?
+
+Be skeptical.
+
+Even though many of us successfully manage T1D, the chronic nature and constant need for monitoring can create significant emotional stress. This stress makes us more susceptible to quick fixes or miracle cures. Our desire for solutions can make us vulnerable to charlatans or unproven therapies.
+
+The vast amount of information available online can be overwhelming. Differentiating between credible sources and misinformation can be challenging, especially when sensational claims are involved. Voices that used to be credible may now be tainted by financial motivation.
+
+Managing T1D effectively requires a balance between leveraging new technologies and relying on proven, evidence-based practices. Stay vigilant and make informed decisions about your health.
+
+## Helpful Links
+
+* [Subscribe](https://www.loopandlearn.org/newsletter-signup/){:target="_blank"} to get the Newsletter delivered to your email weekly.
+    * Some articles in the [original Newsletter](https://www.loopandlearn.org/2022/10/19/loop-and-learn-newsletter/){:target="_blank"} are not reproduced here
+* [Check for Updates](https://www.loopandlearn.org/version-updates/){:target="_blank"}
+* [Find a Health Care Provider who will support your use of&nbsp;<span translate="no">Loop</span>](https://www.loopandlearn.org/hcp-recommendations/){:target="_blank"}
+* [_<span translate="no">Loop and Learn</span>_&nbsp;Resources Page](https://www.loopandlearn.org/resources/){:target="_blank"}
+* <code>Loop</code>:
+    * [`LoopDocs`](https://loopkit.github.io/loopdocs/){:target="_blank"}
+    * [`LoopTips`](https://loopkit.github.io/looptips/){:target="_blank"}
+    * [`Loop` Zulipchat](https://loop.zulipchat.com/){:target="_blank"}
+* <code>iAPS</code>:
+    * [*iAPS* Website](https://www.iaps-app.org/){:target="_blank"}
+    * [*iAPS* Documentation](http://iapsdocs.org/){:target="_blank"}
+* <code>Loop and Learn</code>
+    * [Website](https://www.loopandlearn.org/){:target="_blank"}
+    * [*Facebook*](https://www.facebook.com/groups/LOOPandLEARN){:target="_blank"}
+    * [*Instagram*](https://www.instagram.com/loopandlearn/){:target="_blank"}
+    * [*YouTube*](https://www.youtube.com/c/loopandlearn){:target="_blank"}
diff --git a/docs/index.md b/docs/index.md
@@ -2,20 +2,23 @@
 
 _Master Your DIY Closed-Loop Insulin Delivery System_
 
-Published on 26 May 2024.
+Published on 2 June 2024.
 
 ## In this edition:
 
 * [*Zoom* Sessions](#upcoming-zoom-sessions)
-* [We’ve Lost a Friend](#weve-lost-a-friend)
-* [When Does My *Loop* App Expire?](#when-does-my-loop-app-expire)
-* [Remote Entry Issues in Nightscout](#remote-entry-issues-in-nightscout)
-* [Hacks From Our Experts](#hacks-from-our-experts)
+    * [Omnipod 5: Panel Discussion](#omnipod-5-panel-discussion)
+* [WatchOS 10 Tips](#watchos-10-tips)
+* [Cautions to Keep in Mind](#cautions-to-keep-in-mind)
 * [Helpful Links](#helpful-links)
 
 ## Upcoming *Zoom* Sessions
 
-Note - Informal Discussion is the first Thursday in June. A special event will be announced for the second Thursday in June.
+_<span translate="no">Loop and Learn</span>_: Informal Discussion in 2024 is normally scheduled on the second Thursday of each month; but will happen one week early in June.
+
+###  _<span translate="no">Omnipod 5</span>_: Panel Discussion 
+
+The second Thursday in June is a special panel discussing Omnipod 5, one year later.
 
 *Zoom* Sessions use this link:
 
@@ -24,58 +27,37 @@ Note - Informal Discussion is the first Thursday in June. A special event will b
 | Topic | Recorded? | Time | Date |
 | - | - | - | - |
 | _<span translate="no">Loop and Learn</span>_: Informal Discussion | no | 18:00 UTC | 6 June |
-
-_<span translate="no">Loop and Learn</span>_: Informal Discussion in 2024 is normally scheduled on the second Thursday of each month; but will happen one week early in June.
+| _<span translate="no">Omnipod 5</span>_: One Year Later: Panel Discussion | yes | 18:00 UTC | 13 June |
 
 #### Time Zone Converter
 
 Need help figuring out when an event happens in your time zone? Try the [SavvyTime: UTC Converter](https://savvytime.com/converter/utc){:target="_blank"}.
 
-## We’ve Lost a Friend
-
-Terry Witt was a very nice person and an asset to the looping community. He helped countless people through his role as a moderator in the Nightscout group and around the looping community and was always so pleasant during LnL meetings and open mics. Terry passed away on May 11th and we will miss him. His son Jason shared this [post](https://www.facebook.com/tlwitt46/posts/pfbid0rSg44dbEuiEpo1Ksno96Sr41o2JYsCg7WLtngS8eUHve8y29nzHRMTkAvLH71tjPl){: target="_blank" } on Terry’s Facebook page as well as his [obituary](https://www.legacy.com/us/obituaries/name/terry-witt-obituary?id=55121644&utm_source=webshareapi&utm_medium=share_button&utm_campaign=wsapimobile_beta#obituary){: target="_blank" }. Please feel free to express your condolences and share stories about Terry on his page- his family would love that. The family invites donations to the [American Diabetes Association](https://diabetes.org/?form=FUNSQWPTUDZ&utm_source=legacy&utm_medium=display&utm_campaign=fundraising-wefight&utm_content=clio-link&utm_term=prospecting){: target="_blank" } in his memory, continuing his commitment to supporting those living with diabetes.
-
-## When Does My *Loop* App Expire?
-
-If you used a Mac to build, you have one year from the date of build... but you should rebuild more often than annually. Why? Because it helps you know the app better and be more confident in your building capabilities. This is highly valuable if you should find yourself in a pinch for time. It also affords you the opportunity to update your app and add new helpful customizations.
-
-If you did a Browser build, the app expires in 90 days due to TestFlight limitations. Browser builders, however, have the very handy capability of triggering a rebuild from their phone. 
-
-* The `main` branch, version 3.2.3 does not report the TestFlight expiration date in the *Loop* app
-    * There is a [customization](https://www.loopandlearn.org/custom-code/#tf-expire){: target="_blank" } that you can add to your build that provides the correct expiration for you
-    * Alternatively, you can [build the `dev` branch](https://loopkit.github.io/loopdocs/gh-actions/build-dev-browser/){: target="_blank" }, which is very stable and should soon be released as the next version
-    * If you do choose to build this version before it is released, please switch back to building the `main` branch after the release
-
-* The `dev` branch, if selected as the default branch for your fork, is configured to automatically rebuild the *Loop* app at least once a month or within a week after an update is published
-    * You can [modify the schedule](https://loopkit.github.io/loopdocs/gh-actions/automatic/){: target="_blank" } for automatic rebuild as desired
-
-Regardless of which browser build `branch` you select, you can always check TestFlight to see when your *Loop* app will expire and make sure you have a new version to install so you are not left without your automatic insulin delivery system.
-
-## Remote Entry Issues in Nightscout
+## WatchOS 10 Tips
 
-Are your remote entries not showing up in Nightscout- and then ones you “didn’t enter” show up the next day? Here’s what’s happening to at least some of us: The default date for Event Time is the UTC date, although it uses local time for time of day. If a time of "Now" is selected, this information is ignored, so it works- unless it’s after 6pm local. Then it looks like the entry doesn’t take, but it’s really being entered for the next day at that time. This looks to be true for all types of events, not just remote carbs. Requests for code change to correct this have been submitted.
+Some people report trouble getting their app to show on their *Apple* watch.
 
-## Hacks From Our Experts
+A page was created on the _<span translate="no">Loop and Learn</span>_&nbsp;website. Head over to [WatchOS 10](https://www.loopandlearn.org/2024/05/30/watchos-10){:target="_blank"} for help.
 
-### Hack #1: Overrides
+## Cautions to Keep in Mind
 
-One of our group experts shares a clever way to use Overrides: Set an active override to run indefinitely and look at the ICE screen. You can tinker with the percentage to tune current/ future sensitivity by getting the ICE screen happy for past carbs! For this to work, you need to restart the app between changes. This technique really shines during sickness when you know needs are higher, but aren’t sure how much higher ahead of time.
+### Beware of AI Hype for T1D Management
 
-### Hack #2: Overrides
+Recently, there's been excitement about using artificial intelligence (AI) to help manage Type 1 Diabetes (T1D). Some companies even charge around $20/month for these services, which are being advertised on various platforms, including Facebook.
 
-One other group expert says: I set my biking override to be longer than my expected ride. When I return, I edit the insulin needs from 65% (needed while I'm actively biking) back to 100%. My negative IOB typically doubles at that change. I then disable the override and take the full negative IOB as a bolus. This helps prevent a post-exercise high that often follows my ride.
+### Beware of YouTube Infotainment videos
 
-I do not enter any carbs while biking and almost always ride first thing in the morning while fasting, so I just edit the override. If no carbohydrates are active, there is no need to quit and restart the app. (This idea is included in the [“Recalculate When Needs Change”](https://loopkit.github.io/loopdocs/operation/features/overrides/#recalculate-when-needs-change){: target="_blank" } section of LoopDocs.)
+We've also seen videos by DIY "experts" who really aren't experts. Their videos contain inaccurate information even though the presenter seems knowledgeable. In contrast, our videos may not be sexy or entertaining, but they are always hosted by experts and content is always reviewed before it gets posted.
 
-### Hack #3: Premeal
+### What should you do?
 
-Pro Tip: Engage the Premeal Override before getting out of bed to assist with Foot to Floor rises.
+Be skeptical.
 
-### Hack #4: CGM Issues
+Even though many of us successfully manage T1D, the chronic nature and constant need for monitoring can create significant emotional stress. This stress makes us more susceptible to quick fixes or miracle cures. Our desire for solutions can make us vulnerable to charlatans or unproven therapies.
 
-Try this if Dexcom loses signal for a prolonged period: Restart the phone, remove the Dexcom device(s) from bluetooth, look for a pairing request and accept it.
+The vast amount of information available online can be overwhelming. Differentiating between credible sources and misinformation can be challenging, especially when sensational claims are involved. Voices that used to be credible may now be tainted by financial motivation.
 
-If you want to enter glucose manually in your *Loop* app because your Dexcom G6 CGM is off, first delete CGM from Loop and then can use HUD -or you can enter directly into Apple Health and not wait 15 minutes for the last CGM reading to be reported as stale. If using Dexcom G7, enter it in the G7 app and it will show up in Loop without the need to delete the CGM.
+Managing T1D effectively requires a balance between leveraging new technologies and relying on proven, evidence-based practices. Stay vigilant and make informed decisions about your health.
 
 ## Helpful Links
 

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -94,6 +94,7 @@ use_directory_urls: !ENV [CHECK_BROKEN_LINKS, True]
 nav:
 - Current: 'index.md'
 - Edition by Date:
+    - '2024-06-02': 'edition/2024-06-02.md'
     - '2024-05-26': 'edition/2024-05-26.md'
     - '2024-05-12': 'edition/2024-05-12.md'
     - '2024-04-30': 'edition/2024-04-30.md'