Any questions? All right, so this has happened. I saw this image. These are Fedora container image sizes from Fedora 22 up until Fedora 30. And it went from like 200 megabytes to over 300 megabytes. And there's a dig in here that was some sort of minimization effort, and it just grew again. And OK, so that just appeared. And the question was, hey, can you make Fedora smaller, please? And I was like, sure. So I just grabbed Fedora. That's me and tried to make it smaller. And then I realized, no, that's not the way. I just need to have more sophisticated approach. So I proposed something that's called Fedora Objective. I don't know how people are familiar with Fedora Objectives. But these are like highly vestigial goals for the project. Fedora has like, I don't know, four. So I proposed minimization to be one of those. And I basically say, hey, I want to minimize things. I don't really know what I'm doing. And I'll figure it out, and I'll let you know what happens. I called it the discovery phase. And it got accepted. And let's talk about the discovery phase, what it was, and what I came up with. So they mentioned images, right? Do we actually need them smaller? So if I look at base images and applications, right? No one really runs a base image just for base image. People are on applications. So we might not need to focus on the base image itself, but on the whole thing. And also, you have application with dependencies. And if some of the dependencies are in the base image, it might actually just move the line and it really increase anything. It might. It might not. There's cases in which bigger base images are actually better. If you, for example, have containers on huge scale, the base image gets shared because it's a layer. And in the result, it might be even smaller. So what I took from it, I'll focus on the whole thing, not just the base image. So why do we care about size? Isn't this space cheap? That's a good question. And I think there are three reasons why I care about size. Composier and security slide. Less things installed, smaller attack surface. That's a reason that's not storage related at all. It's a valid reason. Another one, Internet of Things. Again, that's cool. One more slide. It's not about disk space again. Like Raspberry Pis and things are maybe small, but it's really about the connection speeds. Because they run not in the data center, but they often run somewhere even in the fields, have very slow connections, and sending updates quickly. If things are smaller, it actually helps. And then containers, I mentioned containers on scale. Like if you have just too many containers and it's too big, it's actually painful to manage. So making it smaller actually makes sense, even from the storage perspective. So all right. Those are the three things I took in mind. That's why I care about size. All right. Even more existential question, like what's the point of Linux distros? It's even for the right place to do it. So how does it work? Like we have upstreams. They develop software. They develop nice features. And we have users who use it in production. And they need fixes fast. And then they have a bug. And maybe are pressuring the upstream, hey, you need to fix our CVE. But we don't have time because we actually need to develop things and stuff like that. So that's where distro comes in. And they can integrate things. They can test things. They can make it easily consumable and updated and basically make everyone's life better. So they can focus on development. They can focus on running. And like they are the gateways between those two. And you can have various distros with various target groups. You can have community distros like Fedora. You can have an enterprise distro like Red Hat. And then you can actually throw money at them and scream louder and it will do it faster. So that's why we care about distros. So Fedora's the right place again. So let's finally minimize things. How to do that? Let's have a look at Fedora. Oops. That's the repose. It's an SVG file that just somehow tries to show you all the packages and all the dependencies everywhere. And this is live for my last presentation. This file took three hours to generate. It's 1.6 million lines SVG, 130 megabytes. So even for computers, this is kind of hard to approach. And I was like, nope. I'm just minimizing this. I need to have a different approach. So let's focus on use cases instead. People don't use repose for anything. They have use cases. They install something very specific for specific reason. And that's what they care about. It can maybe name a few and focus on them. So that's a thing that we do. And what we make with them, basically they are four areas in the project that we'll be focusing on. So making that's making smaller, minimization, can we optimize things in various ways? As we saw on the graph, things tend to grow. So we need to also keep them smaller over time. So if you make change, it actually persists. Talking is about making this initiative more popular, teaching other people, guiding whatever, educating. And leading is about coordination in the project so we don't actually step on each other's toes. So that's what the minimization effort is actually doing in there. And with that, I proposed a second phase that was much more specific than I don't know. And this is what's going on right now. By the way, in the meantime, very nice thing happened. The size has got smaller with the base image. You can see F30 and F31. Actually F31 got below 200 megabytes, which is even slightly smaller than the F22. And thanks to the container team in Fedora for doing this. This happened just, I think, because the objective was in there, we talked about it, and they're just awesome people. Now we have to keep it small. We can't just let it grow again. So step one, how do we actually approach those things? So back to the objective. I said we define use cases. We have a few like HTTP server. We have MariaDB, Postgres. And we're always looking for more that are relevant that we can take care of. And then step two is prevent growth. We do that before actually minimizing it. So like if you do some work on that, it doesn't creep back. And this is the area where most work happened so far. And I have a demo for that. It's about a service that will monitor things, and I will just show you. If you just open this URL, this is where the service is. I'm quite happy about the URL. Thank you, Patrick. So if you go there, you see something called feedback pipeline. And it says that it's reporting notification regarding dependencies and sizes of defined on-prem installations. Okay, so what that means? Let's have a look. So I just click here on the results. And there's these dependency reports. And I can see two major things here. There's use cases and there's base images. And basically use cases are the applications that we care about. And base images are where we install them. Like in the context, because they can run in many different places. So let's, for example, look at the HTTPD. And it's monitoring things for the size. So I have some history graphs. And there's actually three of the same color. It's a prototype, I'm sorry. But yeah, this is from end of September last year. And it's been flat, which is sort of good news because it didn't grow up. But there's an opportunity, of course, to do some work. I don't have the old data before I showed when it went up, so like there's not actually anything shown from the minimization. But that's what we have. And then we can work on notifications and things if that grows. Where this data comes from. So if I go a little bit down, there is a definition. And that's how I define the use case. So I can say packages, HTTPD, install options. I have no dependencies, no docs. And where it's installed, it's installed in three different contexts. And that's where I can monitor. And we can look at some package list. And this is the full report of what's in there. And this is not the history, but this is actually where we are right now. And there's many things visible. So there's HTTPD, which is the package that's required. And then there's all the dependencies. And some of them are in the base image. These are the green ones. And can you see something interesting in there? So I took a Fedora container base image that has like 200 megabytes, installed HTTPD, and it is 243. And then I took empty space, where it was nothing in there, installed the same thing, and it's 379. That's like 120 megs more. Who knows why? Yeah. All right. So the other student. We'd like this content. That's sort of true. It's not with dependencies. It's basically choices in the repo. So if I, in this case, in this case, so if I sort the package by size, I can see in the middle, there's gilip see all landpacks. It's like 200 megs just got in, but it's not in there. Why it's not in there? Because if I sort it by size again, but the other way around, I can see this gilip see minimal landpack that's zero, basically cutting some support for like languages, but it prevents the one from coming in. So the message from this is that having the base images or the environments is worth it for those choices because you can make specific choices that make it then more useful for users. And the last one is basically only that gilip see minimal landpack and nothing else. And that's the smallest one because that's as low as we could get. It also does dependency graphs. And this is for inspection. If I see, hey, this is too big or why is it in there? I can just show like the relations. There's this container based image squashed into one node. I can expand it by going to the other graph and I can actually even click on packages if I want to see the relations. So I can keep on the system DNC what requires it or why is it there? And it does some basic clustering. So that was useful. For example, there was a MariaDB use case and there was like a bunch of pearl in one of those clusters and it was actually easy to trace like why is in there. So that can be used that way. All right, I showed the base images as well. It'll be very similar like those. But again, go to results, click on base images and I have four here. We saw those three empty container based and minimal landpack. I also have IoT that's just for tracking for the IoT initiative. We don't install anything on IoT because the other things in container that doesn't matter, but it's there. And the definition of, for example, the container base is the same. It has the graph here. So I can see it's mostly flat, maybe tiny bit down, but not much. Not growing though, that's great. And required packages, install options and the full package list here and the size. And I can also show you the minimal landpack which is just a thing I've made up. Only actually requiring the G-Lipsy minimal landpack and nothing else. Got some dependencies, it's 35 megabytes. There's no any package manager. So if you want to use it, you need to use multi-stage builds. I don't know if you're familiar with that. If we can talk later, there's nothing to scope here. But this can be used to build even smaller images. So that's feedback pipeline right now. It only shows things, so you need to go there to look for things. I want to make it more reactive so it actually notifies if there is a change in something and that'll be useful. For example, if a package makes a change and they don't see it in their context, but it somehow influences something on the other side so they can get a ping, hey, you caused this, please evaluate and do things about it. So that's the URL again. You can go have a look. And all right, let's back to the objective. So I said, define use cases, prevent growth, and then we can actually minimize those. And this is actually, we already did something in there, but this will be the main area right now. We'll be restarting some of the discussions and what we're basically looking for. Unnecessary RPM dependencies. There will be not many of those. Maybe not at all, but it's something to look at easy wins if there's something forgotten, whatever, we can take care of that. Multiple implementations of the same functionality that happens like multiple cryptos and things. So this is more systematic approach to just like looking for those occurrences and maybe choosing one. So that's a problem that we're looking for. And that I call it context specific requirements that sounds horrible, but for example, it's completely fine for packages to rely on system D because it's on every system except containers. You don't really need it in containers. So just like in different contexts, you have different requirements. And there's many packages requiring system D for creating users, which is great way to create users, but like it gets many things into a container. So we might wanna think about that. What we actually did was separating or discussing separating the system D, CIS users thing out so it doesn't pull everything, but that's in progress. And then there's this classic case like requiring massive things for a tiny fraction. It's like you have tiny script that you want to run and you require the whole Perl stack for that. So those cases we're looking for as well. And I have a few things. How engaging we upstream developers, of course, we're not doing this in isolation in Fedora. Some things are just packaging, some things are sort of for changes. So we're looking at both. Also implementing process and policy changes. For example, if you figure out a better approach for users in containers, so there's no system D, we can make a policy in the project. So it's easier followed. And then providing guidance, of course. Like there'll be many things that we realize, discover and we can teach people how to make decisions. So how can you help? Last three slides, if you're packages, this is just about the minimization mindset. Like just think about it, if you add a dependency, it can have a huge impact on many things, containers, floodbacks, ISOs, or even just those installations that we don't even ship as an artifact in there. We don't even see it, but what people install. So that's how you can help. If you're developers, you can help improve the feedback pipeline, or just, we can talk about other things, how we can make it easier for everyone.  In all seriousness, I'm happy to have all various discussions if you have ideas. Let me close with this in lots of questions. This is not about like cutting features off from Federa, it's about being more flexible. So you have less installed on the system, but like you can choose things in that. Let's do it all again. Thank you. That was awkward. No. Sorry. I suppose it was gonna be capable of doing notifications. What I would personally like to see in distro is, the example you gave of pulling something for a single script and it pulls in the entire flow stack, I would really like to have thresholds to say that if between build three and build four of this package, the dependency tree group by a certain margin, I think that should be flagged for not just the maintainers, but ideally anyone downstream of that package. Yes, I agree. I just repeat for the recording. Steven proposes that the feedback pipeline should have some thresholds, for example, for certain growth and have notifications so we can actually see like differences between builds. That's exactly what I'm planning there. It's a little bit tricky in that sense that there's nothing to query this data for. Like, if I only care about single packages, I can ask about the build and that's easy to figure out, but here I wouldn't have to do an actual compose of the whole repo for every build of every package, like in theory to get this data. So we're going to figure out something like Alexandra is looking at me will be figuring this out very soon. Not for every build, but like, yeah, very often so we can do those things. And that's a very good point. And it's definitely the plant. Yeah, yeah. Yeah, the note was that we can actually add this feedback to the package update. I think Bodhi and Fedora. So if there's a package you're submitting an update, you can see, hey, you caused this, are you sure? And if you're sure, like you can proceed, but if that wasn't intentional, you can just, you know, revert and do try again. Yeah. Do you have any support from RTL? You want to install on the subset of the package, like you want to throw out main pages, documentation, or you want from packages to build separate packages, the main pages, separate packages, the documentation as well. And the other? Let's do the one and then we can go. So the question was if I intend to be able to somehow install just parts of packages, like we leave out documentation, leave out main pages, or if I want to break these things into separate packages. I would say I don't really have a preference. I just want it to be possible for people to install maybe just what's relevant for them. However, we achieve that in the implementation. Like I don't dictate implementation, I just want the result of being able to. But I'm telling you, like, those are more, the features are more for third is adding features. So we have close features and they make space with more libraries and so on. But often the use case which is bringing the library is minimal, so not that you want to use it, but it's nice to have it. So I do want to squeeze this feature pool or base features. That's a very good point. Yeah, so the point was that people are adding new features into their packages because they used to, but it grows the size and like, how am I going to approach this? So like that's one of the constraints. This is a binary distro. So like some of the configurations that you do before build, like for example, in Gentoo, you can do this very easily. In federally count, but that's why I'm focusing on the use cases and not like on, I don't say like I focus on HTTP as a whole. I want to focus on HTTP in this very specific use case so I can actually know what it needs and what it doesn't need. And if we define many of those use cases, then the project can say, hey, these use cases are the most relevant for us. So we need to prioritize those or we can say, hey, there's these huge groups of people using this same thing in very different ways. Can we build it twice and make both smaller or something like that? But there's ways how to approach it. But yeah, we need to keep in mind that like adding new features is nice, but it has impact. So there's a balance. It's a balancing act. I guess I have time for one last question. All right, two questions, very quick. Just curious, do you have any data online? So if I have data, if it's just like dependency growth or not individual packages, I don't know right now. I don't have, well, I collect the data so I could visualize it somehow, but there's a service, it's developed by David Cantrell, that's focusing only on the packages and because it's just the packages without dependencies, it's much easier to access the data right from the builds to get fresher result and he focuses on violent things. So we already talked and it'll be part of that. How are you collecting the data and how often and from where? How am I collecting data, how often and from where? So there's nothing to query for those use cases. I have to do that and because I implemented that and I'm not that smart, I install everything and then query and it takes like four hours and I do it every day. I need someone to fix it maybe if there's even a way. Like my motivation was to do it as fast as possible because that's the prototype so I expect to throw lots of codes away and I also don't want to introduce errors by re-implementing, I don't know, dependency, whatever. So like that was the easiest way but it's a prototype and we can definitely. So I just installed from the federal repose on the box query pro way. That's how I get the query results. All right, I guess that was everything. Sorry, we can talk.


Hi everyone, Joe for Jasper's casebreaks.com We forgot to randomize the 250 points that popped out of this break right here XR football pick your team number number three So my apologies about that Let's grab everyone's names Let's put all the names in here name on top gets 250 points from pick your team three after four to six ten times one two and 10th and final time after 10 times It's gonna be Corey Corey. There you go. Thanks for getting into XR pick your team three 250 points going your way plus a free top loader and Folks if you want more XR football and if you're watching live today Check out the website Jasper's casebreaks.com. Thanks everyone. We'll see you next time. Bye. Bye


McLaren USA is voluntarily recalling about one million strollers because of fingertip lacerations and amputations. This recall involves all McLaren single and double umbrella strollers. The strollers hinge mechanism poses a fingertip amputation and laceration hazard to the child when the consumer is unfolding or opening the stroller. The firm has received 15 reports of children placing their finger in the strollers hinge mechanism resulting in 12 reports of fingertip amputations in the United States. The word McLaren is printed on the stroller. The effective models in this recall are VOLO, Triumph, Quest Sport, Quest Mod, Techno XT, Techno XLR, Twin Triumph, Twin Techno and Easy Traveler. They were sold at Babies R Us, targeted in other juvenile product and mass merchandise retailers nationwide from 1999 through November 2009. Consumers should immediately stop using these recall strollers and contact McLaren USA to receive a free repair kit. For additional information, contact McLaren USA toll free at<PHONE_NUMBER>. CPSC is still interested in receiving incident or injury reports that are either directly related to this product recall or involved in a different hazard with the same product.


One of the most important concepts in computer science is how to define new commands. How to add your own words to a computer language. Most computer languages have only about 100 words or commands and really the art and magic is in defining your own new words out of these building blocks. We do this all the time in sports. For example, in basketball you start by learning how to dribble, how to do a layup, how to rebound. Once you've learned these really basic moves, you learn new moves and put together these building blocks like a pick and roll or a give and go. And you can then go from there to do more complex plays. And once you learn that play and give it a name, everybody on the team knows how to do it. Similarly, once you've taught a computer how to do an action once using these sequence of commands you can make up your own name for that action. So it's easy to repeat it later. When you define your own command and give it a name, that's called a function.


I'm Jim Anderson, Assistant Director and the Criminal Network Subdirectorate, and I'm honored to oversee the Counterfeit Currency and Security Documents Branch, which is a unit that is responsible for leading the International Research Project entitled Physical-Chemical Study of Crossline Intersection. This study was conducted over the past six years by Interpol and the International Academy of Experts in Handwriting and Documents, and it brought together the expertise and knowledge of 120 forensic document examiners from 54 Interpol member countries. In order to examine microscopic differences in written and printed works to determine the exact timeframe that a document was forged or counterfeited. The results of this International Research Project were prepared jointly by Interpol and the International Academy of Experts in Handwriting and Documents. And our study proposed a unique, non-destructive procedure to address this issue, so as to help forensic experts resolve cases of forgery and counterfeit, as well as to preserve the integrity of the evidence for future examinations. This unique, non-destructive procedure is an exciting development in the field of document forensics, and I would like to thank the International Academy of Experts in Handwriting and Documents, and all the document forensic examiners and researchers who contributed their expertise and time to this significant research project. Finally, I would like to thank Daniela Dervaska from the Macedonia Police, who is currently succumbed to Interpol's counterfeit currency and security documents branch, since this research project would not have been possible without her leadership and expertise in the field of document forensics. We wish to share the results of this scientific research project with the International Community, in particular with forensic document examiners in preparation of their expert opinions. The subject of this publication is the relationship between time and inks and the results of preform analysis, which comprise four protocols, namely A, B, C and IN. Protocol A provides the answer of whether or not invisible ink migration can be used for ink dating. Protocol B addressed the question of whether or not visible ink migration can be used for determination of delta T. This is the time gap of execution of two lines. Protocol C answered the question whether or not fading of luminescence can be used to determine delta T. And finally, we have a protocol D, which focus on identifying the chemical components of inks. Significant project conclusions are that visible ink migration can be used for sequencing of cross-inclined intersection, invisible ink migration can be used for ink dating, decreasing of luminescence intensity within cross-inclined intersection can be used to estimate delta T. And we were able to identify luminescence components of inks present in both visible and invisible migration, such as crystal violet and its degradation products. To learn more, you are welcome to consult the publication via I-247 Global Police Communication System as well as Interpol Public Webpages.


Y'all don't understand what we got up in here today man. We got a we got a big part of history right here Do you got to get the uncut? Good it won't be Give a note with no filter But I'm so excited I can't wait And the new I knew that we jailed as a group was like The night we had the battle roots on 89.3 Like when we battle roots at that time it was almost like shit I was like us against them You know I mean and it was out us putting our skills up against a Philadelphia skills, you know So it made us say okay. Okay. We're good enough for that.   Like you can now we're being used as You got a look at the time like Heidi is right now. Hi. Hi Lenny is right now Right now. That's how I was.  You need to pop it But that's where it was.  It would get too attached. Yeah need to get to it, but you don't count You don't camera somewhere Like that's the only difference that I know that now it's more about with this internet with plan It's like with forces It's like look right now. I Can take the most vile situation Put the right situation together and sell it leave go buy it You Couldn't do that then it had to goddamn Clubs to the street you had to go and walk up in the club and get up Hey, it was a different mix of people always the kids from over there in love five point Always the kids downtown and went degraded the kids that went out there to see that's that's when When Calla roll with the shit so everybody with the South the cab like, you know kids on this side These were the college part shoe store.    So I'm just saying that Atlanta was still slow to the average I you know I mean if you weren't in the street You didn't know and if you wasn't in into the game then you damn show didn't know You know I mean kids only went to Walter's the freshest kids what it needs from downtown They had the freshest gear them these were the killers too.  He he was the guy and then the first the first time ever did a show grows on On Stewart Avenue man. I opened up a salmon Sam. I was the first time I seen Sam like Yeah Yeah, he been gone man, that's a real info see that's from the old school. See you can't talk to him It's all it's on go you call me from the whole You know I mean, I'm just saying that you got a real idea and needed to ask me man. What's so and so and what's so and so and Man, they ain't built for this No matter the money no matter what them folk gave them no matter at the time when it happened And I built for it.   I'm pimps. It's fun. Give my mom Yeah, like Carl Rick will I need we coming on them we like y'all Drove in the Cadillac and he pulled over here mama at the wheel Pimp, what's happening?    You like Won't you see you know me? and and That's the that's the that's the hard part because it's like When you watch the youngest name you like man, you need to get all your money And ain't tripping but just look around bro. Look who they playing with man Look who they playing with It's really in your face man. Look what they doing the Kanye like look what's happening?  You get what you give now, right? You want to get that you want it all unless you got the records got there. You got to figure out something else to see You get out what you put in hey man once the hits ain't there way baby. What we got? No, we're going on to the neck Come on. I didn't get deeper and deeper for breakfast deep and I still get stage fright No, I mean I don't know.    I Ain't tripping if a nigga around here y'all say the greatest and he's God. Yeah, okay.  It's about who gonna major in the most money How do niggas get to their power did they deceive did they cut their buddies out they wanted all do they want it all Hey, man, look at how they got there If that need right there legend, then what's the difference between a nigga living to a tune? If Park died in here legend what made him a legend?  I need with the deal man Yeah, I need to do now.     She what you mean?  No era nigga I'm just saying when you didn't when you couldn't look in the nigga pot. I need to have nothing but to do but to do No, it's like man, I ain't got them All that how you do yeah, oh boy, let me get that Okay, y'all doing the words like that Well, I'm about to do this here tonight.  That's where I'm like way man I ain't tripping any generation. I'm just saying when somebody don't say hey, man, what y'all nigga doing?   I ain't heard this in a minute. They were like nigga.  Keep the numbers the same. Don't worry about it.  Hey hit the button We look good baby pick up awards. Hey, man, it's you all got that inflated now What made me go back in the studio now without the drill do well Money, but his money in motivation. It can't be Real


So I briefly describe the secretion assay that we used to estimate the functions of these mutants. So this is a cartoon of the experimental setup we used to perform the assay. It has, so there is a rotating disk electrode, or IDE, which is made of a classy carbon that is suspended into a sample chamber. And the principle of the assay is based on the electro oxidation of norepinephrine. So when norepinephrine is present in the sample chamber and it contacts the IDE on the rotating disk electrode, it is oxidized. And the change in oxidation potential of the rotated disk electrode can be measured with respect to a reference electrode and can be recorded by an output device. And so we used cracked cells for mutilized cells, which are capable of secreting norepinephrine, and added them to the sample chamber. So what is done to these cells so that they are mechanized, they are homogenized, and their cytosol is removed, but their membranes are preserved intact during the process. And then they are suspended in a physiological buffer, and the test factor, which in this case are caps mutants, are then added to it to test their activity. And this entire cell suspension is put in the sample chamber and then calcium is added to it to trigger exocytosis. And depending on the IDE signal that we get, we would be able to tell whether it increases caps function beyond that of the wild type caps, or whether it reduced caps function, because the amplitude of the signal, which is obtained from the experiment, is proportional to the number of norepinephrine vesicles released. And the good thing about this STA is that it has very high sensitivity, so even small quantities of norepinephrine veins can be detected. So these are our results from the IDE secretion analysis. We find that the 957 to 961 aniline mutant, it has almost the same activity as our wild type, so it is not exactly very interesting. Although this is a surprising finding, because we would expect that because it is within the monchromology domain 1, it would show some activity. And as a second mutant, however, the 1134, 1138 aniline mutant, which lay the seat on the segment of caps protein, it did show some reduction in activity as compared to wild type. So it goes around 75% activity as a wild type. So this graph again shows the comparison better. As in, this is the wild type voltage which is recorded, and this is the voltage recorded using the 1134 to 1138 aniline mutant. So the conclusions from the experiments that we have done are that the conserved residues in monchromology domain may be important for proper folding of caps. That is the reasons why we also update distributions of the protein. Second is that the secretion assay data that we have suggests that 1134 to 1138 aniline mutant shows reduced activity, but we do not know yet what the exact reason for that is. So more experiments need to be performed before we are able to conclude what is exactly the reason. That is, the caps 957 to 61 mutant does not reduce capsicility integration. So it presumably does not lie in the exact snare binding region within the capsic protein. So these are the references that I've used for making the presentation and acknowledgments to the Korana program, Department of Biotechnology in the U.S. Science and Technology Forum in UW-Madison for Funding Bioproject, to Professor Tom Martin for hosting Nina's lab, and to Neil and all members of the Martin lab. They've been extremely helpful and they've offered guidance whenever I've asked for it, and the 2011 Korana fellows and the audience for paying attention.


We are now at the first day of the harm reduction conference, European harm reduction conference in Bucharest. And we have now a registered number of 360 people, which is much more than we expected.  It's the first time in our local history in the harm reduction field when this kind of event takes place here. We can see a very serious divide, a regional divide in the European Union. We are really having an emergency situation in many countries, a crisis, where harm reduction services which were established in the 2000s completely collapsed. And this is partly because of change in funding environment, also partly change in political environments. In Bulgaria, needle and syringe programs completely stopped. There is no needle exchange anymore because of lack of funding. In Hungary, we still have on paper many needle and syringe programs and some of them really operate. But the two largest programs were shut down, actually, which served more than half of needles distributed in the whole country. Here, where we are in Romania, we know that clients served by needle exchange programs in just this year dropped from 7,500 to 2,000 people. We have to struggle to keep alive our services. But I think this is something that everybody should be aware of and not be very comfortable thinking that they have resources for now because tomorrow you never know. Isentres. Isentres. A lot of Isentres is very good. We are having a generalized talk out regarding the AJV treatment in 11 hospitals now. Starting with the last days of August, we start to miss the AJV treatment from the hospitals. I received some participants bring me donation and I will send it. In comparison with 2006, there were I think six organizations who were providing harm reduction services. But by the time they closed you to lack of funding because the financial budget decreased by 65%. The harm reduction services in Bulgaria stopped in July 2017. After the global fund, we drove the country. We don't have any exchange. We also don't have any testing on the streets among the group of people who use drugs and sex workers. And we don't have also case management which is a very big problem because usually people who we are working with are very marginalized. Can you tell us what Haryacht is about? Haryacht has been a three-year project financed by the European Commission and it's about harm reduction, a scaling up, intensifying, advocating for harm reduction, especially in Eastern EU countries. The main lesson we learned was that we cannot really make changes in harm reduction even with the big EU project without governmental involvement. Because if government does not support harm reduction programs and if government tends to close NGOs, then we cannot come from outside with trainings and teach people how to do testing when the government doesn't find these activities. I see a handcuff on you. What does it represent? Yeah, that's about criminalization. Here in the conference, we bring campaign, chase the virus, not people, campaign by nine original Eurasian networks of different communities. And we all recognize that criminalization and discrimination is the key barrier for HIV response, hepatitis or TB response.  In Germany and in some other countries, Great Britain also, we have a high prevalence of overdoses, also of opiate overdoses, also fentanyl. I don't think that the situation will be the same as in North America, but we have from 50 to 75% of all drug-related deaths are opiate overdoses and we have to develop the right services for that, drug consumption rooms, naloxone and some other things. Drug consumption rooms prevent overdose, the prevention of HIV, hepatitis C and other blood-transmitted disease.  The benefits involved in the community and the harm reduction are that we know what happens first, fast. For example, in Glasgow, we had a peer-to-peer naloxone program, gave out more naloxone in one small area of Glasgow, they gave out 1,200 units in 11 months, which was more than every single professional gave out in the previous year in the whole of Glasgow. What is drug tracking? What is it about? We propose people who want to consume drugs or consume drugs to analyse their drugs. We can identify especially new substances sold on the internet and also be careful about phantomies, for example, and to be sure that we have not such big problems in the United States, in France. What does harm reduction mean to you? It's a philosophy, a notion, that sobriety is not for everyone. Not all people need sobriety to function. Some people need drugs to function better. Harm reduction is not only about drug use, it's about how you interfere with other people or institutions or situations. So it's a way of thinking, of living and working.


Hello and welcome to this session. This is Professor Farhad in which we will discuss net operating loss for short NOL. So what is net operating loss? Simply put, net operating loss is when the taxpayer annual business deduction, we know it as business expenses or business deduction are greater than the annual business income. Simply put, we have negative income. Negative income is the same thing as a loss. Therefore, what we have is a net operating loss. In this net operating loss is created from a trade or a business and casualty losses. Those are the items that generally create net operating loss, NOL. Now, why do we have this NOL? What is the benefit of it? What is the importance of it? Let me show you an example with two taxpayers to show you why Congress has this rule, net operating law. Let's assume two taxpayer, Adam and Avi, their single taxpayer, they started their business in year one, and they reported the following income. For Adam, Adam reported in year one taxable income of 20,000. In year two, a loss of 160,000. In year three, a taxable income of 170. In year four, a loss of 120. In year five, a taxable income of 150. On the other hand, Avi reported a taxable income each year for 12,000.  And if we take 12,000, Avi's stable business times 5,000 equal to 60,000. So notice, over a period of five years, both Avi and Adam earned 60,000. The only difference is, Adam's business is cyclical, while Avi's business is not, is stable. Now, what I'm going to do, to illustrate the point, I'm going to use the 2022 tax rate for single taxpayer to compute their taxes. And this is what we come up with. If you compute their taxes, Adam's tax bill in year one is 2,195. Avi is 1,235. And it's the same for the next five years. Again, this is just for illustration. The tax rate may not stay the same. But to make the point, in year two, Adam did not have a tax bill because Adam generated a loss of 160. In year three, Adam made 170,000 and their tax bill is 34,000. Year four, nothing because a loss of negative 120. And in year five, 29,000. So as I stated, they both made 60,000 over five years, net of 60,000. Adam's tax bill is 66,667 dollars, while Avi's bill is 6,000 over five years, 175. What does that mean? It means because their business is cyclical, one was affected more than the other. Simply put, what the Congress says, if you generated losses in a particular year, you could use those losses in future years. So simply put, you have what's called NOL, net operating loss. And you can use this net operating loss to offset income from future years. That's the idea. And I hope you can see the importance of it. Now let me show you on the tax return specifically where this all fits. So simply put, we have something called schedule one. And on schedule one, you first include your NOL notice it's negative, then you compute schedule one. And at the end, you either get a positive or a negative number. Then this number, assuming it's the only thing is NOL, we have a 10,000 net operating loss.  You have a net operating loss of 10,000. Now this number will go to line eight, other income from schedule one line 10. But this will be a negative 10,000, negative 10,000. Now what I want you to notice that the NOL, this is where the NOL end up on your form 1040. NOL comes before your adjusted gross income, your AGI, which is we'll talk about this shortly. So it's very important to know that NOL is a deduction for AGI. It comes before AGI, for AGI. Now before we proceed any further, I would like to make an announcement about my company, farhatlectures.com. Farhat accounting lectures is a supplemental educational tool that's going to help you with your CPA exam preparation, as well as your accounting courses. My CPA material is aligned with your CPA review course such as Becker, Roger, Wiley, Gleam, Miles. My accounting courses are aligned with your accounting courses broken down by chapter and topics. My resources consist of lectures, multiple choice questions, true-false questions, as well as exercises. Go ahead, start your free trial today, no obligation, no credit card required. NOL rules have changed over the years. Simply put, we're going to start by stating that anything prior to December 31st, 2017. So what we're going to do is this. We're going to look at a timeline. Let's draw the timeline here and we're going to say 2018. And the reason I say 2018, because the rule changed as of December 31st, 2017 for the Tax Cuts and Jobs Act. Before 2018, if you had NOL, you can carry back the NOL two years and you can carry it forward 20 years. Those are the old rules. And the reason I put the old rules in quote, because the old rules, the old rules could still be in effect for a certain period in the future. How? Well, the old rules allows you to deduct 100% of your taxable income. So the NOL allows you to do so. So if you have some NOL from 2016, let's assume you had an NOL from 2016, and you are using this NOL now, and now let's assume now is 2024. And you happen to have 60,000 of NOL in 2016. And in 2024, you also have a taxable income just to kind of keep it simple of 60,000. So if you have NOL of 60,000, and you have taxable income in 2024 of 60,000, you can use this NOL 100% of this NOL against your taxable income. And as a result, you will have a taxable income of zero after you deduct the NOL. Now, NOL arising after December 31st, 2017, simply put, after starting 2018, all the way until 2020. So this is 2020. So here we are discussing 2018, all of 2018, all of 2019 and all of 2020, three years, those NOL, they can be carried back five years. And they can be carried forward indefinitely. So those they have a special rule. Also, those NOLs arising after the end of 2017, which is 2018, 2019, and 2020, you can also deduct them up to 100% of those taxable year, obviously before the NOL deduction. However, NOL arising during those years 2018, 2019, and 2020, that they are used to offset income going forward after 2020, it means going forward means they are offsetting income in 2021, 2022, and in the future, then those will have to be limited to 80% of your taxable income. Let me explain this. So let's go back to this example here and let's assume in 2018, we had an NOL of 60,000. So forget about this 2016. Now the NOL arise in 2018. And in 2024, we had taxable income of 60,000. Same example. Here's what we have to do now. We can no longer take the full 60,000. What we're going to do, we're going to take 60,000 taxable income, multiply taxable income by 80%. And that's going to give us 48,000. Now we have NOL of 60,000. Well, although we have NOL of 60,000, and we have taxable income of 60,000, we cannot offset all of our taxable income. We can offset NOL can offset up to 80%. So simply put off the 60,000, we can only use 48,000. And that's going to reduce our taxable income to 12,000. However, we still have after we use the 60,000, we still have 12,000 of NOL to be used in the future. Now NOL after December 31, 2020. So this is basically the most current rule. It cannot be carried back anymore, but it can be carried forward indefinitely. Again, we still have the rule applies of 80% the limit. So it can only offset 80% of your taxable income. So anytime the carryback option is available, which is prior to 2018 and prior to 2020, the taxpayer may elect not to carry the carryback. So you don't have to, if the carryback is available, you are not required to use it. However, if you did use it, you have to go back to the oldest year first in the carryback period. So you have to do it in order starting with the oldest year. Now the best way to illustrate this is to look at an example. Let's assume John is a taxpayer, a single taxpayer started his business in 2017. And this is John's reported income, 2017 taxable income of 70,000, 2018 a loss, 2019 a taxable income of six, 2020 a taxable income of two, 2021 a taxable income of 10. And what is the amount of NOL carried forward 2022? So what is John going to do? So here we're going to assume, we're going to assume that John's going to take this 90,000 and that's the that's the most logical thing for John. First go back to 2017 and wipe out this taxable income, simply put file an amended return and whatever taxes I paid in 2017, get all my money back. Okay. So I'm going to go back because I'm allowed to go back five years if I generated NOL in 2018. So of the 90,000 I used up 70,000 of it. What do I have left? I still have 20,000 of NOL. What's going to happen in 2019? I generated a taxable income of 6,000. Excellent. In 2019, I can wipe out all of my taxable income because I'm allowed to do it 100%. I still have 14,000 of NOL. I have 2000 of taxable income in 2020. In 2020, there's no limitation. Also, I can go against 100% of my taxable income. I still have 12,000. I still have 12,000 and NOL. In 2021, I had 10,000 of taxable income. Remember 2021, what's going to happen is I'm going to have to slow down and think about it. Think about what think about the fact that I cannot offset this whole thing. How much can I offset? I can offset 80% of it. So that's going to give me 8,000. So I have 12,000 of NOL. I am going to use only 8,000. That's the maximum allowed. The maximum amount I'm allowed to use. And what I'm going to be left with is 4,000. Therefore, the NOL carried forward to 2022 is 4,000. And here's the solution. Here's the solution. So you can see what we did. The net operating loss is carried back to offset taxable income from 2017 first. The remaining 20,000 goes against full 2019, full 2020 and 80% of 2021. And here's the computation and what's left is 4,000. Now, remember what I said earlier when I showed you the tax form about NOL and adjusted gross income? And that operating loss carried forward is accounted for as a deduction to arrive to AGI. And I showed you it comes before AGI, deduction for AGI. That's important. Why that's important? Because you have to take NOL into account. Any deduction depends on the AGI, such that medical expenses, charitable contribution, casualty losses, must be determined on the basis that NOL is applied. So it does affect adjusted gross income. And that's why it's important to understand it comes before adjusted gross income, because many computations such as medical expenses, many deductions are dependent on AGI. So it does help in reducing your taxable income, you're reducing your AGI. What is not included in computing NOL? Now, at the beginning, we kept it simple, because to get to the big picture, and I said, NOL is basically generated from your business, from your trade, from your business. And that's usually the case for casualty losses. But we have to understand that certain items, they are considered income or deduction, that they are not included, because this NOL is for individual. We're going to look at the NOL for corporation later. The following item listed are not allowed when determining an individual's NOL. What are they? Access non-business deduction. So we're going to have certain deduction, but those deductions are non-business over non-business income. We're also going to have income, but that's non-business income. So we need to know what are the non-business income and non-business deduction. Well, anything that's non-business, like what? Non-business income will be interest income, dividend income. Those are not business income. Rental income is business income, but those are not. Example of non-business deduction. So those are deductions, but they are not business, so they cannot be included when you're computing NOL. Include, among others, contribution to your individual retirement account. You cannot say, well, I contributed to my IRA, this might create an NOL for me. That's not the case. Alimony payment. Standard or itemized deduction. Think about the standard deduction. Let's assume your standard deduction, I don't know, just for the sake of illustration, is 25,000. You really did not pay anything. This is just basically a phantom deduction given to you by the IRS. So you cannot say, this is a deduction and I want to use this deduction to create a net loss and take this net loss. You can do that. Those are not allowed when you're computing NOL. Again, when you think of NOL, think of business income and business expenses or itemized deduction other than casualty loss. Again, we said casualty losses and it has to be in federally declared area, but casualty losses are. NOL carried over from previous years. You cannot count it in computing your new NOL. So you cannot count it. Say, I'm carrying this NOL. Now I'm going to increase my NOL by this carried over NOL. Well, now you cannot compute your NOL using other years NOL. Then you will be double counting the NOL. Capital losses and access to capital gain. So if you incur capital losses and access of capital gain means you have more losses than gain, remember what you can do with capital losses. You can take 3,000 against ordinary income, but you cannot use capital losses when you have capital losses, net capital losses to increase your NOL. That's not part of your NOL. Section 1202 exclusion of gain from sale of qualified small business stock. If you incur any loss, you cannot use it in computing your NOL. If you have a qualified business income deduction, this is deduction, QBI, you cannot use it to create or increase NOL. Because again, the QBI, the qualified business income deduction is basically a phantom deduction. It's a deduction given to you by the IRS basically, because you have a qualified business. You cannot use it to create NOL to get more deduction. It doesn't work that way. As I mentioned, rental losses are business losses. So in contrast to interest, in contrast to dividend, if you have rental losses, those are business losses. They could generate NOL. Bear in mind, the NOL may not be used to reduce your self-employment tax. So self-employment tax is your social security and Medicare. You cannot use NOL to reduce those. If you have any self-employment tax, you are still responsible for those self-employment tax. NOL may not be deducted against taxpayer self-employment tax. Again, we're talking about social security and Medicare. You cannot use it against them. Let's work an example to illustrate the concept. Because on the CPA exam, they'll try to trick you. They will ask you to compute NOL and they're going to give you all sorts of different numbers. You have to know what numbers included in the computation and what number is not. I told you the shortcut is any business deduction, any business income, that's included in NOL plus casualty. Okay, so let's take a look at this number, this exercise. For the tax year 2022, Adam reported operating income and expenses of 250 and 290. Well, is this part of NOL? You bet. It is operating income from their business. So notice here, we have more expenses. So we have 290,000 of expenses and 250,000 of income. This is the expenses. This is the income. We already know that this business generated 40,000 of losses. Adam earned 2,200 of interest income. What should I do with this? I should ignore it. And 5,000 of capital gains from the sale of a business property. So this capital gain is not any sort of capital gain. It's from a business property. Well, if that's the case, I have an additional 5,000 of business property. Adam claimed standard deduction of 12,950. Well, that's great. The standard deduction is a deduction, but I cannot say, let me add my standard deduction here because I have a deduction and increase my NOL. Not at all. The standard deduction is something that's given to you. You did not even make any effort to generate the standard deduction. In other words, you did not spend money. It's not part of your business. So you should not use it. So simply put, we're going to have an NOL based on this of 35,000. Now, in many CPA review courses, what they do is they show you the whole thing. They will just kind of show you the whole thing. And what does it mean show you the whole thing?  And this is your access deduction. So you have more expenses than income, but that's not your NOL. This is your access deduction. Now you need to back out. What do you need to back out? Well, I already told you that those two figures interest income and the standard deduction need to be backed out. They cannot be used in computing NOL. So what we do is we're going to have to add back the standard deduction. Why do we add it back? Because we subtracted it. If we're going backward, we have to add it. And what do we need to do with interest? Since we added it, we're going to have to deduct it. And if we do so, we're going to come up with 35,000. The same number I came up with here. So first understand the big picture. Follow your CPA review course. But remember, NOL is a business deduction. Generally speaking is a business deduction. But follow the rules. If they're giving you a specific formula, follow it, but make sure you understand it because the way I explain it could be a little bit different than your CPA review course or your income tax course. But the overall idea is the same. What should you do now? Go to farhatlectures.com and work MCQs through false questions that's going to help you solidify this knowledge and help you get ready for your CPA exam. Good luck, study hard, invest in yourself and stay safe.


We work with any industry that has a system that is highly critical to the success of the business. Hi, this is your host, Abhinav Hartyan. Welcome to another episode of TFLS Talk. And today we have with us once again, Margaret Hoogland, VP of Global Sales and Marketing at Syos Technology. Margaret, it's great to have you back on the show. Thanks for having me back, Swap. It's good to be back. And today's theme is high availability at airports. And this is a topic that we can all relate to, all of us frequent and business travelers. We know the pains that we sometimes go through at airports. But before we talk about high availability for airports, can you just explain what exactly do we mean by high availability here? So high availability, we provide application high availability, which is very specific. Customers sometimes put their application in the cloud and they get an SLA for high availability and they think that they're done. In fact, the cloud is providing infrastructure high availability. And so sometimes customers come to us because they've had a situation where their application stops working in the cloud and their cloud VM has continued to operate just fine. The cloud vendor has met their SLA commitment and they're puzzled as to what's missing. They need application level, high availability to cover all of the software driven reasons for a failure in a high availability environment. And by high availability, I mean 99.99% uptime for the application. So the critical applications that customers, businesses rely on are where our market is. SAP SQL server, HANA, Oracle, these big systems that run multiple different important systems within an organization that when they go down, they cause disruption, delay, and they're very, very costly. So that's where we work and that's where the clustering that we provide comes in. In the context of airports, how important or critical high availability is for airport operations? As you can imagine in an airport, everything is deadline-driven and a lot of the activities that happen in an airport are dependent on one another. So if one system is late, delayed, fails, many other things happen in a domino effect. And so all of the systems in an airport work together. And so we are used in a variety of applications and databases. For example, baggage handling systems, card swipers for access control, video surveillance monitoring systems. We are in a validated milestone, makes X protect software, which is a surveillance camera management tool. We also protect in the big board, the arrivals and departures system that everybody relies on. First thing you look at when you go into an airport. So Psyos is protecting systems in over 100 airports around the world, both large international and regional airports in a wide variety of use cases. Now, if you look at airports, they run and manage a wide range of systems. Which of the systems really need high availability? Any kind of system that requires high availability, they're typically running on SQL server, SAP HANA, SAP systems, the Oracle database. Psyos protects both systems running in the cloud, on-premises and in hybrid cloud environments. Some customers put these systems either on-premises with a node or a disaster recovery site in the cloud or they run them in the cloud and they want a special disaster recovery location on-premises. Psyos uniquely covers all of that. You can set up the configuration that you choose, both in a Windows and in a Linux environment. So some customers like to use a lot of applications run on SQL server, for example, with an application running on the SQL environment. Psyos will protect that SQL environment and give the customers the choice of either running Windows server failover clustering that comes with their Windows server. We add the ability to run in the cloud without the need for shared storage, which is a requirement of Windows server failover clustering. And it can be quite complex to do so in the cloud. And Psyos allows customers to run their systems on-premises or in the cloud in a Samless environment using local storage. It makes Windows server failover clustering think that it's a shared storage environment. This allows customers to use SQL server standard edition. They save 70% of their SQL licensing that way. We also will support SQL Express for customers with environments like a video camera where you have a lot of small SQL instances that you need to protect. So it's quite a wide range of use cases and applications that we protect. In a SAP HANA environment, one of our key differentiators is that we provide application recovery kits. So if you think of the complexity involved in taking a SQL server, sorry, a HANA database and detecting a failure, moving it over to a secondary server and starting up all of its processes, A-S-C-S-E-R-S, all of the supporting services in the correct order, that's quite an undertaking. And customers without Psyos have to manually figure out how to script all of that. We have these application recovery kits for all of the major applications. And we have one that you can use to customize to an application that might be very specific. You plug that into your Psyos environment and we handle all of that. And that means that your configuration is easier, your failover is more reliable. When it does failover, it will operate in the best practices that are required by that application, that SAP best practice or SQL server best practice or Oracle or whatever your maybe airline specific requirement is. I don't even want to think about it, but what would happen if there is a downtime at an airport?  Now you may not make your connecting flight that baggage may end up in the wrong place in the wrong time. If your flight gets redirected, you may end up in a city far away from your baggage. So you think baggage handling isn't that critical an application when in fact, when you think of the consequences, it is quite critical. If the arrivals and departure board aren't available, if anybody who's walked into the airport knows that gates change quickly, departure times are delayed. And if you don't know that from that board, chaos can happen very, very quickly. So those are some of the critical applications. Another example would be access control systems. There's so much security in airports they need to know who came and went through every door and having one of those systems fail for some period of time would automatically lock the door, but it might not allow the security people to see who came and went through that door in a given timeframe. So that's a serious potential security lapse. You did touch upon that briefly earlier, but I want to go a bit deeper, talk a bit about how does iOS technologies and solutions help airports with their high availability strategies and needs. Good question. So we run the application or the database on a server that's connected to a secondary server, sometimes multiple secondary servers. And they are clustered, so they operate as a unit. Our software will detect any potential failure from the network to the storage, to the hardware, to the operating system and the application itself through the full stack. And if that our software detects that there is a failure, it will move the operation of that application over to a secondary server. It'll bring it online in compliance with the application's vendors best practices, and it will make sure that that failover anything connected to the primary server is now connected to the secondary server and operation continues automatically within moments. So the end users don't experience a serious downtime incident, the data is moved over and it's a continuation of operation in a very elegant way. Is it possible for you to give some examples or use cases of airports leveraging your technologies and solutions? We have several large international airports that use silos to protect their baggage handling systems. So as you might imagine, if baggage handling doesn't operate for even a short period of time, people might miss a connecting flight, they might be rerouted to a different city and therefore their baggage is now going to the wrong city. It becomes quite chaotic and very expensive for the airline and the airport if that system goes down. Security is very tight in airports and so card swipers need to detect and track everybody who entered or exited a specific door, for example. If that system goes down, the security may be breached surveillance cameras. If the surveillance camera is offline for any period of time. Again, in an airport, that takes on a far greater level of criticality than say a small store or something. The airports have such high expectations for both the time that is required, their lack of tolerance for downtime and for the specific applications that are running. Another example is the arrivals and departure boards. If the arrival and departure board isn't readily apparent to everyone when they walk into the airport, that's setting everyone at disease and everyone's sort of concerned if the board is down for any length of time, flights get moved to different gates, they get delayed, there people don't know when arrivals will come in. You can just imagine how difficult that is. So even a brief period of downtime for those systems is very costly both in time, confusion, customer satisfaction and actual cost. And so those systems are almost always run on a Psyos environment. So ticketing and reservations are another good example. The ticketing and reservation systems, if they are running on a database system like SQL Server, again, it's pretty obvious how quickly things can become very disruptive and very difficult if the ticketing system goes down. So many organizations use Psyos for those systems. Of course, we have run the whole series on how other industries need high availability and how Psyos help them. But just tell me, tell our audience beyond airports what other industries are there that rely heavily on Psyos for their high availability strategies? We work with any industry that has a system that is highly critical to the success of the business. So manufacturing process control systems, for example, manufacturing systems like SAP, ERP systems that are running an entire organization. They run the SAP application and or their HANA database on Psyos high availability clustering solutions so that they can make sure that those don't fail. Healthcare is another one. If healthcare patient record management systems fail or 911 emergency calls, our systems are down, the consequences can be deadly. And so any system that has that level of criticality where they need to be up and running 24-7, 365, they run them on Psyos. Margaret, thank you so much for taking time out and talk about this topic. And I would love to chat with you again. Thank you. Thank you Swap, I appreciate it.


India covers an area of approximately 70 million hectares of native forest. These forests are home to some of Earth's unique flora and fauna. They represent one of the 12 megabiodiverse regions of the world where India's western gods and eastern Himalayas are amongst the 32 biodiversity hotspots on Earth. The country's forests and wetlands serves as temporary home to many migrant birds. Number 9 Peru covers an area of approximately 73 million hectares of native forest and has the second largest portion of the Amazon rainforest after the Brazil. The Peruvian Amazon jungle is one of the most biologically diverse areas on Earth. Peru has the largest number of bird species in the world and the third largest number of mammals. It also has a very high number of species of butterflies, orchids and other organisms. Number 8 Indonesia Indonesia has approximately 91 million hectares of native forest. It is the only place in the world that has tigers, orangutans, rhinos and elephants all living in the wild. Borneo is the largest island in the country and the third largest in the world. But Indonesia has one of the highest deforestation rates in the world where Sumatras Rhine forests are highly endangered and are disappearing faster than forests in any other part of the country. Number 7 Australia Australia has approximately 123 million hectares of native forest. The majority of Australia's trees are hardwoods, typically eucalypts rather than softwoods like pine. There are 457 forest communities distributed across Australia. Number 6, Congo Congo covers an area of approximately 152 million hectares of native forest. The Congo rainforest is the world's second largest tropical forest, spans six countries, and contains a quarter of the world's remaining tropical forest and also the region has the lowest deforestation rate of any major tropical forest zone. Number 5 China China is a large country with different kinds of landscape which has approximately 208 million hectares of native forest. There are over 31,000 species of plant in China. The Ginkgo, a tree associated with China, is regarded as world's oldest living tree species. Number 4 USA United States forests covers about 33% of all land approximately an area of 310 million hectares of native forest. Nearly 59% of the total forest land in the country is private. There are 155 national forests in the country that cover nearly 190 million acres. Number 3 Canada Canada has approximately 347 million hectares of native forest. With 42% of the land area of Canada is covered by forests. The country contains 10% of the world's forested land, made up mostly of spruce, poplar and pine. Number 2 Brazil Brazil covers an area of 493 million hectares of native forest and also it contains one of the largest tropical rind forests in the world with more than 40,000 kinds of plants and more species of trees than any other forest. The tropical forest is home to about 250 tree species. Two-thirds of the Amazon forest are within Brazil. The Amazon represents over half of the planet's remaining rind forests, and comprises the largest and most biodiverse tract of tropical rainforest in the world, with an estimated 390 billion individual trees divided into 16,000 species. One in ten known species in the world lives in the Amazon rainforest. This constitutes the largest collection of living plants and animal species in the world. It is estimated that 43% of Brazil's total area is a large block of natural forest than has been relatively undisturbed and is able to support a wide range of animals and habitats. Brazil contributes 17% of the world's remaining natural forest. Sadly, Brazil also has the highest rate of tree loss in the world. At present deforestation in Brazil particularly the Amazon region, which is home to 30% of the world's animal and plant life, is on the increase. Large-scale resettlement of Brazil's urban population, agriculture and resource developments especially for timber are the major contributors of loss and degradation of the Brazilian forests. Number 1, Russia Russia, the largest country in the world, about half of it is made up of forest and woodland which covers nearly 814 million hectares of native forest. It is equivalent in size to the whole of the United States and contains about 22% of the world's total forests. Russia has two main types of forests which are boreal and temperate. Boreal forests are in northern and subarctic regions and make up about 60% of the world's boreal forests. They contain more than 55% of the world's vascular land plants. The temperate forests are in eastern and southern Russia are richer in flora and fauna. Among these forests is critical to maintaining viable populations of large carnivores such as Amur tigers, Amuro leopards, brown and Himalayan bears which like their prey the most have large home range areas. These forests house the world's largest population of brown bears and the waterways hold the largest spawning population of Pacific salmon. Lake Baikal in southern Siberia, which is the deepest lake in the world, contains 20% of the world's fresh water and supports 1500 species of flora and fauna. These forests are extremely sensitive to disturbances and regeneration takes time due to the harsh climate and soil conditions. Human activity and presence has a large impact on many larger vertebrates, while the fauna is very sensitive to acid rain and other pollutant. Don't forget to subscribe to our channel.


International Women's Day is a fantastic opportunity for us to celebrate women leadership. It's also a great opportunity for us to reflect on where we are today. How are we supporting women? How are we making sure women's voices are heard in order to create the future we want? As women, we've spent most of our lives growing the extra men just to take up space and prove that we can lead any important decisions. But this should not be the case. We are strong, we are smart and the world deserves to know that. Thankfully, with a content-based digital development, many of us women are discovering various platforms to amplify our voices. Now, more than ever, we know that technology has been advanced and has been increasing in every arena. And now it is our chance to use that technology. We use technology to tell the stories of women. Our unsung heroes who are doing amazing things around the world to transform our landscapes. An equitable world for women means providing that atmosphere where women's needs, aspirations, perceptions and their contributions are taken into account in decision making and benefit sharing so that technologies, digital innovations are tailored to gender perspectives. Increased investments in digital skills and technology targeting women will have greater impact in overcoming some of the global challenges we are facing in the world today. We must bridge the digital divide so they too can be empowered to tell their own stories in their own words. Let us use digital innovation to learn her story, share her story and let the world know that women can.