 So I really like the idea of Bisshoot. I'm not sure if you're familiar with it, so for the people who aren't familiar it's a sort of up-and-coming video streaming service that relies on BitTorrents. The idea of the BitTorrent to distribute the videos. Now they have their primary server so when you upload it, it goes to them and then they seed it out to others. But that means that other viewers can then seed it to more other viewers. And this, this is really nice for quite a few reasons. It's just in general more efficient on their servers, which then helps keep their operating costs down. That's an absolutely lovely thing. From from business perspective, but even from the viewer perspective, this helps a lot in areas with bad internet. Now, I know this personally is important to me because a rather sizable chunk of my viewers come from India. Not surprised by that one because we're talking about an up-and-coming industrial nation. They're not quite first world yet, but they're they're getting there and so you're seeing a tech presence. Building. So these videos are highly relevant to that area, but there are some other ones that are surprising, but definitely, I'd definitely like to help these people out. So we're talking like Algeria or Algeria was surprisingly high. It is a decent chunk from what was it? The country just above Costa Rica. It was a rather surprising amount from there as well. And at least from my understanding, the internet isn't great. Although correct me if I'm wrong there. A rather sizable amount from Pakistan and Nepal as well, which again, as I understand it, do not have great internet by any means. And so this really helps. It helps areas like that with higher viewership. Sorry, it helps areas like that with a better ability to view the video. Because you're seeding from a large amount of sources instead of just, you know, like what the way YouTube works. It's just from that single channel. It really helps out a lot. And recently BitShoot announced this, the ability to help them help them out by acting as a cryptocurrency mining node. I had a whole server going on here. Not just this machine, but a full-blown server as well. So we're gonna do this, actually change the size of that. At least for the purposes of this video. So I have not trusted this yet. So we're gonna need to do that, which is fine. I totally wind up trusting them. Obviously I want to run a considerably stricter environment on something like this, but so that's rather unsurprising as well. Have no problem with Cloudflare since they're one of the biggest CDNs in the world. It's always fun when you add the enhanced security stuff. Seeing how much stuff for any given website you actually wind up connecting to is interesting. You really want it on on a server, though. Even on some workstations in a business environment, it can be helpful for. Okay, so you're gonna see a jump just while I get my password because I obviously do not want that getting out to everybody and anybody. Okay, so now if we navigate to this, it was help us grow. So, okay, so we need to add a few more. Now I don't remember if that was a dot-com or what. Authored mine. And now we should be good. Okay, so also support jQuery. One is fine for this as well. It is always a pain in the ass to set up. SiftScience. Never heard of them as a CDN before, but let's see if this starts running. Okay, so it doesn't seem to be that, or it's just really slow and has no type of progress thing. But you're gonna see another jump because I'm about to look them up. Okay, so that's fine. And that's definitely everybody. I don't know why Microsoft blocks the about pages, but okay. So that's set up. Now, just so I give them a pretty decent chunk of the server load, but also not so much that the server can't do what I need it to do because even though I did transition this from, it used to be running Arch Linux. It's now running Windows Server 2012 R2 because I had a license for it and it wasn't being used. And for various reasons, I wanted Windows Server to actually be what the machine was running now. It still has, I'm setting this up, just Arch and Open Indiana right now, but it still has these and these will do the occasional build job, even though this is idling right now, as you can clearly see. But there's also services that are run directly on the server and aren't being run on any of the virtual machines. And so it does need some, it does need processor time and I want memory there as well. Yeah, this is the one we want. Really gotta change the color of you. So let's make you blue. I guess the one other thing, because I'm gonna need another counter actually for, I think you can do this for a specific process. What options do I have? Where's that under memory? Okay, so we're gonna pull up the task manager, because I know I can get the specifics from here. So that's not actually using up that much, which makes sense, because we're not seeing that much here either. A little bit of a spike for whatever reason, but generally this is staying pretty low, well below 5% on average. And the memory used from the specific process is not a whole lot, so we can crank this right up and see what happens now. Still not a whole lot going on. Of course, the thing is, since nothing is being shown here, and I'm pretty sure something should be shown here, it's very well possible that literally just nothing's happening at all, because maybe it's not happy about the IE protected environment. Yeah, because I'm still not seeing anything. What happens if we go over here? Start mining. Okay, so I guess what I'll do is I'll leave this running for a while, and then just come back to it just to get an idea of how much contributions I'm actually generating here. I'm not gonna be on this machine though, but yeah, ideally because I'm not maxing this server out in the majority of cases, I'm not even above 50% in the majority of cases, it's really just the builds where it suddenly skyrockets to 80-90% that I need this so I can leave something like this running on it for much of the time. Of course, I suppose the other thing is that there may be something blocked by the firewall that I would need to open up possibly depending on what ports are necessary, so we'll see. Well, as you can see, I definitely got this working. So what I'd like to do now is explain what I had to do for the folks out there like myself who are running this in quite a bit of a stricter environment, because this should work completely out of the box in the typical home environment where you have, I'm not sure exactly how this works. I'm trying to figure some of the details out with BitShoot, but I would expect in the typical home environment where you have a UPNP router that this should wind up being auto-configured for you. But I do not have that. Windows Firewall is quite strict, and that is a good thing, as long as you're willing to put up with figuring some of the stuff out. So this wound up being about an hour and a half of running the message analyzer and going through all the packets and filtering them appropriately. But what I did wind up coming up with, we've got two rules, and these are essentially going to be identical. You want ports 52450 open, 52454 through 52458 open, 52474 open, 55701 open, and 64085 open. Now these are TCP ports. As far as I can tell, you do not need any UDP ports open for this. And the outbound rules are going to wind up actually being the same. Once all of those are open, the entire thing seems to work out just fine. And obviously you're going to want to tune these appropriately. One thing that I did do that I would also strongly recommend that you do, if you're running it in this type of environment or it's also doing other things, is go into the Task Manager on the specific tasks. I set both of these just because in a server environment you're not really using Internet Explorer or any browser for any serious purposes. So I just went in to both of the processes and set priority to low, just so that if anything I actually need development or business-wise needs to be done, it'll completely bypass the Internet Explorer process and get what I need done first. Because, you know, I'm not a bleeding heart. I need to get shit done. I'll help out bit shoot when I can. So performance monitor-wise, I've got it tuned so that it's definitely using up the majority of it. I'm not really sure why, maybe it's just that it's not specifically processor time, like it's user time or something, but Internet Explorer is not using up basically anything, but you can clearly see CPU is doing work. And I have all of my virtual machines off. Granted, there's only two of them right now. I've got to set up my whole test lab all over again. I'm not doing any file transfers or anything else, so other than the network stuff, which I can do crapload and network stuff, and this thing doesn't even go above 5% CPU usage. So it's definitely using the majority of this. I mean the entirety of the CPU stuff. Memory usage-wise, this isn't bad at all, and that's to be expected given that hashing is overwhelmingly CPU intensive, and if the hash actually uses the GPU, GPU intensive. Performance monitor doesn't have any hooks into the GPU, so I would need to pull up another tool for the GPU usage, but I don't have one of those installed on here. Yeah, that's basically it. Then you have a working miner for BitShoot going on.