Well, welcome everybody to this OpenShift Commons briefing with Dan McPherson, one of my favorite folks on the OpenShift engineering team. And this, as I was saying earlier to Dan, this is something we should probably repeat every quarter as new people come on and old people forget some of the tips and tricks for using the different development tool chains for OpenShift. And it's really key, I think, to participating in the OpenShift community to understand all the different tools that we use in the development process and life cycles. So I'm really pleased to have Dan McPherson here today to walk us through some of them. If you have questions, put them in the chat room. We'll try, if it does, if there's a pause in Dan's talking, I'll try and read them off. And then we'll save most of them for the end of the conversation and I'll unmute folks and we'll have a conversation. Without further ado, here's Dan McPherson and let's start navigating. Okay, thanks, Dan. Yeah, so I'm one of the lead engineers with OpenShift. I've actually been working on the product pretty much since its inception. I'm going to try to give you guys a rundown here of basically what it means to be a contributor to OpenShift, both from a how do we take requirements as well as how we build the code and actually in the end deliver the product. So we're going to start with planning. I will warn you guys, I'm going to be jumping all the real place here going back and forth between charts and various, showing you various of the artifacts and pieces that we use to build everything. And if I get too fast, just yell, I'm going to try and slow down. Okay, so again, starting with planning, we use Trello for our planning. We picked Trello a couple of years ago, largely because we use an agile process where we use three big sprints. Trello is a pretty generic tool and fit nicely for that. But primarily Trello enabled us to be able to share everything we do externally. We're an open source company. We like to make everything we do public, and so it was a good fit for us. So actually, I'm going to actually show you guys that now. So there's a few tools here in Trello that are worth talking about. So when everyone can actually see our Trello publicly, and it's just that Trello.com slash Atomic OpenShift. And this is actually what it looks like whenever you are coming externally even without an ID, I'm not logged in here.  There's a couple of concepts though. So we first have a roadmap concept. That's what I'm showing here. And this roadmap concept has basically two main things. There's an epic backlog of all of the big concepts that we're working on, as well as a number of lists of what we previously have accomplished for both the 2x time frame and the 3x time frame. And as far as the backlog goes, we try and maintain this in a rough priority order, although I will get the caveat of, given the major rewrite we just did for 3.x, the priorities was pretty much a matter of time, we had tons of very, very high priorities. So you will see this every time. Go back to more of a here are the next five or six things that are at the top of the list that are most important. And so for each one of these items, it has two main lists in it. One list of scenarios and one list of future scenarios. These lists tend to match up to things that we are working on for the current release versus things that are at some point in the future we will work on them. And there's two types of things in this list. So you have links to other cards. And these cards are on other boards that a given team is working on. And then as well as things that are added in here directly. And at some point we will, with the items that are added directly, we will come in and convert these to a card and move them to a particular team board. As far as the ones that are linked to team boards already, those are actually automated so that whenever they are finished, on a team board, they will be automatically checked off on this list. So we don't actually add the items in here. They're added in automatically with a set of scripting that we've built around Trello. Okay, so that's the roadmap board. Now I'm gonna show you one of the team boards here. The team boards we have a lot of teams and each of the teams run through roughly the same process. This happens to be our user interface team. And the way this process works, again, we do sprinting and agile. And so we basically move everything in here from left to right as things go through the process. So as new requirements come in, they'll be added to the new list. These requirements can come from engineers. They can come from product managers. They can come from someone getting an external request and coming and adding it into Trello directly. And so again, they start on the new list. We do backlog grooming once every sprint for each of the teams. At which point the teams will go through the items in the new list, decide whether or not they are well-formed enough. And if so, move them into the backlog. And the backlog for each team we maintain in a rough priori order. The next list is basically the top of that backlog of the things that we're planning on working on for the next milestone. And then once we get past the next, we start working on them to move into in progress, complete and accepted are various stages of whether or not it's gone through QB and then everything after that is a list of previous sprints. So that's a team board. I'm going to go back to the presentation. Actually, I will mention before I do that, we do have a summary of this as well. We host a summary off of our CI environment. We built this basically for an easy way to get a high level summary of everything that's going on across all the teams. And so there's a few pages here that are interesting. The roadmap overview is essentially a list of what is on the roadmap board. I just showed you just in a slightly more verbose format that lets you see everything all on one page. And then if you want to get an idea of what's happening at a team level, going back in time as well, we have the sprints overview, which for each team here, there's a list of essentially what's currently happening, what has happened over the last few sprints. The previous sprints overview is basically the same thing except for for going back further in time, but it's not refreshing, right? Oh, never mind, it's just because that team hasn't been around quite as long. So you can see here, the team goes back as far as December of last year to get a long-term history. Actually, the last one I'll show here is the sprint schedule. So if you want to get an idea of when our sprint boundaries are, you can always refer to this page. And again, they're three-week sprints. This basically just shows projecting out through time when those sprints will end. Okay, I want to get back to the presentation. Okay, so next up is the development process. We have a lot of options for actually developing an open shift. The primary two that people actually use for doing development are either using local development, in which case you have to have a machine which can run, get, go, and docker. And there's a link here to the specific instructions to get that set up. And then you can also use Vagrant. We have Vagrant with VirtualBox and Libbert images published. And that basically lets you do development against any local system. And I would say even amongst our development team, we probably have a roughly 50-50 split between using either pure local environment running docker locally or using Vagrant. And actually, I'm going to go back now and do a little more demoing. So actually, what I'm going to show here is a really quick example of how simple it is to get up and start it with the Vagrant. Can you make your view much, much bigger? Yeah, sure. Thanks. That looks great. OK. So yeah, so I am inside of the open shift origin Git repo here. And we have a Vagrant file checked into that. There are actually more advanced versions of this using a plugin we created called Vagrant OpenShift. It's not a requirement.  And we also have CentOS images published as well. And so what this does is it will pull down the images if you haven't already pulled it down, which I have for purposes of this demo. And it will actually melt in your source locally if you have a source locally. If not, you can use source that's on the VM directly. Most people tend to prefer local. Just tends to be how most developers want to work. And so yeah, so in this case, it's already started up here. It's actually showing here it has melted in the source. And so what I'm going to do is SSH to that instance now. And I'm actually going to start up OpenShift. I'm just going to run status on that to make sure it started. OK. Does appear that it's running. And at that point, we actually do port mapping, which it showed whenever it started up, port mapping of all of the interesting ports from the instance to your local instance. And so if I go back to the browser here, it'll look closed. It will actually have a console running. And so, and this is just OpenShift running inside of that VM, port map back to my local host. So pretty simple. As far as making changes, like I said, most people would mount the source in, make the changes, and that point can run builds and everything is all local. So it's a pretty simple setup to get going. OK, so a few more things as far as source code and why we're talking about it. So again, our primary repo here is the origin repo. There are a number of secondary repos for building images and sourced image and a few other external secondary projects to origin. The origin is the primary one. The origin is what we embed Kubernetes into. Most of our actual code is under package within the origin repo. And as far as Kubernetes goes, like I said, we embed Kubernetes in here. I mean, it's used in two ways. So we expose Kubernetes directly. So basically everything that's in Kubernetes is exposed directly through OpenShift. And it's also the case that we use Kubernetes as a set of libraries to build our code on top of. And so, yeah, so if you look under Workspace here, you can see the actual. That's the entire Kubernetes code base, which is embedded inside of origin here. And we tend to rebase on or basically pull in that dependency roughly once a sprint. So roughly over three weeks. Now, I mentioned the two main ways of developing here using either local or using the vagrant image. There's a third way, which depending on what kind of development you're doing may be relevant, which is we also publish a Docker image of origin to Docker Hub. And so you can always just do a Docker run on the origin image. I guess it's Docker run OpenShift slash origin and be able to do development with OpenShift. So for example, if you're building images to run on top of OpenShift, that's a very, very simple way to do it. All of them are still valid if you want to build images. But running the Docker image is probably the simplest. And actually one last thing while I'm in here, as far as the code base goes, we do also do releases of origin. So basically every time that we are spinning a release of origin, there's usually an enterprise release that follows it fairly soon after. The version numbers don't match here, but you can get a rough idea of what's going to land in the next enterprise release by seeing what's happening in the origin release notes. Actually the presentation. Okay, so next up, we certainly accept pull request. We have a number of external contributors now to the origin project. And it's the case that you can always submit a pull request for anything you want to see changed. It's also the case that you can submit issues for things that you want to see changed, but don't necessarily have the time or skills to make the change yourself. Generally, I would recommend that if you want to make a change, then you probably should ask yourself, are you willing to invest the time to make the change first? Or do you want to discuss it? If it's a really small change, then you're probably fine just submitting the pull request with a change and discussing it as part of that submission. If it's a really big change or some sort of re-architecturing or restructuring of the code, rather than then go through all the work to make a change first, I would probably recommend submitting an issue to start against the origin project and discussing it there. And usually that will wind up in a solution that everyone is happy with. So next up here is actually what happens once you do submit a pull request. Whenever we started the OpenShift project, we started with a relatively small group of five or six people, roughly five years ago now. And at that point in time, we did what a lot of folks get away with as far as continuous integration, which is those five people work pretty closely together and they submitted code.  And every once in a while, the test cases would break and it would be pretty obvious what changed and what we would need to go fix to fix it. And at some point in time, we realized that once we got to 10 or 15 or so people, it was the case that it was always broken because amongst those 10 or 15 well-intended people, someone at some point in time was always going to be breaking the code base. And so we were always in a state basically of the CI system was broken and we had to debug which of the 10 to 15 people making changes all day long broke it, which changed whether and how do we undo it or fix it. And that became a pretty tedious process and was a pretty big effort on everyone's part to maintain it. And so what we sort of do that is continuous integration 1.0. And so we needed to move beyond that. And so there are some systems now which are relatively prevalent like Travis CI, which have also sort of moved beyond that. And that's sort of what we consider CI 2.0, which is being able to test the code changes against the pull request without actually having to merge it. And so we ourselves developed a system to do this very closely integrated with GitHub. There are other systems as well like Garrett that give you a way to do this. However, whenever you start using the system like Garrett, you somewhat have to divorce yourself from a nice GitHub pull request model.  And I will say you do not need to read this entire diagram here. There's a lot on the page, which all of this is still exactly what we do. But for the purposes of getting involved, you do not need to understand that much complexity. So again, there's systems like Travis CI, which have this model of you submit port request and they go test your code whenever you submit the port request. There are some downsides with Travis CI in addition to you can't run everything. So we can't run Docker actually with Travis CI yet, which limits us on what we can actually test. The other big issue with Travis is that it does not handle a queuing mechanism. And so there's no guarantee that you won't have two people submit code changes that conflict. It also doesn't give you anything more than a point in time. So if someone submits a port request and it sits there for a week, someone might come along a week later and say, OK, it passed the test. I'm going to merge it. But that was a week ago and stuff may have changed since then. So that if you actually were to run those tests again, they would not pass again. So to be fair, though, we actually did develop this even before Travis CI was totally in place. We actually do use Travis CI now, which you'll see on some of the coming pages, has sort of a first pass. But we do more than that to guarantee that code actually makes it into master is actually still correct and valid. And so again, the way we do that is we have a merge queue. That merge queue test emerges one thing at a time. It guarantees that all of the test cases actually pass so that you know that there was no delta other than that one pull request. And we completely tested that pull request with what was previously on master. And basically you have to wait your turn in the queue before you actually get merged. Now, we don't have a list of trusted users who have merged permission. And we'll talk a little bit later about testing as well, which is a more expanded list. We actually make it so that almost no one actually has real push permission to our repos, which means basically it's difficult for someone to even shoot themselves in the foot and accidentally push something to master. So it's a system basically that we develop to make sure that we do keep a stable code base at all times, which means that whenever we expanded even beyond the 10 to 15 people, we always know that the code that's on master is still valid, which keeps all of those people productive. We didn't build a system with Jenkins as well as a decent bit of scripting that ties together with Jenkins to provide the functionality. Okay, so this is an example of pull request, or at least the bits of the pull request that are relevant here. And this pull request is relative to the common, right? So you'll have someone come in and review a change. And whenever they review the change, they will first go through a series of comments, making sure that things are okay. And once they agree that everything is good, then they will add this merge tag. So you can see the merge in square brackets here. That indicates to the bot that the bot should go and test the change. And then you see the bot commenting back. So the bot will first comment and say it's running the test cases. And then at the end of it, if it succeeds, it will actually merge the code. And you see here, in this case, it did succeed. And the bot actually merged that commit in. There's actually two things here that are printed. One is from Travis, and the other one is from our bot. And actually the bot hasn't actually updated this yet. But eventually the bot would check mark here as well. And I mentioned we also have test. Test is something which quite often people will add before they add merge. So a common use case might be a person would see a change come in, or pull request come in. And before they go, take the time to fully review the changes and make sure that everything's okay. They'll first add a test tag just to know like does it still function. And before they go spend all the time to review it, it's useful just to make sure that the person submitting the code actually has a valid change before it's reviewed. Or in actuality, our own developers even will often just use this to validate their own code. It's easier in some cases to submit the pull request and have Jenkins run the test cases than it is for them to run all the test cases locally. And in this example actually that you're looking at, it's actually the case that the bot actually asked for it to be tested at the time. So that's a way for while you're waiting in the merge queue for something to actually get merged, the bot will, if there is a queue, meaning there's more than one person currently in it, the bot will ask that we run tests against it before we even get to the merge queue. That way, if you are fourth or fifth in line, you'll get early feedback to know wherever you get to the top of the queue, do you actually have a chance of passing? Okay, so I mentioned before we do use Jenkins for this. You don't necessarily have to be too aware of this. It is a public Jenkins, so all the links that we put in the pull request will show up as something you can click on. All of them run through a couple of jobs here. So they either run through merge pull request origin or test pull request origin here. And so for each one of these, you can see that it's going to report success or failure. If it does succeed, it's going to put a link here to the pull request afterwards. And for each one, you can click on it and see the logs of what actually happened. Again, this one passed. So very last thing it did was update the particular pull request. So if we actually click on that pull request here, you can see the bot actually reported back that it was successful. And in this case, someone six minutes ago actually just added a merge tag. So now it's actually in the process of getting merged. All right, let's go back to the presentation. Okay, this is sort of extra credit, but just so everyone's aware, we do also have a set of extended test cases. Extended test cases are, let me actually start with, it is the case that test emerge would try to be pretty rigid about how long they take. So we generally like for it to be less than 30 minutes. We tend to get pretty angry when it's over an hour because no one wants to wait very long for their code to get merged. And so generally it stays somewhere in between those two boundaries because of that. And so currently we're in the process of trying to get it down and trying to add more test cases to it, am I adding more parallelism to it? But it's always gonna be the case that we have some set of test cases that take too long to run. So a good example of that would be a reliability test case. So a test case that says, I'm gonna drive the system for two hours and make sure that it stays running constantly in a good state for those two hours or take a longer time period. There technically is no way you can run that in less than two hours. And we can't wait on that for every single merge to happen. And so we fit those into additional buckets of test cases that are our extended buckets. And it is possible to request those extended buckets to run as part of tests, but not merge. And so the general flow would be, someone would submit a pull request and we would say, okay, this is a risky enough change or we know that we have test cases, but they are in extended. And the reviewer would add an additional command here, directive of extended colon and then the list of buckets. You can add multiple buckets, comma, separated. In this case, they actually ask for all of the test cases to be run, all the extended test cases to be run. And like I said, we don't block on these for merge, but you can ask for them with test. Your test will then take longer to actually happen. And then it's the case that after each merge, we kick off an additional build. I mean, the official build basically for the QE team to look at it. And that official build is after official build finishes, we then run the extended test cases to make sure that those are continuously run just after the fact. So it's sort of the model that we don't prefer that we originally had that I described before of, they could break because we're not guaranteeing that we run them ahead of time. Unfortunately, we just don't have a way to make every single test case run instantaneously. So it's just reality, but at least we limit the amount of test cases that fit into those buckets as much as possible. Okay, we also do our documentation publicly, so I'll show that real quick here. So this is the same documentation that is generated from the same code that ends up for the origin and enterprise and actually only as well documentation. And so this is the origin version of it. It's docs.openship.com for the enterprise version of it. And all of that documentation is generated from this Openship Docs repo. So it's something that we like being public because it means that it's very easy for our developers as well as external people to open issues or poor bust or whatever they, wherever they see changes that need to be made. It's very easy for anyone to do it rather than hit them behind some wall. Lastly here, actually I will show a little bit more Jenkins. But the last slide here at least, I wanted to mention was we do use two mechanisms I mentioned GitHub issues before for being able to open bugs. And we also have bugzilla. So both of these are valid. We treat them relatively equally. So this is our issues list in origin. There's a lot here obviously. And if you want to open bugs against bugzilla, it's under the OpenShift Origin or OpenShift Enterprise product. And just make sure specified version, we will change it if you get wrong, but try to specify the version you're appropriate to which one you're asking for a reporting issue or asking for a feature against. And we have time here. So I will go back and show one quick thing here in Jenkins, which is one of the things actually in that flow chart that I showed before is we also have the ability to do something that we call 4KMIs. So 4KMIs are one more variation on us being able to run our test against code before it gets merged into master. And so a very typical use case for 4KMI is we've made a major change to the code base and we may be able to pass all of our test cases. But things like the reliability test, things like performance testing, more rigorous testing that our QE team may do. We don't have a way to get to those except for 4KMI. And so we basically developed the 4KMI system as a means to be able to be able to submit your code to your branch or your fork and GitHub. And then we can create a 4KMI which creates an official build that our QE team is able to do a full regression against at that point. And so no matter how big the change is, it's something that we never want to risk putting risky stuff into master. And so if you ever do submit a change and it's something where it does have some amount of risk to it, you may see us go through a 4KMI process with it. You say we do this ourselves on a pretty regular basis. And so it basically just means that the change is risky enough that we do want to allow our QE team to do a full regression, essentially, against it before it does go into master. That's probably the last major piece that really is relevant to external contributors. Okay, so I think that's the majority of what I wanted to show. So I guess we can open up before here for questions now. All right, thank you, Dan. That was awesome and a lot in one sitting. So but I think it's a great overview and a great way to get started. I'm looking to see if there's any questions. If there are, if you can type into chat and I'll unmute you if you'd like to speak rather than talk, if not, then I expect you're all going to be experts on this and be doing pull requests, logging bugs and fixing them very shortly. We did get one request to update the OpenShift.org site from Chuck. And I will definitely say that we are working on a new version of the OpenShift.org site that incorporates the atomic pieces as well. So that's happening as we speak. Okay, so there's a question here about when should you open a bug against GitHub or get up issue versus a bugzilla bug? And the answer there is both are OK. We internally, our QE team tends to use bugzilla. Extra only more people tend to use GitHub. We treat them both equally from a triage perspective. So every single sprint, we go through the bugs in both lists to figure out what things need to be fixed versus and if they don't need to fix immediately, then they get prioritized into a list. So it's really a matter of whatever you're more comfortable with is is the right answer. And if you're very used to the OpenShift and OpenShift origin, Dan did point out that OpenShift and that is a great place to even start extending the documentation or asking questions to some more clarifications on pieces of the documentation that aren't up to snow. And we'll probably ask you for feedback on that. And get that going because the documentation is one of the key pieces of the project. So if you're looking for some place to start, join us in fixing up some of the documentation for the week. And if there's no other questions, then I'm going to really say a big thank you to Dan for doing this. It's very thorough. It'll be up recorded. So if you want to play it back and look over some of the things or see slides, the URLs, it'll be up probably first thing tomorrow morning on the commons.openshift.org site. So thank you again, Dan, for doing this. And I think I will try and make this a semi quarterly event because we keep having new members coming in the commons and we need to get up to speed. It's great. Thanks very much. Yeah, thanks, everyone. Take care.


Hey fam, Raif Derrazy here and this is your weekly roundup of the latest HIV news for the week of March 11th through March 17th. Today I'll be going through 13 articles covering topics ranging from gene editing breakthrough, with hopes for an eventual cure. New drug candidates could help reveal hidden HIV in latent reservoirs, a drug that helps reduce liver disease in people with HIV, the state of HIV criminalization in the US, and more. I won't be reading the articles per se, but I will give you a brief summary and sometimes throw in my own opinion and or commentary. If you'd like access to the complete articles, all links will be available in the description box below. A big shout out and thank you to Todd Martin for $5 super thanks. On last week's HIV news video, I really appreciate you all very much for helping to support my continued work on this channel. Alright, jumping right in, number one, the American Journal of Managed Care. Big Ted Revere receives expanded indication by FDA to treat HIV. The FDA has expanded the approval for Big Ted Revere, also known as Big Tar Vee, the drug developed by Gilead as a treatment for people with HIV, who have resistance to M184Vi, a type of nucleoside reverse transcriptase inhibitor, or NRTI, and are virally suppressed. This makes Big Ted Revere the only FDA approved treatment recommended for people with HIV with this specific pattern of resistance. The approval is based on study 4030 which showed that 89% of participants with M184Vi resistance maintained viral suppression after 48 weeks of Big Ted Revere treatment. Big Ted Revere's safety profile remained consistent with common side effects including diarrhea, nausea, and headache. This expanded indication offers a new option for people with HIV with treatment resistant HIV, potentially improving long term disease management. Number two, NIAID. Children surpass a year of HIV remission after treatment pause. At the recent 2024 conference on retroviruses and opportunistic infections, also known as CROI, researchers shared promising results from a clinical trial involving four children living with HIV who achieved HIV remission after pausing their antiretroviral therapy. HIV remission being defined as having viral suppression even after discontinuing treatment. These children who were born with HIV started ART within 48 hours of birth as part of a National Institutes of Health funded trial. After meeting specific criteria, including sustained HIV suppression and certain immune cell counts, their ART was interrupted. Remarkably, four out of six children experienced HIV remission for at least 48 weeks off ART. While this study highlights significant progress in pediatric HIV treatment, further researchers needed to understand the mechanisms behind these outcomes and to explore the potential of very early ART initiation in managing HIV in infants. It's important to note that two children did not achieve HIV remission and one child experienced remission for 80 weeks, but then their HIV rebounded to detectable levels. Number three, BRO BIBLE. Aaron Rodgers says that HIV was created by the US government, quote, the game plan was made in the 80s, end quote. Aaron Rodgers, the quarterback for the New York Jets sparked controversy with his recent appearance on a podcast where he discussed various topics, including his belief that the government created HIV in the 1980s. Rodgers implied that Dr. Anthony Fauci was involved in this alleged plan and criticized the reliance on certain treatments like AZT and Remdesivir. While the New York Jets have not yet commented on Rodgers views, former NFL receiver Antonio Brown joked about Rodgers' controversial statements on X Twitter. Number four, FORBS. Americans are becoming more uncomfortable interacting with co-workers living with HIV report shows. GLAAD and Gilead Compass Initiative's recent report on HIV stigma reveals concerning trends that hinder efforts to combat the virus. Despite progress, intolerance towards certain groups living with HIV is increasing, with a significant portion expressing discomfort interacting with people living with HIV. Shockingly, Gen Z shows alarmingly low knowledge about HIV compared to previous generations, highlighting the need for comprehensive education efforts. Media portrayal of HIV positive characters has improved, but social media remains an underutilized tool in commanding stigma. I believe the amount of people that encountered content on social media that was from a person living with HIV was like 16% really low. Strong leadership and advocacy are essential to bridge knowledge and empathy gaps in HIV stigma, emphasizing the importance of accelerating efforts to educate and raise awareness about HIV AIDS. I created this shorts video about some of the stats you can check out as well. Pink News Public support for equal marriage dips in the US for the first time in almost a decade. The Public Religion Research Institute, or PRRI, conducted a survey across all 50 states to gauge American views on LGBTQ plus equality issues in 2023. The results showed a slight decline in support for LGBTQ plus rights compared to the previous year, particularly in areas such as non-discrimination protections, religiously based service refusals, and same-sex marriage. While democratic attitudes remained stable, Republican opposition to LGBTQ plus rights grew. Despite this, the majority of respondents still endorsed anti-discrimination protections and supported same-sex marriage. The survey also highlighted a correlation between support for Christian nationalism and opposition to LGBTQ plus rights. Melissa Duckman, PRRI's chief executive, emphasized the impact of LGBTQ identity being used as a divisive issue in the nation's cultural conflicts. The American Civil Liberties Union identified over 500 anti-LGBTQ plus bills passed last year, indicating ongoing challenges for LGBTQ plus rights advocacy. Though not HIV specific, I included this article because after reading the previous article, it speaks to a troubling trend in the US. This also can contribute to increased stigma and challenges for ending the HIV epidemic in the US, which is our goal in 2030. Number 6. The Buckeye Flame. He's 23 and in an Ohio prison for exposing someone to HIV, even though he couldn't transmit the virus. 22-year-old Kamar Weaver, born with HIV, found himself facing prison time because of his status. Quote, months earlier, the 22-year-old had reconnected with a high school friend. After chatting on social media, they hung out, and eventually he gave her oral sex. Weaver thought his friend remembered he was living with HIV. He had been open about it his entire life. But after he reminded her, she got upset and called the police. Kamar Weaver said, quote, she flipped out.  I just kept telling her that you can't get HIV from saliva, Weaver said. Despite little to no risk of transmission and his partner testing negative, Weaver was charged with felonious assault. Judge Critchbaum, who deemed HIV lethal, sentenced him to a year in prison, citing the law. Weaver's case underscores the need to reform Ohio's outdated HIV laws disproportionately impacting marginalized communities. Advocates argue these laws perpetuate stigma and discourage testing. Weaver, using his time to reflect, sees his HIV status not as a curse, but as a story to tell amid calls for reform. Folks, these are the types of laws, still in existence in various states in the US, the inherent stigma in not only the law, but in that judge seems to be very apparent. The judge actually told Kamar, quote, you disrespect everything that's proper and moral and ethical. Judge R. Scott Critchbaum told him what Weaver did was, quote, like shooting a gun and hitting somebody and they survive, Critchbaum said. That's what this crime is, end quote. Weaver is currently serving a year and 30 days in prison. While the article does state as a child, the medical treatment kept the levels of virus in his body at undetectable levels and quote, it makes no mention of his viral load currently. Presumably he's undetectable now as well. So it couldn't be transmitted through his saliva and he's presumably undetectable, which means he can't transmit sexually anyway. It did mention that he was born a female and would be serving time in a female prison. I'd imagine that that also had a role to play in the judge's comments about impropriety and immorality. Number seven, the Baltimore Banner, commentary, Maryland must stop criminalizing people living with HIV. In Maryland, people living with HIV can face criminal prosecution, even if they have disclosed their status, used protection, or are virally suppressed. A law dating back to 1989 criminalizes HIV transmission leading to imprisonment for behaviors like spitting and biting. This law fosters stigma, deters testing and creates barriers to health care. And aims to repeal this unjust law, which disproportionately affects black Marylanders. And pointing to one more criminalization article, number eight, Louisiana illuminator, HIV no longer a death sentence, but Louisiana laws target people who live with it. I don't, I'm not sure about the title because most of this is about Tennessee. So the case of LaShonda Salinas arrested in 2007 for allegedly exposing her ex-boyfriend to HIV sheds light on Tennessee's harsh HIV criminalization laws. Despite her denial of the allegations, Salinas faced severe penalties, including joining the sex offender registry, which affected her life profoundly. While Tennessee is slowly making reforms, individuals like Salinas continue to advocate for change, challenging laws that hinder their access to housing and employment and perpetuate stigma. Number nine, AIDS map, Lenna Kappavir plus broadly neutralizing antibodies may offer twice yearly treatment option. A recent study presented at the 30th CROI conference suggests that Lenna Kappavir, also known as Sunlenka, an antiretroviral drug taken every six months, when combined with two broadly neutralizing antibodies, teropavimab and zidliervimab, could create a complete twice yearly regimen for HIV treatment. Professor Joseph Aaron reported that 90% of participants in the study maintained undetectable viral loads six months after stopping their existing antiretroviral therapy. Lenna Kappavir, a capsid inhibitor, offers a promising alternative for people with multi drug resistant HIV. The study shows potential for long acting treatment options, offering hope for simplifying HIV management and improving adherence. Further trials are underway to assess the long term effectiveness of this regimen. Number 10, Euro news. New drug candidates could unmask HIV infected cells that evade the immune system. Researchers at the University of Pittsburgh School of Medicine have discovered new drug candidates that could potentially unveil HIV infected cells, allowing the immune system to detect and eliminate them. These compounds called protax target a protein called neph, which helps HIV infected cells evade detection by the immune system. By marking neph for degradation or destroying it, these drug candidates could restore HIV antigens on the cell surface, making infected cells visible to the immune system for destruction. While this discovery offers promise, further research and testing are needed before potential clinical trials. This approach represents a novel strategy in combating HIV and may have implications for other infectious diseases as well. Number 11, health day. GLP-1RA reduces severity of steatotic liver disease in people with HIV. A study again presented at CROI revealed that semaglitude, the drug that comprises ozempic, a medication used for people with HIV and metabolic associated steatotic liver disease or MASLD, led to significant reductions in liver fat content. Conducted by Dr. Jordan E. Lake and colleagues from the University of Texas at Houston, the study involved 49 participants who received semaglitude for 24 weeks. Results showed that semaglitude was well tolerated, with notable decreases in intrahypatic triglyceride levels or IHTG, nearly 29% of participants experienced complete resolution of MASLD, while 58% saw a significant reduction in IHTG. Moreover, improvements were observed in waist circumference, glucose levels, and triglyceride concentrations. The study suggests that low dose semaglitude could be a safe and effective treatment for MASLD in people with HIV, offering broader cardiometabolic benefits. So not only is this a drug that seems to be helping a lot of people with weight loss, but it could be helpful in this respect as well. Number 12. Queerty. In ultra prep injection, just three times a year could be on the way. Vive HealthCare has developed a new type of prep injection that could revolutionize HIV prevention. The injection called cabotegravir ultra long acting requires only three injections per year, compared to the current two month regimen. Results from a trial presented at CROI showed promising outcomes, with the new formulation being better tolerated and absorbed more slowly, resulting in fewer side effects. If further trials are successful, this strengthened form of cabotegravir could be administered every four months. Dr. Kimberly Smith from Vive HealthCare expressed enthusiasm about the potential of longer acting medications to alleviate the burden of daily treatments for HIV. The new formulation will undergo larger clinical trials, paving the way for advancements in HIV prevention and treatment. And last but not least, number 13, Sky News, hopes of HIV cure after breakthrough using gene editing scissors. Exciting news emerges as scientists make significant progress towards a potential cure for HIV by successfully eradicating the virus from cells in a lab using the gene editing tool CRISPR CAS. Acting like molecular scissors, this technology precisely targets HIV DNA, cutting it out from infected cells. Researchers from Amsterdam University Medical Center in the Netherlands aimed to develop a safe and effective CRISPR CAS regimen capable of eliminating diverse HIV strains across different cellular contexts. Their approach targets consistent parts of the virus found in all HIV strains, aiming for a broad spectrum therapy to combat multiple variants effectively. While this represents a pivotal advancement towards a cure strategy, further optimization and safety considerations are needed before clinical trials in humans can be conducted. Despite these promising findings, it's important to note that a functional HIV cure is still in the development stages. Links to all these articles can be found in the description box below this video. If you would like to join my new mailing list, I'm just starting it now. There's a link in the description box below. Once I get a good number of folks on the email list, I will start putting together quarterly email blasts, maybe even more frequently with updates on me, teasers of what's to come, some news highlights, perhaps share some thoughts on the state of things and some fun surprises. As usual, it's totally free and you get to stay better connected with me and what's going on. Be sure to like this video, subscribe, and hit that bell icon so you get a notification every time a new video comes out. And please share this with anyone who might find value in this content. Those are the best ways that you can help support me and my content. Until next time, cheers!


Okay, so you can turn to Psalm 32 and verse 8, Psalm 32 and verse 8 where the Lord says, I will instruct you and teach you in the way you should go. I will guide you with my eye. Okay, so the Lord is talking about instructing, teaching, guiding like three different things and I mean it's it's it's greatly reassuring because okay, Prince is saying increase the volume a bit. Okay, now Prince, is it better? Check two, three, but you're getting the reverb now. Okay, I hope that's better. Okay, so Psalm 32, the Lord is saying I will instruct you and teach you in the way you should go. I will guide you with my eye and what is reassuring is that you know these are very very confirming and it's like the Lord is saying I will, I will instruct, I will teach, I will guide you and and then I says, I will instruct you, teach you in the way you should go. I will guide you with my eye which is again I will guide you with my eye and then goes on to say in the next verse, do not be like the horse or like the mule which have no understanding which must be harnessed with bit and brittle else they will not come near you. Right, so like you really have to force these animals in order to for them to you know come to you and then you need to control them etc. But so the Lord is saying don't be like that and but I will teach, I will instruct, I will guide and he's saying I will guide you with my eye which is which is really a sign of intimacy, right, a closeness. The Lord is saying I will guide you with my eye. Okay, so we have the privilege today to be instructed, to be taught, to be guided by the Holy Spirit and while we have the principles and precepts to fall back on to say okay this is the heart of God, this is the nature of God, but we have the privilege of being intimately led by Him. Right, so he's saying I will guide you with my eye which means that you know one needs to observe the face of the person in order to be guided by the eye. Right, in order to notice even those small gestures and we have the privilege, we are we don't not only have the privilege but we are invited into that kind of a relationship. Right, so why don't we just pray and say Lord I we thank you for this kind of intimate relationship that we have the privilege of walking in but also that you are inviting us, inviting us to this. It is it is ours. Right, so let's pray. Father God, this morning we just want to thank you Lord, we thank you for this for these I will statements God that you will instruct us, that you will teach us, that you will guide us and Lord we thank you that it is not from a distance, Lord from a place of Lord just legalistic kind of set of rules Lord but but a living intimate close relationship oh God that you are calling us to and that you will even guide us with your eye and we thank you for the work of the Holy Spirit in each one of us as believers and we thank you it's Lord it's something that you're inviting us to and Lord we pray today that it will be a step of walking closer Lord today that it will be a step to understand your heart Father God and and walk in line with your word God we thank you in Jesus' matchless name we pray amen amen okay so that really today you know this this verse really came alive today because as I was coming to the Bible college today and I thought I won't make it because there was so much traffic from just crossing that ring road I said God today is gone I think I'll have to call and cancel the class and then thank God for Google map your entire life gets rerouted and yeah so so at this I just reminded over and over again you know the Lord saying I will teach and so I was able to reach here earlier than if I would have taken that route taking all those shortcuts and all that so so anyway the Lord's teaching guiding instructing is is for our benefit it's for our advantage and and sometimes we go through some tough tough times tough seasons and and the Lord is really you know burning up certain things in us building strength in us refining us so that we can be better yeah okay okay so where did we stop last class okay so we were looking at six practical rules for interpreting scripture right so why is it important to believe correctly anyone why is why is it important to rightfully divide the word word in order to apply it at least like we cannot just get the things over with it and also if we interpret scripture properly when we know the context when we know when it's written to the audience we can just take the principles and then apply it hmm true so the rightfully defining the word is important for us to rightly believe and because our conviction leads to our living like decisions choices living the way we live our lives and if we are going to believe that you know for example on a road if you're going to believe that every green light means stop and every red light means go if you're going to believe sincerely in our heart now that's going to end up in chaos so so that's the thing you know it's dangerous to to I mean divide the word wrongly and apply it that's how heresies are born that's how pulse are born that's how you know things happen so so it's important so that's why Paul instructs Timothy and he says you know rightly divide the word of God and he says you know you give yourself entirely to these things to the teachings that your progress may be evident to all you know there is going to be spiritual progress and it's going to be tangible going to be visible to all right so it's very important for us to know that so we said okay this is these are some rules that we're going to use in order to interpret okay interpret in the light of the context we said okay let me just share the notes also okay so we said interpret in the context of the passage and interpret in the light of progressive revelation and I think that's where yeah we had that question about you know if about polygamy and you know so see one thing about progressive revelation is it's not that we are taking a U-turn okay so what do we mean by that when it comes to progressive revelation it's not like God is saying at the beginning of the chapter even as we feel okay if you look at okay like a book okay so it's not like at the beginning of the chapter God is saying do this and at the end of the chapter God is saying no I changed my mind don't do it right so God's nature is holiness and righteousness so and whatever he's saying is consistent his word is consistent with his nature his will and everything so when we say progressive revelation it's it is something that is revealed to us progressively okay so it's nature is the same his holiness is the same the ways are the same and it is something that is progressively revealed to us so that is why we call it progressive revelation right so when we see okay all these you know the Old Testament sacrifices and everything it was pointing to the cross and like we don't know how many people actually got you know a proper revelation of that even as they were doing it but they knew that okay you know this is one thing that we do and then we know that blood sacrifice is going to whether it's symbolic or not but they did it sincerely because that God had laid down that and it was pointing to something but they said okay my sins are taken away when I do this okay but I knew I need to do it again right because it's for a season it's for a time and so yeah so we see that but then it was pointing through the cross and we know that after the cross there is no more need for the sacrifices right for those rituals because Christ is the fulfillment of the law right so so that is what we mean by progressive revelation and so Ravali had a question okay you know so in the Old Testament you know all the men of faith had multiple spouses multiple wives so you know how can how is that fair she didn't use the word how's that fair but he said you know how did why did God permit that and now we are saying you know there's only one one man so you know right from so the I was just reading through some so let me just share okay so so right from the beginning we see that God's plan is Adam and Eve it's not Adam Eve Sheila you know whatever it's Adam and Eve so God's plan for marriage is Manchal you know so Manchal leave is father and mother and leave to his wife okay so we see that pattern there right we see that principle and the plan God's plan right there so now one of the things that I just read through an article and I think that I saw was that see the Bible at places is descriptive okay what do we mean by that just describes the situation right it says okay this is what happened this person committed adultery this is what happened this is for this person killed and so it's a very direct it's at some place very very in the face right just says it active as it is and sometimes we are shocked sometimes we are even repulsed by some things that are written there it's like how can this happen it's a very direct book so it's a very descriptive book right and certain texts are descriptive so that does not mean that because a certain situation or a circumstance is described that does not mean that that is what is prescribed for our life prescription you know when it's something is prescribed it means you therefore you also do it right so it's not prescribed is not prescribing for us and saying okay this is what is described this is what happened this man you know did all this so does that mean you know I'm also a believer in God a worshiper of God so therefore I can also do it no right so you we go with the nature of God we go with the plan of God and then we go with the truth of God's word and then we obey that so so certain places it is descriptive certain places we know there is a there is a prescription we are prescribed we are instructed to carry out so that's that's one thing to take note of when it comes to you know this whole thing of polygamy right secondly there's no you know there's no command from God to take multiple wives you know there's no command I go through scripture it could have been a cultural practice it could have been practice you know for example in those times women did not have you know in terms of finances in terms of wealth etc. you know it was it was always controlled by the man right so they did not have access to it and if they lost a husband then you know they they lost everything right so so it could have been a cultural practice so as a safeguard for women whatever you know so it could be a cultural practice but we see that God did not command man to take on multiple you know women or multiple wives and so on and though and though we see that people did that we see Abraham did that if David did that Solomon did that by the way a note about Solomon how many wives and concubines 700 and 300 you know other women so it's like almost thousand but we see that how many children did he have I think there are two yeah so you know Solomon was I don't know you know like somebody said you know he was really searching for intimacy you know he wanted to belong he wanted to feel loved somebody said somebody's opinion I'm just saying okay so he had all these relationships he thought that would maybe probably satisfy but he actually if you look at it he had the two children right that's something to take note just an aside okay anyway so these are these are things you know like and also okay just coming to the end of this so when we see that then because of the outcome of these multiple you know like polygamist kind of a relationship that people that men had there's no positive outcome of it if you see you know there's no positive outcome in fact Nathan comes and says once David you know this is what you did murder adultery you took someone okay you took someone and then you married them and all that had this person but then this is God's word for you you know what you did was wrong so we see that even Rachel Leah and Jacobs marriage we read that you know it was as a result of you know laban stretchery but we also see that it led to a lot of strife between the sisters right one would one was barren the other one was and then they would always there was strife they would quarrel etc so the outcome of it was also not lessened in any way right so so we see all that and yeah and then we we can we can conclude that it's not you know it's it's it's not God's plan it's not God's purpose though and we see that God did not explicitly command and certain cultural practice practices continued and out of the revelation that people had they came to a place and say okay you know this is actually God's heart this is actually God's plan and this is God's and so when we come to the New Testament when we come to the epistles and all we see that all writing and you know instructing especially leaders in the church you know you be you know you be like this so so that's the thing so I hope that helps yeah okay we're just addressing one question here okay yeah so on an overall context like this particular polygamy might be one of the topic but there are a couple of topics in the Bible which which are revealed progressively when we coming to the New Testament yes right for example salvation for example sacrifices and you know all of that I mean prophecy everything it's been progressively revealed to us how it is today so when we say the Bible at places is descriptive but doesn't mean that it is what it is prescribing for us if somebody comes with a question saying that even though I question myself for example okay what is prescribed for me and what I should not be prescribed because always when we are looking at it we are looking at the New Testament as a reference to the Old Testament back because after Christ what is I mean whatever God Christ has given us is something that we are following it as a standard right now as a believers so before that there are a lot of practices which are which are not applicable for present age or not applicable for who who we are in Christ so what what do we say that is prescribed for us I mean just my understanding is it like what Jesus told us this is what it is like the new covenant that he made with us is prescribed for us and if we had to go back to the Old Testament not the new covenant the Old Covenants and the Old Testament what it is prescribing for us so also one one one good I hope everybody got that question right so one good rule of thumb is the fact that see the moral laws of God don't change okay so the heart of God the nature of God that it does not change so that's one big reference point for us his nature his holiness everything doesn't change his moral laws don't change well the ritual laws change for a reason because of the change of covenant and the ministry the work of the Holy Spirit again you know with the change in dispensation of covenant change right so so that's for us something for us to take note of and and go with that and we see explicit instructions in the life of Jesus in the teachings of the Lord and in the epistles right we see we see that so as New Testament believers right we can we can learn from that we can you know order our lives according to that but we also learn from the Old Testament saints we also learn from you know from it's there for a reason and we know that both old and new it's it's the Word of God so so we look at the old we look at it in the light of the cross no that's one very important thing okay this is leading up to the cross so I remember that even when I when we study the characters in the Bible we see that okay it's leading up to the cross some things the way they moved and the way you know the God dealt with them it would not directly apply to mean here and now because we have been dwelling presence of the Holy Spirit we have the revelation we have the you know we are in a different dispensation so we understand that and then we we apply accordingly right and the beautiful thing is we have the presence of the Holy Spirit in us we have the community of believers who also present have the presence of the Holy Spirit in dwelling right and the beautiful thing is that when it comes to you know a confirmation of word correction etc God does does that individually and in the context of community so that's the beautiful thing right where there is a there is a witness in our heart when somebody confirms what he's already put in us that's a beautiful thing that we have today as New Testament believers yeah okay any other questions before we move okay okay so online students anything that you want to add or ask if not we can move okay so let's let's look at the next one okay so we interpret scripture in harmony with other scripture I think that that's kind of self-explanatory in the sense that you know if you look at one part of scripture we said you know we looked at the context of the verse context of the text and that gives us a greater understanding why it is there so in seemingly you know certain places where it seems to contradict or you know seemingly contradict we know that well the heart of God we know that God is holy he never changes yesterday today and tomorrow you know forever he's the same and and so we we we compare with other scriptures you know in harmony with other scriptures so I don't just take the verse out of context or I don't take you know certain instruction but I compare it with other portions of scripture and see you know what does it what does it say okay so and and then interpret it right okay so the next one is interpret interpreting what is unclear okay in the light of what is clear okay so okay let's take for example you know this this example which is one Corinthians 15 29 okay I think are you studying Corinthians this semester next next okay but I think that's the third year fine yeah okay so so one Corinthians 15 29 it says Paul makes this statement okay all this question what will they do who are baptized for the dead you know in one 15 he's talking about resurrection from the dead he's talking about the reality that the fact that resurrection is a reality okay because there was some teaching going around that it won't happen and etc so he's actually teaching them you know if we don't if the dead do not rise our faith is in fact you know it's empty you know and so he's teaching that so then he he's referring to I mean he so this particular just consider this question and I says what will they do who are baptized for the dead if the dead do not rise at all why then are they baptized for the dead so he's referring to something that was happening there at that time so there were there was some baptism happening we know what baptism is for it's a proclamation of faith right of it's symbolic of what has already happened to us on the inside so here during false time in God and there was this practice of baptism happening for the sake of the dead okay so mr. X is already dead so here is mr. Y who's taking baptism for this sake of mr. X okay so some kind of you know so so then we look at this text and then we see okay so is that okay right it seems to be a little unclear especially in today's time it seems to be unclear you know why should this happen do you think that can happen so we know a whole lot of teaching came out of that saying that you can do something you can pray something you can do something here for the sake of people who are already dead and then this whole teaching of from you know let's say they did not accept the Lord or they lived a life that was questionable when they were on the earth and now that they are dead you know maybe they are in a place where it's neither heaven nor you know neither the presence of God nor is it really hell but they're in a place where a midsection where as based on what I do here on earth they could either be promoted or demoted you know in another words purgatory right so based on what we do it's something they get their advance to heaven or so the whole thing of salvation by works another version of it salvation for the dead by works etc so we know it is wrong so here Paul is actually talk referring to a particular practice which was there due to prevalent during the time he's not affirming that practice he's just making a point saying hey you know if you're saying resurrection is not there then why are you even you know I see these people doing this for the sake of the dead they're doing which means they have a some kind of belief that the dead will come back to life at some point right and for them for their benefit you know this kind of thing is happening right so what is he referring to is referring to people's belief that yes there is an afterlife and there is resurrection from the so that is what he is addressing here okay so so when we when we when we come across certain scriptures like that okay so we don't build a doctrine on that right we don't build doctrine on what is unclear okay so you know teachings about indulgences etc also came because of money like we see in Luke 16 9 where he says make friends for yourself by unrighteous mammon that when you fall they may receive you into an everlasting home and you know used by the church for the practice of indulgences you know what indulgences is right like the church use certain they had some kind of licenses you pay so much so that you can it is kind of the priest would give you a license or a permission to sin okay so so these kind of practices wrong practices came so if there's an unclear passage don't build a doctrine on it you know so look look at what is clear what is stated clearly and interpret this unclear based on what is very clear so if you look at one question 15 and verse 29 okay it seems like hey we can actually what is this baptism for the dead you know so instead of building a doctrine on yes we can do something for the dead look at what is clear what is stated what is stated is that yeah one dies one lives one dies and their destinies decided based on what they did when they were alive not when they are dead so he who believes in Jesus and converses and is born again and that is salvation so so in the based on based on that when we look at this scripture then we realize that okay he's actually referring to a wrong passage I mean wrong practice he's in fact not permitting that or he's not affirming that but he's actually talking about resurrection he's making a point there right and we study the context as well right okay then lastly we interpret sorry the last two things right interpret the spirit of the passage not necessarily the letter right so this is another error that we can make when we look at it when you look at scripture and we take it very literally when things are mentioned in a symbolic manner right so for example I mean this of course is very obvious Matthew chapter 7 and verse 5 the Lord says first remove the plank from your own eye then you will be able to see clearly to remove the speck from your brother's eye so it doesn't mean that there is a you know wooden frame which is in it just means that yeah even the speck is it's not something that is there in the physical eye you know is this referring to something that is hiding your vision something that is causing a distortion of the way you see things because of your own you know your own balls or your own sin or your own limitations so he's not saying you know first remove that then you will be able to see clearly okay so so we know that so I mean this is a very extreme thing there are other places also where when it when it says you know then the whole I forget the references but talks about multitudes and we know that or John says what does it say there's all the books in the Bible will not be able to contain right so he's using a hyperbole hyperbole or what they call it you know to to refer to the fact that there was so many like there was so many works there's so many miracles so many signs that the Lord Jesus did so he's it's like almost like what would you say an exaggeration but to make a point saying that they were actually many too many to be counted right so things like that so we need to interpret that way then lastly interpret with our dependence on the Holy Spirit okay so here again you know the Lord says when he the spirit of truth has come John 16 verse 13 he will guide you into all truth for he will not speak on his own authority but whatever he hears he will speak and he will tell you things to come okay so the Holy Spirit guides us into all that is the truth so so since he is the one who's guiding we also see that he teaches and he also reminds us of the words of Jesus so so yeah okay I'm just seeing a thing at a question by Jack in if you see the chat how do we correctly interpret cast your bread upon the waters and after many days it will bear fruit is it Ecclesiastus can somebody help with the reference we can look at that good I think it's an Ecclesiastus 1111 111 okay cost your bed upon the waters for you will find it after many years give a serving to seven and also date for you do not know what you will be on earth so it's the context it's it's referring to continuing to do the work continuing to be generous and the fact that it will bear fruit yeah so I know we don't use those I mean that's not our regular usage today cast your bread upon the waters but really the exact etymology of it you know what is that practice I'm not really sure Jack in let's say anyway does anyone know cast your bread upon the waters I'm throwing a chapati on the on the river on that yeah oh I see oh okay okay okay so I will yeah so here's a reference so he's saying in Nile in Egypt is it yeah okay so in the river that people will throw seeds but here is saying bread which is actually a finished product right not just the seed so anyway we'll come back to that Jack in so thanks for the question we'll look at that yeah maybe we can check that out and then we can you know we can discuss it the next class right Ecclesiastus 111 cast your bread upon the waters because it says for you will find it after many days okay do good okay so Prince is saying do good without expecting gratitude or reward it's from Google that's the meaning of Google okay yeah thanks Prince so we shall we shall get to the root of the matter okay okay okay so so we have all these you know reference so when we say you know interpret with dependence on the Holy Spirit so how do we do that so one good thing to say you know I depend on the Holy Spirit so how do we practically do it okay so seeking God prayerfully seeking him and being in that fellowship with the Holy Spirit but the whole process of receiving from him like how we've been learning about the gifts and all that so we know that you know that God is holy and his gifts are perfect his word is perfect but we as vessels we have our own biases we have our own prejudices plus our own life experience you know so we sometimes we can add that right so so how do we yeah interpret you know when we look at the whole picture of okay interpreting with dependence on the Holy Spirit okay I think what you what you said is very valid so what Arun saying is you know like his grandfather seek the Lord and say okay no education no background of you know theological education so completely depending on the Holy Spirit and saying God you teach I'm completely dependent on you so whatever download you get in your spirit from the Holy Spirit you know that's the thing and I know of a person I think I've shared also like this person is completely you know like see illiterate she does not know how to read okay so whatever scripture she quotes is what the Lord puts in her heart like huge chunks of scripture she'll court and then she'll also give references everything is like what the Lord has put in her heart that morning or you know the previous days so that's that's something you know like yeah very completely dependent completely leaning on the Holy Spirit okay so how do we how do it so like okay we see rather you know you're preparing something and how do you very helpful giving the mic there so how do you you know how to depend on the Holy Spirit okay let's say there's one passage okay let's say Ecclesiastes 11-1 okay past your bread upon the waters for you will not find it after many days give a serving to seven and also to eight for you do not know what evil will so now you depend on the Holy Spirit right so how do we practically do it what do you think and not just we rather but anyone anyone else also but first difference chance goes to see how you have shared anything what do you think if you were to interpret this yeah you can use the mic so others can hear I am carefully seeking the Lord do fasting nothing is coming yeah those are valid things you know really you know special disciplines of fasting prayer yes yes anyone else online you know folks also please you know part of it so so we know that the word and the spirit agree if there's always you know God's word God's will God's ways Spirit of God it's not going to be pulling in different directions so the Holy Spirit will lead us back to the word so we know that right so so even as we you know have this spiritual disciplines of fasting and prayer as a lifestyle and not just when we you know encounter challenges and we have it as a lifestyle then the Holy Spirit is we are going to get into the habit of the Holy Spirit community communicating to us directing us like we read just now I'm in the morning I will instruct I will teach I will guide so that's a reality present tense reality for us privilege for us so we get into that habit of fellow shipping communing with the Holy Spirit even as he leads us speaks to us right so we understand here is why so he's going to lead us back to scripture and as we make make it a lifestyle of studying scripture going through scripture one of the like the the ministry of the Holy Spirit is to teach us and to remind us so you know even as we read through he's going to give us that connection hey you remember what you read then is going to bring quick into us and say this is what it is you know this is going to be a step this is going to be a line upon line so we know that you know there's a revelation that comes right so we read the word and then there is and other things you know it's what can lead others to speak into our lives right so you are maybe you are listening to someone you know so that is why we are the body of Christ right and that's why we have the five-fold ministry that is why we have so even we are seeking and saying God I want to know the truth you know I'm really seeking I and then I have this hunger I have this desire God I want to know and you know Mark chapter four has a very interesting verse right after the parable of the sower so the Lord says you know according to the measure that you use it will be measured to you meaning that you go with a big measure measure is you know like the vessel you know you go with a you know you go with a cup this is all it's going to hold so it's going to give you that right and this is the level of my hunger capacity I'm saying I'm satisfied you know I'm just fill me with fill me I'm going to I'll use this but then you say I actually you know I I've grown I I don't need this but I have something more something bigger you know I'm just going with a bigger measure just fill this I want this so according to the measure that we use it will be measured to us talking about revelation talking about what he wants to give us so it depends on our capacity also you know to receive and yeah Jack and I see or come and praying fervently trusting etc right so so the so that's it so we know that it's a progressive thing it's a lifestyle of the Lord illuminating the truth for us so he will teach us through people he will teach us through his you know ministers and so on so there is a confirmation of it so we interpret when we say interpret about dependence of the Holy Spirit it's a it's a wholesome thing you know what the Holy Spirit does on this with us personally even as we read pray revelation that will that others will confirm but also it also means that you know him using the word him using you know others to speak into our lives or confirming what is already spoken to us yeah things like that but I don't remember you know it's early days of marriage and we were just I think a little before that is when there's whole teaching of spirit soul and body you know something new and everybody's teaching nowadays that's the first thing we start off you know when we learn about who we are in Christ and so on but then those days for me it was like wow you know why didn't anyone tell me you know that I've been struggling so so much in my thought realm imaginations and all that why didn't somebody tell me that hey I'm actually born again I knew on the inside but this is my problem right so so so that was something and then it was also a doubt right oh right okay I'm from this background I never heard it before what if it's something you know something heretic in all those doubts and we were in a meeting in the same you know church CSI church and here comes this person you know there's a special meeting and and so praying for different people and very unusually you know like you don't see many such people in that such a environment right in a very traditional conservative church environment so this ministering in the prophetic and ministering you know a word of knowledge you know that so he's come he comes and prays over us and saying you know the Lord is teaching you and whatever he's teaching you he's confirming you know some of these new things that he's putting his teaching you if the Lord says he will teach you and he will confirm those things immediately there was a witness in my heart and oh wow this is what you know the Lord is confirming the Lord is you know kind of reassuring that you're in the right direction you know go for it right so so that's you know something so the Lord can do that right when it comes to affirming reaffirming that you are on the right path and so on right okay so Nina has a comment here so seeds of goodness even when it doesn't make sense to do so only to reap a harvest at least as 11 was 1 to 6 but make it part of our life thank you Nina yeah yep okay one question yeah go ahead we could use the mic for example practically when you are when it's you need to preach and you need to prepare yourself for that were there any situations first thing is whether any situations where you haven't got that revelation or something that you're looking for it's like you know you heard it from God and you preach it it'll be a different impact or you know that you didn't get anything like that from God but you have to go there on the stage and you have to preach it like are there any scenarios like that so your question is okay does everything that you preach is it the revelation personal revelation that you are in other words or do you just preach it despite you know you're not having a personal something like that that in other words that's what you're asking okay okay so the thing is that you know there are certain things that you know you go with faith right in the sense Lord it's there in your word and and though God you know you know just your prayer is always my prayer is always Lord make it real to me in some way or the other make it real to me highlight it to me let that touch me first right so that is always my prayer so so the Lord does that sometimes it's even before sometimes it even as you're speaking it realize wow you know I'm just getting a new revelation it happens sometimes it's after so so not everything you know is something where God is you know connected and then made sense not everything is that way but then you go because it's there in the word you go that because it is it is something that he is I guess I example this some 32 was 8 was something that I read I know that it is the truth but then it just came alive when today's you know a whole incident and they just made the connection so I know it's becomes even more real to me like even though it was a practical incident that happened I know that every time there is a teaching and I think this is one of the things that comes up in my mind so yeah there are instances like that and also like the meaning of the whole thing you know they're not giving a deeper meaning etc that is always there in some places but you go with it because it is God's word yeah okay I think we'll stop here right thank you for being part of today's class we'll continue next class


What's good Josh boros back again with another video. So I'm going to check out 10 wrestling moments that have aged horribly in WWE. It should be very interesting to see what moments have aged poorly. There's a lot of things that when you go back and look at old WWE footage, you be like, ah, that wouldn't work in today's time at all. This age horribly. Actually, there's a lot of things. If you want to be honest, you go back and watch even in just the ruthless aggression they couldn't get said or shown on television. Now, times have changed. So we're going to check this out. Should be good. We appreciate all love and support. Let's get right into this one, man. Certain WWE moments have changed as the years have gone by. While some segments seemed humorous two decades ago. In the modern day, they are seen as exploitative and offensive. Yeah, there are also those segments which were controversial when they took place. But WWE were at a point where they're creative output where they didn't seem to care about the negative reaction outside of offensive segments. WWE have notoriously made some creative decisions that have aged terribly. Join us now as WrestleMania looks at 10 WWE moments that have aged horribly. Be sure to subscribe and hit that notification bell for daily wrestling videos and follow us on Facebook for exclusive layers. Also, check out our new channel, WrestleMania shorts. Number 10, Jared, the subway guy. The subway guy known as Jared Fogel had a number of appearances on WWE television. Most notably, he would guest star on an episode of Raw in 2012. No, I believe this would lead to mainstream exposure. Over a decade after his guest star stint, it's likely that WWE will never mention Fogel's name ever again. Nor should they 2015. It was uncovered that Fogel had committed some heinous acts and ultimately he was sentenced to 15 years and eight months in federal prison. If you don't know what they are, search the guy's name. Yeah, no, you don't. You don't even you two's we don't we don't even talk about it. You two don't even want nobody to talk about it. Yeah, just Google his name. It ain't going to be about subway sandwiches. I can tell you that. So, of course, they should never ever bring up his name. Jesus. WWE has smartly distanced themselves from Fogel and on the WWE Network, if his name is typed into the search bar, no results come up. Good. It seems fitting for a man as despicable as Fogel. Bats. Number nine, Vince McMahon's racist comment to Sabu. WWE's relationship with Islamic-centered countries is well documented. Yet if they saw one specific clip of Vince McMahon, they would have a ton of questions. During the revamped ECW in 2007, McMahon had a notorious backstage interaction with ECW icon Sabu. Following the interaction, fans were left gobsmacked. McMahon would address Sabu by saying, Well, I'll be damned. I thought I was in Texas. Hell, I'm not in Texas. I'm in Afghanistan. Hey, boys, check it out. Here's a member of the Taliban had there are no words to accurately describe what McMahon was thinking when he made these comments. He wasn't there was no excuse. Even in 2007 for a segment of this nature to air on WWE television. Number eight, it's just racism.  That's it's Vince. That's all I can say. There's really no explanation. No reason for it is just Vince. Not every WWE moment that is age horribly occurred decades ago. Nope. One infamous moment took place in 2017 and it saw Jinder Mahal taking part in one of the most controversial and tested segments in the modern era. In a segment on SmackDown, Mahal would mock Shin-Suke Nakamura's accent and he would even compare the decorated star to Mr. Miyagi. Fans were quite speechless that this was taking place in 2017. That's Vince for you. The backlash was so severe that WWE were forced to release an official statement. Just like many other TV shows or movies, WWE creates programming with fictional personalities that cover real world issues and sensitive subjects as a producer of such TV shows. WWE corporate is committed to embracing and celebrating individuals from all backgrounds as demonstrated by the diversity of our employees, performers and fans worldwide.  Someone came up with it.  But at the end of the day, it's Vince. Really wasn't a good look for WWE. Number seven, the 1999 Royal Rumble. A due to contemporary information about CTE, WWE have stopped chair shots to the head indefinitely. For sure. WWE are so strict on this policy that they're even reluctant to show archive footage featuring a spot and this has created problems when highlighting one of their most infamous matches of the attitude era. The 1999 Royal Rumble featured the Rock and Man colliding in an I quit match and the match featuring the unprotected chair shots, bro. Viewing. Now, this type of physicality would never be allowed. No, nor should it, bro. Without a doubt, the right policy. Oh, the match itself was documented on the beyond the documentary, which means footage of the chair shots often pop up when new fans watch the documentary for the first time and it always leads to some criticism being directed towards WWE. Yeah, bro. He was laying in them shots.  He's laying in and this nigga, he's handcuffed taking is different when you're taking a protected chair chair shot.  The hands take most of the blow. Between this unprotected. Oh my gosh. Six Kerwin White and there have been some characters and gimmicks in WWE that have age like milk. One of these gimmicks is the gimmick of Kerwin White. In 2005, WWE would rebrand Chavo Guerrero as Kerwin White. This gimmick saw Guerrero dye his hair blonde and denounce his Hispanic heritage. Most of the content of the character particularly during the promos crossed the line. Guerrero would often make questionable comments towards black members of the roster. The gimmick though was atrocious and it failed to get over as the fans had no interest in seeing the gimmick on TV. The gimmick almost went even further as Guerrero wore a white sheet to the ring and this was going to imply that Guerrero was a member of the Ku Klux Klan. Thankfully, this idea never materialized.  Oh boy. Couldn't just book a traditional good guy versus bad guy match when booking Booker T versus Triple H at WrestleMania 19. Instead of the traditional approach to the storytelling selling the world title matchup, they decided to create one of the most controversial storylines of all time as the storyline had racial undertones throughout which offended the fan base and made them completely disconnected from the product. In one particular promo during the build Triple H would declare I think you're a little bit confused about your role in life here.  People like you don't deserve it. That's reserved for people like me. That's where the confusion is.   That's what you do. You entertain people. How do you entertain me all the time? Go ahead. Do a little dance for me. Go ahead. Go give me one of those spinaroonies. Entertain me. That's your job. Don't be embarrassed.  The segments and promos during the build seem to get worse and worse as Triple H would treat Booker in a despicable way. They refused to change the direction of the storyline. The natural conclusion to the offensive storyline was Booker overcoming the game and defeating him on the grandest stage of WrestleMania. But WWE made the questionable decision to have Triple H win the match. Despite the match taking place at WrestleMania and featuring two certified legends, the match is rarely mentioned by WWE. They clearly want to try and act like the storyline never happened. And it's certainly a storyline that should have never, ever been pitched. Never mind being put on TV. Yep. I got to give Triple H some, some, some, uh, backlash on that one too. Because apparently he was the one that I think the day of he was the one decided that he should go over. That's the reports that he decided that he should go over the day of the show. Because it was going to be, uh, it was in the plans for Booker T to win it to overcome the odds and no, and not only that, he hit the pedigree and then had a slow crawl as he hit the pedigree and then covered him. Didn't even kick out. Still one of the biggest egregious, like egregious moments in WrestleMania history. So Triple H plays some parts in it. But at the end of the day, it's Vince for you. Number four, Vince McMahon uses the n-word. For some reason during the 2005 Survival Series event, Vince McMahon decided to book himself in a segment where he proudly used the n-word. In a backstage segment, McMahon would take part in the promo with John Cena. And to close the promo, McMahon would refer to Cena as the n-word. McMahon would then walk past Booker T and Chamele in one of the most tasteless segments WWE have ever delivered. According to Bruce Prichard on his podcast, the segment doesn't hold up, but in a bizarre fashion, he tries to justify the segment by saying it was a different time in a different place. Now come off. This is too- Of course he is.   I'm just like, what the fuck? No, it don't hold up. No. No. Just. Just no. Just. No. 2005 really wasn't a different time and place. No. Prichard said, I don't think it holds up well. Well, I think there were people whose opinions were asked and again, it's just a different time and a different place where you did different things that were not things that hold up. When I go back and I'm into the Alfred Hitchcock hour now, taping it every single night. You sit there and you watch some of those things on television of men just basically slapping their ish out of women back and forth as if it was just another day at the office. It's just time has a way of making things cringe worthy. Again, different time, different place, different mentality. No. The use of blackface. A WWE is a documented history of allowing talent to use blackface. The first notable instance of this occurred when Roddy Piper who wore half blackface for his feud with Bad News Brown. Fast forward to the attitude era, blackface would be incorporated into a segment once again when X Park impersonated Mark Henry. Yeah. It's insane that WWE believed that this was a smart idea. Now, it's worth noting that during an interview with Uprocks, X Park did admit how much he regretted doing it for the segment, which is more of an apology than WWE as an organization have ever offered over the years. Oh, for sure. It would also be used for Goldust during a match with Flash Funk. Goldust was going through an identity crisis, so they made the decision to paint his face to supposedly represent the inner conflict. Number two, the WrestleMania 20 main event. WrestleMania 20 was to be the biggest event ever. Yeah. Due to Chris Benoit's actions in 2007, the show is rarely mentioned. Nope. The main event of the show featured Benoit winning the world title in a triple threat match and then the show went off the air with Benoit celebrating with his family. Mm-hmm. WWE have tried to revise history when it comes to WrestleMania 20 and when the show is discussed in documentaries or publications of any kind, the Kane vs. Taker and John Cena vs. Big Show matches are usually the only two matches that are ever mentioned. Yeah. On the network, the Benoit match is still featured, but his celebration with his family has been completely removed. And instead, the show simply ends with Benoit celebrating with Eddie Guerrero before posing on the turnbuckle as the show fades out. And number one, Yeah, yeah, yeah. That's just all. That's a big touchy subject. It will always be a touchy subject. It's it's just tragic, man. Chris Benoit tribute show. Yeah, Benoit. When WWE found out that Benoit and his family had passed, they dedicated an episode of Raw with Benoit's memory. Raw was turned into a tribute show and it featured the band as well as top WWE talent pain tribute to Chris Benoit. The truth though would soon surface in relation to what Benoit had actually done and WWE were then forced to distance themselves completely. They just dedicated a tribute show to a man who committed the most unforgivable act and they were quick to erase the show from the history books. In countries where Raw aired on delay, a new show was sent to them which featured WWE highlights from the past calendar year. In relation to the WWE Network, the show has been replaced by a best of WWE compilation. There's obviously no mention of Benoit on the show in any capacity. Do they have it, folks? I mean, yeah, it's once again, very, very, very, very touchy subject. It's just you don't even want to mess with that. Anything that involves the Chris Benoit stuff, you just kind of put your hands up because it's just a touchy subject. It's very tragic on all fronts. So comment down below. Let me know some other moments that when you watch back from like the attitude era or the ruthless aggression era, you're like, this is not, this don't age well. If it wasn't on this video, there's a lot, y'all. There's a lot of clips that do not age well at all. Legitimately don't age well at all. So if they weren't listening to this video, let me know down below. But I appreciate all the love and support that you guys shown on Channel Road to MFDK. I'm still here and speaking to you at the Wrestling Champion of the World. Appreciate y'all kicking in with me. See y'all in the next one. Peace.


Hi everyone, this is Alice Gao. Welcome to another video on decision making under uncertainty. In this video, I will start talking about a new tool for solving this kind of decision problems. This tool is called the Markov Decision Process. In the previous few lectures, I focused on talking about decision problems with a finite number of stages. To model this kind of decision problem, it's sufficient to have a finite number of decision nodes and incorporate them into a decision network. However, in general, we may have to solve ongoing problems. For example, we can have a problem with an infinite time horizon. This means that the process may go on forever. After all, time does not stop for anyone, it goes on forever. Another kind of ongoing problem is one with an indefinite time horizon. In this case, the agent will eventually stop, but it does not know when it will stop. You can imagine a world with some gold states. If the agent reaches a gold state, it will stop. If it doesn't reach any gold state, it will continue exploring. So in this case, the agent does not know when it will reach a gold state and stop. For either type of ongoing problem, because we don't know how many time steps it is going to take for the agent to reach any end or whether there is an end at all, so we cannot use a decision network to model this kind of problem. Because of the difference between a finite stage problem and an ongoing problem, we will have to think about our utility function differently. In a decision network, we can make multiple decisions in sequence and then calculate our utility at the end. But in an ongoing problem, it does not make sense to consider the utility at the end. There might not be an end for an infinite horizon problem, or we don't know when we'll reach the end for an indefinite horizon problem. So instead, we will consider a sequence of reward, one for each time step. This kind of reward may incorporate several things. It could incorporate the cause of taking certain actions in some states. It could also incorporate any rewards and punishment we receive along the way, as we are going through the process and trying to solve the problem. Let's look at a graphical representation of a Markov decision process. Because there's an unlimited number of time steps, we cannot show the entire model. So this picture is only showing you the first few time steps of the model. So we are starting with the state S0, and in this state, we can take some action called A0, and this action may cause us to transition to a new state S1. And because of this action, because of the state transition, we are going to receive a reward R0. You can see that this is basically a decision network we're using the same notation, same kind of nodes. So we have the circles for representing the random variables. We have the rectangles for representing the decision nodes and the diamonds for representing the utility nodes. And also this process is going to keep going on, right? I'm only showing you the states up to S3, but you can imagine this keeps going. We will have new actions and new rewards for the future states as well. So in order to define a Markov decision process, we need to specify the following components. We need to specify a set of states. We need to specify a set of actions that are available in each state. We need to specify the transition probabilities. So given a state and given a particular action, we're taking that state. What's the probability that we're going to go into, what's the probability that the new state is a particular one? Similar to how we dealt with the hidden Markov model, we will again assume that the Markov process is stationary, which means the transition probabilities remain the same for each time step. Finally, we need to define a reward function. In the most general form of the model, the reward depends on the initial state we started in the action and the result, the state we ended up in after taking the action. So S, A and S prime, for some special cases, some of the parameters in the reward function might not be important. For example, we may have a model where it doesn't matter what the state S is, as long as we enter a particular state for S prime, the reward is the same. We'll see examples later on. Let me stop here for this video. In the next video, I will talk about how to model the reward function for a process that may keep going. After watching this video, you should be able to describe what are decision problems with an infinite time horizon and what are decision problems with an indefinite time horizon. Describe how we should model the agent utility in such ongoing decision problems. Describe components of a Markov decision process. Thank you very much for watching. I will see you in the next video. Bye for now.