Hello, everyone. This is the Circuit Python weekly meeting for January the 30th, 2023. My name is Tim, and I am sponsored by Adafruit to work on Circuit Python. The Circuit Python is a version of Python that's designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit, so if you want to support Adafruit and Circuit Python, consider purchasing hardware from adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to adafruit.it-discord. We hold the meeting in the Circuit Python Dev text channel, as well as the Circuit Python voice channel. This meeting typically happens on Mondays at 2 p.m. Eastern time, 11 a.m. Pacific time, except when that coincides with the U.S. holiday. In the Note Stock, there is a link to a calendar which you can view online or load that up in your favorite calendar app in order to get the schedule for the upcoming meetings. That's also another perk of the Circuit Pythonistas role on Discord, the same role that you need in order to be able to speak. If you do get added to that role, then you'll get a ping with upcoming changes to the meeting schedule and stuff like that. There is a Note Stock that accompanies the meeting and the recording. The Note Stock contains timestamps to go along with the video, so you can use the doc to view only the parts of the video that interest you most. The meeting tends to run 30 to 60 minutes or so, so that gives you the option to skip around. After each meeting, we post the link for the next meeting's notes document to the Circuit Python Dev channel over on Discord. You can check the pin messages to find the latest Note Stock there, and you can add your notes throughout the week as well, so you don't necessarily have to wait until Monday to put in your notes. If you happen to think of something during the week, go and hit that pinned message link right there in the Discord, and you can fill that stuff in all week long. The meeting is held in five parts. The first part is community news. That's a look at all things Circuit Python and Python on hardware in the community. It's a preview of the Python on microcontrollers newsletter. The second part is the state of Circuit Python, the libraries in Blinka. That one is a statistical overview of the entire project. It's a chance to look at the project by the numbers separate from what we're all up to. The third part is hug reports, and this is the first of our two round robin sections. The reports is an opportunity to highlight the good things that folks are doing, take some time to recognize the awesome folks in our community and beyond. The fourth part and the second of our two round robins is status updates. Status updates is an opportunity to sync up on what you've been up to. Take a couple of minutes, talk about what you've been doing in the last week since the previous meeting and what you will be up to in the next week until the next meeting. The fifth and final part of the meeting is in the weeds. In the weeds is an opportunity for more long-form discussions. These discussions can come out of status updates or they can be identified ahead of time as too long for status updates. If you happen to know of an in the weeds topic that you'd like to discuss, go ahead and scroll all the way down to the bottom of that note stock and just list it down there in the in the weeds section. That way we've got our topics all ready to go there when the time comes. So with that, we will move on to the community news section. So let me scroll just a little bit here and get the timestamp running. All right, community news. And our first item in community news this week is the CircuitPython <IP_ADDRESS> release candidate 1 has been released. CircuitPython 8.0.0 RC1, it's the release candidate for 8.0.0, it has been released. It is stable and developers are making a release candidate for further testing before the final release. There's a link here to Adafruit blog. The quick note for anybody that might be upgrading though, since 8.0.0 beta.6, which was the previous release that was out there, the file that you specify your Wi-Fi credentials and other environment variables has changed slightly. So this note's in the doc and there's a link for further information if you want to hit that, but just be aware, if you had previously set up the .env file for your settings and Wi-Fi information, you'll need to switch that over for the new version to use the toml file. If you've been working off of main or something, then you probably already have the new one. This is just if you were on beta.6 and have the .env file. Next up is Digikey and Make announce a new boards guide and companion augmented reality app. Digikey Electronics and Make have released an updated board guide and companion Digikey AR augmented reality app that's available for both Apple App Store and iOS devices as well as the Google Play Store for Android-based devices. Divided into sections for microcontroller, single board computers and field programmable gate arrays, MCUs, SBCs and FPGA-based boards, the guide helps students, makers and professional engineers identify the latest technology available to help bring innovation to life. There are links there to Digikey as well as the Adafruit blog. Next up is a milestone in the larger community. GitHub has hit 100 million developers and counting. So this week, GitHub posts that they now have officially more than 100 million developers using GitHub to build, maintain and contribute to software projects. They look a bit at what that means going forward and there are links there to the original GitHub post as well as the Adafruit blog. Next up is some projects. So this one is Project of the Week, which is a CubeSat that's using CircuitPython and MicroPython. First and second year engineering students at Harlow College, which is in Harlow Essex UK, have been busy designing and building a new CubeSat platform with the ultimate aim of getting their boards and designs in space, taking photos of the earth and beaming them back to the classroom. The CubeSat platform is based around the Raspberry Pi Pico, consisting of three parts to the design, an acquisition board loaded with a camera and various sensors and storage, a master controller board with a radio link, and a ground station containing a radio link and decoder software. All three boards use the Raspberry Pi Pico and the software is written with a mix of MicroPython and CircuitPython across the three boards. Last item from community news around the web this week was a tool called CircuitPython Upload. CircuitPython Upload is a simple uploader script for the CircuitPython web workflow. Basically call it with a host name and a password and it'll compare the local directory with the remote and upload the newer file. So this one caught my eye in the newsletter from this week, in particular because they mentioned using it in conjunction with PyCharm. They had it set up to where they were running this script from inside a PyCharm and kind of treating it as an upload script for the project they were working on, which I know we've seen folks, I've definitely seen folks in the Discord asking about ways to develop code on your PC and then send it to the CircuitPython device when you're ready and it looks like this is a tool that could help with that workflow. So I thought that one was interesting. So that was the items from the newsletter for this week. Again, the CircuitPython Weekly newsletter is a CircuitPython community run newsletter that's emailed every Tuesday. The complete archives are available at AdafruitDaily.com. It highlights the latest Python on hardware related news from around the web including CircuitPython, MicroPython, as well as C-Python developments. To contribute your own news or projects, you can edit next week's draft on GitHub. There's a link in the notes doc for that. You can also tag a tweet with hashtag CircuitPython on Twitter or email to cpnews at Adafruit.com. Alright, so next up we will look at the state of CircuitPython, the libraries and Blinka. Let me scroll just a little bit here. So this is a quantitative overview of the entire project. It gives us a chance to look at the health of the project separate from what we're all up to. We'll talk about the project overall and then separately discuss the core, the libraries and Blinka. So first up is the overall section. Let's see here, let's get a timestamp in for that. And just a reminder for folks, this report does contain information from the last seven days. So if you have something that's brand new hot off the presses, it won't be included in this report, but it'll be in next weeks. So overall, we had 41 pull requests merged across all of the projects this week. There were 23 authors for those 41 PRs. A couple of the names that I did not recognize. So these might be newer folks or less frequent contributors that I just wanted to point out and think. Those names are Hex That, T-L-Y-U, C-J-8 Scrambler, Chris W. Wend, H-E Coding 180 and E28 ETA. Again, all of those are names that at least I don't recognize. So they may be relatively new to contributing or less frequent contributors. I apologize if I did miss anyone, but it looks like the rest of the folks there are some of our more usual contributors. So thank you to all the new folks as well as all of the usual contributors. We appreciate all of you and certainly help keep the project moving forward. So thanks to everyone on any of those lists for sure. We had eight reviewers this week. So thank you to all of our reviewers. And again, that does also look like relatively standard list there. There were in terms of issues, we had 27 closed issues by 15 people with 14 issues opened by 14 people. So net down a little bit on issues that looks like more closed than open. So moving in the right direction there, always good to see. Next up, we will hear about the core. Scott, are you available to tell us about the core? Sure, happy to. Alright, so numbers for the core. We had 18 pull request merge from 13 different authors, which is a lot. So thank you to all of our authors. They look like names I've seen before, so thank you to everybody there. We had four reviewers, which is also up a bit, which is great. We have 22 open pull requests. A number of those are draft, although a couple are brand new as well. Issue-wise, we had 10 closed issues by nine people and nine opens by nine people. So a lot of folks being involved in issues, which is good, for a total of 599 open issues. We have nine active milestones, and I'd like to point out that we do have an 8.1.0 milestone as well. And we have zero open issues for 73x and 04800 as well. So that's awesome and why we have a release candidate. The rug we've swept some bugs under is the 8xx milestone that has 51 open issues. So there is some work to do there. And we have 512 open long-term issues as well. So we still have lots of ideas from folks, which is great. And we're doing our best to get all of the critical stuff handled. And that's it for the core. All right, excellent. Thank you, Scott. Next up, Katne, are you available to tell us about the libraries? Now that I can read that section. I am. All right, so this section applies to all of the Circuit Python libraries, which is everything included in the Circuit Python community bundle, as well as all of the Adafruit Circuit Python libraries, which is everything that starts with Adafruit underscore, Circuit Python underscore. All together we had 15 pull requests merged by nine different authors. A number of the new folks that Tim pointed out earlier are on this list, which is excellent to see. And we had four reviewers. And I wanted to say a special thank you to Jose David, who was out for a bit, but is back and evidently reviewing PRs. So thank you for doing that. And we are left with 41 open pull requests. The oldest PR merged was 30 days. Everything else was nine days or less, so it's good to see that we're still getting through older PRs, but we are also keeping up with the new ones. We had 16 issues closed by eight people and five open by five people, leaving us with 590 open issues. 77 of those are labeled as good first issue. If you're interested in contributing to Circuit Python on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more, including a full list of the open pull requests and a full list of the open issues. If you're interested in contributing by reviewing, check out the list of open pull requests. If you have the hardware for that PR, test it. If you don't, take a look at the syntax. Let us know if we missed something with spelling, et cetera. All of that is super helpful. Leave a comment and let us know that you did. And once you're comfortable with that, we can talk about leveling you up to the review team. If you're interested in contributing code or documentation, check out the open issues. If you're new to everything, good first issue is a great place to start. Otherwise, look for bug or enhancement or you can just search on the page to find an issue that works for you. And then if you're new to everything, don't worry about that. We have a guide on contributing to Circuit Python using Git and GitHub as well as us being available on Discord to help out. We want to make sure you can contribute in a way that works for you. In terms of library PI PI weekly download stats, the total library stats over 306 library repositories was 147,746. And then I have a list of the top 10 libraries by PI PI download. Again, the top three are pretty typical, but it looks like, for example, one I haven't seen on this list at all since we started doing it was the LED animation library. It's always interesting to see what folks are interested in any given week with using our libraries through PI PI. In terms of library updates in the last seven days, there is one new library, CircuitPython underscore equalizer, which is by jpasada 2020 and a number of updated libraries, which I will not read off. Other than keeping up with our PRs and so on, things are looking very good. We're over 400 libraries now in total. And as you can see with the library updates, we've combined the community libraries in with the Adafruit libraries because we have been striving to do that for quite a long time and it made sense to do it in the statistics as well since the overall library number includes both. It was a little confusing when there were no new libraries, but obviously there were new libraries. So now it's all in one place, which is very excellent and we can highlight more stuff from the community. And that's what I've got. Awesome. Thank you, Katnie. Next up is the section for Blinka. Make or Melissa, do you want to tell us about Blinka for the week? Yeah. So Blinka is our CircuitPython compatibility layer for MicroPython Raspberry Pi and other single board computers. And this week we had eight pull requests merged by five authors and five reviewers, which are quite a bit more than normal. There are currently five open pull requests amongst all the repositories. And there was one closed issue by one person and zero open by zero people, leaving a net of 88 open issues. There were 30,123 PI PI downloads in the last week and there were 8,960 PI wheels downloads in the last month. We are currently supporting 101 boards. So overall, it looks like our downloads have been a little bit higher and there's been a little bit more work on there, which is excellent. Nice, thank you, Melissa. Next up is the first of our two round robins, the hug report section. So hug reports is a chance to highlight folks in the CircuitPython community and beyond for doing awesome things. I'll start and then we'll go down the list alphabetically as they appear in the note stock to give everyone a chance to participate. If you're text only or missing the meeting, but you have hug reports in the note stock, then I'll read those off as we get to your time in the list. So first up is hug reports for me. So my list this week, thank you to L.Pakinen, who tried out VS Code and figured out how to get the serial monitor working in order to help someone on Discord. Somebody was having trouble with that and asking about it. This person kind of went out, installed VS Code and figured it out in order to be able to help. So that was really nice to see. Thank you to, let's see, M.RaveLorNinjaka. I probably butchered that name, I apologize, but this person posted an issue and dug through it a bit to figure out and even post a proposed solution for the issue, which was being able to use the LED animation library with the 13x9 IS31FL3741, I think it is, driver. So somebody was asking about this on the Discord, it may have even been this same person asking about it, but they eventually went and put an issue and even put some sample code that's what I've been diving into. So it's been great to see and it was a big help to have that head start. Thank you to NeerDoc for sharing an example of how to use scrolling text on that same matrix, which I believe a different person was asking about over the weekend on the Discord. Another hard report, thanks again to NeerDoc who's for sharing the disco tool device manager utility. So I got my hands dirty with that a little bit this week, finally got Node updated on my system and started using that thing out. It's a very handy tool and I'm looking forward to trying it out with Web workflow. I've done just USB so far, but it seems like quite a nifty utility. Thank you to Peter Bay for sharing a neat font generator utility. This was another one that was shared on Discord. It makes it easy to use a few different icons or characters from some common open source fronts with a frame buffer display as well as with display IO also. And then the last one I have written down here is thank you to Dan H. and to Shippu for getting a quick fix in to enable CDC on the Pew Pew M4. However, I will say I forgot one, which I'll write in here in a moment. Thanks also to Tectric for submitting an issue on one of my libraries, the Pi Game Display Library, about an issue with the actual release in PiPi for that. So thanks to Tectric for that and I'll add that one here in a minute. But next up we will hear from Dan for your hug reports. Okay, thank you. All right. Thanks to Jeff and Scott for the issue, 80 issue triage meeting we had last week, which enabled us to really plow forward on getting a release candidate out. Thanks to MicroDev for two things. One for sort of keeping up with various PRs to the core and merging things when I forgot to merge them and in general just sort of prompt fixes when there wasn't one thing that they needed to look at and they looked at it quickly. So thank you. Thanks also to MicroDev for work on the CI part of the builds or the CI builds. There are various cleanups and speedups that they've implemented, which are very helpful. And thanks to Neridoc who was trying to turn off a certain feature and realized that it wasn't really set up the same way as other features and submitted a PR to normalize it to be just like all the other ones. Okay. All right. Thanks, Dan. Next up is David Glauda who's text only. So I'll read. David has a hug report for maker Melissa for, let's see, for the installer integrated into circuitpython.org as seen on show and tell. Hug report for Anecdata and Neridoc for suggesting a way to make a DIY pie cowbell airlift. Although David prefers a real one. And then a hug report for FOMI guy, me for various and various frequent viewers for all the live streams. Next up is DJ Devon three who's also text only. So I'll read those hug report from DJ Devon for at circuit Python developers for an 8.0 release candidate at Noe Ruiz for an excellent video on snap fit enclosure design for Fusion 360. The video is over five years old and it's still just as relevant as if it was made yesterday. Hug report to JP and Lady Aida for taking on some hardware hacking and circuit bending projects. It's been very informative and entertaining to watch you hack circuitry. Hug report for Jepler for a great guide on converting a vintage bus mouse to a USB HID using a QT pie. Hug report for Neridoc and Anecdata for being tech support on the circuit Python channel and beta testing a lot of different stuff every week. And another hug report for Neridoc for an amazing update of disco tool. It's getting better every time I see it. So thank you. That was DJ Devon three. And next up I'll send it over to Jeff. All right. Good afternoon, depending on your time zone. First to thank you to Dan for the release candidate of version eight. Really excited to have that come out finally. And thanks to microdote for your detective work to get some ESP chips to work. And finally, thanks to Ann and paint your dragon for some editing and feedback on that recent guide that DJ Devon mentioned. And that's what I've got. Group hug reports. All right. Thank you, Jeff. Next up is Jose David, who's text only. So I'll read those. Hug report for FOMI guy for the new deep sleep pin alarm example for the mag tag. Hug report for Chris W. Wind for improving the SHT 31D documentation. Hug report for, I'm going to say, TLYU just spelled out the username there for improving the documentation of the LED animation library. And then a hug report for Tectric for reviewing all the different PRs. So thanks to Jose for those. And next up I'll send it over to Katny. First of all, a super hug to you, Tim, for covering hosting the meeting for me today. To Dan for releasing the circuit python release candidates to Tectric for helping me through a CI fix and a lovely chat afterwards. And there are hugs I am missing here for sure. So please accept the following group hug in place of a specific hug and a group hug. All right. Thank you, Katny. Next up is American Melissa. Hello. Sorry, I couldn't find the button. Oh, I lost it. I wanted to give a hug report to Jose David for the updated MQTT code and the home assistant Tim humidity sensing guide and group hug. All right. Thank you, Mac and Melissa. Next up is Scott. Hello. I got a quick one for Gordon Williams, who does Esprino for help getting me, helping me get circuit python running on the BengalJS2, which is a watch that I've been using for a while. And I also have out for review in a PR. Nice. Thank you, Scott. Next up is Tectric, who's text only. So I'll read those. Tectric has a report for TC Franks for submitting 100 PRs and completing their first Hacktoberfest. Hug report for Jose David for a bunch of help on PRs recently. Hug report for Katny for an excellent talk this past week and all weeks that we talk. Hug report for Dan H for helping to merge some CI update PRs I made over the last couple of weeks and hug to everyone who wished my partner well. She had a serious fall the other weekend but is doing and feeling much better at this point after some appointments and rest. This community is and always has been super supportive at every turn. And then lastly, Tectric has a hug report, excuse me, a group hug for everyone. Thank you to Tectric for that. And last one in the list here, we have is Nenverov. I probably perhaps spelled it wrong. Or pronounced it wrong is this person in the... Yeah, it's Nenverov. I just started building CircuitPython this week and I found Dan's building guide very helpful. Awesome, yeah, thank you. Thanks for popping by to give us that hug report. That's really nice to see. So thanks for that. And that is the last of our hug reports. So next up, we will move into the status updates section. Status updates is our time to sync up on what we're doing. I'll start and then we'll go through the list alphabetically to give everyone a chance to participate. When I call on you, you can take a couple of minutes to talk about what you've been doing since the last meeting and what you will be doing until the next meeting. This is also an opportunity to provide tips and tricks relevant to what folks are working on. If a discussion becomes too much for status updates, then we can move it down to the final section in the weeds. So I'll start us off for status updates. So last week, I wrapped up the testing on the remaining open Ethernet PRs, which definitely feels good to get to the bottom of that list. I started working on a game controller library that provides a common interface for interacting with the most commonly used video game inputs like a D-pad slash joystick or a few other action buttons like ABXY. So far, it has support for the following devices, the PiGamer, PiBadge, PPUM4, PicoSystem, and then the Joy Featherwing with any base feather. You can use that featherwing. All of those things are supported by the library so far, but we do still have some work to do, and I'll be publishing that into the community bundle this week. The other thing I had for last week is I continued working on the Bitmap Tools implementation for Blinka Display.io. Specifically, I did the draw line and the boundary fill functions last week, so I do still have some more of the more complex ones to dive into this week. The other things I've got on my plate this week, I am starting to try to wrap my head around the different available classes and modules for the IS31FL3741 LED driver. There's a built-in core module, there's a Python module inside the library, and then from there, there's also a couple of others kind of built on top, like a pixel buff one and a frame buffer one, and it's just kind of a lot of different things. I'm trying to straighten out in my head which ones are meant for what purposes, and then ultimately my goal is to figure out what's the easiest way to make it work with LED animation. So thanks again to all the folks who have been helping with that. The other thing that I have in mind for this week that I like to dive into for sure is a difference between on-disk bitmap and image load. Carter, I think over the weekend or within the last couple of days, posted an image that... a specific bitmap image that displays differently if you load it as an on-disk bitmap versus if you load it with image load, which is certainly odd, I've never run across that before, and it's right at my alley for the kind of thing that I am super interested in trying to understand. So I'll dive in a bit and see if I can spot what might be leading to the difference with that image. And that's what I've got for my status reports, so next up I will send it over to Dan. Okay, thanks. So as I mentioned, we had a bug triage meeting last week and pushed the remaining bugs forward to 8XX or 810, and that enabled me to work on... I released candidate for 8.00, so I built an RC... I didn't work on the release notes earlier last week, and then there were a flurry of small PRs over the weekend, which were worth pulling in, so I did those, and I released an RC... I built an RC-0 and then realized it was missing one particular PR, so I just deleted that one because I hadn't publicized it in any way, and then did an RC.1, which had all the PRs that I wanted to have in it. And that's released, and it's blogged up, and it's on circuitpython.org, so please try it. The only fix I know of past RC.1 or other two, there's a read-a-dox fix, because the docs weren't actually building, and we hadn't noticed that, and that's fixed post RC.1, but it's not a code fix, and there's also a CI fix that Scott just found, which I'll put in post that, but also it will not be a code fix. There are one or two maybe PRs that are very minor, like pin changes or something, which we could probably put in 8.00. But we're not really sure how long we'll try to have the RCs live or not, but we'll talk about that, but we hope to have 8.00 final soon enough. Okay, and then, also over the weekend, there's this new ESP32C3, not S3 module, not new, but it has 32 megabytes of flash, and it's actually hard to build because a lot of things in ESP, like the ADF used to have some 16 megabytes, not megabytes, not megabits, and so microdev was trying various things to make it build, and I had one of these which I just got in the mail from Adafruit and got it working by me testing and microdev changing things. So that PR is in RC.1. And then finally also for the past several days, I've done some things that are hardware debugging and not CircuitPython. Somebody was having, there's a kind of a problem about on the feathers that have a second regulator for controlling the StemAQT bus. If you try to turn everything off by pulling the enable pin down, it actually doesn't, it can latch up so that the StemA bus still has power even though the CPU doesn't have power. Pulling the end pin down was kind of not necessarily our primary mode of use, but we understand the problem now. And also somebody else has problems with QDPyM0s not being able to turn on their boot protection flags and that's really strange. I don't understand what's going on here, but I ordered some hardware to try to test it and maybe I'll have them send some of the ones because it works with the ones that I have. Okay, that's it. Alrighty, thank you Dan. Next up is David Glauda who's text only, so I'll read. So in CircuitPython news for David Glauda, reading all the CircuitPython 2023 posts except mine and sometimes commenting on them, watching CircuitPython and other Adafruit streams and participating when live, instinct acquisition of an ESP32C6DevKitC1-N8 before I figured out that CircuitPython support would not be before long, but I'm ready. Temporarily put a hold on my attempt to read the C64 keyboard. At one point it did send so many random keystrokes that my PC crashed. Oh, that's no good. And then in non-CircPython-related news, decided to try, let's see, decided to reinstall BCM64, the C64 to validate my pinout of the keyboard, added joystick 1 and 2 support to my Raspberry Pi board for BCM64. So thank you to David Glauda for those. And next up is DJ Devin. He's also text only, so I'll read theirs. Finished the TR cowbell enclosure. There's one small alignment issue. Had to use a mallet to fix everything together, to fit everything together, excuse me. The top faceplate has space for a 1.5 inch tall display. It won't fit the larger Pi portal or TFT featherwing size displays. You'll, of course, be able to use the files to modify the design to suit your needs, such as one of the most amazing parts of 3D printing, for sure. There are, let's see, F3D, STL, and OBJ, as well as other formats for the enclosure are now available on GitHub. There's a link in the notes if anybody wants to grab those. If you don't have a 3D printer, you can use these files to have one printed for you. I cannot offer an enclosure to everyone. Too many people have them now. It would take me months of printing. But yeah, there definitely are services out there where you can send a file and get a print. So if anybody got the cowbell that wants one of those, look into that. Next up is Jeff. Hello again. I'm a little distracted looking for a replacement piece for my solder sucker. But yeah, back to the meeting. I didn't have, it felt like a whole lot of circuit Python activity last week, whether I worked on creating a text terminal using Pico DVI under the Arduino programming environment, and we might use that in some kind of future project. I responded to guide feedback and improved a couple of guides in tiny ways and posted the first mouse guide for the next computer's mouse. And at least one more mouse project is in the works. The mouse for Mario Paint on the Super Nintendo looks like it's something that we could run with circuit Python. I figured that would feel pretty vintage and exciting. I got that little project approved. This week, I'm still hoping to test out the ESP32-S2 slash S3 RISC-5 Ultra Low Power Co-Processor for an upcoming keyboard project. And Lamar also asked me to take a look at I2S out on the ESP32-S2 and S3 and kind of report back on how well or poorly it's working and that will include checking on WAV files from Flash, MP3 files from Flash, and WAV files from SD card just to see what works and what doesn't. And other stuff, my spouse Ingrid has been on a week-long trip to India and Nepal, and she will get back on Wednesday and it will be pretty nice to have a housemate again. I'm looking forward to that. That's what I got going on. Thank you. All right. Thank you, Jeff. Next up is Jose David, who's text-only. So I'll read. Jose says, last week, a couple of documentation, prose review, I think maybe PR's review. Updated the community library driver list, adding their description and documentation link, if missing. Working on the TMP117 sensor library for memory optimization. Work in a new example for the JLED community library, which allows non-blocking LEDs, sequences, and effects. Adding a magnetometer example for the LED to increase and decrease brightness if a magnet is close by. Some type annotations, PR's. Working on releasing some personal libraries to PiPi. Gladly surprised that other people than me have downloaded them. And then for this week, Jose David says, maybe work on the TMP117 memory issue, update the community library helper's list descriptions, and take a look at other community libraries to see what they can do. Next up is Gnevarov. Hi. Yeah, I've started working on one of the issues about adding a non-poling read to the PIO state machine class. And I'm still sort of getting started and familiarizing myself with the code base on that one. Awesome. Well, welcome in. It's great to have you working on that and popping in to join for the meeting as well. So that's great to hear. Next up is Katnick. Hello. The last week, I had some various miscellaneous stuff that I didn't really track. I had a lot of meetings fixed up. The iSpy guide updates. I realized after Liz and I were talking about reviewing each other's guides that I hadn't shown all of the pins that a display uses. I was only showing the ones used in the CircuitPython example. When the point of those guide updates was to show what pins are possibly used by the display, not what pins are used in a particular example. So I fixed all that up, and now that shows all the usable pins, both on a list and a wiring diagram. And I worked with Alec to fix a CI thing on the Adafruit Blink of the LEIO library. It was something that we updated across all the rest of the libraries, but this one somehow got missed and it didn't actually trigger that failure until a very recent PR. So that's all fixed up. This week, I'm going to be working on the reverse TFT feather guide. That's a recently released board where the TFT is on the opposite side from the chips and buttons and so on. I'm going to be doing a time lapse using Raspberry Pi guide. If I remember correctly, at least five years ago, it was very, very easy. So I have to imagine it's easy now. So it'll be quick, but I have these plants that I got that I talked about last time and we'll talk about in a minute. And one of them bloomed. The other one looks like it's starting to, and I want to catch that in a time lapse. So I will be writing that up as a guide. Then I'm going to be doing the CH90102F guide update. We have a guide on installing the drivers for it, no guide for the breakout that we made after that. And then a Metro mini guide update because we have updated the existing Metro mini to the V2 and the existing one is no longer available. So the guide needs to explain both. And then probably more various miscellaneous. And the unrelated bit is my plants, which I pretty much said everything about. The blooms on the one that already bloomed are already on the way out. And I did not get a lot of photos. So I'm disappointed, but the other one looks like it's starting to get the beginning of the blooms. So I think I'm going to set up a time lapse situation for that and catch it all the way through. So that's what I have going on. Nice. Definitely do please share those photos if you end up getting them. That sounds awesome. Next up is maker Melissa. Hello. So last week I worked on mostly fixing up my PR for code.circuitpython.org, which should improve the USB workflow. And I had a number of bug fixes I found and fixed on that. I also separated out my JavaScript code that interfaces with the circuit Python ripple over a serial connection and I helped a user troubleshoot their braincraft driver install on Bullseye. This week I am working on getting an initial version of the circuit Python installer running. I'm currently working on addressing some cores issues and have a plan at this point. I do need to update the GitHub actions for the tiny UF2 boot loader so that it uploads to Amazon S3. And I need to add info for the new release candidates, candidate boards to circuitpython.org since it added like 12 new boards. And I need to update the guides and drivers for the revised 0.96 inch TFT. And I also need to test... I'm probably going to be testing the ESP tool.js because it looks like it's really close to being able to use. And then we can use it over the ESP tool that we have now. So I'll probably work on testing that soon. Yeah, that's it. All right. Thank you, Melissa. Next up is Mark Gambler, who's lurking. So I'll read. Mark says, started work and investigated adding a GIF output support for circuitpython, hoping to get a proof of concept written up this week time permitting. So that certainly sounds awesome. Thanks to Mark for adding notes in here. And then next up is Scott. Hello. First, I wrapped up circuitpython 2023. Last Monday after the meeting, there's a link to the blog post there. So thank you to everyone who took the time and had the time to write it up. I also sent out a draft PR for BengalJS2 support that includes seven-color ink or e-papers support as well. It's kind of a weird twofer, but the common thread is that they both have three-bit color displays, although what the color means is different between the two. So I just did both. Sorry in advance to whoever reviews it. I will have to follow up with changes for that. I already found a bug in our CI where it was loading an older version of a file that I changed causing the build to fail. So I tried to fix that. For those of you who've seen this display ruler.pmp file, I made a separate repo for the source of that, which is a used gimp, which is a terrible name, but used gimp to put that together. And I've made a bigger version. I called it the 720p version that has a rainbow on it too, which is really handy for these seven-color displays. And the largest seven-inch one is 800 by 400, so I needed something bigger as well. So you can find that in that new repo. I have two things kind of on my plate. One, I have to get the... And I didn't put this in. I have to get the libraries for these e-inks out and published. And then after I do that, I'm going to be looking into finishing up USB host support on the IMX RT. And I might also be looking into Scorpio as a logic analyzer with some sigrap code as kind of the foundation for that. So, yeah, those are kind of things that are on my mind to do. All right. Thank you, Scott. Next up is Tectric, who's text only, so I'll read. Last couple of weeks, we've got PR reviews, more type annotation PRs, at least one community bundle edition, woohoo. Others that I'm forgetting, but a belated group hug to everyone who contributes. Updated the report to combine Adafruit and Community Bundle updates. Updated and patched the CI for more deprecation warnings in the libraries and Blinka ecosystem. Tectric also says, please tag, message, or ping me if you find any additional CI deprecation issues, since I'm assuming that I've found them all by now. Created a new GitHub action to replace the one in the core with deprecation warnings. Fun getting to revisit JavaScript after about 15 years, personally hoping to make some cool stuff with the OctoKit API. I'm not familiar with that one, but I'll have to look into it. Taking some personal time to help care for my partner. And then this week, Tectric says, trying to finalize all the CI updates. Hopefully working on feature additions and bug fixes for a few libraries. I have hardware for now that I have hardware for now that the CI is mostly patched. And then feasibility testing for some library updates like issues and PR templates that I can suggest next if they work and make any sense. All right. And that is the last of our status updates. So our fifth and final section for the meeting today will be in the weeds. As a reminder, in the weeds is an opportunity for more long form discussions. These can be things that either came out of status updates or they could have been identified ahead of time. If you haven't in the weeds topic, please be sure to go ahead and scroll all the way down in the note stock and drop that in down at the bottom. We do have a couple there. So you've got a few minutes while we discuss those. But if anybody knows of a different one that's not in there now, do please go ahead and add that. So our first in the weeds topic this week is from Tectric who's text only. So I'll read this one here. So Tectric says whenever there are updates to things like the CI or cookie cutter templated items, e.g. like the read me file, like the license file, I think there's a couple of those that would fit into that same umbrella. So when there are updates to those, Adafruit libraries are patched, but community bundle libraries can lag behind. Sometimes gaining the improvements is more relevant to Adafruit libraries, but there are times where the community bundle libraries should benefit if those libraries are still maintained, such as GitHub Action CI updates. I'm exploring ways to have said updates visible to the community at large and have said fixes and improvements readily understood. Since these issues are potentially rediscovered after, excuse me, rediscovered, months after the Adafruit libraries have had the fixes put into them. And so Tectric also mentions, I've thought about releasing Git patches to make the fixes available or allowing automated PRs, but this depends on the repository already being at a specific state. Additionally, Git patches aren't always applicable. E.g. you couldn't change circup installation instructions because every library is different and repositories vary greatly. So PR automation is a major challenge. Would a rolling blog like... Yeah, so let's see. This is the next question here from Tectric. Would a rolling blog-like format be better, explaining issues and their fixes? Should it be more newsletter-like where individuals can subscribe to get updates, just brainstorming and looking for ideas? So I'm voting for something like the second one. One thought would be create a GitHub repo that is just documenting the changes to the libraries, and then people can subscribe to watch that repository and get notifications when there's changes to it. I think documentation is a far better way to go about this than trying to figure out how to do automated PRs across the community bundle because while there is quite a bit of consistency within it, there's also obviously these are hosted by individuals and maintained by individuals, and so it's not always exactly the same. So I think our time would be much better spent doing a little bit of documentation when we post these changes, and you can even link to one of the commits each time so that folks can see exactly what needs to happen to apply that fix. But I think that might be a better way to go about it. Talk to Rick is typing. I would definitely agree with all of that as well. The one other thing I might add is if there's any way to make some kind of like instructions for someone if they wanted to kind of like start fresh, if that makes any sense. At some point I imagine it would be easier to just cookie-cut a new thing with the current cookie-cutter which will have all the updated stuff and then kind of paste your existing code into it and then push that as as an update to your repo. So maybe instructions like that might be helpful. Starting fresh is kind of covered in the building a library in the first place guide because you're supposed to cookie-cut or paste your stuff in. I just mean from like a library where you've already published it and you want to like essentially take a new one with the actual code into the new template if that makes any sense. No it does. I just, I don't know how different that would be from how we explain writing a library in the first place. That's true. There could be obviously a short explanation put somewhere and just basically adapt what we already have, don't write up a whole new explanation. But yes, that is my thought on it. I'll just subscribe to a GitHub repo that we just create for that or maybe an issue on the Adafruit bundle where folks can subscribe to that issue and then that's an ongoing issue. We don't close it. It's another possibility instead of a whole separate repo. But yes, I think let's go with documentation not we're not maintaining those repositories so we shouldn't be trying to do maintenance on them, I guess is my point. Sounds like we've got point in the right direction then, Tektrick, for that one is either spin up a repo where we can put like markdown files or text files or something for documentation or start up an issue on the one if you want to go that way for what it's worth. I'd probably lean towards a repo just so it's easier to search and look back at the history and all of that sort of stuff personally but either one sounds like it would work out just as well. And then, yeah, Tektrick, let us know if you have any additional questions or anything to add and while you're doing that, I will pass the baton over to Scott for now, for the next In the Weeds topic. Thank you, Tim. I would just, because CircuitPython 2023 has been wrapped up, I thought I tried to take some time for us to just all talk about it. I just skimmed over the stuff that I saw and I think if I were to take a theme out of it I think it's actually tooling both like the tooling that kind of like Tektrick's just talking about but also like tooling USB side command line stuff Android apps although that seems to be a really common theme I didn't see any like microcontroller platforms Async came up a couple times I'm wondering if other folks saw any themes or have any thoughts around CircuitPython23 as well. We're just all happy with it. I think you're I definitely agree with your observation about like not much in the way of new platforms and stuff like that compared to years past. So it feels kind of like we're at a pretty good point where the platforms we have are capable of the vast majority of what people want so I think that's definitely a good sign. I did see a couple of folks mentioning different avenues for tools and utilities and things. That does make sense as the theme as well. I'm pretty stoked about just about everything that I saw mentioned. I know GIFs is something that has been mentioned in the works as well. I'm definitely really excited about the possibility of GIF support in DisplayIO. Um... TypeDark agrees that it's tooling mostly. I don't remember if I don't think I mentioned it in my post. On the topic of tooling that has crossed my mind sometimes is like an advanced it's definitely meant for the advanced user but some way to make more customized builds as time goes on we get more and more modules that are optional.  I think it would be cool if advanced users had a way to be able to make a build through some web app or something like log into a page and just tell it what you want and it creates a build and gives you a link and after a few minutes you can go and download it. To customize pin names? To customize pin names as well as being able to turn on and off the modules so let's say you want for whatever reason the device you're using a module is turned off but you want to be able to use it in your particular project it'd be nice if you could get a build without having to actually clone the repo and get everything set up and do the build. It seems like a server could kind of provide that ability. Now the risk, the downside of this is it fractures the number of versions of circuit python out there so it does get harder if somebody makes a custom build with all sorts of things changed and then comes back and says hey this isn't working with this thing how I expected it to or something so there's a support challenge for sure on that front it needs to be clear that those builds are customized in some way certainly. Yeah and I think a lot of people that are like I just want to turn on this one it's like no it's off for a reason it's not implemented yeah it's not that we just turned it off in most cases it's not implemented but yeah custom pin names as well even built in displays like let's say you make a project where you use one of the external displays but in your project you know maybe you're never going to use it for anything else and so it might be nice if you could have a custom build with board.display implemented even though it's not like a built-in display. Something like that I think could a custom build system would allow you to do stuff like that without needing as much of the technical knowledge. Right. The challenge with those services is that they can be hard to maintain. Yeah and costs time and money right for the server to run and actually take the builds and stuff as well so it's like yeah if you can't do it on github slash Microsoft's time. 100% we're so lucky about that. We spend a lot of Microsoft dollars. Cool well I don't see anything else. Alrighty yep thank you Thanks. Thank you all. Yeah for sure. Thanks Scott. Next up in the weeds is from Mark Gambler. So hopefully I'll be there. Mark are you got a microphone or do you want me to read that for you? Yeah I have it. Just a quick summary of it was for the github support I was looking at there's the animated gith library that actually has been used in some other Adafruit projects for Arduino in the past the license on it is Apache and I'm not super familiar with how the licenses transfer between them all. So I was just wondering is there going to be any issues if I include a potential new library in circuit python? I think one of the things to be aware of is that Arduino tends to be C++ and as far as I know we don't have any source that we compile for C++ yet so there might be some work that you have to do in terms of like C++ and digitalization calls? Yeah so I actually I've looked through the library the core of it is actually in C so that actually works fine I got it compiling it only adds about a hundred bytes so it's not even too large but yeah it sounds like you don't have everything you need that's pretty small Yeah well that's why the next step is the proof of concept but I just wanted to make sure there's no immediate show stoppers with the licensing I'd be worried if it was GPL but it's not Yeah that I know there would definitely be an issue I'll keep plugging away on it and see where it gets and show everyone before I'll start a draft PR at a certain point Awesome thank you Mark Thanks Alright and that is the last of our in the weeds topics so with that I will take the final timestamp and do the wrap up here this has been the circuit python weekly meeting for January 30th 2023 Thank you to everyone who participated once again as a reminder if you want to support Adafruit and circuit python and those of us that work on circuit python consider purchasing hardware from the Adafruit shop at adafruit.com The next meeting will be released on youtube at youtube.com and the podcast will be made available on major podcast services it'll also be featured in the python for microcontrollers newsletter visit adafruitdaily.com to subscribe to that the next meeting I believe will be held next Monday as usual at 2pm eastern in the normal time slot but I actually don't have the calendar open so somebody please correct me if I'm wrong um yeah so to Monday at 2pm eastern 11am pacific I believe that should be for the next meeting um the meeting is held on the Adafruit discord which you can join at any time by going to adafruit.com fru.it slash discord um if you want to be notified about the meeting and any changes to the day or time you can ask to be added to the circuit python easter's roll uh over on that discord and that's it for today's meeting uh so thanks again to everyone for participating and we hope to see you all next week


Hello and welcome to the CMC markers week ahead video with myself market analyst David Madden and the week ahead We're going to be looking to is Monday the 13th until Friday the 17th of November and FYI Today's video is been recorded on Thursday the 9th of November and the time is just coming up to 1 p.m. UK time The structure of the video will be me running running through the major Corporate and economic indicators that are coming out next week and then I think it was the end in second after the video I'll then be discussing Some of the major markets which could could be impacted by the data and updates are having next week our corporate calendar our corporate Economic calendar can be found under the market impulse tab on the fourth option down And to be honest the on Monday the 13th is a relatively quiet day in terms of economic indicators We do have the foreign direct investment FDI numbers out from China overnight, but excluding that is a relatively quiet day Tuesday is our could be the busiest day next week overnight on Tuesday, we're going to have Some economic indicators coming out of China. We have retail sales industry production and we also have the fixed asset investment By and large the economic indicator is on becoming out of China have been fairly fairly decent in terms of manufacturing Services and also on the import side Beijing does hope to achieve a GDP growth of 6.5 percent in 2017 And the way things are going and given that we're now actually in November It's looking fairly likely that they're going to achieve that target If you are trading high-grade copper or any of the big mining companies such as Rio Tinto, Anglo-American Glencore or else Vedanta resources for example keep an eye on the Chinese economic indicators because It can add quite a bit of volatility to the market Later on on Tuesday morning We have both German GDP and CPI numbers coming out Obviously Germany's by by far the biggest most influential country within the European Union and the Eurozone So in terms of any kind of alterations to future monetary policy from the ECB Obviously what's going on in Germany is going to play a big role in that Later on choose the morning We have CPI numbers inflation numbers coming out from the UK CPI in the UK is currently running at three 3% and it's obviously quite a headache for the Bank of England seeing as our target is inflation rate of 2% and Seeing as it is partially brought on by the wrong decision in August 2016 to cut interest rates and the Decline in interest rates led to a salaf in the British Pound which then Made imports were expensive a term no a term economists referred to as imported inflation So inflation has been driven by the relative to weak pound rather than an increase in demand in the domestic British economy In the latter half of choose the morning We have the we have the Eurozone growth figures The region as a whole will produce its GDP numbers And as I mentioned earlier on the German figures are coming out earlier in the session Turning our attention to Wednesday a half nine on Wednesday. We have the unemployment and earnings figures coming out of the UK Arguably the the earnings figures are probably are probably the more important of the two Unemployment in the UK is that a multi-decade low results you great for the economy and something politicians like to boast about But British but the the rate and in decline in unemployment Hasn't really been matched by a rate of increase in wage growth Which growth is relatively speaking lagging the lagging in comparison to the rate of which jobs are being created or jobs are being filled And we have a scenario for unemployment is quite low, but but both the actual wage What isn't overly impressive British consumers aren't actually going out and spending as much and as I just mentioned British consumers are being squeezed already by higher inflation Later on on Tuesday later on on on the on the Wednesday We also have retail sales and consumer price index CPI coming out of the United States Inflation used in the in the US is currently running at 2.2 percent But the core inflation which strips out the ending to do with commodities such as Suggests such as oil or energy is lagging behind at 1.7 percent So it would suggest the gap between the two is more down to the recent uptake in the price of gasoline and also oil If the Federal Reserve are widely expected to raise rates in December But what to do in 2018 is what traders are really going to be focusing on? Turning our attention now to Thursday We have the CPI numbers coming off from the Eurozone as a whole on Thursday morning Inflation in the Eurozone is 21 and a half percent. It's still well after 2 percent target The European Central Bank only recently stated they're going to extend their their bond buying scheme out until the end of 2018 the mr. Draghi the president of the European Central Bank As he often does it left the door open to additional easing should it be required and he didn't even point to actually the inflation rate liking It's a two percent target. I think one of the reasons for the QE being required in the first place Turning our attention to Friday It's a relatively quiet day the big one to watch off on terms of economic indicators on Friday is going to be the Canadian CPI which comes out at half one and if you trade the dollar card the dollar loony That's obviously going to be a big one to watch out for In terms of corporate data next week We do have some companies reporting But the big ones to watch out for from the UK are going to be British land and Royal Mail Both of which are reporting their figures on Thursday the 16th of November So we discussed some economic indicators are coming up next week We obviously got data coming from the UK the Eurozone and the US Marcus which are potentially impacted by this. I will not take a look at the euro versus the US dollar If you've tuned into our previous videos either one by myself or Michael We've often discussed how the the euro dollar is in the head and show head and shoulder reversal reversal formation So we can see here the euro pushed higher versus the US dollar Creating at the left shoulder here that are pulled that a pullback to the reaction low at one sixteen seventy Pushed on higher here took off the take off the height of the shoulder and created the head formation here Then declined back to the reaction low at one sixteen seventy and has gone and pushed higher here And now we've actually dropped back below We dropped back below the reaction the the neckline as it's called to reaction lows at one sixteen seventy And while we remain south of one sixteen seventy the outlook for the euro versus the US dollar is going to be bearish Levels to watch out for to the downside first protocol could be the two hundred a moving average was comes into into play at 112 90 and we could even head down to out to 112 or even south of 112 itself Turning our attention up to the pound versus the US dollar cable as it's referred to cable has been Recently has been fit has been trading a lot of Trading in a relatively small range hasn't really recovered from the dovish hike by the Bank of England It's been trading within a relatively small range here It's almost like the market is trying to try to decide which way it's going to go But if you draw a trend line from the lows of March this year all the way through to where we are now We can see that we're pretty much testing the the trend line support in this area And if while we hold above the trend line support and even if the beyond even if you hold north of the 130 level The broader bullish trend for the British pound versus the US dollar is likely to admit to remain in place Looking at potential moves to the upside if we do push higher we could potentially run into resistance And at 133 35 and if you do move south of the 130 mark We could be heading back down towards the two of them moving average who's comes into play at 128 62 Any moves in sturning can have a big impact on the footsie 100 seeing as it's actually so internationally focused So even even though in the last few sessions the footsie 100 has come back a bit from the multi month highs It's still getting trend line support in around this area here And while we remain north of that trend line support the outlook is going to continue to be bullish It's only should we break below say this area here The lows from October in around seven thousand four hundred twenty five Then we potentially see a pullback back down towards the dirty moving average at seven thousand three hundred and eighty six Seeing as we have numbers coming off important numbers coming out from the euros on next week the the DAX is going to be in play And the DAX has quite a positive one recently not too long ago It was at a record high and the DAX has since come off its record high, but notice how The DAX managed to actually fill the gap that was created here So it's not is it one of the myths about gaps in the international markets is that gaps are always filled They're not always filled. They're often filled, but they're not always filled But it wouldn't be a surprise if I saw the mark if the if the market resumed the the wider upward trend now that this gap has been filled So while we remain Not to say 13,200 or even 13,095 the wider Bullished trend for the for the for the DAX is still going to be in place I'll be quick look now at the u.s. Markets which are in quite a quite a healthy healthy state First off the bag what we look at that is the at the Dow Jones The two charts that look quite similar the Dow Jones After creating record highs in the week just gone has it ever dipped ever so slightly, but About pullbacks from record highs is already a surprise while we remain north of the this this level here One of the lows from late october in a 23,250 while we were in north of that the outlook is likely to remain Still positive for the Dow Jones And I would have a quick look at the s&p 500 as well S&P 500 looks quite similar. It's come off at its record highs We have seen a bit of profit taking but seeing as buying on the dips has been a popular strategy for traders Over the last number of months. We could see some new buyers enter the fold. So Yes, this is this is the s&p here As you can see it was in a fairly clear and concise Upward trend should we see any move to the downside? We may find support in this price here the november low Which comes to play at 2,565 or maybe we even see The market pulled back towards two thousand two thousand five hundred and sixty So the u.s. Markets are still looking in quite decent shape even though we have seen some Some some profit taking taking place That's all for me this week. Thank you for tuning in and have a good week trading


Almost 10,000 Russian soldiers express their willingness to surrender. 9,836 people from Russia and temporarily occupied territories of Ukraine have already turned to the Ukrainian national initiative called Hoshu-Zit I Want to Live, stating their intention to surrender. Coordination headquarters for the treatment of prisoners of war announced it. Over six months of the project functioning, more than 14 million people visited the website of the Hoshu-Zit initiative, despite regular attempt of Roskomnadzor to block access. Roskomnadzor is the Russian federal executive agency responsible for monitoring, controlling and censoring Russian mass media. 84% of those who searched the website were from the Russian Federation. Apart from Russian soldiers themselves, their family members and close people call a hotline. Conscripted Russians who have come to Ukraine often do not have any access to the Internet or cellular data. The website of the Ukrainian state project Hoshu-Zit, where Russian servicemen are offered an opportunity to surrender to the armed forces of Ukraine, was blocked on the territory of Russia.


My experience was very good. The panel was very positive and that's the good part. My key takeaway is that the industry is ready to take on the artificial intelligence and use it to its advantage. There was very less talk about loss of jobs or anything like that. But one more important thing which I also re-iterated is ethical use of AI. We have to have full disclosure. We have to also see that we are not impinging on the rights of anybody or also not leaking any data inadvertently of our clients.


True love. Yeah, can you come look at something? Sorry, the camera's a little Yeah, it'll be quick Aren't those nice? They're coming in. Oh Boy, hey get out of there Basically, we planted this a year ago and it did not bloom at all last year which they told us would happen And so now this is gonna be true loves rose Tunnel Oh my gosh, I love it so much. Isn't that nice? Isn't that just precious? Aren't they just nice? Yeah, they're real pretty. I love the color. I love the color You know that's my favorite I know. So honey's gonna, you know, keep going there Here goes nothing. Robert, Damien, I tried. I tried with the newspaper Didn't have a chimney. Don't have a chimney yet and the newspaper didn't quite work. Probably just didn't have enough of it So anyway, we've got a resort to the good old lighter fluid Next time. Give her another shot. Not giving up. This time we gotta eat, we gotta eat. Pops. I painted today. I know it doesn't look like it, but I did Basically, I got all the nooks and crannies up here by the roof ridge line With primer. So that was put off from last fall So now, perhaps, if it doesn't rain, it's a little cloudy and after grilling and after eating and after the boys are down I can put the blue on, slap it on there and the back wall of this house will be done That would be nice, but we'll just see how the weather does it. It might be getting bad weather, we'll see I'm tired of looking at a dirty grill. I'm tired of it. I'm tired of it. Fun, special delivery Wasn't that awesome? Honey, I want to grill every night. Okay, perfect. Ciao Do not watch this vlog if you are hungry. Do not watch this vlog if you are hungry I'm telling you. We are mastering the Weber Yeah, that that felt like a good step forward. I know I didn't have the chimney and lighting the charcoal correctly But guess what? I am a master when it comes to the right circulation of the heat ventilation Okay, YouTube


Christianity is just boring. It takes the fun out of life. You only have one life to live and it's my job not to waste it And so I'm not gonna stay in some hard pew in a stuffy church just wasting it No, I'm gonna live my life to the fullest and actually enjoy my life You know, have you ever thought something along these lines? No, I know I have but I want us to think together about it What is Christianity? I mean at its core. It's not about popular worship bans or about celebrity pastors or about Televangelists no at its core Christianity is about Christ Jesus Christ in John 1 verse 4 to 5 It says in him was life and the life was the light of men The light shines in the darkness and the darkness has not overcome it John 3 19 says this This is the judgment that the light has come into the world and men love the darkness rather than the light For their deeds were evil. You see we think we can live a life of meaning and Purpose without Jesus like we're fine on our own and we can do it all by ourselves But the Bible presents a very different reality without Jesus. We are in bondage to our sin We are in bondage to darkness We love the darkness rather than the light and that has serious consequences Roman 623 says this for the wages of sin is death But the gift of God is eternal life in Christ Jesus our Lord Remember back in John in him was life We can now see a clear distinction sin leads to death and Jesus is the life and leads us to new life in him James 1 14 to 15 says this But each person is tempted when they are dragged away by their own evil desire and enticed Then after desire is conceived it gives birth to sin and sin when it is full grown gives birth to death It's a sobering reality our sin leads to death But you look at Jesus and you think how could anybody reject him who is the life who is full of life Who is willing to give us eternal life? How could they reject him? But we go back in John and see this he came to that which was his own But his own did not receive him we can see clearly the rejection of Jesus as we look at the cross They killed the Savior they reject him very rejected him They didn't receive him through his death on the cross He bore all our sin guilt and shame all him on himself so that we could be free and on the third day He resurrected from the grave defeating sin and death This is what John is talking about in him was life and that life was the light of all mankind The light shines in the darkness and the darkness does not overcome it The darkness of sin could not overcome Jesus and he demonstrated this by his sinless life The darkness of death could not overcome Jesus and he demonstrated this through his resurrection He is the Savior and yet the world continues to reject him and mock him So my question for you is have you received him or have you rejected him? Have you considered the sinful pleasures of this world? Greater than the one who came to free you from them The truth is is that we have all rejected Jesus and rebelled against him either through our words or through our deeds But here's the good news in John 1 12 it says this but to all who did receive him who believed in his name He gave the right to become children of God today You have the opportunity to become a child of God and with all your heart I'm asking you to embrace him ask God to give you the faith and Convict you of your sin and see Jesus as the light and the life that you so desperately need See all of his forgiveness and his mercy and receive it I hope you enjoyed this video and got something from it It's my mission to help you find Jesus and follow him daily if that's a mission you want to get behind I'd ask you to help partner with me on patreon.com slash daily underscore disciple link in my bio Through your support this ministry keeps going and growing. It is a tremendous blessing. So thank you so much guys I'll be back with more videos. So subscribe Thanks again for watching and I'll see you next time. God bless


When you break up with a narcissist. We often talk about how narcissists discard their victims But what happens when you can't take it anymore? What happens when you get fed up with the name-calling the emotional or even physical abuse?  You need to do it very carefully. It will often create more problems. It will often create situations that are difficult to deal with. If you have experienced physical violence from the narcissist in the past and you feel that this may happen again if you try to leave. I highly recommend that you research domestic violence resources in your area. You may need to involve authorities to get a protection order or a restraining order. You need to keep yourself safe and away from any danger or harm. Narcissists do not like it when you break up with them. Because it means that they have lost their source of supply. They have lost their source of attention and admiration. In their minds you are supposed to attend to them and give them whatever they want whenever they want. You are not supposed to think for yourself or try to leave and do your own thing. When you try to break up with a narcissist it will cause a narcissistic injury. A narcissistic injury occurs when their fragile ego gets bruised. It affects their sense of self-esteem and self-importance. It makes them feel like they are under attack as though they are at risk of danger or harm. They cannot deal with criticism. They cannot deal with rejection. They are extremely sensitive.  But once you've lifted the veil, that false character fades away. They will only pretend to be nice if they believe that's going to get them what they want. But once you stop validating their false self, it's game over. Then you will see who they really are. The false self isn't real. It lacks any basis or foundation. So any criticism or slight remarks could cause it to collapse. It makes them feel like they are under attack and that is when they will lash out at you. They react to their injury with narcissistic rage. And this can be quite a frightening experience. It will often result in shouting and screaming. It may even involve physical violence. They will slam doors. They will damage your property. They will do whatever it takes to grab your attention and to feel as though they are something significant to you. When you try to break up with a narcissist, they're not just going to let you go without a fight. They're not just going to let you move on and live a happy and fulfilling life without them. But they're sitting at home alone and miserable. Misery loves company. So they're going to do whatever it takes to keep you tied to them. So that you can't just move on or let them go. They will engage in character assassination.  They will recruit anyone who knew both of you. And tell them terrible things about you where the real are imagined. They recruit flying monkeys to do their dirty work for them. To get you to do what they want. Or to get you to stay in and do more abuse. They will use whatever information they have. Things you might have privately confided in them. They might give half truths. Whatever it takes to get people to make them look like the good person or the victim. If you are going through a divorce with a narcissist, it will rarely be resolved through mediation. It will almost always end up going to court where you will need a lawyer. Divorce in a narcissist can be a very expensive breakup. Most narcissists will engage in unfair tactics. They will be deceitful and deceptive for an unfair advantage. And you are likely to lose a lot in the process. But even though this may pose a risk and a cost to the narcissist. Many of them will not back down. They will be willing to sink your ship. Even drowning themselves in the process. If it means that they can get to you. Narcissists are known to engage in never ending acts of vengeance. They will be committed to destroying your life. They will try to damage your reputation. They will try to put you out of work. They will make false accusations. And this can all be psychologically damaging to you. Which is why if you are planning on breaking up with a narcissist. You need to have a plan. You need to have a procedure that you can follow. In case of an emergency where you have to leave. Keep all of your documents and sentimental objects away from the narcissist. But leave anything that might be considered joint property. Take everything you need. Take all of your money and credit cards. You might want to keep your property in a safe place. With someone you can trust. If you are planning a divorce. You should be talking to a lawyer already. But even if you are not married. It can still be difficult. And you should still have a plan. You should still keep hold of all of your property. When you break up with a narcissist. They are going to be unkind. They are not going to have any compassion for you. Breakups hurt. And hurt people hurt people. Even for normal people. This is true. We all make mistakes. But this is different. Because when the narcissist experiences narcissistic rage. They have a never ending amount of anger. Where it just keeps going on and on. People may normally experience some anger from a breakup. But at some point they will let it go. Narcissists are very sensitive to criticism and rejection. It causes a narcissistic injury. And that is why it is so difficult for them to let it go. If you have broken up with a narcissist. And you have met someone new. It is highly likely that the narcissist will go after them. They will criticize them. They will stalk and harass them. And you may need to involve law enforcement. This could feel really overwhelming for your new partner. And it may be difficult for them to understand in the beginning. You may want to end the relationship.  You've had enough of the yelling. The name calling. The invalidation. But as you are moving on. You may notice that the narcissist moves on very quickly. And even though they may have found someone else. They may still continue attacking you. It depends how much supply they are getting from their new target. If the target keeps them occupied. They may not have any time to attack you. But they are unlikely to lose interest. If there are shared assets. A shared home. Or children. When you are planning to break up with a narcissist. You need to be prepared. Most breakups may take a few weeks. Until they're finally over. And the other person moves on. But when you break up with a narcissist. It can go on for years. Narcissists are very difficult people to deal with. And they could still be hassling you. Even years after you have broken up. Narcissists just cannot deal with any refusal or rejection. They will dedicate the rest of their lives. To trying to destroy you. It will become their new found purpose in life. For my future videos. If you would like to donate. My PayPal link is in the video description. Coaching inquiries. You can email me. At narcisfyvercoaching.com Thank you for watching and I'll talk to you soon.


We'll go back, this is part, Thrice. Thrice is nice. Watch along. Jaya, Jaya, Jaya, Jaya. Hey! The Malayalam film from 2022. How about that part two and one? It reminded me of other parts I've seen of other parts. Yeah, yeah. Three parts is a weird hairdo though. If you're watching this on YouTube, if you haven't seen the first two parts, please go check those out. But if you're watching this on YouTube, you can see a very, very cut up version, five, 10 minutes, very, very cut up footage because of copyright reasons. Yes. If you'd like to see full uncut unedited versions, you can head over to Patreon. Patreon, Patreon. To check out the full unedited version. And at the end of this reaction, you will see our, we'll discuss the film. Yes. End length. So, let's finish this now. Here we go. Jaya, don't be silent. Come, let's go home. No. Help her. Help her go wherever she wants to go. He has seemed like he was a, of everybody might be the one that could possibly be compassionate toward her. Hopefully. It sounds like, Yeah, yeah, yeah. Working woman. Good, he's helping her. No. What? I've talked to Raj for two days. I'm going to go home. Yep. I'm going to stay at home before I go home. Leave. Get out. Raj, what did you say? You didn't listen to me. Yeah, yeah. Why would she listen? Why would she listen to you? All you care about is what you want for her, not what she wants for herself. Also, her husband's beating her. What? Don't cry over it anymore. Go. You don't need them. They don't love you. Very believable. Very believable. I mean, how hard it would be. It's the only family she's known. Even though it's toxic, it's all she's known. And she's probably dreamt, please just love me. Just love me. Just love me. Dude, don't look at the people. Dude, don't worry. No one has seen this. I've sent messages to all the groups. No one has shared it. Don't worry. I'll take care of it. Can't stop a video from going viral, bro. Women are like this. Why did she do this in person? Yeah, right. Yeah. Talks the talk, doesn't walk the walk. I need one last climax fight scene, like where she just kicks all the people. Everybody just goes off. Yeah, right. Exactly. Parties, I am trying. This is brilliant. Give it to him. Then we'll find out who it is. Who is this? I don't know. I don't want to see him. Give him the divorce papers. Oh, nice. Who is this? That was very good. No reason at all. We can't give him the divorce papers.  Thank you, sir. Ah, everybody's seeing it.  Leave me alone. His voice cracked. Aw, poor baby. We can't live without them. That's all. Yeah, because you expect a mom, not a wife. Exactly. Bro. If you love him so much, why did you divorce him? Because I can't control her. She can whistle in her own place. No one's telling her to stop whistling. Woman judge. Nice. But what kind of woman judge is she? She's kind of like her mother-in-law. Right, we'll see. I'll give you one more chance. Why do you need a life? Such a decent guy. What? It's an objection. Why? They don't talk. It's true. It's true. It's true. It's true. Yes. Tell me, Dash.  All of you know that. Dash. What? Oh. Oh. That was him. That was him. Yup. I thought you were going to feed your own sister. And cause her fatso. I didn't understand because of the hormone change. Dash, how do you know a woman in your life? I'm sorry, bro. Then? Five places. Oh. Then? Subscribe. Give me a minute. You're going to make a simple lunch at home. Stop it. Calm down, bro. Good team. Good team, good team. Nice conversation. The same exact conversation reversed. She's the one in the power now. Nice bookend.  This is the best superhero movie of the year. How's that taste? That was nice with it ending with the matter of feet. Yeah. Thinking they still have the upper hand. Yeah.  Yeah, I understand. Thank you. That was fantastic. Absolutely phenomenal. Yeah, I don't. And that's a great, the way whoever described it to you said it's the great Indian kitchen with comedy. Yeah. It's a lighter take in a little more style on the subject matter of a gradient kitchen of toxic and abusive relationships in certain cultures. Just superlative in every way. I want to watch this with Andrani and with the kids. Yeah. This is going to be one I recommend, too. I think this is a really accessible film for folks who are not familiar with Indian cinema or Malayalam cinema in the West. Yeah. I think they could watch this and be blown away and go, I had no idea. Also who pissed them off, especially if they're not familiar with the culture at all sometimes or the subject matter and they haven't seen it a bunch like we have. And when it starts, it would make them think that what they're going to see is what they think Indian life is like with the stereotypical patriarchy, the kind of life they're living with the families, making the marriages and the arrangements. It's just, yeah. I'm kind of sorry we didn't see it any sooner, but I'm glad we finally got to it when we did. I don't remember it being in theaters when it was here, just like the other ones, but I would have loved to have seen it. It's a shame, yeah. Because... What platform is this on now? I think it's Netflix, actually. Okay, that's great. But, yeah, everything about it was just... The score. The score was incredible. One of the best scores. Definitely, you'll definitely be hearing about the score. Everybody's performances. Everybody, especially her and him. But everybody, the whole ensemble, this would have been one of those things that if it had been released in the States as an American film, I would have been telling people this thing needs nominations for best cast. Best film. Yeah, best film, best score. That's her name. Best direction, best writing. It's just Darshana Rajendra. I don't know if I've mispronounced that. Forgive me. I don't know if we've seen her name. Other than... Everybody. It was... It's like a great movie. Oh, I.R.U.L. Oh, we've seen that one, I think. No, we don't think so. Virus. Virus. That's where we've seen her. And we saw that a while back. Oh, and isn't that... No. Oh, okay, I thought that was the long name. I thought it was the boxing movie. No. It was Virus. Yeah, okay. So it was Virus and... What a great job. That we've seen her. Great job. Everybody. It's like I was saying in it. It just feels like no one takes risks and chances. And does originality like Maliello.  Because I think all industries make great films. Yeah, they make... They have their own contributions. Yes. But it's just so consistent with acting, story, originality, score even. Yes. And just doing different things that haven't been done before. Yes. And they're just like, yeah, let's do that. That seems awesome. Right. Which is what you hope, you know, all cinema would be. They also have the beautiful capacity. Because there are films that are entertainers. And there are films that are the high caliber artistry that are on the level with these great stories that you remember forever. With the fine art that are in the awards festivals and things of that nature, right? Yeah. And both have their place. Maliello and cinema, and this is a great example of it. They can blend both seamlessly. They can make a high level artistry film that should go on the film festival circuit and be talked about for its caliber of artistry and still be an entertainer. They do that all the time. Shout out to the director, Veepan Das. Because, yeah, if you would have, I would have loved to be in the pitch meeting for this because... Yeah. They're like, okay. Member of Great Indian Kitchen. Exactly. Right. Impactful. What if the film festival circuit made it funny and everything everywhere at all at once kind of like fights things a little bit? Yeah. Thoughts. Yeah. Exactly. And they're like, yes. Counting in. Which is like, it's just hard to conceptualize such an important and deep subject matter as abusive and toxic relationship between husband and wife and families as well. Right. Right. And in the culture. But then to be like, yeah, let's put some kung fu fight scenes. Right. Right. That outfit. And it's going to work. Yeah.  And I think one of the things that really Maliam does so well is that they incorporate unique scores into their films. Yeah. And that helps you kind of accept a lot of the different stuff that they would do as you're like, oh, this is corky. The score is oftentimes another character in the film. Yeah. This one especially. Yeah. I don't like that there's already a Hindi remake. No. Please. Just spread the love all over the world, man. This thing doesn't, this doesn't need to be redone. Mirkanis looks like he's producing. But then it's the only, oh Fatima, at least you get a good actress. But I mean. Yeah, but come on. Just watch the original. Watch the original. Because, yeah. It's already on the, it looks like the. Just spread the love. Read the subtitles. It looks like the original director is directing it. But it's like just. No. That doesn't work anymore, guys. Especially when something's as well made as this. Yeah. If you're going to remake something, take a film from 25 years ago that you want to retell in a fresh way. Yeah. Don't just make the same film for another audience because they refuse to watch it in the original language. Yeah. I actually think they should remake old films, not the good films that were old, but the bad films that had a good concept that wasn't done well. Yeah, of course. Remake those bad films into good films. Yeah. That's what we should be doing. Yeah, there's great films that we don't need. Having a remake of a film that came out last year, just to put it in Hindi, as opposed to literally just going and watching the Malayalam original version. Anyway, I want to stick more on the positive vibes. But yeah, everybody involved, even the husband as well. 100%. Great job. Is that Basil Joseph? Of the director of Manol Manari? Yes.  That was him? He played the husband? I know because I know the name Basil Joseph because we've seen... I didn't realize that he was... I recognized him as the person on screen. I didn't remember that he directed Manol Manari. Wow. I think we've seen him act before. Did a great job. Joji. Oh, Joji was in Joji as well. Did he didn't direct it? No, he didn't. Okay. But it looks like he's a director actor. And virus. He was in virus as well. Yes. Okay. So I thought we had seen him before, but I... Please. I'm just now making the connection that he was the director of Manol Manari. I really hope this was successful box office-wise, and I really hope it gets great legs. Wait, he was the voice for... Wait, was he the lead in Associates?  I'm trying to remember. No way. No, they just used his voice for something. Was that the... Yes. Was that the... That's the guy. Okay. So he played his voice, though. Or did he not? I don't know. It just gives him the credit for voice. Yeah, it's his self voice. I don't know what that means. Anyway, sorry. Just going down the rabbit hole here. Yeah, he did a very good job in his role. I really hated him. Yep. Everybody did. The family. Yeah, the family did a really good job. I believed all their toxicness and awfulness. Just nothing else to say. It's superlative at every level. I would have even loved another fight scene. I loved the climactic end fight scene, when she takes over the business. Yeah, that was a nice final touch. Yep.  Did she divorce it? Did she sign the divorce paper? That's what she signed at the end. That was the divorce paper. With the agreement to take over that part of the business. Yes. Okay. I just wanted to make sure that's what I understood. Yep. And she, because I was like, please. Because at first I thought the judge was going to be like, that's what she was saying, go to counseling. And I was like, oh. Well, she was at first, yeah. Oh, no. And then she was finally understanding what was going on, even though, you know. Which, and that sucks, if that's the reality that you can't get a divorce unless a judge gives you permission based on a reason that the judge deems okay.  Yeah. That's like once again. You can get a divorce for any reason you want here. You just need to specify a reason. And it's typically irreconcilable differences. Yeah. Yeah. But like, you don't have a, she doesn't have a choice in if she wants to get married. And once she gets married too. Yeah. Because that's the man's decision. Right. And she doesn't have a choice as to how she can get out of it. That's the other thing. If a woman wants to divorce her husband, any party who wants to get divorced, the other person doesn't have to agree. They're going to get served whether they want it or not. I think if I, like he was saying, if there's abuse or if there's a health reason or whatever, then she could file for divorce. But also, whatever. I love the culminating scene in its entirety. The judge did a great job. It was written really well. And I loved the three reasons she's specifying and what the men are saying the reasons.  Love it.   Great stuff. I'm watching it again. I will watch it many times. This is one I will share with a lot of people. Just like The Great Indian Kitchen, just a different vibe. That's a more serious vibe. Right. Which is no less great. That's a drama. It's a great film. One of my favorite Malayalam films. This one is surprising. This one has that same anger that you feel in The Great Indian Kitchen, but also it brings corkiness and maybe more of an accessibility for some people. I think so. And hopefully that you're smart enough to get the message. Right. Right. Because for some reason, I saw some people saying this was toxic, but not the way they were obviously toxic. The empowering of the film. The power, the empowering of the feminism. I don't know, man. I said that when we were watching it. I said there's going to be people who watch this and side with the men in this and find her to be the villain. Yes. I guess like the family was doing. Exactly. Yes. Phenomenal. Yeah. I'm sad I didn't get to watch this. I'm going to have to show this one to her. Yeah, she'll love it. She'll love it. So will Indrani. She'll love this. So will Ashley, Alexis and Micah. So will our friends. My mom will like this. I'm looking forward to watching this. This is one of those movies that when I've seen it, my next thought is I want to see this with other people to watch their reactions. Yeah. Yep. And I hope you enjoyed our reaction. Yeah. Our first, I do believe. I think so. Our first watch along for Mali Alam. I think that's right. If we've seen 30 Mali Alam films, which I might have seen more. We didn't do a watch along for See You Soon, right? No. Yeah. We might have seen more than 30, but if we've seen 30, we've had 28. It's about there. Yeah.  Of good Mali Alam films. Good Mali Alam films. I would say that 75% of them are just, not just good. They're great. So original. So well executed at every level of artistry. 33, it looks like if I put everything in the... Yeah, that sounds about right. In the playlist, correct? Yeah. So we had that one. This one is associated. And I know we have so many more. We still haven't even scratched the surface. It's the heck of a year, by the way, for Mali Alam. For Mali Alam. So this is just this year. Yeah. LJPs. Well, this is what we watch this year. We saw the LJP film, the Unius Associates. Irrata. Irrata. Roman. Yeah. Roman Chom. 2018, which you didn't see, but I saw that. Right, you saw that. No. If I got it. And I can't... It's hard to place, but it might... Because last year was RR, right? Yeah. And Kala. Kala. Yeah, it was between the two. This would have sucked. Because... It would have sucked to have had this in that argument. To have this associates and that one. That might be my top three, these. It would be and I... It would be harder because I love Kala. Kala's a great artist. I do. And then RR. And they're so... Right, they're so different. But... Yeah. But those three really do. I mean, if you want to show people, if people want to know the greatness of Indian cinema, just point out those three films from last year alone. It really is. The consistency with which Indian cinema, all industries, no other country in the world produces more quality cinema than India on an ongoing basis. That's true. Especially the Malayalam industry. Yeah. It's just... I mean, granted, we are... There's a lot, we don't know about a lot of other countries, obviously. Yes. And when we see international films, we are obviously deeply impressed with what we do see and I'm sure if we dove deep into those, we would be equally astonished. But of the two places we know the most, which are here in India, it's a mile, mile. So, if you're watching us on YouTube and you saw the very cut-up versions, if you'd like to see the full uncut versions, you can head over to Patreon. Patreon, Patreon. And comment, obviously, got all of them on there. I hope you enjoyed our watch along. Let us know what the next Malayalam film that we should review or watch along. Obviously, not all films are watch-along. Able. Worthy. Yeah. Not because they're not good, but just because, you know... There's not much to react to. Yeah, not much to react to. We're sitting there going. It's a really good one. The last one, the ballad of fights, would have been obviously... That would have been a great one. I saw when we did the review, a lot of people were like, we wanted a watch-along. Yeah. It would have been a great one, obviously. That would have been a great one to watch along. Watch-along as well. So, let us know what the next Malayalam watch along should be and what you thought about this film. We're at the halfway point of the year and I already don't know what's going to happen at the Demis because there's already been enough films right now that I don't know what I'm going to select. And you still got all the... We still got a whole other half-year coming. Jawaan, we got... Yeah. All the Malayalam film. We got the Vikram film that... No, this is going to be a tough, tough year. In the best way. Let us know what the next Malayalam watch along should be down below.