Mars is our second-closest neighbor next to Venus, and our spacecraft and landers have explored it in great detail. Iron oxide in the dirt and rocks gives the planet a reddish color. It's tilted like the earth, giving it seasons. Olympus Mons, its biggest mountain, is three times higher than Mount Everest. And Valus Marineris, its giant gorge, is three times longer than the Grand Canyon. On May 12, 2016, the Hubble Space Telescope captured this striking image of Mars. The planet was 80.5 million kilometers from Earth. This observation was made just a few days before Mars' opposition on May 22, when the Sun and Mars were on exact opposite sides of the Earth. This phenomenon is a result of the difference in orbital periods between Earth's and Mars' orbit. While Earth takes 365 days to travel once around the Sun, Mars takes 687. As a result, Earth makes almost two full orbits in the time it takes Mars to make just one, resulting in a Martian opposition about every 26 months. The next one will be on July 27, 2018. Given that the orbits of Mars and Earth are ellipses, and their orbital velocities are different, the distance between the two can vary from 55 to 402 million kilometers. That's 34 to 250 million miles. Back in 2003, the two planets reached a near-minimum distance of 56 million kilometers. The last time that they were that close was over 50,000 years ago.


Sim swapping attacks are one of the most vicious kinds of identity theft that regular everyday people might end up facing. What makes them so dangerous is the fact that they can be done remotely. The amount of access that sim swapping can give to hackers continues to grow every single day. And worst of all, sim swapping requires almost no technical skill on the hackers end. It's usually pulled off by just social engineering somebody that works at your telecom company, or in some cases, the hackers might actually have an inside man at the telecom company to help them pull off the sim swap. Now, usually the goal of sim swapping is to intercept the SMS verification and recovery codes for the online services that you use so that the hackers can ultimately take over those accounts. And if it just so happens to be an account for a financial service like a crypto or bank account, then of course the hackers are going to steal as much money as they can out of those accounts as well. Now part of the reason this is such a huge problem is because it's really difficult to even find an online service these days that doesn't require your phone number for signing up. Usually the phone number verification can help limit the number of accounts that spammers are able to create to make the platform itself better. And it might seem like a good way to be able to recover an account since people always have their phones on them. They might forget their passwords, but they're never going to forget their own phone numbers. But sending these one-time passwords and these recovery links over SMS is a really, really bad idea. Besides the sim swapping issue, SMS isn't encrypted, which means that anyone that's listening on the network could intercept those verification codes and those one-time passwords. Sim swapping is so easy to do and so lucrative that even young inexperienced black hats are able to make millions by doing it. One of the more recent sim swapping hackers to be caught is 19-year-old Noah Michael Urban, known by various hacker identities such as Sosa, Elijah, and King Bob. He was recently arrested in Florida for committing wire fraud and aggravated identity theft, which resulted in at least $800,000 being stolen from at least five different victims. And he is also believed to be a core member of the Scattered Spider hacking group that was responsible for hacking into Twilio's customer support console by harvesting employee credentials from a targeted phishing attack. This Twilio incident allowed the hackers to attack other services that leveraged Twilio like Signal Messenger, which used Twilio for their phone number verification service. And there were other supply chain attacks that were carried out by Scattered Spider against services like MailChimp that could have allowed the attackers to compromise accounts belonging to Digital Ocean or other similar services that utilized MailChimp for emails related to account info. And in addition to hacking crypto software and telecom companies, Noah also liked to use his sim swapping techniques to collect Grails, which are unreleased music tracks from popular artists. In particular, Noah liked to steal unreleased tracks from Lil Uzivert, Playboy Cardi, and Juice World. He even said that he had a dedicated folder to storing Grails that he had taken from these artists.  So this should give you an idea of just how much access a sim swapping attack can grant you. Phone numbers are the default account recovery method for most online services these days, including bank accounts. And a victim's personal phone number is oftentimes really easy to discover online or through database leaks from other services that have gotten hacked in the past. People really don't change their phone numbers that often and people don't actually use their phone numbers directly that often. Now what I mean by that is most people when they're communicating they use third party apps like WhatsApp that don't actually require an active phone number or a SIM card to work. That's why when people travel internationally they'll oftentimes use WhatsApp to keep in touch with one another without having to pay those really high roaming or international charges. So when a hacker calls your mobile carrier to get them to switch your phone number into their SIM card that they control so that they can then intercept your calls, you won't be able to receive regular phone calls or text messages on your phone until you contact the carrier to restore your number. But things like Signal, WhatsApp, Facebook Messenger, all those third party messengers are going to keep working like nothing happened. So if a sim swap attack happens to you, it could honestly be a few days until you notice that something is fishy which makes this attack so much more dangerous. So what can you do to protect yourself from sim swapping? Well because these attacks have been so rampant most cellular carriers at this point give you the option to put a transfer pin on your account. So that means that your phone number cannot be transferred to a new SIM card without that pin. You'd have to give it to the customer service rep over the phone or if you're going into one of the stores to try to do this transfer, they're going to ask for the pin as well and they might even ask for your ID if you physically go to the store. But the numeric pin codes typically are not something that's very secure. Like people have this habit where they like to make pin codes things like their birth date or their favorite football players jersey. And those are numbers that you could probably figure out through open source intelligence just through scrolling through their social media post. A hacker could put that together with just a little bit of recon. And ultimately the weakest link to a sim swap is that customer service rep at the telecom who is probably paid a low wage and has very little security training themselves. So the risk of them being social engineered or even bribed to transfer out a phone number is just too high for some people to take that risk, which is why I recommend opting out of SMS account recovery options altogether and instead of using a code texted to your phone for two factor authentication use an authenticator app instead. These apps work by letting you scan a QR code that's generated by the account server for the online service that you want to secure. That QR code contains a secret algorithm that lets the authentication server and your authenticator app generate temporary one time passwords or TOTPs that are in sync with each other without them having any direct network connection. So you're able to get your two factor authentication code on your phone even when you don't have any wifi or cellular connection or anything like that. The TOTP code is never being sent over a network. So there's no way really for a hacker to intercept it. In fact, the only way a hacker could get your TOTP codes would be for them to get the algorithm from the QR code that you scanned when setting up your account. And then they would put that into their own authenticator app and then they could generate these codes and sync with you. But that QR code is typically only sent once when you're setting up your account and it's typically sent over an encrypted HTTPS connection. So you should definitely get yourself an authenticator app and switch your online accounts over to using it as your two factor authentication method. Now there's a lot of options out there for authenticator apps. Personally, I recommend Aegis Authenticator because it's free and open source. It lets you set a password on the app itself so someone can't just get to your secret codes by just stealing and unlocking your phone.   So make sure you apply this knowledge and take the necessary steps to secure your accounts today. Like and share this video to spread the word to others. And if you want to support my work, consider shopping on my online store base.win where you can buy my merch and save 10% of checkout automatically when paying in Monero XMR. Have a great rest of your day.


Hi and how are you all today? The question says A and B are partners sharing profit and losses in the ratio 3 is to 4 respectively. They admit C as a new partner, the new profit sharing ratio being 2 is to 3, 2 is to 2 is to 3 between A, B and C respectively. C pays rupees 12,000 as premium for goodwill. Find the amount of premium shared by A and B. So let us proceed with the solution. First of all the old profit sharing ratio that was between A and B is given to us as 3 is to 4. Whereas new profit sharing ratio between A, B and C is given to us as 2 is to 2 is to 3, right? So let us find out the share sacrificed by A that is old share minus new share that is 1 by 7. Similarly, we need to find out share sacrificed by B that is 4 by 7 minus 2 by 7 that is 2 by 7. The amount of goodwill is given to us as rupees 12,000. So now we can find out is share in goodwill share in goodwill. Above we have found out the sacrificing ratio as 1 is to 2, right? So A is shared in goodwill is 1 upon 3 into 12,000 that is equal to 4,000 and it is 2 by 3 of 12,000 that is rupees 8,000. So the respective share of A is 4,000 and that of B is rupees 8,000, right? So this ends the session hope you understood it well and enjoyed it to have a nice day.


Hi everyone, Joe for Jaspy's casewrakes.com coming at you with the Rockets Thunder Grizzly's Net Sixer's Bucks Bulls, random number block randomized that's going to help fill the brand new impeccable basketball picker team too that just dropped yesterday. We're also giving away a full spot in this if you specifically bought a spot outright. Buy a full spot, get entered to win a free spot. So that's what we're going to do right now, big thanks Jeff, Matt and Han for getting into this one. One spot in six, it's got a shot. New dice, new list, name on top after three, we'll get the extra spot, one, two and three. Goes to Han, there you go Han. After three times, an extra spot going your way, also won all those spots in that mosaic filler pack too, mosaic 63. So now let's gather all your names again, put them into this list, I think I grabbed numbers, I did not. And there are the numbers one through nine and then zero. Now different dice roll, names and numbers two and a three five times for names and numbers one, two, three, four and five. After five we got Han down to Jeff, two and a three five times for the numbers one, two, three, four and five. After five times, we got two down to nine, we don't need this list anymore. So Han with two and one, Jeff with four, Matthew with six, Han with zero, Jeff with five, Han with seven, Han with eight and three and Jeff with nine. Now watch this, I'm going to alphabetize by a number and Han will still have seven, one and two, et cetera, et cetera, and zero. There it is, all matches up. All right, thanks everybody. I'll see you in the next video for the break, jaspyscasebreaks.com, bye-bye.


Everybody forced tier ripping 20 22 tops diamond icons baseball hobby 1 box number 47 random hits style So we'll type in hits as we go We'll do the random at the very end to see who gets what? Good luck everybody if there is 11 hits, then we will combine the two hits of The least value of the best I can Not perfect, but if we do a pretty good job of it, right here we go Again one box number what I say 47. Yeah 47 Still spots to go on the next one too It's a good point Rory. It's a good point. We're starting off nicely here Nice Manny Machado one-of-one patch card Great starts nice three color Padres patch there Manny Machado Good luck on that one. That's awesome, man. You got a cut signature now It is George high pockets Kelly four of four on the cut signature Legendary Giants first baseman George high pockets Kelly four of four good ol high pockets I'm guessing that's because he was tall George high pockets Kelly all right. It's going here nice Jersey Auto. That's gonna be cc. Sabatia 5 of 10 legendary pitcher cc. Sabatia 5 of 10 red parallel patch auto chipper Jones 205 Sick chipper Two-color braze patch on it that red color match as well. That's awesome Have a nice chipper Chipper Jones patch auto 205 Got an Eloy him and his auto for a five He's Eloy with the red ink Got icons of the diamond auto you're done Alvarez you're done Alvarez auto 14 to 25 It's good box so far Got a Paul Goldschmidt auto six of 25 Nice Goldie with the red ink to match the Cardinals colors It's gonna win MVP, maybe Maybe that's nasty Vladimir Guerrero, Jr. Two of five with another red ink auto Sick Vladdie Really good box a lot of really nice hits nice Vlad II of five a lot of red parallels and red ink You got a Sammy Sosa auto number 12 of 25 slammin Sammy Close up to it and a Greg Maddox auto 7 of 10 on the back of Hall of Fame pitcher Greg Maddox All right, that's 10 hits right there. All right, let's do the Random really good box man. Even the relic was a one-of-one and there was a cut signature All right 10 hits 10 names. Good luck everybody. Let's roll the dice There's a 10 will randomize the names and the hits 10 times put them side-by-side to see who gets what one Two three four five six seven eight nine and ten See Martin down to Tyler s and ten times on the hits. Good luck everybody one two three four five six seven eight eight nine and ten The Machado one-of-one patch to the CC Sabathia Jersey auto not refresh. Oh, there it is I don't just took a second. All right, see who's got what see Martin with the mini Machado one-of-one patch Jonathan and with the Chipper Jones patch auto two of five Peter M. The Jordan Alvarez auto brain Kate the Vlad jr. Auto to five Tyler asked a Greg Maddox auto to ten Harper has the Eloy and the Sammy Sosa will W Why that Cut signature George Kelly Rory with the Paul Gulchman red ink auto to 25 and Tyler s with the CC Sabathia Jersey auto gonna get these results posted to the site. Thanks again everybody another one boxer coming up next


Hi, my name is Chris Osmondson, welcome to the NCRAC Research Vineyard. The first vines we put in here were put in in 2013, we put in around 1300 vines. Since then we've added over 6400 vines and we're still taking data on more than 3000 of those. Every one of these vines is a wine grape, so they're a little different than the ones you see in the grocery store, they're a little smaller and they have seeds. But they're really good for making wine, which is what we're trying to do here, it's where the market is. They're all a little different than you would buy in like a nursery. These are grown especially from seeds and the seeds are hand pollinated and the parents are carefully selected. So we have a lot of the parents are from the University of Minnesota or the University of South Dakota, some cold hardy lines from Elmer Swensen in Wisconsin and they're crossed with select riparia or wild river grapes that have unparalleled hardiness and wine lines that are more popular, more people know about like Chardonnay. What we're trying to do is develop a wine grape that will work in North Dakota. We have grapes that will grow here and there's grapes that make good wine but there aren't many that will do both. And our season is short enough that we also need them to ripen quickly otherwise they're not much good. Since each of these vines is unique and they're grown from seed, everyone is tested separately. So once they grow fruit we'll take each plant and separately test cluster weight, berry weight, yield, sugar content, pH, flavor notes and if there's enough present which is about two-thirds of a pound will do micro-venification which is basically small batches of wine where you're making one bottle of wine at a time. And when those are done they're all evaluated by a peer group and the wines are compared to each other and only the best ones are kept. We've been really lucky this year with a grant from the USDA, a specialty crop block grant from the USDA and another grant from the Grape and Wine Association. We've been able to take on some really neat new projects this year. For the first time we've grown and planted in the vineyard here seeds that were specially created by the NCREC staff with material that was generously donated by Jeff Peterson from the point of view winery. And it's the thing that's really special about these is they have their start close to home. One of the parents that was selected is a riparia or a wild river grape that was discovered down in the Missouri River base and right between Minot and Burlington and the numbers on this plant are so spectacular that it's being used in research as far away as China. So it's going to be really exciting to see what they do and since we've started them here in the greenhouse and planted them out here we also have germination data and growth data that we were never able to have before. Another thing that we've done this year that's really exciting is we've taken our plants that we've grown here that have the best wine numbers the most promising vines and we've created mother blocks which is where you take a plant and you clone it and you get several plants that are the same. And since we've done that we're also able now we're going to be able to do wine studies on a much bigger scale than we've ever been able to before. We'll be able to study hardiness and if we're if we like what we see there's a chance that this will be a first step in creating and releasing the first wine grape that's ever been specifically for the North Dakota region.


Hey everyone, today we will talk about driving continuous delivery, trunk-based deployment strategy with Pipecity in large scale. So first of all, let me introduce ourselves. So I'm Yoshiki Fujikane. I work as software engineer from Cybiagent and currently we belongs to the developer productivity teams and I'm a member of Pipecity team. My name is Ken and I'm from the same team with Fujikane. I'm software engineer at Cybiagent and maintain our Pipecity project. So first of all, let me express my gratitude. So this announcement would not have been possible without the cooperation of Abema's back-end teams. Thank you again. Okay, so for the agenda of our speak today, first we will talk a little bit about productivity and durability. Second, we introduced the Pipecity, a tool that realized the progressive delivery with off. And lastly, we send you stay, the chunk-based deployment with Pipecity. So first of all, I would like to introduce a little bit about the Abema, how you skate today. The Abema is serviced from our company Cybiagent. Abema is famous video streaming service in Japan and we handle various content such as anime, drama and sport. We have, we are leading traffic handling service in Japan. We serve around 30 million user activity and for the development side, we have a back-end engineer team with around 20, it's about 12, 20 members and we handle about 130 microservice of many guys. We still in the growing phase and the more productivity and the more reliability is the better for our growing as a service. So why productivity and reliability are important? Productivity is mean for delivering the new values, the new features, the new bug fix, new thing to user. Why reliability is providing stable for existing thing that's serving user already. So it's not about productivity or reliability. We think that it has to be both, it has to be productivity and reliability and we have to find a balance for them. So we think how we can actually ensure productivity and reliability for our service, how we can actually balance them to ensure that our service growing good. We investigate it and we realize that track keeping are required. We introduce chunk-by-deployments and the mean for ensure productivity and progressive delivery as the mean to ensure reliability. So for the chunk-by-deployment it's a well-known deployment method. We develop a small and frequent PR to update a core chunks or a main branch. This allows the significant reduce the time it takes to resolve the conflict between the revision from different reviews. We all know that the resolve conflicting is not an easy work and it slowed out our team. Secondly, for the progressive delivery is about gradually rolling out the feature to the selected user. Developer and DevOps team can increase incrementally roll out and deliver the new feature with fine gain control to a small group of users to minimize the risk of pushing new feature to the production environments. And it's not just new feature. It's maybe new bug fix, new things, everything that we face in the daily life of engineering. For the progressive deliveries, we have two well-known methods which is canary deployment and bugging deployment. For the canary deployment, we have full control of how many percent of traffic we do to the new feature and how many was still serving by the old workload. And for the canary for the bugging deployment, we have kind of switching things between new and old workload. And it's not just like that. We need progressive deliveries, we need canary deployment, and also we need the board for all of our services. It's kind of specific problem with our infra, but we have a requirement for the monthly platform. Our system consists of many different components and we have several elements for monthly platform. For instance, API workload, we are using QRities on the managed cloud like ZKE or EKS. And on the other hand, for the batch workload, we use serverless things like LLS Lambda. We want to realize progressive deliveries for monthly platform. That's why we choose PyveCD. So a little bit more information about PyveCD. The PyveCD as a vision is the one CD for all application, platform, and operations. It's a bit of style CD solution. Currently, it's support deploy application to multi-platform. Most of our using platform is supported by PyveCD, such as QMTIS and AS Lambda ASI. Next, PyveCD supports progressive deliveries in mice, so that it's really easy to get in. Lastly, PyveCD is already a CNCF sandbox project. So now let's take a look at some actual use cases. We will explain trunk-based deployment using PyveCD after a demo. So we know the session title is trunk-based deployment, but we also mentioned previously that we need not only trunk-based deployment, but also progressive delivery pattern to achieve our needs for the previous productivity and reliability for our product. And great free PyveCD can help us achieve both. We will show you right away. In our demo, following trunk-based deployments, we separate the feature branch from the main branch, and we will work on this branch to keep the changes as small as possible. Additionally, we speed up development cycles by encouraging culture to review PR as a priority. Up to this point, this is standard deployment development that follows so-called trunk-based. However, ABMA has taken another step to further improvement deployment development efficiency, and the point is to merge functions into development plots at the same time. Let's learn about this while looking at actual CI CD configuration diagrams. So this is ABMA's CI CD flow. Let's take a closer look at each steps. First, create PR. So developers first make modification to branch based on the main branch and create a PR here. And once created, CI will automatically commit the version fixes required for PRD release. And this will cause development to begin when this PR is merged. Once the PRs are merged, CI creates artifact for deployment to production. At this time, artifact information is notified to 5CD as an event. By adapting this architecture, CI and CD are root-free couples, and each one does not need to know authentication information. From here on, the behavior on the CD side, 5CD updates the application's manifest files based on the event it received. And this is a feature called event watcher of 5CD. When defining an application managed by 5CD, you can define what behavior will occur in response to which event. And specifically, in response to certain events, it is set to update the image name of the corresponding file and the commit. And this saves you the trouble of creating a fixed PR for your manifest version. And 5CD regularly checks for changes in the manifest. So after a certain period of time, it will detect the difference in and change and reflect them in each environment. The sync strategy is different between dev and broad, so I will explain it next. So 5CD has two main sync strategies to choose from. One strategy is called Quick Sync, which simply updates the differences to our application. Another strategy is called Pipeline Sync. And you can create your own pipeline by combining stages provided by 5CD. And Abema mainly use Pipeline Sync to configure a pipeline that can achieve progressive delivery. Let's take a look at Proto and Dev Pipeline. At first, Proto. Abema's production environment uses Canary release. And first of all, we will release a few percent of the number of replicas as new version Canaries. And next is the analysis phase. So check the error rate of Canary for about 15 minutes and make sure that errors above a certain level don't occur. And this enables progressive delivery. And this feature implemented as standard in PipCD is called Automated Deployment Analysis. Based on the metrics stored in Prometheus and Detoc, you can determine whether the correct funding version of the application is normal. And if an abnormality is detected, you can automatically roll back to the previous version. And next, if ADI determines that it is normal, we will change our application to the new version after obtaining the final approval of the person making the changes. So after all, release is finished. So on the other hand, in the Dev environment, the first step is to roll everything out to the new version. This is Dev environment, so there is no need to do Canary strategy. After that, we analyze it using ADA. And if there is a problem, we immediately roll back to the older version. So let's go back to the previous question. Why match to Dev Proto at the same time? So this is because the lead time during deployment can be further shortened. I have illustrated the flow from the actual match to the deployments of Dev and Proto. While we are checking the operation in Dev environment, we are preparing to change the Proto environment to a new version at any time. If we discover a problem with the Proto at the time of ADA, it will automatically roll back and minimizing the impact on the production environment and minimize the time to release. So ultimately, we have recently been able to achieve average 22 release per day. And this means that the members currently involved are releasing at least once a day. And furthermore, this is the result of checking the latest recording on the PIPCD console. We can confirm that the development cycle is running at a very high pace. So currently, we are implementing this for some projects, but we hope to expand the scope of applications in the future. So thank you so much. Thank you for listening. Thank you all for listening. We have official sites at PyCDR Dev and live demo at play.pycdr.dev. So everything is up online. Just give it a try. Thank you.


doesn't. Yeah, go ahead. Okay. So when you look at what we get in the 15 line, not the pro line, yeah, it's basically the 14 pro. Yeah.  And you have the 15 pro and the 15 pro max. So what sets the 15 pro apart for for most users? Exactly. It's the 15 pro max that's different. Because only a little bit, right? It's got the 5x zoom instead of 3x zoom, but that's it, right? Yes, but it's also the one that lets you do the spatial videos. I think spate. Okay, so we haven't talked about this, but there is a way to do spatial videos. I thought that was the both pro models. If it's both models that that that totally knocks my someone will correct me if I'm will tell us which one of us remembered it correctly.