Hello everyone, welcome to another video. So I'm super happy and excited to announce that we are doing a special fundraiser. Now, the way this all come about is with the recent scare and the crisis lately in the news and all of that, it was putting an enormous amount of strain on sanctuaries. And a couple of sanctuaries that are really close to my heart is the Retreat Animal Sanctuary run by my friend Billy and Tower Hill Stable Sanctuary run by another one of my friends Fiona. So the Retreat weren't able to open for their normal public entries where they would have people spending money at the cafe and you know, bringing in revenue to help the animals.  So I was trying to think up a way of creative way of fundraising for these two sanctuaries. And I thought, how about we bring out some apparel? So we brought out a shop and my project manager here has been working very hard over the last few weeks to bring this shop to life and it's very professionally done and the designs look absolutely epic. So the designs are Animal Guardian and we have like a classic style design here, which is like a shield.  And the text says Animal Guardian. So the shield's supposed to represent the guardian of the animals and on the back it says Defend Animals. And then we've got another design here, which is just one of my favorite pictures ever of me and a little rescue piglet named Julian, me kissing Julian. And this here is more of a limited tea. We're only going to put this out for people who are, say, long-term subscribers and they really want something more personal. But we've got the Animal Guardian with the animal shield here on hoodies and t-shirts and we've got women's and men's and we really hope that, you know, you guys have got a little bit of spare money. You might want to support the t-shirts because 100% of the profits made from these garments will be going split between 50-50 between the Retreat Animal Sanctuary and Tower Hill Stables. So we're really excited to see everyone wearing the apparel. So if you've got any concerns about how the garments are made, they're completely ethically made, sweatshop free, all the inks are vegan and they're all made in factories that are powered with renewable energies. So we've been quite careful about where we've got the supply from for the garments and we've had a lot of help with fulfillment on that end. So basically there's a presale on for the next two weeks, be a two-week period where you can order, order, order and then we'll fulfill those presales, see how they go, we might bring in another batch as well but we're just going to put it on presale for the next two weeks, so order yours and then we'll get those orders out to you after the two-week period of presale is over. So if you go down into the description you can find the Shopify store there. There'll be complete transparency about the funds and you know what profit is and where it's going and all of that. So the reason these sanctuaries need funding is because they have extremely high running costs. There's hundreds of animals at these sanctuaries and the running costs for the retreat is £15,000 a month and the cost for Tower Hill Stables is much the same, about £15,000 a month. That's a lot of money and I don't even think that includes vet bills so the bills add up and Billy and Fiona they both do amazing work and I just want to help relieve some of the financial strain for them and yeah so thank you everyone I hope you know that you can purchase something and really looking forward to raising a lot of money for these sanctuaries. If they do really well we'll keep them on and we'll keep the money going to the sanctuaries and hopefully this can be a more of a long-term thing. Share them around, get your friends a present as well if you know if you don't need any new clothes you can get a gift for someone and yeah I'm really super excited about this hoping that they get a lot of extra money to feed the animals with and it sort of alleviates some of the stress during this crazy time around the world. It's been so crazy. A lot of people are out of work and I understand that you know the sanctuaries are getting a lot of you know stress and pressure as well because they've got so many more individuals to look after and yeah we really hope that this small deed makes a difference to them. So yeah I just want to say thank you to everyone who helped bring these t-shirts into action especially my project manager working very hard put those designs together she she got it really did a really amazing job there and another thank you to the supply of the garments the ethical tea company. So thanks for watching go get your garments from down below and let's see if we can help these animal sanctuaries out. Peace!


Welcome to this course on nanostructured materials, synthesis properties, self assembly and applications. Today we are in the module 3 lecture 10 and we begin a series of 3 lectures on core shell nanostructures. So, today is the first lecture on this 3 series lecture series of core shell nanostructures and that belongs to the module 3 lecture number 10. Now, what are core shell nanostructures? These are particles that contain an inner core covered by a shell. Now, the so the inner core can be of one material and the shell can be of a different material. So, why core shell nanostructures are important? They are important because they give improved physical and chemical properties over their single counterparts. For example, if you have a core of a material A and a shell of material B, then the core shell of A and B can give you improved reactivity on the surface, can enhance the stability and dispersibility of the colloidal core and they can be used in many applications. So, what are these applications? There are diverse applications in medicines. For example, in controlled release of drugs in drug as drug delivery agents, they can protect materials from light and moisture sensitive compounds. So, if you have a moisture sensitive compound, you can make it as the core and you can cover a shell which will prevent the reaction of the atmospheric oxygen or moisture on the core. So, you can stabilize the core material, then you can use them as catalysts, as coatings, several applications are there for core shell nanostructures. Now, the synthesis of a core shell nanostructure can be followed on basic principles which are the miscibility of two materials and their interfacial energy. That is very important when you design a core shell nanostructure. If they are immiscible, significant possibility of the formation of core shell nanostructures are there. However, if they are miscible, then they may form a solid solution. So, this immiscibility is important. Now, if you have a large interfacial energy, then you get individual particles. So, you have A and B and you want to make a core of A and shell of B. If the interfacial energy between the A and B material is very high, then chances are that you will not get a core shell material, but you will end up with two materials, one A and one B and such a material will then be called a composite material. It will not be called a core shell material. So, large interfacial energy is not good for core shell nanostructures. Then if you consider lattice mismatch, that refers to basically the lattice parameter of two materials A and B. If the lattice parameters, that is the unit shell parameters are widely different, then that will increase the interfacial energy. Thus, you have to choose materials which do not differ significantly in their lattice parameters or lattice constant and should be within 1 to 3 percent. So, if you have large changes in lattice mismatch or large lattice mismatch, then that will increase the interfacial energy and that in turn will make it difficult for you to make a shell on top of the core and you will in turn end up with two different types of particles which is a mixture and then it is called a composite. Now, how do you achieve uniform core shell structures? If you slowly add the shell forming agent at relative low temperatures, that is important. Then the sequence of mixing of the reagents, how if you want to make A on top of B or B on top of A, the sequence of mixing of the reagents which are related to A and B are important. The proper choice of shell forming agent is important. For example, if you want to make a shell of silica, then you have to take appropriate reagent which contains silicon. For example, some alkoxy silanes like ethoxy silane, ethoxy silane, they will be used for making the shell. So, appropriate reagents have to be taken which will be related to the shell forming agent. Then the rate of addition of the shell forming agent is important for making a proper shell and the control of the temperature and the selection of organic ligands which adhere to the surface of the core. So, these are some of the key parameters which one has to take into consideration when one is planning to form a uniform core shell structure. So, there is thermodynamics and there is kinetics both involved in making a stable core shell structure. And of course, by changing parameters, you can sometimes get metastable phases and you can stabilize those which normal thermodynamics will not allow you to make them stable especially because you are making the synthesis in the nano dimensions. Now, some of the mechanisms which lead to the formation of core shell structures, typically core shell structure is represented like core with this symbol which is at and shell that means whatever suppose you are making A is the core. So, you write A at B where shell is B. Now, the there can be several different mechanisms by which you can form core and shell. So, here for example, you have a particle which is going to be your core material and then you want to make a shell of some other material. So, if this material and this material come close and they start agglomerating on the surface, you can make a shell like that. So, you can do what is called direct heterogeneous nucleation and growth. So, you have this A reaction showing you direct heterogeneous nucleation and growth and it can form a seed then on top of that you can make a shell like this. So, first you can have one layer which can be kind of a capping layer and it forms one black layer on top and then you have a material which can be put on top of that capping layer. So, here you have the core and then the capping layer and then the shell. However, you can directly make a shell on top of a core if you have a rod like particle you can get rod like core shell structures. Then you can also have suppose you have this is the example of zinc sulphide if you have zinc sulphide or zinc in the wood side structure or zinc sulphide in the zinc blend structure depending on the two structures since they are different the shell will form in a different manner. For example, if you take wood side type zinc sulphide and you are trying to make a shell on top of it then you normally get this kind of a rod shape structure when you take zinc blend typically you get this kind of tetrapods. So, the shell adapts to the symmetry as well as the shape of the starting core. So, that is what is shown here. So, here the core is anisotropic and the shell which forms on top is also anisotropic. Here the symmetry of zinc blend and wood side is taken into consideration when the shell forms. So, on wood side you get an anisotropic structure whereas, on zinc blend you get a tetrapod like of structure because of the tetrahedral symmetry. So, the symmetry is important and the shell adapts to the symmetry. Now, you can also have a three step shell growth process example in an organic media here you are making a silver shell on a particle. So, you are adding some silver nitrate and then you are making this shell on top which is initially amorphous and you add some other alkylating agent. So, you do some cation exchange on top of that and you can remove the silver and you will get this shell which is favored by the strong acid softness of silver plus. So, then you can get this kind of coverage on top of the core. So, you can have three step shell growth process in organic media the way it has been explained using first a silver shell which forms then an amorphous silver sulphide or a shell on sulphidation and then you can remove the silver ion and you can exchange the cation with silver and then you get a different shell with this sulphide on top of it. So, this kind of three step shell growth process is possible in organic medium. Now, this is another process by which you can get core shell structure. So, it is a controlled hydrolysis and condensation reaction in organic medium. So, you supply a metal alkoxide it can be silicon alkoxide or titanium or zirconium and you have a core particle and then you build this kind of a structure on top of the core and then you have hydrolysis and then condensation and then you get this kind of shell formed on top of it. So, this is one mechanism you can also have a sacrificial mechanism where you start with a particle and then you some of these exposed layers of the starting core are removed and these particles come on top of the inner core. So, the core diameter you see here it gets reduced in the core shell structure that is because part of the exposed layers have been removed during this reaction which may be a redox type of reaction and ultimately the core diameter is smaller than the starting nanoparticle and the shell is of course, formed by the new material which you have started and this can be done by a galvanic replacement reaction in a cell and you can see these particles which are going out is actually belonging to the core material. So, the some of the particles are removed from the core material and the incoming material is deposited on that inner core ultimately giving you a smaller core size compared to the starting material. So, this is called a sacrificial conversion of the core material. Now, there are other methods or mechanisms by which you can get core shell nanostructures. For example, this is a very famous method and the effect is called the Kirken-Dahl effect where you have a core and you form a shell on top using this kind of redox reaction or a sacrificial reaction and then in you have the Kirken-Dahl effect where it is a atomic diffusion process which takes place through vacancy exchange without having a direct interchange of atoms. So, there is a vacancy exchange once this core shell is formed then you basically there are fast diffusing species in the inner core and the outer region acts as reservoir of slow diffusing species example metal cations and oxygen anions in oxide passivated metallic nanoparticles. So, what you can get using Kirken-Dahl effect is you can get a hollow structure or you can get a core shell kind of structure like this. So, in this Kirken-Dahl effect you are basically taking the process is through vacancy exchange rather than direct interchange of atoms and there is a net transport of matter from the core outwards along with coalescence of the vacancies into a large void. So, these vacancies they start moving and the vacancies all kind of coalesced together to form this gap between the core and the shell and you have that matter transport is towards the outside. So, a net transport of matter from core to the outward direction takes place in this Kirken-Dahl effect. Now, you can also have a self controlled nucleation growth. So, the energy activation barriers for the homogeneous nucleation of individual compounds may diverge such that two different materials form at distant distinct times or temperatures. So, initially you may have one particle and so that forms the core which is the first reaction from a system of two types of species. One you can see is light gray the other one is the dark one and what happens is the lighter ones aggregate faster and you get a core particle and then the darker ones aggregate slowly. So, they form on top of the light gray sphere and so they form the shell. So, this is a self controlled nucleation and growth mechanism and it has two different materials which form at two different times or temperature and the shell material is produced exclusively by heterogeneous nucleation on the in situ formed seeds. So, this is the seed the light gray particle which is formed in situ from these small light gray particles. This acts as the seed for the formation of the shell for which is denoted by this dark small spots and so you ultimately get this dark shell on top of the light gray sphere. So, this is by self controlled nucleation growth mechanism that you can make a core shell structure. So, there are many ways by which as you see you have already several methods forming core shell structures from seeds using heterogeneous nucleation and growth mechanism. Then a three step shell growth mechanism then controlled hydrolysis and condensation reaction sacrificial conversion of the outermost layer of the core. Then the kirkendall effect giving you movement of particles or matter from the inside towards the outside leading to this vacancy a coalescence and ultimately leading to this hollow core shell structure. It may be completely hollow if this a continues and this is an intermediate structure this is the final structure where all the matter has moved from the core to the shell. Then you have self controlled nucleation and growth you can also have thermally induced phase segregation and solid state diffusion. So, you have two types of particles here and then it forms a composite particle and then as you heat them this composite particle as you heat them the phase segregates the dark ones and the white ones segregate to form two completely distinct entities one forms the core the other forms the shell. So, this is thermally induced phase segregation and solid state diffusion here what happens is you have a core particle and there is another particle and initially they adsorb on the surface. So, you have these small particles becoming larger they are coalescing on the surface and ultimately you can form a core shell type of structure. So, several mechanisms of making core shell structures now we come to a very important thing that how do you look at this core shell structures finally, once you make the core shell structures you have to show that they are core shells. So, how do you look at them and that is very important in this kind of science or technology where once you have made this nano structures how do you exactly identify the core and the shell. The basic technique which is used to characterize these core shell structures is by electron microscopy and in electron microscopy you use basically the TEM which is the transmission electron microscope and then in the transmission electron microscope you can do several things you can image the nano structures or you can do electron diffraction and find out the crystal structure of your nano crystals and you can also find out the composition of your nano crystals by looking at what we call the energy dispersive x-ray analysis. So, all these things can be done using a transmission electron microscope. So, this is an example of a core shell structure where you have cobalt iron alloy as the core particle and your iron oxide which is the shell. So, this is the high resolution transmission electron micrograph which is showing the crystalline shell around a core. So, the core is at the center which is made of cobalt and iron and the shell is made up of iron oxide Fe 3 O 4 and how do you make these particles is that you start with cobalt ferrite CO Fe 2 O 4 and use oleic acid and oleal amine and then phenyl ether and iron carbonyl if you reflux it you end up with the core shell nano particles of this kind. This is what you see in the image and if you see the scale here this is 10 nanometers and so this particle diameter the core shell diameter is around 10 nanometers and if you look very carefully then the core is here and this diameter of the core is around 4 to 5 nanometers. So, what you can say from this transmission electron micrograph is that the core has a diameter of around 5 nanometers 4 to 5 nanometers and the shell thickness is around 2 to 3 nanometers and what is in the core and what is in the shell if you want to find out then what you do you do electron microscopy by passing the electron beam through the shell and also through the center of the particle when you pass the electron beam from the shell then you get a spectrum and you analyze the spectrum this is the energy dispersive x ray analysis and when you do you can identify these peaks as belonging to various metals. So, what you see here is you can see copper iron oxygen carbon now copper is coming because you have used a copper grid to mount your sample. So, the copper does not belong to this material, but you are getting this copper line because it is mounted on a grid for holding your sample and that grid is made of copper. So, you can ignore this copper peak what you have to see is the other peak. So, iron is there oxygen is there and some carbon. So, carbon and oxygen normally can come as either oxide and carbide or most of the time carbon comes as an impurity. So, what you can say is that the electron beam when it passes from the shell it can see carbon, oxygen iron and copper out of that carbon is an impurity and copper comes from the TEM grid. So, the material is made of oxygen and iron and hence the shell is Fe 3 O 4 which is what you wanted to make. So, you can confirm that the shell is Fe 3 O 4 now when you do the same experiment with the electron beam going through the center of the core shell structure and if you analyze the spectrum you will see that the peaks correspond now to carbon iron oxygen cobalt and copper. So, carbon and copper we ignore because carbon is an impurity and copper is from the TEM grid. So, what you find is that you have iron oxygen and cobalt. So, when the beam goes through the center you can say that cobalt is certainly at the center and iron is also possibly in the center, but iron and oxygen are certainly in the shell because that you already found out. So, from the edacs what you can say is that the core is made certainly of cobalt, but it can also have some iron and it can also have some oxygen because that distinction you cannot make just by using this edacs analysis. You have to do some other methodology what you have to do is called depth analysis that means you have to remove the surface and then study and then you can actually identify the real composition of the core. Now, you can also do electron diffraction and from electron diffraction of the core shell structure you get particular spots and these spots can be identified with the Fe 304 structure and also belonging to the alpha phase of iron which can be due to the core which is made up of cobalt iron. So, using electron diffraction and by assigning these reflection each spot is from a plane in the lattice crystal lattice and when you can assign the planes of both the core and the shell you can say that both these are present in the solid. So, using electron diffraction you can assign both the structures which you see in the core and in the shell. Now, let us do some examples of core shell structures and you can choose many thousands of examples of core shell structures which have been synthesized over the last 10, 15 years and we will choose some selective examples to give you a feeling of the type of core shell structures that people are discussing today. So, first one of the most important shell making substances is silica S I O 2 why people choose silica is because of easy control of deposition of the silica shell then you can control the porosity of this shell silica is optically transparent. So, whatever you put in the core if it is an optical material it you can harness the optical properties of the core when you have a silica shell silica is also cheap. So, it is a low cost material to tailor the surface properties while maintaining the integrity and the stability of the core where are silica nanostructures applicable. So, there are lot of applications of silica coated nanostructures they are used for biological applications they silica encapsulated nanomagnets have found applications as in biomedical science and they can enhance the stability and luminescent properties of bismuth sulfide nanorods. These are few of the vast number of applications that you can expect from a core shell nanostructure which has a silica shell on top of some particle that particle can be a metal particle it can be a semiconductor particle or it can be an insulating particle. So, there are many many examples on which silica has been coated to act as a shell. Now, this is a typical procedure by


Oh, do you want to use this one? No, this one's okay. There you go. I will tell you my map up here. You can read the chart directly. Perfect. Because now this is lots of results for the host because we've already taken the people. I see. Cross our fingers. Okay, I think it's time to get started. So this final session of the day before we go to the posters and the reception, we've got three talks to one in, sorry, one invited one contributed one invited. The first is a really Pollock from University of Basel. I need the floor is yours. Okay, thank you very much. Thank you all for the introduction. Okay, so let's get started. So the first part will be about this paper we published three years ago in annulators. I have to acknowledge the contribution from Guillame Villena. So Guillame Villena did a lot of molecular dynamics simulation that I will show you today and I am grateful for his calculations. He will have a talk tomorrow. I invite you to go because you will see more of these simulations and you might be interested to discuss with him about this. The second part will be a non published results that will hopefully come soon to publication and it's about this quantum dot super lattices. Okay, so what we do for quite some years now at the University of Basel, we look at friction and mechanics as a single molecule level. So these are two cartoons that basically summarize the kind of experiments we can perform. Here on the right picture on sorry on the left picture we have pulled a few years ago some DNA strands attached on the gold 111 surfaces, and we could probe the force, the mechanical response to pull this object from the surface. On the right parts we can also put on the STM tip or STMI FM tips which is shown by this cluster of let's say copper atoms. We can plug a single molecule and slide it over the surface and we can see really a single point as perity that we can basically model with a typical quantum new some models so this was one of the first experiments. So we work at very low temperature that's really important for this experiment because we want to attach a single molecule to the to the apex of our SPM tip, of course, and I will show you how we do that. So this is the experiments or the machine we use to do this experiment so it's a low temperature STMI FM so I stem for scanning tunneling microscopy FM for atomic force microscopy. It's based on this kind of sensor so the tuning for sensor which is from here. So it's basically STM tip, which is attached to a tuning fork that allow you to measure as well forces so we can do both STM imaging FM imaging, and we can measure forces and local density of states through the STS mode, let's say. So we work in ultra vacuum. We put a sample in this environment which means we have really ultra clean surfaces. We absorb the molecule also in ultra vacuum and we can proceed to some chemical reaction to build up structures that we will then manipulate manipulate manipulation experiments are done at low temperature again at about four to five Kelvin, which allow you to remove any particles. So when you will discuss cooling experiment for example you don't have, I mean, thermal excitation of the of the system. Another aspect which is important we use really really small oscillation amplitude of our FM it's below one answer so it's typically 30 to 50 picometer oscillation and this oscillation scale very well with the size of the molecule we manipulate so you don't detach molecule at every oscillation cycle if you stay in contact and you look at all the molecule actually rearrange under the pulling force for instance. Okay, another aspect which is important for us is that we can proceed to some chemical reaction the idea here is to build up nano structures that we will manipulate afterwards so a good example is this on surface synthesis with woman So basically use usually a precursor that chemist will provide you which is from here, it has bromide atom on the side and you can through annealing of the substrate after after the position of the molecule on the surface you anneal the surface, you split this bromide off the molecule so let's shown here is molecular than in the radical state and they will react together from linear polymeric chains as shown in the middle here. So if you can keep the reaction going on, you will have some processes and you will be able to close some of CC bonds between the structure and form a nice graphene nano ribbons. So years ago my colleague, she actually did an experiment using such a nano ribbons here you see a knife and picture of the structure of the nano ribbons so what you see is actually the hexagonal rings of the graphene. So you can see that as the ribbons length increases, so the force to move this ribbons is not increasing with it so basically it's a, it's a fingerprint of the superlubric behavior of this ribbons on the Gordon and one. And this is something important for us in many different results we have obtained afterwards because we can really pull this ribbons or slide them on the surface, and they have a superlubric behavior. Okay, so today I want to discuss this particular topic is if I compare it to this one what we did we simply in introduce inside the polymer exchange single carbon carbon bonds so they are shown here between this. So, basically you use this precursor you have bromide atoms with the brominates on the surface, the molecule through annealing it polymerize and then you have this pyramid and units which are these things. I'm sorry for that. So these are the pyramid units and they are connected by a single cc bonds between them, which allow you to have more degree of freedom in the system. So, here you see a collection of images so the, this one is actually a nice image of intact. After reaction, you can see clearly that you form the chains as we expect from a chemical point of view. And if you look at the STM image you see that chains are all over the surface, and they are well, I mean, let's say, chemically pure as we expect in terms of chemistry. And there is an important aspect also here, we have quite a substantial in plain bending of the chain and this is due to the single carbon carbon bonds that you have in the structure so we can see really made is good. I mean not twist but some bending of the structure on the surface. And then I will show you now the DFT calculation of the chains in vacuum to show you all the molecule should relax in vacuum. So you should have basically between units, an angle of about 40 degree between units consecutive units. And the reason of that is you have some steric in runs between the auto hydrogen of the perinatal units that force the molecule to twist that way. Now, of course, if you put the molecule on the surface, you start from the from the twisted molecule in vacuum you put it on the surface of pistachios all units are flat line. And you can see through this molecular dynamic simulation, which is basically a relaxation from above room temperature down to low temperature. You see that the molecule wants to create some in plain bending and this is basically because the molecule wants to increase its commensurability with the surface so you want to have a nice absorption of the molecule. And this is also what we see in experiment. So experimentally, we then use one of this molecule so it's a free standing molecule on the gold 111 surface. And this is a molecule here, so by sdn you see that it's about 20 nanometer long that correspond to 35 units. And this is now the trace we obtain experimentally which is a trace showing you the stiffness of the stiffness between your tip and the molecules, which is basically proportional to the force we measure here, which is a frequency and then upon pulling you see a succession of dips all along the curve, which are actually corresponding to the detachment of single units. So you see we pull by about 28 nanometer, which is the length we see by sdn just prior to the manipulation. And this means that we are fully pulling the ribbon from the surface so we simply take it pulling out of the surface and then it's on the tip afterwards after the experiment. Guy was strong enough in terms of simulation to reproduce fully the experiment so here you see that every dips actually correspond to the detachment of single units. You see that the length, the pulling length is also found again in the simulation and we are from this point of view quite happy to have a really good agreement between theory and experiments. But what I want to show you today is that in this course there are much more information that just we pull and we see a number of units. So, as we discuss, let's let's say, as we see now you see the pulling movies from the simulation, and you see that many things are happening so on top you see the top view of the pulling. This is the pulling axis to the left hand side, and this is the side view of the same movies where you see only the detachment of the units. So, first of all, you see that we start from a straight chain and then the chain immediately rotate downwards or upward with respect to the absorption position at the beginning. You also can see on this movie that units are left and right or clockwise and anticlockwise as you are pulling the object. And these are the things we started to look in the experiment. Can we actually see this kind of behavior that you can really well see in the molecular dynamics simulation in our experiments. So the first thing we look, we look more into the detail of the pulling curve. We see that we have always two kinds of detachment lines so that are called that are called here L plus and L minus so you have a short detachment and a long detachment. And they are always alternating because they are colored in gray and white respectively. In the simulation we also found this behavior. Again the movies and you can see at the same time, so you will have too many things, you will have the maximum force to detach the units will change between alternating detachment. So you will have let's say different forces, whether it's detaching clockwise like now or anticlockwise. Okay, we can see from the, from the simulation that stiffness is really well produced. But the additional information is actually the ideal angle so the angle between the two subunits along the system. So you see that you have two kind of rotation. And they are not symmetric. Because the structure is symmetric. In fact, so this is just to summarize the rapid need or let's say you have a force maxima which is changing depending on the detachment if it's clockwise or anticlockwise the work is also different and the dealer angle also different. In fact what you have to look is that upon sliding upon lifting sorry you have the tail of your, of your chain that start to rotate away from its first absorption sites. And this is the two snapshots of the lifting and this are the same for all the units. If you are considering proper attachment, the units will look like this. We will have steric entrance located here on this red area. If you have an anticlockwise rotation with the steric entrance at the opposite side and this are two different configuration and that's is the reason why you see two different lengths help us and then minus in the fourth case. So, besides that, we have also on the surface, the way the molecule slide before its attachment are completely different. So these are the project, the projected trajectories. But we imagine that we select one of these items of units in these items and we compare all the slides on the surface before the attachment. So the length, the attachment length is different, but it does not mean that the unit is jumping away higher than the other ones. Here you can see that the relative height is similar for both units. So the difference is actually all the units travel on the surface, is pulled and then relax after its attachment. And this is what you actually see on these two plots here. We look at all the molecule travel across the surface. So it usually likes to travel along two main direction, which is the one one zero one minus one zero, which are preferential low friction displacement path for the molecule. But you see that the way the path is trajectory is found is completely different between one detachment and the other one. And this is also the reason why we see two different detachment lengths for the clockwise and anti-clockwise units. So just to show you that this is not just an imagination of us in terms of theory and experiment, we actually do see this behavior all along the detachment. In terms of experiment and theory, we are counting the different detachment, you see that for the tendency of having always L plus, then and minus, L plus and minus, which means you have always clockwise, then anti-clockwise, then clockwise, then anti-clockwise, et cetera, et cetera. And this is what you see here. And the reason of that is, is basically when you start detaching from this point here, the molecule will always slide on one direction of the surface, which are always equivalent direction of one minus one zero. So what I show you now on this graph is actually the sliding of the last unit of the chains. And you'll see that it's always the same direction. So because the molecule rotates, the detachment, so the twist cannot be equivalent, because it doesn't follow this direction, but it's put in the equivalent platform, because the tail is actually sliding away. And this is thanks to the in-plane bending you have in these molecules. So this is thanks to the CC bond you introduced in the structure that allows you to have different bending, in-plane bending of the structure upon sliding. So this was just to show you really detailed experiments of what we can do. We have many more different pulling experiment or even sliding experiment. We will talk most probably about some of them. And this is to really remind you that the curve we obtain experimentally are rich. They have a lot of information that are difficult to really interpret without the help of the molecular dynamic simulations. Okay, now I will go to the second part of my talk. How much time I have? Eight minutes. So eight minutes. So now I will talk about completely different system. So we were looking at energy dissipation in actually quantum dots. So this was actually shown in 2010 by the group of Peter Grutter where they use quantum dots. And they could show that when you use an IFM as a gate voltage, so you approach an IFM on top of the quantum dots, you can tune the electron occupancy on the dots. And basically you see the charging of these dots, as well as energy dissipation. So this is what is actually shown here on this piece. So the quantum dot is on top of an insulating substrate. You have a yellow color in yellow to the gas that allows you, which is basically your electron reservoir. And if you apply the right voltage at the tip, you will be able to take an electron from this reservoir and charge the quantum dots. So you can charge with many electrons from zero to six, and each piece will give you dissipation support. So if you now imagine, especially what's going on, here you have four different quantum dots, and they show some different rings. The largest one for a single charging is double charging, and each ring is centered to the dot, because you can charge each of these dots. Now the question we wanted to discuss, I mean what we wanted to look at is what happens when the quantum dots are actually interacting to each other, when they are strongly coupled, because in the previous experiment I showed you, they are actually non-interacting. So here our idea was to actually build a nanoporous network on a metallic surface and confine the electron of the surface, that electron of this metallic surfaces, in this case it's silver 111, and create artificial quantum dots in a way. So each part of this network would actually confine the electron and create a quantum. Then our assumption, and it was discussed this morning by Alexina Olliam, is that force voltage spectroscopy is actually sensitive to quantities that we rarely discuss in IFM, which is the quantum capacitance. The quantum capacitance would scale directly to the local density of states of the quantum dots. So in principle, in the case of a normal metal, whether you have a quadratic dispersion of your surface state, you should have a simple expression of this quantum capacitance. So this could be a quantum capacitance to scale of the effective mass function of your quantum. And this is what we try to basically observe experimentally. So we build two nanoporous networks on the silver 111 surface, we use this molecule, so it's a pure inland unit with oil group at the site. We can by annealing of the substrate promote some tiny reaction. And this will trigger two kinds of sub assembled system on the surface. On the right you see the STM image you will get, and you get another network with different pore size, pore cavities. Let's have a look a bit closer to it. So you have the so called alpha phase, so it's only six membered pores or hexagonal pores. You can see here a better resolution of structure, so it's going to be molecular assemblies for the molecule interacts through hydrogen boundings. And you have the beta phase which contains trigonal, octagonal, hexagonal and nonagonal pores. So this represent different size of the confinement of course. The confinement you can actually interpret is so difficult. The confinement energy from where the quantum dot level will appear depends on E0, so the surface state energy, the position of the surface state, plus the reduced constant, the plant constant, the ternium wave vector and of course m star effective mass of the surface state. So with all these things we can interpret basically where should appears the energy level due to confinement, but we can also probe that using STM. And the idea here is simply to have a clear idea of what's going on in terms of local density of state, what is the band structure of our system. So here you see the calculated structure by GFT and this is the TID spectrum at the middle of the dot, so this is the gray spectrum and on top of the molecule is the dark spectrum. The confinement state is actually located at plus 300 BB, this is this dot. Here you have a second TID that appears below the Fermi level, and this you can consider it as a bonding, bonding anti-bonding basically state. So it would mean already by seeing this that the quantum dots actually strongly interacting to each other. And on the right you have actually cross sections across two of the dots, each of this icon difference after the confinement state and this will be the star which is the bonding states related to the confinement. Just to make a bit more clear, the picture in terms of band structure, you have Fermi level, and you have bonding, anti-bonding states with confinement which are located here when you have the connection band of the silver and below the balance band of the silver. And this is now what you could consider as a local density of state of your system that we want later on to translate to quantum capacitance. We can do the same, but I will go faster on it for the beta assembly, so here we have different force, of course, confinement levels for the confined state are appearing at different energy. If you look at the next element for it again, if you look at the bigger part of the energy flow, then you have also a shift of this bonding energy that is modulated by the variety of four you have in this system. Here again it's what we use for scaling the quantum capacitance in our system. Again the band structure or you can interpret it. Okay, this is now dissipation spectroscopy so what we do we measure the force at the function of the voltage on top of these two assemblies. So these are basically site independent measurements you don't need to be inside the poor on top of the molecule you will have the same response everywhere on top of the molecular. So this is on the alpha superlatives. This is the political parabola of the delta for the force that you have tiny drops in the force, and you have an increase dissipation. Look at the beta that is the same effect of its larger and higher dissipation on the in this system. So I will just show you how we fit these things that I say we use the local entity of state members by sdm to see now from here, it's called it as a quantum capacitance. So this is now the bonding and I'm taking states as determined by sds. We put it in the force formula, which is shown on top, where sqe is a quantum capacitor. So we just to make it simple. So as soon as you are before this value in terms of energy, you will be accessing this kind of quantum capacity. And this is now force waves. And you can then vary the force and get the data and you see in yellow, the spectra as measured and in dark, this is a fit. So you see that it's quite coincide. I mean, there is a good agreement, let's say. So you can keep repeating this measurement at different heights. So the only thing we change is the tip sample separation. And you see that this is a clear phenomenon that you see even at large distance between the tip and the sample. So there is an interesting things here, you have different quantities we have the threshold voltage where you start to access. You can see that this is a shadowing of states, you have star which is a threshold force and star which will be the dissipation. And all these quantities are shown here, they are almost always constant everywhere. So basically, even if you increase the tip sample separation, you still see the same dissipation magnitude. And this actually is not really intuitive at first sight. It means that you are created fluctuating current in your sample, but there is no transfer between your tip and your sample. So basically your potential is creating current between the dots, but you have no transfer from the tip and the sample. And this is because if it would be the case, you should have a decrease of the dissipation as you increase the distance. We can also scale because it's a really packed quantum dot superlatives of strongly interacting quantum dot we can from the IFM measurement we can try to get access to tuning range between these dots. So this is something that was introduced in IFM many years ago. So basically you have to look at the width of the peak and do the force of the drop of the force. We could relate this to some frequencies so you see that for the alpha phase would be in the order of 69 kilowatts, I mean 69, 79 kilowatts for the beta phases would be higher. This would, let's say, this would show you how easy it is to transfer electron between the dots in your delocalized states. And with that, I just want the last slide, I promise. I just want to show you that we can also image the things, I mean the dissipation. We will go ahead and talk about that. You can have access to the force. You will see different contrasts when you add the voltage threshold. And you will see the dissipation more over the assembly. The force will change and the voltage will be greater than 0. And you see the dissipation coming from the voltage. And we are really inducing current in the molecular asymptotes with an effect from this. I want to acknowledge that most of these components are measurements. Yeah, maybe not all the insulation on the lifting belt, there's many more. And my office and our kids that provide us really nice money. Right, we have time for a couple of questions. Very nice and clear talk. In the first part of your lecture, you measured the modulus when you put these things is K effective or what that is. That was on your slide number 15. And at the same time at all the same slide you showed the force as a function of distance. The force linear, right but the modulus is defined as force derivative of force with respect to distance. So I just wonder why the modulus is not constant. Slide number 15. This one, you show us a force as a function of distance which is just linear. And the derivative of the force with respect to distance should be a constant right, but that is a definition of the modulus. And I wonder why you get the spike like structure out of these data. This is the one the one on the top. Yeah, this is one in the middle. Okay, I know I understand so. So, okay, I understand so. Okay, the experiment. A bit more information. Just here. I see we are also. I understand why you get that. I just don't understand how you can get these data out of a linear force for the system. I don't understand how it holds me. Well, the one that was just defined as the next. Yes. Contact. So it's essentially constant and then it drops. The top part is not very fast. Okay. So the problem is the stiffness is measured through an oscillation. Right. And this oscillation has given characteristic time. So you're not able to actually see with this oscillation. So this, when the unit snaps off, it looks much longer gross. And it really is. And this is a set of solutions that you can see. And the duration of this oscillation is larger than the process itself. So it looks like this shoulder on the tip. And the other part you can see also in the simulation, there are some, some, some, if you look at the road, yes, you see also some modulation that this is related with the sticks. So we need to move on to the next talk, but we'll encourage more discussion posters. So let's thank from you again.


Hello everyone! Today in this Beast Worm Simulator video, I'm going to be teaching you how I get my gifted, or my Mythic Bees gifted fast. So obviously I have 6 gifted vectors and 18 vector Bees right now, so I need 12 more of those gifted. So I figured I'd make a little video about how I'm going about getting those gifted and how you can do it fast. So if you're one of the little guys, if you're like Jeremy, you don't necessarily need them gifted, there's 3 main ways of getting gifted Mythic Bees. It's...oh he's doing jelly. Basically Star Treats is the first way, Treats is the second way, like Favorite Treats. And then the third way is Royal Jellies, but that's extremely rare. So I'm not going to go for the Royal Jellies method because it's 1 in 6 million Royal Jellies chance to get... Why is Shadow Falling? So 1 in 6 million chance from Jellies to get a gifted Mythic Bees. So I only have 1.6 million right now, meaning I wouldn't even have that good of a chance. And it's actually 1 in 24 million chance to get a specific gifted Mythic Bees from Jellies. So that's not necessarily the way you want to go. I would recommend Star Treats and Favorite Treats method. So that means getting tickets fast and how to get sunflower seeds or strawberries, pineapples, blues, how to get those fast. So my counts are all around 3,000 for my treats. And it's a 1 in 24,000 chance that when you feed a Mythic Bees their favorite treat, it will go gifted. So if I feed 50 right now, chances are it's not going to go gifted. And if I feed another 50, chances are it's not going to go gifted. But if I feed 24,000 at one time like I did to this fella, it will probably go gifted. So how did I get 24,000 sunflower seeds? The answer is Macrowing. So if you don't know how to Macrow, if you don't know what Macrowing is, I would very much recommend Critical HD's video on it. It's somehow, if you don't know who that is, but you know who I am, that's probably a miracle. You should go check his Macrow video out. That's how I got 24,000 sunflower seeds. It's how I got these 3,000. I'm going to save up to 10,000 and get more. But basically, just by going AFK, I can run and then make a ton of sunflower seeds. So you can do that with most of the treats. Macrowing is the best way to get them, feeding them, hopefully you get lucky. And that brings us to the second way, the Star Treat way. So we all know what Star Treats are, but they're also, they're always extremely expensive. 1,000 tickets each, that's over like 2 trillion honey in tickets for me. But anyways, how to get tickets fast? If you haven't seen AR Animates video, or AR Roblox's video on tickets, how to get them fast, go watch that. But I'll explain how I'm getting tickets fast. Obviously killing my stumps now, 50 tickets every time, or more actually. You can get up to 250. And then what I do for around a guaranteed like 40 tickets a day. I do Windy Bee, and at my level I can get around 20 tickets from one run of Windy Bee once a day. And then also Meteors, I basically do my Meteor showers for the tickets. It's a bit weird, but I can get around 10 tickets from that. And also from Lucky, King Vito, and Tunnel Bear Drops, you can get tickets. So then you just, and also Sprouts, but those aren't necessarily the best way to get tickets. So yeah, that's how I get tickets fast. You can also get a Star Tree from Mondo Chick, although extremely rare. You can get them from Fireflies, although extremely rare. You can get them from, you can get them from at 100 kills. And it's actually a 100% chance for that to happen at 100. So there's not many good ways of getting. Tickets are Star Trees very fast, but feeding them to the bees. But something I would recommend, even if you really want your Gifted Mythic, please gift your events first before you gift your Mythics. Mythics are very beneficial, especially early game, but they don't necessarily need to be gifted. My friend Shadow got extremely lucky with a Mythic Egg from Mondo Chick, and then he hatched it and got the Gifted Vector, but that chances are it's not going to happen to you. So yeah, that's my guide on how to get Gifted Mythic bees fast. It's a very end-game thing that not many people actually need, but thank you for watching.


Nuba is a new capability in OCS4 under the name Multi-Cloud Object Gateway. They can run on-premise, they can run on multiple data centers, they can move the data and have a hybrid so they can easily move applications from on-premise to the cloud. So we actually provide the data portability very easily and they can even have multi-clouds. So from the developer point of view it doesn't really matter. So it's the same application running with the same target but the data can be simply anywhere. And on top of that we provide a very, very simple and efficient layer which provides both data efficiency and security. So all the data is encrypted in rest and in motion. So even if someone breaks into my cloud account because we separate the keys from the data, it is safe. And again, the idea is that the developer has a very easy way to use the service while the administrator has the ease of use of deciding where is the data.


Hello. Thank you all for coming. My name is Tim Plunkett. I'm a principal software engineer at Aquia on the Drupal Acceleration Team on the co-initiative lead for the layout initiative and the primary author of the layout builder module. Do I need to push this button? Are we good? Great. Thank you. So the good news is layout builder is stable. The other news is that that's not really news. That's been true since May. But so the 8-8 release, which is coming out in a month, will be the second release where layout builder is stable. Still something to celebrate. What's happened since then? 12 bug fixes, a couple more criticals, a couple minor cleanups, one feature that allowed for custom labels for sections, which isn't really that much there. Why is that? The reason is that in the last six months the focus has shifted away from the stable layout boundary core to contrib. Now that there is both a stable layout API and a new module with the UI patterns that have been added, contrib is really where the focus has been. There are a lot of new, it's kind of an experimentation ground for all the new ideas. So I'd like to talk primarily about that. So as the 8.7.0 version we launched was sort of the MVP, the minimum viable product. We had to hit that deadline, otherwise it wouldn't have been stable six months ago and we'd be waiting for it for next month. So we left out, there were some of the things that were left out that we knew would be good but we just didn't have time to land in time. The other thing is that there wasn't really time for user testing. We had had feedback on their initial designs, but from the time we had the designs to the implementation, there was no time to actually validate the implementation and see if it really actually panned out when people were put in front of it. And while the functionality has been really well received, the user experience really isn't quite there yet. And for me, I want it to be just as good to use as it is, the functionality is really not worth it without a nice experience for people, for the content authors, for site builders. The end user of your site won't be able to tell the difference anyway, but as a core module, I think the user experience is really important and we need to sort of improve that. The good news is that there is a contrived module currently called it Layout Builder UX, LB UX, and it's kind of implementing some of the designs that have been proposed. There's been a couple of different improvements suggested. We've only built one so far, but the whole module could eventually be moved into core. There's a lot more work to do. There's both more, as I said, there's designs to be implemented. There's also a lot that could be suggested. A lot of suggestions needed from end users, from the community, from everyone. But one of the struggles there is we don't really have, throughout all of Groupal Core, there's no real way to share designs between designers and developers in the community to sort of iterate on those and comment on those. I noticed that, for example, the Claro initiative used Figma. It's a great success. So far with this work, we've been using a tool called Zeppelin, but it's not really integrated into the Drupal Issue queue at all and there's oriented Drupal Slack. So it has been a real challenge to sort of take those proposals and then work on them as a cohesive group. So if anyone has any suggestions on that, that at a meta level is very important, in addition to the actual designs produced by those tools. Another module we've been working on is called Layout Builder Everywhere, which is maybe not the final name of it. It's kind of a placeholder name inspired by the Panels Everywhere module, if anyone had ever used that. The idea is that you can use the Layout Builder UI to configure the header, the sidebar, the footer, the regions of your page around the main content. It includes a nice little integration with the Toolbar module, which I will show you. It's not quite done. There's a couple of known bugs, but there's a lot that could be done there. And it would be really nice, as you'll see from my demo, that I really don't like the block UI. I worked on the block UI twice. I reread the block UI twice and I still don't like it. And then I think this is maybe the third time in the charm, we'll be able to remove that sort of way of interacting with your Drupal site and really embrace the layout of the UI. So I'm going to take a breakdown and demo these two modules. I'm going to try to do that. There we go. All right, so this is a stock Drupal 8.7.0 install of Umami. This is just, as I said, I've made no changes to this site. So the Umami by default uses Layout Builder, but Layout Builder only currently focuses on this main region.  So there's this body field which has all this text. There's the picture, there's these tags. It's not really clear exactly where this tag section ends and where this picture begins or if that's part of this body or if these are all, these paragraphs are one thing. There is an ability to toggle the content preview off, which will allow you to see that this is actually a tags field, image field, body field, et cetera. But this is just sort of the only real way to be able to do that. It's either all or none. You either see your content or you see just those placeholder labels. The other thing is that this, as I said, only affects the things in this blue box. You can't change anything in your sidebars over here in your header. So if you really want to put a new block above this more featured articles, you can't do it from this page.  More featured articles is on the page. You have to go down and read through this sidebar. It's probably the sidebar. So if I just place any old block in the sidebar, you know, I'll save that. Then if I refresh this, maybe it'll be there, but I still don't see it.  And that's a lot. There's a lot of steps there and there's a lot of confusion. I happen to know exactly that Block Layout underneath Structure was exactly how you did that. If you're the content author, if you're just a site builder that has not been building the underlying structure of the site but is more focused on the end part, I don't know how you know that. I don't know how you find that. That's not discoverable. But you know, at the end of the day, there's your block and you're happy with it. That's fine. And you can from here, using Quick Edit, you can, you know, change the title of that. That's nice. But that's not enough for me. So the Layout Builder Everywhere module, this is a new, a different site. Same install, but I've installed one module, which is Layout Builder Everywhere. You'll note that the Layouts tab is gone. It's now up here. We're in View Mode. Now there's a new Layout Mode. If you click Layout Mode, you now see a visual representation of all your regions. All of these regions are all global. You have your sidebar, you have this one down here in the footer, and then you have your content region.  And you want to add a new section. Let's add a one column section for now. And in this block, we can add our powered by true pull. And there it is. And then you can hit Save. And you never had to leave this page. You know, there's no more digging through the admin UI. There's no more wondering where it's going to show up. It's going to show up exactly where you put it at the top. If you want it to be somewhere else, you can move it somewhere else. So that's sort of the idea between Layout Builder, a Layout Builder Everywhere. Going back to this Layout tab, you'll see this is the... So those are stored as configuration. All those changes in the sidebar are stored as configuration. As this is a node, any changes to this node's layout will be stored in the content itself. It will be revisionable. It will be content moderationable, publishable. It will be translatable through the normal entity workflow. But you can even see here this has changed to published drafts, archived. And this still... This inherits, you know, the fields that are defined above it, like the... At the display level, for all articles will have their fields in this order. But maybe on this one, you really like that picture and you want it to be above the tags. So once you save this, you are editing the layout just for this specific carrot. Let's hear it for the carrots article. The thing is, this still doesn't resolve the issue of being able to understand exactly what it is that you're moving around, as I mentioned before. Once you click into here, you still have the same problem. So that's where the... I'm going to install the Layout Builder UX module and wait for it to install. I don't have a third site.  There we go. So when I refresh this, you'll see slightly different UI here. So now, as you hover over them, it'll tell you exactly... Let's make that a little bigger. Oh, that's too big. There we go. You'll see exactly what field it is that you're manipulating. You can see the section name, you can see the different fields. If I want to relabel this section field, this was the one feature we landed in the last six months to my cool section, then it's labeled as my cool section, which for some people, helps them with their... Mapping out the page, what that section is intended for. Because you can have many different sections, you know, you have a four column, and you could even... You could call it four column, or you could say like, this is important for whatever reason, to communicate to your content authors. That's what they should really be using it for. So that's Layout Builder everywhere and Layout Builder UX modules. They're both available on Google Work as contributed modules. As I said, they may eventually make their way into core. There's a lot more we want to do there, but that's what we got so far. Jumping back in. So Layout Builder Styles. So those two modules were written by me and my team at Acquia. These other modules are written by other members of the community, some of whom have been participating in the Layout Initiative for years, some of whom just had a really good idea and one day decided to help out. Layout Builder Styles is great. It allows you to define specific styles via... Like you provide a separate CSS classes, and then your friend and designer goes and decides what CSS is actually loaded for those classes, and you can name these styles. So I'll show you an example, but the important thing, the feedback we got from Layout Builder was that it's too powerful. It allows you to do too many things, or it gives too much power. And so as you'll see from the next couple modules, most of them are about reining in that raw power. And this module to me is a good fit for my trip, not necessarily for core, and you'll see why. So let's see. If I go... I've already set up one style. I'm going to get rid of my This Is Important section. Not that important. If I go back to my Cool section, you'll see this style drop down. I have no style. I'm going to make it fancy. It's the one style I've set up. So now everything is purple and cursive, because that's fancy means. So if you were to, and if I go and show off the... Let's see, it's under configuration, as I said, that fancy layout push styles. This applies to all sections, and it just applies this thing called my fancy class everywhere to each section. And then in CSS, I have to find somewhere that that fancy means cursive and purple background. So you could even have... Each individual style could have more semantic classes. And you could even have things where it's like fancy right, and it would be like, oh, you know, float right or something. I don't know. I don't really see CSS anymore, so I'm really kind of behind on this, but I know it's really cool. You can also define these styles to be available for both blocks and sections. So this is a section level one, so it'll apply to everything contained within it. If you use it on the block side, it'll be more granular. But once you... If I go back to this, as you add other styles with just any label, cool. What's the... Yeah, cool. Let's see. My cool style section. I don't have any CSS written for this, but so it won't really do anything. But if I go back into my section, now I have cool, fancy, and none. So this is really nice way for your front-end developers to provide you a set of styles and then allow all your content authors to choose from them. Speaking of restricting things, the Layout Builder Restrictions module, by default, everyone on your site can place every block on your site. They can use every layout on your site. That can kind of both be overwhelming for them as just the choices available are things that you may not ever really want to place. Like, for example, the email address of the author of the article you're looking at, not usually something you'd want to, you know, place or move around that much. So you never want people to be exposing email addresses and you just remove this block from being available. The one caveat is that right now it's global. There's no per-role configuration of this. I know that they're working on that. The problem is that when you take the entire list of blocks and then multiply it by the entire list of roles, you get a page even worse than the current permissions page. So we're waiting for, like, three-dimensional VR or something. I don't know how they're going to fix it, but they need to work on something. So, and that's really truly a problem of court software. That's not just a problem in this scope. So if anyone has any ideas of how to solve, if you've ever thought, I really like permissions page and I want to fix that and make it even better, but I want to be, I want it to be more challenging that you can help them solve this problem. And I could show you this, the playable restrictions. So we're buying. It's under content authoring. Nope. Crap, where'd it go? Oh, is it directly on the thing? Right, thank you. I'm working on articles, manage display, yeah, box available for placement. So currently it allows all content fields, all core fields, all custom fields.  That's a lot. Imagine that, but then all the roles. You can restrict to say, oh, they can't place any forms, they can't place, you know, any views or inline blocks. And this kind of gives you an idea of all the things that labeled or can place. And then you would hopefully say, you know, this doesn't really make sense in an article, or this doesn't make a sense on this content type. And sort of lock things down for your users. Similarly, similarly, there's also you can risk, as I said, you can restrict the layouts, core, live relationships with only four layouts, one, two, three, four columns. But I know there are many modules, especially for the themes like bootstrap, whatnot, that will ship their own layouts. So this can get, you know, this can get kind of long. And you might not want to let certain authors use certain layouts, or you may never want to ever have just four columns. It doesn't fit in your safe theme. So you don't want that one around. So that's your option there. And there you go. So Oh, thanks. So that's a lot about contrib. But what about core? Like that's that was fun. It was fun six months, a good summer, you know, working away from the core issues. That's kind of a nice break after getting everything stable and in. But what's what's next for core? There are a lot of feature requests, or I think I counted like 57 current open feature requests, which is great. Some of them, you know, just like these modules, they could be done in contrib. You know, you don't always need a core patch to allow new functionality. A lot of this could be able to contribute. I call out three here, visibility conditions, section reordering and nested sections. Those would be very difficult to accomplish via contrib. And I think they do need to be worked on directly in core. They also need people to work on them. Some of these issues, like, for example, the visibility conditions, there's already code in place. It's just not quite done yet. And actually, the I think the blocking issue there is that it needs some design. It looks like Drupal six panels, you know, and we don't want the uploader to look like Drupal six panels, we want to look like the uploader. So trying to figure out the best way to allow authors to say, I really only want this block to show up, you know, for this role to the end user, not just for selection, but like actual display, or I really only want this thing to show up on Tuesdays. Any sort of any sort of condition about when and when things are going to be displayed to the end user, we don't really have in core. We have nothing like that in core and except for on block page, the block UI, which once again, I don't really like the block UI. So we need some help there. A lot of these other things like the section reordering, for example, that just that needs user testing that needs people to actually go and say, you know, this doesn't work in Firefox on Windows computers, or this one doesn't really work if I try to use the keyboard. So anyone who is interested in any things can can participate and contribute. Yeah, so there's 87 bug reports right now. We fixed a lot of the bugs before release and as I said, 13 criticals and majors over the summer. Over half of the bugs already have a fixed proposed, which really lowers the bar to helping push those issues forward. Some of them don't have fixes proposed yet. They're just their known bugs. So that doesn't work. We don't know why. Or we do know why we don't know how to fix it. The good news is that nothing's critical. We got rid of all the critical bugs. That was sort of the caveat to becoming a stable release, including the critical performance bugs fixed over the summer. There on Thursday, I will be available with a table of a bunch of people are going to be working on layouts. So please come find us if you're here on Thursday. And also in the Drupal Slack, we are the layouts channel. And there are people all over the world, 24 hours most of the time, there's someone in there chatting about layouts and lots of lots of very knowledgeable people in there who are very willing to help. So please come answer and ask or ask and answer questions there. Yes, this is more information about the contribution on Thursday. So now I'd like to open it up for questions. The trick here is going to be getting people to the microphone, all the people on the floor. They're, in theory, other people come up to these mics, but you have to ask the mic the question into a microphone. Do we all have a room, a passing one? Yes. Because that's kind of wired in. I could also repeat the question if I can hear you. So let's start. Who's first? Someone has to be first. David? Thank you. What point does Layout Builder become the only sensible default for laying content out in Drupal? And should we just deprecate the blocks interface entirely? So could everyone hear that question? Because I can barely hear. Okay, you can hear it. I can't hear it. I think there is, I think that Layout Builder everywhere, this module, is the first between that and the visibility conditions. I think those are the one, that's the one to punch to remove the block UI. If we land both of those in core, I think we can deprecate the block UI. There is no additional functionality provided by the block UI after those two issues land, which would be wonderful. That's the answer to your second question. First question of it being the de facto approach to laying out your content. There is, show of hands, panelizer. Who uses panelizer or has used panelizer? Okay, so I'd say a quarter of the hands went up. About page manager or panels. About half the hands went up. About display suite, about a third. And then, who has used the paragraphs module, but for layout reasons? I feel so bad for the two thirds of the people who raised their hand. Paragraph, just to jump to the, well, I'll let someone ask the question about paragraphs. But to answer your question, panelizer, there's an upgrade path, or a migration path from panelizer to layout builder that is written. It is not yet complete until visibility conditions lands, because panelizer has visibility conditions permitted. So panelizer's gone. That's done. You don't need that anymore. There is an issue, this was asked yesterday during the keynote, about using the layout builder UI on custom routes, or on pages like page manager defined pages. There is a patch in the, sorry, there's a patch in the page manager issue queue to adopt the layout builder UI, which then will allow you to continue using the functionality that panels is provided in D7, or page manager provides in D8, but with the familiarity of the layout builder UI. So that one's done. Displaysuite, I'd say, Displaysuite is an interesting module, because Displaysuite, the module itself does a couple of things, but there are a lot of Displaysuite extras models. There's a lot of different, Displaysuite field, Displaysuite template, Displaysuite, there's a lot of extra stuff there. The core Displaysuite functionality is already covered by layout builder. In fact, when we wrote the modules in the first place, it was, we want to take the 80% best case of panelizer and the 80% case of Displaysuite and combine them. And that's sort of how we ended up with layout builder. So I can't really say that all of the extra parts of Displaysuite are solved, but they're well on their way. So to sum that up, I think that already layout builder has become the de facto layouting solution for new sites. And even for those that are on panelizer, with the migration path, it should become the de facto solution for all sites that are existing that have been using panelizer. So that would be, that's what I would like to see going forward. Thanks for the question. Who's next? So while testing layouts, we were trying to replace paragraphs with layout build, as you mentioned, but we failed hard with translated blocks and revisions. So the question was about migrating from paragraphs to layout builder, but hit stumbling blocks with regards to translation and revisionability. The revisions things worries me because revisions are supposed to work fine, but if it's revisions and translation, then that makes sense. Layout builder, currently there are two contributed modules that provide layout builder translation approaches. One is layout builder AT for asymmetric translations, and one is layout builder ST for symmetric translations. There are, layout builder itself does neither. It just doesn't supply, provide translation support. And the main reasons we really couldn't pick between the two. And I had, which one were we going to pick? AT or ST? Or do you want to come up and answer it? Guess, phone a friend, Ted, who wrote both of those modules, has got to come up and answer that question. Who wrote the other one? I think it was the guy, the display suite, Svensil. Oh yeah, so the display suite author, Svensil, who's here somewhere, also wrote the other one. Thank you, Ted. So basically we kind of ran out of time for translation. So to be clear, translations work for layout builder in the sense that if you place a field, it will show the right version of the translation. So don't feel like if you have a multilingual site, you can't use layout builder. If you have a view that you place and the view is translated, it will display the right version of the view. So don't, like, there's a lot of use cases that aren't not covered, but the basic use case of if you place something and it's translatable, the rest of Drupal takes care of that. But the ability to have different layouts per translation, our goal for core is what basically the layout builder symmetric translations does. And that is basically like your layout will not change per language. And we wouldn't, the idea right now is we wouldn't let you change the actual layout, but everything you put in the layout as far as inline blocks, other strings, and plugins that declare translatability, you'd be able to translate it, but it'd be in the same place across languages. Asymmetric translations would be that you have a different layout completely per language and it's sign of totally divorced. There's no sinking between languages. If you have a Russian page and an English page, you can have them totally different. That's sort of more of a localization than translation. So the goal for core and the thought from the product managers was having this totally different per language without having the ability to sync them is kind of a no-go on a product management standpoint, because if you want the layout to be the same, but just have like your inline blocks translated, it's very difficult to do that manually. So if you have like six languages and you try to like, okay, I'm going to change this, put this block over here, and now I have to change it in all six languages, that becomes very difficult. But so the first one would be get in the symmetric translations, 9-1, I guess, would be the earliest at this point. And then is there enough use case for the other one? But if you want, take a look at the layout builder symmetric translations and asymmetric translations in contrib and file bugs or whatever. They both, I think, work pretty well and they have a fair amount of usage. Thank you. That was Ted Bowman, Ted Bow on Dribba-Lawr, thank you. So for the paragraphs case, the symmetric translations with inline blocks would be the close one. That's already solved in paragraphs, but what about copyright moderation, like drafts, untranslated? So the content moderation of, well, so revisionable, like content moderation, publishable translations is already, that's a solved problem in theory by the interaction of those two modules. And I didn't think that layout builder complicated that. If there isn't, so if we're stacking all of those things, and there's still bugs, and you're using layout builder ST, file a bug report in that issue queue, because that's a problem. I think also paragraphs makes a different expectation than boredom as far as so. So paragraphs has a very different sort of data model and workflow to get through that. So it doesn't quite line up one-to-one with inline blocks. So there may be a way to solve the problem you need. It would probably be very hard for, the stumbling blocks would be in the migration, not necessarily in building the solution. So we can talk about this more if you're around on Thursday. Next question, there was, okay. How do you see, I know there's currently an issue exposing layout builder information via REST and JSON API, how do you see the future of layout builder working with decoupled solutions in this household? Okay, so the question was, current, well, layout builder does not currently expose any information over REST or through JSON API. And there is an issue to allow that. But assuming that we do that and allow them to read from it, A, which should be easy and fine and safe and not scary. That's one thing. What if we go the full route and allow writes and everything else? And what's the future of that? Honestly, I don't have personally a good idea for the, I don't have a vision for that. I think it's kind of exciting. There's a lot of open-endedness there. I don't think the only reason is that we were trying to land JSON API and layout builder module in the same release at the same time. So the decision by the product managers of Drupal Core was to just turn off all JSON API access to layout builder just so we didn't, on the last day before the deadline, introduce some major catastrophic bug. There's no real reason for it to still be off other than just momentum, that she needs some effort. But I think that in the same way that when we landed layout builder and we took a breath and then a lot of contrib modules sprung up, I think if we enable JSON API access to all the layouts data and then take a breath, I think there will be a lot of interesting stuff proposed, either for core or via contrib. And if you have an idea, please share it. Like there's a lot of cool stuff we can build. So thank you. Yeah, on Thursday, if anybody's around, it would actually be very easy to open that stuff in a contrib module, but nobody's actually done it. So if you're looking to be like, we want to make it be couple of layout builder, let me know and there's definitely, you can open up the event yourself, but then you're on your own. Yeah, so as Ted said, there's, in addition to the patch and the issue that allows you to have access, you could also, if you don't want to run a patch for that, you could enable that access via contrib module, but then as you're on your own, in terms of accidentally letting people mess with your stuff. So that's kind of scary. Was there another hand over here? Yes. One big issue I'm seeing is the roles and the permissions. So for example, having a certain section of the layout builder be accessible for an editor and not for other roles, something like you mentioned during the slides, is that something that's rather picked up by more or that you just offset in the culture? Because that's, for us, for example, that's a new operator for using it. And that's why we use paragraphs for a lot of stuff that would make more granular control of the area. Okay, so the question was about roles and permissions and granularity in terms of editing sections, especially in comparison and contrast to paragraphs. Yeah, there are, when we were working on the module, there was one permission, which was do all the things. We split it into two permissions per content type. So for articles or recipes, you can enable the ability for anyone with that permission to edit the layout of that content. Or there was another permission where you could let anyone who already has edit access to that content be able to edit the layout. So one is where you just want someone who can only do layouts who comes in and can't even edit the words on the page but can move things around. That's one permission. And the other one would be for them to be able to do anything. That does not address your specific concern of being able to lock down individual sections or individual fields or inline blocks. And you're right, there is a gap there. I think that I don't know of any issues where people have raised that as a problem. And more importantly, people haven't told us what they want. So I can ask you very kindly to open that issue and say what is wrong and what you want it to be. The thing with permissions is that every permission is kind of, they're all provided by individual models. So you end up having the same discussion over and over and over again. There's a very long running issue about the block UI, the one I want to kill, that has one permission and it's administer blocks. And it's considered, you only give that to people that you trust. And if there's a security vulnerability related to that permission, then you shouldn't have given them that permission.  And there was a very long running issue to granularize that more. And yeah, it's a fight you have to keep fighting on every module. So if there's specific things we can learn from paragraphs with regard to that, then we should. Layup by restrictions, does it solve some of that? Layup by restrictions does not solve that because, well, I mean it addresses some of it in terms of saying, oh, you can't add that one field or whatever. But the more complex things like, you can't add the header to the first section or something. Or only people, only certain roles can edit the top of the page. And everyone else can only mess with the bottoms of the page. Any sort of granularity there is currently, must be done custom. It's doable via hooks and stuff. You can define your own system, but that would, you would have to bait your own business logic into the code. There's no UI for that. Correct. Next question. There's no more questions. Okay. Everyone knows everything? We're good to go? Is there anything anyone would like to see demoed? Ted? My first question. What is the thought about enabling Layup Builder by default, say, on content types? Okay. So the question was when or how do we decide when to enable Layup Builder by default on content types? So the good news is that it's already enabled by default in Umami for recipes. And as far as I know, they're working on making it for most of, for all of the content types. With that change in Umami is very politically straightforward to make. Technically, it's the same work for all of things. But making that decision in Umami is straightforward because that's a demonstration install profile. It won't need, you don't need to push that changes out to new, to new people. Making changes to the standard profile has been difficult and slow going. There are, for example, in Umami, there are lots of complex, or custom block types where you can have a header, a banner, what's the hero image? It's like the new, it's not a new term. Hero image has been a term for a long time, but it's new to Drupal via Umami. Whereas the standard profile only shifts with basic block, which is quite the term. And it doesn't have a level and all installed at all. I think most people just avoid making changes to standard profile because it's too hard to fight to fight. And they just do it in Umami. They do it in contrib via the lightning installation profile. I would like to think that maybe with the changes with Olivero coming in, that Olivero could be built with layout builder at the forefront instead of using the old page templates and stuff. So I think that may be the way to get into that instead of trying to modify Bardek to be layout builder-y. But anyone can pick up that and propose a change to standard profile that's used it. What's the next? We have like five minutes left. Suzanne. So I did some testing of the layout builder, not used in the way that it's mostly been demoed, but used as a landing page builder tool. So it has no, it's used with a content type with no fields. And there were certain things in terms of the UX that were problematic. So I'm wondering in terms of solving for that use case, if you think it would be best to build some kind of contrib module or if there's room to make any configuration changes before? So the question was, I'm going to try to get this right. So no, it was using layout builders mostly been demonstrated as a content operating tool for specific content that has a lot of structured content with fields and whatnot. And when using layout builder for a content type with no fields in terms of basically replicating a layout, a landing page builder, the UX choices that we made don't make as much sense. Everything was catered around fields. And so what do we do about that? And I think the answer is twofold. One, in the short term, just because people already use page manager or panels for landing pages is finishing that work to bring the layout builder UX into that and then make those specific choices in that module. The other option would be to abandon all the baggage of page manager and panels and all the expectations that comes with it and focus specifically on solving that one problem in a dedicated contrib module with the intent of eventually putting it in core. I know Dries has specifically said he wants there to be a very streamlined landing page flow. And that's the thing that we need to build, but no one has taken it on yet. But I would really like that. I think the idea of being able to tailor it to that specific experience and not just reusing the same thing that we're using for the field-based one would be really great. But as far as I know, there's no work specifically focused on that. I'm curious. Is this on? It's on, but you have to get really close. They have to talk really close. I'm curious because I wrote the paragraph box module a while ago. It has very little usage and it's not really the workspace that I work in on a daily basis. But a lot of people raise their hands that they use paragraphs. Is this a useful module still? Paragraphs block, paragraph blocks rather as the most probably, is I think extremely useful. And I think like in the layout slack, I think it's mentioned like once a week at least, especially for people who are already on paragraphs and want it. So just the short version is that it exposes each of your individual paragraph items as two layout builders so that you can rearrange them. Which is great and really cool. And especially solves that use case of people using nested paragraphs to achieve a layout solution. I don't know that, I think as inline blocks improve, people may move away from it if it solves their use case. I think paragraph still has a very, very specific use case around authoring. But I think that inline box blocks and layout builder will sort of decrease paragraphs usage for things it wasn't intended for. As far as I know, the paragraphs authors are thrilled that we're finally doing, because they never wanted anyone to use it for layouts. So they're happy that the module is finally being used for what it was intended for. But no, I thank you for the having paragraph blocks out like over almost a year ago now, right? Time flies. Has really helped adoption of layout builder and really lessened the burden for people using paragraphs. Question in the back. The question was when sort of administrating or auditing a site, how do you identify which nodes have been overridden with layouts? And there is an issue for that in the queues. It's, and I wrote a patch for it. It basically just like lists them and gives you a reverb button or something. Like, it doesn't do anything more because we don't, I don't know what people want it to do. So we can talk, or you can jump in that issue or I can point you to that issue and then you can help us tell, like, tell us what to do or suggest something, you know, Ted. But currently you can make a view that filters on overrides. That's right. So it's not hard to do and it doesn't help you revert them but it'll help you identify them. As Ted pointed out, just for the purpose of listing them to literally just know A, how many you have and which ones they are, you can make a view and filter to only include ones that have layout overrides. So that's a very not great but short-term quick fix for finding out what the scope of your administrative nightmare is. In the front. So this is maybe more of a meta question about the sort of layout and config and triple nine. And as a sort of more DevOps person, one of my big frustrations is people demanding database backups for the purposes of matching up, like their block config to the content UUID and I'm tired of having the argument about, you know, not exporting databases to do that kind of thing but I don't have a great answer. I know it's a broad question but like at some point, I think like the layout ecosystem has got an answer for like that content other than just saying like your block is busted. Yes, so the question was syncing, so syncing the content and config of blocks and layouts between environments is very difficult because if you just push your config, it references UUIDs of content entities that do not exist yet.  With Layup Builder, it's very similar. It's not as bad. It's not better. You can use Layup Builder in theory to sidestep some of those problems but really you can't because as soon as you start placing those blocks that are created, you have the same exact problem. So it's, the same problem exists with menus, for example. Menus are content and config. The fact, the menu blocks are config but menus themselves have to be created. I don't like the idea of making that our problem but no one else is solving it so maybe it can be. Yeah, it's a very long running problem. It was like the one major unsolved thing when we have CMI. It's like everything's great except for that problem which is a huge burden and you hit every time you build anything remotely complicated. So yeah, I know definitely don't have an answer for you. We, everyone I think, everyone who's been writing configing content entities that work together has been waiting for someone else to solve it and it just hasn't happened. But I'm sorry. And there was one last question in the back. Is there any thought about supporting web components? We have an external design system called OPE which makes the web components any thoughts around that? So the question was about web components and integrating that. So I don't have any thoughts about that but there are thoughts about that. The idea is that anything can be exposed to lay up on it. Everything, anything can be. Like paragraphs, blocks. Paragraph blocks is a great example. They just pull all these paragraph individual items out and you can now put them in a lamp utter. There are about half a thousand different ways you could do that. The problem is just finding which one was the best one or finding the best practice. So I would, I don't know of any models that are already starting to do that. I'm surprised that, I would bet that it's going to come soon. It is extremely doable. And whether it be, I think that's the problem is that there's such a proliferation of component libraries and systems that live outside of Drupal in people's minds and in implementation that it's not as clear to tie them to each other. But it is absolutely possible from within Layup Order to expose anything. And then you could use Layup Order restrictions to turn off everything else. It's not a component. And then, you know, lock them down to that, to your system. So it would be really exciting to see but as far as I know it does not exist yet. I believe that's time. So thank you all so much for coming.