Hi, everyone, and welcome to the Zephyr Developer Summit. We're going to talk a little bit today about using flexible system design with RPCs and really embracing the distributed computing concepts in Zephyr. Origin of this talk really came from a real life experience that we've just experienced on Chrome OS. We have these two separate processors, the EC and the application processor, the AP, and we wanted to make better use of our resources that existed. And one of the things is that many of the application processors, both from Intel and AMD, for example, there are others, come with dedicated sensor cores. And what we wanted to do is move the sensor logic over. And we found that to be a little more difficult than we hoped for. There were dependencies that were just kind of built in linker problems, tests, and just overall prior design assumptions that were broken during this process. And the question we wanted to ask ourselves here is could we have done better? Could there have been things that we designed that would have made this an easier transition, made it more extensible? And the answer was yes, and we're going to talk about it here today. We're going to talk a little bit about what is a portable design. We're going to talk a little bit about what the solution that we came up with that is a feasible one, such as the Pigweed RPC and using portabuffers. And then we'll talk about how we can transition from headers to services, how our mindset can be kind of manipulated a little bit into this new paradigm in the embedded world. And then we'll actually build a very, very small and simple example. So starting off with the portable design, the kind of spoiler alert is they're really microservices, which is a very unique thing to come into the embedded world with this. In our example, we're going to be focusing on the motion sense task that the EC had. But there were other tasks that were identified as possible candidates for something like this. And so you can see here the power delivery task. And the real question here is, does it matter where these tasks actually live? This logic can be anywhere as long as the IO exists and the bus is laid out such that the information can flow. And if we wanted to break down the design, we can think of the proper design here as having the right abstraction layer at the right place. And once that's done and once the data channel is abstracted correctly, our services and our clients can be unchanged. When we move things, when we change things, they'll be compatible with possibly different versions of each other even. And that's where RPCs come in. They're originally designed in order to be extensible and not care about what the other end does. And Pigweed allows us to do this in the embedded space. And you might be asking at this point, what is Pigweed? Well, it's really a collection of tool. It's kind of like a Swiss Army knife of embedded applications. We're gonna be focusing on just two of these modules during this talk, but there's a lot more of them. And please look up on their web page at pigweed.dev and check out the other modules. We'll very briefly cover our PC concepts. There's a lot more information about these. And again, I highly recommend reading up on these. The three primary modes that you might see, there's a fourth one which combines client streaming and server streaming are laid out here. You can think of it as just out and back. Client streaming is when the request effectively might not have been computed all the way. And we might wanna send multiple of these requests before we get a response. And the server streaming is the opposite. We have one request and then we open a stream of data coming back in that would process it. So a simple service might look something like this. It's completely asynchronous. And in this case, we're gonna set a value of five to the service from the client, get back an okay. We're gonna get the value and we're gonna get back an okay with the data being five. And this it would be non-blocking on the client side. And the transport layer here is completely irrelevant. So one of the questions you might be asking is kind of when to use streams. We won't really dive into this too much but I did wanna touch on it because we brought it up. Pigweed for example uses server streams for logging. So the example is the client connects to the EC, the EC is the server. And when it does that, it basically sends the request of, hey, I'm interested in logs. And at that point, the service will start sending multiple logs as they come in and kind of never closing the connection. It's very similar to a socket connection being open. So the kind of high level theme is basically whenever data is generated with some latency where we don't know how much data. It's not just a simple repeated field of message. So setting up Pigweed into your West Dot YAML is as simple as adding the Pigweed repo. It's already fully compatible with Zephyr. We are making very active changes. So it's recommended to kind of sync frequently and bear with us as we tweak K configs and things like that. When you wanna set it up, the first thing you'll need to do is enable C++. Most of the modules in Pigweed require C++ 14. In this sample, we are enabled 17 just because it encompasses all the modules and we don't have to tweak it at that point. The next thing is find your Pigweed module and then enable whatever libraries out of Pigweed that you're interested in. We have in this example, a couple of them listed alphabetically cert based for 64 and so on and so forth. So let's visualize the data flow of the RPC, right? The first thing that happens is the application sends the request to a client. The client basically injects these IDs of the method and the service and passes that over to the actual RPC client, which is a router in a sense. It adds this routing header over to the channel. Sorry, serializes the RPC into a wire format. And then finally, the channel output puts it into the right frame. Some examples of this would be, there's a HDLC channel output in order to write HDLC frames. There is another one that we're gonna talk about here that I wrote specifically for this talk in order to optimize the wire format when there's no actual wire. We're writing to just share in memory. So moving away from headers, right? It might seem like a bit of a stretch. And the real reason here is that protobufers give us a lot of flexibility. They make it easy to test our code because we can also mock our clients or services. We can even use different languages, right? Protobufs can be compiled to TypeScript, to JavaScript, to Python, sorry, and to Java itself. This makes our test environment very flexible and might allow us to run scenarios that we would not otherwise be possible. They're also much easier to extend if we wanna support different versions of clients and services and have them still be able to talk to each other without having to update both at the same time. Having the proto file itself really forces us to think about these API boundaries, right? You can't just expose a global variable through an X-turn in a proto file. So this makes our interaction confined, which later contributes to the ability of migrating the code from one code base to another or one core to another. So, sorry. The protos themselves are also designed to be flexible and extensible. This is much better, basically, than a plain header where you might later on have to think that you realize that you need to add a version field or, sorry, deprecate another field and so on and so forth. So if we were to write a simple set and get value in a header, it might look something like this. We're gonna go ahead and include these empty structs here for the response and the request set value and get value just in order to keep things a little more aligned with the protos, but they're not technically necessary. The function calls here would pass in a request and have a callback in order to make this an asynchronous event. Well, the problem with that is, right, they're kind of hard to maintain. If we add new arguments, we have to make sure both ends are compatible with each other. The API is still missing a lot of features, right? It doesn't take into account the wire format, the transport, how threading is done. We have a callback that's passed in, but we don't have any control of what thread that callback is gonna be called on and it has zero mechanisms for canceling requests. And finally, mocking it is kind of up to you at that point when you wanna test it. So for the example, we're gonna replicate that header in a proto. So the first thing we're gonna need is the request for setting the value and we're gonna use an int32 value here from the proto3 syntax. And we don't need a return value, so we'll just have an empty message that will keep things extensible if we ever want to return maybe the old value in there. GetValue doesn't pass anything for the request and gets back the value right there. Finally, the service is to RPC calls right there for setValue and getValue. When we wanna go and implement it, we are gonna implement this service. We're gonna call it a cache. Seems fairly accurate for setting a value and getting a value. And our header is gonna simply have this. This is our private field down here value and that is the cached value that we're having. The dot c, I'm sorry, the dot cpp implementation is gonna simply accept the request and the response right there and it's gonna cache the value right there, the private number value there and return it on the getValue. So the final step is abstracting away the channel output which is kind of the serializing format. And this usually uses the PWStream modules writer which is another abstraction layer for how to actually put the bytes onto the wire. And it allows us to switch how the service communicates with the client. So the service implementation doesn't actually change. We just attach a different channel output to it, if you will. And some examples I mentioned before is the HDLC one that has the RPC channel output. And then we have a custom one that we're gonna talk about a simple channel output. And the reason is really just to show performance that this is a feasible thing to do even to communicate within threads on the same core. And both of them use the same writer and the example to write to a ring buffer when they're talking within the same core between threads. So what we have here is HDLC we already covered for local writes though between threads, the channel output, the simple channel output is extremely simplistic. It uses four bytes a UN32 which tells us the frame size followed by N number of bytes that are gonna follow. And we have just a wrapping struct that is gonna contain everything. So that all gets written and read from a ring buffer that we wrote it is transactional meaning we can write multiple small packets before releasing that increases the performance a little bit. And it just uses a plain Zephyr ring buffer and the mutics with a con bar in order to signal that between the threads. The main question that might be coming up now is what is the actual performance and how the tests were set up? What we've done is create two different threads. One is the responsible communication between the client and the service. The other is the other way around the service response to the client. On the main thread, we wanted to run 1,000 iterations of setting the data, waiting for the response, getting the data and then waiting for the response and then asserting that it was correct. The comparison here is that we used a control which is going to just write to a ring buffer from one thread and then have a fake service that reads from that ring buffer and it uses a plain struct with the data that was passed between them and then write back to the client and then basically call the getter and do the same thing. The experiment was to use PWRPC in order to do this with the same thing using RPCs and our implementation of a service. We still write to a ring buffer, we still have the transactional properties but it's all done through Pigweed's RPC pipeline that we showed earlier. And one of the things to consider when we see the numbers next is the control is much of an oversimplification that has no priority control. There's a lot of features missing that you might want in a more mature product and some of the RPC, PW, the Pigweed RPC code paths were identified as bottlenecks and they're still being optimized, it's not finished yet. But the upside is if you do choose to use this you'll get these optimizations as development continues on Pigweed. So the control took us 65 and a half million nanoseconds roughly 33 microseconds per call and the experiment took us 116 microseconds per call. This is quite a bit of a penalty I know but you get free upgrades as it comes and really these should be fairly infrequent calls. The next thing is looking at optimization options and we looked at a call graph and we profiled this. They showed us several points, very high value points of improvement that are currently being explored. One is the RPC header that it wraps around the data that's being sent, just serializing the header costs us 21% of that penalty. The additional thing is for the unary RPC call we have a destructor that closes basically the call's connection and technically we shouldn't need it or at least it can be minimized and that uses 38% of the duration. So if we were to optimize those two that would bring the overall RPC cost much closer to 45% or 14 microseconds per call which I think at that point is very much doable and agreeable. So if you have any questions, please reach out to me. I'm available through Discord, through email or just tag me on GitHub if you have any issues with this. I will dive in next. There are a couple of appendix slides I'm gonna show them that show the call graph that we've generated. So this is the call graph for the client to service handler and kind of zoomed in you can see here the benchmark started up at the top here the green one and then we call here process we create the span and it keeps diving down basically into these separate calls. Some of the interesting points to optimize that we talked about earlier is this is the call graph for processing the header which includes the PIGWeek serializer right there and this is the destructor call graph that we talked about for the optimization. I hope you enjoyed the talk. Thank you very much.


Hey guys, Realistic Gaming here, welcome back to another video. Today we're gonna be doing some Roblox scary stories, and happy Friday to everybody. Let's go! Yeet! And we're here with GodBag's Huda Feynand, Jack Studio's last drawing, Skyland 300, and that's it, a tweeter. Say hi buddy. There you go man. Alright you guys, so let's go into this scary story here called the Golden Hour. Oh god, that sounds pretty interesting man. Okay, just step back onto the gray track when you are ready. Does it mean here? Okay, so off we go into the scary story. Oh, this is new. We've never seen anything like this.  Alright, this seems pretty awesome already. There was once a little girl named Elizabeth who was born with only half of her arm. Half of her left arm. Oh my god, so I guess this is Elizabeth. Hey Elizabeth, why me? Oh yeah, you can only see she only has her right arm, she's missing her left arm man.  Oh, she does look pretty sweet. Oh poor Elizabeth. Alright, so let's go see what happens with the golden arm. Elizabeth grew up to be a very sub-art and beautiful woman. Oh my god, look at her. Alright, so let's go check it out. But none of the men in town asked for marriage. Oh, that's so sad, look at the other girls are getting asked like, the other guys are proposing to them and Elizabeth's here by herself. I guess it's because she only has one arm but that's pretty messed up man. Okay, Elizabeth's heart was broken. She thought she would never find love. Oh, she's all sad next to the fireplace.  Okay, until one day she met a wealthy man named Colin. They fell in love immediately. Oh, that's good. Okay, so she found somebody that she fell in love with but I don't know, it's kind of fishy, they just kind of met it and they fell in love immediately. That's kind of sketchy man. Colin asked Elizabeth to marry him and she said yes.  No, he's saying no, okay, don't do it Elizabeth. Oh god, so it seems like Elizabeth's about to get married man. The wedding was like a fairy tale. No one had ever seen such a beautiful day but those look pretty nice up there man. You go girl. Alright, so let's see what happens next. But instead of giving Elizabeth the ring, he gave her a golden arm. Oh my god, so this guy gave her an arm since she didn't have a right arm. He gave her like a right golden arm as you guys see here. He handed it over to Elizabeth. Okay, so this is pretty weird. Let's go see what's next. The golden arm fit perfectly. Now Elizabeth had a complete left arm and it was beautiful. Oh god. Alright, so off we go. So now she has both of her arms. Elizabeth and Colin were as happy as could be. Now so they're both home happy eating dinner at the table. Oh my god, look at her arm. I mean it looks like a legit arm but it's just golden. So you could say she's like a cyborg I guess. Okay, what's up clap force? Okay, but then tragedy struck. Elizabeth felt terribly ill. Oh no, Elizabeth got sick. It might have been the arm or something, man. Oh god. Okay, so they took it off right here. Oh no, let's see what's going on with Elizabeth. Okay, Elizabeth changed completely. She became cruel and yelled at Colin all of a sudden. Oh god. So it seems like she's getting possessed by this arm or something. I mean it has to be the arm because she wasn't like this before she had it.  She looks crazy. Okay, how's she ever spoke about with her golden arm? Colin knew she loved the arm more than she loved him.  I told you guys it's that arm. It's evil. Oh god, okay. She made him promise that when she died he would bury her with her golden arm. Of course he promised while that tweet of him. But I don't know about Elizabeth.  Then Elizabeth died and Colin buried her with her golden arm just as he had promised. Oh no, rest in peace to Elizabeth, man. So she did bury her with the golden arm as she asked. So shout out to Colin, man. He's a good husband. He's a good person at heart. But Colin's battle continued. His factory burned down and his crops died. He was now poor. Oh no. So as you guys knew Colin was rich when Elizabeth had first met him. But now like his factory burned down and he's poor now. So it seems like maybe he's cursed. It seems like he's a curse or something, man. I see them coming from a mile away. Okay, the banks said that they were taking his land and his house. He had to do something. Oh no, I know what he's going to do. He's going to sell the golden arm watch. I see it coming, man. I mean, if he has to do it again, his wealth back. I would so be decided that he would borrow Elizabeth's golden arm. He dug her up and borrowed the arm. Oh god, I even called it. Oh, I told you guys. But I feel like that's a bad move, Colin. Oh no, let's go check out what happens. Okay, he sold the golden arm and paid the banks. The goldsmith melted down the arm and made different things with the gold. Oh god, okay. So here he is at the bank. He's paying off his debt with the bank so they won't take his factory. I mean, that's kind of like the right thing. I would do the same thing, Colin. Don't try it, man. And here's a blacksmith melting the golden arm. What did he make? Like a golden helmet? I don't know. It looked pretty cool, though. All right, so let's see. That night Colin couldn't sleep. He kept hearing Elizabeth's voice in the wind. Oh no, Elizabeth is back to haunt him since he did sell the golden arm. Oh my god, no, Colin. Well, here comes the crazy part. Her voice seemed to be saying, where's my golden arm? The voice kept getting closer and closer. Oh no, so she's really haunting him for the golden arm. Since she was like kind of obsessed with it. It was pretty weird, man. Okay, the voice was just outside the door now. Colin, where's my golden arm? She demanded angrily. Oh gosh. So now she's right outside the door. Oh god, dude, she's right here. Boom, the door flew open and there she was. Elizabeth, she was pale and red eyes glowing. Oh my god, she looks pretty scary. I'm not going to lie. That looks pretty terrifying, man. So it seemed like she's back to haunt her husband for selling the golden arm. Where's my golden arm? She demanded Colin explain that he borrowed her arm. Oh no, poor Colin. He must be terrified, man. He promised her that he'd make her a new one. I don't want a new one. I want mine. She screamed. She screeched at him. Oh god, okay. Hey, you got to relax because he did give it to you to begin with. So we have no right, man. You have to relax, Elizabeth. What is going on with you? He told that the goldsmith had melted the arm and made different things with it. So he got to get it back where it seems like my boy Colin is doomed right here.  Elizabeth shrieked loudly with anger as she flew over to Colin, grabbed him and dragged him back to her grave.  She is insane. Oh no, poor Colin. What's going on here? No one ever heard from her son Colin again. Oh god. They got poor Colin, man. Wait, so is he like in the underworld or something? Oh no, he was a good guy though. How could Elizabeth do such a thing? Okay, they say Elizabeth is still roaming the earth, looking for every drop of her golden arm. Oh god. Oh, like Elizabeth's haunting the people because he has gold made from her golden arm. He has a golden chain. It seems like she's collecting all the gold from her arm that was like distributed around the whole earth. She's insane, man. Okay, and as we all know, gold is in many different things, like iPhones, tablets, computers, and iPads. That is true. Oh god. Wait, so where's Elizabeth? She's not here. I guess they're just showing like the stuff that the gold is in. Who knows? Maybe some of Elizabeth's gold is in your computer folder iPad. Oh god, hopefully it's not because she would haunt us. I did not want to mess with that girl. You never know, but you might find out. Oh god. It seems like those people are going to find out right now. Oh no. What is that chain? Oh wow, it's Elizabeth and her golden arm. Oh wow. Is that it? Okay, that's the end of the story. Please exit the ride. I hope you enjoyed the story. More to come soon. Vision Psych 7. Oh my god. Wow, this is pretty cool, man. I've never seen a scary story like this. Wow, this is different compared to the other ones. Wait, oh, back to the... Okay, that's pretty cool. We like faded into the lobby. So it seems like Stick Man is coming soon. I can't wait to see that story. I know it's going to be awesome. Like golden arm was. What about over here? Hey, move out of the way, man. To be announced coming soon. Oh no. Why me? This is pretty cool. Shout out to what was the name? Vision Psych 7. There you go. All right, you guys. Well, thank you guys for watching. Thank you guys for amazing support. If you guys enjoyed the video, make sure to slap the like button. If you're new to the channel, make sure to subscribe and hit that notification bell. And I will see you guys in the next one. Bye.


So today guys we take a look at a brand new legendary called The Mysterians. Today I will review the weapon and give you guys my thoughts on it and also showcase the one very spot you can farm for this thing.  So The Mysterians is a new pistol belonging to the Redarth pistol family. So what's that now? 103? We also have another one within this DLC so there's only four in total. There's this, there's the Infinity pistol, the Magnificent and the fourth which I will cover soon. Well I will straight up state, this is definitely the best in its family so far, not taken into account a fourth by the way. Those are like peasants to this kink for sure in terms of what they offer besides farming money barrels. So all these Mysterians is a very very good weapon if I'm honest and actually using it for a while now I've drawn to really enjoy it. Definitely one of the better ones from this DLC I've used so far. So it shoots what are basically rockets that explode on impact but when you shoot them they do this kind of swirling motion and if you ain't close enough to a target hitting them in the face may be a little difficult. Now it has two firing modes, a standard full auto and a double barrel. With full auto we see gradually speeds up in terms of fire rate the longer you shoot it. Double barrel on the other hand consumes two ammo per shot but that ultimate fire rate is already there. Now obviously double barrel makes it way harder to handle and switch between the two you feel a massive difference in that handling. Now for the purposes of this video I did roll that big head mould and even still for the most part I was having a little trouble trying to keep all shots hitting that head within that double barrel mould especially when you are moving around. Now it's down for how much ammo it does consume I mean yes it's pretty powerful and with the right setup to go alongside this it I feel will take on and many people will properly use it. Me personally I went the route on Zayn using the coppers and the fish lap grenade paired with a few points into duct tape mud and that drawn delivery was selected just so I never run out of ammo. But taking a different route when using this thing make sure you have ways to place that ammo back because before you know it you will run out of it. Now there are two times Zayn to this thing but also interestingly when you switch into double barrel moulds on that two times variant it seems as though it still only consumes two ammo per shot so on the two times it makes sense that you keep it within that double barrel mould for maximum DPS. Now the weapon as far as I know comes in radiation incendiary and trial also available with no element. I farmed for hours for this and never came across a shark or cruelty version. Not to say they don't exist I just haven't seen one yet. Now after spending days on this third DLC thanks to Gearbox allowing me to play early I think I can confirm this drops from one place on one place only as I've never had it outside of this boss. The boss is the quartermaster who is located upon the Hanna within the Blood Son canyon and location to him you will find at the end of the video which will be in a second. So this mysteryant the new Vladov pistol definitely the best of the three and in my opinion definitely worth you making the time to go farm and get this thing it isn't the best pistol in the game but I feel it will be a very useful weapon for certain builds out there. On screen now we can see the route to the quartermaster go get this thing guys. On that note we have come to the end of the video if you guys enjoyed it leaving a like really helps out if you're new around here want to see more boardlands be sure to subscribe and if you never want to miss a video or upload a canton of occasions I'm by hitting that bell button but guys thanks as always for stopping by hopefully you enjoyed the video and hopefully I will see you on that next. One.


Hello everybody, welcome to the hyper ledger healthcare special interest group meeting for December 21, 2022. Happy solstice day everybody. This meeting is recorded and will be shared on YouTube. So, please make sure that you are complying with the antitrust policy by the Linux foundation. You can find that here on this link in the show note are in the agenda notes which you can find. Publicly available as well. So, before getting started, there's a few people on the call. I just want to give them a second to see if there's any community announcements. If not, I'll just get started with the remainder of the agenda. Hello everyone, Pete Harris haven't been on this call for a while, but I will be probably more in the future, as I'm kind of getting back into the healthcare space involving AI and blockchain. So, looking forward again. Thanks Pete. Alright, so we could first I wanted to start off by saying, you know, first of all, thanks for joining and and thanks for taking time to listen in. What we typically do here is we go through some upcoming events that might be going on in the blockchain healthcare technology space, as well as go over some industry news and articles related to the industry. And some additional educational nuggets that we've we found over the last couple weeks. Now there's a lot of events going on next year. I'm not going to go ahead and click on each of them but as you can see here you have the digital health summit, which is going to be at the consumer electronic show or trade show so this is CES very big show. So, if you're attending, take a look at the digital health summit is happening there. The innovator MD global summit 2023. That's happening January 11 to the 13th. The world crypto conference in Zurich is happening January 13 through the 15th. These are London, which is going to be an interesting event in London actually, where people from the decentralized science community are going to come and speak about, you know what's happening and updates in that space as well. And there's also a hackathon a couple days before that on the 13th and 14th, I believe so check out their website if you're interested. And excuse me if I cough I'm going to I had a recently getting over a flu so February 15 17 the European blockchain convention is happening in Barcelona. That'll be a big event as well. Paris blockchain week will be March 20 to the 24th. Vive, which is a relatively newer healthcare conference is happening March 26 to the 29th as well. I think it's like, I don't know what year they're on but should be an exciting time as well lots of great speakers so Oracle health, etc. HIMS classic healthcare conference for IT technology healthcare management stuff. That's happening in Chicago April 17 2023 as well. This is 2023 a major blockchain event hosted by coin desk is happening in Austin next year in April, and then Bitcoin 2023. It's a famous conference for Bitcoiners in Miami happening May 18 to the 20th. And then there's later in the year September 2023 the con v2x global blockchain and healthcare 2023 happening in New Orleans as well. So, check out the links the sites if you have any questions, leave them in the YouTube or reach out to the organizers happy to help make any connections if you're interested as well. So, before we are now, you know, without any further ado, let's dive into some recent, you know, happenings here in the industry. So, two things from hyper ledger I wanted to share with everybody, just so that you're all aware. This is hyper ledger meeting. So hyper ledger so long was released. And it's a new an update to an existing application here with the Berlin release hyper ledger so long substantially improved its capability with many existing Ethereum dApps and concepts within the polka dot and Kusama ecosystem. So porting from Ethereum to a substrate parachain is now easier since the complier supports almost all language constructs as Ethereum Solidity 0.8. This release represents just the beginning of a series of upcoming achievements yet to unlock for the substrate compilation target. So some more information in here if you're developer. Definitely check this out if you're interested. Congrats to that team for this release. That's that's an interesting development, sort of bracing the polka dot world. Yeah, definitely. And the Kusama ecosystem too. Yeah, which is kind of all part of that. Interesting. Had no clue that was going to be happening. Yeah. So the hyper ledger announcement I wanted to share was that there are five new members who have joined the consortium or the foundation really, and they are energy web, the European Blockchain Association, how is instant integral ledger. Those are the five right there and they go into detail about who they are. So it's been interesting to see, you know, the number of members of this foundation continue to grow. Yeah, so if you're interested in learning more about that. And if you're interested in becoming a member as well. You know, either you can reach out to me or you can find more information on the website as well. I did find one of the things interesting in this article, hyper ledger foundation continue to add to its project landscape with the introduction of hyper ledger and on creds a widely used verifiable credential format. So, you know, I've heard and on credit before so should be interesting to see how, you know, that collaboration will unfold. And just to give you some numbers here in 2022 hyper ledger total code contributor community grew more than 18% with an average of almost 800 individuals, actively contributing in each month. Pretty significant for this still nascent industry. All right. Excuse me. So lots of things have happened since our last meeting, which was about a month ago. The future of NLP in health care. So, I'm sure many of you have heard of open ai's chat GP T AI system. Basically it's a natural language processing tool. And sort of like a chat bot, but that's much more effective and has a lot more capabilities. And you sound like you're talking to, you know, maybe a high school student, or even an undergrad to some degree. For some questions. So this article here, published December 10 by Jared dash of Eski basically talks about how this can be used in health care and talks about the many different applications. That has potential. So, you know, here he's asking the chat GP T how health care will, or how we will ever fix this broken health care system. And I can see the chat GP T saying it's difficult to predict the future, but I believe that with the right efforts, it is possible to improve the health care system and make it more effective and accessible for everyone. Great. That's great. So some specific examples that are mentioned here. One is patient care and delivery delivery research diagnostics and treatment. Clinical and non clinical workflows. So, and then it goes into more details about how that's possible, how that could do that. Yeah, I mean, I think this tool is really interesting. Open chat. I think the fact that they made this publicly available is really good too. It's not just like, you know, for people who could pay for it. A lot of issues with new technology are about how, you know, only some people can access it so increasing that accessibility is really, I think a good move by open AI. Um, yeah. Hey, Pat, wondering, Pete, wondering if you actually tried to use Chai GP T at all if you had any thoughts on it. I've not yet I plan to. Yeah, I've, you know, heard various people say it's great to it's awful. So I don't know. But sometimes over the holidays, I'll probably have a chat to it and see, see what happens. Sure. Yeah, one of the examples I saw online as well as somebody, a physician actually asking the chat GPT to write a letter to a patient's insurance company for a approval for a drug. So prior authorization. So it's kind of an interesting tool. Yeah, doctor sometime. Again, it's still pretty new. So I wouldn't use this in your day to day work, obviously. But the fact that this is here now and we're, you know, dealing with it is something to just consider because yeah, definitely worth knowing about all that stuff. Definitely. So the next article I have here is related to a discovery through an investigation. Many telehealth startups, yeah, actually sending sensitive information to big tech companies. So the markup did this and they found that out of the 50 telehealth websites that they tried out 49 were sharing health data with big tech companies like Google, Amazon, Facebook. So that's pretty significant amount. I did take a look at the list of. So here you can even see out of those 50 telehealth sites, 47 sites sent to Google. I also sent information to Facebook. 27 to being tick tock Snapchat Pinterest, LinkedIn and Twitter as well. Surprisingly, Twitter had the least amount shared but yeah, this is just another red flag being raised here that we need to be able to safeguard patients and consumers overall because I think there's still a lot of misunderstanding about how their data is being used. They did also say that one company that did not share data was Amazon clinic, and they talked about how maybe that's because they're still so new so there wasn't really much data to share. But, and they also did close. They're not really Amazon clinic is not right available anymore. But yeah, you can see the list of all companies here. It is but I want to mention a caveat here because I think it's. I thought it was interesting that they didn't include some of the major telehealth companies like doctors on demand is not listed and while it's not listed at all. What else is there. There's a bunch of telehealth companies that are larger and they have more footprint actually in the United States, but they're not listed here. They do specifically say that they try to go after not go after but they were targeting. So telehealth companies that were were specifically marketing, like, what is it, lifestyle drugs. So, right. So that's what, like, you know, row. Hems and hers. So, yeah, I mean there's a lot of good details articles well. It does seem deceptive cerebral cerebrals been prescribing a lot of drugs for ADHD, pretty liberally from what I understand. So I think that's why this investigation targeted those companies instead of the larger companies that are more urgent care type of, you know, patients. Yeah. Actually, they do a lot more than urgent care, but they're not just targeting specific types of individuals. It's broadly used and the many health systems use them so it's different than the consumer facing only telehealth applications. I mentioned this because I have worked at animal before and they do. When I was there they did a great job making sure that there weren't abusers of the program, meaning that they weren't people trying to game the system to get prescription drugs which is a really big deal in the telehealth industry so especially, you know, substance abuse disorders galore. So that's that. And I was thinking about ways blockchain or decentralized technology can mitigate this and I think the fact that, you know, patients here aren't owning their own data and the data is being owned and controlled basically by these companies and they're able to get away with laws because technically it mentions here how they're able to do this. Right so they emphasize that privacy regulations like health and for health insurance portability and accountability act HIPAA we're not built for telehealth. Right so there's a lot of ethical and moral gray areas that allow for the legal sharing of health related data. Right so there's a lot of ethical and moral gray areas from a former investigator of the US Department of Health and Human Services office for civil rights. Yeah, so I thought that was interesting wondering what you guys think leave a comment in the notes in the YouTube. Okay, next here is an article from coin desk about Apple and that this was an interesting opinion article about how Apple's new encryption policy is actually good for crypto. So it goes on to talk about here. You know, Apple made this announcement that their, their cloud I cloud storage service will now offer end to end encryption. And this is something that I think a lot of users have been asking for for a long time. So that means only a user with an authorized device will be able to access the contents of their cloud storage in much the same way only the holder of a private key can control a Bitcoin wallet. So the new feature will protect photos notes and other files for users who choose to activate it. And this says here email counter and contacts material are not included because they need to interact with multiple services, which makes sense. But this is definitely definitely in line with Apple's privacy leaning policies. And I think it's interesting to just see how the crypto industry will react to this in the future as well. Apple has some tweets reporting from Reuters claim that the FB had leaned on Apple not to enable this feature, which also makes a lot of sense. So you do have some government officials, or at least government departments not really happy about this. So I think, you know, we'll be watching to see how that plays out in the end. Well, not personally, but I know that Tim Cook thinks that privacy is very important. And the US government and Apple have always been in this sort of not battle but, you know, conflict in terms of privacy and data sharing. So we'll see how that turns out. I think it's personally a good thing for the industry and for humanity in general. So it says here hundreds of thousands of users are about to be introduced to private key management by the most respected name and computing. So from there crypto is just a hop and a skip away. So I think that's the takeaway here. Okay, next here is an article from fierce healthcare. It's about AWS and talks about their release or their launch of their new genomics data service for life sciences and healthcare companies. Amazon's in genetics now so this is a big deal I think, and the fact that they're probably doing it for a lot cheaper than everybody else is probably a big deal as well. So I'm curious to see how this plays out here it says more than 98% of medical records are now in digital form, and the digitization, digitalization and sharing of medical data is driving the demand for precise or precision medicine technologies. And it's obvious here that there's also been a steep decline in the cost of sequencing with a hundred thousand fold reduction in cost since the human genome, which was first sequence in 2001, reaching an all time low of approximately $200. That's amazing just in general as a technology. This is by far one of the most impressive things I think humans have done in the last 20 years or so. And I think we still haven't really felt the effects of this in the application of medicine yet. I mean if you go to your doctor now they're not going to typically give you a whole genome sequence test. Although it's relatively cheap. It's just not part of the protocol now but I think that is starting to slowly seep into the standards of care. And that's an exciting thing because I think it's going to reveal a lot about our ourselves. Here says AWS built Amazon omics to support large scale analysis and collaborative research without healthcare companies needing to worry about provisioning the underlying infrastructure. Customers can bring their own bioinformatics workflows and Amazon omics manages the infrastructure to run it according to AWS executives. So this further reduces undifferentiated heavy lifting enables customers to operate in a secure environment with built in access control logging and audit trails while still complying with HIPAA GDPR and other regulations. So yeah I'm curious to see how this will unfold. I don't think blockchain is used to at any part or any component of the stack but yeah so it'll be interesting to see if there's any privacy gaps or security gaps that are identified in the future with this new service. I hope there isn't but you know with any centralized system there's there's some risk there. Okay, so coin desk article about MetaMask which is one of the most popular browser wallets crypto wallets out there. There was a claim out there that MetaMask is privacy and settings were really not that great in terms of data sharing practices and there were concerns raised and then MetaMask responded here in a statement the company explained how and why it was sharing MetaMask user internet protocol information IP information with infura, which is the consensus made RPC remote procedure call service for reading and writing data to the Ethereum blockchain. So I change specifically a change in wording to the consensus user agreement last month revealed that MetaMask by default. Key here shared users transaction data with infura alongside their IP addresses. So, like I said this revelation sparked outrage in a vocal corner of the crypto community with some users worrying out loud about that their transaction data wasn't private, as they assumed. So, it's good to see that consensus and MetaMask are addressing this head on and what they said in the statement consensus clarified that it would only collect wallet and IP address information in connection with right requests, also known as transactions through infura as RPC endpoints is going to say we do not store wallet account address information when a MetaMask user makes a read request through infura, for example in order to check their account balances. So, yeah, I mean I think it's good to see that the voices of the crypto community were heard in this case. And it looks like MetaMask is working to address them. I haven't go too deep into this so if there are some caveats, share them in the comments. I'm curious to know about that. One more quote here we think this was overly cautious and we are not intending to scare anyone away from choosing their chosen provider the company adds. Yeah, so obviously it's still developing space but glad to see that there's some activity in the positive direction. All right, so next article or actually this is sort of like an announcement and there was a hackathon events. So, Partizia blockchain, which is relatively newer blockchain teamed up with the International Committee of the Red Cross, and presented a prototype to support victims of armed conflict. I thought this was interesting because what I had learned through watching some of the video here is that the International Committee of the Red Cross and the Red Cross, I believe, do not actually have to comply with many international laws related to privacy of data, because they are such a emergency group, they don't have to to comply with some of that, which is, I thought kind of interesting. But they also said that they want to be able to comply with and they want to be able to provide privacy in a way that is still efficient and fast and effective. Building a platform that maintains privacy is a bit more complex, but with blockchain they are saying that it might be easier to do. During the video I actually learned that a lot of the ways that these organizations like the Red Cross and other humanitarian efforts, the way that they share and provide money to people in need is through cash, like paper money, because that's the simplest way to do it, apparently. And that makes sense, like if you need to give people money who don't even have bank accounts in a war-ridden country, cash makes sense. The issue there is they can use it for anything, so I think the purpose of this is to try to ensure that the money that the humanitarian tokens or the Red Cross or other organizations go to is to make sure that it's being used not to, you know, fund terrorism, for example. So there's a lot of concerns about that. So being able to put on a blockchain in a way that still protects the privacy, but also ensures that it doesn't end up in the hands of nefarious actors, I think is an interesting thing. And, you know, this is a prototype still they're using Partizia, so check it out if you're interested. This event happened just last week, so pretty cool. All right. That's all I had for news and articles. I'm sure there's much more to share but this is what I pulled up. In terms of educational nuggets, there was one lengthy blog from the town butyric talking about what he's excited about in the sector in the industry, as well as an interesting breakdown of decentralization. And specifically how, you know, he differentiated between a decentralization for governance sake and decentralization for implementation sake. Something that we're all sort of interested in learning about is what is decentralization. So part of that learning includes understanding the nuances and different concepts behind decentralization. So really great article I'm not going to dive too deep into it right now.  This section, section four I thought was most interesting, talking about, you know, the distinction of decentralization for robustness and for efficiency. So if you want to dive deep into decentralization, definitely read this article. Again, decentralization for interoperability so and how that breaks down into either governance structure or implementation. So, yeah, definitely a good article here so check this out if you're interested. And finally, I published on my Health and Chain podcast my 107th episode with the leaders of a pharma ledger association. So I'm not going to get too much detail about pharma ledger is a consortium in Europe, trying to devise ways to use blockchain to help improve the healthcare ecosystem overall and increase trust as well. And with their, their main use case now is the electronic product information app and tool so if you're interested, check that out. Great conversation, both Dan and Marco are amazing and they've been really leading that space. Among many others as well in pharma ledger to kind of help explain help experiment with with DLT for healthcare so really, really proud of that team. That's what I had on the agenda today. So quite short, I hope you all have a happy winter solstice day and good holiday as well. Pete thanks for joining. Do you have any comments on the content here anything you wanted to share anything you found recently? I thought it was great there are probably at least three or probably four things on your on your list there that you sort of highlighted that are things that either I'd heard of and not ready yet, but or are completely new to me, and I need to read it out so this has been a thoroughly useful 38 minutes. Awesome. Thank you. And did you have you really done 107 podcasts. Yeah, 107 I've been doing it for years now. Yeah, so. Wow. And to be honest when I first started I didn't think there would be that many people doing healthcare with blockchain but thankfully, there's a lot more actually I could probably do like 500 if I really, really had to. All right. Yeah. Thank you. Oh, thanks everybody for listening and leave a comment, like, subscribe. Appreciate it. Thank you. See you. You take care.


The immediate past minister of interior, Ogbeni Raouf Eregbeshola, has called on true progressive stakeholders, traditional and social institutions who believe in the APC development agenda to rally members for successive elections in Oshun state. Ogbeni Raouf Eregbeshola stated this when he was received by his supporters in Oshubu, the Oshun state capital. Addressing people of the Freedom Park in Oshubu, Ogbeni Raouf Eregbeshola attributed the success recorded in politics to God, President Bollat Ahmad Tunibu and former President Mohamed Abu Hari. He thanked the people for their support over the years and reaffirmed his resolve to return the progressive back to power in Oshun state. The party holds itself together and will consolidate our strength for effective party mobilization and advancement. The party has potential for greatness, but there is need for personalization. That is all I have been preaching, that is all I have been advocating and I believe those who are ready, who are willing to have the party properly positioned for political work, we need our call for effective consolidations. Hello, hope you enjoyed the news please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


The US Space Force's secret space plane, the X-37B, has just set a new orbital endurance record, returning to Earth after 908 days conducting NASA and military science experiments on its sixth flight. For the first time ever, this mission was launched with a service module giving more capacity for payloads. However, this can't be recovered, so it burns up in the atmosphere whilst the X-37B landed at the former shuttle landing facility at the Kennedy Space Center.


going back again once to the 90s because that's when all the fun things happened. Back then, again, I was working at this store that most time I sat around, I was either cleaning the store or just sitting there. But every night, so I've talked about how this store had DOS registers. Well, the registers every night would close out the register and it would dial up headquarters, say, hey, the store is closed and then it would disconnect. It wouldn't upload anything at that point. And then a few hours later, headquarters would dial back to the register and get the information from the sales from that day and give the the registering updates that it needed to give it. So I thought, if this computer is just waiting for someone to dial into it, what happens if I dial into it? Now, I wasn't smart enough at the time to really do anything. I didn't understand how ports worked on networks when you connected in. But I was able to, you know, pick up a phone after leaving work. I dialed the store number. It wasn't even a separate number. The store number ring ring, you know, sound, you know, fax modem. Okay.  I open up hyper terminal and I dial up that number. It connects. I don't get anything.  I'm like banging on the keyboard to see if anything I type help question mark forward slash question mark forward slash help. You know, I'm not getting anything. I'm not getting a login prompt or anything, but I connected to that machine. You know, whatever I gave up after a little bit once work next day, nothing. A few nights later, I try again. Again, I couldn't do anything. You know, I shouldn't be trying to do this anyway, but I didn't accomplish anything. Well, I get to work the next day after doing that and the register isn't isn't isn't starting up properly. Not that I messed up the machine in any way. But what happened was I must have tried to connect and I must have been connected to it trying to do something while the headquarters was trying to connect to it and they were unable to connect to it and their computer must have gave up. So the register never finished closing out during the night and never and never upload all that information. So so basically I did a denial of service attack on this register before I think there was the term denial of service.  So I'm quite sure that this company doesn't, you know, use the dial up anymore in that matter. But for years it did. And in reality, if you wanted to mess with this company, all you had to do, you didn't even need a computer. I could have just dialed up their register, left the phone off the hook. And unless unless it disconnected after a while, if you didn't actually connect to it like with a computer, but I could be I could just keep on, you know, dialing up that number and block the register. And when people got to work the next day, they wouldn't be able to use the register. You know, I forgot I had to go through I think I had call headquarters and and get it all straightened out. But yeah, the very simple to mess up that particular machine with just dialing it up with a phone. Anyway, I thought I'd share that because it's funny how simple some things I didn't accomplish anything useful unless I was trying to do a denial of service attack, which I was not. And um, yeah, the 90s were fun. Things were different back then. Thanks for watching and have a great day.


Live from Barcelona, Spain, it's theCUBE! Covering Cisco Live Europe. Brought to you by Cisco and its ecosystem partners. Welcome back to Cisco Live. We're in Barcelona, Dave Vellante and Stu Miniman. You're watching theCUBE, the leader in live tech coverage. We go out to the events, we extract the signal from the noise. George Bentank is here. He's a product manager for camera systems at Cisco Maraki, great to see you. Thanks for coming on theCUBE. Thanks very much. So, we were saying, Maraki's not just about wireless. It's not just about wireless. It's about cameras now. Tell us about the rule. The Maraki camera is relatively new. It's one of the newer products. It came out about just over two years ago. And it's really embodying what we're about as a business unit at Cisco, which is about simplicity. It's about taking normally complex technology and sort of distilling it so customers can really use it. So what we did was, the camera was, we spoke to a lot of our customers, listened to what they had to say and they were fed up with the boxes. They don't want these servers. They don't want the recording solutions. They just want to get video. And so we built a camera which has everything inside it. All the video is stored in the camera using the latest solid state storage. And then we did all the analytics and the other sort of cool things people want to do with video in the camera as well. And yet to make it easy to use, it's all managed from the Maraki cloud. So that allows you to scale it from one camera to 100 cameras to 100,000 cameras. And yet have nothing else other than the cameras and the management from the cloud. Well the way you describe it sounds so simple but technically it's a real challenge what you've described. What were some of the technical challenges of you guys getting there? Well there's sort of two components. There's the device piece. And when we look at the device piece we've basically leveraged the latest advances in the mobile phone industry. So if you look at the latest iPhones and Android phones we've taken that high density, highly reliable storage and integrated it into the camera. And then we've also taken the really powerful silicon. So we have a Qualcomm Snapdragon system on a chip in there and that performance allows us to do all the analytics in the camera. And so the second piece is the cloud, the scaling and the management. And with video it's lots of big data which I'm guessing you guys are probably pretty familiar with. Yeah, we'll stop by there. And trying to search that and know what's going on and managing its scale can be really painful. But we have a lot of experience with this. The Market Cloud Infrastructure manages millions of connected nodes with billions of connected devices and billions of pieces of associated metadata. This is just like video. So we can reuse a lot of the existing technology we've built in the cloud and now move it to this other field of video and make it much easier to find things. And when people talk about the camera systems, IoT obviously comes into play and security's a big concern. People are concerned about IP cameras off the shelf. Everybody knows the stories about the passwords where they never changed out of the factory and they're the same passwords across the, and so presumably Cisco, Meraki trusted name and there's a security component here as well. Yeah, absolutely. And this is actually one of my favorite topics because unfortunately not many people ask about it. It's one of those, it's not an issue until it's an issue type of thing. And we put a lot of work in it. I mean, Cisco has security in its DNA. It's just like part of what we do. And so we did all of the things which I think every camera vendor and IoT vendor should be doing anyway. And so that's things like encryption for everything and by default. So all the storage on the camera is encrypted. It's mandatory so you can't turn it off and it's zero configuration. So when you turn it on, it won't record for a few minutes while encrypting storage volume and then you're good to go. We also manage all the certificates on the camera and we also have encrypted management for the camera with things like two-factor authentication and other authentication mechanisms on top of that as well. And so it sort of leaves some bounds ahead of where most of the decision makers are thinking in this space because they're physical security experts. They know about like locks and doors and things like that. They're not digital security experts but the Cisco customer and like our organization, we know this. And so we've really taken that expertise and added it to the camera. Yeah, George, security goes hand in hand with a lot of the Cisco solutions. And is that the primary or only use case for the Baraki camera? I could just see a lot of different uses for this kind of technology. It really is very varied. The primary purpose of it is a physical security camera. So being able to make sure that if there's an incident in your store, you have footage of maybe the shoplifting incident or whatever. But because it's so easy to use, customers are using it for other things. And I think one of the things that's really exciting to me is when I look at the data. And if I look at the data, we know that about 1% of all the video we store is actually viewed by customers. 99% just sits there and does nothing. And so as we look at how we can provide greater value to customers, it's about taking the advances in things such as machine learning for computer vision, sort of artificial intelligence and allowing you to quantify things in that data. It allows you to, for example, determine how many people are there and where they go and things like that. And to maybe put it all into context, because it's one of my favorite examples is a Cisco case study in Australia where they're using cameras at a connected farm as part of an IoT deployment to understand sheep grazing behavior. And so this camera watches the sheep all day. Now as a human, I don't want to watch the sheep all day, but the camera doesn't care. And so the farmer looks at eight images representing eight hours, which is a heat map of the animals movement in the field and they can know where they've been grazing, where they need to move them, where this might be overgrazed. And so the camera is not security at this point. It really is like a sensor for the enterprise. Yeah, it's interesting. Actually, I did a walk through the DevNet zone and I saw a lot of areas where I think they're leveraging some of your technology, everything from let's plug in some of the AI to be able to allow me to do some interesting visualizations of what we're doing. There's a magic mirror where you can ask it like in Alexa or Google, but it's Debbie, the robot here as to give you answers of how many people are in a different area here. So, the camera is no longer just a camera. It's now just an end node connected and there's so many technologies. How do you manage that as a product person, where you have the direction, where you put the development, how you can't support a million different customer use cases, you want to be able to scale that business. Absolutely, I think the North Star always has to be a simplicity. If you can't go and deploy it, you can't use it. And so, we see a lot of these cool science projects trapped in proof of concept and they never go into production and customers can't take advantage of it. So, we want to provide incredibly simple, easy out the box technology which allows people to use AI and machine learning and then we're the experts in that but we give you industry standard APIs using REST or MQTT to allow you to build business applications on it directly or integrate it into Cisco Kinetic where you can do that using the MQTT interface. So, Stu, you reminded me, so we're here in the DevNet zone and right now there's a Meraki takeover. So, what happens in the DevNet zone is they'll pick a topic or a part of Cisco's business unit right now, it's the Meraki everybody's running around with Meraki takeover shirts and everybody descends on the DevNet zone. So, a lot of really cool developer stuff going on here. George, I wanted to ask you about sort of where the data flow. So, the data lives at the edge, wherever you're taking the video. Does it stay there? How much, given that only 1% is watched, are you just leaving it there, not moving it back into the cloud? Are you sometimes moving it back into the cloud? What's the data flow look like? So, you can think of this interesting sort of mindset which is let's have a camera where we don't ever want to show you video. We want to give you the answer because video is big, it's heavy. Let's give you the answer and if that answer means we give you video, but if we can give you the answer through other forms of information like a still image or an aggregate of an image or like metadata from that, then we'll give you that instead. And that means customers can deploy this on like cellular networks out in the middle of nowhere and with much fewer constraints than they had in the past. So, it really depends but we try and make it as efficient as possible for the person deploying it. So, they don't have to have a 40G network connection to every camera to make the most of it. Yeah, so that would mean that most of it stays resident to the edge. Most of it stays at the edge in the camera. And then you take the pieces. And I talk a little bit more about the analytics component. Is that sort of Meraki technology that came over with the acquisition? What has Cisco added to that? Maybe speak to that a little bit. So, the camera is a relatively new product line within the last sort of two and a half years and the Meraki acquisition was, I think it was like five years or more now down that road. So, this is definitely a post acquisition and part of the continued collaboration between various departments at Cisco. What it enables you to do is object detection, object classification and object tracking. So, I know there's a thing. I know what that thing is and I know where that thing goes. And we do it for a high level object class today, which is people. Because if you look at most business problems, they can be broken down into understanding location, dwell times and like characteristics of people. And so, if we give you the output of those algorithms as industry standard APIs, you can build very customized business analytics for business logic. So, let me give you like a real wild example. I have resale customers tell me that one of the sort of common causes of fraud is an employee processing a refund when there's no customer. And so, what if you could know there was no customer physically present in front of the electronic point of sale system where the refund is being processed? Well, the camera can tell you. And it's not a specialist analytics camera. So, security camera you're going to buy anyway, which will also give you this insight. And now you know if that refund has a customer the other side of the till. Oh, that's awesome. So, okay, so that's an interesting use case. What are some of the other ones that you foresee or that your customers are sort of pushing you towards? And what is, paint a picture as to what you think this looks like in the future? It really is this camera as a sensor. So, one of the newer things we've added is the ability to have real time updates of the light conditions from the camera. So, you can get from the hardware backed light sensor on the camera, the lux levels. And what that means is now you have knowledge of people where they are, where they go, knowledge of lights. And now you can start going, okay, well, maybe we adjust the lighting based on these parameters. And so, we want to expose more and more data collection from this endpoint, which is the camera to allow you to make either smarter business decisions or to move to the digital workplace. And that's really what we're trying to do in the Marrake offices in San Francisco. And do you get to the point or does a client get to the point where they know not only that information you just described but who the person is and what? Yes and no. I think one of the things that I'm definitely advocating caution on is the face recognition technology has a lot of hype, has a lot of excitement and I get asked about it regularly. And I do test state of the art and a lot of this technology all the time. And I wear hats because I find them fun and entertaining but they're amazingly good at stopping most of these systems from working. And so you can actually get past some of the state of the art face recognition systems with two simple things, a hat and a mobile phone.  And when I speak to customers, their expectation of the performance of this technology does not match the investment cost required. So I'm not saying it isn't useful to someone. It's just for a lot of our customers, when they see what they would get in exchange for such a huge investment, it's not something they're that interested. Yeah, the ROI is just really not there today. Not today, but the technology is moving very fast so we'll see what the future brings. Yeah, great. All right, George, thanks so much for coming on theCUBE. It was really, really interesting. I'll leave you the last word. Customer reactions to what you guys are showing at the event, any kind of new information that you want to share? There are some that we're talking about in the whisper suite which I will leave unsaid unfortunately, but it's just knowing that you can use it so simply and that the analytics and the machine learning come as part of the product at no additional cost. Because this is like pretty cutting-edge stuff. You see it in the newspapers, you see it in the headlines and to say, I buy this one camera and I can be a coffee shop, a single owner and I get the same technology as an international coffee organization, it's pretty compelling. And that's what's getting people excited. Great, and it combines the sensor at the edge and the cloud, the cloud management. Best of both worlds. It's awesome, I love the solution. Thanks so much for sharing with us. Fantastic. All right, keep it right there, everybody, Stu and I will be back with our next guest right after this short break. You're watching theCUBE from Cisco Live, Barcelona. We'll be right back.