Okay. Hi everyone. Great to be here. We're both very, very excited. First, maybe we want to thank you for attending DEF CON organizers for having us, accepting us to talk here. Friends on the first and not the first lines to support. And thanks for coming to our talk on Microsoft RPC. We'll start by introducing ourselves. My name is O'Fair. I lead one of the security teams in Akamai Technologies in Israel. This has been senior security researcher in my team. These are our Twitter handles. You're very welcome to follow for more material and the things that we do and see our work. Okay. Why choosing Microsoft RPC as a vulnerability research target? And first of all, what is MSRPC? So Microsoft remote procedure call. It's practically an inter process communication protocol. It can take place both locally on a machine between processes, but also between machines in the network. And Microsoft implementation was written somewhere around the 90s, which is quite a long time ago. And the most important reason why we chose to try to target MSRPC is because it's practically everywhere. This is a screenshot from a program called RPC View. It's on GitHub. There's a link to it if you want to try it yourself. And it shows basically all RPC activity on your machine, on the machine where it runs. And here we can see a list of many processes that use RPC in some way. Either they host an RPC server in the process or they are RPC clients. Many Windows services use RPC to perform and expose their functionality over the network to various clients. But again, this is on a single machine and what I think is very interesting is to see RPC activity in a network. And here's a screenshot of one of a random network, let's say, Windows network, where the edges represent RPC traffic. So this specifically is traffic filtered for TCP port 135, which we will get familiar with soon. But what I want you to take away from this is that networks, Windows networks heavily rely on Microsoft RPC implementation. Good. Yet it's everywhere and there's not a lot of public research on it, at least not that we're too familiar with. So when we try to kind of bootstrap our research and Google Microsoft RPC, most of the information we found boiled to Microsoft's own documentation, which can be quite dazzling sometimes, specifically with old protocols. There are several research-oriented blog posts that we will reference to later on at the end of the presentation. And with regards to public vulnerabilities, also we try to look for bugs that were disclosed to Microsoft. And there weren't a lot of them. Lately, there have been a couple of vulnerabilities in the RPC runtime. I don't know if some of you may have heard. But again, not too many of them, not compared to other products on Windows. Our assumption, again, is that it's not such a fancy research target because it's old. As you'll see, it's quite complex. It has a lot of mechanisms to enforce security, which are not always synced with each other and can be quite confusing. And we thought it was actually a good thing to try to deep dive into. And what we had in mind was specifically exploiting RPC or the services that use RPC to gain lateral movement within a network and gain this ability to hop from one machine to another, or exploit RPC bugs to elevate privileges on a machine. So as I mentioned before, many Windows services use it. They run with higher privileges. Maybe exploiting their RPC server would lead to having higher privileges ourselves. So with the motivation in mind, this is our agenda for today. I will do the part where we all learn about RPC together, and then we'll talk about RPC security mechanisms and demonstrate a bug that he found in a very common Windows service. This is not getting any less exciting. I'm still very excited. Okay. Thanks. Okay. So RPC overview and thank you again. By the end of my section, what I want you to have learned is all these terms, all this terminology that you see here. It might be a little bit confusing, but hopefully if I do my job well, you'll get it right. So I mentioned before RPC, inter process communication protocol. It's based on a client server model. So the client wishes to execute some functionality on a server, local server, remote server, you name it. In our case, the client wants to run a function called foo, which takes two parameters. In our case, five and hello. But how does the client know that foo even exists, that foo is implemented on this server? For this purpose, we have RPC interfaces that are written into plain text textual files called IDL files. Interface definition language. If we scan from top to bottom, we see that an IDL or a very basic IDL file has the unique identifier of the interface at the top, the interface name, which in our case is test, and then the function declarations, parameters, return values, basically their prototypes. Water, I think. One minute. So that's a textual file. Applications can't really use it, right? So they need code. For this reason, Microsoft developed their own IDL compiler called MIDL or middle. It takes an IDL file as input and then outputs source and header files that the client and server can use. So as you can see here, we have files for the server and the client and a header file that is used by both. The two applications can then include these files and make whatever use they want with the RPC functionality. So this is all like very conceptual contract, right? This is how the client knows what the server is capable of, but how does the client know who to reach out to? For this reason, Microsoft came up with the notion of endpoints that are basically the gateways to the RPC server implemented on the server. So endpoints can use various transports. There's a pretty long list of network transports that can be the basis for the traffic. Here we have a non-exhaustive list. So we see TCP and UDP, HTTP, named pipes that are based on SMB, et cetera. For each such transport, we have the protocol sequence, which is a string representing the transport. And the endpoint itself is basically the TCP port, the name of the pipe, the host name for HTTP transports, et cetera. What I'd like all of us to remember for the rest of this talk is that the interface and the endpoint are registered separately. They're not bound to each other. So if I want to implement an RPC server, I can declare a single interface and have various endpoints exposing it, but I can also have various endpoints and expose them over a single endpoint. Good. Some examples for endpoints that we see on regular Windows machines. I don't know if you can see this well, but we see TCP ports here, some named pipes that some of you may know, UUIDs for Hyper-V sockets that are users transport, ALPC ports, et cetera. So really there's everything there. Speaking of endpoints, I want to make a distinction between well-known and dynamic endpoints. Well-known endpoints, as you can guess, are known in advance. So they can be hard-coded in the client and server applications. The endpoint can be hard-coded in the IDL file itself, but eventually the client knows in advance exactly who to talk to. So in our example, the client knows that the server is on TCP port 39776. But this can lead to trouble because these endpoints can be exhausted or one server can override another server's endpoints. So Microsoft came up with dynamic endpoints that are dynamically resolved. For this purpose, we have a Windows service that is called the endpoint mapper or EP mapper. This is a service that the client can query for the server's endpoints. And actually the EP mapper itself has a well-known endpoint, which is TCP port 135. We saw that before, if you remember. So the client simply asks the endpoint mapper, please give me the endpoint for server whose interface UUID is yadda yadda yadda. And they get in return the TCP port or names pipe or whatever it is they need to actually use. So this is it. Now to some examples of Windows services and their endpoints and interface UUIDs. I took three hopefully famous Windows services here. At the top is the task scheduler service. We see that it implements three different RPC interfaces, each with its UUID. But there is no endpoint specified here, right? There's no endpoint mentioned. So it's a dynamically resolved server or endpoint, sorry. The service control manager SEM remote protocol has a UUID for an interface and a well-known named pipe that we see over there in the middle. And the encrypting file system, maybe some of you have heard it due to somewhat recently disclosed vulnerabilities. This one has actually two well-known endpoints, two named pipes and also two RPC interfaces. This is all in Microsoft's portal. It's documented in their technical documentation section. Okay, so dynamic resolution. Let's see what it looks like by observing network traffic. This is a screenshot from Wireshark, obviously. We start by querying the endpoint mapper. Obviously, we start with the TCP handshake over TCP port 1-3-5. We do this handshake and then we move on to sort of what I like to call the RPC handshake, which is also called the binding process. And once we're done with that, we can query the endpoint mapper for the service endpoint. In this case, we're asking for the task scheduler endpoint. And now that we have this information returned to us by the endpoint mapper, we can move on to talk directly to the task scheduler. TCP handshake, as we can expect, and then the binding process again. And then we have an established session with the task scheduler. I mentioned binding, so let's cover this one. Binding is basically the representation or logical representation of the client server session. Practically, it's a handle of a Windows object, and both client and server can set and manipulate data on this object. We will see later on that it is mostly used for authentication purposes. I think we sort of covered all terms at this point, so let's try to kind of wrap it up with the full communication flow. So the client, as we already know, it tries to call foo function. This function is, when it's compiled by the Microsoft compiler, it calls RPC runtime function called NDR client call. I didn't mention the RPC runtime, but that's a library called RPCrt4.dll. It implements both the client and the server side of RPC operations or functionality. On the client side, it does all sorts of things, marshalling the parameters, namely converting them into network representation, being responsible for connecting to the endpoint on the server and authenticating if necessary. On the server side, after the connection has been made, the RPC is, well, before that, it's responsible for listening on the endpoint, then doing the reverse operation of unmarshalling the parameters that were sent to or with the function, and perform access checks on the RPC interface. We'll get into that as well. Eventually, the RPC runtime calls foo, and foo is implemented on the server and being executed. How does the RPC runtime actually specify foo? Well, it doesn't have foo as a string. It rather has an ordinal number of foo. So we already know foo is declared in an IDL file. It's then compiled to a client stub, and this stub calls the RPC runtime, where one of the parameters specifies the ordinal number of the function in the interface file. So since foo is our first, the operation number or opnum is zero. If it were the second function, it would be a one there, and et cetera. So actually remember opnum because it's important for the rest of the talk. Okay, so I think now we're really done. We'll just have a quick recap. Things are not aligned as I was expecting them to be, but okay. So interface, it's the logical representation or conceptual agreement between the client and the server, specifies the functions, and represented by a unique identifier, a UUID. The transport is a communication medium. It's represented by a string called protocol sequence. The endpoint is the actual destination or gateway to connect to. It's represented by a port number, a pipe name, an ALPC port, et cetera. The binding is the session itself and represented by a binding handle. So I think we should all be somewhat RPC experts at this point, and I'll hand the ball to Ben to talk about RPC security and the bug. Thank you, Ophir. So I'm going to talk about MSRPC security, and I'm going to divide this part into two sub parts. The first one is MSRPC security mechanisms. And this sub part is also the basis for the second one, security related problems in MSRPC. So the first thing I want to begin with is that the security mechanisms are basically a complete mess. There are multiple security mechanisms, there are system-wide policies, flags, and various combinations of those. So basically, it's really for a developer to make a mistake while trying to secure the interface. In our talk, we tried to simplify this part, and we are going to mostly focus on remote communication. For each security mechanism, we are going to specify relevant flags. Those flags are set during the interface registration by the server side. And the first authentication, the first security mechanism that I would like to talk about is authentication. And even for authentication, we have two types of authentication. The first one is not really explicitly set by the server or the client. It happens as part of the network interaction. So for example, when we used an endpoint like HTTP, then HTTP uses IIS authentication. And the more commonly used is the name pipe endpoint. And the name pipe endpoint is carried over SMB protocol. And the SMB protocol has authentication as part of the protocol. And it basically requires us to have a valid user for the target machine. In a domain environment, this is not really a problem. We have our own domain user. And that's enough to pass this check against another machine in the same domain. But if we're in some random network, some public Wi-Fi, for example, then unless we have the credentials of a local account on that machine, we cannot pass this check. And in the past, they used to be the option to specify or use the null session access, which basically means providing no user at all. These days, it doesn't work anymore. But there is one caveat. And that's the DC, only for those specific name pipes. So those are configured in a system like policy. And basically what it means is that an unauthenticated client coming from outside the domain can connect to those specific name pipes on the DC, the domain controller. So is it the end of the world if we decide to use an unauthenticated transports like TCP or UDP? The answer is no, because there's another authentication and this is authenticated binding. So just a quick reminder, binding is the representation of a logical connection between a client and a server. So authenticated binding is a binding that has authentication info. And that happens when the server registers authentication info and the client sets authentication info. Why do we actually need this mechanism? Well, it gives us the option to have identity based access control and also various network protections. So we can have the RPC call encrypted or tamper proof against many of the middle attacks of spoofing. And the level of protection is specified by the authentication level. This is set by the client and later on the server can inquire what level was used. So how does this process look behind the scenes? Basically there's a bind-bind-acc package exchange. Those contain the authentication info section. And at the end of the day you have the security provider handle this data. So basically you have the NTLM security provider or the Kerberos one or Negotiate which chooses the best available option between NTLM and Kerberos. And as you can see here we have a snippet from Walshark and it has the authentication info section and we can see the NTLM security provider is used and also the authentication level is sixth, a packet privacy, the highest one. The end result of this process is a security context and the security context is somewhat similar to a normal binding. You can inquire information like what level was used, what security provider was used. Okay, so what's the catch with authenticated binding? If the server register authentication info, it doesn't mean that the client is going to authenticate. He's not in force to, he's not obligated to authenticate. So basically what that means is unauthenticated clients can still access the interface even if the server did register authentication info. And we can see this in this access metrics below. We have an unauthenticated client from the client side and authenticated binding from the server side. And the end result is still success. The client can access the interface. Obviously if we are a server developers and we register authentication info, that means that we want the client to authenticate. So what can we do? We can specify the following flag and the following flag basically tells the RPC runtime to make sure that the client uses an authentication level of at least one, which basically means that the client indeed authenticated. Okay, so let's move to another security mechanism. This is the security descriptor. And the security descriptor is a general windows security mechanism. The concept is that we can set a security descriptor on a windows object. And the security descriptor contains rules like this user can access the object, this user cannot access the object, this group can access the object, et cetera, et cetera. Later on when a client tries to access the object, then windows are going to compare his access token against the security descriptor. And in our case, the object is the endpoint and the interface. So it can set a security descriptor on both the endpoint and the interface or none of them. Cool. So this is an example of a real security descriptor. We can see the security descriptor string and we can convert it into something readable. This is from a service called app ID service. And yeah, so we're going to move to the last security mechanisms. And this is also the one that we believe to be the most interesting one. This is the security callback. And the security callback is basically function callback that is called every time the client tries to access a function on the server. And the logic of the security callback is up to the developer. They can write whatever they want there. But the purpose is to restrict access to specific functions or users or groups, et cetera, et cetera. So here we have the prototype of the callback. It basically receives the interface UUID and also the context which the server can inquire information about the call or the user or the connection. Now one small thing to note is if the server registers a security callback, then unauthenticated clients are going to be denied automatically. So this is another way to prevent unauthenticated clients from accessing the interface. Let's move to some examples to get us familiar with security callbacks. So here we have the task scheduler security callback. And we can notice that it checks the authentication level is at least back at privacy. The IS one also checks the protocol sequence that the client used. So here we have the IAS which checks if the client is a remote one. And if it is, then it needs to use at least back at privacy. Authentication level also checks the protocol sequence. Here we have the DHCP one which checks basically the protocol sequence. And finally we have ELSAS. And ELSAS does things a little bit differently. It makes a distinction, separation, distinction based upon the opnum that the client called. So if the client calls opnum zero, for example, then the transport that should have been used is TCP and opnum one, then it needs to be name pipe, et cetera, et cetera. Cool. So this flag relates to what I've said before about the automatic behavior of automatically denying access to unauthenticated clients. And basically these flags just disabled this behavior so it allows or gives the chance to unauthenticated clients to still access the interface if they pass the security call back. Okay, so we talked about some security mechanisms and we talked about some caveats of those. Let's talk about two design flaws that we found interesting. And the first one is actually somewhat described by Microsoft. Be wary of other RPC endpoints running in the same process. And basically what it means is let's imagine the phone scenario, we have a client in a server and Interface A registers is a local interface and Interface B is a remote one. So Interface A is supposed to be accessible only for local clients and therefore it holds local privileged operations. Interface B is for remote clients. So Interface A registers an ALPC endpoint which is only accessible locally. You can't use LPC over the network. It's an IPC protocol and Interface B registers a TCP endpoint which is a remote one socket. So the client can access Interface A, the local one using ALPC and it can also access Interface B, the remote one using TCP. But here's the actual catch. The client can access Interface B, the remote one using a LPC and more than that it can actually access the Interface A, the local one using TCP. And basically what that means is that a remote machine can access the local interface using TCP and therefore access a privileged operations. And there is another one problem here and that happens when Interface A registers a security descriptor on the endpoint. And the reason is because the client can just use the TCP endpoint and bypass this mechanism, the security check. So why does this happen? This happens, this relates to something that I said before, interfaces are not bound to endpoints. And basically we can have multiple endpoints and we can access each one of the interfaces using each one of the endpoints. But in what real life scenario we will not be aware of other endpoints running in the same process. So in Windows when you write a service then this service is going to be run inside the SVC host process. And that SVC host process might run other services as well. So you might share the same SVC host process with other RPC servers that did in fact register other endpoints. So what can we do to prevent this from happening? We can specify the following flag and the following flag basically tells the RPC runtime to make sure that the client that accesses the interface is a local one. So it doesn't matter what endpoint it's used, it must be a local client. And about the security descriptor problem, well Microsoft just recommends to not use it on the endpoint. Now let's move to another design flow that we found interesting. This is undocumented. This is the security callback caching and I'm going to explain it using the following diagram. So let's say we have a client and a server and the server exposes several functions, op num 0 and op num 1, et cetera, et cetera. And the client tries to call op num 0 and the security callback is called and it says op num 0. Okay, you can access this function. Now the client tries to call op num 1 and the security callback is called and it says op num 1. Yeah, not really. Access denied. So this is what you would expect to happen. But then security callback caching comes right in and changes what happens. So this is how it actually goes. The client calls op num 0, the security callback is called and it says, okay, yeah, you can access this function. And now the result is actually cached. So the next time the same client is going to call the same interface, then the cache is going to be used. So the client calls op num 1 and the RPC runtime says, okay, same client, same interface, you can access this function. And this is obviously not something that we want. This is a dangerous behavior. The client can now access op num 1, although it should not be possible, not supposed to be. So when does this actually happen? This is actually the default behavior for security callbacks. But there is one requirement. The whole caching mechanism depends or relies upon the context identifier of the security context. So the security context is the output of the authentication process. So basically if the binding is not authenticated, then there's no caching. And what can we do to prevent this from happening? By now you should have guessed. We can use one of the two following flags, the first one is somewhat documented. The other one is not documented. The first one basically disables the whole caching mechanism. And the other one changes the default behavior to be on a call basis instead of an interface basis. And that basically means that if the client calls op num 0, then cache entry is going to be created for op num 0. And if it's going to call op num 1, then it's not the same function. The security callback will be called and returns access denied. And if it does decide to call the same function again, then the cache entry will be used and it can access op num 0. Okay, so just a quick recap. We talked about a security mechanism, some caveats, some interesting design flaws. And in our research we found the security callback to be the most interesting place to look into an interesting attack surface. So we decided to look into multiple services and also their security callbacks. And by doing so we found a couple of vulnerabilities, but most of them are still under disclosure. There is one interesting vulnerability that we can talk about. And this is a bug in the server service. So I'm going to talk about the bug and the exploitation and also show a quick demo. So the server service, which is also known as Lannman server, is the service that is responsible for the management of shares, where shares are basically resources like folders or printers, for example, that are shared with other network machines. The service runs by default on all Windows machines and it is accessible through the name pipe SRV service. From now on I'm going to call it SRV service for privacy. It is just much easier. So let's take a look at the security callback of SRV service. And basically the logic of the security callback implemented by the server is to check that if the client tries to access the range of opnums between 64 to 69, then deny access if he is a remote client. So those functions are only available to local clients. And when we saw this code, we kind of theorized that maybe in other RPC services that implement similar logic or maybe in newer versions of this service, they might screw up and there will be availability. So we decided to be on the lookout and look for newer versions. And when we looked into SRV service security callback in Windows 10 20 H2, we noticed that four new functions were added, but the range also changed to include them. So there is no vulnerability here. The code is still okay. And at this point we thought, okay, well maybe they have a macro to somehow automatically calculate this range and it wouldn't have any vulnerability. But we didn't give up and we decided to look into Windows 11 security callback. And in Windows 11 we noticed that a new function was added and the security callback didn't change. The range did not change at all. And the function is a local one. It's local R server certificate mapping modified. This is obviously a local one. And the range does not include this function now. So that means that a remote machine can now access this function. And this is obviously a vulnerability which received the foreign CVE with CVSS score 8.8. So before I talk about what we can do with this function and the exploitation, let's talk about what it relates to. And this relates to a feature called, feature called SMB over Quick where SMB is the SMB protocol. And Quick is somewhat new transport layer protocol designed by Google not that long ago with the purpose of being secure and privacy in mind and also low latency. And as part of the network interaction in Quick, the server provides a certificate and that allows the client to verify the identity of the server. Basically that prevents spoofing attacks or many in the middle attacks. And those new functions that were added, they basically manage the symbolic link between a Quick certificate to a real certificate in the Windows certificate store. So certificate mapping is basically a symbolic link. Okay, so as you can understand, we can modify and existing certificate mapping and therefore do some tampering, many in the middle attacks maybe. But we ask ourselves, can we do more than that? And when we looked into the structure that the function receives, this is after some reversing, we notice the store location variable. And this variable is basically the path of the Windows certificate store. And we thought, okay, well, what would happen if we provide the UNC path? And the UNC path is basically the path of another network machine. And by doing so, we managed to cause the RPC server call, send an RPC request to a machine that we can control. And why is this interesting? That's interesting because as part of this interaction, the RPC server presents his authentication info. And we can now take this authentication info and relate onto another network machine, basically impersonating the RPC server and saying hi, I'm that RPC server. Here's my authentication info. Let me access your service. So for those of you who are familiar with Petit Potam or DFS Coers or Shadow Coers, this is the same exact scenario. We have an authentication, Coers and vulnerability. And in order to exploit this, I base the exploitation on a research by Specter Ops, guys where they found out that you can relay the authentication info of the DC, the domain controller to ADCS, the Active Directory Certificate Service. And by doing so, you can receive a certificate of the DC machine. And I'm going to work through the exploitation, although this is not the main part of the talk. So we begin by using the vulnerability we found, the authentication Coersion. And as a result, we get the credentials of the DC. Once we have the credentials of the DC, we can relay it onto the ADCS and we get a certificate from the ADCS. Using this certificate, we can now request the Kerberos TGT. And with the Kerberos TGT, we can now perform DC sync attack, which basically allows us to retrieve NTLA mashes of local accounts. And finally, once we have the NTLA mash of an account, we can use past the hash attack and get a shell. So I'm going to show a quick demo of this. One second. About it. One second. We do have it on here. So maybe wait one second. Do we have speaker ops here somewhere? Speaker goon, somebody? We have a demo. We want to show it. From this laptop. It's here. Saturday. Yeah, you're up. Okay. Yeah. Does it play? No, it's not. It's not showing. We see it. You want to come here? Watch it with us. How? She has a video. Yeah, yeah, yeah, but you got an extended view. So only you're going to look at it. But what we can do is I can go to logo. You can put it on mirror and then point at me and I'll bring it back up and then we can't we just flip the mirror. I thought I said it would have been better to go to logos. How are you doing all? Please be patient. Just one more minute. We really want to show it. Right. So, okay, so we have here the DC machine. This is the machine that we are going to attack. And here we have the relay machine. This is a Linux machine, which is going to relay the credentials of the DC to the ADCS. And here we have the attacker machine. This is the one that is going to trigger the vulnerability that we found. And we are going to initiate the request. And as you can see, we receive the certificate of the DC. That means that the attack worked. And now we're going to use the full exploitation. We are going to use a tool called Ruberos and use the certificate to request a Kerberos TGT. Now we are going to just make sure that the Kerberos TGT was imported into the K-list, the local Kerberos TGT list. And now we are going to use the tool Mimicats to perform DC sync attack. And now we are going to actually retrieve the NTLM hash. And with the NTLM hash, we can now perform past the hash attack using WMI exec to basically get a shell on the DC machine. So we are running inside the DC to presentation. Okay, so to summarize, we found the security callback to be an interesting attack surface, specifically those who deal with opnams, also because of caching. We encourage other researchers to look into other services, also SMB over quick. We also believe the RPC are trying to be on the research target. The blog post and POC will be shortly available in Akamai's blog post. Also stay tuned because we have other vulnerabilities that are still under disclosure. So once they are fixed, we will share the details. And finally, those are some references to some great blog posts by other authors. This is also the opportunity to thank them for those. And that's it. If you have any questions, then feel free to approach us so you can also send us a message in Twitter.


The paper discusses the potential of data assimilation, DA, in improving hydrologic predictions, but notes that advances in research have not been adequately implemented in operational forecast systems. This is due to challenges such as quantifying uncertainty and efficiently merging data and models. A hydrologic DA workshop was held in Delft, the Netherlands, which led to a review of current status and potential hurdles in transitioning DA research into cost-effective operational tools. The paper discusses several related aspects, including theoretical aspects in DA algorithms, uncertainty estimation, new observations, real-time control of water resources systems, and community-based generic DA tools. It is recommended that cost-effective transition from research to operation should be facilitated by developing community-based modeling in DA tools and fostering collaborative efforts among hydrologic modelers, DA developers, and operational forecasters. This article was authored by YLU, A.H. Wirts, M. Clark, and others. We are article.tv, links in the description below.


This study investigated the effects of thermal cycling on two types of high-performance polymers used in CAD slash CAM milled frameworks for definitive restorations. The results showed that both materials met or exceeded the ISO standards for dental resins in terms of flexural strength. However, the flexural strength of the glass fiber reinforced composite, FRC, material decreased significantly after being exposed to thermal cycling. Therefore, it is recommended that these materials be used only for short-term applications such as single crowns and bridges. This article was authored by Hanine E.S. Lam.


What's good, Josh. You were lost back again with another video. So we're gonna check out 10 WWE wrestling titles that never saw the light of day This should be a good word. I'm interested to see what titles they are talking about I will say this the older WWE titles I was just a bigger fan of like growing up in an attitude era Like I just love the titles that they had back then they just seen more like Wrestling championships even though now they're the kind of bland. I don't have a lot of like I don't know it doesn't give me championship vibes at least some of them not all of them some of them look fantastic I will still say this the UK Championships in my opinion look the best on WWE like in my opinion They look the best and I've seen that NXT has revamped their championships to and they look even better You know in my personal opinion. I like the way they look, but this is some of the main roster ones. They just they're so So, but we're gonna get into this appreciate all love and support. Let's check this video history There are a bit of number of iconic and notable WWE title designs from the classic wing Love that belt to the big gold design that was used between 2002 to 2014 as a world heavyweight title that one too There were also a number of WWE title designs that were made by WWE But they were never used on television This either comes down to Vince McMahon not being a fan of the specific design or internal factors influenced WWE being able to present the new title on programming for which we're members at members that title I think when that the The greatest royal rumble title whoever won it baby I think bronze rum and won the greatest royal rumble. I think that's what that title is even though it does look cool I'm not gonna lie to you. I it actually looks better in my opinion than just the main WWE Championship even on main WWE Championship. It's okay. It's serviceable I just like different designs on the plates instead of just a big W You know and I like to like that one if you change the strap to black that one will be super solid One's worthy. We'll join us now as WrestleMania looks at 10 WWE titles that never saw the light of day Be sure to subscribe and hit that notification bell for daily wrestling videos and follow us on Facebook for exclusive list Number 10 the Brahma bow belt when Stone Cold Steve Austin introduced the smoking skull belt onto screens in 98 It changed the perception of custom WWE title designs That was a legendary man had reservations at first in relation to allowing Austin to use the title on Raw But eventually he came around to it and the design became insanely popular Yes, it is a replica version of the title sold Insanely well and still remains a top seller on WWE shop to this very day Following that the smoking skull belt WWE wanted to introduce the Brahma bull belt for the rock In fact, this was made and ready to be used on television by the great one But that was until it was lost in the mail Wow 2021 interview on entertainment tonight Stephanie McMahon revealed. That's what's interesting about this is actually never seen the light of day It's never been on television. This is really a premium one of a kind artifact And it was created during the rock and Steve Austin storyline Wow Lost in the mail believe it or not during those two weeks that it was lost The decision was made to scrap the whole thing and the rock never got his own customized championship I didn't I know that wow the design never appeared on television WWE did decide to make toy belts out of the design and these were sold around the world Interestingly, they did a similar thing for a custom undertake a WWE title But this one was made exclusively for the toy market rather than one that was intended to be used on screen Number nine revamped versions and I know that wcw titles just before WWE purchased wcw There were plans in place for them to redesign every single one of their titles That is with the exception of the beloved of big Goldie Yeah, this redesign would see all titles look very similar and the wcw U.s. And television title would feature the wcw logo in the center this way of designing belts was way ahead of its time That's one of the criticisms that WWE face currently is that most of their belts look the same and only I just said this This is the problem. They just look too much like the same. There's no doesn't the belts don't have any flair to them You know, I that's why I loved the NXT UK championships. They look fantastic love those belts Focus on the logo if these were completed just in time for the wcw purchase They would have been used on television and Vince McMahon more than likely would have loved the designs Number eight alternative version of the ic title They have been a number of versions of the ic love that version of that I love that version of the ic title and one that Cody Rose had brought out Brought back a few years ago with the white strap love that dude I I despise the new ic bill. It just looks it just you wouldn't think it's the ic Championship bill you would not think it is Does what does that belt represent looks this shit just looks weird A number of years ago an alternative version of the intercontinental title was leaked online There was some debate as to whether WWE wanted to use this design Some fans believed that this was going to be used during the attitude era when WWE scrapped the classic design in favor of the oval design That was used until 2011 However, the title has the scratch WWE logo on suggesting that they were gonna introduce the design in 2003 following the no mercy pay-per-view in 2002 the ic title had been unified with the world title But at the 2003 judgment day pay-per-view WWE smartly brought the belt back Now there were rumors at the time that they were gonna debut a new design for the belt and this leaked design more than likely would have been it Number seven like the league is on wwe title. I do during Hulk Hogan's historic four-year renaissance champion Four years is champ will Will Roman get to that who knows Title designs, but there was one design that was made for Hogan that was used one time and one time only This was a custom version of the title designed specifically for him And there's only one single image of Hogan actually wearing the title The title looks similar to a title that would be presented in the NWA and features an image of Hogan in the center It's a bold design, but it doesn't really look too great and wwe made the right move Utilizing it at all Custom John Cena wwe title a John Cena synonymous with the spinner version of the title that he introduced in 2005 However before wwe and Cena settled on that gonna lie to you when that first came out When what he did to the United States? I know a lot of people didn't like it But I'm not gonna lie to you I liked it because it was the it fit the time period Everybody remember like spinning rims like if you don't know what that is the car stop your rims keep spinning That was a big thing around that time period so to see Like those those custom belts being made like the United States spinner belt and then the wwe spinner belt I thought it was cool. I thought it was something different They kind of got with the times and they kept with it for a minute On the spinner belt, they actually designed another belt that was never used this belt featured the wwe logo restrained by For the design looks kind of cool and certainly would have suited Cena's first incarnation of his doctor of thug-a-domics Yeah, I see it's likely that wwe didn't use this design as they wanted it to spin as Cena's custom u.s Title had sold extremely. Well, see I'm telling you around that time. That was something you didn't see on the belt So it was selling like crazy, and you know this is all about that bottom dollar them boats were selling like crazy to spinner belts definitely I know some people don't like it think it's a toy and I think it outstated to welcome a little bit too long But at the same time those belts were iconic. They just work because of John Cena And it made perfect business sense to use a similar design for the wwe title Number five the king of the ring title There have been rumors surrounding the king of the ring title for years with fans asking why wwe would make a title for a Tournament winner and why they decided to make a title exclusively for Mabel. Well, it turns out they didn't back in 1995 Mabel shockingly won the king of the ring tournament and following this victory He took it upon himself to get his own custom-made king of the ring title This actually was an approved by wwe and they consequently never used it Once Mabel was fired from the company He began to use the title during independent shows as an extra incentive to attract bookings The Eagle belt returns but when the Rock defeated CM Punk for the wwe title at the Royal Rumble in 2013 they wanted to give the Rock a brand-new version of the title the design process for this was long and hard and Wwe came up with a number of designs Some of them were downright awful, but there were ones which look truly awesome That would have been cool Maybe the winged eagle and it would feature the eagle with its claws instead of the wwe logo So then look like bird wings and it really looked different Could have possibly worked. I like the new version of the winged eagle belt. I'm not okay with that Nevertheless wwe turned down this idea and instead introduced the new version of the wwe now that version of the belt Is the best version of the just traditional wwe logo on the front That's in my opinion is the best-looking version because of all the diamonds and all the stuff It just it looked good. It's just now they kind of blend I like that version of it the gold all around it. I love that version of it Wwe title that was used up until 2014 Number three the giant version of the classic wwe title a WrestleMania 3 featured one of the biggest matches of all time as Hulk Hogan collided with Andre the giant for the WWE title ahead of the match taking place They would create a brand new version of the title. Well, it was the same design just a completely different size WWE believed that if Andre won the match the current title would be far too small So they naturally made another version which was appropriately sized for Andre The belt could be seen on the 16th March She was huge wrestling and it looked rather impressive But sadly Andre would never get to hold that version of the WWE's top prize Number two the Vegas big gold belt a nature boy Rick Flair joining wwe in 1991 was a huge deal It was made even bigger by the fact that he brought the NWA title with him Yep, this was a rather unique storyline for wwe. I'm gonna lie to you. I love that that title, bro Big Goldie. That's what we people call. I love that title. It's just just that. Oh, man. Love it. Love it so much Flair would claim that he was the real world champion whilst he was presented on all wwe programming with the big gold belt around his waist But wwe and flair encountered a major problem when WCW planned to sue flair for using the title on television And wwe decided to take a step back from the storyline to avoid any legal penalty surfacing But Vince McMahon wasn't just gonna give up however He smartly began to pixelate the title on television Wow They even began to use a tweak design of the tank titles which are supposed to act as the NWA title What it's also ordered a new belt to be made that was titled the Vegas big gold belt It featured the nameplate removed and subtle changes being made so it wasn't an exact replica It was believed that the final design looked far too similar to the big gold title and the design was ultimately scrapped And number one the raided off belt Wwe wanted to take the few between Edge and John Cena one step further in 2006 Which they did wwe wanted edge to introduce his own custom wwe title and put an end to Cena's spinner belt Edge was excited by this prospect and he even got to work making his own mock-up of what he believed the design should look like Edge eventually presented these ideas to Vince McMahon and creative and it's safe to say they hated the design Yeah, no fairness to Vince and wwe didn't look great. Yeah, look like a real wwe title design Yeah, wwe instead decided to change the center and side plates of the spinner belt for ours Representing the rated R superstar. Although this was seen as lazy by some it was a smart move and wwe could have easily Transitioned back to Cena's version of the title once Edge had lost the belt I mean that's kind of where they were taking it direction like I didn't I had no problem with his rated R Granted his design definitely Did I look good? But I I actually enjoyed them changing it to the rated R superstar. It really let you it made you believe Okay, we're in a new era now edge is that mother you know what and he is taking over So but I guess at the beginning of this video man. I just the older belts I definitely preferred and like an attitude era was not rootless aggression era and It's just the newer belts on the main roster. It's they're not that inspiring I'm not even allowed to use some of them are some of them are cool. Some of them do their job. You know, they're serviceable, but I Just feel like they should be they should be you know saying when you have these belts people's like damn I want that, you know, I don't feel like that I feel like more people want the old school belts and some of the other belts rather than what we have on the main roster But comment down below. Let me know. What is your favorite WWE? wrestling belt man, let me know or I'm even make this even like a broader selection. What's your favorite wrestling belt not just WWE? What's your favorite wrestling belt? I will say this AEW they have the better-looking belts I'm so glad still that the women's belt look better and the men's championship belt The men's AEW championship belt is gorgeous AEW they killing it on the belt designs. So let me know what's your favorite wrestling belt in any company Let me know down below, but I appreciate all of them sport roll to ADK appreciate y'all kicking me. See y'all next one. Peace


We will travel together from ST and partner locations where the STM32 innovation is emerging. Fasten your seatbelt. You have been an incredible community to guide us on what you need and where we should innovate to help you. Some of you have been with us from the very first day and many are continuously joining us. We are proud that the STM32 is inside the many applications you are creating and which are making the world better with, for instance, giving more care to people or reduced power consumption. How could we believe only one year ago that our world would have changed so fast and that development of an embedded system would happen this way? Electronic and semiconductor, among others, are two segments of the economy which persisted in their manufacturing during this crisis to support new development like in medical and as well to sustain the economy and its changes. We have been facing a surge of demand and we understand that the STM32 delivery are critical for many companies, whatever their size. Our team have been working tireless in 2020 in the middle of the pandemic so that we can deliver more STM32 than ever before and this despite some critical situation with our partner supplier. We hope that at the end of this tour you will have the information on technology trends and how the STM32 can help reduce time to design, connect your application, increase software quality and help to lower consumption so that you can make wise decisions during your next selection. Our strategy is the same. In ST, around the STM32, we believe we are here to give you the product, the tools, the support to entrepreneurs like you so that you have time to focus on your creativity on your added value. To achieve this vision, we want to give you the flexibility, the innovation and the performance in the product portfolio and associate it with the best ecosystem on the market. The four main axes of our STM32 development strategy are more wireless product and ecosystem, more advanced security, software and hardware implementations, more support of artificial intelligence and more MIPS for lower microns per megahertz. We believe that this is answering what you have been requesting to us and as well what the world needs. Billions of STM32 are delivered every year. And as for the supply chain toward our customer, we feel the responsibility of delivering the best with the minimum environmental impact. Sustainability is part of STDNA and values on business model. ST has been actively working on reducing its environmental footprint through the dedicated programs for the last 25 years. In 2019, it had already achieved the goal it had set for 2025 regarding greenhouse gas emission reduction with a 21% reduction per unit on production compared with 2016. ST is stepping in its ambition and plan for the sustainability of its operations. We will become carbon neutral by 2027. STM32 is at the center of this plan and help in addition through all the applications which you do to make the world better.


Still the 20th day of October still on why in the morning still the hardest breath for show around My name is still Valentine or at color me that on everything and you can find us at white 5 on Facebook Why 2 5 4 channel on Twitter hashtag is when the money is a good Monday. There's nothing blue about this Monday's book What do we do about the color was it but that should be the only blue thing I'm not getting my friend We are entering like this the health segment and we want to talk to you about things that are important to you Yes, I think it's important to turn to a youth channel You expect to see something that will benefit and we strive to do just that so lunch Don't get left fibroids and we're going to try and keep it along the age bracket of the youth so 19 up So again, you know what red finders the thing is over there or you could use our text sign to zero 1 5 4 start with Why 2 5 4 that is 2 0 1 5 4 start with why 2 5 4 and help me give a warm Welcome to my guest. Good morning. Morning. How are you? You look fantastic? Thank you. What's your name? My name is dr. Christina. I'm an obstetrician and gynaecologist. Okay. That's not a hot job Was it a pretty girl? It is a hot job. Yeah, you'll manage it. Well, I can see so talk to us about five points What are five points? so fibroids are basically Non-cancerous groups that happen inside the uterus they're not cancerous, but they do cause a bit of Anxiety a bit of distress to the patient who actually has them and they grow mostly inside the muscle of the uterus Mm-hmm. I have two stories to tell you first I hope she doesn't mind me sharing but my mom had fibroids at one point and her fibroids I don't know if it was the size I'm aware they were I'm something but they kind of made her look like she was expecting So some people got confused for a while and then I follow up with the question How is the baby really sad and no there was no baby because and then there's also on this person this Public figure I follow on Instagram. Her name is Ori. She's a model and she also got fibroids now When my mom got it in my head it was an age thing like one of Katomali as a woman you just Develop things but for her it hit hit me a bit close to home because she did not it was and she was trying to lose weight But it was not going away and she was really bummed out So I'm but I kind of hosting duck as a tour. So tell me is it an age thing? Is it a lifestyle kind of situation if I eat this I'll get fibroids if I don't what's happening here? So basically, okay specifically the case of your mom What happens is that fibroids especially when there's many of them they cause the uterus to enlarge and to become really big And so, you know pregnancy also causes the uterus to enlarge and become really big and that's why sometimes people can confuse it for pregnancy But yes abdominal distension is one of the symptoms of very large fibroids Unfortunately unless the fibroids are removed. There's nothing much that you can do about that kind of distention But it's not an age issue. Actually what causes fibroids is not really known However, it has been said that African women tend to develop fibroids more than Caucasian women and African women tend to develop fibroids younger and their fibroids grow faster than that of Caucasian women Ideally the bracket is 30 to 40 But we're seeing fibroids in much younger and younger and younger ladies Then then was previously detected. What's happening? Why the change? So as I said before the cause is not known However, some people have stipulated that obesity is one of the causes of fibroids Some people have said that alcohol consumption is one of the one of the causes Another cause is actually not having had children before Although that doesn't mean that if you've had children that you cannot have fibroids you can still have fibroids So yes, of course, there are very many things that are kind of related to that But yes women who are more obese and women who consume alcohol and women also who start their periods much earlier than the rest Are more predisposed to getting fibroids than the rest There is also a hereditary aspect to it meaning that if your mother or sister or aunt had fibroids You're likely to get fibroids as well. Unfortunately. But yes, there is a hereditary aspect to it Oh, wow, that's I did not know that there's a little bit scary. Is it something you can prevent? Unfortunately, no, it's not something you can prevent. However, you can prevent things like obesity and alcohol consumption But there are the factors like the hereditary factors or you know not having a child is sometimes not very much within your control But yes diet alcohol obesity that is within your control, but Preventing obesity and reducing alcohol consumption or stopping alcohol consumption is one of the things that helps more less any disease It's not limited to fibroids alone, which is true But we are in Kenya and for me party after party That's true. So I don't know what we're going to guys. I think it would be to make cash, too Yeah, so how do I know that it's Let's say I'm a random person in the audience. How do I know if I have a fibroid? What are the symptoms like? What's how do I expect? How do I? Read my own body Okay, so fibroids do come with a number of symptoms. One of them is changes in your menstrual pattern So one of the things you might have is heavy bleeding. Sometimes you can have bleeding in between your menstrual periods You might have a bit of pain or a considerable amount of pain during your periods Although there are other conditions that do cause menstrual pain as well Okay, aside from conditions and but this what happens if there's normal, you know men's menstrual pain How do you now tell the difference? Ideally you should not have too much menstrual pain It should be something that's variable something that you don't necessarily have to take medication for So if you have to take medication for your menstrual pain or if it's very severe if you're Unable to go to school or unable to go to work then that is considered as you know considerable menstrual pain And that could be because of other reasons, but one of the reasons is actually you train fibroids Wow, so your menstrual pattern can change you might have heavy periods Or you might have lower back pain or lower abdominal pain and then in other women they have symptoms such as Infertility, they're not able to get a baby. Oh, one of the reasons is because of fibroids I'm hoping like it's there's a situation where if you take them out then fertility goes away Yes, there is such a situation Not for everyone, but yes, there is such a station where the fibroids are taken out and the fertility actually returns But that depends on where the fibroids are placed because there are different places where the fibroids can be that affect Fertility and then there are other places where the fibroids are that don't affect fertility Those other places could affect bleeding or could affect other symptoms such as urination or passing of stool Where those places like where where can they attach themselves? It's a little freaky. Okay So the fibroid itself is inside the uterus It could be in the muscle of the uterus, which is kind of just within the uterus or it could Protude into the cavity of the uterus or it could be attached to the outer part of the uterus So when there are many fibroids within the muscle of the uterus It makes the uterus very heavy and the uterus tends to lie on sometimes on some of the organ Sometimes it can lie on the bladder. Sometimes it can move backwards and lie on the rectum Sometimes it can lie on one of the ureters and you know the ureters conduct urine from the kidney to the bladder So when it lies on one of the uterus it one of the ureters, it causes an obstruction in that place sometimes if it moves backwards it can cause an obstruction or a bit of difficulty in passage of stool because it's lying on the rectum Sometimes it can lie on the bladder and you have patients who have difficulty in passing urine But sometimes you can have a fibroid that's just literally attached to the outer surface of the uterus Yes, it can still cause these pressure symptoms that we call but sometimes it can actually twist upon itself So abdominal pain is one of the symptoms of uterine fibroids Because it's like on a little stem Attached to the uterus so that stem can actually twist But the ones that actually cause the most symptoms are the ones that Procured into the cavity of the uterus. Those ones cause difficulty in conception because the Developing baby literally has no place to implant and at the same time they cause issues with bleeding because they infringe upon the lining of the uterus Which is called endometrium, which is what gets secreted every month as your period Okay, at least that much I meant by biology It's quite a shade, shade upon any, I love it just crumbles, crumbles on the wall when it's time for a fee Thank you my biology teacher for your contribution to society Although I am hearing it it might you can actually Confuse it for pregnancy You can't confuse it for pregnancy because it causes abdominal distention, it causes abnormal bleeding, back pain Yes, early in pregnancy you do get such symptoms, but the symptoms are actually very distinct You get heavy menstrual periods, you get bleeding in between periods, you get back pain You get difficulty in urination, difficulty in passing stool, infatility And some women even tend to get recurrent miscarriages Because if the fibroid is seated inside the uterus Then you can imagine that implantation cannot occur, but when implantation does occur the fibroid has occupied a certain amount of space And so it kind of just pushes the pregnancy out Walk that's being territorial in all the wrong ways Okay, so assuming I am patient and then I've just found out okay have fibroids What am I expecting as on my root recovery? How are we going to deal with this now? Okay, so fibroids can sometimes be an incidental finding You might just go in for an ultrasound for something completely different Maybe you just got pregnant or maybe you've had other issues And then now you go in and do an ultrasound and they find fibroids So ideally if your fibroids are not causing you symptoms that is if you're not getting any pain You're not getting any abnormal menstrual bleeding You're not having difficulty in conception Most of the time your gynecologist should not interfere with those fibroids if they're not causing any symptoms Or if you found out that you have fibroids and maybe you're just about to become menopausal Then there's no need to sort that out However, if you do have symptoms then the fibroids need to be dealt with depending on what you're trying to achieve So there are those women who are just trying to make the bleeding get better Because the bleeding is very heavy. There are those women who want to get pregnant There are those women who just want that pain to go away There are those women who do not want that kind of distention because it's causing issues with their bladder their rectum So how we deal with them depends on what you're trying to achieve Mainly they're dealt with by surgery So mainly you have to get them removed But that is if you're young if you're looking to get pregnant or if it's causing significant symptoms For those women who are maybe older One of the options is just to remove the uterus entirely And that is called a hysterectomy Yes, but that is for those who've already had their babies who are maybe close to becoming menopausal And whom the fibroids are causing significant symptoms And you know, they feel like maybe it'll be too many years before they become menopausal They don't want to suffer through all those symptoms But for the younger ladies, especially like the 20 to 30 year olds who maybe want to get pregnant And you find this fibroid is sitting inside the cavity of the uterus Then those fibroids need to be removed or maybe this fibroid is blocking one of the fallopian tubes So she's unable to get pregnant and this fibroid definitely needs to be surgically removed Yeah, so most of the time when you're diagnosed with fibroids If they are symptomatic it is likely that you will be having some form of surgery Although there are other ways to treat fibroids as well And and say it's it's I want to say benign. It's it's not cancerous But it's not giving you symptoms. You're not feeling any pain and you know, you decide to just let it chill it want to grow Actually fibroids do grow they increase in size and one of the things that makes them grow is estrogen So fibroids, but my body makes it It's unfortunate. But yes, that's how they grow They do they are predisposed to estrogen in preference to progesterone So that means that when you become an apostle It's likely that your fibroids can shrink Or disappear or stop causing new symptoms But when you're younger and you have lots of estrogen your fibroids can grow They can increase in number And then there are those women who get pregnant when they have a fibroid during pregnancy produce a lot of estrogen And the fibroids can grow during pregnancy for some women they stay the same but for some women they do increase in size Okay, so this Eustrogen tip is kind of making me feel like guys can't get fibroids Because they don't have any Yeah, then they have what's this other one testosterone. Yes, they have testosterone I don't know if I'm going to get it Okay, so it's okay. I tried to find from Facebook. I tried to find what's an order to hashtag this one in the morning We're discussing fibroids how to manage them You know what to do in case you just heard you have fibroids and do not panic you're number one Cyndio. Yeah, so what happens if again, we live in a country where the I I want to say economic situation is a bit Iffy and either you're extremely well off or you are below the poverty line. So what happens if I believe below the poverty line and I find out I have fibroids. How do I get assistance? Okay, so There are certain medications that can help your fibroids However, those medications are called g and g n r h agonists Those medications are reserved for people who are going to have surgery So basically what the medication does it helps your fibroid to shrink And the reason why we give them is because When we do the surgery we want that to be minimal bleeding So that's the reason why we give the this particular kind of medication This medication does not actually cure the fibroid and when the medication is stopped the fibroid regrows So, uh, basically if you're living below the poverty line and you have fibroids Um, one of my suggestions would be to visit a government facility There are very many government facilities with very qualified doctors who are able to remove the fibroids Especially if it's very symptomatic Because one of the things I forgot to mention is that when fibroids cause a lot of bleeding they cause anemia Yeah, and anemia is you know Basically a deficit in your hemoglobin. So in your the the blood that you have And so that can cause a lot of symptoms. It can cause lethargy tiredness dizziness So you're not able to function So below the poverty line you need to work you need to be able to sustain yourself And then this anemia comes in and the bleeding is there and that's aside from all the other issues that are That are happening But government facilities are actually very qualified in doing the surgery to remove fibroids, which is called myomectomy Um, so I feel like that is one of the ways in which a woman who has fibroids who Maybe cannot afford to be in a high end facility can be able to still help herself Oh, okay. Thank you so much guys for watching. I can see someone has just joined our health class We have just discussed this but I can ask her again for on your behalf So they asked about ladies who have enlarged uterus mistaken for pregnancies and how to handle it So previously we said that fibroids actually can grow to to a size that makes you look like you're expecting Yeah, but you're not so how do you deal with a stigma first of all? What is the problem? How do you deal first with the stigma and maybe If you can you choose to not remove and they look that big Yes, you can choose not to remove of course all patients have their choice. There are many women who say I don't want them removed. There are many women who say I do not want a hysterectomy Even though i'm done having my children. I don't want any organ removed from my body. So yes, of course it is a patient choice Um stigma is one of those things that's really hard to deal with It's already hard being female Exactly. So like for example when women come after having a baby and you're trying to you know get yourself back into shape Do you have kids? I do You don't look it. Oh my gosh. Okay. I have a daughter So yeah, so when you're trying to get yourself back into shape It can be quite difficult and already and one of the things that women really complain about is the distended abdomen So um with fibroids, that's the same thing, especially if they're very large the stigma is there I think mainly um family support social support because you know at the same time we don't want to go around telling people No, i'm not pregnant. It's exhausting So but I think lots of support um can make home and feel you know confident because you know you have this condition As you make as you take your time to make the decision as to whether you truly think they need to be removed Or whether you just kind of want to stay because maybe you're close to men or pause or maybe um You just do not want your body interfered with that is also a choice that patients have However, um, it needs to be known that when your fibroids are that big to the point that other people can notice the Distention really something needs to be done about it And the reason is because remember I mentioned that when the uterus gets very large it can press on the ureters When the urine gets stagnant it can cause kidney failure. So that's one of the things The other thing is that when the uterus gets very large It can press on one of the blood vessels that goes to your leg and cause you to get a clot Now when this blood clot dislodges it can be fatal So when your uterus is that large that it's causing significant Distention that other people are noticing you're uncomfortable your gynecologist can see Really you need to do something about it because it could cause other problems So it's not something that you should live with and say, okay. Let me see how the stigma goes It's something that you need to sort out Wow, okay So basically once you've Started your periods you're you're at risk Yes, and especially the girls who start their periods a little bit earlier It's been proposed that they they are at risk of getting fibroids Hey, okay It's breathtaking to imagine how some conditions can affect your whole manner in being the way you think The the way you feel like you should function way is is amazing. Maybe you can conclude What would you like to would you like the youth to understand or not?  It may not be fibroids But it may be and it may be something that you may be struggling with you see And it's better to speak out If you're young and you're trying to conceive a baby and you don't really know what the issue is Sometimes, you know family can be a bit difficult when you're trying to conceive and even friends And everyone is wondering why aren't you getting pregnant? Maybe you're newlywed This is something that you need to sort out especially any kind of gynecological symptoms see your gynecologist Explain it to them. It's better to be reassured and told you know, there's nothing wrong Then to be told or you know, you have fibroids and you know, they've caused this kind of effects and now This kind of surgery needs to be done. So I'd say listen to your body Visit your gynecologist. Let them know whatever you feel is abnormal gynecologically Would would they hurt if if someone with fibroids would have coitus would that affect them in any way? Okay, it depends on where the fibroids are It's a possibility. It is a possibility.  Yes Some fibroids are in the cervix even some fibroids are very low in the uterus So that can cause pain during sexual activity. Yes, it's a rare symptom, but it does happen Okay As listen to your body. That's basic Lesson of the class. Sorry. Yes. Hey, whoa, okay At right five for facebook at five two five four channel onto the hashtag is one of the pointy You have been with us on health matters and we've been zooming on fibroids I hope you've learned something if you've taken away a thing or two And I hear we have a very special something to play for you. I check this out


Hi class, and welcome to the Art of Acrylic. If this is your first time with acrylics, you can achieve results close to this if you just follow the step-by-step guide. You really will be able to get it. They're very simple principles. You've just got to follow them a little bit at a time. This is what we're going to achieve from this painting. It's a very simple still life setup, but it looks at a lot of the principles used in painting, a lot of different elements all working together. So the idea is of negative space, which are really helpful for you to be able to draw things more accurately. You'll see here in the handle and this little shape here. The idea of perspective and giving your viewer an idea of relationships and sizes is used with overlap. So how we've got the lemon placed in front of the jug here. So the method that I'm going to talk through in this painting is using a very limited palette to start with and then slowly introducing colours as we get further along closer to the finish. However, as you get more adept at painting and more used to it, you can of course start with a full range of colours to start with and it will be quicker than your first one. As with everything, it's always better to kind of start slowly, creep up on it so we don't have hundreds of colours getting a mess and then never get our paintings finished. You also learn how you've got to hold off your highlights until right at the end to make the jug have this real nice sheen to it. How to make your lemon juicy with glazes over the top to really bring that warmth and how to make your tea just look tea really good to drink. So we're going to start with one colour, a brown burnt umber, a very very useful colour and we're going to block in our painting. This is just looking at the masses of the drawing as in what is a light area and what is a dark area. This has been shown here from using one single light source. This is very effective when you're painting because it really helps to give the illusion of depth and that's one of the trickiest things to get when you're trying to convince the viewer of your subject. If we had lots of different light sources all coming from different angles, it would look more like a photo shoot where everything's really highly finished. In painting you want to try and keep it simple so it looks more effective. So here we've got one light source which reduces these lovely shades of what are called cast shadows as in the shadow cast by an object. So grab a brew, grab your brushes, maybe a biscuit you might need it and let's get learning.


Good morning, John. So the thing about the way that I'm getting chemotherapy is that they really dose you. They hit you super hard on Friday, and then you get one Friday off, and then they hit you super hard again on that Friday after that. And the whole idea of this is that the four different chemo drugs that I am taking, they do a good job of interfering with cells that are currently in the process of dividing a lot, which are cancer cells, but also some other cells, and so it makes you sick. Like it way disproportionately kills cancer cells, but it also kills normal body cells, and so that makes you feel terrible. And they want people to stay in treatment and not feel too bad, and they also want to minimize complications that you do get if you have too many negative side effects piled on top of each other, and so they let you recover, and I'm feeling so like normal right now before they smack you back down, which is happening at 9 a.m. tomorrow morning. And this schedule turns out to be very good, so far at least, for Vlogbrothers. So like I have a full week of recovery before it's time to make the first Vlogbrothers video, which maybe I'll do next week, and then I have two full weeks of recovery before it's time to make the next Vlogbrothers video. Fantastic, and here's a weird thing. By like day six after treatment, I felt like 100% of the bad feelings in my body were because I'd just been lazy and spending too much time in bed, not walking around enough, not getting my body moving, and I was achy, I just felt gross. But dear Hank from the past and also Hank from the future, you felt bad because of the chemo. I feel much better now, and I'm just as lazy as I was a week ago. It's a weird thing to do to your body. I mean top five weirdest chemo side effects. Hiccups from the dexamethasone, which you actually isn't, it's kind of a chemotherapy drug, but mostly you take it to hold back nausea and feel a little bit better after getting your treatment. Hiccups, intractable hiccups. I probably had like 12 bouts of hiccups, last more than 30 minutes over the course of two days. It's miserable. Red urine, which you might think I'm dying, but in fact is just one of the drugs, is a red color, and it can come out in your urine, and also your sweat, which makes me ask what kind of person is sweating during chemo? Like I am not exerting at all.  Hippos have pink sweat. It protects them from the sun.  Salivary gland pain, didn't realize that that was possible. The moment I saw a dish of food, I would, it would hurt, because my salivary glands would activate and start creating saliva, and for whatever reason, they were recovering from injury, and it was physically painful to drool. I thought I had a UTI, but it turns out chemo can just make your urethra hurt. Is that TMI? I don't know. And last, this one is super normal, and I just had never heard about it, but your mouth gets sore.  None of those, however, have been the worst side effects for chemo for me. I've been very lucky to have been spared nausea, had a little bit, but nothing big, but I've had a headache the entire time. It's much less bad than it was, but for me, the biggest and hardest side effect is just the fatigue. It does not feel possible to be that tired, and I felt that bad. Like during when I had COVID, it was a similar feeling of fatigue. It is hard to move your arm enough to grab the Gatorade bottle. Getting up to go to the bathroom was work. And you might think, Hank, he's putting on a brave face during his chemo, but no, I'm not. I feel better now because I'm on the last day before I get walloped again. And very importantly, different people's chemo regimens are very different. People respond differently, and people are taking different drugs, so I'm not trying to represent like the universal experience here. And they say hair loss begins day 14, which is tomorrow. So I told Orrin about the hair loss, and he said, but when does it grow back? And I told him, you know, it's gonna take a while, but it will grow back, and he felt fine about that. So if he feels fine, then I feel fine. Everybody should feel fine. John, I'll see you on Tuesday. And here's some pictures of some flowers and bees that I took in my garden. It's very nice, isn't it? I'm just glad that this happened when the weather was nice. They would have been miserable in the winter. You believe this trick in flower? I think I'm on a journey of meaning.