I always used to undergo routine mammogram and that's how I came to know in 2019 that I had a lesion measuring 8 millimeters in my right breast.


One of the best game ones in the World Series we've ever seen, Arizona's up two, bottom ninth, they need three outs, they win game one, they've been really good at closing out games. This breakdown is brought to you by DraftKings. First pitch outside from Seawall, I'm says strike, batter's like, I don't know, but Seawall's like, hey, if we're getting that, let's just stay outside. That fastball's up, but now he wants to ride that line. They go, did he swing? He says no, but then he's like, wasn't that a strike? Cause I threw that same ball to open the at bat and you called it a strike. The red one, he called a strike, the green one called the ball. Same pitch. That's a little bit of a bummer. Cause Seawall was like, oh, I'm getting that. I'll take that. Instead that's a ball, now it's more outside. Three in ones to count and that one's even more outside. And that's a pretty important run. Cause now the tying run is at the plate. Simeon chases a slider away and then he kind of hits that slider how he wants it, but foul, squared it up. Then they go up and in fastball. That's what Seawall does. It's kind of a sneaky pitch. He's going to try to throw that up and in fastball to Seager and he says, don't think so dude. Tie game, big home run. Crowd erupts, that dude caught it on the fly. Watch, watch this fan. Ball's way up. Everyone's going crazy celebrating. Not this fan. He's locked in.  Catches it. Great celebration. Ah, Bochi's ecstatic. He's screaming on the inside. Seager screamed on the outside, threw the bat, hopped his way 45 feet and then started jogging. Whole bench, let's go. Let's go.  This is creepy. Avaldi and hedges are very synchronized. Watch their mouths. Watch their mouths. That's creepy. If this was synchronized cheering, they start off hot and then hedges kind of is behind a beat. So see, Avaldi, Avaldi looks and then hedges looks and then Avaldi brings the arms down and claps and then hedges celebrates. But still pretty much there. Maybe they're doing that on purpose. You know, maybe it's like a row, row, row your boat situation where they start on time and then someone falls behind. But yeah, pretty in sync celebration by those two. Creeped me out. All right, let's go to the bottom of the 11th inning. Rangers fans are noivus, tie game. Adelis Garcia comes up. So Arizona says, we're going to go to a new pitcher. Let's bring Castro in. He throws fast and Dolly says, what's this guy got?  I probably told him he's got a slider, changeup, and a fastball. And he's going to open them up with the slider and it's just not good. And he's not going to see another slider. The rest of this at bat, he's going to see a changeup low. 2-0, 2-0 is a fastball count.  You want to find the zone. Not really this dude. You don't want to challenge him. So they go changeup. Garcia swings over it. Kind of a nice pitch. Was a ball, got the chase. Changeup again, 3-1. Now we're stressed.  At least Garcia is not stressed because it's 3-1. Hasn't thrown him a fastball yet. Hasn't thrown him a pitch in the zone yet. He's got to throw a fastball. It's got to be in the zone. I'm at at least Garcia. That's a home run. See you later. Ball game, Rangers.  He just says, that's a home run, guys. You can come out. Throws the helmet.  And then we got low on the Gatorade, a little bit of a disappointing showing from him with the Gatorade because I think he misses. Garcia might get some splash on the butt, but then no one else got hit. You know what I mean? If you're going to ISO one person, you better get the guy you ISO. Otherwise, just throw it up and get everyone wet. I think we end up with just the ground there. That's just a ground screw situation. I think the Grom came with double water bottles on the right. I'm not positive it was the Grom, but it might have been. And yeah, Gatorade is out of there. Look at that. They call it a four seam, but that's a two seam grip. And woo, that's pretty. It's spinning. It's spinning. It's spinning. It's pretty. It's smashed. Gone.  He's just like, yeah, guys, that's what I've been doing. Boom. Line drive. Other way. Fastball low. Goes into the crowd. They're fighting for it. Not this dude. He's just bam in his chest. Hedges was on deck. And he's like, oh, he's in the hole. I don't know. And he's like, thank god I ain't hitting. You did it. You did it again. He's done it a lot. He's done it an absolute lot this postseason. He has now broken the MLB record for RBIs in a single postseason with 22. And this was his fifth straight game with a Homer. Unbelievable stretch we're seeing from Garcia. This breakdown was brought to you by DraftKings. Thank you, DraftKings, for sponsoring the breakdown. Thank you to you guys for watching. And if you want to subscribe to the YouTube channel, that's much appreciated. That's much appreciated.  That's much appreciated. It'd be nice.


So, my talk today is about the way we think about services, especially as we stack them on back ends, have different services access each other, and the different methods of compromise that these sorts of services face. But to start off, we're going to have to look at how we define security, the different types of attacks that we've seen in the wild against these sorts of infrastructures, especially as things have moved more towards stacked services and microservices. The sort of solutions that people have today, other approaches to the security that exists in both practice and in academic work, as well as how we can achieve a more modern approach to least privilege architecture in terms of how services communicate with each other that sort of builds on all this progress and all this work that's occurred so far. I'm David Strauss. I am one of the co-founders of Pantheon, which uses SystemD extensively to run a container grid as well as a bunch of other services. I've also done work with the SystemD project, and I do work with the Drupal project on the security team there as well. So the way that I like to define security is the CIA triad, and there are a lot of different ways to define it, but the first two parts are pretty uncontroversial. One of the parts is confidentiality, the idea that someone can't see information that they shouldn't be privy to. Then there's also integrity, which is the question of security and whether someone can actually alter data, tamper with systems, and actually damage the configuration or operations of the system. These two parts, pretty much everyone includes in security, but I think the important thing to also add in is the concept of availability, which is that we deploy systems because we want them to actually do work. We deploy them out on the web because we want them to be accessible to the public. This means that we can't do what is the trivially most secure thing, which is just a stuff-a-server in the closet disconnected from the Internet, and that's a great way to keep it from getting hacked, but it's also a really bad way to get anything done. Some of these models will also focus on how they can be deployed in a distributed fashion that doesn't have things like single points of failure and doesn't require ongoing engineering and implementation and maintenance effort to be able to continue to use these systems. A lot of this comes down to the attack versus defense. The ways that attackers are confronting systems now have become much more based on not attacking directly the system they want to compromise, but on achieving some sort of foothold in the target infrastructure, often for an extended period of time. Or possibly they might exploit one system and use that as a foot in the door to exploit a different system. Some of the most damaging compromises in the past decade have occurred through methods like this. And what this means is that we can't think about defending systems purely on the basis of a system defending its own resources. We also have to think about systems in the sense of what sort of foothold they provide for compromising other systems. So just a few kind of breaches over the past five to ten years that have involved this sort of foothold architecture. In the case of Sony Pictures, for example, they convinced a bunch of users with phishing attacks to be able to give up their credentials. They sat on the system for approximately a year before actually doing the real payload damage and extracting data and threatening the company in various ways. So it's often about these initial steps that allow the compromise to fester. The Panama Papers breach had an instance of Drupal that was unpatched for three years and then they used that as a step forward to be able to compromise all the documents behind that infrastructure. And then there was one of the most recent ones was Equifax, where they used an Apache struts vulnerability in order to get remote execution capability on the web servers and then be able to use that to exfiltrate all the data from the database. But there's one thing that all three of these have in common, which is that the thing that they attacked is not actually what the payload was on. It was just a step forward toward that. So I have a fundamental problem with the way that a lot of these breaches have been treated in the media and by security professionals because in many cases what comes up is they should have kept up with patches. They should have been managing their systems better and that's true. I'm not saying that that's not actually the case. But what I think is more important when we think about security for these sorts of systems is that one vulnerability shouldn't allow such a large breach. We should be building systems where even if they remain unpatched, they're able to be resilient against attack becoming severe because patching can only go so far with these systems. When you have something like a zero-day attack and a vulnerability gets discovered or announced well before any fixes are available, you have to rely on things like defense in depth and sophisticated methods to contain attacks that don't rely on every system being perfect. So I think they should have kept up with the patches, but they also should have designed all these systems where it wouldn't have been so catastrophic. And we're also facing new threats against each of these sorts of controls. We have, in the traditional case, we've had things like a trusted LAN and VPN where someone has something like an internal office network and then they make a system whitelisted for, say, IP access from their office and then they require people to VPNN to be able to get access to those systems. This is where phishing and malware attacks come in. Basically, by compromising the systems on a trusted network, they're able to get a foothold to be able to access the systems that were supposed to be protected behind it. The same thing occurs on data center networks as well. A data center network segmentation is a really common way to basically break up the networks between different systems, but if you can compromise something on the target segment of the network that's within that trusted firewall or behind that firewall, then you have that foothold and that external barrier is no longer sufficient to protect all the systems within it. And then we have a lot of issues with the way that I see systems, for example, like Equifaxes managing things like encryption and access credentials. Because encryption is almost unbreakable if it's implemented properly. The problem with most encryption is that people can actually get the keys to it. They can decrypt the documents. And in many cases, the security with encryption is most weak by the way that the keys are managed for it. And cases like Equifax, for example, some of their data was encrypted, but the web application had basically the keys and the necessary things to be able to get to some of the data. So these are traditional defenses. They're still useful, but as attackers have gotten better and better at achieving a foothold behind the defenses, and then working from there, they are no longer the strong barriers that they used to be, because attackers are getting very good at this. So, and I think that microservices and the way that we're handling things like container environments, stacked services, cloud deployments are actually making the stakes even worse for these sorts of systems. And I'm saying this out of love for these things, because I want to kind of save the security of some of microservices and service-oriented architecture, but I see a lot of problems with it as well. One of the ways that I often see people deploying these services is where they'll have an edge that's sort of a firewall, and they'll have something like a virtual private cloud, or some sort of other work partition, and then all the services get thrown into there. In this case, what happens here is we have something like an edge proxy, it's performing any kind of filtering validation, et cetera, forwarding things onto these services. But this has an enormous amount of tax surface. It has much more tax surface in my mind than an equivalent monolithic application, because each of these services is working on a different framework, a different programming language, they may have different vulnerabilities. For example, if one of these services behind here has an un-serialization vulnerability that gives something like remote code execution, and I can get the edge to hand it to that service, then I only need one of these services behind this firewall to be vulnerable for me to have a launching off point for talking to the... And in this sort of scenario, it's often the case that there's not a lot of authentication to be once you're within that trusted boundary, and that means that one leaping off point can quickly become a complete compromise to the system. So I don't think that this approach is really where it's at, even though it's the easiest way to basically convert a monolithic service into these sort of service-oriented architectures and microservices. This is the approach more that we are using at Pantheon, and this is becoming increasingly popular in a lot of container orchestration systems. The name that this seems to have been picked up is micro-segmentation. This is the idea that rather than trusting that you have one big boundary around everything, you actually have a lot of flexible boundaries and tunnels between these systems. This is also something that can be enforced by more advanced virtual private cloud infrastructures as well as some of these sorts of network mesh underlying layers that can then create a sort of virtualized and dynamic network that allows services to talk to each other only when they're allowed to. In the case of what we're doing at Pantheon, we're deploying certificates into every one of our containers and then whitelisting certain attributes of these certificates basically create a set where we don't have, we get rid of the concept of there being a matrix where any service can talk to any service. This means that we've somewhat reduced the amount of compromise that can occur to the system because if you compromise, say, that rightmost service in here that only receives requests from these other things and nothing else actually permits to make requests, at least you don't have every single one of these be a launching off point for a complete compromise of the whole grid of services. There's almost an orthogonal approach that I've seen. This is what my understanding of the approach from things like GraphQL is and it's the idea that the edge itself is sort of untrusted, which means that you have a fairly permeable boundary, you're not really relying on the edge to do much filtering and then you can have each of the individual services basically defend themselves, manage all their own authorization, manage all their own validation of requests coming in, the edge tends to forward it to each of those services and the edge is basically unprivileged. These two approaches have almost opposite benefits and one of my goals here is to try and bring these things together and find solutions that actually provide both types of segmentation without compromising the usability of the system. And that was so the empty box in there I'll fix that before I export the deck, but that is like a neutral face. I tried to basically visualize what happens with each of these segmentation architectures in terms of what happens when something gets compromised. In this case with the trusted edge, being able to get access to any system, the edge system or internal system provides a great leaping off point for almost generalized compromise of the system. Half the stuff that I've seen on WikiLeaks is usually from this sort of approach whether it's through microservices or just the active basically putting something like an email server on the same network as the website. And then once they get one foothold, it's end of the story. The sort of micro segmentation approach that we have for the kind of pantheon and the very container oriented setups, it basically trusts the edge to defend a lot of the internal infrastructure and then deep privileges a lot of the deeper services. So this means that if you compromise a deeper service, you're not actually able to do that as a launching off attack to everything else. But if you can attack the edge, then you actually get an enormous amount of access and the edge is kind of fundamentally trusted to have validated and approved requests before they go back to deeper services. And the edge uses its own authority and reputation as a way for the deeper services to get the job done. And basically the deeper services will do anything that the edge asks for. And then going back to that kind of opposite approach where you have the more forwarded credentials where the edge is deep privileged but the deeper services perform all of the heavy lifting. On one hand compromising the edge or proxy at the boundary of the infrastructure is less of a problem. It still has a little sweat mark there because no compromise is completely without consequence. And this one would allow you to access the credentials of whatever users are active at the time but not necessarily to compromise the infrastructure in general. But the downside of this case where basically you forward things like user session data to these back end services is that if an attacker gains control of any of these back end services, you're basically forwarding user session data that provides full control of a user account or a full control of whatever that API token does for every one of those back end services. So if I can get code execution on any of the back end services that are getting the credentials forwarded, I can start harvesting those credentials and making use of them. And one would think you might be able to combine these two things directly but they actually have completely opposite philosophies which is really why I started examining this problem. That if you use micro segmentation, you're leaning on the edge so that you can have acknowledged deep services in the system. And if you forward your credentials, you're relying on your deep services so that you can weaken the trust in the edge. So there's not a trivial way to just combine these two models because you either end up with some combination of the worst of both in the sense that both rely on trusting different parts of the infrastructure to distrust the other part of the infrastructure. So how can we combine this stuff? I started looking for answers. I started looking for answers on this in some new and actually pretty old places. The first place that I looked was one of the oldest sources of design around things like capabilities. How many people in this room are familiar with capabilities not in the Linux kernel sense? Okay, I see a few hands. So Kerberos has a really interesting model that took the better part of 10 or 15 years to kind of iron out. This is just the diagram off of Wikipedia if you want to kind of see this in more detail and more description. But the heart of this is that this has decoupled reliance on the services from the actual user credentials and user session data. So what you have here is basically three phases.  And then in the yellow area the user is saying, given that you know who I am give me basically a permit to access this specific service. Often in the case of these traditional Kerberos things this could be anything like a file server or a pointer or an email server, even some web applications. And then finally that ticket that it gets to actually have permission to access the service is then used to talk directly to the service. But that ticket is only useful for talking to that specific service. So in this case, like a traditional case of mounting a file system, it would be you'd go through the first phase to off yourself, you'd get a ticket in order to be able to mount a specific file system and then you would talk to the file server and say, here's my proof that I'm allowed to mount this file system. And that is what a capability is in the sense moved from the Linux kernel. Since that it is something that through possessing it alone proves that you have permission to access something or do something. And this file server doesn't need to actually know anything really about the user because the ticket alone proves that you have control to be able to access that file system or have specific permissions on it. But because some serious problems when you start stacking it for services what happens is that since tickets are service specific, you end up with a case where either a service then has to be privileged to be trusted for all the deeper services it might access. Let's say that file server is part of a federated system that talks to other file servers. It could forward this ticket from the user but that would mean that this file service basically has similar access to the user on all these deeper systems. There's not a great solution here and in fact a lot of this stuff around Kerberos was designed with the idea that you would access a single monolithic service at a time and not have a service necessarily front a bunch of others. So there was some work done on this in 2017 and it's actually pretty recent that a lot of this work has gotten done. It's a neat paper called CapNet Security and Lease Authority and a capability enabled cloud and they created this neat way of stacking services where they created this thing called sealed capabilities where basically you could give someone two tickets and you could say this ticket is good for mounting this file system and you can also give this ticket in and then that will give permission to perform things with the deeper services. And this is quite secure in my opinion but it's also a huge break in abstraction in the design because if I have a nested service like this I now have to have the client be aware of both of the things that it's connecting to because it has to get a ticket for this service and a ticket for the service that's behind it. And this means that the client is now more closely coupled with the nested set of service implementations. It means that the system that's granting the tickets has to be aware of all these different services and how they're nested and it makes the whole system rather onerous to maintain because every part of the system has to be aware of every granular part of the capability infrastructure. Another kind of thing that I found interesting is name constraints for X509 in terms of like another inspirational thing. This is, I don't recommend using this because the implementations of this are wildly inconsistent across libraries and are often not enforced. So unless you really audit your libraries it wouldn't touch this but it's a neat concept. It's basically the idea that you can create a limited certificate authority that's only able to issue certificates within a certain scope. And in this example here you can have a CA that then issues a certificate that allows issuing further certificates for any of the subdomains of all systems go.io and then that intermediate certificate can then actually issue and sign things for things beneath that and then it basically walks up the chain and says is there actually a coherent structure of trust here with the permitted subtrees. So I started putting these pieces together of these different systems that inspired this project and I started coming up with this thing that basically combines these kind of ticket granting tickets as they're called in Kerberos where it's basically the ticket that it uses to request access to other services plus the ceiling and plus the name constraints and started working on a strategy where basically a user would authorize itself from an authorization service very much like Kerberos but instead of getting back something that's specific to a Singleturf service it gets something that's scoped and in this case it gets back a token that is designed to provide access to any part of the user profile of user A but it's also addressed and this is bringing forward the sealed, the capability ceiling concept where this capability is only going to be usable by whatever set is the destination so it can actually talk to a service here and say I want to pull my user profile and it's able to send its request it's able to send this token and then service P which is sort of the profile service is able to say yes they should be able to pull profile A but then let's say we have something that is like marketing database and someone has marketing preferences and then pulling the profile needs to also pull data from that service as well what this starts supporting is the idea that much like the sort of nested X509 thing with the delegation, if service P here can actually create a new token that it signs and delivers alongside the first capability token we start getting this sort of nested infrastructure where the privileges get dropped more and more as requests go deeper and deeper into the infrastructure and so service M here only gets a token that permits access to the marketing services so if you compromise service M you wouldn't be able to capture any credentials that are useful for compromising other services and if you compromise service P you would only be able to get the necessary data to compromise the actual tokens being passed to service P at that point in time so this represents a strict subset of what's possible to compromise versus something like the kind of more graph QL forwarded credentials perspective or the sort of micro segmentation perspective and it allows combining both of those benefits by taking these kind of proven security model designs and then actually pulling them together not just in a way where they're stacked with each other but actually integrated with each other and with and that actually reduces the attack surface quite a bit and with that I will open it up to questions I actually have a question mic if anyone has any or actually I don't know whether the question mic is the back one or not test it I think this one works anyone so we have we need to send all these tickets among different services and many times we have a lot of services talking with each other how does performance fare with this kind of system because we have lots of tickets going back and forth how does that compare with for instance getting just a grant for one ticket on the edge in terms of the performance one of the beautiful things about the performance of these sorts of systems is that it requires very little external look up for anything in the sense that it's usually implicitly validatable any of these sorts of tickets because they're digitally signed usually have an expiration and that public key gets distributed through the infrastructure so each of these services is equipped to validate the ticket that rides along with the request and fully make an authorization decision without consulting any other services with the possible exception of doing revocation on some of this but often this solution for revocation in this sort of infrastructure is to have very short token lifetimes and then by having a five minute token if you can tolerate a five minute revocation time then you don't actually have to have any revocation infrastructure just synchronize clocks I think there was a question from back could you talk a little bit about how the sub requests thing works like what gets signed how does the cryptography work so this does assume that each service and the user basically has some sort of public private key identifying that entity and that's kind of why I have a little bit of script below this that says like signed by user A or signed by service P and what's happening here so would it be sufficient to talk about what happens in service P when it's trying to communicate with service M so what happens is service P receives the user's request to download their profile and they get that request with the capability token A sub P which is on the left which basically has a scope of the entire profile contents of user A if you see the I don't know if this has a laser pointer on it I think it does but I don't know how to use it oh there we go so you can see that this has actually a pretty broad scope here and then what service P can do is because it's addressed as the destination service that means that it can actually use this token to sub sign other tokens with its own identity so service P has its own kind of certificate or something that isn't really shown here and it's able to take the token AP which is addressed to service P its own identity as service P and then use that to sign token kind of A sub M here which actually only has the scope of the marketing part of the profile but has a source of service P and a destination of service M and that basically means that it's doing a delegated handoff to deeper services but it's only it would not be allowed for to have a scope here that exceeded the scope here so it's only able to close down the scope at each stage and because each of these is restricted to a certain destination the broader scope tokens are not usable by the deeper services either because even though service M will be in possession of token AP A sub P it won't actually have the ability to use it because token A sub P is not actually addressed to service M it's not sealed for service M but by using this chain we can actually validate that because service P had this authority and service P used its identity to delegate to M this token it allows it to to tighten the scope and delegate and do the delegation in a way that doesn't allow service M here to actually have any authority beyond what it beyond the marketing scope does that answer the question okay let me give you a mic oh does that make that that we've I think one of these mics has an issue that's good okay I think it's recording but it's pretty bad if this gets hacked the saving grace of the authorization service is usually that you can break out any identity services from it in a sense that you can usually break out any kind of thing that the user interacts mostly with in terms of how they provide their credentials how those credentials get checked that can be separate from the actual thing that creates the signed tokens and really the other saving grace of this is that it can be extremely small and it really this this design relies largely on the fact that this is while a fairly central point of trust is a very small point of trust there's not much application logic in here there's just whatever look up there is between user identity and authorization oh one second did you know that you can defeat the timeout of the login on Fedora by like pressing escape twice if you get the wrong password it's something I use when I mistype it all the time so are there any further questions out of time oh there's one in the back you generally have to have something like this regardless of the infrastructure you have either you have to embed that in all the services or you have to break it out and have something make authorization decisions yeah I think my question is about that actually so in practice sounds like the drawback of this approach is that you have to duplicate your token verification logic to all your services which may be written in different languages on so on how do you deal with that in practice the nice thing about a lot of the tokens and token verification is you don't usually have to combine much business logic with it because since the tokens actually contain the authorized scope to access implicitly you basically have to validate that the token is legitimate and that the actual specified scope that it's accessing matches whatever resource it's accessing on that service and that's in practice in my mind a lot simpler than having services call out to some sort of RBAC system to be able to figure out what whether a particular user is authorized to do x or y or z on a service and getting even more practical with it if you start using looking at libraries like things for JWT for example there are JWT libraries for almost every major language and framework and that allows choosing a standard like that allows you to embed validation across the board in almost all the frameworks that you might use for microservices and that builds in all the validation for like checking against the public key checking for expiration checking certain scope constraints you can actually put the scope constraints into the validation that's performed by most JWT libraries you can do similar things with most other kind of public key infrastructure setups but I'm quite fond of some of the JWT stuff because it has so much consistent validation across languages and frameworks that you can just include back there. Hi, you've already spoken about the size of the services and not having to call to a centralized RBAC I don't know if you've explored some of the claims that Istio makes to do similar sorts of things can you give a comparison? I'm not actually familiar with the claims of Istio would you mind summarizing them? So in this case delegated authentication for in-service requests but I mean the structure is slightly different in that it runs its own PKI it would end up being a comment if I carried on further I'm maybe a comment is the right answer to this but the real question for me is do the credentials that it forwards contain sufficient material for the backend services to be able to get the same privileges as the client that made the request? It can do, but the architecture has more central points of failure I guess than this does. The only thing I'd like to avoid with the forwarded credentials is the idea that every one of those backend services becomes privy to whatever API or session token the request came in from the edge with at least that's what I've seen with the GraphQL stuff I haven't looked at Istio for it I think we're probably out of time, yeah. Okay, thanks folks.


So this is an Intel Nook and this is the Intel Nook 12 enthusiast also known as Serpent Canon and what is interesting about this is that this is an Intel Nook that has the Intel ARC A770M mobile GPU. This is Intel's dedicated GPU and this is the first time trying it out here so this is the GPU you should be expecting in Intel laptops come next year and this is a very good showcase. Now you guys know I've covered nooks here on the channel and this is one I wanted to put through its gaming paces. It doesn't say it's a gaming nook in any kind of form or regard but I figured having the Intel ARC A770M I should get some good results but before that let's look at the nook itself it's really nice and simple all black nothing too crazy you've got of course USB ports in the front you've got a headphone jack you've got a Thunderbolt 4 you've got an SD card reader and you've got this power button vents all around which is pretty cool but at the back there are more ports for you to go through they are four USB A ports there is a 2.5 gigabit port for ethernet another Thunderbolt ports you've got optical you've got HDMI and then you've got two display ports and of course the power port now this thing comes with a massive power brick so that is a downside but this thing packs a lot in terms of specs. So this Intel nook enthusiast comes with a Core i7-12700H so that's the kind of same processor you'll find in a gaming laptop you've got the Intel ARC A770M with 16 gigabytes of DDR6 RAM which is pretty nice then you've got 16 gigabytes of regular RAM on your device you also got a Kingston 500 gigabyte storage PCI E4 so we've got all the things we need for this and you can see all the specs on the screen anyway now as you know I like to game on this channel and we wanted to put it through its paces to see what would actually get now I did run a Cinebench score for those who are interested you can find the scores up on screen but we care about the A770M what can it actually do for us so we went ahead and tested it off with Shadow of the Tomb Raider and we ran the benchmark test and at the highest settings we're able to get 96 frames per second running it on a 1440p monitor so this monitor you see on screen here is an NZXT monitor we'll talk about that later in the video but we ran it at the highest resolution of the monitor it's 144 hertz and we got 96 frames per second which is actually pretty good so that is just impressive for me to see especially with Intel's first run of dedicated graphics cards then we move over to Doom Eternal and Doom Eternal at the highest settings there which is Ultra Nightmare you can drop it down low of course we're getting between 70 to about 86 frames per second not what I usually like we could get higher of course if we drop it down from Ultra Nightmare to say Ultra we'll get it over 100 on that but it was good to see again I could play Doom Eternal without actually dropping below 70 frames per second so again that was pretty solid and the games looked good and ran pretty well and finally I went ahead and tried of course Call of Duty Modern Warfare Warzone as you know and on Warzone was getting roughly around you know 70 to about higher 80 frames per second again solid outing overall which means at least with the system I can get over 60 frames per second if I'm playing on a 1440p monitor if I drop it to 1080p I'm going to definitely get much higher results so what does that mean for me with this device what it means first of all is that the Intel ARC A770M is a solid dedicated GPU especially a mobile GPU which is what we have in the system and I'm glad to see that it actually can perform pretty well on the highest settings of a lot of games so if you want to get of course higher frame rates you can definitely just drop it down to say high or medium settings and you will get much better frame rates or even just go down to 1080p in that regard the only game we played at 1080p was of course Shadow of the Tomb Raider the rest were played at 1440p so you get the idea that this thing is a at least a good powerhouse when it comes to gaming and that is a good sign it means that when we look at Intel laptops next year with 13th gen and an A series dedicated GPU we should be getting some really solid performances but also hopefully Intel can price that quite generously so I mentioned the monitor earlier and I want to go back to that because that is an NZXT monitor that's the canvas and I'm actually just throwing into this video because I use it of course in conjunction while testing out the Intel Nook enthusiast what I like about this monitor is its price point currently you can get it for 289 the bad part about it is that they sell the stand separately but I do like the stand because it allows you to swivel left and right you don't have to actually turn the monitor the base actually turns and it's pretty steady plus you do have the ability to tilt up and down it does have of course HDMI ports two of those one display port and it has a refresh rate of 165 hertz now this is a 1440p monitor one millisecond response time also has hdl 10 capabilities AMD FreeSync premium as well it's got anti-glare and also a 100 1500 r curved radius which is pretty nice overall this is a saunas monitor and it pairs well with something like the Intel Nook now I don't have pricing for this nook because a lot of nooks you can get them bare bone but if you're looking for something that actually has some graphical punch with a small footprint like this I mean this might be the future of like desktop gaming because you don't have to have a super big rig to actually play the games you want and play them quite effectively so I definitely like this and I think this kind of proves that Intel is here to stay with their graphics cards especially just looking at the mobile version of the Intel arc I'm liking what I see I can't wait to see it with 13 gen and also maybe with the next version of the nook I will be checking out a gaming nook soon so stay tuned for that video anyway guys let me know what you think if you have any questions any comments don't forget to like share subscribe and always enjoy entertainment


Coming up next on this special edition of OES News in depth, we'll take a look at what mother nature has brought us in this latest round of wet winter storms and we'll see what state officials are doing to manage the impacts and what's on the horizon. That's all coming up next right here on OES News in depth. Hi I'm Kelly Houston thanks for joining us. Well there's a lot going on behind the scenes when it comes to this wet winter season and what emergency managers are doing to deal with the impacts of all this water filling up our reservoirs. Well in the middle of all of it is our very own Jonathan Goodell. Jonathan? That's right this building right behind me may look nondescript but in fact there are many key agencies such as the state flood operation center working closely with the national weather service to monitor this latest round of storms and its impacts. The state's flood operation center is the heartbeat of weather forecasting and water management during major storms. This is where experts in flood control, weather forecasting and reservoir operators share information and make critical decisions. A key partner in this operation is a national weather service located just feet away from the flood operation center. So we're currently standing in the operations area we are co-located with the California Nevada River Forecast Center. They are in charge of issuing precipitation forecasts and as well as those critical river forecasts for the area. We are then co-located with the state and federal flood center that way we can make sure information is flowing freely just down the hallway and that we're all on the same page here. That's an important page to be on because officials have been busy dealing with a wide range of effects from flooded roads to reservoirs filling up. For the second time this season the California Department of Water Resources has had to open gates again at the Sacramento Weir helping alleviate pressure on an already swollen Sacramento River. The Weir has a total of 48 gates and as of this afternoon over half have been opened sending a massive amount of water back into the Yolo bypass. This makes for an unusual year so far as a series of wet storms have caused impacts throughout the state. Well what's unusual about this is we've had storm after storm after storm so the ground is already saturated so anything that's falling on top of those saturated soils is pretty much running off so we have seen a lot of mud slides and rock slides up in the mountains and a lot of localized flooding around here because there's nowhere for that water to go. But Mother Nature may be taking a short break as forecasters say changes are in store. So right now we're looking at dry weather probably through at least Wednesday models are hinting at another wet storm moving in by the end of next week and so we really urge people to get out make those repairs that they needed and then prepare for the next round of rain. That's great advice as always to stay on top of the latest weather forecasts visit weather.gov and to get prepared for the next round of rain visit our website at caloes.ca.gov. For Cal OES news I'm Jonathan Goodell.


When talking about transit, a few countries are really important to mention because of their status as legends of transit, such as Japan, Switzerland, and Austria. I don't talk nearly enough about these countries because I'm always a little afraid I won't do them justice. But today that starts to change because we'll be looking at the excellent Vienna U-Bahn. A huge shout out to the folks from Vienna who helped me with this video, including Max who has a great video about cycling in Vienna. I also want to thank Patrick for lots of interesting information about this system. As well as Sebastian for providing excellent additional footage. Thanks so much for making all of this possible. Make sure you're following me on Twitter to stay tuned to whether I'm making a video in your city next. If you're not already, consider supporting me via Patreon, YouTube Memberships, or Substack. As with all transit explained videos, we need to begin with getting familiar with Vienna, which is not that big of a city, for this North American at least, with a regional population of around 3 million and an urban population of about 2, which is actually a really high proportion to be living in the urban area. Nice job Vienna. Of course, you've probably also heard a lot about Vienna, as it usually tops quality of life and sustainability metrics, and high quality public transport plays a big role in that. Looking at the city's features, it's located along the Danube as with Budapest, on the eastern slopes of the Alps. Here is the central area of the city, which isn't circled by tram services, which I'll cover more in a full future video. As with any proper urban transport system, Vienna's fares are fully integrated as well. Vienna has several major railway stations, including the relatively new Wien, Hoppenhof, as well as Vienna-Westbenhof and Praterstern, the latter of which mainly serve regional and S-Bahn trains. To the city's southeast, we have the airport, which is connected to the city's S-Bahn network with a tunnel underneath it, akin to Amsterdam Schiphol. Vienna is also doing a ton of new transit-oriented suburban development in areas like C-Stadt, which are located on transit to the north of the Danube. Vienna of course also has a very famous tram network, which we've talked about a few times on this channel. The tram network densely covers the city, south of the Danube, and even has offshoots to the north. As the U-Bahn network has expanded, sections of tramway paralleling it have actually been removed, not unlike in St. Toronto, but the network has also been growing. Given the great size of the Vienna tram network, a number of models of trams operating on it, including some high-floor models, but the most iconic tram is likely the ULF, or ultra-low floor model from Siemens. On the whole, the Vienna tram network is really quite good, and poorly of its own video in the future, as I mentioned before. Roots aren't super long, and trams provide an excellent local service, filling in gaps between rail and U-Bahn lines. So now that we have a rough overview of the city, let's take a look at the U-Bahn, shall we? The network currently consists of five lines, numbered from U1 to U6, but there is no U5, I'll explain that later. Line 1, or more accurately, U1, has 24 stations over 19 kilometres of track, from the south to the northeast, making it the longest in the network. Something I really appreciate is that in the moderately low density extensive line to the north and the south, portions of the line are above ground or even elevated. Oh, and U1 connects to Vienna-Helpenhof. The U2 runs from a connection point with the U1 at Karlsplatz in the centre, out east to Sistat, and connects to the U1 again at Pratterstern. U2 has 20 stations over 69.5 kilometres of track. The northern part of U2, including the park crossing the Danube, is quite new, and it's virtually all elevated, as with portions of the U1 I mentioned, including into Sistat where it terminates. U3 is a 13 kilometre route from the west to the southeast of the city, with 21 stations in total and connections to the U1 and U2 in the centre. U3 spends almost no time above ground unlike the previous lines. U4 has 20 stations on 16.5 kilometres of track, from the southwest to the north. Thanks to its arching shape, it has two connections to the U1 and U2, as well as a connection to the U3. The vast majority of U4 is above ground, but it does go below grade sometimes, running alongside canals and other waterways, and when the line goes underground it's typically not very deep. The line even has a very cool bridge where it pops out over a waterway for a couple of metres before passing back underground. U6, the final line, has 24 stations on 17.5 kilometres of track, from south to north. U6 has a connection to U3, as well as two connections to U4. U6 connects to the west bandhof, and much of it runs elevated above ground, often on historic elevated guideways through central areas of the city, as well as across the Danube to the north. Now, the system actually has some pretty solid expansion plans as well, especially for the fairly modest system in a relatively small city that it is today. Those plans call for extending U2's south with six new stops, with connections to U3 and U4, as well as the creation of a new line U5. U5 would start at the intersection of U1 and U4 at Carlsplatz, taking over the previous U2 tracks from Carlsplatz to Rathaus, before travelling northwest to intersect and terminate near U6. A reduced version of these works with shorter versions of U2 and U5 is already under construction. With the network out of the way, let's dive into the many unusual features of the NSU bond. The first that's always stood out to me has to do with the depots on the system. Many of them are near the ends of lines, including one elevated in Zistat, and they often have a very long linear format, which reminds me a lot of Mexico City of all places. The rolling stock of the system is also really interesting. Trains include six car sets of 2.8 meter wide trains, which measure roughly 110 meters long. The original rolling stock was similar to some models in Germany, but the newer rolling stock is actually from the Siemens modular Metro family, which you might recall is also used in Taipei. The newest Taipei V sets are probably the most interesting, as they're fully walkthrough and have a front fascia design courtesy of Porsche design, who also had their hands in the design of the iconic QLF tram. The Taipei X trains, which have a design reminiscent of the Taipei V and are also being manufactured by Siemens, will be capable of fully automated operation, and will be used on the U5, making it one of the few automated subway lines in the German-speaking world. And it'll actually have platform screen doors as well, which is also fairly uncommon in the German-speaking world. You might have heard me mention in a previous video, but Vienna's U6 is quite unique. It has its origins in the earlier Vienna stop-on system, which was Vienna's main form of rapid transit prior to the U-Bahn. When modernizing the line that became U6, there was a consideration as to whether conversion to the more typical high-floor cars used on the system was possible. But in order to maintain the historic nature of much of the line and its stations and way of infrastructure, it has been maintained as a low-floor rail line with metro-like characteristics. Despite this, the tram-style vehicles on the line actually are related to the Bombardier-Flexity Swift light rail vehicles, and they even use parts of the tram network to head to their maintenance depot. As it turns out, U4, which does have proper metro-style trains, also is converted from a previous stop-on line. Now, with that history, you might be surprised to know that the whole Vienna-U-Bahn network is actually quite young, first opening in the 1970s. Prints for a system existed for decades prior, but were repeatedly disrupted. That being said, if you're wondering why Vienna has no U5, that would be because, like many good transit cities, Vienna has had long-term plans for its network development. And for a long time, U5 simply wasn't built, and thus its designator wasn't used. Fortunately, the young age of the system means its signaling is quite modern compared to older systems, with manual driving only still a regular occurrence on the U6. The system even has an automatic reversing feature, similar to what should hopefully be coming to the Elizabeth line in London fairly soon. Vienna's U-Bahn has very nice stations, as you might imagine, from the historic station stops on the U6 to the newest elevated stations on the U2, there are a wide variety of styles used. But stations generally feel quite clean and simple, something which is certainly aided by the lack of fare gates. Since as with most systems in the German-speaking world, the U-Bahn is proof of payment. Reminiscent of Toronto for me, Vienna has nice transfers from its U-Bahn and mainline rail to trams, such as heat sink, for example, or a much larger station like Pratterstern. Perhaps where the most learning from Vienna could come from these days, especially for cities in the Western world, is how extensively elevated and accurate design is used to provide network expansion at low cost to newly developing areas, something that can also be seen with the oldest parts of the network on U6. And with that, we have the Vienna U-Bahn, a truly wonderfully designed system in an iconic urban center. Thanks for watching and I'll see you in the next one.


Hi everyone, Shawn with jaspyscasebrakes.com here doing 2019-2020 Panini Chronicles NBA Fat Pack Random Team number 292 Where at the end we're gonna give away eight spots in the upcoming noir break. That's sold out now So 30 spots high risk high reward. We'll first do the break No veteran common ship at the end of the break. We didn't re-randomize all 30 customer names Top eight names when a spot in the noir break coming up next. So Here's our list of customers from Gary Simpson last spot mojo back up to Kyle and Our teams from the Wizards up to the Hawks dice for all to randomize both lists and pair them up four to four eight times and eighth and final time from sumin down to Gary eight times on the teams eighth and final time So The Timberwolves back up to the Rockets no trade window on these, but let's get it all on tape cool Print and highlights on their TJ Leonard with the Grizzlies chances at John Morant Kevin Miyakawa with the Pelicans chances at Zion Williamson Kobe white Phoenix Chicago Bulls Ryan Crespi and Kobe white recon For Ryan in the bulls. So let's go back to the randomizer and Here is Here's the customer list again from Gary back up to Kyle and Dice roll for a new randomizer and it's the top eight names after one and a six seven times Seventh and final time from spots nine down to 30. Thank you guys for getting into the break And hopefully I can get you a spot next time in the meantime. Congratulations to Kyle a boat Summon Kim Gary Simpson Mark Haraki Raymond de Jesus Gary Simpson Mark Haraki and TJ Leonard You eight now have spots in the upcoming noir break That was 2019-2020 Panini Chronicles NBA fat pack random team number 292 On jasky's case breaks calm. I'm Sean noir break coming up next Thanks for hanging out and I'll see you next time


The Nigerian Medical Association, NMA, and the Joint Health Sector Union, Juhezu, are also against compulsory vaccination. The NMA says people should be allowed the rights to reject vaccines while Juhezu thinks compulsory vaccination is senseless. Their statements are coming in the wake of the federal government's move to sanction anybody who refuses to take COVID-19 vaccines. The executive director of the National Primary Healthcare Development Agency, Faisal Shuaib, gave the hint of possible sanctions at a press briefing in Abuja yesterday.


What a surprise you to learn that a group of Danish explorers depicted the Giza Plateau with four prominent pyramids instead of three. Described as being a black pyramid in the 1700s by Frederick Norden who detailed this region extensively during his voyage of Egypt. He also describes as well as draws accurate accounts of monuments, hieroglyphics, and even local people during his time here. Everything checks out except one thing, the fourth great pyramid of Giza. Wait till you hear this. This explorer was a very reliable source of information for this time period. The link he had to go to confirm and describe to the Danish people of the wonders of Egypt are staggering. He had no reason to lie about another great pyramid so what happened to it and why is it gone? Perhaps it was stripped for the unique masonry that created this gigantic wonder. It is a mystery you know and looking at recent images from the European Space Agency it is hard to imagine there ever was another pyramid here yet there is a very reliable source suggesting there was. Egypt has fascinated us for thousands of years. The enormity of the undertakings are literally unthinkable today so why wouldn't this turn out to be true? The pyramid mysteries are unique. They are the talk of much debate today as to what exactly they were, who built them, and why. They have been right in front of us throughout the ages and even into modern times and we still don't have a logical answer. So when it gets suggested there was a fourth black pyramid made by stone more dense and less common than solid granite it really should not surprise us that it ever existed. We should be more concerned with where it went. There is very little trace if any today but in notes and drawings Frederick Norton describes the fourth great pyramid within these notes it reads. The principal pyramids are at the east southeast of Giza. There are four of them that deserve the greatest attention of the curious. For though we see eight others in the neighborhood surrounding Giza they are nothing in comparison to the former. The two most northerly pyramids are the greatest and have 500 feet perpendicular height. The two others are much less but have some particularities which occasion they're being examined and admired. It is without coating closed and resembles the others but without any temple like the first. It has however one particular deserving remark which is that its summit is terminated by a single great stone which seems to have served as a pedestal. The fourth pyramid has been made upwards above the middle of a stone more black than the common granite and at least as hard. Its summit is of a yellowish stone. I shall speak elsewhere of its top which terminates in a cube. It is moreover situated out of the line of the others being more to the west. It makes a series with the three others. Today experts have still not found solid evidence of a major black pyramid at the Giza plateau but that doesn't mean it wasn't there. There are some authors who suggest that this lost pyramid was in fact destroyed in the late 18th century and the pyramids stones were utilized in the construction of the city of Cairo so in itself Cairo may have been built by the lost pyramid. We know for a fact that there are numerous structures that still remain hidden beneath the ground. Perhaps the remains of this majestic pyramid are also located hidden underground waiting for the day someone lucky enough will stumble across its glorious foundation revealing to the world that Egypt is still filled with mystery and that we are on a long journey to discover the real history of Egypt. This seems to be common practice in Egypt these days who seem to hide history based on the notion it is not in line with what the world has believed of this region in particularly if they cannot squeeze the historical elements into the dynastic period of Egypt then they destroy, bury and even deny the existence of major feats of engineering brilliance that not only predates the dynastic Egyptians it also predates the great flood and takes history back to the true timeline of our civilization when human beings literally walked among the gods the golden period a period so grand in design and achievement that it is not so easily swept under the sand the evidence is certainly there for the fourth pyramid of the Giza plateau who built it and why remains the greatest enigma in the history of our civilization regarding lost history and forgotten civilizations what do you guys think of the evidence for a fourth pyramid the black pyramid comments below and as always thank you for watching


My name is Susania Nunez and I'm from Tri-Cities, Washington and my life before coming to church was a lot of darkness, a lot of loneliness, a lot of anger because of my parents' divorce, a lot of confusion. It led me to bad decisions when I was a teenager. It led me to using weed for four years. It led me to bad crowds which got me pregnant at 19 and as soon as I found out I was pregnant the father was sent to prison for seven years for a record of his past history that I had no idea about just growing up to be a single mom and just having a lot of bitterness, a lot of anger, not understanding why I was going through that. How I got invited to Hungry Generation was through one of my friends that I haven't seen about 13 years and I came in contact with her. Her name is Sylvia Cuevas and we met up, she came over and she talked a lot about Hungry Generation, how good of a church it was and how it would be good for me to come and join and events kept coming and she kept inviting me and kept inviting me and I just got too busy and I didn't come so one Wednesday when I was actually really down I decided something deep inside told me to get up and get ready and go to church and I called her and I let her know hey I will be coming this Wednesday and I've been coming to church every Wednesday after that and every Sunday for homework. On August 10th there was a water baptism going on and I decided to come and I felt like that day I got saved, that's the day I gave my life to God was because something inside of me truly let me know and told me that I need to give my life to God that it was time that I just go up there and give my life to Him and the difference between before and now is I feel at peace, I'm still working on some areas in my life but I feel like now I'm letting God deal with a lot of them, I'm doing a lot of more praying than stressing over the problems or crying myself to sleep or overstressing and thinking and analyzing things from every area that I shouldn't be stressing about and I am doing better at a lot of areas. The reason I'm getting baptized is for me to commit to God that I am going to follow Him and I mean no one's perfect but I will do what I have to do and grow with Him in every way that I can to serve God and the reason why I want to get baptized is not only for me, it's for my children too, they could see a better mom, a better side of me to for them to watch me grow into God so they could also have a good role model as when they grow up they know and they have an understanding of God is really true and He is the only person that can save you. So my goals are to go ahead and reach out to anybody that's going through depression, anybody that's going through loneliness, anybody that's going through a drug addiction or anybody that's a single parent out there that there is hope and you know just to be able to reach out and let every one of you know that there is hope out there and to not be afraid and just go and seek and the only person that will actually answer all your prayers and help you through any of those problems will be God. Can you introduce us and tell us your name? My name is Disneya Nunez. Okay, and Sina, have you received Jesus Christ as your Lord and Savior? Yes. And now do you promise to follow Him all the days of your life? Yes. Now based on your confession we will baptize you in the name of the Father, Son and the Holy Spirit.


Thank you for being back on our show, Think Tech Hawaii's Human-Humane Architecture. This happens to be our 302nd episode and the accumulated viewer you are, you see down there. It's going to be the two of us around our extinct volcano of Diamond Head. So it's you, DeSoto, and you're also designed Diamond Head home. Hi. Yes, good morning. And it's me nearby as well in the Waikiki Grand. You could throw a stone to reach us, but we won't. And we're reporting in these crazy days in the desert of Nevada with a burning man, a massive flooding as it is in Libya. And these are the hot arid where you think that you wouldn't have. And obviously here that's what we continue to address where you think it's lush and moist.  So that's what we want to continue to talk about if we could get the first slide up for that one. And we won't have any solutions or answers, but we allow ourselves to ask many, many questions. And we want to encourage you guys to do that along with us. Just keep the heart and the soul going. And this is basically a couple of notes that went through our minds here catching up on where we ended up last time. And our utmost expert in planet and people-friendly architecture who was sort of fusing our two cultures, the American side in you and in the German in me, Matt Noblett, who also through his wife has been on the islands here for many decades. He will join us next week. But he got us, he kept us updated about a, you could say, extinguishing waterways image, right? Where was that? Tell me again, I don't remember what we were talking about. He sent us a hello from Venice in Italy, which again has trees out of water. So this is obviously a good, you know, side effect would be putting out fires. We have Hawaii Kai here, who's been driven different differently, not by that in mind. But obviously, if you have water in the streets running, we got Alawai here, which isn't quite as close to, but Alawai is also kind of the double-sided sword because it kind of drained and dredged Waipiki, which used to be all wet. And now all the water goes into Alawai, and it's very filthy and dirty. And so that's, you know, not as easy of a, again, we won't have any solutions, but a lot of food for thought. So let's jump right in. And I want to do, thank you, Michael, our producer following us. There's a star advertiser link bolt down there. I read that.  And now in the news, if you follow it, it shows the different shades of the tragedy. This one is about the Filipino people on the islands here, which play a large role ever since they came about 100 years ago. And I have to say, wherever I run into Filipinos, might it be our ray of all trades here in the Waipiki Grand, or might it be my students, as you see the show called below there. This was Chris Chupueta, who was a jungleism advocate. And we did a show with him about that they're all great, hardworking, the hard at the right place and totally talented. So this article is about that they played a large role in running the tourism in Lahaina. And now they're worried about not making it anymore. And they have this example of this lady here who was able to, you know, barely buy a home of $500,000, five bedrooms. And now she's worried about that she's not being able to get this back, that she might be bought out.  And now, you know, they were saying maybe we have to go and move back in with mother, because we can't make a living. So along these lines of what can we do to rather than saying, okay, bring it all back to how it was, maybe that sheds a light on that how it was, maybe it wasn't so perfect. And maybe it just looked perfect from the point of view of a tourist walking through it, and all cute and pretty, but behind the scenes as we were debating last time for cultural reasons, you know, maybe there is a challenge there too.  That's a different layer of tragedy here of human existence that we want to just throw ideas out there of very, very unconventional, non-traditional, kind of edgy, intentional as to push us to think as you like to say and kind of quote, you know, quote, unquote outside of the box, right? Yes, exactly. And I think one of the things you touched upon is another major consideration. You know, we tend to focus. I've been focusing my ideas on the commercial part of La Hina, because that was the most famous part. That was the part that generated the income. So it's very important. But there's also 90, something like over 90% of the structures that were destroyed in La Hina were single-family homes as well as some apartment buildings too. And this is something that is connected to the people that you just discussed, the Filipinos, but there was also, to my surprise, a fairly large Spanish speaking population of people from Mexico and people even from Argentina. And I didn't realize that there were so many such people in the town of La Hina. Well, obviously, some of them also being immigrants were probably not legal immigrants. And so they are in a double bind of having lost their jobs and having lost the places to live, but also being scared of being found out and potentially deported. So this is a whole other human aspect to La Hina that until this disaster occurred, I was not aware of. So again, how do we find the places? How do we find the money? Where do, how do we deal with rehousing all of these people? Because again, if there, as you just said, if there isn't housing there that people can live in, then you don't have a workforce. And if you don't have a workforce, then you don't have the support for the hotels and the retail and all of the other things that we're bringing tourists to La Hina to spend money. So it is an incredibly complicated situation. Yeah, it is. And it's on top of what already was complicated to begin with on all islands that we will later on show a civil beat article, you know, quote that talked about homelessness on Maui. And so I also threw in in my notes here the name Ankeny. Ankeny used to be my neighbor, my urban nomad neighbor who at Duke's Beach, which is in front of Porto Rossi Park, I ran into every morning and we started to be friend each other and chatted, you know, and he was basically hanging out there on the beach and we talked. And he told me that all he had was reclaimed and repurposed, found objects, and that he said he just wants to live very minimally. So his footprint, by the way, was very low. And so and I was asking him if I could have the emerging generation come and talk to me. He said, yeah, very much so. When I returned, I didn't see him anymore. He's gone. And that happens, you know, and with all the drama and tragedy of 115 people killed, you know, at once, it's a little like when an airplane comes down, right? It's a shock because it, you know, so many people at the same time. But at the same time, we forget about the almost daily automotive fatalities out on the streets, which you see a note here or someone got killed and got killed, but they accumulate and they build up, right? So we have this massive problem that is intertwined. And so the solutions could and should be for all of these. So again, learning from from Ankeny is live a absolutely essentialized lifestyle of providing main shelter. And that's, you know, we talked about maybe it's more, you know, less of a western tectonic, heavy construction. Maybe it's more lightweight, which by the way, and we, you know, met and I had been invited by you to stop by work and look at the Holly, the oldest Holly you have in there, which is a pretty impermanent structure that also because of natural catastrophes, often there were, you know, strong winds and and hurricanes and they got blown away and they basically rebuilt them again. And so we talked about maybe out of fabrics and we got excited about out of this material, making that material here and other things. So now here, these images here is elevating that on top of what we said. And in Germany, these car roof tents are really becoming popular. Don't get us wrong. Don't even think we're, we're, we're as crazy to say, you know, we on the burned out cars, you put some of these pens is a lot of, you know, sensitivities about that. In fact, you know, one of the staff people of the Holly Colani, which Ron blessed us with the one of the most human and humane hospitality design projects, one of the valet people Mark basically said, don't build there at all, because all the bones are basically all the dust, all the debris, everything is basically bone powder. So don't even think that's just one, you know, informed citizens opinion there. But again, we're, we're talking maybe not literally and, and figuratively, but more metaphorically about how could we basically elevate yourselves literally and figuratively. And, you know, speaking about this is what if anything these shows are about, you know, encouraging people and lifting up their spirits and giving them hope. And so hopeless situations.  And then the GDR, one of the sectors when you got us back on our feet, you know, you had to give to the allies of the Russians and they had one sector. And that didn't work out so well. And people in there basically then also try to keep the spirit up in this dictatorship. And they were actually the ones as I took this picture here, the predominant picture on the left of this slide here is from the equivalent of the Honolulu Museum of Art, which is the Neue Pinakotek in Munich that has this display here for you as the museum guy and the historian about camping culture in the GDR. Where, and, grantedly, not everyone was able to afford this goofy Trabant that we did, you know, point out in the automobile architecture show volume six, show quote up there in the middle top. But, you know, the ones who, you know, waited long enough and were saving money to buy one of these goofy ones, then they had they started this tradition of putting a putting a roof on top of it. And it reminded you of another episode, a pre-episode for the automobile architecture. That was the vintage VWs that you are a member of. And it reminded you of that. Why did it remind you of that? Well, the Volkswagen van was the first large boxy vehicle that was sold in the United States that was quite popular. And after it began to sell in the 1950s, the American companies, American car makers, started making large boxy vans themselves. But what the Volkswagen had that was also very notable for what we're talking about right now is something that the United States companies didn't make. And that was a pop pop in which there was an accessory built onto the top of the van that you could open up as a sort of a little tent-like structure. And that gave you a little more height. And it also gave you more air circulation if you were camping inside your van. And of course, a van is like a room on wheels. It's not curved like an automobile. It's more like a box. So people not only traveled in these and not only used them for commercial purposes, they ended up living in them sometimes, particularly when the hippie movement got started. Then that's when people were really making use of the Volkswagen vans with the pop pops. So how could this help? Again, we're thinking about the $500,000 home that this Filipino family was barely able to afford with five rooms. So now it seems like they would have to go back home. And maybe rather than not doing that, maybe this could be an interim solution to basically because we put out the price here of one of these roof tents. It's 1.5 to 2.5K. So that's something maybe that's reasonable for, again, the interim time. And our consultant, Lindy Robelo, who unfortunately I don't pay enough banking at my University of Hawaii Federal Credit Union. And now her rent in her public housing is threatened to be raised. And she said, well, they're going to make me go back to live in my car way she used to live with. So she knows what it means in a car to live. And in a car, it's hot. It's like a tin can. And that's why these pop up roofs and stuff like that try to aerate and ventilate it. So obviously the roof, the tent on the roof of something is cooler. And it's off the critters. So it has advantages over to be on the ground in a car. So you're just safer also from other threats of water and flooding and things like that. So that's why we wanted to throw this out is to maybe put your thoughts along the lines you might want to think along these lines even more. So a very small show quote at the bottom in the middle gets us to the next slide because this is what Bucky Fuller called tensegrity versus gravity based structure. So certainly it has to rest on something, but it's structure itself is very kind of lightweight. And another thing that sounds maybe totally like when when Matt was cautioning us rightly so and saying, well, it's not as easy. You throw up a tent and then it's going to be happy live quoting Matt, right? So it's also not easy and and you know would be silly to think, okay, we just put a hammer between two palm trees and life's going to be good or good again. It's not like that. But rather than again trying to say, okay, we built pretty heavy to expensive. And why don't we build lighter? And there is a tradition of hammocks everywhere in the tropics. And again, everything take it with a grain of salt. This article where we got the middle provocative picture front is title itself. Can a hammer a palm tree? So there's multiple levels to the literal part of that. But the point is what we're making again. Can you do architecture that's more along the lines of your ancestors, which is more impermanent than being permanent, which is also more easy breezy. We're seeing behind you the window open. We also see a Dyson fan to the left and we see your dog and we hear the bird. So along these lines, can we do something that is more airy? And another example of that is from other areas is the frame at the bottom left, almost there on the grass. This is a, this is a Shorj Haldoy Ferrari chair from 1938 that became very popular in mid-century modern architecture. When Ron listens to us as one of our most loyal audiences, it reminds him of having been in many of the case study homes that he designed. And it's a metaphor. It's an example for doing the most, create something you can sit on with the least material, with the most reduced tube frame steel. And there's also the guy I'm blanking on his name, but we covered in on shows who was using tube from the military, right, and made these outdoor furniture here on the island. Are you, I'm blanking on his name, or do you have? I am too. Now that you're asking me, but yes, that is something that was made after World War II here in the Hawaiian Islands. It's okay. Yeah, it's okay. And you know, what is the chair in the world? For me, it's metaphoric because I used to own that frame and the cloth with it.  And she did it for like a dollar. And it was actually initially mad and thinking, okay, why would she sell this so cheap? Now I think I have to say it was good thinking her because she was giving it away, hopefully to someone who was more in need of it. And so, you know, down there at the very bottom left is just as of yesterday. These are two shots from automobiles or vehicles for thought. And I was given our P.I. mobile by some neighbors here in the Diamondhead area, David, who told me it's likely former First Lady Jean Arioshi's car originally, but they gave it to me as a donation almost for a little money. And we now gave our C model to Roxy, who was our front desk lady here, who also, we don't pay enough. The hotel does not pay her enough. That is the problem actually of the underlying problem is our greediness, our thriftiness. And this gets us back to Ron again, to the chokeboard at the top right, because Ron was doing it right. His design was all-encompassing human humane because he created something that the company decided to pay its staff well. And Mark and Terrence and their third friend, they just came from a golfing trip that they do every year on the Big Island. The hotel pays them so well that they're able to have a happy and healthy life. They got houses. They can do vacation. And I think, you know, the more I do research on that, the more I talk to people. That's the underlying problem. First of all, we need to, you know, get people decently paid. And then they can basically then not spend on the money on something that maybe is not worth it, which is Western style architecture. So the two raise the pay, which the Hale Kalani is able to do.  But come on, you know, you can't be cheap, literally. And figuratively speaking. So raise the wages and lower the cost. And it's only necessary. It's only possible if you lower your standards. But lowering the standards doesn't necessarily mean compromising on comfort if you take advantage of the unique climatic conditions that we have, right? And there's another, the other Martin I'm happy to have in my studio right now, talking Spanish, he's from Colombia and not the state, but the country of Colombia. And he was very enthusiastically telling me about his culture where they keep it small, the houses. And when the big families come, they all throw up hammocks. And everyone is a happy camper there. So rather than the Western bedrooms, and they're going to have so many bedrooms with so many beds in there that have a large club and footprint, right? Keep it lean and mean. And the very show quotes at the bottom right is my hammock experiences because my dad had in the 70s an indoor hammock with a wooden frame, sort of like this one. And don't get us wrong. We're not encouraging you to buy on Amazon. Amazon is a tricky beast. This is just an image, you know, taken from Amazon. But again, the price, something like that, is rather affordable. $200 like that. And I had my cousin stay in that once. And she recently, family affairs, not that it matters, but she got back to us and asked for her images to be deleted for my father's birthday anniversary. We did that, go figure. And she was already complaining back then, oh, she couldn't sleep in that hammock. Well, my buddy, Dan Kubrick, who is our mentor for our to be continued comparing Chicago to Honolulu when he came over around the time, as you see him there, back then in the show quote bottom second from right that long ago, he was more than a happy camper as they say, right? And take that saying literally, right? He said a hammock is just right. So what we're saying is simplify, essentialize, and that might open up opportunities for a new architecture that could free the people. So you're not going back to the before, but you're actually going towards something even better as you put it as the aspiration last time, right? Yeah. And I think this is again, what you mentioned earlier, the idea of, okay, this is an unprecedented situation in which all of the buildings and all of the contents have been destroyed. What do we go with now? We have an opportunity now that even though it came from a tragedy is still an opportunity. So the idea of using different techniques, the idea of building different types of things, the idea of using different types of materials are all things that can be explored now. And I'm going to bring this back to something you and I have talked about repeatedly aerated concrete as a type of building material that doesn't burn, that is insulated against heat, and Lahaina is well known for being very hot, and trying in various ways to either encourage or sometimes even perhaps mandate those types of materials in the rebuilding so that there's never again a disaster like this in which everything burns. So not only thinking about the comfort of people, not only thinking about reducing our footprint in the world, but also preventing yet another tragedy, all of these things are considerations for this rebuilding process, which now is in our future for the town of Lahaina. Yeah, and we want you, our dear audience, to also take a fresh look at things and be more conscious when you walk around or you drive around. So the picture I took yesterday at the very bottom left, you recognize that it's right down your road. And so there is a little RV standing there that's sort of illegal. And that's one way. And then next slide for the remaining two minutes, just kicking it off with us and then we would have to go back to that one. That is approaching your road from the other side coming from me. This is the high street. And this is something that was on the news, being very controversial as well as another person who came from another culture and tried to make a living here and had a food truck and basically got evicted from his place and didn't know any better as to take, oh, and his son got sick, as he says on air. So he basically, he said, rather than becoming homeless, I took immediate action and I built on top of my food truck, which was a big outcry. And I, do you remember from driving home, having been driving by it because I don't know, it must have been when I wasn't here on the island? Possibly, but yes, I remember very well. And there was a whole situation of that street having permanently parked things on it because it was a private street. And that's what this structure was, the vehicle and the structure. So here again, why this might not be taken or it might not be a good idea necessarily to say this is a good wrong model to imitate or to duplicate, right? But this as a provocative proposition to think about elevating things and tree houses, the other pictures are wrong. We want you the audience then for the coming week that you have, because we have to call it good now for today, but please give a thought about tree houses. Give that a thought and what kind of potential could there be within tree houses. We will walk you through the ones that we arranged around the main picture here, which is our experiences and findings and dealings with tree houses, both where we are from and what we have found as tree houses. You pointed out there's a Lahaina tradition of trees there and there is actually the oldest Banyan tree on all the islands of Hawaii is in Lahaina and we have one here in Waikiki next to us that used to have a tree house and there's more here to then continue along the lines. And you please do your homework as well, make us think about what potential for getting our spirits and not just that, but the situation back up in Lahaina and elsewhere here in Hawaii, in other tropical climates in the world with similar situations. So we see you for that. And Matt, back and until then, please stay altruistically attractive. Attractedly altruistic. Bye-bye.