Bitcoin dominance is a metric that measures the percentage of Bitcoin's market cap compared to all other cryptocurrency combined. In simple terms, it's the percentage of all the money within cryptocurrencies that's held in Bitcoin. So for example, if the total amount of money in crypto was $1 trillion and Bitcoin's dominance was 50%, that means that out of the $1 trillion, $500 billion was held in Bitcoin. So why is this important? Because when Bitcoin's dominance begins to drop, usually that money flows into other crypto currencies causing other cryptos to outperform Bitcoin. So how can you use this to your advantage? This chart shows us the dominant cycle. Depending on what's going on in the market, you can refer to this to have an idea where the money is flowing to. If you can follow the money, then you won't miss out on profit. Watch part two, where I'll dive in deeper into the dominant cycle and how to profit from it. Don't forget to like and subscribe for more videos just like this.


Good Friday morning everybody I'm Tommy O'Brien coming to you live from TFN at 9am Eastern time it's jobs Friday 275,000 jobs added in the month of February the expectation was for about 200,000 jobs added we have the unemployment rate rising from 3.7% to 3.9% you do get 167,000 on the downside in terms of revisions for the prior two months nonetheless the market likes these numbers we trade to higher price S&Ps up by 13 points this morning trading at 5175 NASDAQ 100 or up by 43 points that's about a quarter percent 18,359 the Dow up by single digits 38,838 and how about the Russell up by 1.1% to 2110 Bitcoin hanging near record right near record highs Bitcoin up $90 at 68,455 crude drops this morning from $80 down to $78 and change we're trading at 7849 right now and how about gold it's not stopping man gold reaches 2192 on that number this morning at 830 we pair some of those gains gold still up by $15 on the session at 2179 60 right now and notes and bonds they'll be the focus today as we get the jobs number you got the 10 year right now positive by 10 ticks and it is interesting to see that quick move we got on that 830 jobs number you got the 10 year yield right now of 4.07% as we are approaching that 4% boundary line on the 10 year the 10 year yield 4.07% and you see it we got higher price lower yield across the board right now we jump over the dollar index DXY lower price man what do we got we got lower yield weaker dollar that's helping the gold contract of 4 of course and the market is liking things across the board right now it's going to be an interesting Friday folks we got higher prices across the board we'll break down some of those economic numbers from the non-farm payrolls we got at 830 this morning unemployment rising from 3.7% now at 3.9% still under 4% quite a remarkable number we'll talk about some of the wages stay tuned folks we're going to have an action packed hour we got markets in positive territory and how about navidia it just don't stop man navidia is going to trade up by what is that almost a $30 increase in the overnight session we hit $9.59 we're trading at $9.54 navidia looks like it's heading to a thousand dollars nice round number stay tuned folks we're coming back in three minutes for the morning market kickoff we'll be right back don't go away


So, I'm Leslie Johnston. I am the Director of Development and Tools Management at the U.S. National Archives. That means that I have responsibility for the software development application support but more relevant to this talk for the electronic records management systems at the National Archive and for its digital preservation infrastructure. So I'm going to go ahead and talk today about what we're doing to replace the ERA Electronic Records Archives with ERA 2.0, which I know is not the most exciting new name but as one of our leaders put it to me, we will always have an electronic records archive so let's just keep calling it the Electronic Records Archive. So right now the Electronic Records Archive encompasses all the operations for scheduling, transferring, reviewing, describing, transforming and storing electronic records that we get from U.S. federal agencies. That's about 275 agencies that we receive the permanent records from and that's a distinction because that doesn't mean that we get every record produced by every agency or every document produced by every agency but we do get all of their permanent records as they identify and negotiate with us on records retention schedules. Right now the ERA system is multiple systems. We have a system for unclassified federal records, we have a system for presidential records, we have a system for Title XIII or census records, and we have a system for legislative records in part because all of those systems actually operate under different regulations and have different access and controls on top of them as per those regulations. So we developed the current system in the early 2000s. This was a large process with stakeholder requirements developed all over the agency but it was scoped with a single system in mind to deliver all aspects of functionality from scheduling through to public access. The system as it was actually implemented supports scheduling, submission and transfer and only one workflow right now for federal records that come under schedules from other agencies. It is used by dozens of NARA staff to process, it's used by hundreds of staff at federal agencies to actually bring the records over to NARA and this was a very successful project in that it also leveraged a lot of community work and a lot of community tools. We integrated pronom, droid, jove, so this was in many ways a successful project in that at the end of the project we had a working system that we could use to transfer records and manage them at the archives but I would not say that it was a 100% successful project and we learned some lessons from this. We had over 1400 requirements which meant that it was very difficult to actually implement the system in the schedule that we had planned and to actually bring all of the functionality into production and one of the areas that was not fully put into production were the digital preservation functions of the system. We had communication challenges, we had a lot of change management challenges because we were introducing new processes not only for the NARA staff but for the staff at over 200 agencies that were transferring the records to us. So anybody that is familiar with the system knows that we actually did put our development into a holding pattern in 2012 and made plans for future work but stopped all work. So we are now developing and refactoring the ERA 2.0 system because we need to actually improve the efficiency for the full life cycle of the records. We are not developing a single system, we are actually developing multiple modules of a system in a highly modular way. We are leveraging a lot of open source and I'll get to that a little bit later in the presentation and a high level of interoperability with other tools at NARA which is something that we didn't quite accomplish in the first implementation of the first system. So one thing I do want to mention about how we are doing this project differently is that this is an agile project for people that are familiar with the concept of agile software development. We're using a flavor of agile that isn't scrum or can ban but is called agile with discipline. So we actually did start off with a set of use cases but we have developed user stories for all of our functionality. We are doing four week sprints. We started the work in fall of 2014 so we are about two thirds of the way through the development right now. Each of the user stories provides the implementation, the acceptance criteria, the definition of done for each of the user stories so we can actually write the test cases and test this and at the end of every four weeks we have more working code and in fact since the end of the first four weeks sprint we've actually had a working system that has just grown iteratively over time. The work is being implemented by IBM as our partner. IBM has the responsibility for the current ERA system and its operations and maintenance. This has been an extraordinarily successful partnership for us. We have about 40 contractors on the project from project managers to analysts to software developers and software architects. So I'm going to talk a little bit about what the different parts of the system are. We have a digital processing environment. This is actually in many ways the newest and most exciting part of the program for us because this actually is something we haven't had before and I'll just say that this was a very manual bespoke workflow for us for each unit. Each unit had a set of tools that it needed to work with the born digital records but they would have to work on them locally. So things would come into ERA, things would get downloaded, things would get processed, things would get re-uploaded. This is not a very efficient process for the processing and review and potentially redaction and creation of public use copies of the records. So we are now working in an entirely cloud based environment. All the development is in the cloud, the pilot is in the cloud and the production system will be in the cloud but all the processing is also in the cloud. So we're working with about 15 tools right now, both open source and commercial that are actually embedded either into the tool itself or are available to each of the archivists who has their own virtual cloud based workbench to do all of their work. So this includes format characterization, bulk file formatting, image manipulation, common business productivity systems like Office, working with PII identification as well as redaction. So the second module which is one of the modules that we also needed very much for this is the Digital Object Repository. This is all of our holdings management, all of our preservation functions but this is also our staff preservation and staff searching functions, not the public. The public will continue to work in our National Archives catalog. This is where we actually maintain the audit trail for all of the preservation actions that are taken. Every action, this is a very transaction heavy system and it does track all events and provides advanced search not only for the metadata for the objects but also the full text of the objects if they are text objects. Not surprisingly because we have a number of different levels of classification or sensitivity or ownership or access controls based on whether these are federal, presidential or congressional records. We have a lot of different groups and user types identified in the system so that it may be that say the congressional records that come in to that group, they can see that the records exist, they can see the full text of the records and they have full access to them to take whatever actions are necessary but someone in the presidential records that should not have access to those might be able to see that those records exist but cannot see a preview of those records or read the text. Some of the records may actually be dark because they have say a 20, 30, 50, 70 year hold on them and if you aren't in the custodial unit that has access to them you won't even see them come up in your search results. So we have very granular controls placed into the system. The business object management module, the bomb module and yes there's always a lot of jokes about it being the bomb and I get very tired of that very quickly as Meg can contest is the system through which we actually bring scheduled records into the system, it's through which agencies actually submit schedules, schedules go in, transfers need to be applied to the schedules for us to accept them. Right now that's the only workflow we have in the current ERE system. We are opening up all workflows in the new system for federal presidential legislative judicial records, donated records but more importantly for our preservation efforts for our digitized copies of our analog holdings that we have at NARA. This is something that we haven't done before, we haven't had a good preservation mode or in fact even a policy for the retention of the digitized copies. We have a policy that is actually going through the policy issuing process right now out of our digitization governance board that I serve on and we now will have a formal policy that we can point to that says that we do actually retain our digitized copies on the same schedule as the analog records they represent. They will be coming into ERA to be managed and preserved alongside everything else. So I know you can't even read this slide but this is an example of some of the preservation functions that we are building into the system in this new iteration and we describe these as user stories in an agile fashion. We validated these and identified these against both ISO 14721 and ISO 16363. We use Track and Dram Bora to actually check ourselves as we were developing these and its user stories like as an administrator I want to receive regular reports on all incidents of data corruption or loss and the steps taken to repair, replace, corrupt or lost data. As an archivist I want to be able to demonstrate the provenance of digital objects through downloadable reports documenting their traceability from receipt. As an archivist I want to ingest transformations of digital objects stored in the repository in order to store reference and preservation copies. So you get the sense that we've actually looked at the requirements out of the community very closely and mapped them into our development. In terms of the implementation of these I would say we're about halfway through with the preservation functions and we are two-thirds of the way through the development and when I get through the slides I'm actually going to show some screenshots because I'm not so careless as to attempt a live demo from a hotel to a VPN to a cloud location because I know what would happen if I tried to do that. But I can attest that this is a live system that we have about 100 NARA staff actually testing and using right now and I even have a witness in the audience who has seen it and can swear that it exists, can't you Meg? Thank you. So the implementation, each of the modules is an independent code base. We are doing this all in Amazon Web Services. This is not actually happening in the GovCloud, this is actually using Commodity Amazon. This is a custom Java application for us so we are doing the development ourselves but this uses all open source in the stack. So the indexing is done with Elasticsearch. We are using open Amazon services, you know all of the tools that we are building into this are open source except where we need commercial tools that are required for the processing such as needing to use Excel or Oracle or SQL Server to work with certain record types that we have received because when we reissued our transfer guidance in 2014 we extended the formats that we accept from agencies from a very prescribed list of about six to a much more inclusive list of about 60. So we were already getting a lot of these formats but now we are formally accepting them and provide guidance to the agencies on how the files should be formatted to be transferred to us and that means greatly expanding the set of tools that we make available to the archivists to actually work with these files and their work will be done entirely in the cloud because frankly the agencies are keeping their records in the cloud. So we are very much following a data at rest model for this and we have quite a few agencies that have said alright we're already keeping it in the cloud can we just transfer control of these spaces to you from our agency to NARA and we just transfer logical controls over these files without ever having to move the files from wherever it is at the agency to tum some type of media or transfer it over the network and then bring it down onto a machine at NARA and then load it onto a server at NARA that then would then get to transfer it onto a desktop and you get the idea of not only how many moves this is but how much risk this introduced into the preservation of the objects if we had to move them this often. So we are in pilot we're in phase five of the pilot now we will be releasing this into production in early calendar 2018. This will be for the unclassified records it's going to take us about a year and a half to do the classified instance. There are cloud implementations that are rated up to Fizmahai for sensitive records so we could put anything through title 13 and census things that have PII in the cloud but we haven't yet gotten access to a cloud environment that would allow top secret SCI all the compartments of top secret and SCI but this could change but the architectures and the tools that we're building with even if they're Amazon tools like elastic search we're stick building everything so we can actually pick up all of these services and tools and move them into an on-premise private cloud if we need to if we can't take advantage of a commodity cloud a year from now when we start doing the development of the classified environment. So now comes the fun part actual screenshots from a real system. So we have already built out the capability for all of the uploads for agency users as well as narrow users if they're say in our digitization labs and need to upload files from the labs they can associate metadata either in batch if metadata comes in from the agencies this is not always a common enough activity that agencies actually send us metadata we hope for it but we cannot actually mandate it or require it. We can manage access to them by business unit transfer digital materials we have a full workflow already in place in the system that allows assignment and transfer of tasks within units and between the custodial units as needed. They can manage their files in the metadata path as they exist they can rearrange and do new arrangements as needed. We have a shopping cart function I will say that I'm not enamored of the phrase shopping cart but it is a very commonly used phrase it's very well understood by the archivist the technical staff and by the leadership so I think we're going to be sticking with that. In the processing environment you can search by metadata not by full text the full text is only available in the object repository. So you can do browse and fielded metadata search the file paths we also have already built out the restful API for the processing environment and we're right now in the process of integrating the API for DAZ our descriptive tool that we use at NARA which is also a web based tool so that we can automatically transfer and hook on to the ID's the NAID's that are in our descriptive service and hook these in and transfer them automatically into the descriptive service so there's then an automated path from these to go through there into the National Archives catalog in a much more efficient way than send the files to Gary which is the current workflow at NARA. You can use a remote workbench instance it looks like a Windows workbench because that's what we're actually working with right now so this is the archivist working each archivist has their own workbench we right now have one workbench image but regret getting ready to release numerous workbench images because the archivist that are working with textual need different tools from the archivist that are working with audio or video or GIS so we will have personalized workbenches they can also use the embedded tools the embedded tools are you know Joy, Drove, Droid, Jov the PII and also the redaction tools we can work in a grid based UI metadata can be imported it can also be exported as can the objects we then create a SIP that moves them into the repository environment and when I say move the files do not move this is entirely by logical controls that means the control of the processing environment is then given over to the control of the repository environment and that is where the full text indexing happens and where the preservation controls come in we can as I said do browse do search navigate through their preservation structure we retain the original structure through which they came in because the arrangement of the files often has meaning as to how the agencies gave them to us and how our archivist process them if files need to be reprocessed for any reason such as a classification change something might be declassified NARA has the authority to declassify classified files files can then be moved back into the processing environment or if we need to do some sort of bulk automation or preservation action such as changing all of our JPEG 2000s that we get from our partners into JPEGs for public use you move them back into the processing environment their versioned and then the new versions are come back in and are re-associated with the original objects in the repository full set of metadata some metadata editing and reporting this is where a lot of the preservation auditing is I often call this my personal favorite part of the system because I'm actually responsible I am the system owner for the ERA systems so when we do the preservation auditing and when I need to do my monthly and quarterly reports on the preservation status of NARA's holdings I will say that currently that is too manual a process for my taste and I can now actually run what to me are now magically automated reports on the preservation status on the actions that have been taken on the file formats within the holdings and next steps for this will be actually creating format action plans that we can take automated use against I don't know that I will have those in at the time that we go live at the beginning of 2018 but those are a very high priority for me as we're restructuring our digital preservation activities and units and responsibilities at NARA to make sure that this is as automated a process as possible to do the auditing of the collections and I have even left time for questions thank you for showing up today I very much appreciate it


This is my talk on development to DevOps. All right. Slideshow is not what I want. That's me. Here we go. So this is my talk on development to DevOps. Hi. My name is Justin Burris. I'm typically a Ruby developer, and I had the opportunity recently to do about three and a half months of DevOps work. And so kind of the synthesis, I worked for Neo. We're a product development company here in Singapore. So kind of the synthesis of this is that I'd never done DevOps work before. And I was kind of curious about this new kind of exciting area for me to work in. And what I mean by DevOps is basically taking your application and deploying it to production. And all the things associated with that. And so this talk is kind of all the things that I wish I had known when I first started doing it. And maybe some things that can help you now if you're doing DevOps work. Yeah, but first why? So while kind of starting on this DevOps work, I encountered a lot of tools. I encountered a lot of methodologies. I encountered a lot of different thoughts about how to do this kind of work. And it's really important to kind of keep in mind what your goal is. And so throughout the talk, I hope to communicate that. So I first want to start off with automation. And basically automation in this context means how to make it to where your whole pipeline for taking your code from your Git repository or your local machines and deploying it to production can be fully automated.  So my first piece of advice is that you want to automate early. Some people might have some issue with this in that you're going to have to change your code as the situation develops because assumptions that you make early on will not hold up later on in the process. But if you automate early and you have your whole process built up in an automated manner, all you have to do is tweak your code that does your deployments. Let's turn off Wi-Fi. So in the vein of having an early automation, you want to make sure that you have easy to use checkpoints. And what's nice about this idea of checkpoints is that if you do have a change in your whole deployment process, you can just change that single checkpoint. And so you don't have to change your whole automation flow. And additionally, what's nice about these checkpoints is that it makes it a lot easier to debug. So whenever you have problems in your code, you can just think like, okay, this is part of this section and this piece. And so I'm just going to flip a flag and I'll be able to debug that section. And believe me, you're going to want to debug. So in that vein, you want to make your whole system modular if you can. So you want to have pluggable pieces. Our particular setup was pretty complex. We have at least two data centers that our code operates in. One of them is behind a firewall and we don't have direct access to it. We have to have a pretty interesting FTP transfer of the files to it. And so as a result of this, we have a lot of code that needs to run in multiple places and do similar things. And so by making it modular, it made it really easy. Also, you want to make sure any long-running jobs you have are very visible. This is mostly a development suggestion. So whatever you're doing, this kind of DevOps-y work, like you're building up a server from scratch or you're running a new Ansible script or a Chef deploy or something like that, it can take a long time sometimes. And if you have an error while that thing is running, you want to know as soon as you can so that you can either fix it and start it again or debug or dive into it. I suggest like pings on your computer, anything that you can do to make it visible. Blank the tab, make a noise, whatever. So this is part of the automation flow. You want to make it as painless as possible to build from scratch. And by scratch, I mean from an ISO that you download from a website, all the way up to your production box. And so the way you can kind of do this, I'll describe later in the process section. But starting from scratch to production makes it really easy to change any part of your system at any time. So finally, create an assembly line. So whenever you do your automation flow, you want to have distinct pieces and parts as your system builds. So for example, you'll have the phase that takes the ISO and converts it into some sort of image. And then you'll take that image and you'll deploy to a box. And you take that box and you deploy all the core system utilities that you need to have on it. And when you think about it in a assembly line process, it can make it very easy to parallelize. So process. So it's really important that you give your developers what they need. So this is kind of an interesting concept for me because I'd always thought of DevOps as like just building the servers to get the code to run on production. But you're actually working to get code on production and to satisfy the needs of all the people that are building the app. And it's really important to kind of think about them while you're building out your various automation flows and et cetera. And to this thing, you want to make sure that any diagrams you have of your ecosystem are multiple layers of levels of fidelity. And what I mean by that is that you should have one diagram that has your whole data center or data centers on it with all the connections and all the information. But when you have so much information on one graph, it can make it really hard to kind of narrow down and see just a small piece of that. So you want to take that diagram and then kind of build a pyramid out of it to where your bottom level has the most fidelity and your top level has individual small sections. So it can make it really easy to see at a glance what's going on in your system. Write down everything. And I really do mean everything. So one of the things that I started to notice is that with these kind of complex systems and interactions, all of these things sometimes aren't documented anywhere.  They might have a very strong vision for the way that all these servers will be built and deployed. But if it's not written down, it's not that useful because you have to constantly go to them. But if you have everything written down somewhere that's accessible, it makes it really easy for the whole dev team to be able to get into it and see what's going on. So Bjorn talked a little bit about pairing. And we did some pairing with our DevOps system. And I would suggest that you pair often on anything that's a configuration or a discovery task. So if you're trying to learn the best way to deploy a particular software package or to build an RPM from scratch, things like that, I'd really suggest you pair with another developer. But that said, you should really pair sparingly on things that are just tasks that you automate. So if you're building out your Ansible playbooks or your Chef recipes or whatever else other crazy things you do, you don't really need to pair on that stuff. Because it's just kind of like, once you figure it out, you just do it. So borrowing from Python, explicit is way better than implicit with this stuff. Whenever you have these kind of implicit assumptions that are hidden somewhere in some piece of your code, it can make it really hard to kind of know the whole flow at that point in time because there's so many complex systems. So for example, in our setup, we had about 36 distinct servers that all ran like different pieces of software and different data centers. And so for me to like get my headspace into this one server for things to not be explicit would mean that I have to hold a whole bunch of extra context in addition to the context or just that one server. Also, validate what you build. So this is really important. And what I mean by validate what you build is that when you're building out these servers and all this code that lives on them, just due to the nature of it, you're going to be making assumptions about, you know, what the dev team needs in terms of the software packages, what your business owners need in terms of like the connections that these servers make with each other. And so any time you have an assumption, you should definitely validate it. An example is we thought that our packages wouldn't have access to some specific software utilities. And so we did a lot of work that we didn't need to do to kind of work around that restriction. But if we had just like communicated with the business owner about this assumption we had, we would have just been able to knock it out and not even worry about it. So upkeep. During the nature of all this kind of automation and process and all these software things that you're using in your gluing together, you're going to have inevitable upkeep of them. So I really recommend that you have a utility belt pulling straight from Batman on this. So a utility belt is basically just your software tools that you use in order to build out your environment. And what's great about thinking about things in terms of a utility belt is that you try and use these tools to the best of their ability. And you only start to branch out and write code when you have to. And this is like a really important point because the more code that you write, the more chances you'll have to mess things up. And so our utility belt consisted of our VMware setup and a tool called RBVmoney which allows you to script to VMware environments with Ruby. I really love this tool. It's awesome.  But essentially what this enabled us to do is to pass a few flags and we could spin up our whole environment with a single command at the command line. Ansible is a tool that we use to actually build software packages on the box. Packer is a tool we use to take an ISO and turn it into a VM, an image that we could use to deploy with VMware. And then for a little while we were using Trello to kind of manage all these tasks that we needed to do. We've since moved to another tracking system but just have a tracking system. What do you use now? We use Mangle now, which is a ThoughtWorks product. So you want to make the pain development trade-off every day. And so what I mean by this is when you're working on this stuff you're going to have a lot to do. I mean just tons of work that you have to do in order to get this stuff spun up. And so you only want to start developing code when it becomes painful. But you need to make that decision every single day.  This may sound like really plain to the people who have done DevOps before, but do not assume your app is going to copy and paste into production. It won't. There's going to be all sorts of like strange differences between like your Mac box that developers work on and then like the Red Hat Enterprise Linux box you're deploying to. And then even between your different servers, if you run different operating systems, there's all sorts of crazy things you can run into. Even differences as subtle as like Red Hat 6.1 versus Red Hat 6.4. These things all have different packages that they bundle up. And sometimes they have different patch levels and there's a lot of things you need to consider. And so that's why you want to get things to, you know, box as soon as you can. So whenever you do this, you're never really going to face problems in your debugging cycle. And so my suggestion in that is whenever you have a problem, you want to profile backwards. And what I mean by this is that you don't want to immediately dive into the deepest level of your stack. So you don't want to just a bug down in like the actual box where the commands are running. You kind of want to take a higher look in my suggestion and kind of make sure that everything is working from the top down. Because typically the actual system utilities work just fine. And you probably have some assumption somewhere in your code that's not actually true in reality. So inevitably when you write all this automation code, you write all these glue scripts together and you know your assumptions are validated, they're invalidated. There's going to be pieces of your code that are just no longer relevant. And much like a garden, you need to weed these things out. If you don't, you're going to end up having a lot of extra baggage that you have to maintain and think about whenever you dive in. So TLDR, if you take only one thing from each of these points, if you're going to automate, you want to create an assembly line. If you're going to keep a process, you want to validate what you build. And finally, you always want to keep that garden tending. Thanks. Any questions? Ah, good question. I should have included a slide about that. This is maybe a controversial opinion, but when you're doing Ansible deploys, I kind of believe that Ansible does your testing for you.  And then Ansible goes on and does it for you. There are tools that enable you to test things like Ansible, but we just found them really redundant and they didn't help out very much. Our Ruby code that we used is glue. You could definitely test that, but once again, we didn't find it very useful because if it didn't work, it just would blow up and then you would know immediately because you have a whole automation flow with this thing. So once you actually have all of your servers up and running, there's a lot of really good tools that enable you to monitor them, such as Nagios, Splunk, et cetera.  It's not so much going out and testing. It's more like something that continues to check in that it's always working. Because the thing is too, it's not just your code that's going to be living on these boxes. It's also going to be the app that's running. And so essentially, if you think about this whole system is set up to make sure an app runs, as long as you have something that checks that makes sure that app is running, then you can be reasonably assured that things are okay from what I've seen. What about making your code more agnostic, in a sense, without the framework like Hadoop or Bezos, to manage all these cluster servers' requirements and make that transparent for your developers? Yeah, so for the most part, our developers don't have to care about what hardware or software stack they run on. They live pretty much on OSX all the time and they have no idea or maybe don't even have to care about the fact that we're on Red Hat 6.1 or 6.4 or anything like that. Wouldn't such a framework ease you into the whole deployment cycle where you just don't care? And all you need to do is think about just resource education and that scripted already on the framework like this one? I don't know. Look it up, look it up. Yeah, I'd have to look that up. Have you taken a lot of what I'm hearing and a lot of what I've run into in my own situation is parity between developer, developer system, test, deployment, production and keeping everything the same, the pipeline if you will. You've got some tools that you keep on top of VMware which we actually just finished getting rid of in a couple of weeks ago, finally. We're now on Docker for depth run Docker tests run against Docker containers because the container is a container, the container is a container. Have you guys taken a look at that for your stuff? Yeah, so when this project first started out there's a lot of discussion about whether or not we should use something like Docker. There are two main reasons why we decided against it for this project. The first one being that at the time Docker wasn't in a stable state and wasn't really production ready. Additionally, due to the nature of this particular project, software like Docker wouldn't have been possible. We don't really control one of the data centers in terms of the physical machines or the VM system that runs upon it. Now, a lot of this stuff is with that kind of taken in mind. So if you're deploying to something like AWS, you have a lot more freedom in terms of what you can do. But one of our data centers we do control but we still wouldn't be able to really use a system like that unfortunately. But that said, I do feel like that kind of development style is like something that I would have loved to have had. Because in that case, a lot of these issues I ran into where the system wouldn't work in production due to some assumption that a developer had made due to the underlying utilities built into the system Docker would have solved. Thank you, Justin. Oh, thank you. Okay, so let's do the...


Tonight, we delve into insecurity, the PIB, river state politics and what the future holds for the APC in the state that CWP decides joins us to discuss this and more on post-politics. And then of course the House of Representatives bill threatens five years jail term for unlawful protesters. This is post-politics and I very unequivocally. The year 2021 has been awash with events of kidnapping, abductions and insecurity. Even to the banning of Twitter, the fight for the electoral bill and the finding out of a new addition to the bill, well the passage of the petroleum industry bill is not left out and the controversy about the revenue percentage accrued to the host communities. The former director general of the Nigerian Maritime Administration and Safety Agency, Namasa Nakoko-Petisai joins us right now to discuss the state of the nation as well as some other issues in the Niger Delta. It's good to have you join us. Thank you. Good evening. Well, I apologize to everyone for starting behind time but of course the conversation is about to start. Now, just like I said, one of the most controversial issues right now is the PIB, the argument from 2% to 5% to the 30% that is also going to be used for, you know, frontiers. Frontiers. Let's start with the issue of the PIB. The host communities have said that they initially proposed 10% but they were hoping for 5% all they could get was 2.5%. But what are your thoughts because the different people, I remember Chief JP Clark yesterday said that this is satanic and he called it very unfair to the people who are in the host communities but what are your thoughts on the position of the National Assembly? Alright, thank you very much. Let me start by correcting an impression that the host communities asked for 10% and that they are willing to settle for 5%. That is not the truth. That does not represent the true situation. I'm privileged to come from one of the host communities, one of the host oil producing communities. Now, the record that the PIB was first presented on the floor of the house some 12 years ago, that's one. At the time it was presented, the government, because it was an executive building, proposed 10% for the host community development fund. So it was government that proposed. The host communities have insisted all along that what they want is to control their resources and pay tax to the center and that's the model in other parts of the world, in the United States and in other places where you extract mineral resources and that is a sustainable model actually. What it does is it encourages people to work very hard and contribute to the center. It has worked everywhere that they've applied that model. But again, back to the PIB as it is now, it's not just talking about the ideal, let's be a bit more realistic and dynamic in our proposal and in the solutions we'll talk about. The current situation is that the Senate has proposed 3% to the host community development fund whereas the house version has proposed 5% to the host community fund and if you listen very well to Chief E.K. Clarke and other leaders of the Niger Delta who are mostly, who are very often they are the host communities of oil and gas activities. Now they said neither the 3% nor 5% is acceptable to them, so it's not like they would have preferred 5%. Is that clear? I spoke to a representative of PANDEF yesterday and he said that 5% would have been better if they were offered that. I'm pretty sure he wasn't speaking for PANDEF. Well he was. He was speaking for himself. No, he was definitely speaking for himself. Now Chief Clarke and other leaders of that region has made it very clear that the minimum they will accept is 10% because that's a part of fairness and justice. What he simply says is that listen, I contribute my shares and you are giving me one button out of the shares. So for other people to use this share and dress up and have only a button to myself, if you take a helicopter flight through that area and see the level of degradation, the level of environmental challenge they face, not coupled with the fact of climate change, you know that if people are literally in danger, they're almost going extinct. I want to say that even 5% intervention would not help their mother much. So what do you propose the Senate or the House would have done? Because the House is saying, as at today, when people were attacking the National Assembly, the House said that they are sticking to the original plan and the original proposal. They do not, they cannot speak for the Senate. So what would you have preferred that be done because you are from the host community? I'm not only from the host community. I used to be a member of the National Assembly. So I think I kind of understand how the mind of members of National Assembly work is a national institution where they try to accommodate the interests of all segments of the country. But in a community... At the expense of who? Because you just mentioned that if you take a helicopter ride above these communities, the level of degradation, the kinds of things that they're faced with is pretty bad. So if you are taking into consideration the state of everybody, you know, everybody's interests at the expense of the other people, I mean shouldn't they be the ones who benefit more because they're the ones who are experiencing most of the hazards that come from exploration in those communities? You're very correct. And so that's the position of the people of the host communities. But there is even a greater challenge. Now, if you want sustainability in the oil and gas industry, if you want peace, if you want cooperation of the communities, then you just have to be fair to them. They're not asking for so much. Now, when we talk about 3%, 5%, 10%, 3% or 5% or 10% of what operating expenses, operating expenditure, that's what they're asking for. It will not affect what the contribution to the collective force at the center. So I don't think that being fair to the communities that inhabit the area where you drill oil from. They suffer pollution. Their lives are in danger. In reverse state, of course, you know they're dealing with suits on daily basis. Oh, yes. Now they've got long problem, long problem, affect kidneys, cancer. They face all those challenges for the collective good of all at their own detriments, so their own detriments. So all they're asking for is, please, can you be fair to us? I think that both the house and Senate should be fair to the host communities because that's the part of peace. That's the part of sustainability of drilling oil. Now, oil is a vanishing product of commodity. A time will come when oil may be there. It may not be needed by the rest of the world. In some cities, you have more electric cars than fossil-fuel powered cars. So in the near future, the oil may be there. You have destroyed the environment. You've destroyed their source of livelihood. And it's given them nothing in return. But I want to put you on the hot seat because you were the boss of Nimasah.  I remember, I lived in reverse state for six years. I was one of the people who were in the forefront of talking about the issue of the suits in reverse state. We tried to get the attention of the states. The states kicked it to the federal. The federal, I mean, it was a ping-pong game. And today you're here speaking about the suits. What role did you play in all of this? Because we're here now talking about spilled milk. It's almost done. So, I mean, what role did you play? Well, I like to define two things. The first one is the role of Nimasah and my role as chief executive of the Manitama administration of the country. And my role as a statesman in reverse, that's two different things. Well, as Nimasah, our function is regulatory. Regulate shipping and maritime activities. That we know. There's an agency to regulate the environment. In any case, the issue of environment is the concurrent list. It's under the purview of the state as much as under the purview of the center, the federal government. So primarily, it is not my responsibility as chief executive or the agency, the responsibility, not is it the primary responsibility of the agency. The responsibility of the agency is to the extent that it mitigates pollution arising from shipping activities. That we understand.  You're a passing man. I'd like to talk about being a key stakeholder in reverse states. Yes. Now, I'd like to draw your attention to the fact that I made a series of open letters to the governor of reverse states, to the federal minister of environment, drawing the attention to the dangers of the continuous, the fact of having suits in reverse states. Danger to the health of the people. Danger to the means of livelihood. And of course, I have sufficient data to show that it's done enormous damage to the health of the people. And what response did you get? Now, I got some complications from the federal minister of environmental various times. At some point, they raised the issue that they were not getting enough cooperation from reverse state government. At other times, they said, listen, we're dealing with it. I'm curious to understand what cooperation the reverse state government was supposed to give. I remember in the year 2017, if I'm not mistaken, a committee was put together by the state government to look into the suit. I remember a lemon petrochemical, some of those people. We're part of the committee. Exactly. Very much always. But when you say that there was no cooperation from the reverse state government, how do you mean? I'm telling you the communication I got from federal minister of environment. But you lived in reverse states. You came to reverse states. You breathed that air. If somebody gives you information, do you not take further steps to understand what cooperation meant and how you could further push for a move from the federal government? Apparently. Now, what happened is that the two levels of government were acting in opposite direction. The federal government or the federal minister of environment had her own ideas of how to solve the suit problem. And he has to be solved. Now, they attributed it to illegal refining of petroleum products. That was, for them, that was the primary cause of the suit in reverse states. What in local parlance is called profile. Now, one of the things they did, and of course I will not always agree with that approach, was to put the energy on the alert and ensure that you stop illegal refining of petroleum products. But that does not clean the environment. Now, they've also initiated what they call the high prep program. The high prep program was originally focused on the Ogoni areas. But in the course of this, the federal expanded their mandate to other areas of reverse states. But like every other thing, it requires a process. And I know that you've done a number of remedial measures. I am not satisfied with what you've done. I have seen pictures. I have seen videos recently. I'm talking about 2021 and the suit is still in the air. Oh, yes, definitely. I think these remedial efforts seem to be of no avail. Again, I ask, what pressure have you put in 2021 on the government, the federal government, because again, the federal government has the power to security agencies. They're the powers that descend here to deal with it. Refining of petroleum. Which you have pointed that the federal ministry of environment has said is the major cause for... From their studies, yes. Exactly. So what is holding the federal government from cleaning it out entirely? Because we have the rains now. No, but what I can say to you, that I can turn on the statistics that reasonably, the level of suit has dropped. Has it? Yes, it has. I can tell you that. Now, the number of illegal refining of crude has also dropped because of the intervention of the Navy. Now, what remains to be done is the fact that the federal ministry of environment should work collaboratively with the University of the Ministry of Environment and begin to clean impacted sites and impacted environment. That's the next logical step I expect them to take. Interesting. Let's move away from that because it doesn't become the biggest part of our conversation. But let's go back to the PIB.  The fact that the executive has proposed 10%... Not 10%. Well, according to reports. 10% rent for the fund, which is meant to explore oil. Cumulatively 30% of all. Yes, yes. However, in the passing of the bill, the lawmaker's resolved that there will be 30%. Oh yeah, okay. Especially for, proposed for the NNPC, all profits from the exploration. A lot of people have asked why we have to allocate that much to explore land in the Chad basin and all of those areas when we already haven't been able to deal with the problems of exploration in the Niger Delta. Now, it's not about exploration in the Niger Delta. It's about the fact that oil exploration, whether in the frontier basin, in the deep sea, onshore, should be a private sector activity. It shouldn't be the primary concern of government. Now, it is a profit-oriented venture. And the best government should do how to be to provide some basket of incentive. Listen, if you do exploration and you find oil, we're going to give you the following concession. In other clans, that's what's done. Not for government itself to fund exploration. But even that model of government funding exploration, why do we need to put cumulatively 30% of our earnings on frontier exploration? So what it means is that if we put that fund and at the end of the day, now what happens is that government bureaucracy will continue to feast on the fund and they will find no oil. Every year you give them 30%, 10% from the profit of AMPC and 20% from all the other collective that you put together in a basket. Every year they'll go out for exploration and they will never find oil. The reason is simple. They are comfortable having 30% of that fund. But if you make it a commercial venture, a private sector venture, it is in their interest to find oil as soon as possible because that's when they'll begin to make their money. Interestingly, the governor's... And so this will be penny wise and pound foolish. Which you seem to be in agreement with the people who are criticizing this. The governors of the southern states have also kicked against... Even though they're governors of southern states, they haven't been very realistic. Yeah, I know, but I want to... I'm going somewhere. We have experienced militancy in the Niger Delta over the years, which stemmed from the fact that oil was being taken from the Niger Delta, but they were not seeing the dividends of that oil exploration in terms of healthcare facilities, education, no schools. I mean, you would see buildings that were commissioned, but they are all just lying follow.  How do we stop this from happening? Because you're sitting here to say, we should have privatized it. We should not... It should not be government's business. But well, here we are. This is what the bill says. How do we deal with that? Plus, coupled with the fact that the government has its plaitful with the pockets of violence, ethnic agitations and insecurity that's going across the country. Now, I like to make this clear. It's still a bill. It's not an act yet. Well... What it means is that if we identify deficiencies or loopholes in the bill, it can still be addressed. It can be addressed in two ways. One, at the conference committee of chambers of the National Assembly, or by the presidency just before Ascent. It can send it back. Why not do the country any good by putting 30% of our funds for oil exploration and like any other typical government? What it means is that you put bureaucracy in place every day, every year, every budget cycle. You give them 30%, they keep and they'll break down. I say, oh, I'm chief executive now of some frontier exploration agency or some frontier department in the Federal Ministry of Environment or Frontier this thing in some government department. And of course they will feast on it. I've made that point very, very clear. But that if you say the private sector, the incentive will give you is that if you go, do your seismic work and find oil in commercial quantity, then we're gonna... And that was actually more than a nebulous shell and early, early firms that did exploration in in the United Data region, find oil. Oh, you're gonna have exclusive exploration rights for social number of years. We're gonna give you these acreages and all of that. So if we go with this model, the same challenges we face currently in the Niger data will be replicated in other regions of the country. And it will be an endless cycle. I don't think that's what we want for ourselves as a country or as a people. And when people begin to, it will let any day when we begin to find out that that model is not working. But at this age and time, we shouldn't reinvent the wheel. We should look at models that are working in other areas. How did they do it? Study it, adapt it to our environment and apply it.  You see these models that you're making reference to and you see how it's working. But then when you come home, it seems like we do not want to... Local politics. Well, who's this local politics benefiting because your job is to serve us and make decisions or pass bills that would help us to get better as a country instead of taking us back to the dark ages? I know that you're not a member of the House of Assembly, but you were, so National Assembly. What, why, why don't they... It's unfortunate that very many of us do not look at things from a pan-Nigerian perspective and a long-term perspective. What happens is that we come very often with ethnic or regional agenda. And when you say we... I will not look at the par-Nigerian agenda. Well, I was in the National Assembly and I know that a few of us looked at things from the prism of a national agenda, not from the prism of a regional agenda. But what I know clearly is that majority... Yes, it's a pan-Nigerian institution. Majority looks at issues from a regional agenda, but that's been short-sighted. On the long run, you need to look at things from the bigger picture. It's a challenge. Petranny is a challenge in this country. Let's talk about politics of Nigeria since we're already there. The issue of the electronic transmission of results, that's also been an issue that's been on the news. Now, people who have been advocating for this electronic transmission of results by INEC seem to have been very disappointed by the recent outcome where it's been removed totally from the Electoral Act bill, which is going to be accented too soon. What are your thoughts on this? Because what do you presume the Senate's... Why, what was happening in the mind of the Senate's members to actually take this out?  But we're in the 21st century where we do electronic transfers of monies and other things. Why should this be taken out in 2021 if we have been advocating for it for several years? I'd like to put it in perspective. What has happened is that the Senate committee inserted a clause, clause 50, sub-2, saying that that clause outlaws electronic transmission of results, not electronic voting. And I'll try to distinguish what's going on. And my initial take is that it's like putting the electoral system of the country on reverse gear. Instead of moving forward, we want to re-progress, we want to move backward and that's absolutely unfair. It simply will destroy everything we have achieved thus far in the electoral evolution process. Everything wrong with our system has to do with the electoral system. When we have bad leaders, it leads to the fact that education surfers, healthcare surfers, infrastructure surfers, the economy surfers, and it's already product of the electoral system. In the past few years, we thought we've made a lot of gain. And as recent as it do elections, I like tried using electronic transmission of results and it indeed was wonderful. That's why you had an opposition candidate, Governor Basiki, who got returned, who got elected for the second time as governor of a new state. Now, what? That committee, I'm not saying Senate. I didn't say the Senate. I said, what that committee is suggesting is that we should go back to mana coalition of results, then hand carry the results from the various units to the world, from the world to the local government for coalition from local government to state, from state to federal. It's absolutely unfair. It's uncharitable. It's unpatrotic. It's everything evil. It represents evil. It represents typical retrogression. Now, if you look at every other place, initially the thought is that we'll progress from electronic transmission of results to electronic voting. We're not at electronic voting right now. What we've done as a country is that currently we do electronic registration of voters, even when it is partial. And electronic accreditation. It was first tried in 2015. When I happened, I was promised to be a candidate in 2015. Now, we think that our thoughts is that the National Assembly will codify, put in proper legal framework the issue of accreditation and progress of course to the electronic transmission of results and in the near future we'll go into electronic voting. But we're not seeing that. We're rather seeing that instead of moving forward we are on a reverse gear. That's totally not acceptable. Now, with manual transmission of results, when you carry from unit to the world, there will be dispute. There will be contest about which result is original because of course another result will surface. And when it moves from there between the world and the FDA, of course there will be a lot of contest. And that's why very often almost all elections end up in court. So instead of the people's choice prevailing, it is about the decision of the various courts. That denies the people the right of free choice of electing their leaders. And when they deny the right of electing the leaders, the leaders are no longer accountable to the people. They know that it is not the people that put them there. They may be maneuvered their way to the court process. But yeah, just to tie to what you're saying. So these leaders are also found in the National Assembly and they could be in that committee. Oh yes, might be that. This is the reason why they continuously are dilly-dallying around this situation because it's in the benefit or in the best interest of the average politician. And what happens is that the electoral act provides the governance framework for elections in the country. And so if somebody has intents to cheat in the near future, it begins with the electoral act. And so there must be. But I know that the Senate will rise to the occasion and correct this defect for which Nigerians have risen up in one voice to speak against manual transmission of election results. Now mind you, there's also the House. The House provides another window of opportunity for Nigerians to correct that. The House is a bigger platform representing more Nigerians than the Senate. They represent equal number of Nigerians. Of course, you know the Senate, you have three past states. The House, you have more peasants in the House, younger elements, more vibrant elements in the House. And I believe that they will correct this. Like His Excellency, the right, the honorable speaker, Femi Bajabemila, had said, oh please, why Nigerians? Please, why not wait for the House version? Ultimately, when the House deals with her own version of the electoral act, then they move to a conference committee and harmonize positions. I'm very optimistic that at the end of the day, they'll be able to fix this. Because for us, as a people, for now, I don't know of an alternative to electronic transmission of results. In any case, the machines are designed in such a way that if you vote, the machines will transmit the results. So I don't know that the machines that will be or you vote using some electronic needs to vote, then when it comes to transmission, that means they're going to manufacture special machines for Nigeria. Well, that's an issue that we will continue to continue to train. So that's our own passion, is to strengthen the electoral process so that, strengthen it, that it guarantees credibility and integrity and the whole essence of democracy is that periodic elections should have, they should enjoy the confidence of Nigerians, should be credible. So Nigerians will continue to have faith in democracy. Well, that can't happen until that section of the bill is changed. Oh well, Nigerians come out, speak forcefully, saying, oh, what the Senate committee did represents the position of Nigerians. That's not our position, that's not our aspiration. Exactly, so while people have been campaigning that all Nigerians call the members of their representatives. Their representatives. Yes, of course, and impress upon them to make the right moves. But let's take a quick break. When we come back, we're still talking with the Cuckoo Adore, Peter Seid. He is the former director general of the Massa. And when we come back, we'll be talking about insecurity and the state of the nation. Stay with us.


what's everyone take down here welcome back to my retro series here on my channel today as you guys can see I'm gonna be playing Galaga so episode 2 today I do have a kind of a small strategy whenever it comes to Galaga that I always tried to do but I always fail at it and as for the series I'm going to always try to beat my high score so as you can see my high score is 46,580 I'm gonna try to beat that today it is going to be very tricky for me because I seem to get caught up in my talking to the video so far off to a really good start I almost got caught there I thought you can't beam me up okay that was actually my quickest stage one I think I've done now this is where my strategy kicks in because I'm going to try to do it here instead of me just telling you what my strategy is I'm going to try to show you here in a second as long as I don't get caught up that tends to be my strategy not sorry it's not strategy that's okay no my strategy didn't work my strategy whenever these things come down oh just like that get yourself caught I really wish I didn't lose a life in order to have this happen but get yourself caught and then whenever it comes down you're gonna have two ships and then you can go into the bonus stage or the challenging stage and dominate I missed one I missed another one there got them all got them all I missed one so I missed three in total I thought there's more okay so yeah the bonus stages are better with two ships I find that's always been my strategy when it comes to Galaga but now I have both ships in use I don't have any I got an extra ship now okay yeah I talked too early you guys got to watch it the rockets faster and faster and miss that last one there yeah almost have the stage clear but something tells me it's not going to go like I think I'm not sure comment down below but can you get three ships can you triple your ships up almost got me there I'm off to an okay start this is I think it's cuz I'm doing it for an episode I'm just really on it I said that and then look what happened are you kidding me you can't take me I'm the last one standing 29,000 that's not too bad with my on stage six I don't think I've been at stage six in a while last life though that's what scares me they're not shooting rockets this time so something tells me it's gonna be a lot more intense when they come down for me oh I was right 31,000 okay not bad still didn't beat my high score but 62% so not bad I did get top four okay you know if you're wondering who Jay is that's me my real name is Jason but I go by takedown on my channel I could have just done TD as it but I started playing this before doing it for a series so it is what it is we're gonna do it once more just to see if I can do it I believe in myself but the next episode episode 3 is going to be digging wow stutter dig dug the first one now I remember playing the second one for the DS because I have the Namco DS anniversary game something like that I had it on the PlayStation 2 as well but the DS version it was dig dug to that was on it so I remember the 3d aspect of dig dug to but not the first one so it's gonna be fun it's gonna be a throwback to the original if I can do my strategy right this time without losing a life I don't know I think I can do it I think I'm taking I'm clearing out way too many way too fast this guy has to pick me up pick me up oh they're not gonna pick me up oh he's gonna pick me up I thought that rocket was gonna get me so if it did that would have been done for me I would have been toast and I'm not gonna shoot it while it's up there cuz that's just a waste I think it gets you a lot more points from right if I'm if I remember correctly frig see I don't I didn't want to run into it oh okay one more shot there we go challenging stage usually I get it too early or I miss out on getting it which sucks got them all there I missed one and it was an easy one I say that but it's not more button smashing than anything you know that I only miss one that entire time I'm glad I did another go at it I'm glad I didn't just end the episode there got an extra life too so I'm I'm doing a lot better than I did last considering I just blasted them all to hell really quick the rockets almost get me a look away last second are you serious take down take down take down for what I don't know what it is today guys but you're watching this this is possible I'm gonna beat my high score and I'm pretty excited I just lost all my enthusiasm for this I spoke too soon why do we do that why do I always do that I'll get excited something is happening I'll get too excited and I'll freaking jinx it oh not today that's in the name yeah bite me no I was wanting to get beaned up there so bad that just I just passed what I what I got so I know I'm gonna be top four now because I'm at 32,000 this is where I died this is where I screwed up they don't start coming until they're all done so they don't start shooting they won't start doing anything they just kind of sit there I need to turn into turn into I need to get double-shipped please please give me double ships give me all you I forgot they like to turn around on me like fool round on me when I'm not looking whoa what are you we turn into scorpion is that the scorpion coming down below that's a scorpion I was really set on getting captured oh my god would you look at that I was just joking I didn't think I'd actually get captured I'm 11,000 well almost 11,000 from beating my score my highest score that I've gotten in this game is there another challenging stage right now is it going to challenging stage number is number seven a challenging stage I sure hope so yeah oh yeah they go back up about that hey hey come on yeah what I do only miss to maybe whoa hold up how much the bonus did I get 39 well we have officially done it I am so freaking happy right now 42,000 I'm going up I'm going up I'm hoping I just want to get 55,000 am I getting more points I'm not even looking up at my points accumulate because I know it's gonna take me somebody could go up and look at my points whenever I'm doing this no this is it I'm gonna have to watch that back but I want to see if I'm getting more points because I'm higher one life left stage 9 this is the highest I've gotten in Galaga because I haven't played it in a while I might have whenever I was playing it on the place that was really intense maybe when I was on the PlayStation 2 I've beaten it I highly doubt it so excited that was amazing that was amazing high score beat this is why I wanted to bring back the series because it is a lot of fun that is me Jay 57,000 so I beat my high score by 11,000 I am super happy I am hopefully going to beat my high score for the next episode on a dig dug it because I think it's very doable I think it's lower but just because I haven't played dig dug much so I am gonna leave this episode here I'm actually surprised that I beat my high score for Galaga but this game is a lot of fun so I am gonna be doing it for another another series I'm gonna be doing it for another episode for the series later on but I want to try to get one of each game out of the way first and then I'll see what you guys want me to play the most and I'll try to do more of those games for the series but I am gonna leave this video here hope you guys did enjoy I'll see you guys in the next episode please take care peace


Hello everyone and welcome back to another mid-journey tutorial and this one we're in mid-journey version four and version four finally has adjustable aspect ratios and adjustable image sizes. As you can see here I typed in forward slash settings and you can see here I am confirmed in version four and in it now look at this I've got all I've got a three two size here and and this one here is a four seven or seven four or seven pardon me two three size here these are all different aspect ratios and it is a piece of cake look at this little nugget all right fair enough okay how do you do it very simple you just do imagine like you normally do just type in forward slash imagine and then you go I don't know french bulldog pixar style and then very simple it goes dash dash ar space and then the aspect ratio so I'm going to go 16 9 because this is the one that I use the most and then I hit enter watch this it'll take a few seconds I'll come back when it's done but it's going to be 16 9 all right welcome back here it is you'll see here that this has the 16 to 9 aspect ratio look at this cute little studious french bulldog in this little monster guys if you're ever lost you can always go to the documentation on mid-journey itself go here's the link I'll put it in description below docs.midjourney.com and then look under aspect ratios parameters aspect ratios and it's all here so all the different ones you can use four five two three four seven one one etc all they're all listed that's how you do it guys thanks for watching