The principle maintainer of the MariaDB packages in Debian, and I work for the MariaDB foundation, so I have a possibility to invest a lot of time in making those packages properly and keep them maintained well, and at the moment there are no others from the package MySQL team here at Cape Town, but Robbie should be listening in via the stream hall, is Robbie listening? Cool. Great. You can also go to that IRC channel if you want to participate in the IRC discussion. Right. So we have a MySQL team in Debian and in Ubuntu, and it's a very old package, and it's a very big package, so over the years there has been lots of people involved, but at the moment there are not very many highly active people. I'd say we have four active people at the moment, and the most active ones, two most active ones is me taking care of the MariaDB package and Robbie Basak, who is a canonical employee taking care of the MySQL package. And we are looking for new contributors because obviously this is a huge package, and it has a lot of dependencies, and now something happened to the sound. It's okay. Yeah. So how many of you are Debian developers? Great. How many are Debian maintainers or aspiring to be Debian developers? So if you help us with packaging, we are happy to help you on that path. All right. Here's an overview of what the team maintains in Debian at the moment. So this is very small, but I'm sure you all can go to qa.debian.org and look at this on your own laptop yourself. So there's the Galera package, MariaDB package, MariaDB client libraries, LVM backup, MySQL 5.5 in stable, MySQL 5.6 in unstable and testing. No wait, old stable has MySQL 5.5, and we have a MySQL connector, MySQL proxy, and they have Percona extra backup. So mostly the situation is pretty stable and good, but we have all kinds of annoying stuff like, for example, the builds are not reproducible and there are some architectures we have build failures and so on. And the change that's happening now in this release cycle is that the release team said that they want to have MariaDB as the default. And there has not been any kinds of facilities before to define a default, so we are introducing now new meta packages. And this is how the plan looks like and maybe if you, Robbie, are listening in, you can comment if this is the latest plan or have you done any updates in the recent hour or so. So this is very much work in progress and it's fully open to discussion and contributions if you want to say something. So the idea is to have a new source package called MySQL defaults. Robbie is giving thumbs up, great. And that source package is going to produce a few meta packages and all packages that previously depended directly on MySQL or later on MariaDB should in future depend on these meta packages. And these meta packages then point to the version which the release team decides is the default at some time. So if you have a normal runtime dependency, you would write something like this. This scheme with virtual MySQL server already exists. We are going to keep it at the moment. And if you have build depends, then you should change it to build depend on this meta package, which then does some tricks and uses the LibMySQL client 18 from MariaDB at the moment. And then in future it might use another version. And I have typos here. Liby, yeah. So I guess we could stop here for a while. I have a bit more of presentation, but this is a buff. So let's take a pause here and listen into your comments about this. How many of you have a comment? Where should I switch to now? Yeah, so if you have a new installation, if you have a new installation and you write, for example, up get install WordPress and WordPress depends on this and you don't have any MySQL variant installed, then it will take the first option and it will pull in MariaDB at the moment. And if you have installed manually something else which provides this, then that will stay and it will not pull in the default. And if you have an old server which has some database installed, then actually depending on what packages you have that depend on that database, you get a different kind of result. And to the question how stable it is, well, I can't really say I know that I am maintaining MariaDB packages in a very stable fashion and for a long time. So it's basically the release team who should comment on how often they want to change this default, but probably not very often. It was mentioned that MariaDB is more compatible than MySQL itself. So the question is if something happens to MariaDB, can we go back to MySQL? Yeah, so the idea with this is that the release team specifically wanted to have a facility so that there's one point where you can turn the knob and change the default instead of doing a mass bug filing on 200 packages. You just have one meta package and you need to upload a new version of it and then the default changes. And that facility exists for the reason that the release team can make these kinds of decisions and they want to be able to make these kinds of decisions in case there is something that suddenly comes up and you need to change the default. So I think that the dependency resolve mechanism in Debian should not change your currently installed packages if we follow the scheme because all the providers are at the second level. And if it's already installed on your system and your dependency is already okay, then it doesn't need to install anything new. So it will not install the default if the other one is already there. Yeah, right. So your question was about stability and backwards compatibility. Yeah, so I need to upgrade my server so I'm wondering which version should I use now. So should I stay with MySQL, which is already working fine or MariaDB 5.5, which is working fine or go to 10.0.2? Well, I think that you should at some point obviously you need to upgrade from 5.5 versions to something newer and since I represent MariaDB, I think it's better. But of course admins can make their decisions if they feel that there's some specific feature in MySQL 5.6 or 5.7 that they want to use and so on. But if you don't care, then you just install the default. I think he was asking really you to what you recommend. Yeah, well I recommend MariaDB, but you know that's kind of obvious. And what Sergei was saying about compatibility and the stability, your question was about stability. So there was a fork at the 5.5 level and at that point MariaDB is 100% ABI compatible with MySQL. Now it's maybe 99%, but it's not like applications use 100% of the features that mostly it's just the basic stuff. And I think that's probably gonna be compatible forever. And I know that at least in MariaDB development we test that upgrades from earlier versions of MariaDB work well and that upgrades from MySQL work well. So to my knowledge at least that path should work and then you have to ask Oracle people how much they want to support backwards compatibility. There has at least been, Paul had some issues in Ubuntu when they introduced MySQL 5.7 and stuff broke because it wasn't properly backwards compatible with 5.6. So that this is kind of the intent, but then of course it's software and it has bugs and people can't know all the features that's everywhere. So we can't maybe promise anything, but I think it's good that we have this facility so that it's possible to easily change and fix stuff if it starts breaking. So one of my packages built depend on MySQL. So I understand that currently that should not be an issue, either one. What do you think that, yeah, so it's future looking, but what do you think? Yeah, so if you build depend then you should update to this and this will use the MariaDB provided LibMySQL client 18. And it doesn't matter because the client library will work with either one of the versions when it talks to them. The ABI is compatible and it's close enough. And if you have, for example, the MariaDB Node.js library, which uses asynchronous functions that are only available in MariaDB, then you can't rely on this, then you should specifically build depend on the MariaDB client library version. So that's a corner case, but I think like 99.9% of the software in Debian can just build depend on this and everything will work with both client library versions. So it's a fork of the same base and they have different feature sets in new features and they are not kind of super sets of each other. They are going to different directions, but the base is the same and pretty much all the apps use the base. Well, luckily my package hasn't changed in a while, so I'm pretty sure the reports just work. But at some point there will probably be something breaking, but that's not perhaps specific to the MariaDB fork. That's also something that happens naturally when there are new versions of software, their API gets new API versions and the surname bumps up and so on. So we are prepared for those cases, I think. Any other questions? So how many are maintaining a package that currently depends on MySQL server or virtual MySQL server? Pearl guys at least have one package. Yeah. You know, don't server I guess on the library. I mean, well, DVD MySQL. Yeah, that one. It depends on live MySQL client and in future it should depend on this. There's multiple packages recommending of course the server, but because it's a remote database, they typically don't depend on them. Yeah, so this is common for MySQL and MariaDB. MariaDB, and as I said, this is the team and the packages they have. Do you want to discuss something related to any of these packages? Do you have any needs or concerns in general related to the state of this? So at the moment we have MariaDB 10 in Jesse and in testing an unstable and we have MySQL 5.5 in old stable and MySQL 5.6. This says it's available in old stable too, which is new to me. Somebody was doing some back porting. It was you. So is there 5.5 in Jesse? Yeah. Do you prepare the 5.6 back port to Jesse? Yeah. And 5.7 is in the works. I will upload it into Debian soon. So then we will have MySQL 5.7 and then MariaDB 10.2 is also in the works and it will be introduced also soon. I also still want to relay some comments from Robbie on the IRC. It was to the question of the compatibility. Robbie said, he said the biggest issue right now is that you can't easily switch from MariaDB to MySQL. So apparently the way to MariaDB is okay, but the other way around not because the DB formats do not carry over. You must manually dump, restore and tweak as necessary. A newer upstream versions of MySQL have been cleaned up, which breaks some compatibility, for example in locking down things in a schema, which made no sense anyways. Primary key columns being runnable, etc. Deprecating LibMySQL client R because MySQL client is now thread safe. This kind of things is what has been breaking compatibility in MySQL 5.7, which I was observing my package breaking in Ubuntu. You also had the example of the parameter which changed logic that it doesn't accept empty values anymore. MySQL 7 has been cleaning up stuff, which means it has broken some stuff that is backwards compatible. But of course nobody, this is normal evolution in software and we are talking about compatibility on different levels. Can you switch back and forth and can you use the same data format on disk or not? And most of the time system administrators who are smart, before they do a disk upgrade, they will make a dump and backup of their database and they will make that in an SQL dump format and so on. And that format is pretty portable and you can take it into new places and so on. So you need to keep in mind that when we are talking about switching back and forth, we are talking about how easy it is or is it difficult. But probably you are not locked in any situation. You can always do a manual dump and transfer the data into a new installation. So how many of you are making backups of your database? Great. What backup techniques do you use? MySQL dump, LVM snapshots, yeah? Are you using this MyLVM backup package to do it? Yeah? Is somebody using Percona extra backup? Yeah, cool. And is somebody using bin logs in a backup fashion? Yeah. I think that's maybe an area which should be improved a little bit because there are... I have a request in DPConfig common as well of making backups an option there. Is there anything from Robbie on IRC or somebody else on IRC? Just a comment on the previous discussion he imagined that fixes needed for 5.7 will still work with MariaDB also. Yeah, right. So this we already discussed and I said if you... We will start by uploading this to experimental and then you can test out in experimental or you can review our plans at the moment in Git and comment them on plan level or you can wait until they are in experimental and then test in experimental and comment them and request changes. So this is the hot thing which we are doing right now. And then for MariaDB which I'm the main maintainer for, I have some easy to-do issues which I have put up in the bug tracker. And this is specifically designed with new contributors in mind that you don't need to learn overly too much about the current state of packaging and dependencies and stuff. These are independent jobs and you can go to this address to see all wish list level items and I have prepended them with to-do. So if any of this looks interesting to you and you could do it easily then please by all means step forward and contribute by helping with them. Do we for example have some system D expert in the room? Because we are still running the traditional init script and we should have a native system D script in Debian. How about do you have any metadata.yml experts here? How about auto package tests? Could somebody want to contribute them? It's actually quite easy to do them because you can look what MySQL packages are doing at the moment. They have auto package testing in Debian and Ubuntu. You could just start by copying that and reviewing it and maybe tweak it a little bit and then it's done. Just before you go on I have a message here from Jason on ISC. He wants to congratulate you and the Debian team and MariaDB team on the effort that you've done with development. So he's saying you're doing great job. Thank you. So these are the easy ones. On a somewhat unrelated note I'll check MySQL packaging and they do not use open as they use YSL. Let's show I just check the dependencies. So I also checked this just before this talk. So here are some more difficult to do items. So reproducible builds are broken and they are broken for different reasons. But at the moment MariaDB was working correctly for a while. But then something broke and it's very difficult to debug what broke because something is introducing a build ID into the TokuDB plugin. And we haven't been able to track down what does it. It has something to do with the Debian debug builds or something with how reproducible builds are done because it doesn't repeat on normal builds on our own machines and so on. So do we have some reproducible build experts who would like to tackle that one. So it's just one minor thing left and after that the builds are again reproducible. But this is just hard to crack. Have you asked about that on the mailing list? No. Would you like to contribute by hanging on IRC or on the mailing list? I would suggest that even go on IRC here at that conference just ask who's around to have a look at it with you. There are plenty here. But I think for the rest of the evening and so I'm tied up to this default package thing building and testing it. So this is kind of a separate issue which doesn't need involvement from me. So it would be really nice if somebody else would investigate and just send a patch when it's done. We're all busy. And I'm happy to add you to the package MySQL team if you want to have direct push access to it repository. You have a question. So my question is really not technical but I was I was wondering about the what Meridibi like the organization is how it's funded. Is it a non profit thing or yeah. So there's Meridibi Corporation which for example Sergei works for and you can ask more about the corporation from Sergei. It has I think something like a hundred employees and it does all kinds of commercial work and support services and commercial versions and so on. And I myself and iron work for Meridibi Foundation which is non profit and we are funded as I in my previous talk actually presented a little bit about it. So we are funded by by multiple. We have individuals who donate to us and then we have corporations who donate to us for example booking.com and Visma. And Meridibi Corporation is one of the sponsors but it's the amount that they give is only 20 percent of the entire budget. So we are financially independent and the foundation has all the needed assets. So if something happens to the corporation we can continue the open source project. Our our task is to take care of the open source project and make sure that this software is around for 20 30 40 years or how long you have databases running. Another question on ISE from Jayton. Is it necessary to be a DB developer to help in the to do stuff? No absolutely not. So the only magic power you get as a DB and developer is that you can do uploads and stuff. But but anybody who wants to participate can just start cracking the problem. And for example we have the Git repository so you can you can just clone it and make changes and then submit your patch. And if you submit multiple patches then I can add you to the team so you have direct push access to the repository. There's also a mirror on the on GitHub. So if you want to use GitHub workflow with forks and pull request there that's also possible. And so here's here's information and there's a sub page teams slash my skill slash Meridibi if you want to take a look. And I'm happy to happy to help you especially if you aspire to be a debut maintainer debut developer someday. So I'm happy to volunteer as your sponsor in that case. All right and then then the second tough question. So did we have any security team members here? No so at the moment both my SQL and Meridibi use are built with the bundled. Yassel SSL library instead of open SSL and so the ideal perhaps would be to use the system provided open SSL. So if there's a hard bleed or something like that then one single security upload into Debian will fix the system open SSL. And then the security team can just retrigger a build and or not even retrigger a build. It's just enough to start the demon and it will load a new library and so on. So for security point of view it would be nice to have a system provided SSL library. And some something that open SSL is the best variant. So I don't know but at least there's this licensing question that at the moment stops us from using open SSL. So this is a typical open SSL exception to the GPL. So one way would be for Oracle and then Meridibi to add the exception so the license which I'm guessing is a hard thing to do. But open SSL upstream has expressed that they are switching the Apache license. Instead of the open SSL license so eventually this will be fixed not just for Meridibi but across the archive. It will take some time. They're tracking down all contributors and licensing and all that. They have probably loved about it. There are also alternative SSL versions like CSL which is now called Wolf SSL and Libre SSL and so on. But these alternatives have the problem that they are not maybe mature enough. So if we wait enough we will by time will solve this so that either open SSL will become Apache licensed or some of the competing libraries will become mature enough. We can start using them. GNUT LS is also a good option. It's GPL so it wouldn't be a conflict and it is mature enough. Which one? GNUT LS. So is that separate from Libre SSL? Libre SSL is an open SSL fork. Okay. No I just said that Libre SSL is basically the same as open SSL same license. Slightly cleaned up code. License wise GNUT LS is possible and NSS may be possible. And maybe CSL if it will have another functionality. So time will help fixing this problem but is there something we can do right now? I wonder. How old are the comments on this bug? I guess Debian doesn't really have a really authoritative person to actually comment on that. So typically this goes via the legal mail list. So it's more of a consensus thing right? So yeah. Well the legal mailing list is a bit of a talking shop and some of the people on it talk a lot. And they are not related to the FTP masters who actually accept things. So there's a complete disconnect there I would say. The talking people on the legal list have driven away quite a lot of the same people. So I think it's a real shame we've got that list. Because it confuses outsiders who aren't aware that Debian legal is just a place where people chat. So go to FTP master. Is there somebody who has deeper knowledge about this open SSL exception thing and what's the legal status about it in general? And do we need to care about it or would it be okay to ignore it and so on? Probably not. Do you have something else you want to discuss? It's a both session. I don't have any more questions here. I have a question. So the MariaDB and MySQL maintenance scripts right now create a Debian sys main user and run some things over the course of installation and upgrades such as upgrading schemas and stuff like that. So that is clearly not suitable for larger installations like multiple slaves that you want to control the data and use schema. So I'm wondering if there's, have you thought about to saving that in... This was my previous talk. This solves the problem. Okay, I missed that. So we get rid of passwords altogether and the maintenance user is a legacy thing. So there's a main, let's show it here. Yeah, so you are talking about this Debian sys main user and password. So there's a plain text password in the ETC directory and the only thing that's protecting it is the Unix file permission. And this user has root level access into the database in MySQL and MariaDB. So in MariaDB we have started using Unix socket identification. So we get rid of this password altogether and root can access the database. The system linux root user can access the database and run the MySQL upgrade scripts and stop it and start it and so on. Right, but I'm talking about not running the upgrade scripts at all. In some cases you don't want an upgrade on a system to run upgrade scripts. Because you're doing that externally you have more complicated environments. I don't know if the binary is upgrade then you kind of have to run the upgrade on the data, on disk data. There were a few things that haven't looked in a while. There were a few things that needed to be avoided. There were some queries that were run by the mention of scripts that didn't play well with the application. But I don't remember the details. In most cases it's recommended but it's really strictly required. So it makes sense to run without if you can and if it works for you. If it works for you then it's not a requirement. Do you remember what was the exact problem? What happened? This solved the password thing and then in general the upgrade should be safe and work. That's kind of an upstream problem I think. So I have a master slave set up and when I upgrade packages there then there are some things running during the upgrade, updating some internal databases. And that often causes a problem with the replication. So the replication errors because on the master the database has already been upgraded and then the same thing happens again on the slave or the other way around. So this is kind of related how to master slave replication works and how it's compatible if the binary is on disk format changes. So I think you should maybe when you notice the exact problem and file a bug about it. I'm not sure there's any categorical solution to avoid it. In general it should work fine if you have a Galera cluster or a master slave set up that you don't need to synchronize too much the upgrades. They can have slightly different binary versions, minor versions as long as the API version is the same. Yeah, I'm using the same versions but I think it's generally recommended to first upgrade the slaves and then upgrade the master. Okay, say it again probably as a reply to this. When did you have this issue? So when did you have it last time? Approximately like this year, last year, I don't know. Of course I just found in the bug database, maybe we have great breaks replication and the description of the bug starts from Debian starts script for MariaDB in Debian slash edition and so on and it was fixed and closed in 2013. So three years ago it was closed in our repository maybe took a while until it got to Debian packages but yeah for the bug it was fixed three years ago. It's MySQL version 5.5 that I'm using so it's stable maybe that's fixed now. Maybe it wasn't fixed in MySQL packages I don't know about that but we had it when we fixed it three years ago. You're welcome. So do you have any opinions on back porting? Should we, is there something that's justified important enough and justified so that we should back port it in back ports or in a point release into a stable? Do we need something in Jesse that's not there at the moment? So I think I'm happy with the existence of MySQL 5.6 in back ports. I'm not super enthusiastic about being the one, the only person that back ports it. So if somebody else cares that would be nice. Maybe we can talk about that separately as part of the team. Yeah so back port is kind of easy because we don't force anybody but I was talking about do we need some updates to the stable releases. At the moment purely security we do only purely security releases into stable and we haven't done any bug fixing or things like that into the stable releases. Are you aware of any serious bug that should be back like fixed in a stable release? Do you have a question? Let's check on IRC if Robbie has something or somebody else on the channel. So the remark from Robbie, as I understand it, in MySQL we still need DB and SysMain to run MySQL upgrade again. I think that was said here as well. The problem comes when a user wants to have a different route authentication plan, that's not a Unix socket. There's always the option to use MySQL server core and take care of managing the database manually for larger installations example clusters. MySQL server core provides the binaries only now automated maintenance. So if you don't want to run the updates apparently there's a package available. There is both client core and server core packages in MySQL and MariaDB, which you can use for these kind of use cases. And also this socket authentication is default now and implemented only in MariaDB. It's not in MySQL yet, but I think MySQL is probably going to have it too soon. So MySQL still has the DB and SysMain user. And this also applies only for new installs. If you have an existing user database and everything then those passwords will continue to stay there. Time's up. Thank you for participating. I hope to see some activities.


All right, MC on my right hand side, from Chef City to Steel City, representing Scum Farm, it's first battle in Don't Flop, make some noise for A-K. Make sure you check the Scum Farm site for all that other shit, and yeah, make sure you check LOTM6 as well, man, check his class with video on that.  Clash, I can't wait for this, A-K versus XP, like I said, leave all your opinions in the comments. Shout out to all the fans coming through the support, and yeah, XP won the flip, he chose A-K to go first, to end my brother, K, spins the beat, it's round number one, first verse on A-K, let's go.    Aye, I told man that he can't walk me looking like some toothic Make stop trying to make grand music So ask him, make spotty vote, he do keep Tell your girl, stop going on toothic Ask man, pass it about like me and it Said he was a bad boy, but I never freed it Shout, you're about to mutate Yo, act, why is your girlfriend on Prozac? Why so mad for you when you so wack? Why so cold sitting in your own gas? Why's it no electric? Why's it no gas? Aye, I told man that he can't walk me looking like some toothic Fam, stop trying to make grand music Go ask your boys, why they vote he do keep Tell your girl, stop going on toothic Ask man, pass it about like me and it Said he was a bad boy, but I never freed it Shout, you're about to mutate Yo, act, why is your girlfriend on Prozac? Why so mad for you when you so wack? Why so cold sitting in your own gas? Why's it no electric? Why's it no gas?      Nah there, no man You do what he did, put it in there, no man Now what?  You wanna do some in there, nah there, no man So in there, man, you know One car, I'm out, don't flop Yeah, yeah, yeah, alright then Yeah, I have the deal Fuck it, don't flop Yeah, yeah, yeah We're getting seasick, it's me and Finn sleeping Even the wise eyes are keep tying, yeah Cause I'm boy locked up on the dying Like never been a boy that robin There's 20 back challenges in my other one And just sell a gangsta, but I'm just an attack on the I know that I'm in the next caliber Next caliber doing any reject Yeah, follow that, let me try that


Hello everybody. I hope you all can hear me. This is Shweta and I am dialing in from India so it's quite early here. But I'm here from Semantic Climate to talk about how we've been building climate knowledge explorer using Wikimedia tools. A little bit about me. I am a volunteer developer and program manager at Semantic Climate and I've been working with Semantic Climate for close to three years now. So, at Semantic Climate what we've been doing is we've been building climate knowledge explorer liberating climate-related facts from scientific literature. So in the next 15 minutes I want to talk about what we do at Semantic Climate, how we integrate Wikimedia tools like Wikidata and Wikibase in our pipeline and how we work as an open science project. And I'd also like to hint a little bit about our future events. For that, let's get started. So the information to save the world from climate crisis is already available in these amazing reports that the UN puts out.  For example, they've got working group one, which talks about physical effects of climate change on Earth, working group two, that talks about effective climate change on natural and human systems. WTT-3 is on mitigation. And similarly, there are three other sets of special reports. One's on climate change in land, one's on global warming. And finally, we also have a special report on ocean and chai spear. And very recently, IPCC put out what's called synthesis report, which basically synthesized all the key findings from these three reports, WG1, WG2, WG3, and the special reports. And I think the UN Secretary General called synthesis report the surviving guide for humanity. But the problem is that all of this is a lot of information. These reports are really huge. Like, you know, there are seven reports that've got multiple chapters. It's more than 15 pages long. It's got so many terms. And it's written in a technical and jargon-filled language that you and I may not be able to immediately understand. So the climate information is actually rendered inaccessible to most of us. And worse, it's only available as PDFs for the most part. So how do we get this information from these knocked up PDFs and make these climate facts available to everybody? So that's where semantic climate comes into picture. With the help of Wikimedia, semantic climate is making climate information more accessible. So in the next set of slides, I'm going to describe the pipeline of our project. So here it goes. So like I said, we have different sets of climate reports, usually available as PDFs. So our tool called ByAmy converts these PDFs into HTML. Now, HTML is much more easier to work with, at least for the software and also for humans. So once we have that HTML, and it takes a lot of effort to get there, we can do a lot of interesting things. So I, along with some of my team members, and Daniel Meachan, I don't know if he's here, but he's here. Hello. So we have developed a tool called Doc Analysis that extract information, textual information, with the help of what we call dictionaries. Now, I'll talk about dictionaries in the subsequent slides, but dictionaries are basically set of terms that we think are important. So it could be all the abbreviations that I mentioned in these climate reports, or it could be all the climate-related terms of the glossary that IPCC gives us. So we can use that to search the literature, or to search the paragraphs in these IPCC reports to index them, and also to get occurrences. For example, if you want to, you know, find out which all paragraphs mention a geographical area that you're interested in, and a specific climate term, our tools can easily do that for you.  So before I go ahead and talk about what we do with these climate facts, I just want to take a quick detour to explain about dictionaries. So dictionaries, like I said, are a set of terms with unique Wikidata identifiers. So let's take greenhouse gas, for example, it's got a QID. I mean, I'm sure we all know what Wikidata is, so I'm not going to talk more about it. And more importantly, Wikidata gives us information about the specific term in different languages, right? And our dictionary, since it's linked to Wikidata, also has information about specific term in different languages. And we use these data to annotate the paragraphs. And therefore, when we do the linking, we can actually display what a specific jargon term means in a language that the reader is comfortable with. So this is an example of the annotated paragraphs. As you can see, the term CCS, I don't know if you can see it. The term CCS here is hyperlinked. And if you click on it, it will take you to Wikidata. And if you do not know what CCS is, you can just immediately understand what it means is carbon capture and storage, the process of capturing and storing waste carbon dioxide, right? So this was one of the two cases of being able to link into Wikidata and cementifying the paragraphs from IPCC reports. The next thing that I also briefly touched upon when I spoke about the pipeline is when we have these HTML, we can use both supervised and unsupervised methods to extract key phrases and correlations and co-occurrences like I described in the previous slide. So with all this useful information, what are we doing? And like I said, semantic climate is cementifying these climate facts, so we have these climate facts. So what do we do with it? That's where Wikibase comes into picture. Back in April this year, Egon and Lars Willekargen, along with Peter Murray-Rast, who is one of the co-founders of semantic climate, sat together to set up a Wikibase instance for us. And I'm sure you all have had a chance to learn more about Wikibase in yesterday's talks and so on. So what we do is that we take these paragraphs, which we call statements or climate facts, and put them in our Wikibase instance. So for example, let's say 2.2.2 c, the paragraph, and it's got its own QID. And in the statements we tell, okay, this is an instance of a section. It's a part of this bigger subsection, and it mentions these keywords and, you know, it also is talking about these specific geographical location and so on and so forth. And these climate facts, thanks to IPCC, have confidence level that we can be making use of and, you know, we can be documenting that in this item page, for example. So with all this information curated on this open database, we could be doing a lot of interesting things. So through this, what we can do is you could explore the climate facts in however way you want. Essentially, this becomes your climate knowledge explorer. Let's say, for example, you're interested in knowing which all paragraphs from IPCC reports mention a specific geographical area that you're interested in. You can write a quick sparkle query to do that once we have all the information in our Wikibase. And second, let's say you're interested in building a knowledge graph of all of the based on which paragraph references which other paragraph from the IPCC reports and you can do that again by writing a sparkle query. In other words, what we are doing is transforming the way anybody would read IPCC reports. And this can help them build newer connections that otherwise wouldn't have been possible with just simple PDF reports. Right. So this is what we've been doing with semantic climate. Now I would like to talk a bit more about what we, how we work. So we have been running a lot of hackathons and it's driven by all these amazing volunteers are, you know, our project is mainly run by volunteers. So in the past, we've been part of hackathon PRJ, which we've won this happened in the University of Geneva. This happened at the University of Geneva. And after this, we ran our own hackathon in Delhi. This was fully online this September. And very recently, we ran our in-person hackathon in Delhi with about 30 people, you know, trying out our Wikibase instance, trying out our tools and so on and so forth. We have more pictures in the subsequent slides. Finally, we were also part of Fiske recently, where we had about 10 people, I guess, trying out our tools and testing them. So this was in, this was during hackathon PRJ, where we had people run our Google collab notebooks that took them through the entire pipeline. And here we also had people who tried this out and translated the documentation into different languages. And this was truly learning by do. This was our Delhi event, September. And finally, this was our climate knowledge hunt in May 2023, where we had people, we had different breakout rooms and people tried running our Wikibase, tried, you know, writing sparkle queries, you know, you start tools, talk analysis by Amy, by get papers and so on. And these hackathons also produced a lot of volunteers for us. So for example, we have Shivani and Yasin, who were part of our climate knowledge hunt in May. We're now working with us and working on specific chapters. Shivani, for example, works closely in Ladakh, and she is interested in high-mountain structure. Similarly, Yasin works on food security. And all these people have been making YouTube videos to explain what their chapters mean. And they have been able to understand more about these chapters through both manual reading and with the help of our tools. So do check them out. I've put the link in the slide, and I'll share the slide soon as well. So what's next? So we would love to advance our technology and continue building the community. So we are part of many other events in the future as well. We have, we are part of this workshop code data is organizing in September 2023 where people show will get to. Similarly, we're being part of our camp open science and Berlin. I think this is being hosted by Wikimedia, Deutschland. And finally, I'll be at UN data on November this year. This is happening in Geneva and we would love to, you know, explore, continue building our climate knowledge explorer with the help of people we meet there as well. And maybe we could be running more hackathons with Wikimedia in the future. So yeah, please do check out our website. We are very active on our website. You can check out more about our events, test our tools, try out a Wikibase instance. And yeah, so please do come join us in building this climate knowledge explorer to make climate knowledge accessible to anybody.  We follow what's called open notebook philosophy. So all of what we do is put out online as soon as it's done, or you could be a part of our community process. We could engage us through various events that we are part of, or, you know, just test our tools, improve documentation, whatever, and we would love to have you on board. So this is the larger team. I would like to thank each and everybody who are those pictures are put up here and people who are some, I mean, we have had over 50 people work with us over the past three years. And I have not been able to include all of them here. I specifically like to thank Peter Murray Rust and Gita Anjali Yadav who are the co-founders of similar. Yeah, but that I'd like to thank Wikimania for giving me this opportunity. Here are some of the useful links and I'll share the slides. Thank you so much for your time Shweta. We actually have a question for you from event yay. The question is how do you have any ideas about how to enrich wiki data based on the information you've provided today? Thank you. Yes, we've done this before. Let me go back. So with the tool called Doc Analysis, what we were able to do is use semi supervised searching to extract information from the scientific literature. So we also work with scientific literature that that's available as XMN and what we did with Doc Analysis along with this was the work that I did with Daniel Nietzsche. Is that we were able to get information about the ethics that were mentioned in the scientific literature using the wiki data driven dictionary that we had created for organizations. And so for all the papers that we were able to analyze, we got the organization that had given ethics consent for that specific study.  I mean, as an item as well. So what we were able to do is then add information about the ethics for these papers. And we could do the same with let's say all the chemicals that are mentioned in a paper, we could extract those from our pipeline and put it back into wiki data. Or so that's the example we also have to that analyzes the, you know, gets the abbreviations from the reports automatically, there's a Python package with let's do that. And we could be thinking about putting in all the abbreviations that we extract from these IPCC reports into wiki data if they don't already exist. Yes, we have already been able to enhance enrich wiki data and we would love to continue. I hope that answers the question. I believe it did. Yeah, thank you so much. And with that, we're going to head to the break. Thank you for your presentation. Thank you so much.


This episode brought to you by Virtual Shield VPN. If you're like me and you value your privacy from the government and big tech you need Virtual Shield VPN. Check out the links in the description or the pinned comment. Remember before Donald Trump won the election and the Democrat Party State Media along with Hillary Clinton insisted that if he didn't accept election results it would be an attack on democracy. Well, Trump won and as it turns out they were the one who questioned election results and they were the ones who attacked democracy. Democracy hacked? Did Russia want Trump in the White House? Did Russian hacking help Donald Trump win? The CIA says the Kremlin tried to swing the election to Donald Trump. There's no disagreement about Russia hacking the election. The intelligence community, the FBI, Democrats and Republicans believe that Russia hacked the election. The CIA has concluded the Russians intervene to help elect Donald Trump. That is where they are in this issue now. Russia was not only interfering but was trying to deliver this election to Donald Trump. There's very real skepticism about how legitimate was this election. It wasn't simply that Russia got engaged or involved in hacking the election but did so to favor Trump. I think this is a constitutional crisis. I mean, was the president legitimately elected? What it suggests potentially is that the election was in some sense illegitimate. That Trump in any way is an illegitimate president because of the Russian involvement. I mean, the Electoral College before the 19th has got to know whether the Russians had an effect. The Electoral College should behave as it was designed to behave and as it was explained by Alexander Hamilton in the Federalist Papers. It should deny him an Electoral College victory. I'd like to see the evidence because if the evidence is there, I don't see any other way than to vote again. I mean, as an American citizen.  They're just setting it up so that anytime a Republican wins, they could just say the Russians did it. And when a Democrat wins, they can give the all clear. Conservative media is fueling President Trump's baseless claims of widespread election fraud. The nation's top federal election infrastructure agency says this year's election was, quote, the most secure in history. This year, experts are more confident that I think it is safe to say this is the most secure election we've ever held in the United States. Brian, it's just the alternate universe writ large there. Two parallel Americas. It cannot be more stark. And there's no one in charge, no one in charge except President Trump setting the tone and then others falling in line. There's no one at Fox News that is saying this is crazy, this is irresponsible, this is dangerous. Because really, can we trust either man? No, we can't. Trump simply cannot be trusted. At the same time, Trump opponents will speculate that he's really a Russian agent. Having a meeting with his handler, betraying America. In a statement, the cybersecurity and infrastructure security agency said, quote, There is no evidence any voting system deleted or lost votes, changed votes, or was in any way compromised. It's not a surprise, but still, years into this presidency, I find it shockingly disappointing that he still would continue to erode faith that the American people have in institutions. What is going on right now is a clean and fair election and there is no evidence to the contrary. The only thing he didn't do was pull off his wig and reveal that he's been Vlad Putin all along. It was a litany of lies, threats, just a despicable and incoherent attack on democracy in the United States. This isn't just a case of hurt feelings or wounded egos. This is the beating heart of Trumpism, the paranoid authoritarian belief that your political opponents are illegitimate. We have this very real skepticism about how legitimate was this election. I think this is a constitutional crisis. I mean, was the president legitimately elected? What it suggests potentially is that the election was in some sense illegitimate. That Trump in any way is an illegitimate president because of the Russian involvement. No, I'm not psychic. These people and their tactics are just very obvious and very predictable. That's all for this one. Please hit that like button, share and subscribe. And if you'd like to support this channel, you can do so using one of the links in the description or the pinned comment. Thanks for watching. Keep coming back.


What is going on everybody, Astos here. Welcome back to another video. So in this video, we're going to be doing an overall market update, taking a look at the Dow Jones, the S&P 500 and the NASDAQ. We're going to be doing a brief trading update today. What did I end up doing on the 8th of May in 2019? Today, we're going to be talking about that in today's video, as well as my mindset and my plan heading on for the rest of this week and heading into the rest of this month in May with a couple of stocks and ETFs that I'm personally watching. So for everybody out there, before we do get into this, for everybody out there that finds value in these videos, you enjoy the content and you want to be connected with our community, the StriveSmart community on a further basis, feel free to go down below and hit that like button. It really supports me and I also have two links in the description box for you, one of them being the Discord Group Chat, the StriveSmart Discord Group Chat and the other one being the StriveSmart Facebook Group. Feel free to join both of those communities, very solid communities. We're talking day-to-day about stocks, investing, trading, news, strategies, stuff like that. You guys, if you're not already in there, you want to be there, I guarantee you'll find value. So without further ado, let's talk about what ended up happening today. You saw in the title of the video, is this or was this move that we saw today a bull trap? We're going to be talking, do I think, is this a bull trap? So before we get into that, let's just go over a quick rundown what ended up happening today. So the SPX, the S&P 500, the 500 largest publicly United States traded companies ended up closing the day down about $4.63 down about 0.16%. The Dow Jones Industrial Average ended up closing the day up very minimally, very minimal green day up about $2.24 here, up literally 0.01%. Pretty much nothing in terms of green, but it's still technically a green day for the Dow Jones. The NASDAQ, here we can see it's currently down about $8 down about 0.1%, but this is the future. If we're going over to the one day, one minute, so we can see exactly where we ended up closing at about 4 p.m., we can see this big sell-off towards the close of the market. Ended up closing about four points lower from where we are now, so roughly about a $12 red day for the NQ, also known as the NASDAQ. So now that we got a quick little rundown, let's talk about some technicals here and why I personally think today was a bull trap. And for those of you guys that don't know what a bull trap is, it's pretty much in very technical or very basic terms here. It's pretty much when a stock kind of has or an index, an ETF, a future, it kind of has a false breakout where we're kind of breaking out of, let's say, resistance levels. In this case, you know, breaking out of the 180SMA, these different SMA resistance levels where the pattern is kind of telling us, okay, maybe we're reversing to the upside here. It kind of brings in some bulls pushing up the prices, you know, pushing up the price of the index, the stock, or, you know, the ETF stuff like that. And then all of a sudden we see a big sell-off kind of, you know, leaving the bulls in the dust. So they get in, they try and go long, right? Long meaning they want to hold a stock and index whatever for a couple of days, a couple of months, whatever, and then the trend reverses rapidly and then they kind of get stuck with a little loss there. That's kind of what a bull trap is. So do I personally think that is what's happening today? That's what happened today? I kind of do think that based off these different time frames that we're going to show you, that I'm going to show you here on this video, so we can see, you know, for the whole day pretty much, we were uptrending above the 180SMA, above the 50SMA here for the SPX on the intraday chart. And then all of a sudden, guys, you know, once we almost hit $2,900 again, which just happens to be the resistance from earlier in the day, we ended up tanking nearly 20 points in the S&P literally in the last 30 minutes of today's trading session. Take a look from 2896 all the way down to about 2878. So that's about an 18-point drop roughly, you know, roughly almost a 20-point drop there. And if we're going over here to some other time frames, we can see with this drop, guys, you know, we actually got rejected by a 180 simple moving average. And this kind of shows us the bull trap a little bit better here, right? Take a look over the past couple of days, really just from yesterday, the 180SMA or the 50SMA rather was acting as a resistance, right? We ended up getting rejected, sold off, rejected. And we kind of got rejected this morning by that same resistance level as we can see now, right? We almost sold off, but we bounced for a higher low from where we ended up getting to the lowest point yesterday, which was kind of the start of the reversal pattern, right? Notice the low here at 2862, higher low at about 2874 and from there, you know, we slowly started to make higher, highest, higher lows and reversing out of their resistance. And this is in my opinion where the bull trap started to form, right? We started to hold those levels as supports in terms of the moving averages here rather than resistances like yesterday. And this kind of brought in the bulls for pretty much the whole day, right? And then once we got rejected aggressively 30 minutes with 30 minutes left in the market, that's when the sell-off started to kick in, kind of trapping those bulls, right? And we can see, you know, we got rejected by the 180SMA resistance again. Like I said, that's pretty much been a resistance here over the past couple of days. And this leads me to believe on a technical basis here and this is kind of contingent on whether Trump tweets something positive, negative, whatever, but this kind of leads me to believe that we might sell off even further tomorrow based on this aggressive sell-off that we saw. And of course, this is mostly going to, well, we'll understand, you know, where the trend is heading tomorrow morning, right? When we see the futures, right? Pre-market futures, large caps. How are they moving?  Yada, yada, yada, are we going to pop back up? Stuff like that, right? And if we go over here to the ES, which is the mini S&P future, let's see, you know, how we've been moving. So since we did tank, we closed. It seems like we have been down trending in the after hours as well. So hopping over here to the Dow Jones, very similar, right? We were trending up, sold off very aggressively towards the end of the market here, hopping back over to the 184-hour chart. In yesterday's video, we were talking about how the Dow was maintaining the 180 S&P support on a longer-term chart. That was a good sign that the trend was kind of still intact, right? This is a higher low from the previous. That's pretty solid, right? But the fact that we saw a rejection here on the five-day, five-minute, just like the SPX, that kind of brings some warning signs to me, right? Are we going to sell off tomorrow? I think it's very possible, based off of what we're seeing here on these technicals. So the Dow Jones on the smaller-term chart, there's not much difference to the SPX. And the main key support that we need to watch is this 180 S&P on the longer-term chart. If we break that, just like we talked about in yesterday's video, we might be headed to $25,500 for the Dow Jones, which is the next support. So the NQ, this is one that's very similar to the Dow Jones in terms of its technicals on the longer-term chart. We can see NQ currently at the 184-hour chart, 180 S&P resistance here, this yellow line that you are seeing. We're kind of breaking below it here after market hours, as well, since we are trending down even further. And with the big tank that we saw, again, towards the latter half of the market, really the last 30 minutes, this NQ future here in the index really fell down pretty aggressively, right? And if we go back over here to the five-day, five-minute, we can kind of see a similar pattern where we're still under-moving average resistance levels right now. We are still making lower highs. We're in the process of potentially making a lower low. Let's say we have an aggressive red day tomorrow. You know, the next spot for the downtrend to continue for the lower low to really form, the next spot we're looking for it to go under is $75.81. So keep an eye if it does some kind of move like that tomorrow. If this trend, the one that we're seeing right now, really keeps its form, keeps intact, and heads into tomorrow. So there's honestly not much more to talk about, guys. In my opinion, you know, again, this was kind of a bull trap. We saw the big sell-off towards the end of the market, right? This kind of confirms to me that it was a bull trap. Let me know down below what you guys think about this. And let's say we didn't really get that big sell-off towards the end of the market. Let's say we ended up breaking those levels of resistance at the 180S who made towards the end of the market. At that point, you know, I wouldn't really be 100% set on it being a bull trap, right? Because at that point, let's say we ended up closing strong. Let's say we ended up doing something like that, maybe cracking above 2,900. At that point, it could be a bull trap, but we weren't or it wouldn't have been 100% confirmed of it being a bull trap, right? So just keep an eye on those differences there, right? The fact that we got rejected, that kind of confirms that it was a bull trap today. And again, let me know down below what you guys think about this. Do you think the markets are going to continue to sell off? That was pretty much the purpose of this video, right? Really going over, is it a bull trap? Is it not more selling? What trend am I personally seeing? You know, that's what I honestly did. So in terms or what I thought rather, so in terms of my trading today, guys, I'm going to be honest, I didn't really take any positions. I actually didn't take any positions today, but I did end up closing out my Facebook position at a minimal loss here. And let me explain why I ended up doing this. So I ended up closing my Google position yesterday, right? Very minimal loss there. Really nothing crazy of a loss at all. And I ended up closing my Facebook position today for kind of the same reason as I closed my Google position. I kind of want this whole trade deal drama, the short-term drama that we got to really, how can I say this? Fert to blow over, to be quite honest with you. Once it blows over, if it blows over, that is when I'm looking to get into some more swing trade positions. But with it still going on, right, they're meeting on Friday. I think they're actually meeting on Thursday as well. You know, this can definitely push the market down a bit further, which would in turn, you know, definitely in my opinion, drop Facebook because, again, it's a large cap stock, right? It's in the hundreds of billions of dollars. That is kind of, you know, kind of inevitable, right? When the markets drop and if they drop aggressively, Facebook is going to follow. So I cut out a Facebook just plain and safe here, guys, to be completely honest. I kind of want to have cash on the sidelines for potential big move on TVIX tomorrow if the markets do end up selling off like I think there is a solid chance for them to do. And just quite honest, I just want to play it safe, right? So one that I'm actually still in, which is more of a defensive stock, I think, you know, it fends better in terms of, you know, times where we're selling off in the market is proctor and gamble, right? And this one, don't get me wrong, it's kind of like in terms of the pattern here, it did sell off, right? It's not immune to drops, but it's better in my opinion than holding Facebook through a time period where we're pulling back. And that stock is proctor and gamble, right? I'm minimally green on this one. This is one that I was in from the earnings report day that it had a couple of trading days ago. And I feel comfortable holding on to this one as of right now as a swing trade, right? So will that change? Maybe, maybe not. I'll let you guys know, of course, in the trading update videos, but again, as of now, PG, that's all I'm holding in terms of swing trading and I didn't really do anything in terms of my day trading today, right? Because I didn't honestly want to get caught up in a bull trap, right? I kind of expected it from the morning we were talking about it in the group chat and that's just my thinking, right? Sometimes, like I mentioned a bunch on this channel, no trade at all is the best trade, meaning you not risking your money on a potential funky day is kind of the best because you're not going to lose money. You're guaranteed not to lose money, but you're also guaranteed not to make money, right? If you're just sitting in cash. So today, I kind of made that decision and I felt comfortable with it and that's pretty much it, guys. So let me know down below, what did you end up doing? So what am I watching and what my plans are? Pretty much holding cash, like I just said, right? And I'm looking to play TVIX if the market does end up getting rejected at those levels that we just talked about on the major indexes tomorrow. So the S&P, if it's gapping down pre-market if large caps are looking ugly in the morning, I'm looking to trade TVIX as a day trade pretty much in and out for the entire day kind of like I did yesterday. Disney is actually a stock that just reported earnings today. I actually didn't dive into their earnings, but if we look on the live news tab very quickly, I'm sure we'll be able to see what they did end up reporting. And I did actually get a notification from Robinhood that they beat. I think they beat by 2% if I'm not mistaken, right? So let's see if we go over here very quickly. If not, it's no big deal, right? If we can't find it, let me see. Am I just blind, guys? Am I missing it? Do you guys see it? Do you guys see it? Here it is. Walt Disney beats on EPS by one. The estimate was $1.58 for EPS. They came in at 1.61. Sales came in at 12, 14, rather 14,092 versus the 1434. So based on the two key metrics, EPS and revenue, Walt Disney beat on both of these. And I do believe it was 2% of a beat on EPS, which is pretty solid, right? So those numbers, you know, the brief numbers that we just looked at, those are pretty solid, pretty positive for Disney. So keep an eye on this one, right? This one seems like it's been fending strong. It's been holding strong through this turmoil that we've been seeing in the market. And with a positive earnings report, this actually could be a potential play, right? The trend, if we look on the 5-day-5-minute, hasn't really been broken or hasn't really been bothered too much from, excuse me, this market sell-off that we saw, right? We pretty much got all the gains back from yesterday's loss. We got them back today. The stock pumped up on earnings. Keep an eye on this one. It could potentially be a day trade on an earnings, positive earnings play tomorrow. So Disney, TVIX, in terms of, you know, what I'm watching, those are the top two. And honestly, guys, I'm watching a lot of the large caps just in case the markets recover. Let's say we miraculously get news that the trade deal is happening within these next couple of days, right? These are stocks that are most likely going to be very, very helped during that time period. They might go up another 5-10%. They might get back all the gains that they lost. But let's say the tariffs go in place that increase from 10% to 25% goes in place. Who knows how the market will react to that? That might be pretty ugly, right? That might send stocks down even lower. That's what people think. So this is just a time period where I'm sitting back being cautious, mostly cash, not looking to swing trade a bunch of things, mostly day trading right now. And this is kind of like I was a couple of months ago, back in October to December, when that whole 20% market correction occurred. I was very similar in terms of my tactics, my mindset and what I was doing with my money, right? Very, very cautious, mostly day trading, not having capital, too much capital tied up in terms of swing trading just in case the market took a downturn. You know, I was just being very, very cautious. So Disney, TVIX, you might as well just keep an eye on, you know, the big tech stocks like Apple, right? Apple's taken a beating and hit 2.15 nearly. Now it's selling off. It's holding a support at $200. Maybe we can see a bounce back potential day trade here on Apple. Keep an eye on these ones that have gotten beaten down, guys, these large caps, you know, Facebook. Not as bad as, actually might be as bad as Apple, right? We went from 202 down to about 188 today. You know, Amazon, Amazon was at about 1970 a couple of days ago. Now we're seeing a dip, but we're also maintaining the 1910 level of support right now. Maybe we can gap fill back up to 1950. Kind of risky if the markets do sell off. This one's most likely going to sell off, but it never hurts to just keep an eye on it, right? Ticker symbol AMZM. If we're looking at crude oil, I've been getting a bunch of questions on crude oil. This one, guys, it seems like it does not directly follow the market, but it seems like when the overall market is selling off, crude oil is doing the same. You know, it's still pretty much trading below moving average resistances right now, making lower highs, making in the process of making lower lows. We're seeing a bearish cross right here of the 50 SMA below the 180 SMA. That's not looking too hot, right? If we wanted to see a reversal on crude oil, you know, we'd need to see at least a break out of these SMA resistance levels, most likely or mostly, most importantly rather, the 180 SMA at that point, if we slowly start to get back into the 63 level, maybe 6350, that could be a good breakout, maybe a reversal pattern in crude oil. Gold, gold's another one to keep an eye on. This is going to be interesting, right? We're at a resistance right now at the 180 SMA, very similar pattern to crude oil, but when the market sold off aggressively a couple of days ago or yesterday rather, it seemed like gold did very well, right? So if the markets sell off, maybe Tuesday or Thursday rather and Friday, these last two days of the week, let's say we get more bad news, the markets sell off like crazy, right? Gold most likely is going to do good and if we break out of the 180 SMA, JNUG, which is an ETF that tracks gold that goes up whenever gold's going up, this can be a very good play. So keep an eye on that, keep an eye on gold. You know, Tesla, let's just go over Tesla for fun guys. This one has been selling off even more recently.  We got the bad earnings, right? Earnings were terrible.  So Tesla, based on the pattern we're seeing right now, this one could definitely be heading back to the 230s, maybe a lower low, maybe even below 230. Who knows, maybe down to 220-ish dollars, that, you know, general range. This can 100% happen. So that's pretty much it for the video guys. Let me know if you thought today was a bull trap. Let me know what you are watching. Me, again, TVIX and Disney are my top two tomorrow. Positive earnings for Disney that we saw from these brief metrics. This can be a good day trade tomorrow. Watching the large caps to see, are we gonna bounce back? Are we going to have a sell off tomorrow to play TVIX? These are different things than I'm personally doing. So if you enjoyed the video, feel free to go down below and hit that like button. Drop a comment. Let me know what's going on in your life. Subscribe to the channel if you're new. Hit that notification bell so you're notified every time that I do make a video. If you want to stay further connected with me and the community, feel free to follow me on the Strive Smart Instagram. My personal Instagram is down below as well. The Strive Smart Discord group chat, Strive Smart Facebook group. All of those are linked down below if you want to stay further connected.  It means a lot to me. I'll catch you all in the next video. Good luck tomorrow. I hope you all did great today. Peace out.