00;00;00;00 - 00;00;06;11
Speaker 1
Hey, Coco, I'm recording this for a podcast. Is that okay?
00;00;06;14 - 00;00;10;07
Speaker 2
That's cool with me, Bronson. Let's make it a great one.
00;00;10;10 - 00;00;31;24
Speaker 1
Okay. Can you, if I want to build my own custom website or app, can you kind of give me a rundown of the role of a VP as a virtual private server? As opposed to a shared server?
00;00;31;26 - 00;01;08;01
Speaker 2
A VP or a virtual private server gives you dedicated resources on a shared physical server. It's like having your own mini server, but it's still part of a larger machine. This gives you more control, better performance and security compared to a shared server where you'd be sharing resources like CPU and Ram with other users. So if your app or website needs more consistent performance, or you want more control over the server environment, a VP is a solid choice.
00;01;08;04 - 00;01;23;20
Speaker 1
Okay. Let's break down each of those. Can we break down the more control? And actually, before we get into that, I would like to kind of get a rundown of what a shared server provides.
00;01;23;22 - 00;01;51;10
Speaker 2
All right. With a shared server, you're sharing resources like CPU, Ram, and storage with other users on the same server. It's like renting an apartment in a big building. Everyone has their own space, but they share the same utilities. It's cost effective since you're splitting the resources, but it can also lead to slower performance if other users activities demand a lot of power.
00;01;51;13 - 00;02;01;16
Speaker 2
It's a good option for smaller websites or apps with lighter traffic.
00;02;01;19 - 00;02;09;16
Speaker 1
Okay, is the amount of traffic really the only factor there?
00;02;09;19 - 00;02;34;25
Speaker 2
Traffic's a big factor, but not the only one. The kind of website or app you're running matters to dynamic sites with lots of database queries or big media files need more resources, but traffic remains a biggie because high traffic can max out a shared server's resources. Fast.
00;02;34;28 - 00;02;47;29
Speaker 1
Okay, so what if, let's say you're on a shared server with someone who has a really high traffic website? What does that do?
00;02;48;01 - 00;03;12;29
Speaker 2
It can lead to noisy neighbor issues. That high traffic neighbor might hog the shared resources, slowing down your website. It could mean longer load times or even downtime if the server gets overwhelmed. That's why a VP or dedicated server can be a better choice. If you need stable performance.
00;03;13;01 - 00;03;28;16
Speaker 1
Can you give me examples from the real world of websites or apps that are on shared servers and websites and apps that are on dedicated servers?
00;03;28;19 - 00;03;57;05
Speaker 2
Sorry, I can't provide specific examples of websites or apps using shared or dedicated servers. Since companies don't usually make that information public, generally smaller websites or personal blogs might use shared servers, while larger businesses or high traffic platforms opt for dedicated servers for better performance.
00;03;57;08 - 00;04;19;03
Speaker 1
Let's say that I wanted my website to have like a higher level of interactivity and potentially like sound and video. How would a shared versus a VPNs be good or bad?
00;04;19;05 - 00;04;52;13
Speaker 2
For sound and video? A shared server might struggle with the load leading to buffering or slow performance, especially if other sites on the same server are busy. A VP with dedicated resources would handle the demand better, providing more consistent performance and potentially allowing for more complex interactivity without the hiccups you'd expect on a shared server.
00;04;52;16 - 00;05;06;04
Speaker 1
Okay, can you give me an idea of the kind of interactivity that would be okay on a on the demands of a shared server.
00;05;06;07 - 00;05;33;24
Speaker 2
A shared server could handle basic interactivity like simple forms or basic JavaScript functions, and small media files like images or low resolution videos. It's when you start adding high quality video streaming or complex resource heavy features that you'd likely run into. Limitations. Keep it light and you're generally okay.
00;05;33;27 - 00;05;41;22
Speaker 1
Okay, what about, things that have a VP?
00;05;41;24 - 00;06;10;19
Speaker 2
With a VP. You could handle more demanding interactivity, like high res video streaming, complex animations, or interactive web apps. You'd have the bandwidth and processing power to support more users and features, offering a smoother experience for your visitors or users.
00;06;10;21 - 00;06;20;03
Speaker 1
Okay, so what makes a website slower besides maybe just adding video?
00;06;20;05 - 00;06;43;13
Speaker 2
Several factors can slow down a website unoptimized images, excessive plugins, heavy scripts, server response time and lack of caching. Too many Http requests and bulky code can also bog things down. It's all about optimizing every element to keep things running smoothly.
00;06;43;15 - 00;06;51;28
Speaker 1
Okay, can you list those off again slowly for me so I can take notes?
00;06;52;01 - 00;07;14;24
Speaker 2
Sure. Here they are. Unoptimized images, excessive plugins, heavy scripts, slow server response time, lack of caching, too many Http requests, and bulky code. Got it.
00;07;14;26 - 00;07;24;27
Speaker 1
Okay. Can you go over unoptimized images for me and kind of explain that?
00;07;24;29 - 00;07;52;19
Speaker 2
Sure thing. Unoptimized images are larger files than necessary when they're not compressed or resized properly. They take longer to load. Slowing down your site. Optimizing means compressing them to reduce file size without sacrificing quality and resizing dimensions to fit the design, ensuring faster loading times.
00;07;56;24 - 00;08;03;03
Speaker 1
Okay. What about excessive plugins?
00;08;03;06 - 00;08;25;29
Speaker 2
Excessive plugins can slow your site because each one adds code and requests that the server has to process. More plugins mean more potential for conflicts, security vulnerabilities, and updates to manage keeping plugins to a minimum and ensuring they're well coded and necessar helps maintain performance.
00;08;26;02 - 00;08;35;07
Speaker 1
Okay, can you, tell me better what a plugin is?
00;08;35;10 - 00;09;02;24
Speaker 2
A plugin is a software add on that extends the functionality of a website. It's like installing an app on your phone for websites. Plugins can add features like contact forms, SEO tools, or social media integration without needing to code it from scratch. They offer convenience but can affect performance if overused.
00;09;02;26 - 00;09;09;16
Speaker 1
Okay, what are the requests that you're speaking of?
00;09;09;18 - 00;09;38;02
Speaker 2
Requests happen when a browser asks a server for elements to load a web page, like images, scripts, or stylesheets. Every element is a separate request. More requests mean more work for the server. Slowing down the load time. Optimizing a site includes reducing the number of requests or making them more efficient.
00;09;38;04 - 00;09;45;26
Speaker 1
Okay, can you give me like 4 or 5 examples of different requests?
00;09;45;29 - 00;10;21;16
Speaker 2
Sure. Thing one http HTML requests that load the page structure. Two CSS requests that style the page three JavaScript requests that add interactivity for image requests for pictures or graphics. Five font requests for custom typography. These are all different types of requests a browser makes to load a web page.
00;10;21;18 - 00;10;35;22
Speaker 1
I'm having trouble wrapping my head around it. What is like, can you explain what the code for request is? And who is making that request of?
00;10;35;24 - 00;11;07;05
Speaker 2
Sure. Let's break it down. Our request is like a message sent from your web browser to a server. It says, hey, server, please send me this specific file or data. The server which stores website files responds by sending back the requested information. The code for a request is usually in HTML, JavaScript, or another web language.
00;11;07;07 - 00;11;16;28
Speaker 1
And what initiates this request?
00;11;17;01 - 00;11;43;00
Speaker 2
A request is initiated by your web browser when you visit a website or interact with elements on a page, like clicking a link or submitting a form. The browser sends the request to the server hosting the website to fetch the necessary files or data to display or update the content.
00;11;43;03 - 00;12;01;23
Speaker 1
Okay, so can one of those requests be like, if I'm moving my cursor across a page and I roll over a button and the button, like, changes or like it's bigger or something like that, that requires a request.
00;12;01;26 - 00;12;25;01
Speaker 2
Yep, exactly. That's often handled by JavaScript. When you hover over a button and it changes, the browser can send a request to a server or trigger a script to fetch additional data or animations, dynamically altering the buttons appearance. This is a great example of interactivity in action.
00;12;25;04 - 00;12;39;00
Speaker 1
Okay, so a static website does all the requests at the very beginning, and then none until you interact.
00;12;39;02 - 00;13;06;03
Speaker 2
That's right. A static website loads all its content with the initial requests. Once loaded, there's little to no further communication with the server, regardless of user interaction. Everything you see is pre-built and doesn't change unless you refresh the page or navigate to a new one.
00;13;06;05 - 00;13;28;00
Speaker 1
But let's So if we click a link that sends a request to the browser, anything, something, any time something changes, it sends a request to the server.
00;13;28;03 - 00;13;41;25
Speaker 1
Is that correct, Coco? Every time a change happens on a website or an app, a request is being sent from the browser to the server.
00;13;43;03 - 00;13;46;10
Speaker 1
Coco, can you hear me?
00;13;50;04 - 00;13;57;21
Speaker 2
Submitting a form or anything that changes the page triggers a new.
00;13;57;23 - 00;14;00;04
Speaker 1
Coco, you there?
00;14;05;02 - 00;14;06;18
Speaker 1
Hitting a.
00;14;09;13 - 00;14;15;11
Speaker 1
Hey, Gemini. I'm recording this for a podcast. Is that okay?
00;14;15;14 - 00;14;19;23
Speaker 2
Sure. That's absolutely fine. Feel free to record. Do you have any questions for me today?
00;14;20;00 - 00;14;51;23
Speaker 1
Yeah. So I was just talking to Microsoft Copilot, but, it had some difficulties. So we're going to finish the conversation here. We were talking about, things that make a website slow. We were talking about VPNs and stuff like that. And then we're talking about getting into the nitty gritty of what makes a website slow. And, copilot gave me unoptimized images, excessive plug scripts, caching, bulky code.
00;14;51;25 - 00;14;56;14
Speaker 1
Is there anything else you'd like to add to that list?
00;14;56;16 - 00;15;12;16
Speaker 2
Yeah, that's a good list. You could also add things like render blocking, JavaScript and CSS, which can delay how quickly a page loads. And sometimes the web hosting itself can be the issue. If it's not powerful enough to handle the website's traffic.
00;15;12;19 - 00;15;30;08
Speaker 1
Yeah. So we started the conversation talking about virtual private servers because, I'd like to build like a really cool website, and I'm just debating on whether I should go that route.
00;15;30;11 - 00;15;42;26
Speaker 2
It sounds like you're planning something exciting. I can definitely give you more control and resources, which is great for a high performance website. Have you thought about what kind of website you want to build?
00;15;42;28 - 00;16;00;24
Speaker 1
I don't want to get too off the subject that we were on, so I'm going to jump right back in there. Can you tell me about, requests? Can you explain what requests are between the browser and the server?
00;16;00;26 - 00;16;15;27
Speaker 2
Sure. So when you type a website address into your browser, it sends a request to the website server asking for the page's information. The server then processes that request and send back a response which your browser turns into the website. You see. Does that make sense?
00;16;16;00 - 00;16;19;11
Speaker 1
Yeah.
00;16;19;14 - 00;16;33;19
Speaker 2
Okay, great. So each of those requests and responses takes time. And the more there are, the longer it takes for the page to load. That's why optimizing those requests is a big deal when you're trying to speed things up.
00;16;33;22 - 00;16;40;28
Speaker 1
Do some requests take more Ram.
00;16;41;00 - 00;16;57;20
Speaker 2
Yeah, some requests can definitely use more Ram. It depends on what the server has to do to get the information. Like if it has to dig through a huge database that's going to take more processing power and Ram than just grabbing a simple image file.
00;16;57;23 - 00;17;09;25
Speaker 1
What are specific things that you can site that make a request like easier or harder?
00;17;09;27 - 00;17;22;21
Speaker 2
Okay, so requests that ask for a lot of data or need the server to do complicated calculations are harder. Think of it like asking for a whole book versus just a table of contents. The book takes way more effort.
00;17;22;24 - 00;17;29;12
Speaker 1
Okay, that makes sense. Can we go into scripts?
00;17;29;14 - 00;17;42;22
Speaker 2
Sure. So think of scripts as little programs that run on your website. They can do cool stuff, but if there are too many or if they're not written well, they can really slow things down. Does that make sense?
00;17;42;24 - 00;17;52;04
Speaker 1
Yeah. But let's let's dig into it a little bit more so I can understand like what a script is and does.
00;17;52;07 - 00;18;11;01
Speaker 2
Okay, let's break it down. Scripts are basically lines of code that tell a website what to do. Some scripts handle visual effects, others manage how the website interacts with visitors, and some even connect to other services online. The problem is, each script adds a little bit of extra work for the browser, and too many can really slow things down.
00;18;11;03 - 00;18;16;29
Speaker 1
Can you give me ten examples of what a script does?
00;18;17;01 - 00;18;39;09
Speaker 2
Okay. Here are ten examples of what a script can do on a website. First, they can handle interactive forms. Like when you fill out a contact page. Second, scripts can create image sliders or galleries. Third, they manage those little pop up windows you sometimes see. Fourth, scripts can control how videos play on a site. Fifth, they help with animations like making things fade in or slide around.
00;18;39;11 - 00;19;03;09
Speaker 2
Six scripts can track user activity, like what links people click on. Seventh, they can personalize content so you see different things depending on your past visits. Eight scripts can connect to social media feeds. Ninth, they help with search functions on a website. And 10th, script can manage shopping carts and online payments. Do you want to go into more detail on any of these?
00;19;03;12 - 00;19;17;27
Speaker 1
No. That gave me a good idea of what the whole script thing is. Can you? Let's go on to caching and how that relates to, styling a website down.
00;19;17;29 - 00;19;35;04
Speaker 2
Okay. Caching is like saving a copy of your website's files so the server doesn't have to work as hard every time someone visits. It's like keeping leftovers in the fridge much faster to reheat than cooking a whole new meal. But if the cache isn't set up right, or if it's holding on to old versions of the site, that can actually slow things down.
00;19;35;06 - 00;19;37;24
Speaker 2
Does that make sense?
00;19;37;26 - 00;19;46;07
Speaker 1
Yeah. Can you give me kind of like a pretty detailed report on how that works in the real world?
00;19;46;09 - 00;20;11;21
Speaker 2
Sure thing. So in the real world, caching happens at different levels. Your browser saves copies of website elements, and servers use caching to store frequently access data. There are also content delivery networks or CD's which store cached versions of websites across multiple servers around the world. This means that when someone visits your site, they get the data from a server that's geographically closer to them, making everything load faster.
00;20;11;23 - 00;20;19;05
Speaker 1
Okay, that makes sense. Let's talk about bulky code.
00;20;19;07 - 00;20;38;02
Speaker 2
Bulky code is basically when a website's code is longer or more complicated than it needs to be. This can happen for a bunch of reasons, like if the website has a lot of features, or if the code wasn't written efficiently. The problem is, all that extra code takes longer for the browser to process, which slows everything down.
00;20;38;05 - 00;20;53;12
Speaker 1
Okay, that makes, pretty good sense to me. Can you, can you go over the benefits of VPNs and the benefits of shared hosting?
00;20;53;15 - 00;21;09;22
Speaker 2
Sure. With a VP, you get your own dedicated resources, which means better performance and more control. Shared hosting is more affordable, but you're sharing resources with other websites so performance can vary.
00;21;09;24 - 00;21;21;02
Speaker 1
Can you go into the, additional control that you gain from a VPN?
00;21;21;04 - 00;21;38;28
Speaker 2
Okay, so with a VPN, you get root access, which means you can tweak server settings to perfectly match your website's needs. You can install custom software, optimize the server for speed, and have full control over security. It's like having your own dedicated machine, which gives you way more flexibility and power.
00;21;39;00 - 00;21;47;00
Speaker 1
Okay. I have no idea what root access means. Can you kind of dig into that?
00;21;47;03 - 00;22;10;23
Speaker 2
Okay. Think of it like this. Root access is like having the master key to your server. It lets you change absolutely any setting, install any software you want, and basically have complete control over how the server runs. It's super powerful, but you've got to be careful because one wrong move can cause big problems.
00;22;10;25 - 00;22;20;07
Speaker 1
Okay, what kind of settings, exist on a VPN. Can you give me a list?
00;22;20;09 - 00;22;41;07
Speaker 2
Okay, here's a list of some common settings you can tweak on a VPN. First, you can adjust the amount of Ram and CPU allocated to your server. Second, you can configure the web server software like Apache for engine X. Third, you can set up databases like MySQL or PostgreSQL. Fourth, you can manage security settings like firewalls and user permissions.
00;22;41;09 - 00;23;04;24
Speaker 2
Fifth, you can install and configure programing languages like Python or PHP six you can set up email servers. Seventh, you can manage DNS settings. Eight you can configure backups and disaster recovery. Ninth, you can monitor server performance. And 10th, you can set up virtual private networks or VPNs. Do you want to know more about any of these?
00;23;04;26 - 00;23;12;10
Speaker 1
Yeah, honestly, I'd like to get a better understanding of each of them.
00;23;12;13 - 00;23;32;11
Speaker 2
Okay, let's start with Ram and CPU. Ram is like your server, short term memory and CPU is its brain power. The more Ram and CPU you have, the faster your server can handle tasks. Then there's the web server software like Apache or Engine X. This is what actually delivers your website to visitors. You can tweak it settings to optimize how it handles requests.
00;23;32;13 - 00;23;44;15
Speaker 2
Next up are databases like MySQL or PostgreSQL. These store all your website's data, and optimizing them can make a big difference in speed. Do you want to go over the rest or dive deeper into any of these?
00;23;44;18 - 00;23;49;02
Speaker 1
Yeah, go over the rest real quick.
00;23;49;04 - 00;24;10;01
Speaker 2
Okay, so next up are security settings. You can set up firewalls to block unwanted traffic and manage user permissions to control who can access what on your server. Then there are programing languages like Python or PHP. These are what your website's code is written in, and you can install and configure them to best suit your needs. After that, you can set up email servers to handle sending and receiving emails from your website.
00;24;10;04 - 00;24;32;11
Speaker 2
DNS settings are like the phone book of the internet, connecting your website's name to its servers address. You can also configure backups and disaster recovery to make sure your website's data is safe. Server performance monitoring helps you keep an eye on things like CPU usage and Ram, so you can catch any issues early. And finally, you can set up virtual private networks or VPNs to securely connect to your server.
00;24;32;14 - 00;24;52;15
Speaker 1
Okay, so let's say that I'm looking at VPCs. I'm looking between ones with like four gigs of Ram or eight gigs of Ram, or even potentially 12 gigs of Ram. How do I make that decision?
00;24;52;18 - 00;25;11;24
Speaker 2
Okay, so the amount of Ram you need really depends on what your website will be doing. If you're planning a simple blog or a small business website, four gigabytes might be enough. But if you're building something more complex, like an e-commerce site or a website with lots of media, you'll probably want eight gigabytes or even 12 data bytes to keep things running smoothly.
00;25;11;26 - 00;25;42;09
Speaker 1
So I'd like to, I'd like to build a website that is kind of interactive. So it'll be pretty simple, mostly just image like a single image with, a bunch of hyperlinks. But I would like there to be some kind of ambiance to it. So I guess you probably do that with JavaScript.
00;25;42;11 - 00;25;58;26
Speaker 2
Okay, so for a single image with hyperlinks and some ambient JavaScript effects, you could probably get away with four gigabytes of Ram, especially if you optimize the image and JavaScript code. But if you think you might want to add more features later on, it might be worth going with eight gigabytes just to give yourself some room to grow.
00;25;58;29 - 00;26;11;18
Speaker 1
What would be kind of like, a next step up that would kind of almost necessitate eight gigs.
00;26;11;20 - 00;26;26;18
Speaker 2
Okay, so if you're planning on adding more complex JavaScript effects or handling more traffic, you might want to consider going with eight gigabytes of Ram. That'll give you some extra breathing room and ensure your website stays responsive.
00;26;26;21 - 00;26;34;09
Speaker 1
Can you describe what more complex JavaScript looks like?
00;26;34;12 - 00;26;51;24
Speaker 2
Sure. The more complex JavaScript might involve things like real time data updates, interactive maps, or even 3D animations. Think of it like the difference between a simple slideshow and a fully interactive video game running in your browser.
00;26;51;27 - 00;27;25;15
Speaker 1
Yeah, okay. That, that makes sense. Can you can you describe like a website and its JavaScript elements or other elements potentially. That would be good on a for gig of Ram and would use most of that and would be one that would be good on eight gigs of Ram. And how they differ.
00;27;25;17 - 00;27;50;02
Speaker 2
Okay, so on a four gigabytes Ram, you could comfortably run a blog with some light animations or a small e-commerce site with basic product filtering. But if you're planning on having lots of high resolution images, complex search functionalities, or a large number of products, you likely need the extra muscle of an eight gigabytes Ram. MVP's.
00;27;50;05 - 00;28;20;18
Speaker 1
I'm thinking more of, like potentially sound involved with the website as well. Is, JavaScript elements that, kind of enhance the environment. Like, like if there's a picture, or there's like a light, then it kind of pulses or glows like a light would.
00;28;20;20 - 00;28;40;02
Speaker 2
Okay. So for a website with sound and interactive elements like pulsing lights, you'll definitely want to consider going with eight gigabytes of Ram, sound files, and complex JavaScript animations can be pretty resource intensive, and you want to make sure your website runs smoothly.
00;28;40;05 - 00;28;53;00
Speaker 1
And then, can you go into what, a site that would need 12 gigs of Ram would look like?
00;28;53;02 - 00;29;15;20
Speaker 2
Okay, so a website that needs 12GB of Ram is definitely on the more intensive side. Think of things like high traffic e-commerce sites with tons of products and complex search filters, or maybe a site that streams high definition video or host online gaming. Those kinds of sites need a lot of processing power to keep things running smoothly.
00;29;15;22 - 00;29;28;24
Speaker 1
Okay, I think what I'm looking to do, at least for now, kind of falls pretty well in the eight gig category.
00;29;28;27 - 00;29;43;01
Speaker 2
Okay, so an eight gigabytes VP sounds like a good fit for your project. That'll give you enough power to handle the sound and interactive elements without any hiccups. Do you want to talk more about optimizing your website for performance?
00;29;43;04 - 00;29;57;13
Speaker 1
Not right now. I think that we'll get to that. Can you just touch on, how VPNs and security are related?
00;29;57;15 - 00;30;17;16
Speaker 2
Sure. So with a VP, you have more control over your server security settings. You can install your own firewall, manage user permissions, and keep everything up to date. It's like having your own little fortress, which is way more secure than sharing space with a bunch of other websites.
00;30;17;19 - 00;30;32;06
Speaker 1
Okay, can you kind of give us, an idea of what a shared server kind of is and looks like and what what you have to give up.
00;30;32;08 - 00;30;51;15
Speaker 2
Okay, so with shared hosting, you're basically renting space on a server that's hosting a bunch of other websites. It's like living in an apartment building. It's more affordable, but you have less control and you're sharing resources with everyone else. This can sometimes lead to slower performance or security risks. If another website on the server gets hacked.
00;30;51;17 - 00;30;56;12
Speaker 1
Okay, going to that.
00;30;56;15 - 00;31;02;28
Speaker 2
Okay. So you mentioned before that you were recording this for a podcast. Is there anything else you'd like to discuss for your recording?
00;31;03;00 - 00;31;13;28
Speaker 1
Yeah. I want you to talk about how if a website on your server gets hacked, then it can affect you.
00;31;14;00 - 00;31;30;11
Speaker 2
Okay, so if one website on a shared server gets hacked, it can definitely affect the other websites on that server. Hackers might use the compromised website to gain access to the server itself, and from there they could potentially access or even damage other websites hosted on the same server. It's like having a bad neighbor in an apartment building.
00;31;30;15 - 00;31;35;03
Speaker 2
Their problems can become your problem.
00;31;35;06 - 00;31;49;20
Speaker 1
Oh wow. So like, a hacker can find the weakest link on a server and just kind of get in through that and then have access to all of the websites.
00;31;49;23 - 00;32;04;15
Speaker 2
Exactly. Hackers often look for vulnerabilities in outdated software or weak passwords. Once they find a way in, they can move around the server and potentially access all the websites hosted there. It's definitely a risk to keep in mind.
00;32;04;17 - 00;32;30;07
Speaker 1
Okay, I got a pretty good idea about PCs and stuff like that. Is there anything else that you'd like to add on the subject before we sign off? And I just wanted to say, thank you for helping me kind of complete this, bit of research I had to do. But, if you'd like to add anything, go ahead.
00;32;30;09 - 00;32;50;17
Speaker 2
You're welcome. I'm glad I could help. Just one last thing. Remember that choosing the right hosting is just the first step to keep your website running fast. You'll also want to optimize those images, scripts, and code we talked about earlier. And don't forget about caching.
00;32;50;20 - 00;32;58;02
Speaker 1
Okay. Sounds good. I'll have to learn more about caching in the future. I think.
00;32;58;05 - 00;33;05;14
Speaker 2
Caching can get pretty technical, but it's really powerful for speeding things up when you're ready to dive in. Just let me know.
00;33;05;16 - 00;33;07;03
Speaker 1
Alright. Thanks, Gemini.