Okay, good evening everyone. I'm going to go ahead and get started. Today we're going to solve the big mystery of whether Drupal can be the backend API for a desktop application. Before we dive in, I'd just like to give a brief overview of my experience, my background, as well as my co-presenter, Vince, who wasn't able to make it today. So I'm a principle full stack developer at Pegasystems. I'm also a CTO and co-founder of MyStar of Neverending Solutions. I have a deep experience in decoupled architecture. And in terms of education, I have a bachelor's in computer science from University of Rochester and a master's in technical entrepreneurship and management from the Southern Business School. I have over 10 years of experience in JavaScript, PHP, Python, as well as experience in Drupal 7 through 10. My co-presenter, Vince, is a developer at Neverending Solutions. His expertise is in UI UX. He got his bachelor's in computer engineering from Macquarie University in Uganda. And he also has over four years of experience in PHP, as well as experience in Drupal 7 through 10. So before we dive into the idea behind Drupal supporting a back-end application, I'd like to go over the idea of what a decoupled site is. So everyone's on the same page. So at a very high level, a decoupled site is when the content is separated from the front-end in terms of the components, look and feel of the site, what goes together to build the site that you're seeing. The front-end is completely separated from the data that gets pulled into the site to form the components and form the look and feel. So when those two things are separated at a very high level, a decoupled site is formed. So how I got experience in decoupled sites. I didn't start working on decoupled sites until I started at a media current. At media current, I was a lead on the media current website. So media current website said decoupled site. So I had to learn Gatsby and I had to learn how Gatsby pulled in information from Drupal, the Drupal back-end, and how it efficiently generated the site after every build. And as the information, the API endpoints changed, had to figure out the best ways to generate the site speedily, efficiently with a performance in mind. It didn't have any experience at all with decoupled sites before then. But working on that made me pretty much fall in love with decoupled architecture and it started opening my eyes to how powerful decoupled architecture can be and seeing Drupal as a content hub instead of just a website. So what really got me deeper and deeper into decoupled sites was as a lead at redeveloping the media current site, I was assigned a task of coming up with a plan to improve the site. So I had to come up with a way to improve the nature of how it was put together, whether it to be changing from the front end of Gatsby to a new stack site generator like next year or whether it be changing how the endpoints were exposed from the Drupal end. So I did extensive research through trial and error. I was able to learn all the components of what it took to build a very efficient decoupled site and present the idea to the media current team and CTO. The second thing that really showed me the power of decoupled sites was the Penn State project, another project that I was one of the leads on at media current. It is a very large and decoupled site, one of the largest in the world, if not the largest in the world, and working on this site seeing how Drupal could power a site of this size and continuously feed information and how the front end could have successful builds over and over successfully really showed me how powerful Drupal could be and inspired me. And that's how the idea started forming. So how they did it, a little bit more insight into the structure of how the decoupled site works. So on the Drupal end, JSON API is one method of exposing information via endpoints. There's other ways, but that's the most common way. So JSON API will expose all the information for nodes at specific endpoints and all the information associated with those nodes as well. So you'll get all the information you need to pull in on the front end. So the front end can either be in Gatsby, Next.js, or any other stack site generator that you want to use. What Next.js or Gatsby will do is it will query using GraphQL or whatever method that you want to use to query the information. It will query all the information from those endpoints and then pull that information into different components that are defined in the front end theme and the stack together to make up pages in the site. It will dynamically pull that information in. So the site represents an accurate depiction of all the information that's entered on the front end.  So at a very high level, that's how the magic behind decoupled sites work. So the big question that we have here today is, can a similar concept work for desktop applications? Can we utilize a concept like that to spin up desktop application as a web developer? The answer so far is maybe. We don't want to give any spoilers yet, so the answer is maybe. So do we have any questions so far? Okay, if not, we can continue. So how do we accomplish this? So we'll need to have an app idea that can challenge Drupal in a way to see if it can be a successful back end application to not a simple desktop application, but a desktop application that offers at least a little bit of complexity. So the idea that started formulating has to do with desktop application privacy, which we'll go into in the next slide. But the stack which we'll also dive into is Drupal, ElectronJS, using the Quasar framework React as well as AWS S3 storage. So the app idea. So the idea formulated with me identifying a need and a market. So privacy is very important to write. That's why VPNs became so popular with internet privacy. So I noticed this need for desktop applications. So desktop applications can access any files on your computer. They can access personal information, whatever they want. A lot of people don't realize this. So narrowing down that segment into the gaming segment, a lot of gamers realize this and they complain about it constantly and there's not too many solutions for this. Narrowing down the segment, even more specific game Overwatch, which I heard a lot of complaints about the game, saving people's personal information and just completely storing it and being able to track anyone that downloads them in the game. A lot of people were upset with this and they wanted privacy. And it's an easy problem to solve. There's a very easy problem to solve with JavaScript. You just need to be able to build a desktop application and be able to reset those values. It's that simple. But as a Drupal developer, not able to easily build a desktop application, I felt like I was pretty much limited to Drupal. So that was the idea. These are just some simple values you can change with JavaScript or using Windows PowerShell commands or registry edits, which you can access through JavaScript Node.js. So JavaScript front-end developer can change a lot of these values and these are values that games, desktop applications read consistently and save for about users. So that's the app idea in terms of features of the app. But the features that Drupal can support. So let's say you want the app to not be free. Let's say you want to have it be on a subscription basis, access key basis. Can Drupal support this? Let's say you want to have people be able to buy the application for a day, a week, a month and use Drupal as the backend API for that. Who knows if Drupal can support it, but that's a requirement that we'd want for the idea. We also want the application to be able to handle registration. So users should be able to open the application, register the application, and then when they register the application, a Drupal user entity should be able to be created based on the information that they enter in the application. Hopefully Drupal can support this. Who knows? If they can register, we also want Drupal to be able to support the login. So after they register, they should be able to use the credentials that they registered with to be able to login and validate the credentials. So if they match the user credentials, username and password, that's within the Drupal database. They should be able to login as that user and gain access to the application. So we'd want Drupal to be able to support this or also be able to support this. There's a lot that we're already asking of Drupal. Going back to Electron, so as a Drupal front-end developer that knows JavaScript, I wanted to find an easy way to build a desktop application without having to reinvent the wheel and learn something new. I know JavaScript, so figured out that you can use JavaScript to build desktop applications with a framework called Electron. But I still didn't want to learn all the intricacies that Electron offered, and it felt like it would take way too long. So did a little bit more research and found a framework called Quasar. So with this framework, you can actually generate an Electron application with just a few commands. You just have to install the NPM dependencies with Yarn. And you can just, with one command, you can generate a desktop application template just like that. So that saves me time. And then with the front-end of the application, what's even better is that it offers an extensive library of components that you can utilize, just to plug and play. So if you wanted to build, let's say, a login functionality with a field and buttons, you can just pull in those components using the framework, and you don't have to build them from scratch using Vue.js or React or whatever you want to use. You can just use those components using the library, pull them in, and you already have all the components that can put together the front-end of the application. And the next thing you'd have to do is just tweak the CSS a little bit and then you can make it look exactly how you want the application to look. So that was the option I went with, just to save time, because I did not want to reinvent the wheel. I didn't want to spoil it, so at this point it's going to be a little bit of a spoiler. So Drupal is in the stack, so it may be a spoiler to hint that it maybe couldn't accomplish this. So the reason why we ended up using Drupal is because that is where our expertise is at. Drupal already proved itself within PSU and previous projects that I worked on, that it's a very big powerhouse that can handle whatever we put in front of it as a challenge. So it also offers scalability. So if more and more users join the application, Drupal can handle it very well if we want to populate the application with many access keys. Drupal will handle it very well. It's very good at handling structured data and it can scale very well and easily. So that's the main reason we chose Drupal. So AWS S3, this is a more simple reason for choosing this. So if we wanted the Electron application to offer automatic updates, you can easily integrate automatic updates using Electron. The main thing you have to do is point the Electron application to a public URL and so we use semantic versioning. So all the Electron application will do is look and check to see if the installer within the URL, so the public file path, if the installer has a version that's greater than the current version, it will prompt the client that there's an update and they can just click Install Update and then the updated code is automatically downloaded on the user's computer just from that. So we use S3 to push updates or if there's a new update to the app, we just put it into S3 and then all the users using the application will see there's an update, they download it and they get the latest version of the code. So the interesting, we're starting to get into an interesting part now, so how Drupal would power the access key portion of the application. So there's many ways to do this. The way we did it was we created a custom access key content type and with one field, we used a key value pair field. So there's three types of keys, day keys, week keys, month keys. Very simple. The type of key would go into the key field and the value of the key, which would be just name of the application just a random string goes into the value. If a key is redeemed, the node is unpublished. Very simple, easy way to handle if a key is live or not live. Next thing we'd have to change is adding a few fields to the user, the user entity. Because the users are the ones who redeem the keys, we'd want to be able to associate specific information with them. So the first thing and one of the most important things is adding a date field onto the user entity and that's going to represent the key expiration date. So very self-explanatory if a user redeems a key, if it's a day key, the expiration date would be added to that field. The next field is a little bit more complicated. It's called a hardware ID field and this solves an issue with account sharing. So I'm sure at least some people in this room have shared a Netflix account because they didn't want to buy one for themselves. This is good for the consumers obviously but it hurts the developers, people who sell the product and there's an easy way to solve this for desktop applications. So you're able to get unique identifiers off of computers like I was mentioning before. So we do this as well. We use commands from Node.js to get the unique identifier off of the desktop computer right as the access key is being redeemed and then it's saved into this field in Drupal. Now that we have that, if someone tries to log into that account using a random new computer or they try to share it, we can check if the access of the hardware ID value in this field is different than the one that's being checked and passed in from the front end then they don't get access as simple as that and that's the importance of that field. The last field that we added is another key value peer field to the user entity which represents the keys and that I use redeemed. So every single time they redeem my key we save the type of key, so the key, the value of the key as well as the date that the key was redeemed on. So there's two very useful contrib modules that we utilized for some of the REST UI functionality, the REST API functionality. So Drupal has built in REST API and it's not as easy to configure. REST UI makes it a lot easy, it provides us with a UI to configure different REST endpoints so we use this UI to configure the registration and login endpoints and any customization that would be needed there. We also use, utilize the RESTful logger module which is also a very helpful module because it pretty much tells you every single communication that goes from the client to the server which is huge because if there's a lot of users using the application you're going to want to monitor and know what they're trying to send into the back end and it's going to be very hard to tell unless you have a way of doing it, developing it yourself but the RESTful logger module gives you a view that shows every single request that gets sent to the back end with all the information about the request so what's sent in the request the information about the computer like the IP address that is coming from the request so anything you'll need to know to monitor what's going on between the client and server is logged within the RESTful logger module and you get that functionality just by installing the module which was very helpful and it was a huge time saver. So this slide is learning from so learning from my mistakes so being comfortable with decoupled sites I relied on JSON API a lot and I just by default I just was so used to making everything public and then just querying information from those public endpoints and doing whatever I wanted with it so security didn't really come to my mind when I was working on this so I exposed some information like access keys all the access keys that people would want to buy they're exposed publicly at a specific endpoint and a few pieces of user information was also exposed at an endpoint so I treated it kind of like a decoupled site because my expertise was in decoupled sites this obviously is very bad very insecure you don't want to expose all this information to the public so after talking with some developers I was able to quickly fix this and realize how big of a mistake this was and how I saw this was creating custom endpoints to resolve that issue so I was able to remove all the public endpoints and Drupal actually allows us to create custom endpoints through plugins so if you look at the code on the right side simple simple plugin that you can use to create the custom endpoints and in the URL path of string you can see you can define what the endpoint is so the front end would just send the request to that endpoint and then the information that the front end sends in would be in that access key string at the end so with this with this endpoint I'll go into a little bit more detail about the power that you can do just from PHP in this one plugin so access key that's passed in from the front end and it looks like one string and it is one string but multiple things can be passed in that one string so what the front end actually does is pass in three values in that one string and separates those three values with a specific separator so there is going to be an order that the front end always sends these values in every single time and the order is in Drupal user ID dash dash the hardware ID dash dash access key those three values that's all we need to perform a lot of actions in terms of redeeming keys so once that's passed in with the PHP code we can just check the values split the strings based on the dash dash and assign those values based on assign those values to what they actually represent user ID HWID and access key so now that we have those three values we can check to see if that Drupal user exists if the Drupal user exists we can check to see if the access key exists so if it's a published so if it's published and available then we can check to see if the hardware ID passed in is equal to the hardware ID that's stored in the user table we have full access to everything within Drupal right this is in our custom plugin so we can do whatever we want so we can do that if all checks out we can add the time that's associated access key to the user's profile and then just add that it was redeemed within the key value pair field on the user profile so just like that we can perform complex actions such as redeeming keys just from a custom plugin and if we wanted to add a little bit more security behind it or extra checks we can do that as well the only thing limiting us here is just our comfortability with PHP so I'll leave the demo to the end in which I'll demo registration and login if anyone wants to see access key redemption they can stop by and touch base with me after just so we can get through the security part but does anyone have any questions so far? okay so I will continue to security so for security it's very important that we use SSL these certificates are very essential wouldn't think that it's important because not many people are going to be logging into the backend of the application especially in this case when there's not going to be content authors there's not going to be really many people besides administrators going into the backend but still essential to stick to the basics of security best practices because it will prevent security attacks that can happen in the future another thing that's even more important is API rate limiting so what this means is that we want to limit the amount of requests to a certain number that comes in in a certain amount in a certain time frame and we do this so the API does not or the backend does not get overloaded with more requests than it can handle because if it gets more requests than it can handle that will lead to security vulnerabilities IP address limiting and banning this goes with user input sanitation so I'll go over user input sanitation very quickly so with user input sanitation we want to be able to sanitize and control what's submitted from the front end so in the desktop application if someone tries to submit something malicious or something that's out of format we want the front end to be able to handle that and format that in such a way to prevent anything dangerous from being submitted from the backend but if there's an issue with the sanitation if something gets past the user sanitation or if we see someone trying to just submit inappropriate things over and over to the backend we can see the IP address that the requests are coming from and easily just ban them this is a functionality that's included in Drupal so we can ban the IP address and we can see the IP address like I mentioned before from the REST restful logger module so we can ban the IP address and prevent them or make it even harder for them to submit and do the malicious things that you're trying to do so that also goes hand in hand with limiting what the client can do so with limiting what the client can do REST endpoints this is where you understand PHP and the power behind what you can do in the plugin really works wonders so let's say that something somehow goes past the user sanitation and hits the endpoints as a Drupal developer you have full access to what is coming in to the endpoints so you can perform as many checks as you want to make sure the data coming in looks exactly how you want it to look before performing anything that could be harmful to the database and this creates a lot of limitation on what the client can do because we have the user input sanitation and then we have the extra validation checks we can do on the plugin end through PHP to make sure that we can prevent anything malicious from happening so as a worst case our worst case scenario we can also have geo filtering when we're under a DDoS attack and what when you're under DDoS attacks the attacks are pretty much from a singular area so if you filter traffic from that singular area there's a very high chance that the DDoS attack can end so as a worst case scenario you can utilize geo filtering as well so now that we discussed security on the Drupal end what's even what's just as important is the security on the electron application end and as a web developer this is not something that we're used to especially a JavaScript developer if you're writing JavaScript code or front end code you're used to the code it's used to being okay with the code being public things are usually open source supporting the community sharing code it's kind of in our nature with Drupal and with as front end developers but I realize the hard way that this is completely different within desktop application development especially if you work let's say once a year to build a desktop application you spent hundreds of hours to put together this code that has value that solves a problem for a specific customer base you want that code to be protected because someone can easily if it's not protected someone can easily steal your code, steal all that hard work and replicate it and this is something that I had to understand come to understand I'm mainly front end web or mainly full stack web developer focusing on Drupal it's completely different playing field with desktop app development so with electron apps you can actually right click on an electron app open file location and then the app is bundled into a .sr file and it stands for Adam Shell Archive Format and this offers level of protection and just because of the fact that people are unaware so if you see in a .sr file you're not going to think that you can extract anything out of it because it's not like a .zip file or .rar file or something that's common that you extract things out but if you do a little bit of research you can actually figure out you can download something called 7zip right click the .sr file and then extract the full source code using just a 7zip the code that you worked 6 months a year however long you spent they can get full access to it in 20 seconds just with 7zip and that's pretty scary so there's a few solutions to this one solution is a .sr armor so this is encryption for that .sr file this is available as an npm package it will encrypt the .sr file within the build process of electron so if someone trying to gain access to your code right clicks it and tries to extract with 7zip they'll actually get errors on top of errors but this is not a full proof solution obviously we have google someone can google how to bypass .sr armor protection and then they can just follow the guides so that's not enough you have to layer multiple things to fully protect yourself so the next thing is obfuscating the code so this is very powerful it turns the javascript code into something that's very unreadable it's very hard to reverse engineer it looks like a lot of zeros and x's i'll show what looks like in the next slide but this is still possible to reverse engineer this if someone was really persistent so my recommendation is adding a third layer of protection as well so using npm plugin to transform the javascript code into byte code so once you transform it into byte code then it's very hard to reverse engineer and you will be very safe you can feel very safe and confident with your code and it's highly unlikely that someone will be able to gain access to it so to show what this looks like so this is what it looks like if you use the obfuscator to secure your code very hard to tell what it's doing it's hard to reverse engineer this and then with the byte code everything turns into byte code besides strings so this to your actual code very very well protected so a combination of all three is what I recommend so any questions? ok so I will go over the demo now and I will show login and registration and then if anyone wants to see access key redemption and anything else I can show after the presentation so we will just enter username email and just a password click sign up and it will load for a bit and then we will check on the drupal site to see if this user entity is created so the next screen you will see is access key but we will refresh drupal site and as you can see on my drupal site a new drupal user is registered right here and we will see if I can login using this drupal user just by logging out and then I am logged in and then prompted for the access key and that that is the end of the presentation


How can I use competencies in my Moodle site?  Competencies may be used for assessment in Moodle. A competency framework is a set of connected competencies. Competencies are enabled by default, but as an administrator you can disable them from site administration, general, competencies, competency settings. You can manually create a framework from competency frameworks. Here we're making one site wide. To add a framework to a category, you should click the More link from the Edit Category Settings page. Click Add New Competency Framework to create a new one. The name, ID number and scale are required. Use the default competency scale if you're not sure. Click Configure Scale and set the defaults to Not Competent. You can now manually type in the competencies. You can also import ready-made competency frameworks from Import Competency Frameworks. Let's try that now. You can very quickly upload a detailed competency framework. Teachers add competencies to their courses from Course Navigation more, but it's important to realise that competencies don't have to be restricted to just one single course. Learning plans may be created, which contain competencies learners must meet over a number of courses. If you plan to use competencies, it's worth taking the time to read about the roles and capabilities associated with competencies and learning plans. To summarise, Competencies define what students can do. Administrators can add competency frameworks. Competencies can be attached to learning plans owned by students, and teachers can add competencies to their courses and activities within their courses.


Hello, everyone. This is Claudio Covino speaking again. In this third video in our series of four, I'm going to be showing the introspection flow implementation with ConConnect Enterprise and Octa Identity Provider. The ConConnect Enterprise control plane hosted as a service is used to create new APIs and policies and publish them to my data plane running as a Docker container in an AWS EC2 instance. The introspection flow is part of the token validation process. At the request processing time, Con Gateway evaluates the injected token to see if it's still valid to be passed to the obscene services. The evaluation hits a specific Octa endpoint passing the received token. Based on the response provided by Octa, Con Gateway accepts or rejects the request. For production environments, the OpenDConnect plugin provides caching capabilities for the Octa's responses. However, for the purpose of this demo, I'm going to disable caching to get a better view of the flow. In regard to Octa settings, I'm going to use the same client credentials application I had created before. However, my OpenDConnect plugin has to be set with specific parameters to implement introspection. So again, here's the ConConnect Enterprise Control Plane at Minguie showing the service in the service hub with the new introspection route with the same OpenDConnect plugin enabled. So let's check the plugin settings this time. There you go. Besides the regular issuer parameter, for the introspection flow, we should turn introspect JWT tokens on as well as the introspection endpoint with the specific endpoint provided by Octa to implement introspection. And now we're ready to see token introspection action. To get a better view of the flow, I'm going to use Insonia, which is Conx's API spec editor to send requests to both Octa and Connect. So here are my two requests. The first one I'm sending to Octa, and I'm accessing the expected parameters to get authenticated and receive a token. For the second one, to consume the route, I'm using a specific Insonia capability called request chaining. In this sense, I'll be able to extract values from the response of a given request to build new ones. In my case, I'm extracting the access token from the Octa's response to build the other request and then sending to connect. Okay. Now let's send the request to Octa to get our token. There it is. And then this time we can see that the Conx request is ready to be sent since we got the Octa's token injected inside of it. However, it's important to notice that Connect is validating the token behind the scenes. In fact, he is one EC2 terminal where my data plane is running and I'm grabbing the specific Docker container log. So as you can see, since I have disabled introspection caching for the OpenD Connect plugin, Connect hits Octa for each request sent to it to validate the token. Another way to see introspection is deactivating the Octa application. Doing so, all tokens related to it will be considered invalid and as a consequence will not be accepted by Conx again. So let's get back to Octa's application and deactivated it and then we should get some 401 error code from Conx. That concludes this Octa and Conx demo. Hope you have enjoyed it. See you in the last feed of the series.


Live from Orlando, Florida, it's theCUBE. Covering Microsoft Ignite brought to you by Cohesity. Welcome back everyone to theCUBE's live coverage of Microsoft Ignite here at the Orange County Convention Center in Orlando, Florida. I'm your host, Rebecca Knight, co-hosting alongside of Stu Miniman. We're joined by Patrick Moorhead. He is the founder and principal analyst at Moor Insights and Strategy. Thank you so much for returning to theCUBE. You're a good friend of theCUBE. Thanks for having me on. I mean, it's a great show and I literally look for theCUBE everywhere. Oh, very nice. Good to hear. I probably do about 40 events a year and I'm pretty sure you're at about 30. Where are we there? Exactly, exactly. We've got a few more for you to come to in the other place. The year is not over. Exactly. So, so many announcements today. An 87 page book from the Microsoft comms team. One of the things that is getting a lot of attention is Azure Arc. Satya Nadella himself said, I am so excited about this. This marks the beginning of hybrid computing. What are your first impressions of it and are you able to see the immediate differences between stack and Arc? Yeah, so I think I would say completely expected. We're out of this drunken sailor mode where everything's going to the public cloud. Oh my gosh, and everybody is toast who's not doing this, okay? And now we're in this somewhat sober right where 80% of the workloads are still on-prem and 20 of those have gone on to either SaaS or IaaS or PAS, but it's expected. Now, Microsoft already had a full stack, i.e. Azure stack, but this takes it up a notch because you can deploy Arc anywhere on anybody's cloud. They even showed a demo of doing backups to AWS. Whether it's on-prem and I'm sure they're going to show it running on GCP as well. So Patrick, for a number of years we've been saying when you line up the big hyperscalers and say, who's doing well at hybrid? Microsoft's been at the top of the list there because they have a strong footprint in my data center. Microsoft gave everyone the green light to go do SaaS as much as you can because they're pushing everybody to 0365 and of course, Azure is growing in one of the leaders in public cloud. The announcements this week were compelling but it made me kind of rethink as I think you laid it out well and said, but we've been talking about hybrid cloud for a number of years, but we're not really there. So Arc, it's a first piece, it's only in tech preview. I think you were saying for a singular application which is databases, when you look out there and you see the VMware on AWS, Azure, Google, Oracle, IBM. You look at AWS with outposts and those things. How is Microsoft doing today at delivering for what customers need today and moving forward on their cloud journey? So Microsoft was first out of the gate with Azure Stack, they were doing hybrid before it was cool. It was interesting, for about two years when they were rolling it out or building it, they weren't talking about it. So I was thinking, wait a second, is it not catching on or do they want to put more on the big cloud Azure? But in fact, they have been diligently working behind the scenes. And while they had to show Wall Street this, hey, we're the public cloud, they were actively building out their hybrid opportunities and I do believe that when it comes to the slice of hybrid, they are leading right now. Now, it depends on where you start. I guess what I do is they're leading if you have a major public cloud. AWS is obviously there with outposts and everybody in the audience, we were all in the audience, we gasped when Andy Jassy brought that out, we kind of knew something was being worked on, Anthos as well. And I think to be a credible player, you have to have both implementations, going one way and going the other, being able to work with other people's clouds, but also notice everybody has their single pain of glass strategy. If you want to go all in on Microsoft, you have ARC. And that's really the classic Microsoft embrace and extend. Yeah, so Patrick, you said all in on Microsoft. And if I look at the enterprise, you've obviously got some Microsoft. There's probably some things you're doing in Azure, you're running 0365, there's lots of pieces in the Microsoft portfolio, but most people aren't all in on anything today. So the same thing I looked at Anthos and said, in Google Cloud or in my data center, sure, but Anthos on AWS. And no VM, no virtualized applications on Anthos either. So the same question for Microsoft is, if I'm in AWS, have a big footprint of AWS, is this going to fly or what's your take? Yeah, so it's funny, where I've wound up after 30 years of doing this stuff, is there's always going to be a lock-in. You just have to pick the lock-in that you want. Some people are comfortable with an API lock-in. Some are comfortable with a hardware lock-in. Some people are comfortable with a development environment. And you're going to pick one, just what is it going to be? The reality is in a Fortune 500, you're going to have multiple panes of glass. You just need to determine which two or which three are you comfortable with. Maybe you'll have a pan of glass for deployment. Maybe you'll have a pan of glass for ops. The interesting thing that I'm really looking for though is where this heads with multi-cloud. Because I believe, at least in my definition, multi-cloud is kind of fiction if you talk about actually managing it.  So this is a way, ARC is a way to keep, if you buy into their dev and their ops and their security, you would go all in on ARC. So I'm actually interested in what you were talking about with Microsoft going sort of working behind the scenes to Wall Street presenting this one thing, but really working behind the scenes. And then talking about being at the conference and everyone gasping at Andy Jassy. How much are companies really paying attention to every burp of these companies in terms of their competition with each other to be number one? They'll all say that they don't track the competition, but they all have these massive competitive teams that are operating in real time. And I guarantee you all of Microsoft's competitors are watching all these are here and doing that. Now, I think the best companies are looking forward trying to change the game. If they have to change the game, the entrenched vendors are really have been playing catch-up mode. If you were 100% on-prem and you're talking about the public cloud, you're going to be in trouble. I think actually Oracle's a great example of they're in trouble, particularly with IS. I see databases as a service, but it's like too little, too late, and I think they're paying the price right now. Yeah, so Patrick, thanks for teeing up the Oracle piece because one of the topics that Saja repeatedly talked about in the keynote was trust. It's actually the exponential to the environment. And if you talk about the ecosystem, Microsoft, if you look at the hyperscalers, is probably more trust than others. We talk about people wanting to break up companies. Well, we tried to break up Microsoft. Back years ago, we know what happened there. And Oracle was up on stage at Oracle, open world saying you want to run Oracle in the cloud, here's Azure, they're our partner. We actually think that was a key piece of the jet ID. I agree. Is enabling that environment. So the question I have for you is, first of all, do you agree that the ecosystem believes that Microsoft is more trusted? But what about customers? I think you actually made a tweet about it because I wonder, historically speaking, Microsoft was not the most trusted. It was the one that was right behind Oracle as to who I spent the most licensing money to. Microsoft has changed. Are they a trusted partner for companies building their IT strategy? I have to say, based on the last, I'll call it five years, the level of Microsoft trust has raised. And there are other players who make Microsoft look like the super trust zone, okay? I mean, and maybe what they're doing in breaking consumer privacy, let's say 95% of your business is advertising, right? Let's just say, what kind of company could be it? Imagine this, right? Having commercial offerings that are SaaS offerings out there, I think you do have to ask the question. But listen, I think nobody's Mother Teresa here, okay? Everybody's trying to get business, but I do believe particularly since Satya's been here, the level of trust has gone up. And I hear it from clients that I meet with all the time. Other people are on the naughty list for sure, even those 95% advertising companies who haven't let's say done something that's horrible, but it's just the notion that something could go wrong. I mean enterprises, they're slow to adopt, they're very conservative, and it makes great fun. It's important, exactly. So one of the other big announcements is Power Platform. That's right. What are your impressions of this? I mean, is it just semantics? I mean, is this just really the umbrella of a lot of things we've seen before or is it something new and different? So we did see some brand changes and name changes, but we did see some real movement here. And I like to put, even though they're different, I like to put BI, Dynamics 365 and Power kind of in the same region because it's, hey, I'm teeing up HR app for you or CRM, but then you're going to build apps on top of that. And that's where Power comes into the play. I think the RPA portion was relatively new and what they brought out, but I wouldn't say this was the big news rollout for Power. I do think interestingly enough it is their largest growth area. If you think about what, let's say Salesforce is racking up, what SAP is doing out there, even a work day, that is, if I look at the cubic dollars that are available, that is their first or second business driver. So I was expecting a little bit more news here. How about you? Well, I mean, I'm just the host here. You two are the analysts. You know what you're talking about.  Yeah, no, Patrick, you know, from the people I've been talking to, there's a mixture of some of it was pulling everything together, but there is a rapid movement. When I talk to the RPA vendors out there, it's not like they're all quaking in their boots. They're still partnering with Microsoft. We see IBM and SAP, everybody's going after that environment. Come on, RPA is the gateway drug to AI. Is it not? It is. UI path, exactly. A show recently talking about that. So back to that trust there, Microsoft is not usually making announcements that you walk across the booth and there's a few people saying, can we roll out the beer early because we think our business is ruined. That's where some of that trust is in Microsoft. But that being said, it was curious to me that they didn't have any big partnerships announcement. Last year, McDermott was up on stage and he's changed companies since then. But there was a couple of small open source announcements, but not any large partnership announcements. So ecosystem, majorly important. Any commentary from you on how Microsoft is doing in that ground battle for ecosystem? So if I look the past couple of years when some of the biggest players, CEOs were on stage, it was about ODI. Hey, let's share our data. SAP, probably one of the bigger one even though they're doing with Salesforce as well. And I think that was a giant leap for folks. And then I think second of all, we weren't going to see Larry on stage because by the way, I agree with you on Jedi, that was a huge deal. To me, it was Oracle outsourcing IaaS to Azure. That would have been newsworthy. If I look at what could have been up here, not that there aren't more strategic deals that could be done, I think people are busy executing at this point. But if you look at who's going to share the data with ODI, that was the biggest. Working with different clouds, well, we're not going to get AWS to get up on stage here, right? We're not going to get GCP up here on stage, although we could have gotten WebEx up stage because apparently, WebEx at a Cisco and Teams are becoming friends. And maybe we'll see that on a slightly smaller stage. Yeah, it's more of an enterprise connect kind of launch than it is a Microsoft show. Exactly, but I was surprised, and I think it's a testament to how powerful Teams actually is. And it's funny when Teams, which everybody thought was dead after Slack was announced and Hangouts with Google has actually ended up being the darling of the enterprise. And not just because it comes free with your M1 subscription, right? It's really, it's a good product. It's a shockingly good product. You don't have to do any of the, any security, if you have any security challenges with anything in Microsoft, you'll have an issue here, but that's not the case. It all uses the back end of Microsoft for security and regulatory. So anyways, I know I'm veering off here, but there was one partner announcement that I saw. It was Cisco WebEx being friends with Teams. Can't we all just get along? I mean, that's, there we go. When there's money for everybody. Exactly, it's with every consumer. Every consumer. And it's too expensive to go out on your own. Patrick, always so much fun to have you on the show. Thanks for having me on. Thank you. I'm Rebecca Knight for Stu Miniman. Stay tuned for more of the Cube's live coverage of Microsoft Ignite.


I am going to turn it over to two of our in-car science wizards, Jeff and Cecile, and let them take it from here. Hey, everybody. My name is Cecile. And I'm so excited to share with you our movie called It's Just a Reaction. And in this movie, you will learn how to make elephant toothpaste. And you will also hear the sound of a farting bag. And you witness the eruption of a chemical volcano. My name is Jeff. All of the experiments we're going to do are about chemical reactions. Of the chemical reactions we show you today, you can do the farting bag at home. However, you'd have to be in a real lab environment to do the other experiments. So Cecile and I have our cool chemistry masks with us. So we're going to put them on and transport into the lab. Enjoy the show. Hey, everybody. My name is Cecile. And I work at NCAR in the climate science. And I'm also an NCAR wizard. Hi, everybody. I'm Jeff. I'm a chemist. And I work at NCAR in the chemistry lab. And I'm also an NCAR wizard. But as you can see today, we're here in my lab to do some chemical reactions for you. Yes. And these chemical reactions are coming from the NCAR wizard recipe book. And then you can see that today, because we are working together in a lab, we have to have masks. Yeah, if we didn't have the masks, we'd have to be six feet apart, which would make it kind of difficult. Oh, wow. It's very far away. But fortunately, I took my binocular. And I can still see you. Hey, Cecile. Oh, Jeff, you look so big. In this demonstration, we are going to do elephant toothpaste. Then you know our big elephant horn. And then when they brush their teeth, they need a lot of toothpaste. And you don't want to keep their teeth really clean, because you don't want them to run around with toothache or cavity. That's right. But do you know where elephants go to the dentist system? No, no, I didn't know where. They have to go all the way to Tuscaloosa. This is a good one. OK. OK, then if you look at our book here, this is a reaction where we are mixing hydrogen peroxide with soap, potassium iodide, and some food coloring to do the toothpaste. And we have already put in the bottom some hydrogen peroxide and some dish soap. The dish soap is just to make some form and also to keep the teeth of the elephant really clean. Then you see also here the reaction is releasing some heat. Then we should measure the temperature. Do you have a thermometer somewhere in your lab? I do, right here, actually, yes. So the temperature in the tube is now 69 degrees before the reaction. OK, OK, this is perfect. We are going to put some food coloring just for the effect. Right here. Oh, so I have red and blue stripes, just like real toothpaste. This is going to look really good. And now I'm going to put the potassium iodide slowly here. Oh, nice. Oh my gosh, look at this measure the temperature. Quick, 50, 150 degrees. This is really close. Oh, that's a good size brush. Yeah. Perfect. It's shining. It didn't really understand why we needed to put the potassium iodide. Yeah, so the reaction really just involves hydrogen peroxide decomposing. But we know a hydrogen peroxide is stable. It will stay in the bottle for a long time. So the potassium iodide is a catalyst. So it helps it to decompose. But it doesn't really get used up in the reaction. So it just keeps regenerating. Oh, very interesting. So it's a great reaction. Do you think the kids can try this at home now? Yeah, unfortunately not. Because the peroxide that I have used is very concentrated. And you cannot find this at the store. But indeed, I have another reaction that they can do at home. Great, let's see it. OK. I'm going to show you an experiment that you can easily do at home. That you just need baking soda and vinegar. Here I am taking apple cider vinegar because it has a color and I like it. But you can use any type of vinegar. And I'm taking a paper towel. And I'm going to put baking soda. 3 tablespoons too. Closing, I'm doing a little wrap here with the baking soda inside the paper towel. Then you see I have a little wrap here. Now I'm taking a zip lock bag. And then I'm going to put half a cup of vinegar. The baking soda. And I'm putting it in the bag. And I'm going to close very carefully the bag. But I'm holding the baking soda at the top. That it's not falling in the vinegar yet. And it's very important that you close very well the bag. It should be very well closed. And there is nothing that can get in or out. Okay? Okay, then my bag is really well closed. And now I'm dropping and I'm shaking. And then what you see, you have a lot of bubble coming and the bag is becoming bigger. And this is basically CO2 that's escaping. And you see the bag. There is a lot of pressure building inside the bag. Then you see you have the bag explode with the pressure of the CO2 inside. Then it's a fun experiment to do at home. Then I recommend that you do this in the garden because you can make a mess inside. I hope you enjoy it and thanks for watching. This reaction demonstrates a very exothermic decomposition reaction. We call it a volcano reaction. We start with a bright orange powder that looks like lava and we heat it. Once the reaction starts, it creates a second compound that looks like volcano ash. And it's really impressive. And this is the reaction that we're going to do. Oh yeah, I have it in my book that you can see this reaction only involves one chemical. It's not a reaction between two different chemicals like the elephant two spurs. If we can get a little bit of it hot enough, it will start to decompose and give off heat. And then it's enough to keep the reaction going on its own. The products of the reaction are chromium oxide, nitrogen gas and water. The chromium oxide has a dark green color. So dark it almost looks black unless we can get the camera in close. It's also a lot less dense than the dichromate. So there's a big increase in volume. So the volcano grows and really looks like it's erupting. Also, the nitrogen that's produced is a gas. So it helps with the effect of an eruption. But I have a question. I see here that the reaction produce H2O, it's water. What happened to the water? It doesn't seems wet at all. Well, it's pretty hot in there. So the water comes off as water vapor or steam. And that adds to the effect of the eruption. One really impressive thing about this reaction is the color scheme. We start with an orange powder and end up with very dark green flakes. Chromium is particularly versatile and its compounds can show up in many of the rainbow colors. For example, red, orange, yellow, green, violet. And I have a fun fact for you. The name Chromium is coming from ancient Greek. The word chroma means color in Greek. Isn't it interesting? Thanks for watching and we hope to see you in person next year. Let's turn the light. One, two, three. It was such a cool string of reactions and so much cool stuff all in one from elephants to farts to Greek and volcanoes. There was so much fun stuff in there. Thanks for sharing all of that, Jeff and Cecile. I think we have a couple of questions if you're ready. And if anybody else wants to, go ahead and share any other questions. The first question is, why was the elephant toothpaste so hot? Yeah, so that's what we call also an exothermic reaction. So when the hydrogen peroxide decomposes, it gives off heat because the products you make, water and oxygen are more stable than the hydrogen peroxide that you started with. So the difference comes out as heat that goes into the heating the bubbles. Yeah, you probably saw some steam as well coming out of the top. Yeah, absolutely. And Dan had said just that this was really cool and also made a joke about elephants getting cavities. Do elephants get cavities? But I have to think, well, no, that because of elephant toothpaste, right? Yeah, I would say that, I don't know, I'm not a dentist for elephant, but I think that we get cavities because of sugar. And I don't think elephants eat sugar. Then I think probably elephants don't get cavities. That is true. It's my guess. Good point. So here's a question from someone whose name is entered in a cumulus, which just obviously cumulus needs some of my cumulus cloud earrings that I'm sporting today. And cumulus wonders, can we do the volcano experiment at home? When to answer this, Jeff? Yeah, sure. Yeah, not the last one that we did, the dichromate volcano in the, that's pretty toxic stuff. We were doing it actually inside a fume hood and we were wearing face shields and glasses and goggles. And so you really have to get that stuff from a chemical supplier and be a trained professional to do the reaction as we are, obviously.  That's all you have to do. And then you can do a volcano like that. Here's a good question. Jeremy's wondering, would I be able to extinguish the volcano with water? And also, why does it become green instead of a different color? Yeah, I don't think, I think you need a lot of water to put it out. It's pretty hot in there. I don't actually know the temperature. I couldn't get a thermometer in there to check it, but that is pretty hot, I would think. And the green is just the nature of the compound you get, the chromium and the oxidation state, if you know a little bit about chemistry. So it goes from being like a more oxidized, which is orange to a little less oxidized, which is the green color. And that's the color of the compound we make, the trioxide just happens to be green. And that's just to do with the energy of the compound or the energy levels inside it. Great, thank you. Dan is asking what we're probably all wondering, does the fart bag smell bad? Yeah, and it doesn't really smell bad. It's a reaction between vinegar and baking soda.  Then it doesn't smell really bad. And I want to add something about this experiment because you should try this at home. You should ask your parents first, but you should really try this at home. But you should know that it doesn't work every time as well than to do the recording here. I did probably three movies and I took the one that worked the best. Sometimes the bag will become really big and it will take a long time to fart. It will take a long time. And also if you don't close the bag very carefully or if you have a little hole, then it will not explode because what will happen, you will have the gas that will be allowed to get out of the bag. And you will not have enough pressure than being inside the bag. Okay, tips, tips for home fart bag making, very important. Oh, this is an interesting question. So, Leif and John are wondering, they say this is very cool. And they're wondering, what's your favorite chemical reaction? Well, I get to deal with a lot of chemical reactions in my everyday work and I'm in the lab. So I do see a lot, but you know that elephant toothpaste reaction is pretty cool because it illustrates a lot of things. It gives off heat, it changes color a little bit and I get lots of gas given off and pretty dramatic. So I think I still like that one, like of all the ones I get to do. Yeah, I would say it's my favorite one. Well, and one more thing, we have Vivian who is age seven and joining us today. Is wondering a little bit more about why does the elephant toothpaste explode out of the tube like that? Then what's happening when you have this reaction, you have put some dish soap at the bottom of the tube and then you are going to release gas, then you have liquid that become gas and gas take much more room than liquid when it's why it's exploding like this. Okay. Do you want to add something Jeff? Yeah, there's also some heat as well. So the gas expands, but yeah, basically gases are about what? A thousand times less dense than liquid. And so when you start with a little bit of liquid like that, you get a thousand times bigger volume with the gas when it expands and add the heat into that, then it gets pretty dramatic. Great. Thank you. And we have a question from Juniver about the orange powder that you used for the volcano. Is it used for anything else? Don't know about that one specifically.  So a lot of chromium compounds are used in paints, for example. So I wouldn't be surprised if it won't use, how many negatives is that? But I think it is used. Different chromium compounds, yeah. Great. And Danny's wondering, can you do a really big volcano with those same, I'm guessing with those same ingredients? Okay, so yeah, if we have enough stuff then yeah. Don't see why not, yeah. Probably not as big as the Himalaya or something like this, but if you have enough material, you can do a big one. But you have to be careful that you need to put it in, it release a toxic product then you want to make it outside or in a place where you can get all the toxic product out of the volcano. Sure, because the bigger it is then the more toxic product it's gonna produce, right? Yes. Okay. So we have a few more good questions. Chetcho, Kai and Amaya are wondering if you could explain a little bit more about what actually made the farting bag fart. Yeah, that we saw in our chemistry book that the reaction when you mix vinegar and baking soda is releasing CO2.  And it's basically the CO2 coming out of the reaction that make the bag fart. Great. So try that at home, Chetcho and Kai and Amaya. See if it works for you. So here's a good question. These are cool experiments. And Alice is wondering how are these used or how are they relevant in the real world? These kinds of reactions. Yeah, I don't know if you'd necessarily see some of these and oddly enough, I think maybe the farting bag is the most relevant because it involves acidifying carbonate, which is what's going on in the oceans a little bit and CO2 uptake kind of the reverse of this. But yeah, I mean, that whole system of carbonate and CO2 and bicarbonate is very relevant in the upper levels of the ocean and trying to take up acidifying the shells of mollus and things like that and decomposing when they get very thin when it's too acidic. So I guess that one is actually somewhat relevant, believe it or not. So we're getting a glimpse into the, what the scientists do on their off days when they're not doing directly real experiments all the time, they get to have a little bit of fun with some fun experiments too, right? Yeah, yes. So, oh, Danny is wondering about your actual lab. How many people work in your lab? Is it just the two of you? And are you, yeah, I guess Danny is asking about the chemistry lab or is it the old building? And indeed, I don't work in the lab. I came to do the experiments, Jeff. And Jeff, you can answer the questions. Is it just you, General? Oh, there are a couple of us. My colleague, John and I work in the lab together. And so there's basically two of us in the lab plus we often get student visitors coming to help us. And some of them have come over from CU or from other universities, sometimes for a couple of weeks or sometimes for a year or something like that to work on projects. So, yeah, we're always happy you can get people to come and work with us. But usually the two of us and there are about 80 people in the chemistry division all together, chemistry lab, per se. And so there are the... Are they all chemists? Not all, no. Some of them are physicists, some of them are chemists and some mathematicians because we also do like computer modeling of the atmosphere, the chemicals in the atmosphere, not just the weather. And so we do have the mathematicians also working in our section as well, yeah. Great. And we're just about to wrap up but there's one more good question from Leith and John. You've been talking a little bit about gas versus liquid and actually some of the past presentations did as well. And they're wondering, is there more gas or more liquid water on earth? You mean water vapor or liquid water? I guess so, yeah. That's what I'm guessing, the gas phase of water, water vapor. Yeah, I think there was more liquid water than water vapor. Yeah, all the ocean of them. The ocean, definitely. Well, it's just about time to wrap up.  So I just wanna say thank you so much to our science wizards, Jeff and Cecile for joining us today from your homes and from your lab in the video. And thanks to everybody who has joined us for this presentation and we will be back in just a couple of minutes for the next one which I believe is what's up with weather. We're talking about a lot of weather this afternoon. So thanks, Jeff and Cecile and thanks everybody for joining us. Thanks everybody, bye. Bye-bye.


Hey guys, welcome to another week of Watch It Weekly Wednesday. I'm Beth, part of the Stamping Gel Creative Team, and I want to share a suite with you today that is in our mini catalogue. It is the Lights a Glow Suite, and I just don't think that the catalogue does this suite justice. So I wanted to show you the suite in person, and then I want to show you a really fun card fold that was shared with us. So let me show you the suite. There are two stamp sets and die sets in this suite. There are the Christmas lights and the Twinkly Light dies that coordinate. And there are the Labels a Glow dies and the Brightest Glow stamp set that coordinates. This is the stamp set that I'm going to show you projects from today. It was my favorite out of the two. There are a few papers that are offered in this suite. We have the Festive Foil Papers. It's got kind of that foil print. They come in 12 by 12. So, so pretty. And then we have the Glimmer 12 by 12 that comes in a pack together, too, with the Evening Evergreen gold and then this iridescent. So fun. They just made these cards come to life. There's also the Pearls. These are the Festive Pearls in the different, the four different colors. And this ribbon, vanilla and gold satin ribbon. So easy to use with so many different projects. But I think the winner of this entire suite is the 6 by 6 Designer Series Paper. It is so beautiful. One side, you have the gold foil on in all of the different colors and designs. So pretty. And then on the other side, you've got the more matte colors, but still so usable. Really, really fun. So I wanted to focus on the Brightest Glow Bundle. And included in that bundle is the Brightest Glow Stamp Set, which has a lot of different sentiments and the labels a glow dies. And it comes with 13 dies. I pre-cut the dies here so that you could see all of the different variety that this set offers. They have little ones for sentiment. They've got some fun things that will add texture to your cards. I really, really enjoyed this die set. Let me show you some cards that we made using the sweeter products. So here's one with the Joy. The Glimmer Paper just adds so much and brings out that DSP. And got that cute little design on the inside. Merry Christmas.  All is merry and bright with a little fun album fold there. And the stamp set that comes with the sentiments have ones that you can put on the outside of your card and on the inside. So it's great for Christmas cards. Also happy new year with some of that pretty designer series paper. Jill and I recently attended a backstage conference where we were able to do swaps with other demonstrators. We had an idea given to us from Don Cotter. And I love this fold, this fun fold so much. And I thought it showed the paper of the sweet off beautifully. There's this designer series paper that's included in the 6x6 stack. It comes like this. It's got the little circles and squares already printed on there. You can just cut it into little 3x3 sections and you can use them as backing on your cards. That was really easy and fun. But this fold I just loved. And I wanted to share with you today how to create that fold. So you'll need your trimmer. And you'll want a piece of cardstock that's cut to 4.25 x 11 inches. You're going to take that cardstock and score it at 5.5. So you can see that score line there just in half. And then you're going to take it back to your trimmer. And you're going to use your cutting blade. And you're going to go from your score line here to the edge to create that diagonal just like that. And that's your card base. And then you'll take a piece of designer series paper. This has been cut to 4 inches by 5.25 inches. And I want to layer that on my card but I need to cut it diagonally. So I'm going to take that edge to edge here and cut that on my trimmer as well. And then I've got the perfect little part to put on that card. Just like that.  And close this and then close that. This is a really fun fold that shows off the designer series paper but still gives you a chance to have a little sentiment on the inside. Let me show you some ideas we've made with this fold. Here's another one really showing off the paper in this suite. Just like that. And another one showing off the glimmer paper. That evening evergreen glimmer paper is just beautiful. I hope you've loved all of the products in this suite. We've included the links below in the video description if you are interested in purchasing any of the products. I think this suite could easily get you ready for your holiday season. Thanks for watching and we'll see you next week for another Watcha Weekly Wednesday.


Ευχαριστώ για εσάς. Θα ευχαριστώ για τη σορσή της δεύτερας. Τώρα, όπως εγγραφωθώ στο πρόγεκτο της εξχαβείας του ΑΕΣΟΤΟΥΡΙΟΣ, είναι έναν εξχαβεία μεταισμένη θεωρά φετά Nowyap дис directionρω συγκρα あτο τον Κύριος Πριέγου που βρίεται με το Ζαμίδι. Μετα στην μέτρε με Sapus, είναι η έμευταια Πόρση της ΑΕΰΕΕΝΟΞ, ό específicιμα έχοντας πρω estéντίως παγωρα. Ε melanό της MTV Kamra,)! Από τηνλεση της Mosya, για τη Ευτ thighs αλλάψω να συγβαίνω, Ας δείξουμε τρεις σημερινές σημερινές. Η κοινωνία εργασίας σήμερα στην Ελλάδα... είναι ένα δύσκολο σημερινό για οικογένωσης, γιατί η εμφαστρακτική εργασία είναι πολύ συγκεκριμένη. Έχουν σημερινότητα στις εργασίας και εργασίας. Είναι χρειαζόμενο για την εργασία, αλλά η εργασία μας, κάτι, είναι αγιωμένη. Αγιωμένη για η χρειαζή εργασίας. Αυτό είναι ένα σημερινό. Η άλλη είναι ότι σε εξαβεσίες like αυτές, στις εργασίες, η εξαβεσίες πιστεύουν πίσω από εργασία. Έχει ένα σημερινό εργασίες. Έχει ένα σημερινό εργασίες, όπως οι εξαβεσίες της εργασίας πιστεύουν πιστήρια της εργασίας. Και ο αρχιολογικός εργασίας, η διάφορξη της εργασίας είναι να εξαβεσίσει σε αυτή τη τεχνική, ή, όπως Ιούλια Τόμας κάτι είχε πει, δεν είχα καταξύσεις εργασίας. Στην εξαβεσίες, προσπαθούσαμε να εξαβεθούμε αυτήν την εξαβεσία, και προσπαθούσαμε πρώτα να προσπαθούσε, προσπαθούσε με όλους, όλα η διεξαρμία μας δηλαδή, έρθει η εξαβεσία να έδωσες πολλές δυο εξαβεσίες τεχνικά, για να δημιουργήσει ένα πρόεδρο της συμπλείνησης πρακτήσης μεταξύ μια πραγματική συμβουλία στον παιδίδιο. Λοιπόν, θα σας δείξω κάποιες πρώτες φορές και την εξαβασία, την εξαβασία. Η εξαβασία was... We combined the conventional methodology, some model models and we provided also. We had done on the surface an underground excavation. This is from the underground excavation. And this is our finds collection system, the processing system for the finds from the fieldwork to the lab. And this is the collection of data, some procedures. This is a special data collection, photographic and video documentation. And also sample collection of all these materials for analysis of artificial and natural materials. Geological data from hydrology, in situ measurements. This is from water permeability and conservation and restoration of the finds in our lab. The final... Now, this is our database. This is where all raw data ends inside our lab. This is the artifacts registry. As soon as they enter the lab, they are registered under a code that follows them until that time. This is the code. And this is the second level of our recording system, the conservation data sheets where our conservators record their work. And this is the third level, it's the database for the artifacts and the features and context, the excavation context. And I'm going to present three different examples of our study, the next level. One of these is the built environment and particularly the houses of Piraeus. In Piraeus, until the 5th century, the principle of egalitarianism, the Athenian democracy and so on, dominated the planning of the city as we had equal houses, equal sized houses with a uniform plan. In the Hellenistic period, houses became larger as we now have private representation developed. Our data comes from two different sources. One of them is the disposal layers inside the underground water supply structures, systems and wells. The material comes mainly from a disaster in Piraeus, not a natural disaster. In 86 PC, the Roman army destroyed the whole city. When they came back and rebuilt the city, they just cleaned the surface and threw every superstructure and artifacts inside these water supply structures that were available underneath. So we tried to connect this material to the user. As we didn't want to just form a typological series of objects, we used and we formed our database in such a way that we can try to place the objects in the hypothetical representation of the original framework. This is an example where we have used, the core is the Hellenistic house. We used objects from our excavations, our finds, to parallels from the iconography or parallels from... So we have the main rooms of the house in this way. Now we try to pass a difficult passage. This is some attempt to reconstruct houses and building blocks of the city. Now we try to pass a difficult passage from 2D to 3D. We're working on this. I don't have something to present you now, but this is the next step and our next purpose from now. These water supply structures have their own history before becoming garbage like repositories. We found 130. This is our biggest excavation, the largest one, the final station of the line. They found it since the 19th century in Piraeus, the 19th century. These are the 100 of them we found. They are wells, the first attempt of the inhabitants of the city to obtain drinking water, typical wells. We also have systems that they could store water. They worked as reservists and here is a reconstruction combining systems and wells. In later stages you can see in this animation the phases of the revolution. Connection of systems of wells, bigger systems for more water, more big systems as they added these tunnels. Connection to huge systems combining by five systems and many wells. The next chronological step was the Roman aqueduct. We excavated 95 meters of the city's aqueduct. This is a photo of the aqueduct. We tried other collaborations with the water resources and environmental engineering department of the National Technical University of Athens. We tried to connect the development and the management of the systems with changes in the residential development and the improvement of materials. We did some hydrological models and then we tried to explain every feature and every detail on the structures as the hydrologists convinced us that it is connected with contemporaries such as sustainability, use of limited resources of water, use of rainwater also. The third example of our study is the landscape analysis and mapping because we have a whole city in front of us. We have maps since the 19th century. This is the first one from Taupert. But we think that they were a bit, first of all, inaccurate in today's terms. But then they were limited to capture the essential elements of the development plan. So we started to create a primary digital model of the terrain from scratch. These are versions of the urban grid of the city from these maps. So we obtained a series of orthophotos from a national agency and then we combined them to a single orthophoto map. The result was, you'll see it in a while, it was an accurate map that we could annex first our excavations, our major excavations and then try. This is an autocadding environment. We have now scanned over 300 original handmade plants and we annexed them on this map, on this accurate map, in order to start the explanation and the reconstruction of the city grid on accurate terms. In some cases we went back to excavations that today are visible. They are not under buildings and we collected points because we didn't have accurate drawings. Then we had another cooperation with the Urban Environment Lab of the National Technical Diversity of Athens that resulted in these thick maps. This is what they call it and we have no reason to doubt it. We can now filter with layers of our data, data collected from various sources just as you'll see some layers. This is the orthophoto map. This is the basic map we formed and then we start to add layers. City walls, ancient shoreline and many sites in categories, workshops, basic categories. You'll see the map filling with sites. These are the sites containing systems and you'll see the final layer. The final layer is the thick map. These are the main buildings as we know them. This is the orthophoto map and everything on a single map. Now we are forming our GIS database. We have cooperation now with the GIS expert and we are passing this passage too. We want to give the temporal aspect on our maps. So just statistical tools we believe that they are going to be very helpful.