the scooter here is what they said will actually march on march on to occur. So the needs of what the local systems will need and how that will happen is the game changer and you know what you can get as power saving from a workload defined computer is not what you can get otherwise from a virtualized environment, because virtualized environment still runs on a computer which is 8 core 10 core 12 core or whatever it is that kind of a module and if you if you slice it thin then you will not be able to run that many VMs and if you slice it too big then you don't you cannot utilize it in full. So there is a and although you have power cycle controls it's not that these two will meet end of day and that's where you see a paradigm with the advent of all these mobile phones and arm processors and calcidas which are coming you will see a trend which is made to define made a compute which is made for a specific type of workload and you will start this model will start emerging. So a cloud never said that you know cloud never said that clouds basic that's why I put what is clouds basic needs and cloud didn't say that what type of compute it's actually needing and what it is doing is that the industry is adopting to cloud and answering to cloud in different forms and this is one of the forms which it is answering the known form is virtualization and there are trends which are happening and these trends is what I wanted to introduce here and I'm not trying to say which one is winning or not because then I wear a suddenly I wear a HP hat and I intentionally don't want to have wear that hat put here. So it's a cloud never defines that it's virtual or physical cloud basically says I should be able to migrate I should be able to do this it should give me elasticity I should be able to meter that's the semantics and the first slide which I put is primarily to say what's a cloud okay and cloud says any form of compute can be cloud managed okay. Come and say okay you know it could run in any hardware X86 platform we are all good right but it's up to the company you know how they want to minimize their operational expenditure. Sure I agree there. So it doesn't say that this type of compute cannot come okay so you might see IBM's power someday coming into cloud okay I don't know when but that's also feasibility. So just to add to your question I can tell so one of the problem which we were trying to address was that how can the cloud situla be intelligent to choose among the type of workload to be pushed to a type of particular type of compute node. So that's kind of little futuristic but suddenly a lot of people including us are looking to that that if I get five requests and these requests are not all same they are different and they are there are different type of cloud compute nodes to be optimized for them. So can I have an intelligence built-in that I can row reroute it based on storage base same with network same with compute and get the maximum output of the cloud. I agree so I chose the topic as compute and I kind of if I touch networks and go on storage I think I will not stick to my 15 minutes or 20 minutes and I kind of stayed only with one topic and wanted to tease the brain of people out here so that how do you want to look at most of us look at virtualization and there is a paradigm which is actually evolving and how do you want to look at that paradigm. So this was a brain teaser and nothing else and you know I just wanted to play it that way and that's all I wanted to do. So basically in the networking maybe no let me touch up something that I'm running into and also you know it is part of grisly. So we introduce something called a service type right you define the service type what you want and the driver will be chosen based on the service type the request is going to submit to the cellular. So we are implementing that as part of quantum but you know it could be extendable to anything else. So you know do you want it as part of flavors and service type as part of flavors. See the only problem with the open stack is when you put the idea you have 20 ways of putting idea okay and how do you say which one is right is a challenge and that's where most of us struggle and it's how to convince the community is one of the challenges and you'll have to be pretty powerful inside the community to convince somebody or not get convinced one of these two is true. Yeah actually I was playing the troll for some time at least in the load balancer stuff. It's mediating you know the vendors between the vendors and community and you know finally we agreed on the service type at least in the quantum area but it's almost like flavors. Yes. So any more question. He has been presented by the Vianchu and he leads the open stack development and open stack initiative at Dell R&D. So I would like to welcome the Vianchu for taking up the next session. Thank you. Good afternoon everybody. Just okay you can hear it. So session just after lunch is not the most interesting session. I totally agree because I feel the same way and a lot of things in lunch so it was good overall. However I when I saw my slot and I think so when I saw the slot and initially when Atul contacted me to talk I was planning to talk on quantum or something like that but past two three months or five months I've been working open stack for kind of like two years now when I jumped into that and earlier when I was to visit two customers or talk to them what actually open stack used to be a very big question. They have not heard of it. They only heard of VCloud or Amazon or some competitive product and we should explain them this is what it is but over a past of five six months in my interaction what I observed people buy and now know what open stack is. People buy and now want to use open stack because when we talk to our customers from their side and we propose something on cloud computing we are okay are you guys doing open stack so that's a good news. However when we try to put a complete solution to them to the all the customers we always struggle. Struggle in terms of that who will do this who will do load balancer who will do metering who will do billing where will I get opens like open hardware things like that. So that's the current state what we are seeing in India. I'm talking of some very big names I can't put it in open but like guys who are running close to 20-30 billion dollar business those are our people want to experiment with open stack because they understand the value open source but they don't know how to do that. So this presentation is kind of arranged around what are the customer problems which I saw here and what these customer problems do they like span to some opportunity or to the very point if they are not solved can it be detrimental to open stack in terms of getting adopted by the business and that will be the death knell which none of us want. It's good that we are strong on kind of technology best it came from NASA I have all the 200 big names in the world even think of but end of the day a Goldman Sachs or a Citibank or HTFC bank has to consume it. Dell IBM HP NetApp was some name but we are and end of the day a service provided with open stack to a business. If they don't get the complete solution chances are we are not going to take this story very far. So this is this presentation is all about that it took me a lot of time to do that because that's not my core skill. I'm an engineering manager I do I have done like 15 years of coding mostly writing device driver for Linux and however I picked some business skill in the meantime and kind of read a lot of reports from KPMG to McKinsey to price water house and what actually this consultants or big five as we call them how to position cloud computing to the customer. Like if I go to some like big bazaar or a future group chances are they will go to this big five and ask them to do a audit. This is my IT problem this is what it is. I want to go for cloud computing does it make sense or doesn't make sense. Then these guys will come up with some sort of report and see that okay their business problem fits into the cloud computing or not. So they play a very intermediary role and we have to accept it that's the way the world works because if I the technology company go and talk to a customer chances are this thing I am like biased I want to promote technology or I'm to putting I'm putting technology on his plate because I'm a technology company. So this whole presentation is kind of thanks to KPMG and McKinsey for putting a lot of reports on the internet all open like open information nothing confidential here and I could read and skim and understand okay what actually customer talks about. At least from the India perspective I may say so. This also gives you this will also give you a presentation this will also give you a perspective that if I am a I'm not a Dell or HP or Cisco I'm a SMB where I'm going to invest my energy in cloud because cloud computing is growing if you have seen economic times probably two days back there were eight VC fundings in one week for cloud that's how hard is cloud that's the way I've known two of a very senior colleagues of mine a different company with quit their job and started a startup and within eight months they got six million dollar funding of cloud but what actually is getting funded is like infrastructure service getting funded or a pass is getting funded or a SAS is getting funded or a B pass is getting funded because these are the customer pain points. So this this presentation will kind of touch among that it's not the higher technology so bear with me if you get bored with all the business talks. So this is kind of a little bit of evolution of okay this is a little kind of how everything grew to from like mainframes to this virtual society of a Facebook or LinkedIn and the cloud computing when computing was supposed to become a utility this kind of little bit of map there it tells a lot of things that okay how the new business models came into picture how we started talking of CAPEX to OPEX was computing how we started talking of the elasticity of demand like switching off the lights how we started talking of activity based costing that if I am a business house I run a textile business I want to start a new business how will I accommodate active cost of IT into my business earlier IT was a big idea was a small room then the budget of IT became more than the business itself and then they have to move to data center and then they close down and the outsourcing and things like that so this kind of a graph for that that how the things changed things change because adaptability of IT or we became more digital in our content we started doing a lot of things digital in terms of interaction cell phones social media even professional contacts recruitment most of the things start going to be applied so this kind of a map for that now if I did if I looked into the definition of cloud computing and kind of skimmed out these two lines which on the whole like explains everything to everybody like internet based data access and exchange that's what we want to do in a plain and simple English internet based access to the low-cost computing and application the cost has to be low and finally there should be an application that is relevant to my business I'm going to buy storage but I'm why I'm going to buy a storage I'm not going to buy a 15 meter clothes I want to buy a jeans to wear so how does the business so that's part of application that how it does the business look into the investment in cloud computing now characteristics what we talk of is on demand self-service internet accept the internet accessibility poor resources kind of you can take a huge resource position into the different clients at the same time to the cost of operation becomes low if I have this room used by 500 people suddenly the cost of this room becomes 1 by 500 if I have one guy setting this room probably he bears the whole cost that's a cool resource in what we talk of usage base building that's still coming up I see a lot of interest around that I heard it nice talk of PayPal's and from Bharat that how it's all bringing up from rixon so it's good but when I when I when we talk to the customer who are non-IT guys we have PayPal is like tech savvy company rixon the very tech savvy company fp one of the like pioneers Dell and all so we know what to do however when I talk to like big bazaars and future groups who are the real consumption they have absolutely no clue today that what's going on when we go to position cloud in the non technology company if I go if you come and talk to me I'll take a guy I can tell you five more things of what cloud does when I go and talk to a non IT company these are the stakeholders which I see there the CEO who has to do a business transformation because his bonus rest on that he has to say that everybody talks about I'm going to do the cloud to it then there's a CFO and a CIO or a CTO who talks from the cost perfect cost perspective how will the whole infrastructure look into that and there are IT managers and the teams and vendors and outsourced partners who got to do the real work so there has to have a visibility of cloud in terms of the top guy the second it's a second stage and the third stage by the way at the CEO level chances are that he is not concerned with your implementing cloud at open stack or a imagine or a week out his business is not he doesn't even care about what sort of cloud you're implementing so how will an open stack make a pitch there or is it feasible for open stack to go and pitch at that level that's what we're trying to explain this again from this side of that I told you that each one have a separate goal so when we talk to them like we have an opportunity to talk to all the three levels we have a three different slide decks for them when we only talk about how we're going to how is your business going to transform in terms of globalized business how is your business how you are going to when I come to see a for CTO the chances are I'll talk about how will I reduce your IT budget CapEx to OpEx modeling the third guy comes I'll say okay I'll help you to scale out your push out your patch to 20 different countries over time without breaking anything so different sort of conversation that you make in terms of the type of people you talk to and then on the other side we see others like kind of one year old because I was a little lazy to do that and not well I can do this this is a whole of the math I did that house rack space cloud business growing so even in your growth if you see is kind of pretty high so there was certainly consumption of cloud computing in the business where ever everywhere in the world but why not India that's the question which buzzered me up if everybody in the world is consuming cloud from rack space Amazon has a even bit better growth story why Indian businesses are not adapting to cloud so then I look into that okay how does a cloud ecosystem looks so we have like a supply side and a demand side supply side we all most of the chances are which is on the supply side we have a different role somebody is a strategist somebody is an architect somebody is an implementer I said


What's going on guys welcome back to the channel critical overload here We're gonna go over some horror updates here in this video here today horror topics We'll be going over saw in the future with saw 11. We'll be talking about Friday the 13th We'll be talking about that update that came out from h45 regarding the Halloween franchise We'll be talking about scream 7 a brief recap of the video I put out this past weekend and we'll be talking about Chucky season 3 So just to start off with saw 11 saw 11 has been teased by Mark Berg one of the producers in a late or in The latest interview with dexurdo. He said saw X ends where I think the audience will want to know what happens And there's kind of a cliffhanger ending Kind of I mean it quite literally was to me Anyway, and should this movie work there are going to be a bunch of actors from the past who have already called wanting to Know if they can come and be in the next movie since we're going back in time in reference to the fact that saw X is set in between saw and saw 2 Orncolis or orange holes also added this we're very superstitious We don't even start thinking about saw 11 or the next movie until after the latest one is released But I'd bet on it. I believe there's like a six to five month Window between saw 2 and saw 3 if I'm wrong miss correct me down below I think there's like a few months in between saw 2 and so saw 2 and saw 3 So there's room for stories to be explored. Could they go back after more of those frauds connected to CC? I think her name is Cecilia. I'm gonna call her CC What was the fallout from Henry and what happened there? You know, there's so many different questions What was the fallout from what else happened on in the mid credit mid credit? Sequence that came out when the credit started rolling. What is gonna go down with Amanda And how do we get to her betrayal of John? Well, we see that unfold in saw 11 so many different avenues You can take jumping into Friday the 13th Ryan Turek from Blumhouse recently made comments about a Friday the 13th revival Some hopes that they have I guess while speaking with inverse He said Jason Blum and I are definitely in agreement that the Friday the 13th series is a thing We would love to get our hands on I really want to go back to the basics You don't need too many ingredients for a Friday the 13th film You need summer camp you need campers and you need Jason for he's in a mask I mean, that's a simplified way of putting it but fans who care about and know about How the series could definitely and be improved in the quality department I think we could argue that you also need a good story strong cast strong director strong crew in general I'm sure that's not lost on miss a Turek. He's just basically Simplifying his answer of the ingredients and he's not wrong But I would hope that's genuinely not all you think that you need I trust that you don't But the Crystal Lake show we know is still expected to debut on peacock sometime in the future So we'll see how that goes I honestly am becoming one of those fans who doesn't want Blumhouse obtaining rights to horror franchises Since this upcoming exorcist film and the handling of the last two Halloween films are just turning me off to the idea of Blumhouse Dipping their hands or dipping their feet into any other existing IPs. I'd rather them just continue to distribute or produce and put out Original IP content. That's all I want from them. Like keep focus on Megan focus on the Megan franchise. Do what you got to do there Friday the 13th. I don't know. I I'm just getting turned off by Blumhouse and their involvement in anything I don't want them touching Freddie. I don't I damn sure don't want them touching ghost face dive it into Halloween at H45 Malika card according to Halloween Daily News shout to you had announced that a new documentary on his father Mustafa Card is coming teased big news for the Michael Myers franchise dropping before this Halloween and Strongly hinted that a Halloween video game is on the horizon So that leads me and many others obviously to think some of that news that's been reported previously is more than true 824 leading the bidding war for TV rights Trank is being open to both film and TV projects and of course the possibility of a six episode TV show set in the Season of the Witch universe all of those were some of the things that came out last week from reliable sources We'll see what ultimately comes out this month. If anything I really didn't think that Mikey or this franchise in general would be talked about In the capacity of a revival not even a year after Halloween ends it hasn't even been a year since Halloween ends if I'm not mistaken hasn't been a year just yet Also Malika card He allegedly made remarks about a diva actress in the series and unfortunately as much as I love her All I can think of is Daniel Harris, but again, that's alleged. I don't really know if he said that But let me know what you guys think about the possible announcement this month and what you think it will be since Halloween Daily News labeled it as big news for the Michael Myers franchise dropping before this Halloween I'm inclined to think that we're gonna see Michael Myers very soon not just a season of the witch Adaptation or revival of sorts, but we're gonna see Michael Myers announced in some capacity to have a big project on the way Now diving in the scream seven scream seven Will as of now be planning to take place during the Christmas season But I wanted to let everyone know that Canada is still on the table I do not know where shooting will exactly take place, but I do want to reiterate Canada isn't completely off the table as a possibility I also will add that I don't think there should be too much concern over this being a gimmicky thing Because Halloween and scream six wasn't particularly overly prominent in the story either It was basically just a backdrop if anything Christmas setting can be ironic to the story Considering Ghostface always want something and they want something yet again. And what do you get for Christmas a gift? What better gift than knocking off every survivor from the face of the earth? That's how you can correlate it to the Christmas theme. That's the most I would want them to do anyway I don't want anything over the top. Like I said, I don't want him killing someone with Rudolph's red nose I don't need someone being killed with a Christmas tree or a Christmas tree ornament in some type of comical way I don't I don't need that stuff. I would hope that that's just simply a backdrop and you retain a serious tone That's all now. The last thing I want to touch on is Chucky season three I saw some of you posting Clip it snippets from the reviews that are continuing to come out ahead of the series debut season three anyway this Wednesday So season three will indeed feature some Hospital shenanigans. I saw a review shared by one of you. I think it was you Eli. So shout out to you guys The hospital shenanigans are not scary In fact, they are why I'm a little disappointed in this season when it comes to suspending my disbelief because while I can't suspend my disbelief for this to work in general You're talking about a killer doll. I never want the person creating the art to constantly just say well We took it this far with their suspension of disbelief. How far can we keep on pushing it until we cross a threshold? So trust me when I say nothing about the hospital shenanigans. They're not scary Chucky yes, we'll be on screen in a hospital gown Very little about this is sensible and it raises several questions that I pray get answered in part two because so far it makes no sense if anything it's a sequence that I would argue isn't even necessary if you're telling me that you're Going to be giving me these scariest or going back to the roots of being scary him in the hospital gown is not scary That's not scary and in the context of it all. It's just laughable There's so many different things about the first half that are the opposite of what we were told we would get and that's why It's disappointing that is why it was as if you just lied for me to simply trust that you would do it And you didn't do it now granted. Maybe you'll do it in the second half and I'll praise that That's why I'm trying to be fair and I gave it a 6.5 out of 10 if you keep it up I am going to drop my my rating for the season and it still so far is the weakest Let me know just think about this down in the comment section below if you haven't already of course Make sure you subscribe turn on post notification numbers video in the description. I have links on my social media accounts I'm on Facebook Twitter and Instagram you can message me there, of course I'm as any movies news or reviews I'm going to cover in the future and with all that in mind guys I will see you in the next video


All right, welcome to the July 10th and on CREDS B2 working group meeting. A couple of topics for today made one being revocation requirements and trying to get to a formal definition that can be put in a paper of what the revocation requirements are so this is a chance to talk through those and then this to lead to a formal document that we produce that outlines the requirements of revocation. Since it seems to be the trickiest part of all that we're doing. I hear that this specification is under the community specification license so if you're going to work on it, make sure you're aware of the requirements of that it's kind of like the Apache for not for open source but rather for open specifications. This is a Linux foundation hyper ledger foundation new meeting so the Linux foundation trust policy is in effect, as is the hyper ledger code of conduct. I'll share in the chat the link to the whoops that's not it. That's not it at all. And hopefully you. Hey, I can delete a message. Whoa, cool. Anyway, this document is here I want to shift into edit mode for it, but if anyone wants to add their name to the attendees please do so. And help with the note taking that would be great. Anyone is new to the community and wants to introduce themselves and what their interest in this is that would be good to have done now so grab the microphone. My name is Ashley. I'm new to the group. Just trying to get my feet wet a little bit and get my, get my understanding oriented towards what what what you're doing with an on credit so just kind of interested in listening in today and seeing what it's all about and hopefully we'll be able to contribute down the road. Awesome. Welcome Ashley good to see you. Hope you are well. All right. I want to get into a presentation discussion on what we need for revocation that's the big topic for the day. So let me share a presentation that I've got share. Copy the link. I'll put that also into the chat. So this is the presentation I'm using. As I say looking for feedback on this. Whoops, what we're trying to get to is an academic paper or style that outlines the, the revocation requirements in a formal way. So I'm using a bit of pushback from the academic community and in looking at some of the revocation methods that we are talking about. And part of that is they just don't feel like we've got enough in the formal definition stage so that's what the goal is coming out of this. Problem statement. We need to replace the insufficiently scalable and our friends be one revocation scheme as soon as possible so that's the main thing we're trying to accomplish. So revocation being a requirement of pretty much all use cases for verifiable credentials there's some that don't need it but but most do even if, even if it's not understood at the time you get started, even if the only reason you need revocation is because you issued a credential by mistake and you need to correct that. That's the requirement for having revocation and and so almost every use case for verifiable credentials includes revocation. Expiry dates in verifiable credentials are crucial and and are recommended but are insufficient for revocation if if there's any sort of pseudo real time need for revocation it has to. be available. It has to be part of the revocation scheme and expiration isn't good enough, or generally not good enough expiration is is well we'll go from there. The dog wants in so I have to open the door. But that's okay participants so revocation options I'm going to go through a set of options but do that by going through the participants the attributes and trade offs and then look at the options we've got. So participants generally people know these issuers holders and verifiers anyone who knows anything about verifiable credentials knows those. Revocation manager is a new participant from time to time a revocation manager is someone who provides information about revocation in some form. In some of the schemes we've got their formally called revocation managers. Others, they, they just hold and provide the data necessary. Data sources are include revocation manager so where you get revocation manager issuers published revocation data holders retreat generally holders retrieve that information and generate a proof verifiers also generally retrieve revocation information and they verify the proof in the holder so that's the common model there's a couple of variations that we're going to see. So it's not always that. But that revocation data source, where the information that gets published by the issuer appears can be in a couple of places. So verifiable data registry eg ledgers or, you know, places where it did to reside. Ideally, it would be passive meaning that the verifiable data registry itself does not dynamically need to generate revocation data. It is just static data that it serves out. So just like a did doc is a static document that is returned when a did is resolved it would be nice if revocation data were static data and could be returned as as is from a registry and the reason for that is it reduces the capability necessary for the registry. So for example is hyper ledger Indy which dynamically generates requested data so Indy knows about an on Cres revocation register they're not just some static data that gets published on an indie ledger but rather Indy knows about them and accept specialized requests to return. For returning the deltas being the change statuses of various credentials so instead of getting the entire state from Indy. You get a list of the credentials whose status has changed since you previously asked for it whether that's from the beginning of time or from some point in time where you previously asked. That's a potential privacy issue. Yep. Exactly. And, and it adds an additional requirement on the ledger to say oh I need to be able to do that so in an on creds v one that we've implemented we basically taken off that as a requirement that well Indy can do that. Other other ledgers can simply return the full state of all credentials and not asked for a point in time or anything so when they get the state of, you know, a given state of the of the credential status they get all of them. So that's a way to turn it into being passive. Revocation managers are proposed for some schemes basically they are an active server that responds to a request from from perhaps an issuer to get revocation information. The response is dependent on the type of scheme so one example is basically called linked verifiable not remembering LVVM that we're going to talk about through this. Basically, the issuer asks a revocation manager, give me a proof of non revocation of my credential as of now. The revocation manager simply issues a verifiable credential and a non credits verifiable credential that is in the same format as the primary credential. But the purpose of that verifiable credential is to prove non revocation. And so that's one method of doing of a revocation manager operating. And there's other ones as well Alasor in its implementation has revocation managers as well. Generally revocation managers share are provided information from the issuer, and then they share that information. And again, last one file servers is really the same as verifiable data registry. If it's a file server than it truly must be passive so it provides only static files not server generated responses. So, where a revocation manager responds to a specific request. A file server is simply providing a state object essentially a static static file that was issued to it, perhaps likely from the issuer. So those are the participants in the process so the basics. A revocation state of all credentials is public published periodically by the issuer. So the issuer keeps track of every credential that issues. When it wants to revoke a credential or a bachelor credential it publishes a state update where it shares either. Either the deltas of what it's changed recently since its last update or it simply shares the entire state of all the credentials, and that gets published periodically to whatever is the appropriate place for the given scheme that's being used. When presenting a proof derived from revocable credential the holder provides proof that their credential is not revoked based on a specific revocation state. So, the issuer has published a bunch of revocation states, the holder gets one of those, and if their credential is not revoked they are able to produce a proof that their credential is not revoked. So I guarantee we're looking for the, the, what we're interested in is that the holder cannot provide a non revocation proof, based on a published revocation state in which the holders credential is marked revoked. It would be nice to have so that's that's the, what we're aiming for it would be nice to have that a holder can create a non revocation proof for a given time in the past so the use case is. So a car accident occurred on in 2020 and the holder could produce a non revocation proof that at the time of the crash back in 2020 their credential had not been revoked, even if it had been revoked later. So that's a nice to have proof. A credential is not revoked must be linked to the credential to which it applies so a given proof of non revocation for a primary credential cannot be used. It can only be used for the credential to which it applies so there must be a linkage between the proof of non revocation and the credential about which it is talking. And finally there must be an unlimited number of credentials for credential type so there must be no set limit on how many credentials can be issued. And if a revocation registry size so if you do have a limitation on the size of a registry a revocation registry, there must be a way to have multiple registry so you can just create a new one and continue to issue the same type of credential. That had been that you've been issuing just using a different revocation registry. Jump in anytime if I'm not being clear as I say I'm trying to get this to be a lead to a formal document that outlines all of these things so help in making sure I'm getting that down would be useful. It's in a in a zero knowledge proof based system unlinkable identifier so no linkable identifier is given to the verifier. The goal is to prevent correlation across verifiers and between verifiers and the issuer so when a when proof of a revocation is given to a verifier you given to multiple verifiers, you don't want to wait for those verifiers to. Compare a unique identifier across each of those so they can correlate or or with the issuer so they can report to the issuer when a credential gets used. There generally are two IDs that are involved. So one is the revocation registry ID itself so where the revocation is tracked, and it is okay to share that or it should be okay to share that now get to that next. The second is the actual revocation ID. And this is a loose term because generally it's a, it's a concatenated key if you will generally it's the revocation registry ID and the index within that registry of the particular credential. For a particular credential, it is not okay to share this revocation ID that would be a unique identifier for the credential itself. It is okay to share the revocation registry ID and often necessary so that the verifier can verify the can verify the proof provided. The revocation ID itself is commonly shared between the issuer and the holder, it is not shared with the verifier so that's the limitation there. The registry size must be large enough to hide in the crowd. Hey, Stephen, what about a revocation registry public key? Can that be, I mean, obviously not every revocation registry needs it, but can it be optional? Yeah. Okay, that's helpful. Thank you. Yeah. No doubt on that. Because some accumulators use them some accumulators don't but you might like let's say you're on a file server, you might have the public key use to verify a signature overhead revocation set. Yeah, I guess we could say public parameters that are unique to the registry. Yeah, yeah. So like maybe instead of revocation, well revocation ID is fine. Registry ID is fine. I'm just talking about like, yeah, public parameters for that revocation registry. Yeah. Thank you. Okay. The registry size must be large enough to hide in the crowd. So the idea here is, suppose I have two credentials that are revocable. I share them, I present them together. And in doing that I provide a revocation registry ID for each of them. Basically, registration, the rev regs themselves are so small. Basically that the chances of somebody being in those particular two revocation registries is as unlikely and hence you get what amounts to a linkable identifier so this is the current problem we have in on with an on credits one.  And so the suggestion that I've heard of. What I just made it up was at least a million credentials needed within a revocation registry to prevent this this to prevent this kind of linkability. And obviously, if there's only, if it's a single credential with a registry a population smaller than the revocation registry that's fine there would only be one revocation registry for that entire credential. This one is probably the loosest requirement I'm not quite sure how to say it any better than that so. Hopefully that's clear. This is the one that I didn't realize for quite a long time was this, this issue. Once the verifier has received a proof of non revocation the verifier must not be able to see changes to the revocation status of that credential. This is a complaint that I see or and I certainly make with the revocation list 2021, which is a non ZKP to begin with but basically once a holder shares their identifier for their credential to the verifier the verifier can go to monitoring the revocation status and see if in the future the credential gets gets revoked which is could be a feature in in some people's view but I see it as a consent issue that you're actually not giving you don't want to give the verifier ongoing ability to track your revocation status. Linkability can also be looked at from a calling home perspective. So nice to have and perhaps required in some cases is to avoid calling home during presentation so calling home is where the issuer or sorry the holder or the verifier, or both have to call back to the user for example the issuer to be able to retrieve the information necessary to do a presentation. And the issue there is basically web logs can be used to track holders and verifiers and track what they're doing and the correlation between them. Nice to have, and in some cases required avoid the user being able to track when a holder is doing a presentation, avoid a user being able to track both the holder and the verifier during presentation and the problem there is a holder gets revocation data from the issuer to create a presentation and then immediately afterwards the verifier calls the issuer to verify that presentation. And now the issuer can correlate that the holder use their credential and the verifier with which with whom they used it. And that's, that's what we want to avoid. Even the perception of calling home is a problem for government so for example if I, every time I used my person credential to prove my age. There was a web call made to a gov.bc.ca, you know, domain, a government of British Columbia domain, even if there wasn't data being tracked, this perception of calling home is problematic. And that could just be the rejection of the use of the mechanism. Basically a viral. We won't use this because it's it's government tracking. Call home assessments must be considered based on the likelihood of collusion so the revocation manager idea can be considered a call home, even if the issuer and the revocation managers are different parties. So that is something that needs to be looked at as well. For example, in, in Canada, where the revocation information is going on in indie ledger that ledger is actually operated by a different government entity but it's still government entities, or sorry, entities. So there is a call being made which may offend holders and may develop mistrust in the system because even though it's going to a ledger which is in theory a neutral party. So that's the possibility of tracking now again it's all a, a range of of gray in this. So it's not always clear exactly where this problem needs to be prevented I mean you've got to get the data from somewhere. But there's better. Some places are better than others is the idea. And I'll do an aside on this that an idea came up recently where the verifier provides revocation data to the holder so the verifier is the one that reaches out to wherever the data is is cat. And then the verifier provides that revocation data to the holder. That's an interesting idea that I've been exploring a bit to try to eliminate this call home from the holder. It does require in some cases and extra back and forth between the verifier and the holder but it does mean that the holder is only interacting with the verifier and that's it. I've been looking at a paper from Andreas fry tag, based on a diff survey he did that talks about issuer holder privacy and issuer verifier privacy so this is the issuer holder. So this formalizes a little bit the issuer gets no information about the usage of the VC and the verifier and or the verifier involved. Semi private the issuer gets information that the VC is used from the holder. Or gets information that a verifier is performing a validation process. So one or the other, and the, and then the no privacy is where the issuer knows the VC the holder and the verifier used in the validation process. So obviously the higher we are on this scale the better. So this is likewise from the same paper holder verifier privacy so full privacy, semi privacy and no privacy. You can see those definitions so those might be useful in the paper we use. We're creating. So we can use those descriptions. So just looking at the last slide of course there's always a risk. Because the verifier knows who the issuer is. They can. They can tell the issuer that a verification is happening. They might not be able to tell them who the holder is exactly. Although most of the time they will have one or more attributes to write back. Not based on the fact that presentation was given, but based on what was presented in the credential. Yeah. Yeah. I think you can always do that. I'm going to be careful not miscommunicating that you can always of course, if you know the issuer, which you're going to have to report back, but it's it's important that to achieve the verification required that you're not systematically required to. Yep. Yep. Competing capability so basically. Assumptions that that I've seen lately assume issuer and revocation managers are enterprise apps so they have pretty powerful systems, lots of storage. You know an issuer must track all the issuances unilaterally revokes them and publishes revocation is necessary either as the revocations happen or in batches. Our assumption has always been pretty much that the holder is a mobile wallet. In the worst case. You should not have to download substantial files during a presentation presentation time generation time should be short and I've actually got numbers on the next screen about that based on Andreas's work. And then this is a bit of a new one. Usually we think of verifiers as enterprise apps as well. But we're actually doing a fair amount in verifiers being mobile apps. Where, you know, a mobile verifier could, could, you know, display a QR code scan it by the holder mobile app and the two of them just trade a presentation and the verifier would have to be able to do it so again, if we if we go with the lowest common provider this is a reasonable requirement should not have to download substantial files verifier time should be short. This is the from a paper that Andreas did again based on the Diff survey. This is what the survey participants said they sort of you know, the verifiers and verifiers in this case as enterprise folders as wallets. They've got a tighter bound on the size of the data that the holder should have to, you know, retrieve and use on their device. And then in the initial time, nobody really cares about the issuer. They can throw more metal at it so that's okay. We want it to be within a second. For the most of the respondents to the survey and a tenth of a second for verifiers so they want them to be very fast. So those are higher numbers. So if it's with the call home, I should probably get rid of this slide. This is really to do with calling home that the holders and verifiers collect the data from different sources. They do it from other than the issuer because of a call home issue and perceptively independent so really is the same issue. There's one extra one, which this requirement stands from the idea that when issuing a credential that you may want to sign the credential with an on creds signature, but you also might want to sign it with a nest signature. In that case, if you also want to support revocation, it would be nice not to have two different revocation schemes having to be kept in sync. So, if a relatively simple bid array techniques similar to status list 2021 was available, it could be used for the nests. It could be used for the on creds purpose, but also used for an on creds purpose so that's, you know, another reason, a nice, a nice to have alignment. That is looking like a possibility down the line of having a credential signed with two different signatures and then, and for them to be used by the two different. Signatures to be used by verifiers, depending on their needs so that is a possibility coming down. These are the. This gets into finally the four schemes that we've looked at you know on creds 1.0 Alasaur, LVBC, which is the one that Andreas produced, and then finally ZK Sam, the signed accumulator membership. So papers are linked to all of these. As I said this, this presentation is more about less about the solution more about the different how to how to formalize what the requirements are, but this sort of shows where the on creds basically falls apart, can't be used. A benefit from ZK Sam. Having a bit array type data scheme. The size of the file being much, much larger but still not massive in the ZK Sam but much larger than the other schemes. The call home or perception of call home is in both of the Alasaur and LVVM approaches. So yellows. Well, maybe have a clarification like Alasaur doesn't necessarily need to call home every time you present. Yes. And when it calls home it's anonymous. Yeah. And that's why I've got in here revocation managers. They are dynamic. The revocation manager is a dynamic service that must be available right. Yes, that's. So that's the summary. Anything I've missed there. And Mike, in particular, do you see anything that would contribute to a paper. So what I'm thinking of doing. If I go back here. Andreas has a section that that basically uses the survey as the, what are the scheme so I'm sort of taking some of that from his but less survey based. And talking about the things that are in my in that presentation as the way to present here are requirements seem reasonable. Yeah, I think for the most part. Maybe I don't know how to add this. If it does call home, is there a way to say it's required to be anonymous. Yes. Yeah. So the other requirements and I don't know where to put this either and maybe you already covered it is the. The inability of folks to like the issuers or revocation manager to determine when was the last time they updated like if they have to call home. Then they can't determine whether they last called home like a year ago or just a month ago or yesterday. Because that was one of the requirements we had an Alasaur was to was to solve that. Yeah, I wanted to check to the Alasaur update protocol does that mean that the revocation manager doesn't know what index they're updating. That's right. They do not. Okay. And even if they how did they not know. How did they not know the last time updated. I thought they basically that was what you did you call back and said the last time I updated was now when the update me. The holder knows the holder knows but the revocation manager doesn't. That was the whole idea behind Alasaur was to fix that problem. Because, because one of the methods of tracking is that like you said earlier, when was the last time they updated or last time they phoned home, like, so Alasaur mitigates all of that. What does it do that. What do you what do you request when you call when you call to the revocation manager and Alasaur. In a nutshell, a little more complicated than this but in a nutshell basically I split my share, or my revocation ID into multiple secret shares, as many as I want say like, first time I could do five or 10 next time I could do seven of 20 it doesn't matter. And I contact vacation manager that many times that maybe it's all at the same time maybe it's different times it doesn't matter. And then I can I alone can obviously re aggregate those, but they're all anonymous so the revocation manager can't determine whether one request is the same user or a different user because they're all the same. I'm also resistant to like, let's say even if an attacker tries to request for something. Let's say he doesn't know my revocation ID, or maybe he does. He's going to he requests an update for it. Unless he had a valid witness at any point in time unless he unless he has one that response back is completely useless. And that is like a that when this is a signature. He never had the signature to begin with, but then his result is useless. So even if the bad guy asks for data, his result is useless. But, so the holder still says, Oh, I last updated on June 20. Yeah, well the holder, the holder, the holder will know that right the holder has to know when they last updated. Actually, they don't even care. They only care do I have a valid witness for what the, can I present a proof that's valid for what the verifier wants. Okay. I'm saying just the holder specifically passed to the revocation manager June 20 because that was the last time they updated or they just say, No, they just say I need I need a version for this one. That's it. So they could they could say like, yeah, let's say each revocation ministry was tagged by a date. He could say yeah I need one that's valid as of June, July 20 or something like that. He could. Oh, but the cryptography doesn't matter the cryptography that the pro as as Nathan George always says the protocol does not betray you. That's the metadata that would. Yeah, yes. So if the revocation manager was just saying, here's my versions of the accumulator. And if someone said I just want the latest, then they don't know when they last updated. Or actually they don't even know when they last update they just know which one they're which version they're requesting. That's it. They learn nothing else. And then, and the way you do that is you split the key. If you don't split the key, do they know who you are. Well, that's it. Yeah, that's equivalent to spending the full thing. So yeah, they would see it. Well, actually it's a commitment so they really wouldn't you could say hey this is one of one. But the protocol would still hide it. My gosh, Oliver, what do you need. Okay. Sorry, my kids are asking me lots of questions. Any other questions or comments. Also, do we like, do you want to add like a section on calling home private, because I don't think calling home is entirely bad. In every case. Yes. And that's why I lost you there. I was just saying the perception could be that it's bad but I don't know like calling home isn't always bad but it could be a yellow flag if it's done wrong. It's a red flag if it's definitely done wrong. Exactly. Yeah. Yep. One of the ways evidently Jen digital did the link to validity verifiable credentials what they do is they provide a list of essentially revocation managers, and you can call it to any of them, and you basically pass an ID to them and then you get back to the non revocation that's linked to the credential you've got so it's got to use the same. It's got to be linked somehow to the to the credential but you could use different managers and the verifier has to know which are the trusted managers to get that that from. So, they've got a technique to do that. But that would be considered in the calling home. How, how safe is it how good is it. And is it every time or is it just once per any time the registry changes. Um, that would be important to call out because if it's like every time or just once, because like Alistair for example, the only time you have to call home is anytime the registry changes. Otherwise you never call home. Yeah, I would think it would depend on the verifier because the verifier doesn't know how often it change well. Yeah, the verifier wouldn't even know in that in that because there's no accumulator anything for it to collect it just got to know it just got to know if the if the if the credential is valid or not. They wouldn't know when it changes so they would do it more like they based on how recent it was how recently did you you get a a get a non revocation credential. Okay. The other topic I wanted to go through so we'll leave it for there I'm going to try to get that right up done. The other topic I wanted to do Mike was in in schema claim type. You've, you've listed a series of claim types I wonder if I wondered in doing that, whether the way that a piece of data is encoded is a useful claim type and in particular around dates. Do you have an ISO 860 date type or an ISO 860 date time type. The encoding of that could be into the integer date form or the Unix time form. That would be helpful. Do you see that as a useful. Is that what you were thinking schema claim types to be used for do you think that was useful. Mostly yeah so like when I said there's a number type you can obviously be more specific. Right. And you can create subsets so yeah obviously date date times day since 1900. I mean there's all sorts of different times or numbers that you can represent with that. Sure. Yes. So it would make sense to put it in the spec that since we're going to have claim types anyway, having these two would be particularly useful so that the data could be provided and I 60 but be useful for ZKPs for for predicates. That's right and then whether you want to support negative numbers or not. Right. Yeah. That's, that's built into what you've already got because you've got that zero centering. Correct, but if you don't need zero centering and like some things don't make sense like when did this happen. You know, within this century, for example. Yeah. Okay, well that was quick and easy. All right, I want to get that into that use. All right. So those are the topics I had for now as I say the next chunk of work I think for the, the two oh is to and and in our present general is to get a more formal definition of what the revocation requirements are suitable for photographers to use in evaluating schemes. And to try to get those schemes. Some evaluation done on those schemes to try to get contributions from some cryptographers on the various places on the various schemes where we want to use where needed. So I had any other comments questions. Discussion points. I wanted to maybe add to non creds to is what just as we're doing with revocation requirements, credential signature requirements, missed or not snark allowed or not, you know, basically, can you say the signature is missed approved, but the ZKP is not approved is mostly KPs. I don't know of any exception or that are missed approved. I think the path that we're most likely going down is that in addition to an an on credit signature you can put a nest signature on it but you lose all of the capabilities. A proof can still be be created about the about the credential but the an on credits capabilities go away essentially. All right. So that's it for today's meeting. Thanks all for attending. We'll be back in a couple of weeks with some new topics go over and hopefully some new get to some documents. Sounds good. Thanks. Thanks.


In this module, we will talk about something which is called as the validation. If you recall in the prior module, I very very briefly gave you an introduction about JavaScript and I told you that JavaScript is used for client-side validation, so this module will give a brief overview and some of the pitfalls which the program has fallen to because of JavaScript validation. So it is very useful. Now what the JavaScript does is that it tries to ensure, it ensures, tries to ensure, cannot guarantee, it tries to ensure that the data which is filled into the form is as, is correct. Not cementically correct, but it is correct as per the requirement, right. Now what was happening before, actually JavaScript is in use for quite a while for the purpose of form validation, but before JavaScript was there, there were the browsers and in the browsers, there were forms, text boxes, radio button, check boxes and the users entered the data in the form and the browser transferred that data in the HTML page to the web server and the web server checked what were the contents in this form and the contents were correct or not, right. That is called as the server-side validation, right. Though the checking is taking place at the, at the database server, it could be the application server also but usually it's a database server, right. And in the client-side validation, we use the JavaScript to check the correctness at the client which is the browser, okay. So let me give you one example over here. So you start in and there's a page and on that page, there is a alert box and the box is asking something from you, okay, asking you to give the name, right, asking to give the name. Now if you type numerics over here or if you don't type anything and you just submit this Q repress this button over here, okay, then there are two options. One is that you give something which is correct, which is here or you give something which is incorrect, which is here, okay. So it will say that a name is required which is shown by this red circle over here, right. So this is the validation. So asking and when the name was confirmed is generated the hello message and I click on this okay and I move on to the next page or I move on to the next task or whatever is required in the next site. Now the thing is that the JavaScript as I said that people have been using in for validating with JavaScript, validating with jQuery also. Now in this course, we will be using JavaScript for the purpose of validation, not jQuery. And remember that when the form is filled, you type something in the form, okay, then there are different commands for JavaScript to read the contents of that that it could be a text box, it could be a radio button for the case of radio buttons, there is a grouping. So they are logically grouped together, they have the same label also because only one value of the radio button is selected at a time is considered at a time as opposed to check boxes where you can have multiple values. I believe you understand this, right or not. Now, this is one thing over here that we can work with these boxes and radio buttons also, which I will be talking about over here is the hacking of the JavaScript validation, hacking of the JavaScript validation. Now if you recall in the prior module, I spoke about the dollar underscore get and dollar underscore post also. What they are doing is that they are passing the commands to the server. And those and if I can circumvent this, if I can circumvent this, then I can be doing things which I am not supposed to do, right or not. Now before I go into more detail, one point is to be remembered is that JavaScript is running on the browser, on my browser, I am the client. I have the option of turning off the JavaScript, right, and I can do it on purpose or I can do or that person who has turned off the JavaScript may have malicious intents, okay, may want to run something on the database server, okay, through the web server without validating on the client end. There are many, many programmers, okay, who kind of boast and they say, we are fine, we are safe. Why? Because we have done client side validation in the JavaScript. But remember, remember that anybody can turn off the JavaScript and that validation is no use. Let me go into more details. Hacking JavaScript validation, what, what is going to happen? Say, I give you one, one example over here that if I turn off the JavaScript, what's going to happen? Say, for example, I submit the data and there is a range of numbers which I am allowed to submit, say between one and three, right? And based upon the data which I submit and order is generated. If I turn on the JavaScript, this is fine. It will check. But if I turn off the JavaScript, then I can enter negative numbers also that will confuse the server or I can enter data more than three and that data will be passed to the server database server and it will make a wrong order. You see, you can play with JavaScript.


New assistive voting and precinct tabulating equipment will be in use in all Crow and County precincts for the state's primary election next Tuesday. The image cast evolution system provides an assistive voting capability which will continue to offer all voters the opportunity to vote privately and independently regardless of disability. So basically the voters are going to still be able to mark their ballot like they traditionally would with a paper and pencil. All voters will get the same ballot regardless of what type of voting they are choosing to do whether it's the traditional pen and paper method or if they choose to use the assistive voting session. If they choose to use the assisted session basically they will have the opportunity to navigate through their ballot with a handheld device also listening to the audio version as it's being read to them. Their ballot will be marked utilizing the machine and their ballot will then be placed back into the tabulator to be counted with all other ballot. A demonstration model of the image cast evolution is available for public inspection at the Crow and County elections office at the courthouse from 8 a.m. until 5 p.m. Monday through Friday.


A few days ago, we received some very exciting news about the long talked about Project Madrid for Busch Gardens Williamsburg in 2020. Let's look at this and find out what we have going on. You guys have probably all heard what Project Madrid is at this point. From what I can gather, it's been talked about since about 2017. So this project has been in the works first quite some time now and it's certainly shaping up to be something big and something very exciting for Busch Gardens Williamsburg. On February 8th, BGWFans.com posted this great article with a lot of information that they received from permits of sorts that Busch Gardens filed and there is a lot of stuff we still don't know and I want to stress that a little bit here. There's a lot that we don't know yet and we don't know the exact elements of this coaster but there's a lot that we can infer from the information that we do have as well. These documents here that BGWFans posted, this confirms what everybody knew was going to be coming in 2020. It's going to be a huge new roller coaster. It's going to be in the Festa Italia section of the park and it looks like it's going to be sort of like an add-on plaza to that area and it's not a new area in and of itself. But getting on to the coaster, we have an overhead view of what the layout is going to look like essentially. Basically this is showing where the footers are going to be going and we don't know exactly what the elements are going to be. We can only guess at this point but it appears that this is most likely going to be an Intamin project and something very interesting is it looks like this is going to utilize the very fast switch track technology that Intamin has developed and is going to be putting on park asterix 2021 launch coaster and this is going to be a shuttle coaster so it's going to utilize that switch track and have forwards and backwards launches to get the ride through the whole course. Looking at this overhead layout, we have the station and then it looks like the train is going to depart the station, make a 90 degree turn to the left, go through a sort of twisted S-curve type thing and then it's going to hit what looks like is the first launch. It looks pretty short, this is probably going to be a slower launch and it looks like this is basically just going to be used to build up some momentum to turn the train around and go through some sort of element. Could be like a helix or something like that and then it looks like it's going to go through another little S-curve type thing and then it's going to hit this section right here that appears to be the switch track and then it will hit a forwards launch and then it's not going to go all the way up whatever this element is. A lot of people seem to think this will be a top hat here. It's going to go backwards. The switch track will have moved and the train will go backwards into a massive vertical spike then it's going to fall down from that spike. It's going to hit another launch, take you all the way over that element which like I said many seem to think will be a top hat and then it's going to hit the max speed and the train is going to traverse a lot of wide sweeping turns it looks like. It's going to start by turning 90 degrees to the right and then just go through this massive turn over the river and then it's going to take us basically back around to the station. But looking at this layout it really doesn't look like to me that this is going to have any inversions at all just based on the nature of the layout and the way the footers move and also thinking about it too something that would kind of support this theory in my eyes is that Busch Gardens Williamsburg already has several coasters that focus on inversions Loch Ness Monster, Griffin, Elfin Geist, Tempesto, so you know that's four coasters that focus on inversions just an interesting point there. It looks like there's going to be a lot of wide sweeping turns suggesting that this coaster is going to be traveling at very high speeds which isn't really a surprise either. This is going to be a huge ride. Whether it's a giga or not remains to be seen. According to documents proposed in the past by Busch Gardens Williamsburg this coaster could in fact reach heights of up to 315 feet tall and I'm thinking that the vertical spike could lead to that 315 foot height and drop but what doesn't make sense at the same time is some leaks that were made several months back by SeaWorld Entertainment and this coaster was listed as having a top speed of 76 miles per hour so there's you know some contradicting things here like I said we don't know everything yet maybe that 76 miles per hour is just a launch speed and it's not the top speed of the ride and it has been pointed out in the past if anybody knows where exactly this came from let me know in the comments but apparently the ride is going to have its largest drop and reach its top speed going over that river so it's going to be pretty interesting to see how this all turns out whatever is coming down the line this is certainly going to be very exciting especially for coaster enthusiasts and I'm hoping to make it out to Busch Gardens Williamsburg in the year 2020 I was thinking about possibly trying to make it this year I really don't think that's going to happen but I definitely want to try to get out there next year especially with this addition do you guys think this is going to be a giga coaster and any ideas for certain elements that may be coming in this layout or what would you like to see this is going to be a really big and very exciting looking shuttle coaster unlike anything we've seen in the United States or anywhere really at this point another really interesting thing is if Intamin does manufacture this ride I mean Intamin has not been working in the United States very much at all due to all of their reliability issues parks are just tired of putting all of this time and investing tons of money into these huge rides that are just down all the time and we've seen a large shift in the industry away from Intamin with the Harry Potter coaster opening this year and then Project Madrid here if it is in fact manufactured by Intamin could we be seeing a sort of resurgence coming within the next few years it would certainly be very exciting as despite the unreliability of Intamin's rides they certainly do push boundaries and make really phenomenal rides so I would definitely love to see Intamin you know giving another opportunity in the United States and you know see how it pans out thanks for watching this video everybody leave your thoughts in the comments below about what you think Project Madrid could be this has been a long time in the works like I said and we're finally getting most likely pretty close to finding out a lot more official details stay tuned if you want more content on theme parks and roller coasters make sure you subscribe I love hearing from you guys I try to read every single comment thanks to all of my new subscribers my channel is really starting to grow a lot and I really appreciate that so thanks for sticking around and watching the videos and I will see you all next time this is Coaster Daddy bye


Are you an every-way woman? Every-way woman is doing everything we can to make sure that we can reach you at home, on your phone, or across the world. Stay with us and continue with the movement. Welcome back to Every-Way Woman. So we are taking the conversation beyond the show to the movement. Tell me about this platform, Yonda. Well, the movement is just an extension of the show. It's things that we cannot get to, plus it gives us an opportunity to reach women around the world. Now, Madison and I, when we was first talking about the show, we first did a segment. We wanted to test this blender. Magic Bullet. Magic Bullet Blender. It's been around forever. Yes, it's better now. Yes, it's better now. And we pulled it out, we pulled out some recipes, and we made things that it gave us to make. Yes. And it started smoking. Yeah. So that's what the movement is about, for like, we are testing products. And our like, I remember Madison was like, we should really test these magazine, fitness, you know, workout programs and see if they actually work. Or recipes, 15 minute deals. When you go to the store and you want to buy something, and like, there's 10 different lemon poppy seed muffins on the table. Which one's the best? Right, which one's the best? Do you spend $2.50 on one box and the 99 cents on the other?  And ladies and gentlemen, you can get more information on the movement, of course. The beauty products. Yes. I want to know which ones work. I, in fact, I'll put one eye cream on one eye for two weeks and one on the other.  Oh, absolutely. That's incredible.  But yeah, I'm so serious because I've really invested in the discovery of, you know, searching for the truth behind these articles with these products. And we really want to share that with our audience. Yes, because how do we make choices? How do we make smart choices unless you actually try it? And what we've learned, Yolanda and I learned over time, is that some products work really well with one type of skin. I think it's good. And it doesn't work well with another.  Well, yes, I think it's good for being on the web because, I mean, there's so many, everybody goes to the web for everything, you know? And not everyone watches television. They use the, no. The other thing is, too, is I might go to the web, but I don't have time to go to the web and look at, you know, 12 different sites. But we can test it for you. But we can test everything and all of that information we want to have in one place. And not just test and products. Do it yourself. You know, quick fitness tip, quick money tips, things like that. We'll follow up conversations. You know, let's talk to the guests behind the scenes. Let's talk to them after the interview. Right, because the interview faces sometimes different from who they are off camera. Exactly. And sometimes it can be more interesting. Is there going to be edits? Yes. And also, believe it or not, we get chance to talk entertainment because, you know, even though we don't celebrate celebrities on this show, you know, people do like celebrities. So it gives us a little bit of gossip. We like to gossip. We like to gossip as well. Exactly. So it gives us a chance and opportunity to gossip. But I just like the opportunity. Always in a positive way. We never trash. And we do. We have a large audience outside our area. We have a lot of women that reach out to us from around the world. Right, China. Yeah, so it's great. We're in there. Love you, China. We want you to embrace the show. And we're really excited to go beyond just your living rooms to your computer screens, your iPhones. Check us out at everywaywoman.com. Are you an everyway woman? Woman gives back to the community. Go to everywaywoman.com to find out how you can match our donations of undergarments for needy kids. Thanks for getting to know everyway woman.


Let's take a look at what is perhaps one of the most misunderstood concepts in mathematical modeling, which is the number line. And this is a way of representing the integers. And one problem is that while it can be a very useful model, it's very, very, very easy to misunderstand if you don't know what it actually represents. So the number line itself is based on the following ideas. First of all, any cardinality can be represented by a set of units. This goes back to the idea that when we talk about cardinality, when we talk about the number of objects, we refer to some particular property of a set. So the idea is that any cardinality we can think of as corresponding to a set of units. And again, the set itself, the elements of the set, don't have an order. But we can imagine our own innate sense of orderliness, we can imagine that we might want to put the units down in some sort of orderly and neat arrangement. And when we use the number line in practice, what we do is we take our set of units, we put them down in some sort of nice order, and then we identify some place, our origin, as our starting point, and then we put down our set of units. Well, let's take a look at that. So let's draw a number line representation for three. So to draw our number line representation, we need to specify some sort of origin. So I'll put a mark down. I'll say, here's where I want to start. I want to start there. And I want to select what I'm going to use as a unit. And so maybe I'll use a little bar there as my unit. And now I want to form a set with my cardinality that I'm trying to form. So here I want a set with cardinality three. So I'm going to form a set that has cardinality three, and it may look something like that. So again, the idea here is that the set elements don't really have an ordering to them, and I can put them any way that I want to. And in this particular case, I want to arrange them in this nice, linear fashion there. So there's my set with cardinality three.  Now because we read from left to right, we might think about this as our starting point. So I want to put the starting point right at the origin. So I'm going to move that set there through the magic of CGI animation. There it is. And there is my number line representation of three. And to make life a little bit easier, what I should do is I should mark that end point and indicate that this end point here represents the number three. And here's where the confusion over the meaning of the number line arises. The important thing to realize here is that the mark indicates the end of the number. It indicates the end point of the set whose cardinality is three. Mark is not the number. When we talk about the point on the number line that corresponds to a particular set, we might say, well, here is three, and that is a lie. We are lying when we say here, right here, is three. What we really mean is, here is the end of the set that represents three. Three is not this point, three is this entire set. And that's the thing to keep in mind when we're working with the number line. Well, let's take a different example. Let's draw a number line representation for the number zero. So as before, we want to decide on where our origin is going to be. So I'll throw down a mark there, figure out what our units look like. So there's my unit. And now I want to form a set with a desired cardinality. And again, through the magic of CGI animation, we'll produce that set. There it is, right here. You see that set? Not this. That's not part of the set. The set is right here. There is our set with cardinality zero. Again, through the magic of CGI animation, I'll move this set with cardinality zero to the origin. There it is. And again, I want to make one final change, one final notation here. I'm going to mark the endpoint of the set with the number. So see my set here? There it is. Begins here, ends at the same place. Now I want to mark the endpoint with the number zero. And so there's my number line representation for zero.


If you take a close look between the adductor magnus and the adductor brevis, we can see this nerve here. This is the operator nerve and we can clearly see it is giving numerous branches to the adductor compartment. It's giving branches to the adductor longus, magnus and brevis. It also gives branches to gracilis. Now we shall move to the inner aspect, pelvis.  This is the operator nerve in the pelvis. It rises from the adductor division of L2-3-4 and it passes through the operator canal and it enters into the thigh. And we can see when I'm exerting traction here, this nerve is moving here. So this is the operator nerve. Now we shall switch to a totally different topic altogether. We shall talk about the femoral artery and then the pulmonary artery. This is the femoral artery and this is the femoral vein. They were all enclosed in a sheath called the femoral sheath which is derived from the iliosuas fascia and the fascia transversalis of the abdomen and we have removed the sheath. The course of the femoral artery is from the mid-enguinal point to the adductor hiatus. So let's take a look at the mid-enguinal point. It is not the same as the midpoint of the inguinal ligament. This is the inguinal ligament that we have lifted up here. We can see that the femoral artery is coming in the sub-enguinal space and this space is referred to as the vascular compartment because the blood vessels are located here and it is the continuation of external iliac artery and the external iliac vein which we have lifted up here. So the mid-enguinal point is midpoint between the anterior superior iliac spine and the pubic symphysis. The midpoint of that and one inch below that is the location of the femoral artery. The femoral artery then descends down to the thigh and it becomes a pulmonary artery here. If we were to look on the medial side, we can see a tendular structure here. This is the adductor tendon and just later to that, an opening and my finger has gone into that opening. That is called the adductor hiatus and that places the location where the femoral artery becomes a pulmonary artery. So this, where my fingers are located, this is the course of the femoral artery and this is how we draw the surface marking of the femoral artery. Now let's take a look at the branches of the femoral artery. We can see this branch here. This is the superficial circumflex iliac artery which goes around the iliac bone. There should be a branch which runs like this towards the abdomen which we have removed. That is called the superficial epigastric. Finally, one branch runs towards the genitalia that is known as the external pudendal. So these are the three small branches and after that the femoral artery gives this huge branch and we can see that. This is the profunda femoris artery, the deep artery of the thigh. And we can see in certain situations the funda femoris is almost as big or even bigger than the main femoral artery. To continue, the femoral artery in the femoral triangle is located lateral to the femoral vein and then as it descends down, it enters the canal here and that canal is referred to as the adductor canal or the sub-sartorial canal. This adductor canal is bounded by the sartorials medially, the vastus medial is laterally and posteriorly it is bounded by the adductor longus and it is pitched over by a fascia called the sub-sartorial fascia which we have split open. And in the adductor canal, the relationship is like this. Anteriorly is this nerve here, this is the subvenus nerve. Middle is the femoral artery and posterior is the femoral vein. So these are the three structures which run through the adductor canal and now my finger has gone into the adductor canal and this adductor canal then ends in the hiatus which I mentioned earlier called the adductor hiatus where the femoral artery in the vein becomes the femoral artery in the vein. So this is the full course of the femoral artery. Now let's mention a few important clinical correlations. Femoral artery is a very useful root for various angiograms. It is usually palpated here just below the ligament against the superior ramus of the pubis and this is where we feel the femoral pulse and we can cannulate it and we can go through the external iliac artery, the common iliac artery, the abdominal aorta and we can do various angiograms in pheromiscentric, superior miscentric, celiac, renal angiogram and we can go right up to the coronary circulation and we can do coronary angiogram. This is a femoral-puppetial-tibial angiogram. We can use the femoral artery to demonstrate the tendency of the distal circulation also. So this is one important use of the femoral artery. We can use the femoral artery as a guide to do any puncture of the femoral vein for cardiac catheterization because we know that the femoral vein is located just below the femoral artery. So this is another important use of the femoral artery. Finally, when we want to do a knee surgery or any surgery on the anterior aspect of the thigh, it is sometimes necessary to give a femoral nerve block. So how to locate the femoral nerve? We use the position of the femoral artery as our guide and using this we know that the femoral nerve is located about an inch lateral to the femoral artery and that's how we give a femoral nerve block in the femoral triangle before any knee surgery. So therefore these are some clinical uses of the femoral artery in the thigh. Now we should show the continuation of the femoral artery to the popliteal artery in the popliteal fossa. For that we are using a separate cadaver which is prone. The popliteal artery in the femoral vein becomes the popliteal artery. We can see a circular opening here and we can see that the popliteal artery and the popliteal vein are disappearing. That is called the adductor hiatus and I'm going to put my finger inside and my finger has disappeared in the adductor hiatus. This adductor hiatus is formed by this tendon that we can see here. This is the adductor tendon which is the hamstring component of the adductor magnus which is attached to the adductor tubercle of the femur. That is the medial boundary and the lateral boundary of the adductor hiatus is the adductor component of the adductor magnus. So there's a small opening between the two and that is known as the adductor hiatus. This adductor hiatus forms the inferior limit of the adductor canal which we can see on the medial surface of the thigh from the anterior view and it is in this location that the femoral artery and the femoral vein become known as the popliteal artery and the popliteal vein. So from here onwards it is now the popliteal vein and the popliteal artery. This is one potential side of entrapment of the popliteal artery. So here the nerve, vein and artery form a very uniform relationship from lateral to medial and from superficial to deep. We have the nerve, vein, artery and we can see that clearly here. Now let's take a look at the branches of the popliteal artery here and I have lifted up the popliteal artery and we can see five branches one, two, this is the superior lateral superior medial genicular artery then we have the next branch. You can see this branch. This is the middle genicular artery. Further lower down we can see two more branches. One going laterally and one going medially. This is inferior lateral genicular and the inferior medial genicular. This is a popliteal angiogram to show some of the genicular arteries which you mentioned just now. So these five genicular arteries, apart from supplying the knee joint they form a genicular anastomosis which is reinforced by two arteries from above and one from below. One artery from above is this one. This is the descending genicular branch of the femoral artery and we can see in this case it is coming through the adductor hiatus and then there's a descending branch from the lateral circumflex femoral artery and from below we have anterior tibial recurrent artery. One artery from below and two arteries from above and five arteries inside the popliteal fursor, all of them form a genicular anastomosis. And this genicular anastomosis forms a very important collateral circulation in femoral, popliteal occlusion. The popliteal artery position can be felt when we are testing a patient for peripheral vascular disease. When we gently flex the knee, partially flex the knee and we can feel the pulsation of the popliteal artery against the posterior tibial condyne between the two heads of the gastrocnemius. That is one of the place where we can feel for popliteal artery pulsations. It should not be confused with an aneurysm of the popliteal artery which can sometimes occur where there will be swelling and it will show a different kind of pulsation from that of a normal popliteal artery. This popliteal artery, the popliteal vein, can be endured in posterior dislocation of the knee. This popliteal artery, it can also be obstructed by the medial head of the gastrocnemius and this is the medial head of the gastrocnemius which we have cut. The medial head of the gastrocnemius is larger than the lateral head and there is a very well defined classification called the popliteal artery entrapment syndrome by Love and Valen which describes six different types of obstruction of the popliteal artery, popliteal vein and functional obstruction. So that is another site of potential obstruction of the popliteal artery. And the third site of obstruction of the popliteal artery I shall show you when I come a little lower down. In order to show the continuation of the popliteal artery, we have sliced the origin of the medial head of the gastrocnemius and the lateral head of the gastrocnemius and we have reflected this up here. And under that we can see this muscle, this is the soleus muscle.