Diolch yn dda, mae gennym'n reddli, rydw i fe wnaeth hyn ysglwyddiad, Let's go through status, plans, help needed, oh hell yes there is help needed, and if you've got any discussions and ideas, yes please talk to us if you're here or on ISE if you're not, and we'll try and relay questions. Please take notes in goby someone, I will endeavour to send out notes after this, it may take a week or so. So, WN web team, I have commit access but I don't pretend to have any great power or control over the web team. Does anybody else here have anything more? We're still using CVS despite the fact people have been talking for what a decade or so about moving away from it. I would love it if we moved over to Git, there's been discussion about that several times over the years. There's been some pushback in that A, people are scared that it's going to be a big repo and that's going to put people off downloading it and working with it. I don't believe that to be a major problem at all personally, but I'm not in the situation, I'm not one of those people who might be put off clearly. The other thing is that the Git workflow it is claimed may put off some of the more casual contributors. I'm not equally not all that convinced that CVS is a wonderful tool for those people either, but it's difficult to know, I don't tend to talk to these people very often. I hope other people may have more insight. Is the mic on? Yes. Rhonda's done a conversion of the website to Git, but I'm not sure if it's updated or it's certainly not synced with the website. How big was it at the time? I have no idea. My own personal thing is I used to be the CVS maintainer, it's horrible, I got away from it and that made me very happy. I haven't had to use CVS for anything else in five years. Every time that I come across doing stuff for the Debian website, and believe me I don't do much, it's typically tweaking pages to do with CDs. All of my finger memory has gone away and I end up having to fight with it. The biggest problem with the conversion to Git is that the current translation system relies on the CVS ID numbers. Oh God. CVS revision numbers, so you'd have to switch to Git commit IDs I guess. Of course they're not going to be. Of course I've seen this in other situations, they're not monotonically increasing so it's not as easy to work with. Yes, and the other thing is that for some pages there's a chain of translation. The original might be in Polish and then an English version gets translated and then that gets translated to German and Japanese and whatnot. So it seems a bit complicated and so we'd probably have to invent a different way of doing that. A different workflow? Yes, probably not involving commit IDs. One thing that could help with that is converting to something that we can do normal get text files. I'm not sure if that's possible with WL, anyone know? I don't see why not, but we don't have DNS here unfortunately. Anything else people would like to talk about about the website stuff? That's my pet peeve out the way. The reason I did the boff here together for the two groups is to not just take up too much time. I guess everything's perfect, more people will be here, torches and pitchforks. Is anyone on IOC watching interested? There are a few people on IOC but they're not saying anything. I guess we'll move on. This could be a short boff. The wiki, which is the main thing that I'm interested in, I'll be honest. Paul and I are the two active wiki maintainers in terms of we have shell access on to the wiki server and we can do everything on it just about. Several other people have super user access within Moin itself, which means they can do things like set ACLs, they can go and delete spam, that kind of thing easily. More support, more help is always useful. Believe me, like every team, we have many, many other things that we want to do if only we have more time to do it. And the individual people are busy doing all the tasks too, but fine. I did a check last night and we have currently have 12,203 pages in the wiki. Of course, we probably have a couple more since then. That's a scary number, it really is. Most of them are out of date. This does not count spam pages. There are quite a lot more pages that did exist but have been deleted since. This is system info, so it only checks things that are currently valid. The number that scared me even more was the system seemed to tell me we've got 12,500 registered user accounts. Now, we did have about 3,500, 4,000 more spammers which have been disabled. That number seemed very high, but I couldn't find anything that told me that I counted it wrong. We're currently running a mostly clean version 1.9.4. We have a few patches that mostly that I've come up with for helping with spam. We're about to move to 1.9.7 probably today. Again, still with a couple of local patches. I'm going to jinx things and say, I think we solved the spam problem. Three years ago when I really started getting involved with the wiki stuff, we had a horrendous problem of people just posting all kinds of crap all over the wiki like they do. We've gone through a whole slew of different approaches to stopping spam. The main one is you must now be a registered user to be able to edit pages at all. To create a user account these days, shockingly, you've got to be able to register with an email address. Still something that's missing in Moin. The patch that I have to add this is something I'm hoping to get pushed up again this week. I've been talking with Upstream. Even forcing people to have working email doesn't stop the spammers. You'd be amazed how many we get, still trying to get through. The second part of the spam stuff is basically I've come up with a big set of heuristics and encoded them in a pull script. Whenever anybody tries to sign up for an account in the Wiki, we have a script that basically has historical knowledge of what looks good, what looks bad. It's not quite Bayesian, but it's approaching it these days. So, as a rule of thumb, if you try and sign up for a Wiki account and you're coming from hotmail, it's not going to work. Because to a first approximation, 99.99999% of hotmail sign-ups are spammers. Don't get me wrong, it's not just hotmail. If you're using a Gmail address, it's unlikely that you will be able to create an account straight away, unless you look particularly non-spammy. Again, all of the free email providers are too easy for spammers to sign up with. Paul, we have comments. Oh, yes. Hi. Do you have to be a registered Debian developer to get a Debian Wiki user account? No, not at all. Just because I'm a noob, so I'm not a registered Debian developer. Sure. And we have a question at the back as well. I'm new to Debian. Could you explain to me how you're making sure that the user looks less spammy? Sure. A typical spammer, in fact, I'll show you in a moment. I've got a demo of the system I currently use to look at it. A typical spammer sign-up will have some random sequence of alpha numerics at hotmail.com for an email address. For the user account name, we'll have four or five digits or capital letters as an email address, so as a user account with no overlap between the two. They will be coming from as often as not a random Chinese mobile IP, or they'll be coming from a known spam haven. I'll list a few of those in a moment as examples. If you're coming from one of those, then the anti-spam script will basically, it gives them all scores, and if your score is above quite a low number, your total score, then you just get told no. If you try to come from the same IP address too quickly, say in less than two or three days, and you try three or four times with, again, obviously ridiculously spammy things, we blacklist the IP and say, sorry, that's it, you're not getting in. Blacklisting the IP isn't just a, you can't sign up. It's a, well, you're clearly not interested in Debian, we blacklist it, you don't get to see the Debian Wiki anymore. Going beyond that, if there are obvious patterns, and we see it all the time, were a whole slew of addresses from the same network provider, all in the space of one overnight session, I've seen some say a couple of hundred attempts from loads of things in the same slash 24 or something, we will just block the slash 24. If I go, let's see if I can make this fit. Basically, I have almost a console running on the wiki, and I'm not on the network, of course, am I? Bear with me. Are we using catches? I don't remember something catching or something. We've tried using captures in the past for a short period, on a mean short, like a few weeks, it helped.  Privacy violations. Privacy violations, there are so many problems with it. To be honest, the biggest problem is it doesn't work. We actually found it didn't help for more than a few weeks. The spammers have already solved the recapture problem, their problem with it. They either have systems that manage it automatically, or for pennies, they get people in the third world or whatever to just sign up and do them for them. The fact that we're already seeing people coming from Hotmail, Gmail, Yahoo, where you've already got to have done a capture to get the email address in the first place means that people have solved this problem. We can slow them down very small amount, but unfortunately it just had no effect. It did legitimately annoy a number of people who wanted to be contributors. Again, I added a recapture patch for Moin, which I'm pushing upstream. In case other people want it, I wrote it and then turned it off. Steve, on that front, I talked to the entry and said he sent you a script so that we can whitelist tour, is it not? Yes. It would be great to integrate that at some point. That would be lovely. So that we don't ban people who like to be anonymous. Yeah. Again, that's something I'll come back to in a moment. If you have a look, I have a simple screen session that's running on wiki.debian.org. I don't know how visible that is. Yeah. And then it's basically going to go away. Is that more readable? That's about as big as I can do. You will see, basically, I have a monitor script that runs, and just for my information, basically goes every couple of minutes. It checks through the last so many days' worth of account sign-up attempts. I've got something that will give me the IP address that something came from a call. Of course, it's got no reverse DNS. This is one at the top. We have, as I was saying earlier, we have random looking attempts.  They're not getting in. So we've denied both of those. The average score that we've given them is 29, just based on the information that that's given us. A score of 29 is much more than the threshold of 10. They're not getting in. It's as simple as that. They've only attempted twice. If this same IP address had tried a third one with yet another username and yet another email address, the system will actually say, you're clearly irredeemably a spammer, go away and will block the IP address. The next one down looks maybe more believable in that the email addresses are at least vaguely consistent, but still Yandex is a well-known Russian search engine and female provider.  It's not a guarantee of spam. None of this is. A lot of it comes down to judgment, but I'm not about to block them. If they try again with an average score of 28 and higher, again, they'll get blocked. Yesterday I wanted to sign up for the wiki to edit for the wine and cheese party thing. I have a live.in account, simply because it was easy for me to get that handle. I did not receive a confirmation email. How do you deal with people who are genuine but still have emails coming in from live? It is a very good question. When you try to sign up, if you have been blocked, you will actually see it's not as obvious as it should be. I know that this is a problem. After you do the register account, you should be told at the very top of the next page in a banner, sorry there was an error. If that error persists and it will give you an error code, the error code is purely and simply it's the number 900 with your spam possibility score added to it. If you get an error code saying, number 914, please try again, if this continues, mail debbyn.org, then that's what is meant to do. It's not perfect and for people who don't speak English and we have quite a number of those obviously, it's not great. It's the best thing we can do for false positives. If you mail debbyn.org or wiki at debbyn.org and say, I've tried to get in and I've got this error message, we do it every day, we can whitelist the email address and then the next time you try and sign up, it will let you in.  I'd actually, and I'm not kidding, see it as a capital crime. But the point of the anti-spam stuff isn't the point of a boff, it's not the point of the wiki. The point of the wiki is the content and that's why we want to get shot at the crap. Perhaps. We have a couple of comments from the gobby. Yes. Debbyn deserves an archer's or Gentoo's grade wiki. That's one of the comments. There's an idea to freeze the wiki per release and copy on right to the new version. I've added an alternative idea to that, to add some macros allowing pages to know what the current release is and show the stable release. That's pretty easy. You've done that. I've done a couple of things so that you can show the name of the current stable release. Probably not that hard to extend that. Or to have something like that. Our wiki is very large. We have a huge amount of data.  I wish that was an exaggeration, but it's probably an underestimate. The Gentoo wiki was great, as I understand, and then they moved site, decided that they wanted to start again and it never quite happened. A lot of the content just never reappeared. The Archwiki is absolutely awesome. They've got a great community of people who keep on posting vast amounts of really good documentation. Some of it is arch-specific obviously and doesn't necessarily translate. But half the time if I go looking to solve a problem, I've got a laptop configuration issue or whatever, I do a search and the Archwiki is at the top of any good content but good links as to where to find more information. Yes, it's great. The Debian wiki is also great in some respects, but it often comes up in good searches. Unfortunately quite often with the same outdated information that I know because I wrote it a few years ago, that kind of thing. Hell, the internet's like that. I haven't, no, not yet. I know they're using media wiki or something that looks very like media wiki. One of the issues with the different wiki engines is they all have very, very different spam setups and very different spam solutions. Moin is very much our preferred setup. We have this something that happens every couple of years. We have the boff like this. People ask about, well, should we use a different wiki engine? And the answer is possibly but who's going to do it? And the big problem with switching wiki engines is then migrating content or not and then you end up with an empty wiki and nobody uses it. Sorry. So if someone was interested in doing at least a test case of media wiki migration, that would, I just asked this in the IRC, but that would require having an actual copy of the media wiki. Obviously the GitHub, or the Git that you can get from the teams slash Wiki is just the scripts. Is there a way to get a copy of the entire wiki? We can happily give you a toggle dump of the entire wiki. We have done to a couple of people in the last few years. Yes. In addition, I wrote a patch for Moin so that we can have a daily generated offline copy in HTML format for people who are in remote locations when we read the Wiki. Unfortunately, that hasn't seen much traction upstream. Steve, do you have any way to get people to review my patch? It's been reviewed a few times and I've fixed it up. Moin upstream are very helpful. Thomas in particular is really cool. A lot of us is overworked. Best thing to do with the Moin people, to be honest, is talk to them on IRC and push the patch into the upstream Moin wiki as a patch for a review. I've done both of those things. Ping again, they get busy. Again, they don't tend to do that much by email. It tends to be IRC or wiki itself. Thomas is good enough that he's interested in the patches that we have for Moin 1.9 for the recapture and the mail verification. I've just been too rubbish at factoring them and dealing with his review comments which are at least six months old, possibly 12. Again, it's on my list to do this week. Other things that we do have, and again, a wiki is all about the content, forget, the engine is frankly irrelevant in the long run. The main thing that you need is good content. And good content of course is correct up to date and maintained. I do have the first cut of a script that will walk through a Moin and will go looking for pages that are out of date. We could start maybe using it, pick out the users who have contributed to pages previously and say after six months, if pages are tagged appropriately, say you suggested that this page reviewing every six months, please check and update it. I think that's a useful thing and I've never seen any wiki do that. I don't say I've ever played with every wiki on the planet, there's far too many clearly, but I think that will be a useful thing to have, I just haven't rolled it out and really tested it yet. There are issues of course that people doing trivial spelling tweaks of course will reset the counter. Equally, the people doing the trivial spelling tweaks will then be the last people who touched a page so well that they will then get pestered about the content and say you're clearly the expert about the details of the kernel driver for this USB webcam, please tell us more about it, please check it's correct when all they've done is they've added a link to the Russian translation or something. It's not perfect, but I think it'll be a good start. Yes, it is. Do you know how many people use it? Approximately zero. Hello? What about using templates? Have we explored that? Basically bootstrap new pages with templates for common... Moin does have a template feature and a bunch of pages already use that. So there's like 20 or 30 templates already. Depends on what kind of page you want to create. For certain things, say announcing that you're going to do a BSP exactly or whatever. We have a really good template for that already so you don't need to fill in all the details yourself you can just fill in and it generates the rest. Again, it comes down to people using it and people maintaining those. If you have ideas for things you think we're missing, please chat. That's about it for what I had to talk about really. We are always looking for more people to help, as I said. Especially with the bugs. Especially with the bugs. Because they're kind of piling up and aren't being looked at. Oh, yes. There is wikidocdebyn.org BTS category. We're not very good at tracking bugs there necessarily. We do see them. Honest. We can mention some of the special features that we have on Devian Wiki. Go ahead. Do you want to come up? One of the things is that when you add a link to the Devian bug tracker we have some JavaScript to go and look up the status of the bug and alter the CSS on the page so that it's more obvious what the status is. And then you can hover over it and see the title and all that sort of stuff. Also the wiki looks up daily what the current Debian release is. And then you can say what's the code name for the stable release and there's a macro for that. And there's another one for release dates and for version numbers. There's one more macro for linking to message IDs so we'll just link to the Debian lists URL for the message ID. There's also a convention for if you're working on stuff in the wiki and you want it to stay around because it's linked elsewhere there is also the category permalink which we use to make sure that say especially later if people have got we've mailed out press releases and stuff that link to things in the wiki that those pages don't go away when people are finding them in the archives later that kind of thing. So one suggestion from ILC is that a couple of people are suggesting they could do a www slash wiki bug squashing party remotely at some point to try and get through some bugs and things like that. That would be cool. There is going to be a bit of a step change coming of course and I should have mentioned it earlier and it's just remembered one thing that we don't have yet for the wiki is single sign on. So if you're a Debian developer or an AliF user or anyone any other random person everybody at the moment has their own separate wiki account frankly that's crap and single sign on is mostly working it's still in flux for some of the Debian web space we're planning on looking into single sign on real soon now we have been for a while the only reason it hasn't happened yet is down to manpower and other people doing other sites first with a single sign on so if you have a Debian wiki account and you're a DD then expect at some point in the near-ish future you'll probably get an email to say stop using that account or we will somehow find a way to link that account to the single sign on system it's a bit in flux at the moment and that's exactly something that would work very well at a sprint or a BSP type setup on another topic I'm not sure if anyone here has other languages that they can speak and write but the wiki it is possible to do translations and the way it's currently set up is you add the language code to the start of the page name with a slash after it that's not the best way to do it and it'd be great if we had a different way maybe with get text files or something but it'd be great if someone could research that if you're interested certain of the system pages in Moin because this is provided by Moin will automatically we direct you to the appropriate page say if you log in and your machine is set up and it can recognise your browser says it prefers French you won't get sent to front page you'll go to the French equivalent I don't know why I picked French because that's the one I can never remember the front page translation but for example I've tested this myself it's maddening because once you've told your browser it knows about all the languages trying to turn that off again and then I spend the next day struggling to redutch or something can you speak a little bit about the performance and infrastructure of the wiki sure the wiki itself we used to run on dedicated hardware that frankly was a cast off from other uses over time as we started getting more and more page views the thing I should have done as well was actually go and grab the stats for that we realised that actually it wasn't going to work that well we've since moved over to a dedicated VM provided by DSA AMD64 with huge amounts of memory so basically it runs something silly like 1632 threads of WSGI running moin it seems to work okay we have found we are one of the biggest moin using sites on the planet we did find that we had a major issue there was a major performance problem with page saves not that long ago so you could happily read the wiki pages but saving something could take literally a couple of minutes and that turned out to be it was a scalability it was a design flaw in the way that moin notifications are done when you go to save a page there isn't a link from that page to each of the users who is known to have to be wanting to watch it to get notified when it changes so instead it was walking through the 12,000 user accounts looking in every single user password file to see does this person want notifying about this page that doesn't scale very well so there was a patch already that the known wiki people had come up with I tweaked it slightly we reviewed it backwards and forwards a bit I think it's actually gone into moin for 198 which is due to be released soon and it went down from literally a couple of minutes to maybe two or three seconds which is fine a lot of people may not have noticed it but if you went to a bug squashing party and the convention is that at a BSP you will fill in details about all the bugs that you've fixed so you've got competition if you've got BSPs in two locations or you can just point people at it later and say yay look what we did if you've got 12 people around a table all of them working on bugs and going to update their list oh my god that was painful so I got shouted at a lot at a BSP and that was what prompted me to go and fix it I'm not aware of any other major performance issues at the moment we did have a fairly well publicised security breach a few years ago which was due to a bug upstream in one of the drawing plugins and that was fixed and that caused reset one of the flip sides of that one of the downsides was many many of our older accounts were set up by people who had never put in email addresses because you didn't have to when they first signed up so a lot of those people we had to of course reset all the accounts or disable all of them force people to do user account password changes for those people who didn't have working email there is no way of doing an automatic password reset through Moin because it sends you an email so if you're one of those people and you couldn't log in anymore sorry talk to us the great thing about that security hall and attack was that we adjusted configuration so that they ran as a different user and they can't modify the file exactly, the default setup of Moin is not very pretty in terms of security it's simple it works but it does end up with all of the data and potentially a lot of the Moin code itself owned by the same user we've explicitly set up a privilege separation for the WMWC to get around that and we worked with the DSA folks for quite a while to get that working and they were awesome about it basically it was just over Christmas that year and we ended up spending a lot of time overnight if I remember correctly installing a new machine, we migrated all the pages it was horrible but hey sometimes it happens so I've been wibbling far too much in here so please, does anybody else have anything? Hello I'd like to I've got a question which is about the website the previous topic each time developer commits a change on the website there is 4 hours there is a script to rebuild why not just each commit for example I think Neil has an answer for that so when I update update bits of the website for the press releases just updating the news section where all the press releases go takes about 10 minutes or so so basically it's just huge the actual size of the site to generate it from WML and all the languages we have it's about a 540 megabyte repository so it's basically the time just to generate all that HTML is sort of the issue there for pages where we know that they shouldn't be affecting very much it is, as I understand it, it is possible to just rebuild small bits of the website but it's always potentially risky the way that WML lets you cross link things and essentially hash include bits and pieces and use macros all over the place that's what it boils down to it's not pretty, it's not great I'm not aware of a better solution I think we are just about done so oh no, or more currently it's with CVS if I will understand this because there is a hook which is used for translation or something like that is it possible to use more get text and profiles to fix some of this problem there was some discussion on IC about this apparently that PO4A supports WML so we could possibly do that and at the moment there are some parts of the website that are using get text but not the whole thing so there would have to be a conversion and that could be totally manual I would think but I'm not entirely sure the biggest problem with a lot of the ideas that people have spoken about like to get migration and whatever we are struggling to find the people bandwidth to get through a lot of this too more volunteers needed as always and if you have any questions about the website or the wiki Steve and I here we are both here all week come and ask us and we are both on the best list and of course I should have put this down but we didn't we were at list.debian.org or wiki.debian.org is the best place to get in touch with not just us but with all the other people involved as well and well thanks for coming hopefully that was useful I don't feel it's convenient because like it's really a lot of it's fun and it's only a few weeks I don't remember how it was what is it I don't know I've been using it I've been using it I've been using it I've been using it I've been using it I've been using it I've been using it I've been using it I've been using it I've been using it I've been using it I've been using it You are using it Yes I am I'm visiting the!!!!!! It's time to get started See you are going to очень!!!! Thank you very much gyda hyvä yn gyfwscar. Wrth o, gallu'n gwneud, rydych chi'n edrych yn ein bod gyfwcfadau. Tuhl, o'n eich mae'r gyfan, yn gofod? Beth yn gwneud ac dim bydd yn gwneud a'r rhywbeth? Mae'n cyfwc, ond mae'n byd yn cyfwc. Mae wedi'u hwpin, mae'n first ffoget. Mae'n rhywbeth eich bod o'r cyfan. Mae'n gwneud unrhyw表us? Mae Fyloedd ychydig. Cnow ddim are ddweud o'r cyflosio o Feitio. Well, I don't think this one's the weird one, because it's American yet. Oh, yeah, well I just went to Malaysia to get a dish for, you know, a 3D gift, which is like $1. No, but Brazil is expensive, isn't it? People are like random, shitty, maybe like $15, which is about $7-8. That's expensive. Yeah, right, exactly. But that's not a shitty place. Here, I could eat anywhere for less than $10, but, you know, what do you think? Yeah, if you're already here, yeah.  Okay, great places to go for a drink with a nice romantic rhythm. Yeah, I know that Brazil, they're not like home foods. Are you going to go eat? Yeah. Now, people actually, I didn't pass by the dorms first. The dorms? Yeah, well actually, that's a food. I need to check it out, because I'm going to say to the point that I want to make sure that I can. I just want to make sure that, like, I have a reservation because, like, I'm not on the list for food. Like, I don't hang with my meals, I can work out all the goods. All the goods?  And that's where I talk in. That's not the problem, you can't take in, but it gets hot. Oh, like if you're already home. Yeah, there's always a reason. But it's fine if you didn't do it. Oh, it's like a great thing. Wow. This is a... Oh, if you were talking about shopping, this is the more main, this is the more central. Yeah. It's here, and you can have two seats. Shit. Yeah, yeah. I just thought that was fun. It was good, because, like, I like my tennis shoes. Like, a little running shoes. But she liked it. Yeah, yeah. Like, if you need to get something like that, is that a cure? Really? Yeah, like, I bought... When I got to buy a MacBook, I bought it at a hardware store. I think I paid $200 or less. Because New York has so much. Like, I wouldn't pay with a fast book. Yeah, oh, you should have bought it again. Yeah, it's so expensive.


What's up, everyone? My name is Alex. I'm one of the co-founders of MyInvestingClub.com and I want to let you guys know about something special we're doing for our viewers on YouTube. So the most common question we get asked is, you know, how do I start day trading? So what me and my mentor about it is we create a free two-hour mentorship course for the brand new trader. It's going to be available at MyInvestingClub.co. The link is going to be right here. This is a free webinar that reveals our 12 secrets that every single brand new day trader should know before they start. I also want to let you guys know about something that's very unique to MIC. So if you have any questions about trading or you're curious about trading or you don't know if MIC is the right fit for you, now you can text our head mentor, Tosh, whose number is going to be right here and he'll answer all the questions that you have in less than 24 hours. Thank you and enjoy the video. What's up, guys? It's Harry Haas here. And today I'm going to be going over a video on the dip and rip setup. This is probably one of the most popular, one of the most talked about setups in the long trading world. And I'm just going to be going over some examples of stuff I look for so you can apply it to the market. And once again, I'm not a licensed financial advisor. So even if this does sound like investment advice, it's not. It's just all for educational and entertainment purposes. So without further ado, let's get into it. So a little background on the setup. I know I've mentioned this already before, but this is probably one of the most talked about long setups in the trading world. I didn't really fully understand why the setup setup worked. A lot of the kind of mechanisms and components to it. I didn't really understand till I met Bao. It's actually very simple if you don't over complicate it. And the reason why I'm making this video, it's almost like a first bounce part four because it kind of gives you an idea of when to take a quick first bounce trade and when you can be a little bit more patient on these types of trades. And I think this will clear up kind of a lot of confusion that's been going on with it. Basically the dip and rep, it's similar to first bounce. It's always between 930 and 1030. So with the first bounce, the first bounce doesn't really have a set time frame. So you can catch a first bounce in the pre-market. You can catch a first bounce after the market opens. Sometimes there's some in the afternoon. Sometimes there's some in the morning. So the first bounce doesn't really have a time frame. But this one is always going to be between 930 and 1030. This one kind of has more of a grindy feel to it. And we'll get into that in some of the examples. It's a lot slower than the first bounce. So when you have a first bounce trade, you kind of get that quick spike. And then we're trying to make money off of that kind of quick pullback as if a ball was kind of bouncing on the ground. We're trying to make money on that first kind of pop up. But in this one, it's kind of more of a slow, grindy feel towards the support line. Pre-market support always as our line. This is supposed to say our line, but it says out for some reason. But we're using pre-market support as our line. We can use line charts and candlestick charts. And I actually show examples of the candlestick and the line charts. And it's, as I mentioned, a little slower paced than the first bounce. The first bounce is kind of like a quick. This one, you can be a little bit more patient on. But as always, you always need risk management in all of your trades. So as far as criteria goes, I don't necessarily have a set criteria every day. And I know I've talked about this in a couple of my other videos where I don't, I don't say like, well, if it's 11 mil and my criteria is under 10 mil, I'm not going to trade it. I'm a little bit more kind of, I'm just going to trade the hot chick. And as long as it's not 100 mil float, we're OK. So it's the hot chick of the day. We, as long as we're getting some kind of high consistent volume, I really like that. And yeah, the lower floats always work best with any of these setups. The lower floats are always going to work best if you're a long trader. And that's just kind of how it works with float rotation and supply and demand. But it's not really a spot on criteria where if it's not under a certain amount, we're not going to trade it because that's not what I kind of do. So anyway, this is kind of like comparing the first bounce and what I call kind of like the dip and rip. I know that the dip and rip, like this type of setup, is probably going to always still be referred to as the first bounce. But it's more so kind of like a more, it's a patient first bounce compared to these where we get this parabolic move and then we're just making money off this sort of niche in this where we are kind of making money off the pre-market support. And that's pretty much what this setup is. It's you can be a little bit more patient. You can kind of draw your line of pre-market. You can go grab a coffee and then by the time the market opens, you can just wait for those lines to kind of hit. But instead with this one, this is kind of like a quick move up and then we're making money off the move down and then this little bounce right here, as I've talked about in some of my prior videos. If you haven't watched the prior videos, I have a first bounce, part one, part two, and part three out. And this is almost like a part four. But I would advise you to watch one, two, and three before you kind of start trying to learn this setup. So anyway, this is SES. What I did basically is I took on my computer. I have different file folders for examples of different types of setups. So like the VWAP bounce video that I made, I have tracked that setup kind of extensively and the other kind of setups that I trade like first bounce. I always take screenshots of them when they come and save them in case there's like a time like this where I'm like, hey, check out this SES trade that I made just so I have all my trades categorized and I have all my trades kind of right there in front of me. So if I need to pull an example, I can pull it right away, whether than spending 30 minutes trying to look for the type of setup. So anyway, this one with SES, it's kind of a good first example to start with because we notice in the pre-market we have this nice pre-market move where it just kind of flows all the way up. We notice that this support right here, this kind of support line on the way down, the chart likes to, the lines like to conform to the chart. So we know that already. And then we kind of get this move up, the market opens and we kind of get a little tank here and then we get this nice pop up here. And what I like about this chart so much is that it is already kind of broken this support line. So the next one is kind of like this 3, 320 area and that's where you can kind of look to find some support here. And then after that, we kind of get this nice pop and we notice that there's kind of some constant volume always happening. So the volume isn't inconsistent like it is over here where there's not a lot of volume left. This is always doing some volume. So I really like that. I love when the stock doesn't feel dead. This stock isn't a broken stock. So we kind of get this move again and then we get this little area of support here. This area of support holds and it ends up coming up like this. And if you look at this on a candlestick chart, you can ignore these trades. These are kind of like sometimes I'll do pre market trades in the morning with like a little smaller size just to kind of get a feel of the stock and kind of feel how the stock is trading. So we kind of notice this area of support right here. We know that there's an area of support right here. We know that there's kind of an area of support down here. So we get this open and we kind of get this fade and kind of pops off this kind of 320 area once and then it used this kind of support line and ended up coming off it. And this was probably ended up being like a chat pump or a bunch of shorts ended up getting squeezed who were trapped down here. But basically there's a couple of things to note about this type of trade. Number one is that I wasn't chasing in up here trying to be a hero, trying to get a big squeeze. I was very patient and waited for my kind of lines in around here. Number two is that we notice the volume is pretty consistent down here. We get these 150K bars all the time up here. It's more upwards of 400K all the time. So we know that there's a lot of volume being done and that's something that's important to note because let's say that this volume had a dropped off way off to like less than 100K and a volume bar or 60K or even 50K. I probably would have just started ignoring the stock and I probably would have cut a loss on here. But this is a type of trade where I know that I can be a little bit more patient on because I noticed that the line is kind of holding a little bit longer and that's it, like this type of move is not something that you're going to see every day but although recently we have been seeing a lot more it's something that I just kind of pay attention to and it's something that I'll draw my lines and say to myself, okay, this kind of looks like a dip and rip setup coming in. Let's try this line out and I'll just risk underneath three and if this gets broken here I'm just gonna cut for a loss and that's it. And that's pretty much my trade idea on this one and ended up working out. These types of trades are just so I can, just so I'm kind of sitting in my seat watching the price action and I kind of get a, they're almost like warm up trades. So it's not like I'm looking to like bank big or I'm looking to be a hero or I'm saying, oh man, oh man, like crazy. These trades are more so like warm up trades just so I have a little bit of skin in the game early. It's not really a FOMO trade. I don't do this all the time but when we have a setup come around like SES I'm gonna try and look to just get a kind of a read for it early. Number one, you're never gonna always be perfect. And number two, these stocks are just vehicles for your money to grow. They're just vehicles for your money to get to point A to point B. So if you start out with let's say $100 then and your goal is to make $120. Well, if you've made $120 that was your goal in the beginning and the stock was just a trading vehicle to get your $100 to 120. And I think that's probably the most important part is that you're gonna see charts like this where I show the best setups and the best kind of ideas of the year and I'm just trying to showcase the absolute best trades with the setup but I also think that it's very important that you realize that pre-setting your sales on a daily basis can help you catch a lot of the B green consistently rather than trying to hold for something like this and have it not come. I'll be back next week with a new one. Thank you so much for watching our video. If you wanna see more of our videos please subscribe to our YouTube channel by clicking the button here. We do our best to post a new video every single day. If you have any questions about MIC or any general trading questions please text Tosh using the number here. Also stay up to date by watching some of our most recent videos right over here.


I'm here to talk about your Plasma Desktop, quick recap for everyone who doesn't know which window has focus. Okay. Ah, it's upside down. So, what is the Plasma Desktop? You've presumably, everyone in this room, seen it. It's this. It's the desktop and the panels and your widgets and everything visible.  There's a lot of background services, so all your different keyboards, layouts, configuring every possible setting, and we're known for having a loss of possible settings. So, all of your system configuration. And also on Plasma, there are a lot of background services that you don't really know about but take for granted, making sure when you close a lid, your computer suspends, making sure when you press a volume up, your volume goes up. And it's these little things that make quite a bit of a difference. And in terms of code, it's a roughly evenly split between each of these four components. Although, for goodness sake, known people are here to infect our talk. Equally large size of our code is all of the style and integration. We have styles and integration for not just Qt5 and our applications, but also backporting out to Qt4, backporting out to GTK2, GTK3. And also, if you look through your code, we support TK. We export all of the colors used as X resources databases. So, TK applications will have some level of style and integration. I don't know how much that's used, but we try and integrate into absolutely everything under the sun to get a consistent experience. So, overall, Plasma is everything that puts you in between a black screen and any application, no matter where it is, and being able to use your applications. So, last year I sat on a stage very much like this one, but not this one. That would be amazing photography. And I talked about three things. I talked about how a desktop is still relevant, because there's a lot of hype about mobiles last year. And I talked about how Linux is still relevant on a desktop and how Plasma is in a good state, but a potential is bigger than what we currently have. We can improve a little bit to reach out full potential that we have available. So, what's changed in the past year, in the past 12 months? That's what I just said. Desktop usage. I managed to find a new slide, updated now, including 2015, shows how many hours are spent using a desktop every day. And, with our new entry, it's exactly the same as the year before. There's no real sign of it waving. If anything, it peaked in 2011, but that's just an abnormal blip. A desktop isn't going away. There's no signs of it going away if you look at stats. If you look at percentages, yes it is, but that's only because people are spending more and more time on mobiles, not at spending less time on desktops. So, Plasma is a desktop still relevant. In terms of Linux market share, fancy quote taken from Slash. Slash. are all-over-loving Katie and Linux. Linux desktop now accounts for 2.48% of everything in June, and that's not including Chromebook. Did quite a lot of research in checking out. Chromebooks don't identify themselves as Linux, for some reason. So, Linux overall has increased over the past 12 months. This was roughly 1.9%. Now it's steadily nearly 2.5% of all users. And in terms of absolute users, that's millions. Any company would be pleased to have that many users. Obviously, that's not all Plasma. It's probably 99% or so. Yes. This is time spent in hours on a computer. Blue is desktop, green is mobile. Yellow is, who knows? Foglio's weird key, obviously, fine in shopping centres. But desktop still relevant. Linux on your desktop still relevant. So, what's changed in Plasma over the years, and it's a nice montage of all the different wallpapers we've had. It is the main reason these slides are here. So, we wrote the main key menu. That got completely rewritten. Visual theme got refreshed. Restored the super old legacy icons. And we had four brand new applets arrive in the Plasma 5.5 release. Warm to show how much this space is used if you have quotas enabled on your system. Next Dominic. A colour picker for quickly finding what colours used in the awesome backgrounds. Being able to switch between users. And also being able to switch between activisers quicker. Lot of things improving your workflow. And of course, work on well and support. So, what happened in 5.6? More improved workflow. Again, that's really our target because we're trying to put you to your apps as fast as possible. So, a task manager gains some features. It shows progress in your task manager so you don't have to open the application to find out it's not finished yet. And you don't need to open your media player just to go on to your next track if you call it on random and it starts playing Britney Spears in the loop. Or you can go back and listen to it all again. And this work on well and support happened in 5.6, continued. And we had a new applet, a weather applet got restored. So, we're back to pretty much most old apps we had, plus new stuff. Plasma 5.7 continued rewriting everything. A task manager back end got completely rewritten. Task manager being the bit that's normally at the bottom by default shows which applications you have. Your system tray at back end got rewritten. And we improved your workflow. If you know K-Runner, assume everyone does, you type and it shows you search results so you can type anything you get results. And that got improved your workflow so you can jump directly into a specific activity within an application. Oh, and there's some work on well and support. That continued. So, 5.8. It's got a rewritten back end for your pager. There's lots of rewriting. Most are legacy code from Plasma 4. Once you know what you want the code to actually do, then you can go back and rewrite it. And that's something we've found on Plasma. It's things we've built up with adding new features. And it comes a point where you have to say, oh, now we know what we want. We can redo it again. And this time basing it directly on knowing we'll be in Qt Quick and we'll be knowing we'll have new features. I've got new things for if you switch between different themes, change the layout of your desktop. And oh, there's some work on well and support. So, your general themes over the past 12 months, because we've had those four releases, 5.8 is just about to come out because academy is at a slightly different time. There's been no dramatic changes. We haven't had Qt 6. And there's been this continued iterative improvement. So, everything's always getting slightly better, but not getting worse, which is always a good combo. And it was improved well and support. So, coming up next, 5.8 is an interesting twist on it. Now we're going to have long-term support. So, instead of just having three months of patches, it's now going to have 12 months of patches. At least 12 months of patches. 12 months of patches, 18 months of support. We'll see how it goes. Something that we've not really tried before, even in plasma 4 days when we're dealing with six months release cycles, that was not as long as this. This is twice or three times, if either of that. So, that's going to mean interesting times, but it also brings in new opportunities because we found one of our particular distributors, and I think you're going to find in Munich that you want more in three months of support because you don't want to grow up upgrading every three months. And it's really a sign of maturity that we're now able to say, we can offer 18 months of support and not get too stressed about it. If we did that for earlier versions of plasma, I don't think anyone of us would have been as excited. We would have missed out on a lot of Wayland support. But Wayland is not part of the plasma 5 long-term support. 18 months being long. So, with any slide presentation, it's always good to throw in some stats because it shows I've done some research. In the last 12 months, 194,000 lines have changed, which is quite a lot. Over 8,000 commits, which again, so quite a lot, averages out if my maths are correct, 26 a day. But including anything that was in, a branch and then merge into master.  And this is something I think is quite encouraging. There's 146 different contributors in all of the plasma work modules, in the past year. Only in the last 12 months, but it does include scripty, which is a bot. But scripty is one of our best developers. So that's an encouraging sign. It shows that plasma is alive. It shows 145 different people were able to set up plasma in a development build and start contributing changes. And that's probably the biggest challenge we have on plasma is to set up to begin contributing. So it's not a bad state. Own cloud in its peak was around 300, but in other projects which are successful and they have considerably less. So it could be better, but definitely not bad. Not bad at all. 1,082 bugs marks has resolved fixed. So we've actually made a change to close something. We haven't just said, I don't care about your problem. We've made a change and fixed 1,082 bugs, which is pretty encouraging, because I don't think we've introduced anywhere near 1,082 bugs. And overall we've closed just over 3,000. That's including solving people's problems without a code commit, maybe pointing them in the right direction or it being a duplicate or in some cases, disagreeing with the user. But I still want that increase, but it shows generally things are going quite well. So on to talk a bit about what makes writing a desktop hard, because we see quite a lot, particularly over the last couple of years, of new desktops coming along and we're going to be a great new desktop. Why is it hard to write a desktop? Well, you have integration with completely different distinct components. If you write an email client, you're going to be an expert in IMAP and maybe SMTP, not a lot of things. To write plasmer, we need experts in pulse audio, we need experts in system D, we need experts in spell checking for your word completely and spell checking. Again, you have all of these different layers that come in and require different skills from proofreading to reviewing, but also all of these different libraries and the problem of the more things you depend on is this big chain from any graphic driver to your spell checking libraries and we have an abstract layer over three different ones, or in my case none. We have all of the different things and if any one of them fails, plasmer seems like it sucks. We need people with a wide variety of skills and that's hard to get. That's more external dependencies both explicitly and implicitly in most other pieces of software and that makes writing a desktop hard. I want to tell a story of something that happened over the last 12 months with this ridiculously old legacy support for many, many systems. One example is accession management. Accession management is a thing that restores your applications and it was an old protocol that we dropped from client side at the start of KD2. It's so old that it's predate to Spice Girls. It's a point of reference for most things and we don't need any more. There's no way we need that bit of code so we dropped it because of the cleanup and in theory any application should better speak a new language which we support. One month later we ended up putting it back because applications still used it and we got reports on it and that's something nearly 10, 15 years old that we still have to support. At the same time, we've always constant new things to support. System D decided to change its behaviour of what happens when you close a lid. Previously plasmer handled it. It was plasmer job and plasmer could check and decide, oh, I'll shut down or the user said they wanted to stay open. But we have a new code of path that decided no, I know best. In fact, it's true of most of new system D, log in D and we've got new graphic changes. We have the way to support. We have the new things and we have this legacy old things and that just means we're continually growing and growing and growing and that makes it also very hard to change up. So Dave's definitely correct opinions on the future. So it used to be a rule of thumb in computing that every... I don't want to say how many months now. See, I thought it was 12 and every 18 months, the speed of a computer would double and that lasted true for ages. That's kind of stopped now, particularly on the desktop side on backwards. Now we have this demand for... this particular computer here was given away free on a magazine in the UK. Not an increased price of a magazine, it was free on the front of a magazine, a computer. And that's now almost a standard and it's not faster. Users aren't getting faster and faster hardware, they're getting cheaper hardware and expecting our software to run on it. So our normal expectations of we can use these new things, we can increase in memory and RAM because computers allow it, we're actually going backwards and if anything, we're now trying to support computers with less resources than we were a couple of years ago, which is interesting. And Android desktop is definitely coming. We know it's coming in a couple of years. What impact is that going to have on plasma? Is that going to take away some of our users? Personally, I don't think it will. I mean, I wrote some software to run up Android application on a desktop and really there wasn't much demand because anything of an Android application also has a really good website, which normally works better. And I think it's going to take away users who would otherwise switch to Chromebooks, taking away a Windows users because we kind of have a market of nerds that I don't think are changing. But it's something to be wary of. It's going to change the shape of desktops over the next few years. And one thing that's big to talk about is a slash that article recently, KDE is dying. And that's not true in terms of a community or just showing plasmas doing quite well. But we've had the marketing changes. There is no KDE anymore. We have a distinct plasma, we have the applications and we have the frameworks and they're pushing in different directions. And this is good. If I wrote an application, I would want to try and reach as many people as possible. It makes sense. However, it changes the way we think we do things in KDE now. If we had a new idea for creative tech, like activities to some extent, or a remote file system, we can't do that at a KDE level anymore and then just change this entire suite of applications to match. For two reasons, partly because our applications want lowest column and denominator to run everywhere, and partly because our plasma users a lot of the applications they use now are now in the web. It's not a KDE application for doing every single task, even playing music, you do it in the web now. A lot of people, a lot of tasks straight into the web. And we have limited control over the two big web giants, Firefox and Chromium. And that changes the way we do things in plasma means we have to target slightly lower levels. When we're seeing out now, Phonon did some crazy ideas of how sound gets rooted and we did that at a library level. Now, we always saw in 5.7, 5.8, we're improving our... talking to pulse audio, which is at a slightly lower level beneath KDE and we're plasma is improving our integration now. And that's not necessarily a bad thing. It improves desktop homogeneity, desktop behaving similarly. But it's a change that we're having in plasma. So, wrapping up conclusions, a desktop is still relevant. Linux is still relevant on the desktop. And plasma is in a good state. Over the last 12 months, we've seen very encouraging changes. We've seen a good amount of contribution. Things are heading in a generally positive direction. But it still has more potential than we're currently reaching. Yes.  In case I can't hear you. So, what do you think we should focus on at a high level? Dropping, not dropping things. It's like a tendency yet. Focusing on a high level, I think there's been a theme, particularly stuff Kai has done on getting you to your applications. I think that's very important. Or a jump action changes. I think that's very important. And that's very good. And one thing I think we'll see. One of my favourite applications that I use is something called Nevolva Player. And what it is, is a web view. But it, by default, loads either Spotify or Google Play Music or Deezer. And it has a very, very tiny bit of JavaScript that turns Empress into irrelevant changes on your desktop. So all of the plasma functionality, all of our application integration, still works even though it's a web client. And I think that's something that, over the next few years, something we might see in various other applications, is something that we can control and it allows plasma to be useful to people because it's getting them to their content, no matter what platform it is, because we used to do that. We used to get people to their content, even if it's on GTK. We need to focus on getting people to their content even if it's on your web. And our bookmark handling code in the start menu and runners, that hasn't changed in 10 years. And there must be room for improvement now. There's still the data integration between the desktop or the workspace and the applications. Agree? We can do a lot better there. I think that everything around that works pretty well. We can do more to poke into applications and no metadata. The dynamic window decorations that some people may know can actually play. It can, yeah. Two questions. I think the mic... Oh, yeah, now it's working. First question, was that presented on Weiland? No. Second question, did the bug numbers include the recent bug closing sessions I did? No. Then every number, probably 100 up. OK, Martin wants to show off how good he is. I know. Yeah. Ken's got a question. I don't know how long I've got. If you had like a million dollars and you could just pump it into a few things on plasma, what would you have people focus on? Well, swimming pool. Um... Now, it's a tough question. Yeah, I mean, yeah. Auditing of our code is important. I mean, we're going to see Weiland allows applications to be sandboxed. However, that's only as good as the surrounding software. It doesn't do anything by itself. It requires our software to match. And it's not just a Weiland part, because as Weilands is secure, we can no longer use the excuse or if it's insecure, we can't do anything. And we're going to see the weakest component get shifted about, because the weakest component is not X. I mean, the weakest component is now this, which means the weakest component. After we fix that, there'll be a new weakest component. I mean security auditing. Security auditing requires expertise that is new, and it's not a very fun, sexy task. Anyone else? I have a question from the perspective that we're looking for. We have a lot of Linux users, actually almost everybody in the company is using Linux. We are probably one of the few bigger companies where everybody, including sales people and management and so on, are using Linux desktop. I think my company probably has the same. That's perfect. What I'm saying is we have a lot of enthusiastic Linux users, and we also have a lot of enthusiastic KDE users. What I've seen over the last couple of years is that people have switched away from KDE. What I hear is the number one reason for that was almost always stability. It was never a lack of integration with the web or lack of new features or lack of whatever. It was mostly about I updated and something stopped working, so I switched to something else, whatever it is. My question would be on what position is stability in the list of the priorities of the Plasma team? As a team, there's obviously lots of different people from lots of different influencers, so I can't speak on behalf of everyone. I'm not going to tell our contributors to stop working on new features because we want to do this. Personally, I mostly do bug fixing instead of any new features, partly because that's part of my employment, is working on making sure my boss's distribution is awesome. Everyone should use Netrunner, no offense. Within that, it's something I strongly feel about. We've got a Plasma LTS, which obviously you guys influenced. That's going to help, I think, improve our perception. I like to think we're working on it. Obviously, we only see how it acts in a couple of years. Also, we are losing communication between the different aspects between frameworks and Plasma and applications, and that can be difficult. Yes. The important aspect is that we... Actually, we've been going on for about half a year now. We have very, very recent builds for both open source, but also based on Neon. And for me as a developer, that makes a big difference because I don't have to wait until it's too late to get feedback. I can get it the next day after I fix something.  But imagine a user installs a half-year-old release of OpenSousa. We get feedback. Okay, it's a version which lets say 4.7.4. So we got one more chance to actually put a patch in a stable branch, which is still never going to be shipped by OpenSousa. So that's not helpful for us. So either we need to get the distributions to ship at least our stable updates or preferably even more updates, but we need to improve our stability and quality and progression problems for that or we need to be better with testing that beforehand. The truth is probably somewhere in between, but from my point of view I can say that it helps a lot to have daily builds and people I can actually point to something concrete they can test and not say, I've committed a patch and the next time we talk about that so I guess that's going to have an impact. Or 18 years. Can I interrupt for a second because I'm on a stage? It's still nothing. But it's also six times longer than what we did so far in the five seconds. We're getting a lot closer. We do have a plasma buff starting on Monday in the morning and you can find that on the academy website. So I also want to just answer the question from a CWIN perspective. So one would expect that for example all this wayland work goes into while the code quality goes down but the opposite of the case because we are now able to auto test what we were never able to do before and I've built up a test coverage of the CWIN core of now 10% probably higher because builtkde.org cannot test everything yet and that's just it changes so much if you are able to, oh I have this weird condition if this window has this X property and that one set then this code path is taken and now I can simulate everything and so the quality goes up thanks to Wayland for X on X. Because we could never reliably start a full featured X server in an auto test situation and now we are doing it all the time. I actually do it 5 times in the same auto test. I just want to reply also to you and so from a blue systems perspective this is the number one priority. I always tell the employees working on Plasma, Plasma desktop, the parts that we have to stabilise the things that are there first before we introduce new things that are half baked and this is not because of Netrun and Netrun is the highest upstream but it goes for DB and Ubuntu, neon all the stacks in between so I always am very glad when people report that they have much more stable version on SUSE or on Chaos, Manjaro wherever Plasma is used so this is the most important form of blue systems perspective. Mine was just a very quick remarks again about the stability issue and the perceived quality problems. One of the problems that often happens is not of course not the only one but there are also problems beyond our side also on lower levels of stack it could maybe drivers, maybe X11 maybe cute but are things like this one that we are in this moment a conference like that that we are all together that we can we can sit together also with the people that you usually don't see that are overseeing those lower aspects and see what we do improve so if anybody has some issues it's those are the proper days for to be addressed. Okay thank you more questions that's it okay.


Hey, you guys so I want to talk you through your first real like hands-on kitchen lab in this class This is to me one of the more complicated and What high maintenance labs in this class in our face-to-face Bio one class this lab requires a lot of prep from our awesome stock room Queen of everything Marlena and so in my brain. I'm thinking this is one of the labs where What you do for this lab is going to be more like you're gonna have more work in doing this online lab Than our face-to-face students do because they have Marlena prepping things for them. You don't So I've got the lab ready and you'll notice remember how I said that once the once the lab is ready I'm gonna put a title on it Once you see the title in your lab notebook, you'll know that you can go in and start messing with this thing That means that lab three four mm-hmm. They haven't been dealt with yet. So stay out of there Okay, the lab two were ready to rock as is normal you have an introduction where this is gonna kind of Orient you like what were why we're talking about this stuff and and how hopefully you've watched the chemistry lecture Already and now you're in here and you're ready to get started with this lab Because of the prep work you're gonna have grocery lists. There are four pages in this lab That means there's four different activities that you are gonna have to do The first activity that you're gonna have to do has to do with just measuring pH And I give you a little bit of background here a little bit of reading stuff to kind of make sure that you remember What's going on with pH and then I've got your grocery list now Look into my eyeballs This is me like I made that grocery list sitting here thinking Okay, I think I've thought of everything. I went to our face-to-face lab I looked at the materials list in the face-to-face lab and I tried to put them all in here And then I looked at my material my procedure here where I'm telling you what you have to do and I thought I think I've got it all in here if you find that there is something missing from this list if you're like dude Actually rigs you should totally include friend of plenum, huh? Please add it to your procedure like please add it to your grocery list. I Love it if you like tagged it in a certain color or you somehow Indicated like rigs. I added this thing because then I will go in there and look at it and be like, oh, dude I totally should have had that I'll add it to the master and it will improve the future online lab experiences for upcoming students One of the things I made a little list of things that I wanted to talk to you about And one of the things that I want to talk to you about is well the first thing on the list is a pep talk And the pep talk is that in exchange for You getting to take this class online whole bunch you guys are Graduating after this and you're getting to take this class while keeping your jobs and not having to come to campus them all all the Benefits of doing an online class well There there are some disadvantages There are some places where being in the face-to-face class is easier and the lab component is gonna be one of them I Really would love you to think of Your lab notebook as a literal I've thrown a procedure out there But if you need to change it if you're like dude, she said I needed to use like Like I needed to test ammonia and I don't have any ammonia in my house And I'm not gonna go buy some and so and I don't have any bleach and so I'm gonna test I can't think of a single cleaning supply because I'm not to Cleaning supply ish But dude test whatever you want. I really don't care. Just record it record what you did these like the whole procedure is It's it's my vision of What I Think will be beneficial to getting us to have the lab experience But if your brain is engaged in this you're actually gonna have a richer experience because You can you can kind of design the experiment how you want to design it Do you know what I mean as long as it's Meeting the same outcomes so down here it says don't be married to my procedure That's what I mean like feel free to get in there and mix some stuff up Again, I'd love for you to somehow note like if you want to change the color of it or somehow note that I'm I'm going away from the rigs procedure, and I'm doing this other thing But I'm doing this other thing that is showing you that I understand pH and that I'm actually measuring the pH of various substances the other thing that I want to talk about is So feel free to mix up the procedure the selfies I want to talk about the selfies The purpose of the selfie the whole reason why they're in there really is about authenticating you Doing the actual lab work. It's it's just proving that you did it in a face-to-face class You're in lab. I'm watching you. I see you doing the lab or not doing the lab If you are just sitting on your patootie and not participating do I'm not giving you points for completing the lab like I'm Like sorry, but I'm there and watching the whole thing. So this is an irritating part of the online scene that is going to Accomplish the same thing that's accomplished by me being in the same room with you Which means You can decide how that is best going to work. I Want to know that you really did the work so if you're selfie the room suddenly changes and now the Data like the kitchen table is a different kitchen table I'm probably gonna wonder like dude whose kitchen table is that and where did you get that picture? Especially if you're not in it But if you've established yourself in your kitchen and You've got a selfie that has you in it then some of these things like you Your picture you can take a picture without you in it You can take a picture with your dog in it or your cat or your kid and Like I don't care like get the relax in fact, I think that's like don't be a perfectionist relax and and See how it goes if something doesn't work That's why we have our lab groups going on One of the things that I'm hoping to do in this week is to match you up in lab groups Kind of coordinated with when you want to do the lab So that you all can know that okay We're all gonna do our lab on Tuesday, and then we can talk about it on Wednesday, or we're saving the lab We're not gonna do it till Friday. We'll talk about it on Saturday that way people have others To talk about it at the same time, but if something doesn't work It's like talk about it come up with some ideas about why it didn't work This is the first time through so it's entirely possible. Don't tell anybody but things might not work That's okay. Like I'm not expecting you to spend eight hours on a lab Three would be my dream if you could get through this whole lab in three hours I would be so happy four might be more Realistic because of the prep that you have to do like you're gonna have to boil your Cabbage is in order to make a pH indicator and that's just gonna take time And I'm not gonna be there to answer your question So you're gonna have to think things through and you might have to ask your lab group for help like You're just gonna have to be flexible Okay, how are you I wish that you could answer that question There are Four sections to this. I don't know if I need to really like walk you through them all. I did make you data tables when necessary and Again, if you want to adjust the data table by all means adjust it like they all everything in here As you know is completely editable and so go ahead and edit away The buffer section I'm honestly, I don't know about my quantities here In the labs we have Hydrochloric acid and we're gonna try to use vinegar instead of hydrochloric acid because I figured that would be easier to come across We'll see if we can see it.  You can do this I'm gonna have you blow in bubbles You're gonna need a straw so you can blow some bubbles and some cabbage juice because you know you always wanted to blow bubbles and cabbage juice And then this is the first space where I've got a bunch of lab questions You are welcome to hash out lab questions with your group mates So if you were like dude, I got nothing on this lab question Take it to your group and see if the if your group mates can come up with something If you find you're in a group and nobody is talking to you Shoot me an email because the group component of this is really important And if your group mates are not coming to the table I'm gonna throw you in a new group and leave all those clowns in their own group to not come to the table. So Make sure that you're getting what you need from your group mates The last section, let's see what's going on here the last section I actually have multiple selfies in our face-to-face lab.  Whatever that means and then here's some more questions when you edit the questions when you answer these questions you're welcome just to edit this and Go in and type in your responses just right underneath each Question and you can format that however you want Again, don't forget that once you're done You have to go in and submit the assignments so that I know that you're done I can go in and grade this thing and assess how it went How do you feel? Can you tell how I feel? I'm feeling a little bit anxious about this one. I feel like I just want to make sure y'all are okay and That you are flexible and That you are not getting cranky because This is a process That we all are going to be figuring out and improving upon and it's what you're trading for the chance to do this online class if you aren't good with this one man Because they're all gonna be like this like this is what the labs are gonna be like Okay Huller at me if you have any questions and I'm actually excited like you guys This is good. We'll see how it goes. Okay. Have fun Bye