I'm very sorry to keep you for lunch, and I know that we just did all that raffle, so this talk won't be that long, so don't worry, lunch will be there when this is done, so cool. Hi, my name is Chris. You can find me online at Twitter, you can get me on speaker deck, and I'll be putting up all my slides on there after this, and then I occasionally post some code things to GitHub as well, so you can look for that on there. Just before we start, I wanted to plug another conference, which is a bit unusual at a conference, but this is also the other best premier regional conference there is in Elixir, so if you didn't come last year, basically MPEX is a one day single track conference in New York City, which is where I live. I'm one of the organisers. We're looking for people to come and speak. The CFP is open until March 12. Basically, it's just a really, really fun day. We host it in this really awesome jazz club in Soho, and we do a lot of really fun activities, and there's always a lot of good people and good vibes, so this will be our second year, and I'd love to see some of you down there. So tickets are on sale now. You can get everything at MPEX.co. Now that the plugs are over, and that's not a plug joke, honestly, I'm going to be talking about today umbrella apps in Elixir. So I actually gave this talk a few weeks ago at a meet-up, and someone came up to me after, and they were like, you know you really need to rename that talk because it's not really about using your umbrella. So I've kind of put a subtitle in here, which is the what, why and how to use umbrella apps. So I'm going to give you to start with just a really, really brief introduction to applications and umbrella applications in Elixir. And then we're going to move on to talking about some designy kind of things, and hopefully that will pique your interests a bit more than talking about applications. So in Elixir, some of you may know this, but an application is a component that implements some specific functionality, which can be started and stopped as a unit, and which can be reused in other systems. So basically applications in Elixir are pretty much like libraries in most other languages, but one of the other key parts here is that they can be started and stopped as a unit. So any of you who have done some Elixir programming, you're probably very familiar with your MIX file and your dependency declarations like this, where we have, where we can specify some dependencies like Ecto, or Phoenix, or even this other library which is called Spotify EX. And some of these libraries might, sorry, all of these things here are actually applications, and some of them may start up process trees, and some of them may just include some library code as well. So we have this kind of difference where we can start these applications as units like we might do with Ecto, or we can just include some code like we might do with Spotify EX. So the long and the short of it is that applications give us a defined way to configure and run our Elixir code. So if you've worked with one application, you can move on to another application, and it's very easy to kind of know where you are and know like actually how to write these things and actually how to configure and run them as well. And that's great for our systems because it gives us a defined way for our system to kind of bring these things up into life. And we've talked a lot over the last couple of days about OTP and all the wonderful concepts there. And applications that have actually come out of OTP as well. So again, just a very simple example. If you do any kind of mix new with the dash dash sup flag to start up a supervisor, you get something that looks like this, which is just showing that we have this defined way to say that the module MyApp is actually the entry point into our application and can start up all these process trees. So that's kind of what applications are. So an umbrella application and many of you may have heard of them or possibly started to use them in your applications. So an umbrella application is a single repository that inside of it is made up of one or more local applications. So this is really, really handy when we want to actually start composing our applications of sub applications and libraries that we don't want to host in a remote source. So we can always put our code on hex. That's always a possibility or we could always use git modules to do dependencies, but a really nice way to keep everything local and especially when you don't need to publish it externally is to use umbrella applications to do that. So I'm just going to walk you through what that looks like now. So we can run our mix new command and we can give it a dash dash umbrella flag. And what that will do is create a directory structure that looks like this. We have a single configuration point here. We have a mix file at the top level where we can specify application-wide dependencies. And then we have our apps folder, which is where you guessed it, all of our apps live. So when we want to create a sub application here, we CD into the apps folder. We can do mix new inside of there. And mix is smart enough to know the context that it's inside of an umbrella application and it's going to create you an application with everything that references up to the top level umbrella as well. And you can even do that for Phoenix as well. So as of yesterday, that command should be replaced by phx if you're using the 1.3 release. But anyway, I'll get onto that in a bit. So when we create those apps, we get a directory structure that looks like this. We have our apps inside of that directory. We have our web app and our sub app here. And what we can do is actually, if we have tests across all of those applications, we can run this mix test command from the top level and that's going to traverse into all of the child apps and run tests inside of there. And then we get an aggregated view of all of the test results. So it's really handy to develop these umbrella applications. So you don't have to sacrifice many of the tools that you're used to in order to start writing umbrella apps today. And similarly, if we want to start up the entirety of the umbrella application, we can do that from the top level as well. And that's going to start up the applications inside of it. So often I'll build Phoenix apps inside and possibly have a single entry point, like a proxy or something like that. And we can start that service so then we'll be able to access that on a port like we would a normal Phoenix application. And when we want to rely on these applications, when we want to say that one of our apps depends on another app in the umbrella, we can just use this really simple piece of terminology here. We just give it the name of the application. So in this case, we're inside of our web app and we're going to say that the web app depends on the sub app. And all we have to say is give it that in umbrella true and it will know how to wire those things up and run it as a unit. So you may all be thinking like, yeah, I know all of this and I get it, I've used umbrella apps. But really the big idea coming out of umbrella apps here is that we can make these more complex applications that are composed of small isolated applications. And that's kind of what I'm going to be talking to you about today. So now that we've got past the introduction to umbrella apps, we can start talking about designing them. So before we start, I'm just going to give you a bit of a warning that this is all my opinion and this is something that I've done on a project. So there are a million ways to do this. I hope this approach is useful for you and we can definitely discuss trade-offs at the end as well. So let's steal some ideas from domain-driven design. There's a ton of really, really great ideas out there in the community, especially coming around from the .NET community. There's a lot of similarities between some of the concepts that we have in Elixir and some of the other concepts that we're using in the .NET world. So especially if you look at F-sharp, we have similar operators in Elixir. I would even go so far as to say that Link, if any of you have used C-sharp, is fairly similar to Ecto in a lot of ways. And the idea of domain-driven design is very big in that community and some people here might be thinking like, ooh, I don't want to bring in all of that OO baggage and that kind of thing into my applications, but hopefully I can show you today about how that can work for you in a smaller kind of way. So what we're going to be talking about today is really separating your applications into these specific bounded contexts. So some of you may be familiar with this term, some of you may not be. I'm going to literally rip a quote out of the Eric Evans domain-driven design book, which is the Bible for domain-driven design. So there are conceptual boundary where a domain model is applicable. It provides ubiquitous language that is spoken by the team and expressed in a carefully designed software model. So a lot of you may be thinking, huh, what does that mean? How do I apply that? And honestly, a lot of Eric's book is quite dense and reads a lot like this. So if you're really fond of reading something like that, go ahead. But hopefully I can explain this in a simpler way and give it a bit of my take here. So the way I think about bounded contexts is just think about breaking your app into smaller pieces that have clear responsibilities and boundaries around them. So I'm going to hopefully show you some examples and that will become a bit clearer, but keep thinking about these boundaries around our applications. So applying this to umbrella applications, we want each application in our umbrella to focus on a single context. So that means that, again, it has those boundaries around it and it focuses on one part of our bigger problem space that we're tackling with our applications. So let's see an example. So the canonical example in domain-driven design is often an e-commerce app because I'm not that inventive. I'm also going to use that model. So let's say that we have an e-commerce application that processes sales, ships orders, manages customer support requests and manages a product catalogue. So lots of very common functionality for an e-commerce app. So if we're going to approach this into a design where we put everything into bounded contexts and into more of an umbrella application approach where we split everything out, we could start to think of it looking a bit like this. So we might have two applications at the front here which could be our API and one could be our back office or our admin application and they might be Phoenix applications here. And the boundary around the edge here, this represents our repository for our projects. So this, in essence, is the umbrella app. And inside of here are the individual applications that are the individual contexts that we're going to be talking about. So we might have one for sales, for shipping, for customer support and for that product catalogue as well. So the really nice thing here is that every application inside of that, inside of our larger context that we're dealing with can be tested in isolation. We can develop these applications in isolation. We can deploy them independently and we can actually hide the complexity from those other applications through these defined public interfaces. So the idea of modularity in software is often to hide those complex decisions from anything else from the outside world and that encourages an easier way to change and develop your software. So the deployment independently and composing these umbrella applications and deploying them separately I'll touch on at the end. Also Paul did a great job of talking about distillery and hopefully I can elaborate on that a bit more as well. So, yeah, you can kind of think of these applications as microservices. Microservices is obviously the buzzword and Paul's diagram of the emojis perfectly summed it up in my mind. And there's a fantastic blog post from Jose about this where he talks about using Erlang and Elixir to kind of build up these applications and thinking of them as microservices without much of the trade-offs that we have if we're going to be deploying smaller services as well. So what about integrating with Ecto in these applications? So I'm sure everyone here is familiar with Ecto, our persistence library. So our applications aren't that great unless we're actually storing some state to somewhere and actually doing something with it. So just a refresher. Again, our application design looks a bit like this. So remembering that everything in here is an application inside of our umbrella. So one way that we've approached this before is that we've actually introduced a single what we call a DB app that is our entry point into our database and is the point in which we keep all of our migrations as well. So this gives us a really nice place to kind of put the stuff that we didn't want to scatter around all of those other apps and it gives us a single point in which we can start up our Ecto repo and all of the pools of workers that that has as well and also do our configuration of that Ecto repo in one place as well instead of scattering that around the apps. So that might look like this in our diagram where DB again is another app inside of our umbrella and we pretty much we treat that like a regular Ecto repo. So we have an entry point into our repository into our database through using the Ecto repo here and then inside of our DB app we just depend on Ecto and we depend on Postgrex in this example. So what that might look like in terms of your application design is just focusing on the sales and the shipping app here but we have these applications inside of our umbrella that communicate with our database through this DB app. So every time that we want to make an update to the database we're going to be referencing the repo through that DB application and in this example what we've done is we have customer order and line items in both of these apps that are Ecto schemers in both places and you might be thinking oh that's a bit weird but I could hopefully touch on that in a sec so the idea here is that we basically have each application defining its own schemers which are essentially these value objects in DDD terms that we can then pass around but the idea is that we're focusing on the specific functionality for each one of the apps so in this example again we've pulled out the sales and the shipping app and we're looking at a customer schema in both of those applications now but we might have a completely different set of fields that the sales schema maps to in the database than we have with the shipping customer so an example might be that our shipping customer might not need an email address whereas our sales customer might need an email address so because we have this separation between these schemers and our actual database in Ecto we can define these in two places but they're still using the same source under the hood and you might be thinking but we're duplicating our schemers and you're going to be right in that sense but remember that dryers isn't necessarily about duplication of logic dryers about avoiding duplication of logic and not duplication of code so in our example before you might see some duplicate code but the logic is very likely different between those two places and if it's not what we can do is move that into a somewhere shared and kind of share it between those two places instead so when we want to call out to this database we can do so through entities or aggregates or services personally I pretty much call everything a service in this sense remember that could be that could be a set of processes or whatever you want to do in this case we're just encapsulating that inside of these umbrella applications and then we're providing that as a public interface for all our other applications that are relying on this behaviour so an example of that might be in our sales app we have this order manager that can complete an order again it's going to build up this change set and it's going to call out to the DB repo here and remember that this is in our sales app so then basically when we want to depend on that database app we can do that in our domain context as well so in this example again looking at our sales application and we just have to say that this is on the database app and we always have to remember to start that application as well because unless we're using elixir 1.4 in which case we don't have to do that but if we're using an older version we do so this isn't the only option available there's actually some really interesting discussions in the C-sharp community about doing this domain driven design approach and actually having an entry point to your database in each, like they call them solutions in our sensor in our applications so one other way that we could approach this is putting a repo in each one of those apps and then having a configuration in each or we might use a system like CQRS or there's many different ways to do this but we've had great success we're just splitting it out and having a single database app as an entry point here so what about Phoenix in this context I kind of showed you at the beginning how we might have that API and that back office app and those can be kind of our Phoenix applications into this wider amount of business context so remember that and you've probably heard this and everyone I feel like has beaten this point like a drum right now but Phoenix is not your application Phoenix is this web layer into this bigger world of your business logic and your domain logic and because we have this powerful umbrella app idea we can kind of do this very, very elegantly and very easily so let's see an example of that so let's say we're dealing with our API and we're dealing with our checkout controller in our API we might be calling out to our sales manager, sorry our sales order manager here which is actually in that sales context that we were looking at earlier and that will handle all of our business logic for us and everything to do with processing sales and our Phoenix app really concerned itself with all of the things web like processing parameters and dealing with sessions and reading headers and all of that kind of all of the stuff that you know Phoenix is good at and it's and all of those things fit inside of that web concern world so one really cool thing is that Phoenix 1.3 has introduced generators to do this inside of your app hopefully everyone saw the announcement yesterday and Chris McCord's talk at Lone Star Elixir so Phoenix 1.3 takes a slightly different approach in that they are using the idea of context but they're placing them inside of the lib folder instead of inside of separate applications personally I prefer moving these things out into their own applications because we might have a bunch of different processes started there and I also really like this boundary that moving them into their own applications creates in that you actually have this physical kind of separation with your team that they might be working on one app and someone else might be working on another app as well so if we do all of this like what does it give us what's the point of doing this so we end up with this dependency where everything kind of points in one direction which is really nice so what we're really talking about here is a sense of looser coupling between our code so we end up with a flow that might look like this where everything only points and knows about something on the inside of it the sales app doesn't have to know anything about the web or anything about the world outside of it and again the API doesn't really have to know that much except for calling those applications as well so there's a fantastic article by Teff which is called Write Code that is easy to delete not easy to extend and really like loosely coupled code isn't going to just give you like everything from day one but it really really helps in a sense that it gives your team and you the ability to write more maintainable code that hopefully is easier to change over the long term so we're kind of taking that big ball of mud idea, splitting it out and using the power of Elixir to do that and for those who've come from the rails world we used to dabble with these ideas with like cells and those hexagonal rails architecture but all of those concepts were kind of bolt-ons into rails whereas with Elixir at least we get this concept of applications where we can do this on a lower level as well so what you end up with if you follow this kind of approach is again this clear separation of concerns your Phoenix app becomes just this really really thin layer into all of your business context and one really nice thing and Uncle Bob has this article about the screaming architecture where your application screams its intent for those who look at it and actually this is a really nice win in the sense that someone new coming on your team can look at the code and immediately know the different context in which you deal with all in this single monolithic repository and then again you get this really nice simple unit testable business logic that's totally separate from your UI and if you wanted to you could make that separate from your database as well personally I'm not a huge fan of that approach but you know your mileage may vary in that sense and of course this is just one way of doing things not necessarily the right way Elixir is an amazing tool for being able to easily refactor code as well it feels very very easy to pull out applications and move them around and to be honest most of the apps I started with recently have been single monolithic Phoenix apps where there's a lot inside of the lib folder and then we'd basically pull things out into applications when we needed to as well and honestly that's very trivial to do in Elixir as well so don't feel like you have to start with this from day one I just wanted to touch on a few gotchas that I've experienced and tips for working with umbrella applications as well the first one is definitely if you're looking at deploying umbrella applications definitely have a look at distillery it is an incredible tool for being able to do the composition of those umbrella applications into whatever kind of means that you want so we can define basically separate releases where we can say that we have a release for our API and we might have a release for our back office and we can deploy those to totally separate boxes and it will wire up all the dependencies as well for us so if our API depends on only a few bits of our business logic or other applications that we have distillery is smart enough that it's going to build that release with only those things inside of it and then we can deploy that to a separate node or deploy it somewhere else of course taking into account Paul's great talk earlier about trade-offs of doing this in a distributed manner as well there's a ton more on the distillery page here for umbrella projects as well another tip that I found really useful is using xdoc for all of these bounded contexts as well so just actually writing documentation and then generating that documentation for all of these applications and having that as something that you can share with your team as well and it's been hugely useful for us and again writing specs as well even if you don't use Dialyzer just writing specs so you can show what return values are there I just find that hugely useful as well again you don't have to do this on day one refactoring is so simple and honestly I've done this I think about three times now I should probably just start with an umbrella app or you can also you can cut this a lot of different ways you might think okay I'll just have my web app and then I can have a single bounded context with everything in it if your business logic isn't that great that you need all of these separate contexts as well so it's another way to do things one big gotcha is that circular app dependencies are not allowed inside of your umbrella applications this kind of bit me at first when I got really really excited about doing umbrella apps and started splitting everything out into a separate application it got way too granular and then basically I think that's a definite smell and that you have all of these things depending on each other and it's far far better to think about a context in a bigger sense another gotcha is that you can't run gen migration from the top level honestly like you just have to cd into your apps and then into if you have a single app for your database you just cd into that app and you generate all your migrations from there it's not too much of a big deal and this one has bitten me a couple of times where you might have lots of dependencies inside of your individual umbrella applications they all have the same kind of transient dependencies or different transient dependencies and it gets quite difficult to work with at times and often you have to use override flags as well to kind of get around the situation it's again it's one of those interesting points that because it bundles up all of the dependencies into the top level basically everything has to match inside of your umbrella apps so we can talk about that more after if you have any questions there so thanks and we'll be going to lunch now but I'm really really happy to take some questions before we do or if everyone just wants to run out feel free to do that as well so thank you


ly out of everything right now. And even if we've got a stockpile of river road floods. I mean, getting access to those other quarries in this distance the way they are, you know, be advantageous from that perspective to have power in place where we could get it. So if you can use that as any kind of leverage to kind of pile on from another avenue, the importance of that resource might open some doors for us. Okay. Okay. I think he's probably got enough input because we gave him 15 minutes and he's only got 10 minutes to speak. I'm going to watch it online as a note. You choose. Be excited. That's going to be tomorrow. Tomorrow? Wednesday. I hope we have the full agenda. Yeah, we're not quite at midnight yet, so. 1.30 p.m. on Wednesday. 1.30? Okay. Let's see. Senate operations. Okay. Let's talk about next meeting. I think the look is pretty full up. Well, maybe not certificate a five-way mileage, but. It'll be Monday, 22nd. Again, point of order. Danny, you were available to chair if I just zoom in as a. Innocent member. Yes. Okay. Coming in under an alias. Yeah. So. We've got Joe is ready as far as we know to make his presentation. I believe he's already sent a draft out to the committee. Yeah, the library will need some time. Mm hmm. I met with them today. How'd it go? They had a meeting continued after I left. But they're. They're struggling with their own. The library trust. Okay. Whether they whether they agree with a bunch of proposal or not. It's a good conversation to have between the boards. I think. And they're going to be there, right? Yeah, they're there. 20 seconds should be plenty of time for that. Okay. And then revitalizing Waterbury and senior center. They're looking for flat budgets. I highlighted them because I'm not sure that we need to. Yeah, if they don't want, I mean, it doesn't seem like it's a contested issue. Do you think dump? It's certainly not contested. So I don't think we need to have them here. If you, if you wanted them, they're certainly not to come. I don't feel like we need to talk with them if they're just asking essentially for flat budgets or. I've said this to Tom before, but I guess it's like we use the budget de facto to do kind of our annual updates. So I do. I like having been an employee for revitalizing Waterbury. Like they should come and present to us and we should hear about what they're doing. I don't feel it needs to be on January 22nd to defend the budget proposal. Or I would say Karen should come and she'd be mad at me, but I digress. But, and Ditto with like the senior center, you know how to ARPA funding for the kitchen. So to be clear, I don't have qualms with that outline in the budget. They need to be there the 22nd. Maybe I would propose for an agenda item on the 29. We have a conversation about regular check-ins with groups like them. I mean, again, they tend to set the six month update, but I'm okay with foregoing it in the budget context, but not in an overall annual checking context. I agree. Knowing how much we've got going on this month, it might be better suited another time. So it would help me with a more specific director. We're going to move them to the first agenda in February. Well, making sure Roger agrees before we. Yeah, I'm okay. In fact, I would prefer honestly to talk with them about their annual plans. If it's not specifically budget related. And we can spend a little bit more time perhaps talking about the economic development proposal because they essentially, you know, revitalizing Waterbury is our economic development committee. And then the senior center. Unless people feel that they are particular things that we want to know from them. I would say we should schedule a note. Go ahead, Mike. We should probably just keep them on the agenda, but really not have. I don't think they need to be here. I think it's better to be there, and just go over the numbers very, very quickly in cursory. And just say we all agree on what's there. And so just say as someone who used to work for an organization, if I'm on an agenda, I sure as heck am going to be at that meeting. Just person. That's my first. So that's fine. But if the intent is for them to not come personally, I would. I mean, we can specify that. We have to discuss the budget. Right. You have to discuss the budget. So they have to be on the agenda. I don't think you can just say, you know, flat budget don't include it. Even though it is, we all know that we're looking at both having flat budgets, but I think we at least have to acknowledge that and agree to that going forward with the whole budget. Okay. So in response to Karen's request, I would say we're going to keep it on the agenda. They're welcome to be here. Right. Speak to any issues that may come up, but we will reserve an opportunity to speak with them at greater length at another time. Yeah. Deal. Okay. I didn't write this, but I thought I think you took it off of the template that you provided, Tom. What are we talking about with special articles? Because I want to be prepared. Do you want to see the letters of request? Are there any changes? No. G-M-T-A-R-I, who I just finally got in touch with. Last you wanted to talk about it, but I have to ask three times for an invoice. But anyway, no, there's the tall flat funding. So I can bring the letters of request. I think, yeah, we just reviewed the last statement so last year, but if it's all flat, last year the conversation focused around the senior center and the increase, but also how much of it was in the budget versus has a special article on it. And maybe the decision, maybe that's the conversation this year again, is now that the increase is not an increase to just move it into the budget. Okay. That's your call entirely. On the 20th, aren't it? And then just to give where we're at in terms of the tax levy, the public works budget had that $30,000 for sidewalks. And the more I talked to Bill Woodruff and thought about it, we have no qualms about deleting that in part because it's a lot of work for his crew because to stretch the $30,000, they pull the old sidewalks. And they've had other priorities that are in the roads. And in part because the more linear a fee you can bid out, the better price you get. So it's nice to chip away at it and show some progress each year. But maybe it's something we save up for a few years and have it later on. But if that were to, so we have no, you could certainly leave that in and repurpose it. But if that were to come out and the library were to agree on the trust fund usage, your tax rate would go up depending on a half, which is less than 3%. Without the $100,000 bidon? Correct. Without Tom presented a rate that was based on paying down $100,000 of debt from the general fund. Without that, you could be less than 3%. Keep that $100,000 dry and keep it dry and save it for a few terms. I guess my only instruct that was not on the agenda tonight and we're approving a $10 and I don't forget to agree which is just to say I have no problem with it but I find this RW Senior Center. Will they certainly be on the agenda? No, I don't think they need to be on the agenda nor do I think it's RW Senior Center.  And then on the sidewalks I guess I would just say I felt like, Roger, you said that as a passing comment at the end of the last meeting or maybe I interpreted the conversation wrong but just saying we're facing, you know, a lot of pressure with school budgets which is real and whatnot and what choices we should make. I guess I would just say like if there's a desire to change the budget by $30,000 and to be clear, I defer to you when Woody more than anything. So if Woody thinks it's a good idea, great. You know, he knows the crew and knows the people. I guess I wouldn't, I didn't feel like I was going into that conversation with we need to cut something in sidewalks is what we should cut. I felt like it was kind of an afterthought comment so if staff thinks it's the right thing to do I'm not going to advocate to put it against staff recommendation but it wasn't like leaping off the pages like wow that super extravagant maintenance of sidewalks in the village. It was something we had in the budget in 2023 and didn't get to do it. We wanted it in 2024 and then after some conversation Bill Woodruff and Celia you know, one of their, you know one of their complaints about the Main Street project of which sidewalks has been part of it is that, you know, they lose two members of their crew for quite a bit of time pulling sidewalks and they'd like to just have some more time for roads and especially to get some gravel road projects done. And don't they already have to do part well? They have to do some of that already. So there will be sidewalks done but it's already made for them. So yeah, I'd be happy to have the $30,000 disappear and keep our price, our tax increase as many as possible because, again, our taxpayers are going to be facing all sticker shock regardless of anything we do here but the more that we can reduce that the better for my standpoint. Okay. Will we have a copy of the, on the agenda draft warning will we have a copy prior to? Yeah. I don't know if this is narrative and you mentioned you drafted us like we're before it just strikes me that we spoke to Arthur really specifically and for the reference of Brian earlier tonight. You know, there is $500,000 of course we've accounted for it for our agreement. I accounted for it but I personally and the way Alyssa does accounting and budgeting feel that we have $500,000 that was originally ARPA and so I'm just thinking about either addressing that how we address that. I guess my sense is it's going to be narratively in the select board report but again just particularly in the context of our earlier discussion tonight like there was so much focus on it last year and we provided a plan that accounted for so at a minimum I think it's important that we highlight how we accounted for it for general government expenses but I think if we have intentions of using it for special projects in the future which I guess is my personal whether it's flood mitigation or something else again it's not part of like the warning but I think we just need to make sure we address that or have a response to that for a town meeting. Okay. And as I texted all the members of the board I am drafting a letter to go into the annual report and we glad to mention that if I think that we would say ARPA monies have been incorporated into the town so it's all part of town revenue now it doesn't have any special requirements in terms of being appropriated but that we're personally I'd be interested in directing at least a portion of that towards flood mitigation since it's one of the things that qualifies as a local match. So is this conversation going on the next agenda? I was going to just put it into the letter that I was going to submit to you since you told me I had a deadline of Friday and then also invite others to feed me and I can send you out the sort of like the outline of what I've got right now and then you can tell me if I'm missing something. That makes sense. It could be a status update too because there has been positive like this bridge work was done and this gravel will be happening this letter and this is how the recipe was accounted for in future plans. The certificate of pilot mileage I put that on today it doesn't need 15 minutes I think it just requires your signatures. It's an annual, it's a formulaic part we have to complete. Woody fills it out and I think I just have to bring it here and decide it is my recollection I'll change the times. I'll be in by the end of next week I'll be here for the meeting if you need my signature through next week. I'll see if I can get I gave Bill Woodruff the deadline of Monday the 22nd so I'll see if I can get it done. She's giving me a deadline but the budget's not done so I can't write the report. It's not fun. I'm going in storage relationship I know the real deadline. Just one last thing Danny has invited Skip to present EFUD on the 29th. Yeah I have that on me. One other final thing of the big importance I responded affirmatively and I've already got a couple people from Town Hall but I was invited to be part of game show night for Winterfest. It's like a town team. I think the library might do its own. So give me a second here to give you the date. It's February 2nd Friday night starting at 6th. There we go. Did we have to enter by the 12th? Is this what Natalie just told me to do? Yes. You should get yourselves registered. There's going to be... Your email to me just said Friday at 6. I thought it was this Friday. No it was the part you wrote at the top. Oh did I? I don't know. Well just maybe clarify because when I read it I'd believe it because I would be available. Friday is the second. Starting at 6.30 I think getting there by 6 would be helpful. And it's at the Legion. They have a look at what their bars are like. The bar is very open and reasonably priced. And there also will be a photo bench on the 10th. Kevin and I sent that to staff right? I should have sent that during public. I should also say speaking of venues at the Legion that you all should come to. February 10th there's a... What are we calling it? What? What event? Is it a volunteer appreciation? Yeah volunteer appreciation but I think the select board is all duly invited and should try to attend. What time is it now? I believe it's... I don't think I got that yet. There wasn't a nice other time for someone to staff. I think there's going to be some broader events. Yeah they're making like a town Facebook event and what not. I'm just really going to meet again to the 22nd. Yeah I think there was a motion to adjourn in the second. Yeah Alyssa made it in the second. Alyssa? Okay. You did but I don't know what to tell her. All in favor say aye.


Hi everyone, Joe for jaspyscasebreaks.com coming at you with 2020 Panini Prism Baseball, number two. Really, it's mystery, it's Jaspys mystery box break number two. Let's not fool you. We're just basically doing this break and at the end we're gonna re-randomize your names and the name on top is gonna win one of these Jaspys mystery boxes right here. We have boxes one and three remaining. So on the dice roll at the very end we'll go one, two, three, four, five, six. But of course we gotta do the break itself first. Big thanks to all of these lovely people here for getting into the action. There are the teams right there. Let's roll it, let's randomize it. Six and a one, seven times. One, two, three, four, five, six, and seven. After seven times we got Jeff down to Adam. Make me some surprises in this mixer, or in the mixer, in this prism baseball box too. Seven times for the teams. And seven in final time. After seven we got the St. Louis Redbirds down to the Milwaukee Brew Crew. All right, there's the first half of the list right here. Anthony, Mariners, right, what else? Royals, Sean, Yankees, Mark, Kurt, White Sox, Blue Jays, Adam, Aaron, Dodger, so on and so forth. All right, let's sort that by column B and let's print and rip. Show you the final printout one more time. All right, good luck everybody. Josh Hader, Silver, Glavor Tourist Red. They're not numbered, but they will ship. Hey, Mendex been playing some decent ball right there. Gavin Lux finally got called up. We got Chris Paddock, Blue Mojo to 175, Payson Slazardo, was pretty good. Chris Paddock for the Padres, Mark, Dodgers, Aaron with the Dodgers. Top of the class, Scott, Kingery, Blue, are also not numbered. And behind the Christian Yelich wave is Ryan O'Hearn Royals. That'll be for Sean Maddock, pro penmanship. And the Yelich is 36 out of 60. And there is a Silver Rookie, Tony Gonslin for the Dodgers. Aaron, Josh Bell, Matt Scherzer, Stargaze, now I was like, where's the number? 30 out of 35, Davey Gruyon. And the next auto is gonna be Aristides Aquino. Didn't we get one in the last box? I hope in a fresh case of this too. Aristides Aquino, Rookie Auto, going to Kevin Mendoza and the Reds. Not really doing much this season, but definitely a lot of future upside in that guy considering what he did last season. There's Joe Palumbo, 24 out of 99, Red Wave autograph, Jack Flaherty. Marcelo Zuna, Silver, Eduardo Escobar. Joe Palumbo for the Rangers. That's gonna go to Kurt, Kurt Brose with that. And the next autograph, Carlo Santana, is gonna reveal a Jaime Barrera. Barria that is, pro penmanship autograph. There's your third auto, going to Tyler Rutledge and the Halos. And the Carlos Santana is to 149. That's for Cleveland, Andy. Shoei Otani, numbers game. I thought that was number two, it's not. Numbers game, not number. Another parallel right here. That's gotta be number, there you go. Instant impact, Kristen Yellich to 125. For the Brew Crew, Adam Cuperman, Tommy Pham, blue. And Eloy Jimenez at the back right there. Now, here's the whole reason we're doing this. We're gonna randomize, re-randomize everybody's names right there. There they are. Name on top, Mystery Box. What's behind door number one? All right, let's grab everybody's names right here. That's a different list. Let's clear that list out. Get some new dice. All right, there's everybody right there. Thanks everybody, good luck. Name on top after seven, lucky seven. Cross those fingers, get the lucky rabbit's foot. The four-leaf clover. One, two, three, four, five, six, and seventh and final time. After seven times, big thanks from two down to 30. Thank you everyone for getting in. And congrats to Mark. Wow, there was no doubt about it. His name was up there twice. Mark Stemmerman, congrats to you.  So now, one, two, three for box number one. Four, five, six for box number three. All right, so we're gonna chew that. So remember, one, two, three for the top box and four, five, six for the bottom box right there. Arthur's guessing five. Bradley, I'll get back to you on that after I finish this video. And it's gonna be, wow, Arthur, you nailed it. Five, one, two, three, four, five, six. It's gonna be box three. And this is for the last Mystery Box break. So Mark, congrats, thanks again. Here's what we got in box three. Look at all this fun stuff. We got a jersey in there. We got a mini helmet. A TriStar mini helmet from 2020. Looks like a Tua jersey in there. We've got 2020 Daenerys baseball. Nice. We got 2019, 2020 Chronicles basketball. There you go, Mark, with some green parallels, hanger box exclusives. There's the Tua, autographed jersey. Nice. Beckett card and sticker. There you go, and the Alabama Crimson colors there. Look at this. A stack of cards. First of all, you also get $500 in break credit. That's pretty nice. Now let's see what we got here. All right, we've got Jake Arietta, rookie Jake Arietta from 2010 Topps Update, PSA 10. We've got a Tyler Hero, PSA 9. That's pretty nice. We're gonna see him in action in the playoffs. There you go, Mark. Next is Pete Rose, PSA 10. Two color relic, got the otter, that's a nice auto. One out of 10. One of the nicer Pete Rose autos I've seen. There's a lot out there, but what else do we have? Ooh, some Giannis from 2019. Panini Prism, red, white, and blue. Giannis, PSA 9. We've got Jordon Alvarez, Gemmin 10. We've got Vlad Guerrero Jr. from Flawless. Five out of 10. Kind of thick that card, that's pretty nice. That is awesome. From 2019, Flawless Baseball, we've got, there's more, TJ Warren, 12 out of 99. Remember how well he did during the restart, or during the playoffs and the restart games? TJ Warren, he's got a lot of upside there. He's looking good. And we've got Zion from Playbook, from Chronicles, Playbook Design. Got another graded card. Hey, Fernando. Nice, PSA 10 from 1981 Fleer. That's nice too. What else is Mark getting? And wow, a Sandy Kopex cut autograph from Leaf. Six out of 11. Wow. That is nice. And Mark Stammerman, you also get, don't forget the $500 of break credit. There you go. We're gonna ship these to you sealed. You can rip them if you want to. You can sell them if you want to. It's all yours. And enjoy that break credit, that $500 of break credit on jasphyscasebreaks.com. I'm Joe for jasphyscasebreaks.com. I'll see you next time. Bye. Woo.


What's going on guys welcome back to the channel critical overload here, so in this video here We're gonna mostly be talking about Maxine but before I dive in the maxine and the updates regarding the lawsuit Alec or the alleged allegations in this lawsuit from a crew member against Mia goth and Ty West and 824 and also confirming the release date which is coming out this summer as me as a Michelle monigan was Speculating on as I can point it out She likely was just recalling something she heard in the past before I go into that I'm gonna touch on foundestination six really quick. So Craig Perry Put out this post on it looks like Facebook today He said after a long hard slog through the pandemic and the strikes day one is finally in the can 2025 will mark the 25th anniversary of the release of the first installment in the franchise to honor the occasion with another worldwide theatrical release and I max no less is a rare and wonderful thing I'm wholly grateful for the opportunity and humbly appreciate the subliminally talented team or the subliminally talented team That has worked so hard to bring this to life. See you next year PS I know I know pet cemetery bloodlines But this is the title we've had for three years and we're keeping it for now So it gives me hope that the title is gonna change not that I really care one way or another I'm gonna be seated. I know a lot of you are gonna be seated We haven't had a final destination movie in over a decade and To know that this film is gonna be an I max has me excited as well It's nice to know that they did start shooting yesterday because that's what the reports were for several months I pointed that out back in January that the filming dates were a hundred percent locked in and They seem to have not had any hiccups with making the start date of yesterday. So they started filming on March 4th We don't know who the cast is outside of Tony Todd, but I'm certain we will find that out probably this week Or as production gets deeper So shifting gears over into Maxine So we're gonna talk about the release date. But before I get into that, we're gonna talk about this lawsuit. So radar online claims to have obtained court documents related to the lawsuit and it details briefly me of goss response to this Ty West's response and I guess some other people involved with the a 24 Their response to it. So let's start from the top This all started back in January and according to this headline from radar online Mia got this fighting a $500,000 battery lawsuit Brought by Maxine extra over alleged kick on set actors Mia golf denied the allegations She intentionally kicked the film extra on the set of her upcoming horror film and then belittled him in the bathroom or according to court documents obtained by radar online Goth asked a Los Angeles superior court judge to dismiss the claims brought by a man named James Hunter As radar online previously reported earlier this year hunter sued golf director ty west in a 24 In the lawsuit hunter claimed he worked as a background extra on the upcoming film maxine The third film in the series featuring x and pearl hunter claimed goth kicked him in the head during a scene The man claimed it went down during a late night shoot Hunter said he was playing dead for hours while wearing a robe and covered in fake blood from head to toe The extra said the conditions were rough and he had to endure ants and mosquitoes Per the lawsuit goth the lead of the film was instructed to run past the extra step over him and stare and then continue to run Hunter said goth was not being careful and kept nearly stepping on him during the takes Now nearly as in quotations The extra said goth was warned by the staff to not step on hunter He said he said she then intentionally kicked him in the head with her boot Hunter said the kick caused him serious pain pain and stiffness in his neck He said he later learned from his doctor that he suffered a concussion hunter associated or accused goth Of targeting him after the incident He said she came up to him in the bathroom and taunted mocked and belittled him the drama didn't stop there Hunter claimed the fake blood the crew put on him stuck to his body and caused pain when taken off Hunter said he wasn't asked to return to the set after the incident with goth He demanded five hundred thousand dollars in damages for alleged battery and rawful termination In her newly filed response goth argued if any of the allegations in the complaint occurred Which defendant denies then each and every cause of action alleged against defendant Therein is barred because plaintiff consented to and approved all the acts and or emissions about which plaintiff now complains Further goth said any damages allegedly suffered by hunter were not proximitally caused by any acts or emissions of her goth asked that all claims against her be dismissed and her attorney fees be covered the director and a 24 Both denied all allegations of wrongdoing in their recent file responses a judge has yet to rule So I guess that's the latest update on the lawsuit Alligate on the allegations from this lawsuit that spawned back in january That goth tie west and a 24 both denied all allegations of wrongdoing and their recently filed responses With this lawsuit. I feel like i'm back in jeepers creepers for territory talking about lawsuits related to an upcoming horror film And with maxine of all things that was the last thing I had expected me talking about on this channel We're now going to shift gears into addressing this release date So online ceramics had a leak that came out on reddit a few weeks ago A couple of days ago at this point where it was a poster for maxine Had the mark of the beast it had the pentagram that I've been hyping up to you guys about how it's correlated to the movie And it's very important to the killer and what they're doing and how they refer to it as the mark of the beast or something like that um And then it had the release date on it of july 5th 2024 One of you reached out to someone with online ceramics in a discord server sent me screenshots of the convo Where this alleged employee Told you guys that it was fake and I proposed in the video Why wouldn't they say that if it was a legitimate leak?  And I expected them to lie because I said there's a good chance that this is just real and they're lying to protect it And that's sure enough what happened because deadline fangoria bloody disgusting other outlets have been reporting today Maxine will 100 be dropping on july 5th of 2024 Just so just let that be a lesson if you're going to reach out to an employee And expect them to tell you if a leak is real or not I'm not saying that all of them are going to lie to you But they're probably gonna lie because it wasn't supposed to be out there to begin with it was a leak We weren't supposed to know about it. So that's why I proposed it in my last video But it's nice to know that we can expect to see ty west's maxine in theaters this july I've already requested time off for it because that whole week is going to be dedicated to that trilogy me watching maxine a few times probably making a lot of videos and Just reviewing it. I'll have a spoiler for reviews spoiler field review I'm probably not going to have two reviews from any movies this year maxine is going to be one Where I definitely want to do a spoiler free and a spoiler field review possibly also just Dissect what they could do next since we know that an idea apparently is in ty west's head But let me know what you guys think about this down in the comments section below If you haven't already course make sure you subscribe turn on post notification at name is video in the description I'll have links on my social media accounts I am on facebook twitter and instagram You can message me there to let me know if there's any movies news or reviews Let me to cover in the future and with all that in mind guys. I will see you in the next video Thank you


Alright, next step is to put off the guys. We're going to be talking about what's going to happen to you next week. Thank you. Hello, I'm Spiroffs. I'm a computing engineer at the CERN Cloud team. And I'm the project team on the OpenSpec Magnum project. It's a computer infrastructure management project for OpenSpec. And I'm going to talk about OSHA computers. OSHA computers. First, let me say that the Elux containers are just normal processes controlled by Elux kernel by Elux default groups. And the name spaces, so it's got a different name, so this is a totally new mindset. But specifically about OSHA containers, the most popular containers are containers mounted by Docker. And in 2015, Docker and other vendors created OSHA specification. So, OSHA specification has three parts. It's the runtime specification that defines how runtime should understand the configuration which describes the container and how it should run it, how it needs to create mount and mount name spaces and names of all these, and how to implement the lifecycle operations of the container. Then there is the image spec which defines how the image should propose that the image should have a manifest that describes the layers with the image index. And also there is the set of layers described in the image index. And of course it has the configuration configuration. And finally, it's the file system bundle. So, when the container runtime or any other tool pulls an image that is OSHA compliant, it extracts it in the file system bundle that has a file system where the container will start and the configuration which points to the file system and describes all the capabilities and the needs that I mentioned. But why we need the OSHA containers? So, as I said, containers are just a few new processes. You need someone to start the container. And most likely, if you have more than 100 containers, you need a supervisor of these containers. If you are in a large deployment, most of them will be orchestrated containers. So, you have a system like OpenSharm, or Kubernetes, or NOMAD, or NISUS, DCS, something else. But if you are in a single post, then you don't want to orchestrate. You need something to manage the containers. In most of the distribution, the processes are managed by system D. So, an idea would be to manage other containers with system D, but that means if they call system D, and then system D is called the DockerDemon, then the DockerDemon talks to the container, the great container. This has some directions, because when we talk to the DockerDemon, the Docker client, we do an API call. So, that might be a secret. And you need to be using the direction in system D. So, it's better to manage containers that are directly with the DockerDemon, or the system D. Another use case is Kubernetes. Kubernetes was initially started by talking to Docker, but that means you get that grant again that you do the API calls to the DockerDemon. So, in Kubernetes, with a component that creates the actual containers with this couplet, they create the CRI specification. And there are a couple of CRI specification implementations, like one is the CRI container D and the CRIO. Container D is a project that is behind Docker now, and it's developed by DockerDemon and other contributors. And CRIO is another specification, that is another implementation of the CRI specification, that is implemented in the CRI container and other contributors, and it was based in the previous design of Docker. So, a use case for that is... I'm going to use the use case that I will describe later. It's like a CNA problem. So, what is in the process that needs to start before Docker, and sometimes like manage Docker or configure Docker. So, if you have an orchestrated environment based in Docker, you might not be able to run all the containers with the containers, so you might want both of them. So, in this talk, I will try to motivate why I got into this. So, I would like to clarify that I'm coming from the user's perspective to the developer of the CRI specification, or any of these two, the user and the consumer of them. So, all this construction comes from the CRI container service. So, at CERN, we have just one minute to describe what CERN is. I hope that you already know. It's the European Council of Nuclear Research, and that has a fundamental analysis in probably particle physics. So, at CERN, we have a big accelerator that accelerates the protons and create collisions, and these collisions create events and lots of data. So, our biggest use case is batch processing. To process all this data. And in 2018 or since 2015, containers are a very good use case to define workloads that you run in a computing grid or in a plethora of environments. So, here is the big motivation. Other use cases are energy analysis, which are most prominently defined by two notebooks that you can build a container that essentially is a notebook and you can do analysis and then share the container images so that other cases elsewhere can do the same analysis and ensure that it will run in the same environment and it will have exactly the same results. The other thing is that all IED companies and IED environments have is transaction management, continuous investment employment. As we are a big open-stack shop, we also run open-stack containers. So, the container service is based on a project called Magnum, since I'm the project team with them. So, this is a very simple workflow, so in the first command we just create a cluster and we say in this case that I want a token form cluster with 100 nodes and you wait some time in our cases like this or maybe less or more depending on the environment. You wait for the cluster to be complete and then you just get the credentials to talk directly to the ticket to the container on the master nodes and just talk straight to the containers. And in this case, as you can see, after two commands you don't have to do list, you can start to talk to the cluster and the container so no open-stack anymore. And this is how a node looks, even if it's Swarm or Kubernetes in this environment that Magnum creates. So, in the Apricots we have a Swarm cluster that has a token demo. In the legacy Swarm, before Swarm mode, you have a Swarm agent that's running a container on every node. We also have the ETCD that should run on our console that should run on the master nodes. In our case, we have some templates which we run in containers and then we have an open-stack agent that takes configuration from open-stack and applies the nodes. Similarly, and even more complicated in the Kubernetes interface, we have more Kubernetes components. We have Lana, we have ETCD, we have a Seri runtime, and then we have the agent and the plugins that we want. So, in the case of, for example, for the legacy Swarm, if you wanted to run ETCD in a container, you should, and you had it on the docker, it's a chickening problem because you need to start ETCD before starting the docker. So, if you want to start ETCD in the container, there is a deadlock there. So, what you want to do is to start in an ETCD in a different way, like as a Managed Container by ETCD, and then deploy the Swarm cluster. It's exactly the same review stage in Kubernetes. So, if you want to run, for example, Kublet in a container, and if you want to run Kublet in a container managed by docker and Kublet, you need to, you cannot know which one to start first. So, in our case, we can start Kublet in an ETCD Managed Container and start docker again in a system container and then stop that container and start the pod in Kubernetes. And, of course, the other interface is the OpenStack agent which defines and configures all of this. So, since this agent contributes everything, it must start personally before all. So, this was the initial motivation. And, for these problems, we ended up living in a CI container. So, how to build them? I was about to describe the build up, but since I found it more complicated, I think it's easier to build manually. So, a system container is a container that runs in atomic hosts. Project atomic hosts as Fedora and send us atomic hosts. Send us atomic hosts, and if you are in the other private world, they have a record of the state, but in our case, we use Fedora or send us. This comes with the atomic utility and some set of other tools that allows you to create containers to be managed by system D. And, to build those containers, you must have you must build them and to be also managed by system D. So, we have a docker file and then we use docker to build the image. And then we have a system D template, which would be added to the docker image and then extracted by the utility and deployed on the node. So, the system D knows how to manage that container with RunC. We have a list of TMP files, which are files that may be that container and they may be they don't. And then my association which are default files for the application of the trans in the container and the application which is the standard from the OCI specification. We have a lot of these files in the list that I've written before. So, this is how we look to build the container. There is a fellow world example, of course, in the atomic system containers repo. So, you can just build the fellow world atomic, the fellow world container as a normal one that you would do with the prep and then you push the rest. Then you can just do atomic install which is also only an atomic host but then there's also a data based system and if you do atomic install minus my system, which means that if you run a group unless you specify otherwise in the configuration and then you can give it a name and that name will create a system-based based on that template. And then you can do just system-based start from work and start that system to use it. So, in our case it was a precondition. We could run whatever lines and double-stack specific rules that we wanted to define host. So, treating the host as a middle-level infrastructure that we don't take host and install a bunch of things or we don't just rebuild host all the time we just take that distribution and then we explain that we want. But, if you start looking into a shared containers and if you ask anyone that works on them, the most difficult part is to create the configuration file. So, in one of the documentation of RunC, the OSA specification they said, this is how to create a template and then you populate it. There was nothing after that, there was no documentation. So, you should start starting about name spaces with the the main page of the kernel but the permitting that you need as an advice is the main space because if you run a process without the main space it just starts in the high system of the host. So, the root file system of the container just goes away and you don't use it. Probably, you should add IDC but it's important then you should add the user to have a user name spaces and create what's seen by user and then you might also need BID to have if you have more than one processes in your container you might want to have a different main space and using system containers which are containers that are very close to the host you usually don't want to add a network name space it's better not to add it and share the same network space with the host. Then, the capabilities if you go to the website that I missed to add in here of the Linux kernel main pages then the number of capabilities is endless. So, one advice that you have that it's a pretty cool hack is if you start a container with Docker and you won't find, okay this container that runs in Docker, what capabilities it's using this is a pretty cool hack how to find it, you get the ID of Docker and then you go to the proc file system and there's some grep and dock you can find exactly which capabilities you need. So, this is the world world first day iterations that I was doing for my any containers and then of course you have mounts. So, in mounts you should be able to understand when do you want or what do you want to share with your host or share with your other containers. So, in this case in this case this mount is a byte mount the container will have access and these are private so that means only my container will have access to that directory and changes that I'm doing there are not provided to the host that will be provided doesn't have to be shared and that is also because we have Haslave which means only the host changes and then they are provided to the container. I think, let's go through my talk I finished a few minutes early so I put in some links here and that you I advise you if you are in the containers to go have a look at the runtime and the image spec they are not very long and they are very well defined and don't follow all the links that they have because they go to ares which are extremely long and you can check the other system containers repo that I've contributed and the atomic team contributes and you can pay your containers there of course it is my project and if you have any questions you can leave a free note and I'll be bigger. Questions? Let's say for example that I am an e-max user and I have a lot of plugins and a lot of sectors Can I make a container with my e-max my plugins, my settings that whenever whichever machine I'm running I tell for example Docker to run this container it's going to run with the user of that machine and not the super user of some special container in the container If it is defined in the compensation Docker will follow the situation because Docker is a non-straighted client in the runtime and these containers that I described apart from some special files for the system beginners are just normal containers that Docker runs than other containers How does Docker know which user was the user of that as far as the container in that usually the container is formed is formed on the root but then they run as a different user but they are not rootless containers How does he know a whole different container the user the user can look at the container and just know that's where the container is The user that created the container in the first place will be a good build and then inside the container the user will be specified in the right hand of the container


Hey everybody, welcome back to magic orthodoxy. My name is David and this is a deck review Hey today, we're gonna look at the Knicks playing cards from a collectible playing cards. All right, so what is Knicks? Knicks spelled NYX. Okay, NYX This was a Kickstarter release that collectible playing cards did and it was successfully funded and this is the deck So yeah, Knicks is one of the goddesses of Greek mythology. She is a shadowy figure Knicks stood at or near very near the beginning of creation. She mothered all of these smaller deities She was the mother of sleep.  She has exceptional power She's exceptional beauty and legend has it that even Zeus the father of all gods Is afraid of her. The front of the tuck case is a bicycle branded tuck has a very haunting Spade pip picture there in the center with a face and holding some sort of glowing orb It says Knicks playing cards at the bottom One side says the United States playing card company. The other side says air cushion finish The bottom has an ad copy about collectible playing cards and the back design is of course the back design of the cards It has a custom tuck seal which is pretty indicative of CPC And then it just has a non-descript top that is pretty much it for the tuck case Let's take a look at these cards. These cards come printed from the United States playing card company And they come on a B casino stock They do have a modern cut and air cushion emboss and if you'd like to learn more about stock cut or finish You can click the link below in the description. Of course, this is a bicycle branded deck It's gonna feel handle work like any other bicycle branded deck that you're familiar with especially a deck of casino grade stock Bushes that are thicker stock Similar on par to the B stock has moderate edges moderate sides. It's a Q1 quality good deck from bicycle The back design has a thin border and it has a little broken edge on the left and the right very beautiful and then a lot of just inward art there with these exploding wings in the center these two mirrored diamonds These two mirrored triangles that are facing each other and they're floating on kind of like these mandala flowers I don't know. You know what the back design on the cards and the tuck case. I Wasn't a fan. I like the art. I love the art I didn't love the color blue that they picked especially Doing this juxtaposition of blue and black I feel like they didn't look at their proofs very well and then the ink came out really dark These cards look great in sunlight and really bright light But in like a regular fluorescent lit room or just like regular, you know looking at it Looking at it in your house The design work is really hard to see and so I was kind of disappointed with the art on these with this deck You're gonna get two extra cards You're gonna get a collectible playing cards and card and you're gonna get a double backer, which is great for magic With this deck, you're gonna get two original jokers. They depict ninks herself One in a red dress and one in a blue and she is holding some sort of a crescent moon above her hand The pips and inti cards are all completely redesigned The pips themselves are much larger than maybe a standard deck And I think the red is a little bit more of an off-color. They all have a very rigid very abstract design I think it pierces through the white backdrop and makes the design really pop the court cards in this deck are also completely modernized You still have courts, right? You still have royalty, but they've been dressed up They've been all revamped to be in like this old metallic dark armor They're also featured in blood red and night blue and I think they look like they're ready for battle All right So that is my review of the nicks playing cards from collectible playing cards as always we ask that you like this video Just so other people can find it faster We also recommend that you subscribe to this channel just so that you can see up to date on the latest in cards and card magic If you want to follow me on social media, you can I'm at facebook.com slash magic orthodoxy twitter.com slash magic orthodoxy Instagram.com slash magic underscore orthodoxy and if you ever need more content You can always find it at magicorthodoxy.com. Thanks. Bye


In this presentation we will calculate federal income tax FIT using the percentage method. We currently have our payroll register here where we're focusing in on Pam who's the bigger earner here and therefore the one that's going to need to be calculated with the percentage method rather than just using the tables. She's going to be married for allowances. She's got a salary pay which is going to be this 3653 since there's a weekly pay and that of course will be the total earnings. Our focus then here is on the FIT calculation. So we're looking for the FIT calculation. Therefore we're going to need to know what the FIT wages are which could differ from this total wages. This is what she's getting paid. We'll typically be reduced by those types of things that could be reduced in say our 1040 adjusted gross income things like a cafeteria plan or a retirement plan like a 401k. So if we say here that the cafeteria and retirement plan are these numbers then we can say that her total earnings are going to be or the FIT earnings are going to be this 3653 so we're going to say 3653.85 minus and then we have the cafeteria and retirement plan of 280 minus 185 and that'll give us the 318885. So that's 318885 that we're going to basically be using here. We're focusing in on this on this number on Pam's wages because that's the one we're going to be focusing on for the FIT. So here we are at the circular E. The circular E can be found on IRS.gov the IRS website IRS.gov the circular E to get the most current tables. We need to go down to the tables to calculate the payroll withholdings. These are not going to be the the normal just tables that we can look up. They're going to be the percentage calculations typically used if the wages are too high. For example if we went and found this number in the tables we'd say oh the tables aren't big enough to find that number and therefore typically that's when we would have to go to this method the percentage method in essence calculating what the wages are going to be. Now this is an important method to do and it's useful to do because we get a better understanding of what the progressive tax system is. What are these tiers doing? How complex is it to calculate these taxes and why is it that format? So to do this first we got to look at the table on the circular E to see what the allowance is. So we need to know what pay period we're using. We're currently in weekly and then we're going to say okay that's $779.80 is how much money per allowance that we get. So $79.80 once we have that we can then take our federal income tax pay. This is how much we started with from our table. That's how much we earned after the retirement plan and the cafeteria. Then we're going to calculate the allowances which is going to be the $79.80 that we just looked at times the number of allowances which for her is $4 which is going to give us $79.80 times $4 or $319.20. Then we're going to take the FIT wages minus the $319.20 for the allowances to give us this $2,869.65. This then is the number we're going to use for our percentage tables. So now we're back to the circular E and we're still in the percentage areas. This isn't like the tables where we would just look up the number. Notice what we're going to have our our calculations will have to do. We've got to find the right bracket that this is in and then we'll have to calculate the top tier and add it to the tier below. So let's see if we can kind of break this down and why this happens. This is closer to us actually having to calculate what the tax is on a progressive system. And remember it doesn't mean if we're say in this tax bracket that all of our money is taxed at 22%. It means that some of it's taxed at 10%. Some of it's taxed at 12%. Some of it's taxed at 22%. So it's just it's a it's the top portion that's taxed at 22%. So we need to go through this whole thing and say well this much is taxed at 10% and this much is taxed zero this much is taxed at 12%. And to do that we can shortcut it a little bit by saying for example we are in this bracket and that's going to be between 1,711 and 3,395 that's the number we're using because this falls in between there. And so we can basically say that this number up to the bottom level of 1,711 has already been calculated. We can calculate that on the table. A table can give us that because that's a set point in time it knows exactly where that is. It can't give us the number of tax at the highest bracket because it's somewhere between here. So we'll have to figure out what that is because it's we don't the table obviously doesn't know exactly what that how much is going to be taxed at 22% but it knows exactly how much is taxed at 10% and how much is taxed at 12%. So we can take that floor number and the table can just give us this 171,36 which is in essence the amount taxed at either 0, 10 or 12%. So we have we have that and then we just need to figure out how much is going to be taxed at the 22%. To do that we're going to take our number 2,869 minus the floor number typically the bottom number which they give us over here excess over 1,711 the difference then will be taxed at the 22% the highest tax bracket and then we add to it the 171,36 which is the table already calculating the tax on the 1,711 the floor which is the 10% and 12% brackets that we don't need to recalculate because the table can give us those. So it looks basically like this we've got the federal income tax here and then this this is our tax our taxable wages and then we've got the lower limit on the table this number this number and that will give us the amount to be taxed at the highest bracket so we subtract these out that's the amount the highest rate which is 22% so the amount taxed at the highest rate times 22 gives us $254.90 then we add to it the 171 given to us by the table which is in essence the tax on the lower portion and if we add those together we get 426 which is going to be our work withholding amount. So this is basically the full breakout that we'll take from the table it's nice to have a format like this you can kind of think through it if you do it a few times if you have some of these calculations and you set the table up then you can go through and just fill out the format of the calculation and fill out what's the appropriate amount what's the appropriate table that you're looking at just make sure you're picking up the correct table ours was for weekly if you're bi-weekly semi-weekly or semi-monthly or monthly another table and make sure we're picking up the single versus the married side of it so then we can basically use all that in order to fill out our number here in our FIT federal income tax withholdings.


Good afternoon, for those who are new, I'm Dr. Theron Sherman, and in today's briefing we will be discussing SCP-7096. There isn't any objectionable material in this document, so let's begin. Item Number SCP-7096 Object Class Neutralized Special Containment Procedures All known SCP-7096 instances appear to have self-neutralized, all civilian witnesses of previously active SCP-7096 instances are to be properly amnesticized, and all casualties caused by said instances attributed to IRA-affiliated snipers. Description SCP-7096 refers to a series of road sign silhouettes capable of autonomous movement, restricted to the space occupied by the signs they inhabited. Footnote, the previous sentence fragment has been struck through. See additional documentation for more details. See within several Irish roads from 1990 to 1994. The signs were accompanied by the words Sniper at Work. These silhouettes were not capable of speech, and didn't demonstrate signs of sapience or higher intelligence. They appeared to wear paramilitary combatant gear, carrying a rifle, and would become hostile at the sight of people. When a subject got within a close enough range of an SCP-7096 instance, the anomaly would shoot with its rifle, and the bullet would exit the sign, being fully capable of causing damage as any other bullet of its kind. As most SCP-7096 instances were located on rarely used roads, and the entities presented remarkably bad aim, only three casualties were caused by SCP-7096. Outside of this activity, SCP-7096 instances were mostly dormant. Addendum On the 6th of April 1994, SCP-7096 instances adopted a new position while in their dormant state, where they could be seen holding a cup and sitting in a chair. Additionally, SCP-7096 stopped showing any hostile attitudes towards humans for two days. On the 31st of August 1994, SCP-7096 instances stopped showing hostile attitudes permanently. Additionally, many of them abandoned their home signs, and could now be seen inside several other dispersed road signs, mainly ones announcing construction works. They seemed to be wearing a tie and holding a paper, and appeared to be establishing a conversation with other road sign figures, who now also demonstrated the capability to move it will. Whether this effect was caused by SCP-7096 interaction, or if it's a phenomenon present in other road signs other than SCP-7096, is currently unknown.  Additionally, it was reported that many construction signs now featured two figures, further research is ongoing. Thank you for listening.  Please become a patron or visit our merch store at the link in our bio to support our work. Secure. Contain. Protect.


Good morning everybody today is October 19th Friday 2018 and I have to be at work in about 30 minutes or so and I just got back to my computer I might be trading this here give me a second to 7850s that expire in three days let's go and get to all righty I think I bought two here I don't know where I actually got executed I bought two 27850 calls that expire in three days there we go and I am gonna get out all righty I made a profit I don't know how much here started with $500 this morning I got 521 positions options this is the weirdest thing guys this is the first time I've actually traded using tasty works and I can't figure it out activity okay so I go to my activity cool so it looks like I am bought at $1.40 and sold out at $1.51 so that's 11 cents I was looking for a 14 cent move so that wasn't quite 10% but as you can see here I bought two see I'm only trading with $500 guys I literally made $21.46 like here filled I can't tell here if I got filled at $1.39 or got it filled at $1.40 this is the strangest thing but anyways I made money on today's trade pretty cool that was quick easy literally I was in that trade for three minutes three and a half minutes it was a good quick trade guys awesome good deal sorry about this morning again I'm trading off of a tasty works for the very first time I'm only trading with $500 and literally try to figure this out on tasty works so bear with me here first trade using tasty works I made it I made a winning trade I made 21 bucks 21 46 to be exact hey guys this is Giovanni from spy options trading as you saw in the video I had no clue what I was doing that was my first time actually using tasty works in actually placing a trade making a trade and selling a position so I did watch a couple of videos on how to execute your your your actual order but I never actually saw how to actually close or sell your position so as you saw I had no clue what I was doing and so that goes without saying whenever you guys start or get a new broker do some research guys don't be like me don't just wing it especially when it whenever you have your own money on the line and now I kind of know exactly how to actually execute my orders by order sell order and also as you saw I mentioned that I actually bought at 140 and placed a limit order at $1.40 and I actually got executed at $1.39 I sold at $1.51 thus giving me a 12 cent profit it's actually pretty good I mean it's about 8% it's a little under 9% but we'll just call it an even 8% so I'm actually really happy about that trade without exactly knowing exactly what I was doing I did make $21 off of you know under $500 so thank you so much for watching hit that like button hit that subscribe button and hit that bell notification so you get notified the moment I upload a video guys thank you so much for watching I'm literally rushing to get this video out before I go to my day job I have to be at my day job in about 30 minutes so I have to get this on the computer edited and load uploaded for you guys to watch thank you so much for watching everybody