Hi. Hello. I just wanted to thank you all for coming to our session on how you can build passive income by selling Pantheon to the friends and family who already need it. Oh, yeah. It's a great turnout for our Spon Con. Thank you for coming to a sponsor. This is the most people I've ever seen come to a sponsored session. So I feel pretty good. For those of you who don't know us, my name is Josh. This is David Strauss. And we're co-founders of Pantheon. And we were there from the beginning, built a lot of stuff together. Now, we're working on the next generation. And if there are any direct competitors, can I just ask you to not be kidding? We are going to explain what we're doing with the next generation architecture. And it is kind of a little like if you want to copy our whole business and try to beat us to the punch, this is the playbook. And what we do is show in the spirit of openness, transparency, trying to show the way, because there are lots of people who are trying to solve these same WebOps type of problems as we are, but can't use our platform for whatever reason. So if you have to do it yourself, this is not a bad place to start. It's all about moving on up. So that's just what I said. How do we reinvent ourselves, reinvent ourselves, or are in the process of reinventing ourselves on GCP? For those of you who don't know about Pantheon, we emerged from the Drupal community, founded in about 2010. Today, we have around 20,000 active users that are regularly engaging with the platform, building websites, launching websites, maintaining websites. The websites running on Pantheon reach about a billion unique visitors monthly, a little bit over now, actually. We power Drupal sites. We also power WordPress sites. And we're now powering JavaScript-based frontends, whether they're attached to a Drupal or WordPress backend or just running on their own. And our engineering team has grown to over 100 full-time engineers, plus designers, product managers, QA, and other stuff. So we've got a lot of momentum behind this thing that we've been working on. And we're very proud of it and happy to share with all of you. David, I don't know if you can read it. No, I think that sums it up great. OK. And we've got cool new colors in our graphic design scheme now, which I'm super thrilled about. This is way better than just yellow and black. So we'll do a little bit of history, just so you can set the stage and context. We had to do create a really significant amount of net new technology in order to deliver Pantheon originally. Sort of between 2010, when we first got started in 2013, 2014, we invented a lot of stuff. And it's because we didn't have the camel case word for it at the time, but we were trying to deliver this idea of web ops, which is, hey, everybody should have a totally scalable production environment.  And you can't do those things if you're delivering a platform in the old way at the time, like it's still the state of the art in many cases, is slinging virtual machines, building clusters. It's just not possible to replicate architecture affordably, I guess, at that scale. Your point around generosity, I think. Yeah. A lot of it we conceive of today on a different, more like financialized perspective. But from the beginning, it's always been this concept of us being able to be generous with customers, because if the infrastructure costs can be maintained well enough by us, then we can be generous to customers in terms of being able to build tools like multi-dev, because it means that there's fundamentally an easier problem to solve around the continual cost of that infrastructure, around the capacity planning for that infrastructure. And we've been able to get our efficiency to some really interesting levels with kind of scale to zero style tech around the stuff that we've been doing for 10 plus years now. Yeah, and at the time that we started, like we had to kind of roll our own for an awful lot of things. And we wanted to be able to sustainably give away free sandbox sites. We wanted to be able to give people as many development environments as they needed. We didn't want to have to charge extra for those things. In order to do that sustainably, not just lighting a bunch of VC money on fire, you have to figure out technology that lets you do that in a sustainable manner. So we had to dive deeply into container technology. At the time, Docker didn't exist. It was a different startup that hadn't pivoted yet called DotCloud. We built and run still due to this day, honestly, our own Git infrastructure, because at the time, in 2010, 2011, Git Hub had data all over it. We were pretty sure that Git was the winner, but Git Hub was one of a few things. And we couldn't force people to sign up for another product just to use ours. When we first started, we used Rackspace as our underlying infrastructure provider. And we did that because AWS was slow as balls at the time, where they had very, very poor disk speed and not so great CPU speeds. And we wanted Drupal to be fast. So we did put extra effort in to let us use kind of a more old school infrastructure provider because they could give us solid state disks and faster CPUs. The orchestration of this involved like marshaling an army of over 500 Jenkinses. If anybody's used Jenkins, it's a pretty cool tool. You're using 500 of them coordinated together. It's also pretty cool, but it's a lot of work. The Hudson project finally closed shop, by the way, for anyone who's old school or not. You remember RIP Hudson. We can pour one out. Yeah, Larry Ellison finally did it in.  It was a moment where we realized that there were no good network mounted file system options for the scale we were looking for and the agility we were looking for. We were sat in this room and it was like, do we have to write our own file system? Yes. Yes. So we did all this stuff, right? And we're trying to get rid of as much of it as possible because the truth is that the, oh, and we are making progress getting rid of it. So one of the things that we did originally was we had varnish integrated in the stack, like every website had a varnish in front of it because that's the way it should be. But that's something, you know, we don't really wanna run that if we can help it and wouldn't it be better if varnish was distributed around the world rather than just being on the, just located with the same stack of resources of serving your Drupal website. So that's what we did with Fastly. We partnered with Fastly starting in 2016 and let's encrypt. So you got HTTPS out of the box as soon as you point your domain name at Pantheon and it's globally distributed and this cache and validation and like all that stuff just works. And this is actually a way for us to reduce our operational overhead, lighten our burden while delivering more benefit to developers and customers. Yeah, and I think one of the biggest things I like to point out about the value that we've achieved here is that it's not just like an additive thing of like one plus one equals two here. This is more like a one plus one equals three with the integrations that we have because you don't want HTTPS deployed to just your origin for your main website. You want that deployed to the edge. You want the integration between the cache and validation and your content sources. So we've been able to ship a lot of integrations that I think that no matter how big the budget has been for our project, I don't think it's ever been done with Drupal outside of the sort of integrated stack that we shipped this stuff on. Yeah, I'm sure other people have done it on one-off basis, but we make it easy out of the box. The other thing we did was find that we were like, okay, Rackspace isn't it. And they told us that too, that they were like basically getting out of the business. They ran up the white flag and said, we're just gonna be a support company. We're helping all of our customers move to these clouds. Can we help you? And we said, no, we'll figure it out on our own. And we moved all of our workload from Rackspace to Google Cloud Platform, which we're gonna talk about more in depth here. The bulk of that migration occurred in 10 days. The time scale on this is not July 2010 to July 2022. It's just July 10th to July 22nd. Summer of 2017, moved like 45,000 active websites in two weeks. A lot of work and planning went into that, but we were able to, as an example of the operational efficiency we get with our platform at the level that it's abstracted. And it was also really good for us to move up to a infrastructure provider in GCP that could offer us a lot more than just slinging fast virtual machines. I don't know, David, you wanna talk to like how we chose, why not Amazon? Like what? Well, I feel like we'll, we will get into a lot of the details of that, but the fundamentally like GCP is built from the opposite direction of AWS. In the sense that AWS started off with virtual machines, started off with cloud storage and block storage, and then built all the services upwards from that. Google, on the other hand, was building upwards from, building from different foundations, foundations like Bigtable, Borg, things that were already sort of internally utility managed services. So their conception of how infrastructure works, particularly data and on-demand compute is just fundamentally different in the sense that it's less around stamping out footprints of infrastructure and then dedicating it to a purpose and more about reconceiving of the implementation of infrastructure so that it fits a model that is then scalable and deployable on a more dynamic foundation. So yeah, they, the Amazon Smart Move to meet the market where it is, like move all your machines to the cloud as virtual machines, but Google sort of is playing a longer game and we think that has the potential to leapfrog them and is doing so with some of the services they offer. And really like the interesting thing is, so I'll just back up for a second, this graph was the graph of our moving, but it was a lift and shift move. We went from virtual machines at Rackspace to virtual machines at Google and with the idea of moving providers, making sure everything still worked, making sure all the networking was good, and then we would be able to thence forth, invest in modernizing things as we were able to leverage things from Google. We did a lot of that internally over the past, the first few years, because like our internal engineering organization, and frankly is still getting benefits from being based more like Google cloud native, but we're finally getting there for our customers, where we're able to leverage higher level things at Google that can deliver the same value that Pantheon delivers with its proprietary technology and potentially more, which is what we're gonna talk about. So starting with this idea that as we are able to deliver in this next generation context, we can draw a Google project box around every single customer, which gives us like a future ability to be flexible, which is really, really enticing and interesting. And this is again, kind of something to be hard to do with a different cloud provider. It was kind of a surprise to us that we could do this because we basically started designing these tools and looked at various quotas and limits on GCP projects, and we're like the only way we could possibly make this work is by just spawning thousands of projects on GCP. There's just no way that could happen. And then we talked with them and they were like, no, that's totally cool. So like we have built our whole approach around some of these new products around basically stamping out extremely isolated infrastructure at the project level, but built from these sort of scale to zero foundations that allow a mix of isolation and efficiency. Yeah, so the benefits will be that, you know, we'll have flexibility, we'll be able to offer stronger guarantees to customers. Like right now today, with our proprietary technology, we have this like big, one big platform that all of our customers share. In this next generation model, we'll be able to give people much stronger guarantees around their resources, their network space, their data storage, and like Pantheon's very secure. Like I have no real worries about people like getting at each other's data on our shared platform, but you gotta kind of take my word for it. And you all know I'm trustworthy, but not every CIO knows that I'm trustworthy. And they've only got 30 minutes to make the decision. So it's way better for us to say, Google's got it. You know, they're at the level of assurance they can bring it significantly higher. And we didn't take these approaches previously because a lot of them would require stamping out pretty lightly used infrastructure on a wide scale and cost inefficient basis in the sense of, it just doesn't make a lot of sense to deploy infrastructure that's gonna be used five percent of the time or five percent of its capacity on an exclusive basis. But like we're no longer forced to choose between these things. Yeah, we can kind of have our cake and eat it too, which is great. And the other thing that's nice about this is not just the efficiencies that David's talking about like costs and our ability to offer things for free or not have them be like metered or like with additional environments, but also the agility and the quickness with which we're able to deploy these things. Like again, at the time when we were first designing Pantheon, we wanted to give people on these teams doing the web ops, as close to a real-time experience as possible. It's not instantaneous, but like spin up a new project in just a couple of minutes, give another environment and let it get 30 seconds or less. That sort of speed to provision is now also where these cloud platforms are, whereas, even just like, I don't know actually, I haven't run any benchmarking, but like still stamping out a new virtual machine from a machine image can take one to five to, sometimes it's like an indeterminate amount of time, which can be really frustrating for users when you're waiting for a thing to provision. But let's get into it. Let's get into like what it is we're actually doing. So the first thing we're doing is we're embracing cloud build as a cornerstone of the new architecture and the new developer experience. Importantly, this means that you will no longer be forced to use our janky git infrastructure that we stood up in 2011 and haven't really modernized since. You will be able to bring GitHub and friends shortly to the equation, which is what everybody wants now. We realize that our git infrastructure is in the way and we're gonna get it out of the way so that people can bring wherever they prefer to do, that whichever of the popular social coding platforms they're using, they'll bring that, connect it to Pantheon, which will connect the cloud build, which will run all the processes to deploy code when it's pushed, when a pull request is created, when a branch is created, et cetera. I don't know if you have anything to add. I'm just trying to think of a joke about us opening up Bizarre again as a coding platform. But the app... That's right, secret subversion support. No, never again. So what happens in cloud build? Cloud build is a, you can think of it as, this is a replacement for the army of Jenkinses. It does a build process and will deploy. It will deploy to Cloud Run. Cloud Run is ready, we think, and our early testing confirms this, to replace our main, the number one thing we spend money on Google right now, which is our massive container matrix that runs all the PHP environments. And this is something, again, that we really can only get from Google. The equivalent, nominally competitive tech from the other cloud platforms is still one or more generations behind. Primarily in the ability to do things like scale upward and downward, in the sense that we can deploy things onto Cloud Run, have the container image available, and have it actually scale down to zero containers deployed. This is less important for production environments where we might actually still force a minimum of higher than zero. But when it comes to pre-production environments, our ability to provide features like multi-dev, it's important to be able to deploy a stack and not have that stack sitting around, doing almost nothing except for when the developer's working. Yeah, and be able to create more on demand and not have resource limitations around the stuff. Cloud Run, and Cloud Run also performs really well in all of our benchmarking and so forth. And it's only recently gotten the maturity it needs to actually handle the full use case that a Drupal runtime would require. And then, of course, there's some things that we had to invent ourselves, so that this is offline in our container tech. It's not all Google. We're still deeply investing in our relationship with Fastly. They have a new project product, which is called Computed Edge. Think of it as a way that you can, anything you can compile to WebAssembly, you can deploy to Fastly, and they will run in the same computing environments where they run their varnish. So basically, it's a way to deploy a lightweight application to now upwards of like 80 points of presence around the world. And this will allow us not to retire because we're still gonna have an application that gets deployed there, but to really move, again, up the stack, our routing technology. That's, I didn't, wasn't a bullet on the other slide, but we had to figure out a routing approach that would allow incoming requests to pantheon to then be sent to the right ephemeral container instance on our proprietary matrix. And that's like running, depending on what time of day, a week between 800,000 and 1.2 million different runtime containers. And it's like there's not a lot of like regular load balancing tools that will take that job. So we had to invent some of our own technology there for load balancing and sort of like managing self-healing and other stuff like that. We'll be able to push that up to the edge. And it means that a request will come in, get terminated on TLS, go to some of the caching configuration, and then ultimately, if it's missing the cache, we'll get routed directly to the Cloud Run container pool that will serve that request without having to go through any additional layers of say multi-tenant load balancing. Yeah, and it lets us do pretty neat things in the future around like potentially targeting load geographically, being able to actually spread applications out across wider areas. It'll be pretty cool. There's actually some, I would say also, like we're not gonna use it, but there's some pretty good stuff if you're thinking about large scale routing, like in open source, it's also catching up to what we had to invent ourselves, this tool we called sticks, which takes a request from the land of the living to its, what did you say? Well, to its final destination. To its final destination. Yeah. Like the stuff that they're coming up to with now with Istio and parts of the Anthos framework, they're able to handle that type of scale now, or they're getting close. So if you have that type of problem, you don't have to use fastly or computed edge. There's an open source solution that's pretty good in that regard as well. I think we actually kind of anticipated Web 3 with sticks, because like the whole concept is that you're supposed to pay like a token to the person who's running the, I forget who runs it, but in the mythology, but like you pay a token for your request to go through. Right, yeah, to get over it. I think it's a fungible token though. A fungible, okay. Yeah, okay. No, no, no. Anticipated, anticipated. We're riffing, it's a joke. So then, okay, like behind the runtime, behind the PHP environment, there's all the other stuff that Drovo will need to talk to to actually serve content. And there, it's like, this is more, this is frankly more commodity, right? Like, you know, cloud-based SQL. Lots of people have that. A key values store. Lots of people have that. Search backend. We're really conscious, we're really, really thinking about making Elastic our go-to rather than Solar for the next generation. There's just much, much wider support in the broader, off of Drupal Island for lots of things around Elastic. And I think we could probably help level up some of the search capabilities within this community. And you know, I'm not saying this is for sure, but we're definitely considering it. But these are all things that we can just assemble and orchestrate from Google Cloud without us having to manage the underlying infrastructure and machines so that we can, you know, the punchline on all this is that we can get more of our engineering organization up the stack, which means they can focus more on things that are gonna matter to you versus just making sure that the platform is stable. Which of course everyone cares about, but it's not that strategic. Yeah, not much to say. Not this one. Yeah. And then the nice thing about Google is they have this cool marketplace capability, which then lets you bring in other services. So whether that's, you know, if you are like really into solar, search stacks is here. They're great. They do the really good job at delivering solar as a service. And they're available through the GCP marketplace. So in, you know, in this future world of Pantheon, if there's something that you need that we're not providing out of the box, you'll have access to this marketplace to be able to get it and have it plug into, again, that project that's gonna surround your application on Pantheon. And it will no longer be this somewhat more complex thing of doing weird secure gateway stuff to connect other services. And this also goes for the other cloud services at Google. So for instance, a lot of people are using like Google's big table. If you do anything with even medium data, let alone big data, big tables just fricking awesome. And BigQuery is even awesome because it gives you this great interface on top of it. And you can write SQL queries that have embedded machine learning models in them to do predictive modeling and so on. It's really awesome stuff. And so like we have some customers that are really leveraging that with as part of their web mission and their web project. And wouldn't it be, it'd be way better for them if they could just plug that in to Pantheon versus having to do like a rather, again, convoluted data extraction and load process today. Yeah, yeah. Simply by conceiving of our projects and deployments in a way that is sort of more legible to GCP and its integrators really makes those available much more directly off the shelf both to us and our customers. And then we return to the file system which we codenamed Valhalla when we created it and we still are probably gonna have Valhalla. Yep. We have done an experiment on this and we've used, we've tried out like Google's off the shelf file system which is file store. Works great. Has a minimum of two terabytes, has no copy on right and has a whole bunch of other limitations where yeah, we can get a site running but to truly provide that sort of Pantheon great experience from a workflows perspective and the ability for us to just spawn these environments out. This is probably one of the few places where we're gonna have to keep some of our tech. So yeah, and we're evaluating, like we have a good, we got like a red phone line to the folks at Google now because we worked them for quite a while and we're partners but I don't know if they're, I don't think they're gonna be able to solve this problem on our timelines. We'll probably end up having to solve it again. That's okay. So and the other thing is, this is our next generation Drupal infrastructure that we're working on. This is also the current generation of the infrastructure we're using to serve JavaScript front ends today. You can see it at the booth. Steve's got a great little demo of what this looks like. You connect your GitHub repository, it goes through Cloud Build, deploys to Cloud Run and we handle the routing at the edge. So like we're, we don't have any of the content services in here. There's no like database or file store or anything yet but this tool chain is being used in production today by customers who are running JavaScript front ends on Pantheon. So I'm gonna hand full of customers now because we're still in the very early phases but that's gonna open up a lot over the summer and we're gaining confidence in this architecture because we're putting it into production now and we expect in the next year or so to start to put CMS sites on the same type of architecture in production and eventually it'll become like our default or probably our default or go-to architecture. And we're keeping some of the Pantheon goodness in this sort of process too. Like rather than it being a dashboard where you see your Git branches from our repositories and then can promote them into multi-dev environments, we have it tied in with the pull request process. So like you create your branch, you do a pull request, that fires up a new stack out in Cloud Run after doing the build a process and then you get a URL so you can go to the stuff that is representing that branch. So like we're still keeping the whole fork the stack kind of capability here. Yeah and so and you know this involves us owning different pieces of technology. So now we run a GitHub app and we have a whole abstraction layer so we can do GitHub, GitBitBucket and GitLab and we have to manage events across all these things and we have like a whole orchestration layer that is, we had an orchestration layer before but it's more complicated orchestration layer now. But it's better, it's better because we can, we're moving our engineering resources closer to the things that you and your customers really care about and we're able to kind of offload or outsource a lot more of the very drudgery oriented end or high stakes security wise labor to Google who are pretty good at this so we can trust them as a partner and so I think it's a way for all of us to continue to evolve and get better at the work that we do. I believe that is the presentation. We just sort of whipped through it. We're happy to answer any questions you have about this content or anything else if you just want to jibber jabber we're happy to do that too. But does anybody have a question? Show of hands? Yes. So the question was, is there a difference in pricing when it comes to the jam stack approach versus doing things traditional way in Drupal? The answer is yes and I don't know exactly what it is yet because that's one of the things that we're figuring out. So show of hands, how many of you all have used Netlify or something like that? Yeah, OK. So I'm very interested in understanding, I think they have a great product and basically we want to compete with them and we want to compete with them and bring Drupal and WordPress to the party too. I think the way that they price based on how many seats you have, how many environments you create, how many build minutes you use has been, I've talked, people find that frustrating because it's hard to predict, it's hard to understand. It is tied to their underlying infrastructure costs so I get why they do it, but it doesn't seem particularly good for customers. So we're in the process of figuring out what does pricing for a good jam stack product look like. And I think we're gonna try to keep it simple. I think certainly for simpler projects, like the cost basis should be low because it's, you know, especially if it's a static site or something like that, it's like pretty easy to run and scale. But we don't have that 100% figured out yet today. But if, you know, open to hearing people's thoughts about it for sure. Yes. Is there a next generation varnish on the horizon? I don't think that there's a next generation varnish from a tech, like a new caching technology in terms of like really the work is more, honestly from a performance standpoint, if that's kind of what you're thinking about, the work is more in optimizing how people actually build their front ends so that when, like what varnish can do, and it does a really good job. It's hard to imagine something being that much better. Like fastly is varnish in a local point of presence. And it will send you the bits as fast as it fricking can in response to your request. So there's not much upside to be gained in sending the bits faster or from a closer location. But the contents of those bits and how they're interpreted by a browser is where the battle for performance is being waged right now. So like understanding how to make that payload as small as possible, ensuring that it's all the images are optimized, that there's not render blocking JavaScript in part of it. It's more about like actually thinking about it from how a web browser or user agent runs and optimizing kind of the execution of the payload, not the delivery at this point. It's a good question though. And in case this is at all flavoring the question, we are still continuing to partner with Fastly for the delivery of the infrastructure for decoupled front ends too.  The question was, does the current composer build process already use cloud build? And the answer is sometimes? Yeah, I think it's sometimes. We have an abstraction layer above that build system that is able to use different delivery back ends among them cloud build. And I'm not sure where we've turned the knob on that yet. It's less of an implementation thing and more of a cost and isolation control question. Yeah, when we first implemented it, the answer is no. And what we've been doing is looking at ways to embrace, moving up the stack, moving on up and leveraging kind of configuration and implementation around cloud build as a generic job runner, which it can totally do. And so today, I'm not sure if 100% of the composer builds go through that process, but that would be our aspirational goal for sure. I can say 100% of the builds for our decoupled front end go through that. And those builds happen in the same project that they get deployed to. There was a question here, yeah. The question was, are we planning to continue to support upstreams generally as part of this? The answer is yes. We didn't talk about it a lot in here because we're kind of talking about like the hosting part of Pantheon, but the value propositions that we bring that are actually differentiated from hosting, in my opinion, are about productivity, principally like multi-dev, dev test live, work close, stuff like that. And then the ability to manage a portfolio at scale, which is really like the ability to have like one code base that you can deploy a hundred times or a thousand times and manage a release process around and so on and so forth. And so that we're 100% committed to keeping. This particular details of like, okay, well, how do we link a GitHub repo and like are we helping people manage their own GitHub repo sort of hierarchy or are we still last-miling it? I'm not sure yet. We have to get through a lot of the details and kind of product development there, but that value proposition of being able to manage many, many, many, many, many instances of the CMS that are mostly the same, although potentially a little different as needed, is gonna be something that we're very focused on continuing to deliver and hopefully improving. Like frankly, when we have this next generation build pipeline in place, we should be able to make real products around release management. So, you know, people do this on their own with Terminus, but like, why doesn't, wouldn't it be cool if Pantheon lets you tag three sites as your Canary sites and auto deploy to them first and like autopilot tested it for you. Like wouldn't it be cool if there were some other sites you could mark as like hold these until the very last because we know they're heavily customized or highly sensitive sites, right? Basically helping people do common deployment workflows at scale with some like, you know, kind of opinionated approach in the same way that we have an opinionated approach to like releasing sites for a particular, releasing changes for a particular site. So long answer, it's gonna get even better, short answer, absolutely yes. Yes. It's not a lot of faster. There's not a lot of gap between the compute resources that we're already deploying today and the kind of compute that you're going to get on something like Cloud Run. CPU is usually the bottleneck for the PHP side. For the database side, it's usually, you know, memory and IO throughput. We may see some improvements through Cloud SQL in the sense that there's some joint optimization between the persistence layer and the database engine on top, but from our own testing, we're actually seeing pretty parity like performance. We, one of our earliest evaluations of this stuff was wire this all together, deploy a Drupal site to it, throw some new relic on there, develop a load test plan that touches the different aspects, everything from file creation to database rights to content create, regular content creation in the database. And we benchmarked it and it's basically a parity. Like this is definitely not motivated by unlocking a new tier of performance. It's more about the capabilities of the infrastructure, the reliability of it, modernizing aspects of the developer experience, and ultimately being able to refocus some of our efforts higher level in the stack. There's a lot of speed in those. Oh yeah, yeah, yeah, yeah. So I think I'm not gonna promise because again, we are gonna have to build a more complex orchestration layer right then we currently have today, but if we do a really good job there, it should be able to give you new environments faster. And in particular, as we, some of the bottlenecks in the experience around that to be totally transparent, just don't point and laugh too much, it's actually the user experience part in the dashboard. Like it's our own JavaScript app that's not optimized and we're replacing that too, but it's not really part of the story. So yes, the developer experience and how long it takes to go through these workflows, we absolutely wanna bring the time down on that. Like we're absolutely looking at like what does build time look like with Cloud Run? There are some things that we can do faster. There are some things that might get yeah, just a little bit slower, but like we're taking a really close look at that and are doing our best to make it like so that there's no degradation. And in some cases we may choose confidence over speed in the sense that we would very likely choose an approach that is like 99.9% successful in its completion rate over one that's faster, but is like breaks 10% of the time. Yeah. The other thing I would say that is almost certain as we get to deploying this for CMS sites is the deployment pattern that will take as a default will be similar to the one that we're doing at the Jamstack project, which will mean that there's no requirement to go through a test environment before you get to production. You'll go directly from feature branch, if you want feature branch to production. And the first environment that spawns is attached to your default branch and get and then that is what you sort of fan backwards from in terms of your development process. There is yes. Yeah. So the question is maybe more about like, you're talking about like the demo that we have at the booth. So the approach that we're taking and it's about like, well, what is this thing you're talking about with personalization at the edge? So I can give you my best answer on that. The approach that we're taking to content personalization is one that's based on really observing what has not worked well in the market over the past decade. And that actually takes several forms. There's certain technical challenges that we can solve with the architecture and doing things at the edge instead of in the user agent that are gonna make it easier to guarantee a good user experience. There are certain things that are strategic. Like you get a lot of people who buy personalization tool without a clear use case and lo and behold, a year later, they're not doing much with it. That's something that our marketing and sales team can help guard against and we can try to give people more opinionated product. But in terms of what it is we're actually doing there, we're building into it. So the product we have today is really a software development kit. So it assumes that there's gonna be significant implementation done because you need to wire this up to your content editor stack in Drupal. Like are you a paragraph shop or are you like, and what we wanna do is make it as short and easy as possible to connect, you can think of it as the pantheon component is all the tricky wiring between the CMS and the edge to do this orchestration and cache variants and identify audiences and deliver the right variant. We wanna make that something that's like people don't have to think about too much. But you do have to think about where your content editors see the option to switch from one experience to another. And we've talked with enough people and there are enough diverse opinions about the right way to do this that we didn't feel like the place for us to start was to say, here's the thing, this is what your editorial users must use. I think we'll probably get to a point where we have something that's like, if you want it, you can use it, but it will be built on top of a, in kind of like the Drupal way, an SDK level module that you can do your own custom implementation on top of. Because some people wanna vary each paragraph. Some people might just wanna switch to a whole different page. Some people, you know, there's like a lot of different use cases. So, and we're kind of in learning mode to be totally honest. We're looking for partners who have projects where there is a clear use case so we can help them deliver quickly on a successful use case and then close the loop a couple of times and we'll develop stronger opinions. Yeah, we basically want to improve that dynamic content assembly process of the edge, which reminds me like, how many people in here have successfully deployed ESI as part of their websites? There we go. How many people have? Exactly. How many people have had a conversation about using ESI as part of their website? Okay. Well, maybe it's worth. Well, it turned out to be so ineffective that I think it actually fell off the like Overton window of plausible like perfection methods for Drupal sites. It's true. But there was an era where we were all about this thing of like edge side includes of this idea of splicing together content with these individual things that are sort of mixed and matched at the edge. And the problem has always been actually making productive use of it. And that's really what the question comes down to for some of these personalization and dynamic edge tools. Not does it technically work, but is this something that actually will fit into the workflows that teams have and allow them to get business value with the resources and expertise they have on the team? Yeah. Brittle. Yeah. The last thing I'll say is the fun thing about the edge integrations roadmap is once we get confidence in the pattern that we're using and some confidence around what content editors, what like the Drupal developers and the like non developer content editor personas need to succeed. There's like a bunch of like adjacent use cases that are really fricking cool because there's like, oh let's personalize this homepage for audience A, B or C like returning visitor or person from the UK or whatever. But that's actually technically not different than let's deliver a paywall for non paying subscriber customers. So the idea of being able to deliver like actually gated content or quote unquote logged in experiences that can actually scale to like hundreds of thousands of concurrent users because actually they're not really getting different, you know, they don't need Drupal to deliver the page to them because the page that they're getting is functionally the same as everybody else that's of the same class of user. There's a bunch of really cool use cases we can knock out that are next to content personalization. This is part of why Fastly is so popular in the media industry because it allows doing these dynamic content delivery decisions of the edge about even paywall to content and other personalization or customization of it as it ships out and not having to go back to origin for it. Anyway, we digressed. Other questions from the room. I'm gonna do my like, oh, there we go. Is there a reason why? Actually, I didn't think about the fact that there's like a preponderance of after lives. The mythology thing is just cause it's pantheon and we thought it was clever. And like I'm like 40, I don't mean 43 like next week and we started this thing like 11 years ago. And like one thing I've learned between age 32 and 43 is that if you are being clever, the odds are very high that you're basically screwing over your future self. But yeah, we thought, you know, it's fun, right? It's fun. You could name your projects after deities and so forth. But I didn't actually, it's a good, maybe there's something subconscious going on with like sticks, Valhalla. I don't know, we don't have a Hades. So. That was sort of part of the origin of it. Yeah, because the whole idea around project mercury like the predecessor to some of the pantheon stuff was that there would be other things in that space named after other gods and that we would assemble them together. Like wasn't there a whole idea that there would be like a CI one or something? Yeah, yeah, we had, we had a, it wasn't very widely done. We had a Jenkins based thing that was like Vulcan. It was like the forge. So you've got like your pantheon of different things. And yeah, again, cleverness. Like name your company pantheon. Everybody we've ever hired into marketing at this company is like, what are you doing? That's like, you can't get that name for it. Like that's not available as like any, you got a dot IO, good for you. Great job. You're never getting the dot com. You're never winning first rank in the, in, in Google unless somebody compares it with a technical keyword. But, but yeah, here we are. Having been a little too clever by half. Yes. Thank you. Well, thank you for your moral support on our naming choice. And I'm gonna let David answer the question of like what about a web IDE? Cause he has thoughts. So yeah, pretty strong lines actually. So one of the things about cloud run as compared to our existing container foundation is that it does not have much support for say a mutable environment. There are ways we could kind of cluj one in there. But it's really time for us to revisit how this development experience works. And I've been setting my sites most frequently on dev container, which is also the underlying infrastructure that runs things like code spaces at GitHub. It's a way to specify a container or a cluster of containers as a compose with a compose file that you can have the whole constellation of services and it's possible to fire them all up with one click on say a GitHub repo or locally on your machine with visual studio code. And I do say visual studio code cause you have to use like the official releases to have the support for this, but it provides actually a lot of portability whether it's cloud IDE cause code spaces will fire that up and provide a VS code experience in the browser. But also if you have an IDE installed with visual studio on your desktop, visual studio code specifically, then you can pull it down there, run the entire local development experience as well. And it's exactly the same experience in the sense of the container images and the IDE. What's really cool about some of these approaches is it also allows us, allows tying in things like step-based debugging and other tools that are, that have proven really hard to tie in from cloud infrastructure to IDEs because like they often connect in challenging ways. So like it's very likely that we will continue to explore that space, whether it's literally dev container versus Git pod versus Eclipse Che, those are all different approaches to like cloud IDE and portable experiences of development across local and remote. And we're probably just gonna look at that pretty much from scratch around this in the sense of how to provide a great dev experience. Yeah, it gets into, I think two things that we feel pretty strongly about that are true today of Pantheon and need to be true tomorrow. One is, inevitably you build the product for yourself, right? So David and I, when we were first architecting the experience of Pantheon, we were very much shaped by our experience being technical leads and agencies and having to hop from project to project to project, often multiple projects in one day. And the overhead of like having to recreate your local tool chain to come in and help someone debug something, we just didn't want that. And in fact, we had in our various agency, our own hobby infrastructure, we had figured ways around that. And it was very important for us that you could get like debug something on the platform quickly and effectively. So we need to keep that. And then the other thing that we wanted to ensure is that one of the big promises of Pantheon is you can deploy with confidence, right? The development and like the environments you're working with in pre-production should behave exactly the same way as the environments do in production. So like if your test pass, you can hit the button and it could be the middle of the day on a Wednesday and don't need to worry about it. So there's lots of work for us to do to basically make sure that we're still meeting all of those guarantees with this new infrastructure, but we'll take that really seriously. That's a core promise we make to all of our users. Any more for any more? You can do my... By the way, the stuff that we do on the IDE side will probably occur first for the decoupled support because it does not have like SFDP mode for the reasons that I've already outlined around Cloud Run. Yeah, so that's another way to think about it. Like if you're curious to like track what we're doing with this, like you should get in the early access program for the decoupled stuff because a lot of the developer experience that we build out there will be just bringing to Drupal and WordPress projects as we extend the platform to include all the other things those need to run. Also to answer your other part, no, we did not cover that in the presentation. All right, I think we're good. Thank you all for your time. Thanks for coming to our spawn con. Looking forward to building the next generation of the internet together. It's been a pleasure.


Randall, time for bed?  Time for bed. Time for you to go to bed. Don't bite me, I'm gonna put you in bed. Oh! Okay. I'm about the feathered fun box, okay? So today we are at Jungle Toys Wood Factory. What's going on in here? Look at all these toys. We sell all these. So here's why I'm here. For our feathered fun box, we have a very special theme, tie. Tie is the bird representing the box and he is going to the butterfly part. I got these wood pieces. Mike of Jungle Toys colored them for me. We are putting dots on the butterfly. Tough process because if we do it wrong, then it can bleed. Right, Mike? Oh my God! He got a lot more to do. How exciting. That is banana from his lunchbox to give to Leo. And Gabe Leo is banana. These two are learning how to be together. And so, Alias, the little boy, decided to give Leo his banana. Leo is giving him a foodie.  Is that it? It's not. I can do it. Look how mad she is. She's pissed. I'm just gonna. Oh my God! See, yeah, it's this way. Okay, we're just gonna block you out. I'm not here. Yeah. Wait till you see how that works. Ooh! Nellie's on my shoulder laughing. Girl, you need to realize that. Yeah, you think we're safe? Sometimes I'm watching a movie and I'm like, okay, I haven't covered head to toe. And then out of nowhere, the creeper's behind me. It's like Alfred Hitchcock.  Where am I supposed to sit? Right over there. But actually, we like you to sit here. It's a good time. Yes, so I can get attacked.  I know she is. Watch this. Brando, time for bed? Time for bed. Time for you to go to bed. Don't bite me. I'm gonna put you in bed. I'm faster than you. Faster, I'm faster than McCall. What's she's like, what? Time for bed?  I've met none of my birds in my face. None of them. Oh, she loves Joy. She hates women and them. Oh, she loves her. She's misogynistic. Look at her. Can't see. I don't need you to see her. Smells like cookies. Let's see the cute baby doggy. Hi. Wow, this baby doggy is so cute. They snatch dogs. Who? See you and Danny. I almost brought my new dog. Hey, yeah, where's my dog? Oh, look, she's a dog. I'm surprised you weren't like telling Danny, like, okay, time to return the dog. Like, we can't have two dogs. But you're like, I have a new dog and I've renamed her. Sally, every day is the new name. Sally, Tanya. Look at all these maternal instincts. Oh, she said hi to you. Oh, kitty cat. Jersey, what do you think of Monroe? Oh. Look, Jersey's like got closer to Monroe. Jersey, decision. That's like in Halloween. She won't do anything because she doesn't know, like. Oh, wow, that's all got short legs. Is that normal? Yeah. The good bird. Oh my God, this is so beautiful. Watch this. Let me get Sandy gel, I stir it. She's not getting enough of June June. He has to meet Monroe. Monroe is like so perturbed. What do you want to say to Monroe? Monroe likes Jersey. Time for a bath. I know Jersey's like, I had enough of this. That dog is adorable. Michelle, do you see what I see? She's like, she's all mad at him. She's like Hitchcock. You're so cute though. Look at you. I love this bird.


Following is a presentation of TFNN for Trading Hour with your host, David White. Call now toll free at 1-877-927-6648 internationally at<PHONE_NUMBER>. Now, David White. And welcome all to another exciting edition of the Power Trading Hour with me. You're humble, lovable, and squeezibly soft host. As always, we love to come to you at this time. The following takes place between 2 p.m. and 3 p.m. What do we have here? Well, we've got a market and it looks like there is the rumor mill of all rumor mills pushing the market higher today. We'll talk about that in a few minutes. Of course, I don't believe rumors, but man, are they pushing this hard off the TV and around Wall Street? So we'll see what it is. I'll tell you what it is in a little bit. It's basically they're selling the sizzle for tomorrow and we'll get into that. I had one short position in the short term newsletter. It was basically 20, 30 cents down on a $44 ETF. So basically flat. Got out of it. Just don't know kind of a coin flip tomorrow. I don't much believe in rumors. We had Levi Strauss come out as a new IPO. Been around forever. Not exactly sure why they needed cash. Always worry about that after a company's been around forever and doesn't really need cash. But probably the family wants to get out of it or the people that own a lot of the stock. So it does go public. But you know, is that why they're pushing this so hard today to get it up so they could get the IPO out? Is it so they can get another IPO out? And then of course, as far as I know, Washington, D.C. is a sieve. Maybe someone did tell them actually what's going to happen tomorrow. So you just never know. Anyway, volume has not been that impressive. We're just earning 4.3 billion shares. It's not bad. It's not good. Certainly not anything close to having the 10 billion or over 10 billion shares we had on Friday. That look like we get back up there if we continue to get up to the previous size on light volume. You know, I thought that the market could have had a lot farther run. We needed to pull back pull back on light volume, set up a run on heavy volume probably, you know, maybe in May or in April or something. We never did. We've just kind of stumbled up all the way. The question is, do we stumble up and test the all time highs on no volume? I mean, we're basically just one rung on the ladder below pushing higher. And maybe it's all it takes. Like I said, we'll get into that. And at least what their story is, I'm always reticent to believe it. But man, they are thumping the drum on this one today. We'll talk about that maybe in the next segment. We're going to look at the most hated stocks if this market doesn't go higher. We're going to look at the most shorted and most hated stocks of the last few days and see if there's anything in that kind of interesting also to see that no matter what anybody had to say about it. Mr. Boeing is only down three bucks. Man, you got to think generally that the wisdom of crowds is better. I didn't get into that yesterday. Maybe we'll talk about that again today, which is I've done some reading on it makes some sense. But again, I don't know a great deal more than anybody else other than I've probably spent a more time reading about it. Anyway, just down three bucks, which is less than a percent. And that happened on any other day, much less a day where everybody's telling everybody that the FBI is coming in like Ruby Ridge. You never know. But that just seems a lot of self self flagellation so far. Yeah, you can give me call<PHONE_NUMBER>. You can email me at path at tfnn.com. And of course, you can always put in the den. What is pushing Apple? Well, it is that subject that I actually talked about and that is short interest. Apple has been the highest short interest stock pretty much for a while. And like I said, we'll talk about that in the next segment or in the next one after that. I want to get a little history out of the way. Then we'll get into all those things. Talk about the rumor. We'll talk about Apple. I'll probably get us into the bottom of the hour. But what we need to do is a little history before this break. And it's all just a little bit of history repeating. Oh, history doesn't actually repeat, but it does rhyme a lot. On this day in 1963, Alcatraz Prison in San Francisco Bay closes down and transfers its last prisoners at its peak period in the youths in the 1950s. The Rock or America's Devil's Island. Devil's Devil Island. Deviled is an egg, isn't it? Housed over 200 inmates at its maximum security facility. Alcatraz remains an icon of American prisons for its harsh conditions, record of being inescapable. In the, I'm going to say mid 90s, 95, 96. I ended up spending probably in total, maybe three and a half, almost four months in Silicon Valley. And I ended up renting a houseboat down on Pier 39 over looking right out at Alcatraz. Always nice. Went over there a few times, met a couple of people that had actually been in there as inmates that had written books. If you go in there now, I don't know if they still do it because I went over there so many times. I really haven't felt about or felt like going back. But they got a very interesting view of what Alcatraz was like. Universally, they all wanted to kill the bird man of Alcatraz. They said he was the worst human being. And of course, this is the worst of the worst. They said that anybody that the guards had to watch him extra closely is everybody wanted to kill him. Half the guards and all the inmates, which was kind of interesting. Also, one guy that I talked to there that had written a book about his time there with Al Capone saying that the guy was kind of out of his mind when he first showed up. And one guy trying to escape in a steam tunnel. They were going to all escape the next day. One guy went the night before, ended up getting roasted in a steam tunnel before he could escape. And that's kind of interesting to see. At least a couple of people actually came out of Alcatraz, became good members of society. One guy that I met, his name's Quinlan, actually got a pardon from Ronald Reagan in 1986. He became a radiologist and worked about 35 years and then retired for a hospital there in San Francisco. There is a redemption when we come back. Rumor and innuendo. The Taz Profile Scanner is the most revolutionary piece of trading software that you will ever try. Wouldn't you like to approach the markets with confidence? As you begin your trading day, it's likely that you'll be faced with lots of decisions. In order to make the best decision, the first thing you'll need is a strategy that will help you minimize your risks. Whether we're in a bull or bear market, a good strategy is to have the tools needed to help you scan and analyze the markets before you trade. The Taz Profile Scanner instantly scans and filters over 2,500 global financial markets, such as stocks, ETFs, commodity futures, and forex. Headed by Steve Dahl, president of Taz Market Profile, the Taz Profile Scanner understands that in today's technological world, the use of top-flight software applications, automated trading algorithms, and technical analysis expertise is essential to successful trading in today's market. Whether you're looking at the trade matrix, the ETF heat grid, the market breadth, the landscape charts, or the many other features of the Taz Profile Scanner, this is a piece of software that will revolutionize how you look at the markets and set up your trades. The team at Taz has even put together a 12-part video series to walk you through every aspect of the Taz Profile Scanner, which you can find directly on the Taz Order page at tfnn.com. Sign up now for only $97 a month with a risk-free 30-day trial so you have nothing to lose and everything to gain. See for yourself how you can harness the full power of the Taz Profile Scanner by visiting the front page of tfnn.com today, and you'll find the Taz Profile Scanner under the Services section. Remember, with a 30-day money-back guarantee, you have nothing to lose. Don't let another day pass you by without trying out this amazing piece of software that will revolutionize how you look at the market and how you place trades. Sign up today. Tfnn has launched our brand-new website. You can still visit us at the same tfnn.com URL, but when you do, you'll see a new and improved homepage with a much simpler navigation, whether you're watching Tiger TV live in high definition or just accessing your newsletter subscriptions. We even have new pricing in six months and yearly options. Check out the new tfnn.com now and experience all the upgrades. tfnn.com, educating investors. Call now toll-free at 1-877-927-6648 internationally at<PHONE_NUMBER>. And we're back, yeah, we're at 2854, we'll call it that, up almost 30 points on the S&P cash, and volume for a 30-point move, about four point, and not even 4.5 billion shares. Again, we're having these big swings. There's not that much juice in it. But again, it may be for a variety of reasons, and we'll talk about that in a minute. But I'm going to say that it's a handful of people getting short stocks that probably shouldn't be, should have been shorted. Had a conversation with a few folks that I know in the industry from Chicago and New York, and they all told me that they're getting fed this big line today, and that is that the Mueller report will come out tomorrow.  And because of that, the Chinese have been waiting for the trade deal to see what was going to happen.  The thought is that there's not going to be any of that. And he certainly is nothing's going to happen to him tomorrow when the Mueller report comes out. And again, don't shoot me. This is just what everybody's pushing. Who knows if it's true, but they're certainly using that to push the market up today, at least from what I hear. So anyway, nothing happened. And of course, then maybe the trade deal goes a little farther on. I know we heard this story and enough wolves, but you know what? When you got enough people short and they probably are in the wrong stocks being short. A lot of times these stories, which sometimes made an entire whole cloth, get people to worry. We had a question in the den about why Apple is going higher. And I wanted to show this because I put it in every the newsletter every single day, which is a chart of the top 10 shorts, both in the NASDAQ and the S&P 500. Actually, I got 15 in the S&P and the top 10 in the NASDAQ. But Apple even yesterday continued. But it's been probably a couple of weeks, maybe one of the highest shorted stocks that's been out there. Yesterday or no, the day before that 24% of all the shares were being shorted doesn't mean that the shares went home short, but means that during the day that one out of four shares that traded was traded as a short position. But generally does mean that you get a couple of two or three or four days like that, getting out in front of a company that has $250 billion is sitting around. I don't understand the idea of shorting a company that has decent sales and a lot of cash. You want it to go after the stocks that have weak business models, iffy financials and other big problems. So when I look at Apple, anything probably more than about 15% on a day is a giant red flag. In fact, let me go ahead and do this. But, you know, I don't know how you short a company. I wouldn't bullish on the stock, but at some point you have to get bullish because too many people are on the wrong side. Let's take a look at this. Okay. I mean, we've had weeks where this thing actually, I'm going to say the last 10 trading days where this thing has been almost every day over at least 20%. And that's pretty big on a big stock like this that doesn't have, you know, financials or books that are probably cooked or other issues like that. So when you ask why it continues to go higher, probably more rumors and a lot of people on the wrong side of a stock that shouldn't be that short. Now, when you look at the buy monthly, I'll show you, maybe you can see it. This is my own program, so it's hard to see. We went from one day to cover an apple in the last reporting period to the end of February from four days. We went from about four, what is that? Let me get the digit, 40 million shares short to 97 million shares short. And that's what it's all about. And that's why I always publish those short numbers every day of the most heavily hated because of the market goes up. Those people going to be on the wrong side and they get squeezed the bet the most. Now we're going to go through the most hated stocks today because if we do get another push, there's probably other stocks out there like Apple that over a couple of days or maybe even during the day that you might want to day trade, especially into Friday, if things get going and you got a lot of stocks that are short. Anyway, Apple, maybe one of the most hated stocks over the last couple of weeks.  They do have at least a kind of array of hope with their new earbuds that are rechargeable. And a lot of people are buying them kind of plan obsolescence, the old earbuds, wireless earbuds, the batteries are failing. There's no way to replace them. And people are having to shell out another 200 bucks to get these things. And apparently that's actually been just enough to turn the tables on people that have been way, way, way too short on Apple. I mean, from the chart, you look at it, you go in, not much happened in here. You certainly, though, wouldn't want to be short when you saw that many people piling on. Generally, the people that short the most are the people that short at the bottom right before they get squeezed. ALGN, which is another one out here that with the mighty shorts on this is kind of popping up today, not a lot of juice. But certainly wanted to see at least fill half of that gap that goes back to the 25th of October. That was eight and a half million shares. You don't have a lot today. But again, when you got a lot of people piling on short like this, it's not uncommon for them to push it as hard as they can. Another one that has been massively shorted has been advanced micro. We got another follow through today, not a lot of volume, certainly not the kind of volume you want to see. You need about 140 million shares and you don't have anything close to that right now. You might even if you're, you might even want it to see 90 million shares from this gap down on the 25th of October. But either way, you wanted probably a lot of volume. You want to watch that for the end of the day. But again, I'm not a big fan for shorting a $25 stock more than likely it's easy to get you squeezed. Another stock that's seen massive shorting and it is Amazon. Amazon's been bucking it up against this previous high. I wouldn't be surprised to see these guys push a little harder over the next few years. A few days as it goes up against this November 8th high and the December 3rd high about 1778. Both of them. You might have the volume today. It's not going to be fantastic. What you have is a lot of people getting short too early and then getting run. We'll be back in a minute. The path of least resistance is David White's daily trading newsletter. And if you're looking for active trading ideas, then now's a perfect time for a 30 day free trial to this powerful daily trading advisory service. David uses his years of trading experience to offer his subscribers his trading ideas each morning in his path of least resistance newsletter. Using a combination of equity trades along with options, David keeps his subscribers up to date with all pertinent market information with intraday afternoon updates when warranted. Don't miss out on this great chance to get a 30 day free trial to David's daily newsletter, the path of least resistance, with no obligation to pay anything. David has been delivering solid recommendations for his subscribers recently and if you'd like to see the type of newsletter he delivers every morning, then visit the front page of TFNN and you'll find the path of least resistance under trading newsletters. For all the details and to start your 30 day free trial today, log onto TFNN.com now. Hi folks, Tom O'Brien here. If you'd like to get my daily newsletter and market insights, then now is a great time to sign up for a 30 day free trial. Every morning by 9.30 I send out my morning letter to subscribers with market commentary on a variety of markets, currencies and commodities to keep investors up to date on the day's trading action. Included in market insights are specific buy and sell recommendations for stocks, ETFs and even options, which stops and price targets included for every trade in my newsletter. If you'd like to try my newsletter risk free for 30 days, then head over to the front page of TFNN and you'll find market insights under trading newsletters. I use my years of trading experience to bisect and dissect the market every morning and give my subscribers the most important information they need to know for the day ahead. I even issue afternoon updates for my subscribers whenever warranted with important market action. I'm always scouring the market for the next great trading opportunity. Sign up for your 30 day free trial to my daily newsletter, market insights today by visiting the front page of TFNN.com. Well, go get them folks. TFNN is excited about our new software charting program, the Art of Timing the Trade Chart. In collaboration with Tom O'Brien and using his best-selling book, The Art of Timing the Trade, Your Ultimate Trading Mastery System, David White has programmed an outstanding piece of software that will complement any trader's methodology. Using this first-of-its-kind program, the Art of Timing the Trade Chart allows you to scan thousands of stocks for Fibonacci formation setups, including guardleafs, ABCs, butterflies and much more. The Art of Timing the Trade Chart is designed to help you when scouring the markets for stocks just beginning to form the trading patterns that many investors spend days, weeks or even months searching to find. And right now we're offering licenses available at only $79 a month. We are so confident that you're going to love this new charting software that will even give you a 30-day unconditional money-back guarantee. To miss out on this incredible new piece of software, get your copy of the Art of Timing the Trade Chart today by visiting TFNN.com. This segment is brought to you by Think or Swim. For more information, just click the Think or Swim banner on the front page of TFNN.com. And we're back. We're going to go right away to Dave and Framingham. How are you doing? How are you? What was that stock that you bought that was the Semi? No, that wasn't me. Wasn't you? No. Maybe a month ago or something? No. It's AKS and the U.S. Steel I'm looking at here. That's good. The AKS. Yeah. So what are you looking at here? Where are we going? Are we going to get up to the $5 area? That's what I'm looking at. Well, I think you do. If the trade deal ever gets signed, that's the issue. Yeah. I mean, who can time that? And that's the issue, right? Right. But then I got to wait it out. Right. Yeah. I just don't know. But right now, I don't think. I mean, you're just going sideways for five days. You've got a little pop today. Yeah. Right. But you've got five. I don't know who in the world is sitting on this. Like somebody thinks that they could go bankrupt. It's got five days to cover on short interest for $2.80 and 285, whatever stock. Yeah. I don't know who's this massively short on it. I don't know. What's that? I don't know who's shorting it. I read things, but they're making money. They made money. They're making money. Yeah. Yeah. But I mean, it's got like 55 million shares short, right? So if it, if, yeah, if anything happens on it, this could be a Roman candle. So I could see maybe putting, treating it more like an option and just sitting on it. Yeah. I don't see any, I don't see anything in it now. Okay. But, you know, all those shorts are there and if their trade deal comes through, I think it would be pretty good, but I don't know if you have to wait six months or a year. Yeah. Or two days. Or something here shortly. Something's going to, he's, something's going to happen. Yeah. I mean, I, I like this, this setup of this. I'm just wondering what the catalyst would be. The best one, the best one I could think about would be a trade deal. Yeah. Right. Which, which is going to cut out a lot of Chinese steel and, and then these guys will have contracts where they know what's going to happen. Right. Yeah. That US companies can go, okay, I can give you a contract for the next three years for the steel we need. And I, I think that would be good. It's just, with it being in limbo, it's hard to tell. So. David, they've got 50% of the auto market here in the state. Yeah. And if you can't make any money, it's not how much you sell. It's how much you keep. Right. Yeah. These are out there dumping all the time, which is what they do to try to bankrupt these bankrupt or US businesses. I mean, they've got two reasons to do it. One, they like to do it just so that it can keep their businesses growing over there. And two, militarily, they don't like us having a lot of ability to make steel here in the US either. They love to see us basically without the ability to build new stuff. Yeah. If they decide to ever invade Taiwan or something. So I like the setup. I just don't know how you time it. Yeah, you just got to wait it out, I guess, because anything can happen. You know when earnings, you know when earnings is on it? The 29th, I believe. April. Right. What is this? AKS. Let's make sure about that. Okay. 29th to April is right. You know, I think. I think the play would be to probably just sit on it. Yeah. And if you get to the 29th. And you know, you haven't got a you haven't got a profit. Just get out of it. Yeah. And then, you know, wait the day after the earnings are okay. You go right back into it. I don't want it wouldn't want to roll the dice on earnings. But what's today? The 21st. So he gives you four or five weeks. Yeah. I think I think there's going to be some fun buying here going into the last week of March also. Yeah. I don't I don't know how much they're going to want to jump on this. Yeah. I mean, the fun guys would much rather buy this thing at four bucks knowing that everything's done and try to buy a flyer on it at 280. Okay. They're not they're not the biggest risk takers in the world. Right. And two, if you remember what I said about funds and $10. Right. For those people that are new, basically a lot of funds can't own stocks below $10. It's in their charters. So you've got to find some people that, you know, that can buy it. And again, the big money generally made once it gets to $10 and the funds can then make it, then it goes from 10 to 20. So if you can get into it and hold it if it does well, but I don't know. I think kind of a roll of the dice out here. If you treat it like an option, a non expiring option, that means that you don't go in large, right? You put a sum in it, but maybe a half or a quarter position and just sit on it. But that would be the way that I would look at it. I can see all the all the issues here that could make it roll. I can't see a lot of things that drive it below two bucks. What about US Steel? How's that chat look? It looks like it went down to around 19 and change. We talked about that, I believe. It's back up over 20. What's the symbol on it? US Steel. X. Yeah. The US Steel. Okay. It looks kind of the same thing. Let's look and see what it looks like. I mean, the big difference here is that funds could buy it. It's a $20 stock, right? Right. So that gets you out here. Short interest has been high in this. Let's see what it is. Now, this one doesn't have much in the way of short interest at all.  So if you were looking for the rocket ship, I'd like having less money in AK Steel than I do in X. You probably have a better chance of making a little money in X. You probably have a better chance of making a lot of money in AK Steel. Yeah. Yeah. If I was going to handicap both of them. But yeah. Like I said, the only problem is you just probably don't want to be in these things on earnings day. Yeah. David, can you take one more here? Yeah. Let's go ahead. Yeah, David. The S&P we talked about could it reach the October top of the high there? It certainly could. It could go up there on no volume. It could do it in a matter of four or five days. Yeah. Yeah. I mean, we could do it by Monday or Tuesday. It could be done. It could be done. And it could go up there. Now, the question is no volume. No volume, right? Yeah. Say it goes up there on no volume. And then you ring the bell. That tells you one thing, which is going to be that you're going to have a long, long-term high put in it. You might be in a very bearish market. If it goes up there, rings the bell on volume, then maybe you're looking more like 3,500, excuse me, 3,500. Yeah. In the S&P. Yeah. I mean, this is a market that's kind of balanced on the edge of a razor. I had a short position. I was basically flat in. I got out because I just don't know. Yesterday would have been fine. Then I started wondering what was going on this morning. I started seeing all those rumors. I mean, the rumor mill, it's not in overdrive. It's like gone flat. We'll be back in a minute. Okay. Thank you, David. You bet. If you are in the CD market and looking for a secure investment, the Tiger First Mortgage Program may work for you. The security for these first mortgages are building lots in the tax opportunity zone in St. Petersburg, Florida. The Tax Act of 2018 set up tax-free zones across the country where you can build and hold for 10 years and pay no tax on the profits, which makes these lots valuable. The investment is anywhere from 30,000 to 75,000. The interest paid is 7% yearly paid on a monthly basis. According to bankrate.com, the best rate for a four-year CD in the country as of February 20th is 3.1%. A $50,000 investment at a normal four-year CD rate of 3.1% would give you income of $1,550 per year, or $6,200 over the four-year period. That same $50,000 investment in the Tiger First Mortgage Program would give you $3,500 per year or $14,000 over the four years. What should you prefer? $6,200 or $14,000 of interest on your investment. If you'd like more information about the Tiger First Mortgage Program, you can call me at<PHONE_NUMBER>. That's<PHONE_NUMBER>. If you haven't checked out the newsletters page of TFNN.com, what are you waiting for? All of the TFNN newsletters are informative, up-to-date, affordable, and must have for every trader looking to gain a competitive informational edge in today's markets. TFNN newsletters cover every aspect of the markets to offer you the very latest in market news. Plus, new subscribers get to test drive our newsletters risk-free for 30 days. From all aspects of the markets, including stocks, bonds, metals, commodities and tech, there's a newsletter to fit your needs exclusively from TFNN. Stay informed each day you trade and get the competitive edge that will help you stay ahead of the game. Visit our newsletters page by going to TFNN.com and click the newsletters button near the top of the page. TFNN.com Educating Investors Will the S&P 500 continue to climb for bold trades on U.S. large-cap stocks in either direction, trade SPXL, SPUU, or SPXS? Directions daily, S&P 500, bull and bear, leveraged ETFs. Direction leveraged ETFs. An investor should carefully consider a fund's investment objective, risks, charges, and expenses before investing. A fund's prospectus and summary prospectus contain this and other information about direction shares. To obtain a fund's prospectus and summary prospectus, call<PHONE_NUMBER> or visit Direction Investments.com. A fund's prospectus and summary prospectus should be read carefully before investing. An investment in the fund is subject to risk, including the possible loss of principal. The funds are designed to be utilized only by sophisticated investors such as traders and active investors. Distributor for Side Fund Services, LLC. Don't forget, you can listen to TFNN live on your mobile device 24 hours per day. Go to TFNN.com and hit Watch Tiger TV. That's TFNN.com and hit Watch Tiger TV for the latest market information. We're going to go to Nike with the earnings, I think, after the bell tonight. Let's just make sure about that, but I think that is it. Yep, yep, after the bell tonight. Nike has a very low 1% one day to short. So there's not, if it does go higher, I don't think it's because it's got a ton of shorts out there. You've got it breaking the previous high of September 21st, 85, 82, 14 million shares. Got into that a couple of days ago with 6.6 million shares. There hadn't been any real energy up here at the top. I think the risk reward is pretty horrible on this. That is, you don't have a lot of shorts if they whip. They're not going to be there to buy on the way down.  Other companies in this footwear space have not been doing well. And the question is whether or not Nike just had enough dough to make the books look good yet another quarter last time. And this is when it catches up. I don't like flipping a coin here. A lot of these stocks look like they could go, you can make and drag out maybe six months or nine months or even a year if you continue to work hard on the books. And I don't know, it just doesn't seem like, at least the people I see out and about anymore, not that many people buying Nike shoes. The death of the mall kind of hurting them a bit where people used to go and buy them. I mean, they still buy them, but it's not like you won't go buy a footlock or that many more times or many of the other ones that are selling the shoes. So I think it was, if I remember right this, the tennis shoe business is kind of about 50% an impulse buy. And they used to make a lot of money for those mall stores where people just didn't go anymore. And sports viewership kind of down to, which also makes it an issue. I don't know. I don't like being long. I certainly wouldn't be short. And I think that's about it. Now we've got a couple other ones out here. Another one in CZR. Caesar's Entertainment. Now this is a, I assume this is what you're looking at. Man, is this a stock that's been horrible for forever? And I brought this up on the show when these guys IPO'd. They IPO'd with 4.2% of the shares outstanding for the flow. And these guys have been selling and selling and selling into this for forever to get all those shares out and cash back into the company. I haven't looked at what it is now, but I know this is like one of those trees that you go up and you hit and it's the ants have eaten the insides out. It's always been one of these sliver deals. And I'm going to say that the 95% of these sliver deals end up blowing up in somebody's faces. Eventually, they can't, the financials don't carry it. You know, I don't know that much about Las Vegas. I know that it has been fairly good out there, but I don't know if it's big at Caesar's anymore. The other big hotels doing well is going to do horrible. No, is it probably going to blow up in your face? The next couple of days, the answer's no either. I just don't see where this thing ever really goes and does much anything. Let's go back in fully years. I mean, it got up to 1450, but I think it came out at like 10 bucks. And let's go back even a little bit farther here. See what I got. Never do anything. I think they ran some kind of scam to get it up to this $26.74 high.  And then they started letting all the shares come back in. And that's how this thing got back down to $3.20. But heavily manipulated stock. This last run from the February 1st, a high of 2018, absolutely massive volume and getting out back down to 584. Just what I know, not the amount of people going in the front door of this place, but the way that this stock has been operated, I just don't know how you can do anything with it. They are all over this. And if you think that they think that your money is their money in Las Vegas, just wait until you buy their stock. But I kind of vaguely remember this whole thing being jiggered up to get it up to that February 28th high. So it's just one that I won't touch, because I always know that there's something going on. And it's very easy for whoever's stock operator in this one to really push it around. Okay. What else do we have? Oh, we wanted to look at more short stocks. Okay, so we got that done. Okay. We got that. Okay. Let's go ahead and move on to some of the stocks that I wanted to look at. As we said, I was talking about the rail companies and looking at whether or not they can do anything up here and talking about Greenbrier the last week was at GBX. We'll look at that in a minute. One of the most hated stocks, massive shorting, has been CSX. Generally, the problem with shorting a company like this, which had a 20%, almost 20% short move on it yesterday, is that you reverse that. It's not as bad as others. It's got three days to cover with 222. What is this? 12.7 million shares short. Energy's about the same on the way up. Let's take a look at that GBX. We talked about this one making a fairly... Let's go back here a little. Trying to make some kind of low out here on no volume. Got about 800,000 shares in two previous January 10th low and the December 24th low. A little under 800, let's call it that. Went below it with 336,000 shares. A little reversal today, but no volume in it went 12. You need this to close back above 3,795, 3,744, either one of those. So you still have a little ways to go. I guess you can say that as long as this thing hasn't broken those previous lows today, this is just low volume. A pop back into that trading range would be good and kind of tell you that maybe CSX is ready for a little short covering. Let's take a look at hog. Another one with massive shorts. We're going to go to the break. We'll be back in a minute. We'll take a look and see how bad it is. Look at this. 11 days to cover in Harley Davidson. If everybody had to get out that was short, it would take them 11 days of just the average volume of the last 30 days. We'll be back in a minute. I'm Steve Rhodes, author of Mastering Probability, and for the last 12 months, Timer Digest has been tracking my newsletter signals, which have earned me the ranking as their number one market timer in the nation for the S&P 500 for the last 12, 6, and 3 months. Timer Digest also ranks me as the number one market timer for gold as well. The fact is markets can be timed and I'll teach you the exact set of tools that I use that has transformed me into one of the best at what I do. Sign up for Mastering Probability today by clicking on the newsletter tab on the homepage of TFNN.com and get immediate access to workshops where I take you step by step how to use an extraordinary set of tools as well as provide great market calls to. Sign up today. David White's newsletter, The Technology Insider is focused like a laser on finding the next big things in technology. If you had invested only $10,000 in Microsoft in 1986, you'd have been a millionaire by 2000. Disruptive technology like Microsoft's is the key to these massive long-term profits and The Tech Insider is the vehicle from TFNN to capitalize on these opportunities. This is the go-to newsletter that identifies, monitors, and profits on mostly little-known cutting-edge companies with great long-term prospects. David's experience is as an inventor of Emmy-winning animation products for TV and Hollywood that propelled a company public. Match that with the technology that propelled a company public. Match that with 14 years as a full-time trader and he's uniquely qualified to guide you through the light-speed world of ever-evolving high tech. If you're ready to ride the next big technology bull market for less than $40 per month, log on to TFNN.com and get your two-week free trial to The Technology Insider. Get in on the ground floor of the next big thing today. Since 1984, Basil Chapman has been using the Chapman Wave methodology to advise traders of his expert market opinion. While originally hand-drawing charts from the late 1970s into the 1980s, Basil noticed that prices under most circumstances virtually always had a certain number of legs to the upside before declining sharply. Later, Basil found that computer software which included the standard market technical indicators enhanced the degree of accuracy in calling price turns as well as market trend calls. Thus was born the Chapman Wave sequence. Using the Chapman Wave methodology, along with other indicators, Basil Chapman advises his subscribers of his expert market opinion each market day with his opening call newsletter. Right now you can get a two-week free trial to the opening call, Basil's daily trading newsletter, by visiting the front page of TFNN.com. Cancel at any time during that trial and pay absolutely nothing. Get your two-week free trial to Basil's newsletter of the opening call today by visiting TFNN.com. Also, a special guest on CNBC. Tom will bisect and dissect the markets. The Tom O'Brien Show, next on TFNN. And we're back. Have a e-mail coming in from Eric across the Ethernet. Looks like they worked out lithium issue in China, great show. I would be wary of believing that there's a huge problem getting rare earth minerals. We've been through this and to that already before within CP. Rare earths are not rare. They are just in light concentrations. If you can get 5% somewhere, then you can mine it and make some money. It's not that it didn't somewhere else at 3.5% or 2.5%. In fact, I think there's a big bunch of it here in the United States at about 3% or 4%. But because, of course, environmental laws can't actually mine it here in the United States, it's just not worth it. So the question is on this one, I mean, you got 120, 110 EVs that are going to come out. I just don't know if the market hasn't been saturated already by Tesla and now a ton of these cars are going to come in over the next year. I think some of them are going to sell good. The Porsche Taken looks very good. The Hyundai Kona looks very good on the lower end. But I mean, there's so many of them. There's a couple of trucks that Amazon's invested in pickups that looks pretty cool. But that's it. Let's take a look at Lit real quick, which is the Lithium ETF. I don't see anything in that one right now to say higher or lower. You got a little bounce in this, but again, no volume in this. And I think you're really going to have to see these cars go into production, which is going to be probably mid-summer. And maybe it's just the timing, but I think maybe you got another month or so to go before Lithium. Maybe two months to go before Lithium really gets moving. In the meantime, sell when you can, not when you have to. We'll see you here tomorrow.


You know we had two different groups today where you know we're spacing and so that was different and you know I always try to just go up there and you know have an idea of what I want to say certainly but then just go and but trying to keep it consistent for two groups you know the second time didn't feel quite as good but yeah you know we had to go through a lot of health and safety protocol so that was pretty time consuming this morning so I was fairly brief you know five or seven minutes or so of you know just some things that I really wanted to hit on for us as we as we get rolling here Beyond what your normal message is to them about competing for a championship you had a certain unknown last year where you kind of plowed through this in 60 games when you're trying to ward off quarantine fatigue for eight months what are some of the things that you can kind of build into this to keep that from happening and keep this team focused on what you're trying to accomplish. Yeah you know keeping the expectations very high is one way and knowing that that carrot's out there knowing that we have a group of guys that by and large you know have experienced a lot of success but a lot of disappointment too and so one of the things I feel like we have going and have had going for us is a hunger with this group so you know we haven't gone through this in 162 in this kind of scenario in a pandemic so there'll be challenges along the way but those will be things that you know as spring unfolds as the season unfolds as we continue to learn how to live and exist and thrive in this environment you know we'll evolve with it and with that is the challenge of making sure we are have the right kind of focus to survive the long haul.


Basically up there, I just auto ran all the way down. Lived. Yeah, I've been having some battles, mate. I need to get in a fire up, see me. I'm in kidney. Go silence some nooks. Oh, the other lads are coming. We've got to kill this guy fast.  He's dirty, but he's good. I might get sapped, I'm out of combat. Get in combat with this lad. No one's even dismounting. This is what is this shit? Dude, he's waiting to sap you, I reckon. Get that rank one only, no right. Yeah. Wait, max rank. I'd silence the bison. That was certainly a missed quick. Oh, the black hat. Oh, the black hat. Oh, you hate to see it. He's got blood fang. What is going on? This kid running away like a push. I don't have the key. Lucky for you, I don't have the key. I've got like 10 dudes in there. Lads, lads, lads. I love how we banded together there, boys. This guy doesn't use CS, dude. Dude, don't miss your nades. That one's called double field, bro.  Hi, have a great time. Oh, no, dude, you hate to see it. I need to lose aggro somehow. Go on, Hunter, get aggro for me. Oh, jeez, I'm so dead. If I can slay it, though I could save him. The heel landed.  Oh, that's an epic blind. All right, we've got this important.  Yeah, stay there, dude. Dude, this is flawless. All right, we're dark ruining. Calculations. Oh. Oh, my heart. I hope my doctor doesn't see this. By the way, just for reference to everyone that's listening of what I'm just talking about.  He was jumping all ways.  But he was playing anyway. And he was killing stuff fast. And he was chain pulling mobs. And it was all going really fast and smooth. And I was like, wow, that's made me really doubt my ability to play the game. You were doing that really well. And now I feel like I don't know how to play the game. And Ryan was like, no, no, it's not you. I'm just not the average. I'm just not the average player. I try to make you feel better. All of the calculations. The least.  You're actually the worst. When a mom's hitting me. I know exactly how much damage I'm going to take. I know exactly when it's going to kill me. And I'll let you.  No, no, no, no, no, no. You have to roll for the chest.  What the? Oh, I can't do it well in combat. Wow, really bad.  He's going to aggregate more. He's healing himself. He's out of blocks. If you get this, I'm going to be so pissed. I'm going to let juicy ice cold milk. What ping do you have? 29. I have 28.