Hi everyone. So thank you all for joining us today to learn about open orgs. We're really excited to present the service that's so vital to data quality and its newly launched website. So today we'll start off with presenting open orgs and the rationale behind the service and why it's important for the open air graphs data quality. After that we'll run through the new website and then break down how you can participate and contribute as an open org curator yourself. And then we'll finish off with 15 minutes of Q&A at the end. So we kindly ask you to keep your microphones muted but in this case don't think you have a choice. And we'll open the floor in the end to the Q&A's where you can either raise your hand, post in the chat or in the Q&A section. So with that said I'll pass the floor over to Ivana to get us started. Hi everyone and thank you for coming. Just let me share my screen. Do you see it now? Yes. So thank you Ivana for the introduction. I'm here today presenting to you my colleague Martina and also me. What we will talk about in a second. Let's go through the agenda for today. First off we're going to talk about this pretty common issue, the challenges that come with organization affiliations. Next we're going to talk about solving this problem through open orgs and give an overview of the service itself, what deal with it and how can you benefit from it. Then we're going to skim through, as Ivana said, our new open orgs website. We'll navigate the sites together, pointing out key features and how you can make the most of it. And then it's my colleague Martina takes over and it's all about you and our curators. We'll talk about how you can pitch in and help because community expertise is the backbone, you can say, of what makes platforms like open orgs work so well. We'll also delve into why your knowledge skills are invaluable and how you can share them with the community. At the end we'll also share with you an invitation to an open orgs training, which is a great way to learn more and get comfortable with how you can contribute. And finally, as Ivana said, we'll wrap up with the Q&A session and some concluding remarks. This is your time to ask questions and share your thoughts. Other than Martina and me, I think our colleague, Claudia from CNI is also here. She's more knowledgeable, we can say about technical stuff behind open orgs. So if you have questions in that domain, Claudia will be here to answer those. So let's start. And let me start by emphasizing the catchphrase that has become synonymous with open orgs. It's evident in the past webinars and sprints. And also on the portal I will showcase later. So breaching registries of research organizations. We can say that this title captures the core message of the service itself, which acts as a tool for creating the connections between existing initiatives that maintain the identities of organizations involved in the research ecosystem. So open orgs addresses a critical need within the open air infrastructure, offering an added value to other open air products. So essentially it's a tool for managing disambiguation of organizational entities and enhancing the metadata quality that describes this entity. So let's address the problem at hand, the ambiguity of information, which significantly impacts the quality of data foundational to a scholarly communication system. Specifically, regarding organizations, information is scattered across various data sources, leading to inconsistent representations through legal names, full names, acronyms, short names, aliases, etc. Moreover, organizational structures often appear unclear, such as the division into branches, faculties or departments, further complicating clarity across data sources. This ambiguity poses a substantial challenge, making it imperative to disambiguate this information to ensure the efficiency of the scholarly communication system. Also, this ambiguity not only affects the entire system, but also complicates the development of robust services essential for advancing open science and science in general. So why do we need this unambiguous clear information? For example, clear information is crucial for researchers seeking to search and discover enabling services that facilitate the findability of research outputs. Then research performing organizations require services to aggregate and showcase their scientific production. Similarly, research funding organizations need monitoring services to have consistent information on the impact generated by their funding. And in general, all stakeholders want open science services that are functional and up-to-date, highlighting the critical nature of this disambiguation issue. Within Open AIR, organizations are introduced through the Open AIR aggregation subsystem, which gather information about organizational entities from a diverse range of data sources, each presenting the data in its unique way. On the left side of the screen, you'll notice names such as OpenDoor, R3Data, Cordis Grid Roar, and others, which are key contributors of organization lists to the Open AIR. And because we are collecting information from many different sources, it is not easy to determine whether the information refers to the same organization. Organizations are mentioned in various ways, as responsible bodies for managing data providers, as managers or beneficiaries of projects, and as affiliations of researchers in the full text of articles and papers. However, how harvesting data from these sources presents challenges, such as the lack of common identifiers across all initiatives, despite the existence of IDs for organizations. This often results in the same entity being represented differently across sources. And just an example here, how this looks in OpenOrgs when it is already curated, we can see here all of these different versions of the same organizations that come from various sources. So here we have OpenDoor, National Science Foundation, Richard Bosco Institute Library, this is from the project database, etc. So these are all the curated replicates of the same institutions. You see here that different names can be used, names in English, names in the national language, etc. So this often results in the same, sorry, the primary issue in reconciling this data is disambiguating and finding duplicates among these mentions of organizations. OpenAir began addressing these issues through an automated system that despite being configurable to various criteria, faced uncertainties due to data incompleteness, the current matching algorithm employs a method that groups organizations by legal name and website URL then performs a fair rise comparisons within each group. However, a significant challenge is the often lacking comprehensive information across different data sources. Among the fields that describe an organization, only a couple of characteristics could be used to drive the matching. Namely, you can see here in this table the legal name is basically always present as a strongly distinctive characteristic along the website URL. In many cases, other information is not available. So as a consequence, an automated mechanism cannot really take a decision at its own alone. The two states, the two mentions of a given university or research institution or school are the same or not. So even if it's let's say a large portion of the data was correctly disambiguated, the uncertainties start to harm the quality of the results at the end. So these inaccuracies or limitations in disambiguation pose several issues, such as generating false positives that then skew statistics and affect the reliability of searches in open-air portals. If our data isn't precise, we might miss some important details. For instance, if we are focusing on just one org in open-air, you might not see all the services or products it offers. Similarly, if we try to look at the big picture and consider all institutions in a country, we might not capture all the relevant services or products for each of those institutions. Also, when using a search tool, for example, like open-air Explorer, to find information about a specific institution, we might end up with several entries that in reality refer to the same place. This makes it hard to get a clear and accurate understanding of what we're searching. On the other hand, false negatives can also cause similar issues. For instance, when different aspects of the same organization, like its research papers and projects are treated as if they belong to separate entities. So let's say the project belongs to the University of Zagreb and the research papers belong to Zagreb University. Essentially, this means we might overlook that all these aspects are actually part of the same organizations. But for some case, it has a different name, even though it's the same. The visuals here resemble what was the previous approach in open-air. Initially, there was a direct link between the application system and the open-air portals. This means the results from the application system would automatically show up in these portals here. However, due to problems with accuracy and reliability, as I said, the decision was made to remove this direct connection and that's when open-air was introduced. This system acts as a middle layer, we can say, between the application system and the public portals. As you can see here, within open-orbs, the metadata curators play a crucial role. They review and mediate the information produced by automated algorithms before it is shown to users on the open-air portals. Well, this change aims to improve the quality and reliability of the information that users see. So, as we have seen in the previous slides, open-air services benefit from organization disambiguation. Services that are most affected with this situation and the problem of ambiguity of the metadata are these that you can see here. So, open-air explore, monitor, connect, open science, observatory. To these services, the curation work can be really helpful and useful because the organizations resulting from the data application and enhanced by the user feedback are indexed and then exposed by the open-air portals. So, in summary, we can say that the process of organization disambiguation significantly enhances the effectiveness and utility of the open-air services by ensuring that data and metadata are accurate and clearly attributed. This in turn supports better research outcomes, better interlinking of research outputs, enhanced discoverability, more effective monitoring and the advancement of the open science initiatives. So, to recap and give you an overview, open-orbs is essentially based on three main activity pillars. The first is automated approach. We have, as we said, an algorithm which detects a similarity between organizations and it establishes this similarity, but that has to be accepted by the curator. So, the second step is the manual management of duplicates. This enables curators to manage these duplicate suggestions by either confirming or denying them, recognizing that some decisions can only be made by humans. And the third pillar is the metadata curation in which the curators can enrich the quality of data, basically, and improve the findability of organizations within the large space of data that open-air has developed. So, that's it on the short intro. Let's hop on to the new portal, open-orbs.openair.edu. So, yeah, let's hop on to it and I will show you what it offers. Just a heads up, although there are all of these complicated algorithms behind it, in the world of open-air, open-orbs is a small rather simple service and the such, we didn't want to complicate things much on the portal itself, but still wants to give you all the info and also provide some sort of online everyday support for our curators. So, when you first come up on the page, this is what you will see. As I already explained, the Bridging Registry sketch page has became synonymous with open-orbs since the beginning, so we wanted to showcase it here also. Right in the hero section, you have two buttons for the tool, I would say, most important things to either explore open-orbs and start the curating or become a curator. We'll go over these a bit later. Other than that, we also wanted to showcase who the key beneficiaries of the service are. We went over those at the beginning, if you remember, when it talks about who actually needs unambiguous and clear information. So, just to recap, the key beneficiaries are researchers, RTOs, RFOs, and basically, in essence, entire research community. Then we have a section named why open-orbs, where you can expect to find information about open-orbs capabilities and benefits, including how it enhances the discoverability of research organization, how it integrates different organizations and registries, resolves duplicates, also curates metadata, and features this curated information on the open-air portals. The next part is very dear to me because it showcases that open-orbs doesn't just talk to talk, it walks the walk. Here you can explore case studies which illustrate the impact open-orbs has on a research collaboration and the global research landscape. These examples highlight the tools, capabilities, and the difference it makes. So basically, by clicking on them, you can explore real cases from Serbia, Greece, and Cyprus. So, let's just click on one of them. If we'll read you here, here you can read all about it, get an overview, see what was the challenge and scenario, how they implemented the solution, and the impact it had on their community. Also, details with screenshots from the service. Okay, let's go back up here and check out the menus. So, on the about menu, two main articles pop up. One is about open-orbs in general, the problem statement, etc., and the other is about metadata curation. Let's check out the first one. So, here we have the main problem statement and how open-orbs works to solve that problem. It is explained that open-orbs works by using automated workflows and curator feedback to deduplicate and manage organizational records. So, this is basically the magic that happens behind open-orbs, but explained in a simple manner. For those of you eager to delve into the net involves of open-orbs, the data curation section offers a deep dive into the processes and practices that ensure the high standards of data quality. We have a few things here, but overall this section of the website highlights the community-driven nature of open-orbs, underscoring its role in enhancing the open-air graph with clear and accurate data to elevate research quality. The things that pop up on this page immediately are the benefits we get from data curation. Martina will mention them later, but let's just briefly go over them. Recuration work in open-orbs plays a significant role in enhancing the functionality and accuracy of the graph, contributing in several ways. So, data quality and accuracy enhance discoverability, interlinking of research outputs, compliance and reporting, facilitating research assessment and metrics, and supporting the open-science movement. Next year we have a section on how you can help and the roles and responsibilities of data curators. Furthermore, curation methodology and these are the activity pillars we talked about earlier. And lastly, an overview of metadata that is available for curation. So, you can enrich organizational entities by adding official name and type, adding geographical location, acronyms, aliases, identifiers of the URLs and relations, which are very, very valuable because you can define hierarchies between organizations such as departments, institutes, subunits, etc., clarifying the structure and enhancing the understanding of the organization's composition and scope. On the About menu, we have a few more articles. The website provides a statistical overview of the services reach and impact with over 70 curators from 24 countries and more than 100,000 curated organizations across 200 countries and territories are that speak to the, I would say, vibrant community and collective effort driving open arms forward. The website also introduces you to the team behind open arms. Here you can meet the service managers, some of the data curators who are actively involved also in the development of the service and all the people who actually made open arms such as developers, data engineers, and data scientists. Also, we also introduce you to the newly formed curation board, which is a dedicated team with one goal to enhance the quality and reliability of research organization metadata globally. Beyond date of the curation test, the board actively engages with the open arms community, providing feedback, answering questions, etc. For new curators joining the platform, the curation board provides training resources, guidelines, and ongoing support to ensure that they are all well equipped to contribute effectively. So whether you're a potential curator looking for guidance or a researcher with questions about our data, the curation board is here to ensure your open arms experience is both rewarding and impactful. Okay, let's go to another tab in the menu called support. And here you have a few things to go over. Let's go look first at the supporting material. As of now, available here you have six tutorials covering different aspects of data curation. So first we have an introductory tutorial called understanding open arms. Then we dive deeper into the metadata enrichment and curation, approval of new arms, curating duplicates, resolving conflicts, establishing relations, and more will be added soon, of course. Other than this, whether you're new to data curation or an experienced curator, our glossary section explains key times used throughout the service, making sure you have a solid understanding of our processes and objectives. Of course, there is also a frequently asked questions section where you can find the answers to most of your questions. We have a general section and also a section about the curation process. So here you can find the answers to questions like what qualifications do I need to become a curator for open arms, or can I contribute to open arms if I'm not a professional curator, etc. My opinion will go over these two. It is important to note that the materials in this menu will be updated regularly. This is something that evolves over time. Of course, we plan on updating the application itself and with that new materials will come probably new functionalities, and the answer is new questions arise and so on. In the menu, we also have this publications section, which leads to the new open-air graph site. This is something for those who want to know even more. You can find here the articles on this application and research more about it. And of course, we have a health desk here with a contact form where you can ask questions and comments, which will then be sent out to our open-air health desk. And another thing you might have noticed in the menu, how to become a curator. This is something that will go over in detail, but just know that here you can reach out to us through this form if you want to join the team and we will get back to you as soon as possible. And the chair on top, let's go back to the home page for this one. To explore the service itself, there are two buttons. One is here in the here section. The other one is in the menu. Click on it and it will lead you to the signing page. And if you enter your sign-in, you will be directed to the open-air service. If you are not yet a curator, you can send a request for becoming one through this signing as well. The interface of the application itself will change in the near future and I hope to make it compatible to the service website we've seen just now. And this is where my tour is ending. And Martina, the floor is yours. Thank you, Ivana, for the presentation so far. And hello to everyone from me. My name is Martina and I am a data curator and part of the newly formed curation board, as Ivana has mentioned. And I'll be talking to you about the role of data curators and how you can become part of our open-air community. So first, let's start things off by exploring how you can help. So as data curators, you play a vital role in curating and enriching metadata for organizations, ensuring that information is accurate and comprehensive. This involves identifying and resolving duplicates, both algorithm-based, as suggested, and manually identified. You also establish parent-child relations to create organizational hierarchies, approve organizations that add them to our database and gives them a stable open-orgs ID, as well as add new organizations to the database, document your insights in the node section, and resolve conflicts through either merging or distinguishing organizations. Now, there are two curator roles in the open-orgs community. The first one is the user. So as a user, your scope of data curation is typically limited to a set of countries. As a data curator, you are editing and enriching the metadata of organizations, you are approving suggestions from the automated duplicates identification, and you are potentially creating new organizations that then depend national admin approval. The second one, so the national admin, the national admin curator role has a similar responsibility, but with the additional task of giving final approval to new organizations, managing user access within their nation, resolving conflicts and making decisions on suggested organization, and finalizing their approval status. Now, why do we need you and what would be the benefits of curating within the open orgs? Now, your expertise is unparalleled, especially when it comes to knowledge of your country's research landscape. Your contributions are vital in enhancing the open air platforms, ensuring that shared information is thorough and accurate. Your input also helps maintain up-to-date and precise data about research organizations. It increases the visibility of research outputs, projects, and datasets, and it also simplifies the adherence to open access regulation, which in turn promotes greater transparency and accessibility in research. Next that I'll be talking about are the skills of a data curator. Now, as a data curator, you will need expertise in research organizations within your chosen country, as well as awareness of major research institutions and universities and national or regional research information systems. You also need to be familiar with national or regional research information systems. Other than these specialized skills as we have labeled them, there are some general skills that we think a data curator should have, and those are the attention to detail, strong data management skills, analytical skills, technical proficiency, and problem-solving skills. If all of this resonates with you, we encourage you to join our team as a data curator. And as Ivana has mentioned, the process of becoming a data curator, if you're interested in it, it's pretty much straightforward. As Ivana has showed you, there is an online form which you fill out and that expresses your interest in becoming a data curator. After that, you will have a one-on-one meeting with a member of the curation board, so either Ivana, Bojan or me. And in that meeting, we will be discussing your role as a data curator in more detail and also answering any or every question that you may have. After that, after that meeting, you will receive a comprehensive training on how to use the OpenOrgs platform. Effectively, you'll sign a volunteer statement outlining your rights and responsibilities. And once you are accepted, you will be ready to start contributing as a valued member of our data curator community. Now, if all of this that Ivana has said and showed you and what I have said about becoming, about being a data curator and becoming one, if this has sparked your interest, we also invite you to join us for an engaging training session on OpenOrgs. The training session is scheduled for the April 15th and it will take from the 2.30 to 4.30 Central European time. During this session, it will be different than this webinar. You will gain a deeper understanding of how OpenOrgs operates. You will learn about the workflow involved in data curation and you will participate in a hands-on session where you can ask questions that are tailored to your country's context. And this is it from me so far. And now we've already had the Q&A time, but if there are any more questions, we can answer them now. Perfect. Thank you so much. Yeah, we do have another question or two. And then of course, so now that the Q&A session is officially open, feel free to also raise your hand. Anyone if you have a question, so you can type it in the chat and the Q&A or simply raise your hand. So first off, we have Will OpenOrgs also have API interfaces for query and use all the collected data. And this is from Jordan Piszczak. Yes, Claudia, thank you. I think I can answer that. For the moment, no, but it's in the plan indeed to support interfaces, programmatic interfaces for returning back the added value built inside of OpenOrg thanks to the disambiguation activities. So I cannot provide yet a timeline that has to be evaluated and prioritized with the rest of other many other activities OpenAir is involved with. But yes, this is the idea. Else, in the audience, if you have any questions, feel free to raise your hand. A reminder that this is recorded. And what we can also do is we can send the registration link here in the chat for the curation training webinar. That way, if you didn't have a chance to get the QR code, you can have that now. So I'll just share that. If you're interested in becoming a curator, we have the training session, as Martina said, on the 15th of April from 230 to 430 CEST. And then here is the registration link. There's a question here. So that it sounds very time consuming. And how is the experience of current data curators in this scale? I'm a data curator and it is time consuming. But once you get in the rhythm of curating, it becomes easier and easier. We will explain more how to curate and what the workflow is in the training session. But once you know what type of organization there are and how the duplicates work and how the suggestions work, I think it becomes more and more easy. So I don't know if Ivana has anything to add to this. I agree with you. I mean, nobody expects from you to work on it eight hours a day. It depends on your schedule. Great. Thanks. The question is if we indicate in OpenOrgs that some records of one Xenodod community are affiliated to an organization, will future records of that community automatically be linked to that organization? So this is about linking OpenOrgs to Xenod communities, same for other institutional repositories. Maybe this is something called you can answer yet? Speak. Hello, hi everyone. Can you hear me? Yes. So to answer that question, the linking between the affiliation information coming from Xenodo depends on the availability of such information in the metadata record that Xenodo delivers to OpenAir, but not only to open it to everyone through the OAPMH export format. So let's imagine that Xenodo exports the raw identifier of that organization indicated as an affiliation of the authors of a given deposition. Then OpenAir is capable to capture that raw identifier and use it to assign all the products to that specific institution. So this is how the integration works. However, if OpenAir is aware of multiple variations of the same institution, then it might be needed to perform some curation, indeed to disambiguate them. In general, in Explorer, in this case, those organizations would appear in multiple occurrences. So until the curation is done, might not be straightforward to identify, to search it and identify it in Explorer right away. So this might need some time to perform the curation and update the index, but that's how it works. Okay. So we have also, this was already answered in the question to answer, but just so we have it recorded for those who weren't able to make it watching the recording. When you become a curator, is that only for your own organization? No, I think it's not only for your organization. You will get the rights to curate all of the institutions in your country. So you can curate all of them. But yeah, if you want to curate on your own organizations, yeah, you can. Thank you. And we have, okay. All right. So another one. We have, what's the benefit of curating data that's not from your own organization, nor linked in any way? Let me talk about this tool. The benefits are, I would say global, because it benefits in your own country.  I can support what Ivana said, or to give another angle. It would in general improve the overall quality of the data so to better support their discoverability. So maybe today some organizations might not be linked to research outputs, but maybe tomorrow they will. Perhaps the platforms that host the products that are from that institution are not today supporting the exposition of affiliation information, but maybe tomorrow they will. So it's important to disambiguate the information anyway to leverage on the persistent identifiers. Thank you. And then we have another one. Is there, so I think Julie said you can respond to this one. Is there any relation between open air and some editor repositories, Elsevier? Yes, I can answer. So in general in the open air graph we are making data exchange agreements with publishers and editors in order to have metadata from them. So this is part of our agreement and the transparency that we have in the open air graph. Other than that, we don't do that much. I don't know if Claudia would like to comment or it's fine. Actually, I think you summarized the situation. As far as I know, open air is only collaborating with some publishers to experiment on some research activities, but that's it. We are getting some metadata from them and some full text from them, but that's it. All right. So that looks like all the questions in the Q&A and the chat. Are there any other questions? I don't think I see any hands raised. I can also add to what was said before in terms of the time consuming activities. It's also true what Martina said, but we are organizing two sprints a per year to help you to do together. So it's going to be also a community activity and we would like you to be part of this creation activities. So don't feel that it's just a constraint from you. It's actually something that it can be of the benefits for the country. You will have more visibility. So we will also amplify the section that is on the creator's activities and how it looks like. So be part of our community and don't be afraid of it. Perfect. Thanks. I mean, we just have another, oh, sorry, it looks like I thought I was muted. It looks like we have another question coming through. So if national curators will do it for all other institutions in the country, how many curators will be accepted per country? I don't think we have a general consensus on that. At this point, we are, you know, whoever wants to and whoever can join, we encourage you to join. What, how will be organized, what the trainings? I think how will the curation be organized? Oh, oh, so who will curate which data? This is something we leave to the teams in the country.  It's up to their, you know, agreement. Can I add something else again to give another angle? I think different countries might require different level of efforts to perform the curation. Some countries do have a lot of reserve performing organizations and might require a more structured approach and finding someone that is actually knowledgeable on how to address that is an immigration task in different languages can be challenging. So once I think my perception is that once a given country has a certain base of curators, then the time will come to organize some meetings, maybe on how to shape the curation activity per country. Some approaches could be reused also in countries that feature similar characteristics, maybe small to medium by number of organizations, of course, but large countries might require a dedicated approach, a more structured approach. But this is up to the specific curation board, so those that do enroll to perform the curation, to organize. Of course, OpenAir will be there to support and to guide them, but we'll see. Consider that by now, who is requesting a monitor task port for their own organization, we are giving the opportunity to create the data, so they will have more curators, more curated dashboards. But also we are open to the members, so if you would like to contribute to the data in OpenAir, but also have an active role in OpenAir, you can contact the nodes of your country and it requires to be also a member of OpenAir, and this will give you an extra visibility and extra opportunity to co-curate, co-design with us the services. Thank you. Will there be a public list of curators? No, but we'll think about it. But for now, no, no, it is not public. So it looks like someone's looking to know if there's already a curator, so how do we know if there's already a curator in our country? For now, you can reach out to us at, I will write an email here, OpenAir admin, and we'll tell you if there is anyone already curating for your country, of course. Anything else? So a reminder, so the webinar is then recorded and we'll upload it to the OpenAir YouTube channel, and then also I think we have the list of everybody here, we can email you those links as well. So you can go back and watch and also see where to find certain things in the website and who to contact when. So no last final notes? Anything? It looks like not. Okay, so I guess we'll give you four minutes, so you have four minutes for your next meeting to get some more coffee, and thank you everyone so much for joining us. It was great to, it's great presenting OpenORX to you all, and thank you again to our presenters, Martina and Yvana, for giving us such a good walkthrough, and it looks like we had some good comments on the website as well. People said they liked the interface and it looks very user-friendly, so congratulations. Job well done. All right, all right, well I think we'll leave it there. Thank you again everybody, and have a wonderful rest of your day. Thank you everyone. Thank you, bye.


Damage control resuscitation is a relatively new resuscitative strategy for patients with severe traumatic hemorrhage. This strategy consists of permissive hypotension and early balance transfusion and transfers the patients to subsequent surgery. There is growing evidence on harms of excessive fluids. Since 2013, survival benefit of massive transfusion protocol has been proven in adults. Despite insufficient evidence, pediatric massive transfusion protocols are widely used in North American trauma centers. This review focuses on the concept of damage control resuscitation and summarizes the relevant pediatric evidence. This article was authored by Jung Hyun Kim, Yura Ko, and Kim Won Jung.


So this both is about handling of the home directory and configuration files in the home directory. And it's basically the fastest priority standard concept for the home directory. There were some other talking during this discussion about making it also about APIs for configuration files. So there will be a library that can handle multiple types of configuration files and convert between them with administrative deferral. But it doesn't quite fit the specification we are working for. And so that we should have to be a separate project there. So I'll start with problems and I'll show you what the current specification is at freedays.org. And the idea is that I have gathered from people for the next version of the specification and how to implement them when we can discuss that or think about something really different. So the initial problems were first of all the fastest and priority standard does not regulate at all how applications handle the data inside the home directory. Isn't that? Then the other problem that is more closer to me as a developer of a backup program is that backup applications cannot differentiate between different types of data that are stored in the user directory. There is user content, there is configuration data, there is temporary data that should not really be backend. I have a question here. What's from the point of view of a backup application, the difference between user content and user configuration? I'll try to differentiate that a bit later on. For example, if a photo and a tag for a photo are a user content then... because it's hard for me to see, why do you have to differentiate? Do you have to backup and restore it anyway? For example, the list of game, the configuration for the game, for the chat, different configuration. There was a different example. For example, for an email program there is the configuration of how you read your email, how you receive your email and the email itself. The point of restoring it separately is that you could have an email program that stopped working with the latest configuration information, but you still need the emails that you have received before. So you would restore the emails but not the configuration of the program. And you can have different backup policies for each other. The emails change very much and the configuration tends to be stable. That's a very hard point, a hard task that I see your intent. Another application of this, if we separate the configuration from everything else, is a uniform way to reset the configuration of the application, so that we know that here in this folder is everything that is configuration for this application, and if we erase that folder, we only erase the configuration, reset it to default, and our user data should be lost that way. And the discovery of a lot of files, the user directory and all of them are hidden, a lot of users even don't know that they are there. It's a hidden complexity for a user today. When I proposed this idea on my blog, people came to me and said, well, there is a free desktop work specification about that. The XDG base directory specification is currently at version 0.6 and hasn't changed since 2004. It specifies splitting the data, splitting the user home directory data into data, configuration and cache information. It has very detailed and complex information about how there could be multiple directories for user data, multiple directories for user configuration, and what priorities they all have. And also it had environment variables that allowed administrators to have the configuration information or user data outside the idea pool. And there was nothing about some directories, so there's also only a global definition of, well, the configuration information of all applications here in this directory, and nothing about how applications should share between themselves in there. And there are a couple of limitations of this specification software as well. When I talk to people that are developing this, they'll seem to be eager that this specification moved forward somehow to create maybe better versions of it that are more implementable and engage in wider implementation of them, because currently developers look at it as a very complex thing to implement. There's only a few programs that have done that. So what I think about moving on from that specification is, I wanted to see David's leading role in the community in this sense by creating and implementing the new version of this specification and moving it on into the wider community. By doing three steps, defining what we want here in this specification, second step, implement that via a hack by basically redirecting access from old config files or old data locations to new ones via the LD3 library or something similar, and then push these changes into individual packages further upstream. So what I thought about so far in this version one, there need to be three data classes. The configuration data, user data and temporary data. Use patterns, rules of operation of every class need to be defined. Folders for each class need to be defined. There should be at least a recommendation about how applications should use the subdirectories, how related applications should share these subdirectories, and also we need to clearly define migration path from either the regular situation or from the 0.6 version of the specification. There were two proposals about the main look of the folders. There could be type slash application folders or application slash type folders. The difference being that in the first option there would be one folder which contains configuration for all applications. And the same one folder containing all cache for all applications or user data for all applications. And the second option would be that configuration, cache and user data are in one folder for each individual application. And then they are put into some bigger folder there. When the first option is similar to what we have here now in the specification, 0.6 version of the spec. And the second option is more similar to how the Markov 6 is treated where every application basically is a folder with strictly defined contents. There is a set location for the binaries, a set location for the configuration, a set location for user data, for application data and similar. I myself, after a long discussion, preferred the second option actually because it allows, I haven't seen any drawbacks of the second option so far. But I will be showing some interesting side benefits of choosing this way of storing configuration and get to that just a bit later. So what I see is a configuration data, just setting some parameters on the software. The main thing is that the software should continue to work but just reset to default settings if the configuration data is removed. So nothing that the user creates should be erased or lost if you just raise the configuration data. There are border lines here in the questions. For example, is the pop3 access information to remote email? Is that a configuration thing? Because if you remove it and you cannot access the user data at a remote location until you configure it again. Action of the application slightly changes here. That should be defined in the specs by example. So programmers can refer to that. User data? Data and files that users have created or made significant contributions to creating and have not explicitly saved to another location. That for example would be the emails or the typing information from photos. Isn't safe to the photos themselves for example. And it should never be necessary to erase the user data to make the software work again. So software should not be breakable by the user data. If software is breakable there is something that is probably configuration or should be rephrased. And I think in this specification there is a place for suggestions to application writers as to how to handle different types of data. For example, that application should be extremely careful when writing user data to avoid losing it in all situations including situations like a full partition. And temporary data is less class that can be regenerated or is of temporary use like web cache or managed thumbnails. There is quite a lot of this information in the home directory. For example, the thumbnail directory can be several hundred megabytes large on a typical user home directory about several months of use. And application should be prepared that this data can be erased at any point. About the structure of folder names so if we go with the second option the structure like this can be formed where all the information of the application the only place where the application can write except a special user request would be home, some kind of folder name like library like it is in Microsoft and folder for the application name. It would store the configuration data home library application and config temporary data, home library application, TMP, cache not quite sure which to use here and they could store the user data in the rest of this folder. It is quite fine with the backup software actually because at least my backup software can have frugal expressions, makes no difference whether it is cache dot application name or application name slash cache. So it should be able to handle such a situation no additional problem. A population would be shared by many applications? It is an issue there that needs to be addressed that there are applications that are sharing information between themselves where that is information that needs to be stored. So it should probably be defined as some kind of master application that would store this configuration information. Or maybe generic names for application name for example email or mails or something like this, name slash config and there is the... Like a virtual application that is holding the problem is there will be complex and it will be hard to manage and many of the things are in the code many applications so it will be very difficult to assess. It could be the next step of consolidating similar configuration information from multiple applications. It is partially what Gconf is supposed to do. Right, I was asking how does this relate to Gconf? Gconf is a very problematic case here. Why? Because it stores the configuration of an application in a completely unrelated place to that application. So you can't really define a way to reset for example all configuration information of evolution maybe. Why not? Because it is in multiple locations even inside the Gconf. Can we manage that? Sorry, all configuration of evolution is under one specific tree and you can preset the configuration of evolution with one command line just reset everything under below this subtree. I'm not sure about the evolution, I haven't looked at it yet. It could be in one subtree. If it spread among several subtree we could consider that as a bug or something or we would need some really good explanation but even then evolution itself is registering a schema and you should be able to say look at all keys which are going to be registered by the scheme of evolution and rest at all keys introduced by the schema evolution has introduced. So in fact it's quite easy to do this with Gconf. The question of how Gconf would fit into here and even how whether configuration information from the Gconf should somehow be stored into the same directories it would need to be separate it's an interesting question to have here and I'm not quite sure of the answer because I would really like everything to be in a folder and not spread across multiple locations even if there is a map of these locations somewhere. Maybe you are thinking in backup and he's thinking in integration I wonder if you are a different person. Well Gconf is some sort of configuration database you don't have to care where the configuration actually is you have a new configuration space this Gconf tree and you think where in the Gconf tree is my configuration store and you don't care where it is on the file system in fact you can even configure it to be an elder. Yes, but the problem is that I do care where it is in the files when I try to backup it or restore it. Well, the canonical answer of the Gconf developer which I'm not would probably be what you would need to write a backup interface to Gconf database. Which would be nice. Yes, it would be pretty well answered because in that case everything is standardized except Gconf which would be a special term. You can't say the other way Gconf introduced a standard and other folks are doing something else. No, I'm not that fond of Gconf anyway I understand why I... Yes, right. I understand that point in some ways. For the beginning you could of course treat the XML file Gconf is... by default Gconf uses an XML backend for configuration data and you could treat that XML file as configuration data for a start. A solution might be to treat Gconf as one single application and integrate this single application into this scheme. Well, that could be a very, very rude hack to get it working with. I'm not quite sure if it's really a hack. The point for example is the same evolution. If we later... One of the targets of having this specification made is to have an application resetting settings simply by erasing a configuration directory. So... to have an account of Gconf files to programs like an evolution, we would have to erase evolutions to the configuration directory and the evolutions of the directory in Gconf directory. Yeah, that just shaped it for the specific case of the evolution of three of database called apps evolution and it's quite easy to say please reset everything below the subtree. I'm not quite sure if every configuration, every information of evolution is there. It could be that some parts of the configuration are shared with other programs for example outside the street. I have no idea, I have not wanted to do this specific case. Okay, let me just comment. First I don't think that it is and if it is, I perhaps consider that as a problem. Well, it could be a feature because like with example several programs share several programs share false information all the proxy server information yes I prefer the iteration of that. Well, is that a configuration of evolution? No, it influences how evolution works. Well, that's a very var definition. I think evolution is a very particular example of a very big program with a lot of things. Well, we have to consider such a big problem of the programs. Oh, yeah, I know. But maybe it's not a happy order that we look for. Maybe evolution will be the application which needs more has to be integrated to the standard. Well, anyway, what's the problem we're discussing actually here? Well, the two uses of the spec the backup in the store of everything except cash basically maybe different times of backup for configuration and for user data and an application to reset configuration Well, I think there isn't actually a problem here because everything which is stored in Gconf is in fact configuration. Yeah, that's good. There is no temporary data in Gconf. That doesn't make too much sense to put temporary data. No, does it make sense to put user data in there? Right. So no matter of that spec we could just perhaps 3Gconf indeed as an application of its own and make store its backend data for configuration as Gconf configuration and be done with it. If you want to reset a specific application well, then you would need some specific interface which knows which schema authentication is introduced in Gconf and the version data of this application which then it will reset in Gconf 3. Well, a slightly more cleaner approach like here is to have the Gconf store this particular tree of configuration just there in this directory. Well, of course you could perhaps write its based your conforming Gconf backend that should be also possible. So in the sense that you don't store it in one flat XML file but spread across your library, saturate it it should be possible as well but I don't see much point in it. It's just the problem of applications using slightly different short names for themselves but there's Thunderbird, Mozilla Thunderbird, some confusion by the application on there but that's unrelated to the main problem. The interesting part about having application type in directories is that there are other folders there that are these folders for plugins maybe you could have Firefox for example store their plugins inside that application name and maybe share a plugin name with the executable files for some plugins that are executed somehow by the software itself in the bin sub directory and configuration files for the plugins integrated into the configuration for the main software as well as having a possibility of adding something to the menu having a desktop file in the application name directory the idea behind all of this is to possibly later allow having a install applications, user installed applications that are simply unpacking this application directory into the correct place in a similar way that it is done on Macintosh the idea is that you receive from the Internet an archive you unpack it to move it or unpack it to your library and you have an installed application inside that archive there is a bin where you have the executable files there is something that adds this application to your menu the program files, config files every part of that application and once you as a user put it in your library there is a part of the menu that regenerates this application and gets added to your menu I think it would not be that hard to add this functionality once these directories are established so that third-party software can be installed by end users in an extremely simple manner then and you are aware that such a directory the last point on that slide already exists is called don't load to share applications are you? don't load to share applications if you put some of the desktop files in there for example the normal KDE desktop we respect that for example overwrite system-wide or register user-specific applications well, yeah great I was aware that there is such a thing but I wasn't aware of this for example I can show you I've installed Adobe Reader for example which is a normal desktop file which tells how you start in Adobe Reader so this already exists and is already used great well, as it is part of the home directory there should be in this specification where these files should be what is the desktop specification of the desktop right but it also needs to be here if this specification is to describe everything that applications need to do it in the home directory obviously the specification should be completely changed that's true with the top local applications it is in a different location than this application directory so the desktop file would need to be copied over to there if this can be either changed or added as an additional way the desktop files can be added so if we take this Adobe software and you simply unpack its archive into your library directory then it gets installed without any need to execute any scripts or copy any files around I think would simply simplify that significantly but oh yeah that's a way to do the desktop file specification the migration path the suggestion is that we do this in two simple steps first we do an ugly hack it uses either LD preload or some other way to hack into the system and intercept every file request and have a map from the file locations to new file locations so that every file request to an old location would actually go to a new correct location in the home directory possibly with moving the old file over while this process is being done and the additional benefit of this actually is that if we make a preloading library of rewriting file locations preferably using that allows the use of regular expressions in this it could be a very useful administrative tool for moving files that don't exist yet in this way and would allow us to do this application and in the second step we just add support for this specification is a policy requirement and in a couple of releases introduce that to the software and forward that upstream Your last slide Yeah Okay Then Thank you for your presentation I have a few remarks about that Let's start with the last one I'm not too convinced about this migration path I think the very first step of this plan should be to prove that it actually works This means to take one application one well-known application or larger applications to actually use this and implement this specification and to show the benefits of that So in the first steps you have introduce a new allocation this library directory and they show that there are benefits of it in the other application and then convince to more and more upstream to actually adopt this specification I am the maintainer of the midiplate scene and I know that scene is actually adopting this base specification for the next release 1.2 but version called 0.6 they don't know all 1.2 0 because that's I think the ratio of yours yes So there are actually upstreams which are keen on using that and before we are doing ugly heads like this I'd rather try to convince main adopters of larger application like KDE, GNOME, XFC well no the situation adopted before will create legacy applications and the next thing is this is not how Debian policy works you don't change policy in order to change things in Debian not to change things in Debian first and then adjust policy according to what's actually done this is what I am observing regarding the later changes in policy because this way this pushing changes in Debian policy first is going that lots of Debian maintainers will stream and not implement the policy and then you get terribly flameless as observed in the last years of Debian development Well, you need to discuss the policy first before implementing it of course and that's the point, no I say first implement it and then document policy because I think Debian policy should document what is common practice well the common practice is scattering things all over the place but it is not defined in Debian policy you won't find the part in Debian policy where it's outdated to scatter all your configuration in your home directory Exactly, that's what I am thinking of describing a better way of doing it Yes, but then making it required I fully agree that it should be documented but I don't agree that Debian policy is the perfect place in the first place to do it I mean, it's very fine to do it as a free desktop space or as another specification and get applications using it but I think it's a wrong way to force the maintainers to do it out in the blue because you won't get many upstreams which won't implement it either because they object or because they are not interested in interacting Well, if the maintainers get them patches that would significantly make it significantly easier for upstreams to implement it They might not want to create patches for it The major thing about free software is that people tend to be different and they tend to implement things different and they are and it's a major but it's a good point about free software because you have the choice between different systems and forcing to introduce such a major system that might just not work and we are getting to a basic problem about free software Everything might just not work and maintainers might just want to change files in other packages along the way or might just want to put executable files in the root directory or do something else like that That's why the policy exists to set the rules for the packages That's why Yes, but if we really enforce it a dead end policy we would have to enforce it in every package and we will I guess in the least like 50% of the package a stock stream would not adopt it so we will I work from upstream in a lot of cases, that's probably not what we want There is a lot of diversion from upstream in the file names in the outside the home directory Yeah We already have problems there please note because that's as a file system priority standard it's outside home directory it's inside home directory that should be not no difference in that I generally agree that's a good idea to get this implemented I just disagree about the migration path and the way we implement it Well we have to think if it's really going to work in first place The thing about this ugly hack in the beginning is that all the work of translating from the old file names to new file names is concentrated in one package Yes, which is the list of translations, yes and just by installing that package you will have a compatible system that implements this specification and then you can see I think you would never get rid of that ugly hack if you don't want to have an enormous amount of work to do I think that the ugly hack can be done in parallel with the version of the abstract but the abstract really believes in this that it should be applied by itself so the ugly hack can be made because that's not a conflict with the abstract and the abstract should be convinced that they use the COOIC standard COOIC standard is 5, the COOIC standard for the 1.0 3% here which is the top and the middle bits 0.6 is much more complicated actually it has all the provisions about forcing environmental variables and having multiple configuration directories for one user and priorities of files in those configuration directories I'm not sure it sounds like a very interesting idea but I'm not really seeing the benefits of it that is why I didn't include this in my proposal there's a lot of quite complex stuff in the 0.6 version of the specification that actually does require significant changes to the applications that's why that's why I think it is not made the right way accepted yes, only half of the program is included in that Do the upstream of your package know that it's complex component? For the execution well, they had me work with a very small library and I haven't looked at the next version because if you change the standards many times it will say he works a lot he works a lot for implementing he will want to change again the thing is that basically the only difference between this my proposal and the current regular situation in the applications is the paths where the files are stored where in the 0.6 version of the specs there is quite a lot of additional code that needs to be added to applications and I agree with him the deviant policy requirement is the step with a long number it's not step number two probably forward the step one and the policy requirement will be that that's not the problem now I think well, the policy requirement I'm thinking when through this ugly hacks or other methods we can get for every package this translation information that when you install this ugly hack package you have every configuration file migrated every user that file migrated to your location when that is complete then I think it can be moved to the packages I think that the ugly hack could be a good proof of concept of how the standard works but probably is a really bad solution because if you go to maintain it's probably don't work in every bad hash so we have to have different ugly hacks for like C and like if you put it in GLC then it would intercept older and faster related calls just like fake would for example maybe some things just make first and change directly it's an open one file it's a change that we maybe it's not open it's an open slash file or so normally they make and then change like me and open some files it would be useful for proof of concept so evolution works here it works like this without the standard and what's like this with the standard and this is the benefit but probably will not be will not really use it in reality I think so you might not find here about this LDP reload hack I'm not sure all architectures support LDP reloading at all I remember that MIPS doesn't support it it's another problem and the other thing is it doesn't work aesthetically fine with this one of the major targets for the rewrite the the proprietary applications would actually be intercepted another point which I don't see addressing this way at all when you talked about credentials a confidential information like passwords at least I think it would be a very good chance to explicitly mention that and this is a sensitive information please make sure that no other application than the application who's supposed to be able to read that the enforcement of this can be for example done by Aparmo or SCN but it would help them a lot if the specification would designate some special kind of this confidential information it would be useful for that too because can you have a policy to save the confidential information that's a really good idea manage the confidential information information to have at least the specifications that's a really good idea that's good so you don't see a special case because you said before you're not sure if that's configuration data at all because if you're really good at it then the application is usable and it won't it's correct and if a special case well then a special case that's a good surprise I would like to ask a question I think it's a really good idea I think it's necessary to have a policy to make these to collaborate with the standard then the for example well making this making a new version of the standard this may be a problem because people at the free desktop work out open it towards this the major problem is really implementing it in major software like non-kiddy, mozilla stuff if the standard is easy to implement and it's stable and discuss it by the community I think the option will be implemented with the time that doesn't really happen with the existing standard because it's complex as you said I will I think I have an example where the hack is going to break horribly for example take open SSH with open SSH why at the moment you have the configuration and confidentiality key information in the box SSH and a different configuration of the open SSH server is looking in dot SSH slash author's keys and if you are now moving rather taking it to slash library as the open SSH author's keys then you would have to adapt the configuration of the open SSH server the code that doesn't run as the user you see it's going to break the software open SSH when we are doing this library it's a criminal hack so really we have to do this in the source and I'm very interested to see how you convince open SSH upstream to adopt this specification I'm serious that's true we could back here try to convince open SSH you see the very question I'm thinking as one way of convincing people hacking the convention the convention of people is actually adding this somehow to the fastest hierarchy standard I think I think you shouldn't go the way up by making it mandatory by policy requirements I think you should go from the way from down saying look these are my problems I want to solve I want to make backup applications I want to ensure that security frameworks can more easily define access for example I don't see any reason why any application besides my SSH should touch my SSH key or my GPG key as well I don't see any reason why any other application than my GPG should be able to meet my GP and this specification if you can show that this specification is considerably helping security frameworks to enforce sensible security policies I think that's way more likely that more upstreams are going to help the specifications so you have to show that there are actual benefits from that yeah that's a very nice benefit that we are talking about both real benefits and talking about RAC and that's why I'm saying I'm not sure about the migration part first show that there are actually benefits implemented for applications that are known and open SSH that's true maybe give it to know because most of my upstreams use files in home records and probably they don't even know the standard so you need to give it to know who you are and step of the path I'm not sure that actually many people know about the standard it has been built quite quietly and put up on the free-desk border site and forgotten about but a huge call of comments will be that many developers can fill their view and they will be feel their part of that so they will be agree with the standard too that have been a policy requirement I'm seeing actually as the final push towards making a complete support yes but you can't do it before it's already widely adopted yeah but you probably don't want because policy will trick you with a large take if you try if you implement in the policy and it's not widely adopted there will be a huge amount of free-disk critical backs with free-disk validation so it will never I think we already read that migration is not so we will take a lot of effort it's like there was a doc to use a standard of migration and probably it was not really adopted at the time of and probably it was to use I don't think this is going to end in this decade no no you have to show their benefits if you really want to write a policy we would have to put it in policy probably maybe not as a requirement but as a really really short well first at least we should yeah if you go to provide a ton of mass backfiting and stuff like that and well it's going to take a lot of time we maybe should think about how we for a few seconds I think you should be sending if you want to do it like in one release the release is going to take like a couple of months and if you want to do it like in a couple of releases that's going to need a little bit harder it's going to take several years anyway I think it's going to go in like it would be a shoot for one release please and then it could be converted to a requirement for the next release and thank you thank you


Hey everyone, Dylan Schumacher, Citadel Defense, and we're back with another episode of what did the government screw up this time? So every day I wake up and I think, can they still find a way to make this worse and then they manage to do that. So while there are a litany of things that are going horribly wrong in the world right now, the one I want to talk about right now is that the CDC has decided that yet again they need to study gun violence. This is of course hilarious because they've already done this. A mere 8-ish, 7-ish years ago, back in 2013, the CDC released their study on gun violence. And that study is such a big deal because that's when we found out that about 750 to 2 million times a year Americans use guns to defend themselves. That's how many defensive gun uses happen per year. Again, remember a defensive gun use doesn't mean anybody gets shot. It just means you tried to rob me, I pulled out my gun and you said, okay, I'm going to go find something else to do. That's a defensive gun use. And that happens on average somewhere between 750,000 to 2 million times a year. So people use guns to defend themselves quite literally thousands of times a day in this country. Now, to make sure they get the correct results this time, the CDC has declared gun violence a health epidemic. Because why not? I mean, rent was a health epidemic. Now we can have gun violence be a health epidemic. There's really nothing that can't be a health epidemic at this point. Now, like a very good scientific organization that you would trust with your health, the CDC has decided to make their conclusions and then get data to back up those conclusions. Because after all, that's how science works. So of course, I will be super interested to see the results come back from this study because they are going to quite literally have to make up data in order to support their case, which is what they will do. Or at the very least, of course, omit very important relevant data to the conversation. For those of you who don't know, of course, we use data to drive conclusions. That's how the scientific method is designed to work. You make some hypotheses, you gather some data, and then you draw some conclusions from those data, which don't always align from the same set of data. You might have learned this in third, fourth grade if you grew up around the time that I did. These days, however, that is not the case. These days, what you need to do, of course, is make a conclusion and then go out and find data to back your point up.  Here's a great example where an organization has decided they have an agenda to push. An agenda that, of course, the Democrats have wanted to push for decades, and now they're just going to go ahead and try to find a way to finagle it through. I am a little bit surprised because the rent moratorium thing did get shut down, so I'm really curious to see the CBC declare a moratorium on gun sales, or ammo sales, or online gun sales, or online ammo sales, or whatever other thing that they come up with. I'm super curious to see them try to declare some kind of health-related emergency around guns and why you don't have a right to own one anymore. This, of course, comes at a time when government control and tyranny and communism are off the charts and growing. So stay tuned as we continue to live through this wonderful historical event. To brave deeds and endure.


What's up everyone? It's your girl Kenzie here from Layton Sports Cards and I'm ripping a personal for Neil B We've got a 2022 Panini select UFC Hobby box all righty Neil best of luck. Thanks for hopping in. Let's see what we can get you Rift some each two of these earlier some nice cards See we can get out of the hobby See some big autos. I want to see a tie-dye. I'm feeling tie-dye out of here Let's see Then ship shanko Got bj pen and silver of sonin sonin Anyone do anything fun this weekend? Adesanya Chamea Whitaker try color of Brandon Moreno Flyweights on the premiere level Friends had a barbecue pool party yesterday. We went to it was a lot of fun. Very relaxing. I'm glad the weather held up too We've got out of 199 Silver patch auto little vulk.  I had a one-of-one black disco of him I sold it too early. There you go. Very nice hit Neil Vulcanoskvi Vulcanoski That's sick. What's up, Karen? We will mag this one for you again. That is 122 out of 199 There's really no one that can that can fight him I feel like I think they were talking about him bulking up a little bit and moving up to the next um Class I couldn't think of the word petromonios on the red to 99 Because the way that he beat up on max hallway Dude literally split his eyebrow like in half like he had like three eyebrows is what it looked like He's a hell of a fighter Usman on the octagon side and we've got whites of cirro gone. There you go Nice one there. The white is out of 75 44 out of 75 Is it okay, so the vulk is cut a tad long Neil so it won't fit in a mag, but we'll put it in a um Well my train of thought today a top loader with an lst sticker over it for you. I make sure it's all protected up So we've got out of 99 a red octagon action signatures edson barboza Nice barboza on the red octagon action Signatures and grant Dawson on the rookie tri-column We've got gold. We don't have we don't have tie-dye, but we got some gold here Neil for you phenomenon of grant Dawson Come on. Let's see a big rookie. Let's see a big rookie. Here we go Neil. Good luck of joelle alvarez on the octagon side There you go six out of ten Wow beautiful card there no uh Neil Let's go joelle joelle alvarez That's sick Dust right here.  You're right. Oh, we've got silver Pedro Muñoz Wow, we still have half a box to go too Yes, he's been on on a fire this morning too his h2 boxes earlier were really nice Moreno We've got silver patch of marlin vera vera on the patch albazi silver rookie premiere level All right, let's see some more color. Let's see some more color. Come on here. I think we've got all of our hits Nunez global icons of olivera silver rookie of alonzo menfield Cormier Sean brady phenomenons tracy cortez and scope of uzman Again, I believe he's fighting at the end of the month. I can't remember who's fighting I remember seeing I think he's fighting someone that he's already fought because I'm pretty sure it was someone versus uzman too that I saw A couple days ago on the tv. McGregor on the octagon side Nice and silver a macy chassis All right, last back here for you neil. Good luck. Very nice box Dan hooker uisis nice and umar ner magamadoff Nice one there. I love the the wig And the last one we've got a tricolor of mackenzie dern All right, neil that will do it for your box. Congrats on the gold rookie the nice bulk patch auto Heck of a box. We'll be getting these right out to you


Hello and welcome to the session. In this session we are going to discuss the following question and the question says that Raven bought 6 pounds of tomatoes for $13.86. Write an equation relating the cost to the number of pounds of tomatoes. How much money would Raven pay for 9 pounds and 20 pounds at the same rate? We know that unit rate can be used to write an equation of proportionality between two quantities and that the equation is given by y is equal to k into x where x and y are two quantities and k is the unit rate or the proportional ratio y by x with this key idea let us proceed to the solution. Now in this question we are given that Raven bought 6 pounds of tomatoes for $13.86 that is 6 pounds of tomatoes cost $13.86. So unit rate between cost and number of pounds is given by $13.86 upon 6 pounds and is equal to $2.31 per pound. As we know that $13.86 is divided by 6 we get 2.31 so we get the unit rate as $2.31 per pound. So we can say the cost of 1 pound is $2.31. Now let cost be denoted by c number of pounds by p and the value of k is equal to 2.31. And from the key idea we know that unit rate can be used to write an equation of proportionality between two quantities and the relation equation is given by y is equal to k into x where x and y are the two quantities and k is the unit rate. So here the required equation that is the equation relating the cost to the number of pounds of tomatoes will be given by c that is the cost will be equal to k times p where k is 2.31 into p that is the number of pounds. Now we need to find that how much money would Raven pay for 9 pounds and 20 pounds at the same rate. First we shall find the cost that Raven pays for 9 pounds at the same rate. And we have the following relation equation which is given by c is equal to 2.31 into p and here we replace p by 9 in this equation and we get c is equal to 2.31 into p that is 9 which is equal to 20.79. So we get the cost as 20.79 dollars. So Raven pays 20.79 dollars for 9 pounds of tomatoes. Similarly we shall now find the cost that Raven pays for 20 pounds at the same rate. We know that the relation equation is given by c is equal to 2.31 into p and here we replace p by 20. And we get c is equal to 2.31 into 20 which is equal to 46.2. So here the cost is given by 46.2 dollars. So here we can see Raven pays 20.79 dollars for 9 pounds of tomatoes, 36.2 dollars for 20 pounds of tomatoes. This completes our session. Hope you enjoyed this session.


Hey guys, what is up? Welcome to my channel. For today's video, I'm going to do a first impressions on some new items I picked up from the new Chanel Lae Pearl Lime. You guys know I've been trying to get a little bit more into Chanel, so with their newest collection, I wanted to pick up a few items that caught my eye. So if you wanna see the demo and my thoughts as I first apply them, then just keep watching. Okay, if you've been following me, I've done a little bit of chatter about absolutely being in love with the blush item that I recently picked up from Chanel's. Spring collection and Chanel released a new collection. It's called the Lae Pearl collection. I'm officially, I'm on board. I loved the cheek products so much and I'm still getting acquainted with Chanel and their formula, so that really was what this was about. I tried to get like one of each formula. So yeah, I ordered from the Chanel website and I'm so excited. Haven't even swatched anything yet, so this is going to be a true first impressions and I'm hooked now, you guys. I wanna place some more Chanel orders. I wanna try more formulas. I love the feeling of getting the box. I can't afford a purse, so I'll buy the makeup. Let's get into it. Like I said, I haven't picked up everything from the collection. All of the information that I got and what helped me make my decision was following Erin Nicole's video. She is an expert on Chanel. I definitely think if you're looking for some great information on Chanel beauty, you should take a look at her channel. I believe she used to manage to counter at Nordstrom and she knows her stuff, okay? She's the person to go to when you want to know about how the new collection compares to old collections, comparisons. She really knows the ins and outs of Chanel beauty, so I'm gonna put her video down below because it helped me make my decisions. So ultimately, I did pass on the quad. It looks like this. It didn't look like anything that I was really interested in. I just didn't think it would be worth my money. It was $65 and it's a very sheer formula, which according to Erin, I'm gonna probably reference her through this video. The whole pearl collection is supposed to be pretty much a very sheer ethereal kind of look. And for me, I just couldn't justify $65 for that. I'm waiting for the perfect quad to pick up to really get into the Chanel eyeshadow formula, but I did decide to pass on that. So the first item that we're gonna put to the test, I picked up a bomb essential multi-glow stick. Now, I actually have tried this formula before. I have a bomb essential in the shade Golden Light. I bought this when I didn't know the formula. I thought it would be like a regular cream stick. It's like a shiny balm. And this shade would be beautiful as a highlighter on a deeper complexion. But for my skin tone, it's kind of awkward. I did actually use it today to add a little bit of depth. You can see that shadow there. But because of the balm consistency, the finish on the skin is a little bit too shiny for what I would prefer for this shade. I wanted to give this formula another try now that I kind of understand the formula more. I decided to pick up one of the two shades that came out. So I chose the shade Print & Yeh, which is this beautiful pinky rose shade. They also had another color in the shade Pearl Lesson. I kind of wish I picked that one up. We'll see how much I like this.  It looks like a gorgeous, glowy, just highlighting stick that would actually work for my skin tone, but I'm into pink cream blushes. So I had to pick this up. So this is $45, 18 months shelf life, and made in Italy. Let's try it on. So let me show you. You can see from swatching it, it's very, very, very sheer. It's more so about the shine. Hmm, I was hoping you would have a little bit more pigment, but let's play with it anyways. I'm gonna put some on the back of my hand. So I actually am using ABK Beauty 106 brush to apply it. I mean, this is beautiful all over the cheek. So it's not gonna give you much color like I was hoping it would, but I think it's perfect as an all over cheek color just because it gives you a glow, but it still adds a very, very subtle flush. I don't know if the camera will be able to pick up the very subtle flush of color, but it really just makes you look like you have a very fresh, glowy cheek. I probably would go in with a pink blush stick that I have from Chanel right on the apples, but I don't dislike that. But I do wish I would have gotten Pearl Lesson. So these are very, very sheer. The lesson learned on that. It's pretty, and these do, based on my experience with the older one, they stay a little bit more sticky, like they don't dry down, but they do dry down a little bit. They don't stay as sticky as when you first apply, but honestly, I don't think that was totally a necessary product for me to buy, but I feel like when I would like this is in the summer, when I have a little bit of a natural flush and tan anyways, this would be great just to throw all over the cheek for a glow. I think I should have gotten Pearl Lesson. See, this is, I'm so new to Chanel. I'm gonna make these mistakes, and that's okay. Let's go to the main reason why I purchased this collection. I am in love with Chanel Highlighters. I have another one in my collection. I am starting to collect them now because they're just so beautiful. So this is the Pearl de Lumiere. It comes, of course, in the beautiful velvet sleeve. Classic Chanel packaging made in Italy, 18 month shelf life. You open it up. You have the brush and untouched, baby. No explanation is needed as to why I picked this up. Now a Chanel Highlight or a blush is a splurge. This was $75. I'm in love with it, and I haven't even used it. So I'm gonna swatch it now. There's no kickback.  I wouldn't say it's quite like a gelé formula, but it's a pretty hard pressed powder. And that's how the Highlight looks in a swatch. I'm kind of gonna better be right there. So it looks like it could potentially be maybe a tad too dark, but I think it'll be fine. Let's find out. I'm gonna use my Kaleidos H1 brush. Yeah, see, it's not completely baked. I'm gonna put that right on the high points of my cheek. Now I do have that balm down, so it is gonna stick to the balm, and it might end up being a little bit extra more glowy. Honestly, this is much more natural than I thought it was gonna be. And this is not a highlighter that you can over apply. It is actually quite natural. It's really, really pretty. So now we're gonna move on to the eye products that I picked up. I picked up the eye coal. It's like an eyeshadow liner coal. And there's two colors. There's a burgundy color that came out. I picked up the beige color at number 40, so I've never tried this formula from Chanel before. So I wanted to give it a try. You can see it's like an eye coal. Very pretty, everyday kind of bronzy color. I wanted to line my lower lash line with this. It looks really pretty. See how it defines the eye, but it's not harsh, like a black? This is why I love shimmery browns like this. And I'm just gonna put it all over. Now you can use this as an eyeliner too if you want. You don't have to go everywhere like I did. But I want to test how this blends out. It blends out very nice. I don't know if I mentioned this, but it is $34. And it just gives you a nice natural, kind of quick, easy shadow to the eye. Honestly, that's very nice. I don't use products like this too often. So I'm happy that I have this. I'm gonna put it in my waterline as well. That is so nice for a one and done shadow. It's very easy to work with and just use your fingers. You don't need to use a brush. I think honestly, I know this is crazy, but this is my favorite thing that I've discovered from this collection. Hear me out. I know I love Chanel highlighters, okay? So this one is the most shocking because I did not expect to like it as much as I did. Okay, so I'm gonna do some mascara and then we'll be back to the final lip product that I picked up. Just put on a little bit of mascara. Let's move on to the lip products. Now there were a few different formulas that came out and a few shades within each formula. Given the home ask situation, I just didn't want to buy too many lip colors, but I did pick up one. I wanted to play with a good Chanel lipstick. I have a Chanel lipsticks or a couple in my collection, but they're older. So I wanted to get a new one. So I ended up picking up the ultra hydrating lip color. I got it in the shade Tendress. And it looks like in this, there's two hydrating lip colors. There's one vibrant shine lip color, or two, excuse me, two vibrant shines and one luminous intense lip color if you're familiar with their formulas. This one looks to be like the lighter, more natural of the two lipsticks of this formulation. This is the typical Chanel packaging. And it's just gorgeous. I feel like it's a wearable pink. It's a little bit sheer. I feel like this is gonna be beautiful. This formula does have a little bit of almost like a metallic finish to it because it's that hydrating formula. I really like this color. I think this is perfect for the upcoming spring. It doesn't really go with my eyes. I feel like because of my eye color right now, I really want like a bold brown neutral lip. So the bright lip is a little bit odd to me, but the formula feels really, really nice. I know Chanel lipsticks are very popular, so I'm looking forward to trying more from other formulas, but this one feels very hydrating, so I like it. And I like that it's not too pigmented as well. All right, I'm gonna zoom out and kind of give you my final thoughts. So ladies and gentlemen, here is the final look. I mean, the overall vibe from what I was collecting from this collection is that it's not supposed to be really pigmented and just Chanel in general. It's not supposed to be super pigmented. It's just quality makeup, you know. Really great, wearable, easy to use, and that's how I feel about this collection. So starting off with the bomb essential, if I'm being completely honest, I do wish I just picked up that pearlescent color. I'm learning that I'm just not the biggest fan of this product because I'm trying to use it in a way that it is not intended for. I like a cream blush, but an actual cream, not necessarily a bomb, and I need to try to stop making the pigmentation happen from these because I'm just not getting it. I didn't love my golden light. I don't love this one. I think it's nice. I think I will continue to use it.  It does add a hint of color. But for the price that I paid personally, it's just not what I'm looking for. The highlighter, of course I'm in love with. I think it is so beautiful. I love Chanel highlighters in general. This one's a little bit more natural and as far as if it worked on my skin tone, it absolutely does. I don't see a cast from it and it's really beautiful. It's mess free. I think it's a really great everyday highlighter. Just know it's not gonna give you super blinginess but it's all about the experience. This is beautiful. I'm very happy with it. I don't think you need it. It's $70 for a highlighter. And let's be honest. If you're ordering from Chanel, you're ordering because it's Chanel. You're ordering for the experience, not just the products. So this for me, I got the full Chanel experience with. I am surprisingly into this eyeshadow liner coal formula. I'm interested in trying more like this. I normally don't like products like these which is why I'm so surprised. I love this color. I think it's a great one and done shadow. I thought it was so easy to apply. It is a little bit more sheer. It's not super pigmented. But that's what is part of making it so easy to use and the particular color. Just great for everyday. It defines the eye. I loved it in the waterline. I loved it in the lower lash line. So surprisingly, I think this is my favorite thing that I picked up from this collection. And you can also put a powder shadow on top of it as well and use this as a base. But so far alone, I'm not noticing any creasing or any hints of creasing. I'm very, very impressed by this. So this is like my new favorite discovery. I love it. And then lastly, the lipstick. I really, really like it. This formula is hydrating. It's pretty wearable.  You don't have to worry about being completely in the lines. And I do recommend this color for spring. So I'm very happy with this as well. That is all I have for today's video. I hope you guys enjoyed it. If you aren't subscribed to my channel already, I would love it if you would consider taking the time to do so. And I will see you all in the next one. Bye guys, have a good one.