model we've heard from Hans about Novartis's intra-country price discrimination. I'm going to turn over the mic to Prashant Yadab who is one of the most distinguished scholars in this space, has spent a lot of time thinking about these issues and would love to hear your reactions. Thank you Quentin and thank you for having me here at this workshop. I think when we look at products which serve populations in developing countries, I think it becomes important to segment into two types and some would argue perhaps three. But I think having that distinction is important because if we are talking about pragmatic strategies unless we look at that segmentation, our pragmatism, the strategies gets lost. So the segmentation I want you to start with is products which have a market in both high income, sizable market in middle income, and some market in low income, and products which have a vast majority of the market that only exists in low income countries. Examples would be malaria drugs. So the kinds of strategies we can put in place will differ depending upon which we are looking at and some will have an overlap but I think unless we separate the two we won't get a clearer picture. So let's first think about those products for which there is only a market or the burden of disease is largely in low income countries. Malaria would be one example. Some middle but largely low income countries. And I think there the question of sustainability is to be asked in a very different way and I think if we say sustainability means a firm does everything then I think we are looking at the right wrong model. Primarily because even the cost of manufacturing. So even if you do not recoup any research and development cost even if you do not recoup anything else just the sheer cost of manufacturing is something that cannot be met by the current paying population or in some cases even the government which may pull. So there sustainability doesn't mean a firm doing it alone. Sustainability means ensuring that our institutions such as the Global Fund, Gavi, PEPFAR, PMI and the interface they have with the firm is an area where some low hanging fruit remains where we can improve things, improve access in a dramatic way without having to do something very large scale change. So we often critique large global institutions just because being a global institution comes with its set of bureaucracy comes with its set of constraints that public capital or philanthropic capital often leads to. But I think there are opportunities to change the way firms and the Global Fund or PEPFAR or PMI or other institutions like that work and that can help serve this segment of the market which is primarily low income countries. There are some opportunities of using intra-country differential pricing in that market like Hans was mentioning but I think even intra-country differential pricing alone cannot perhaps solve all of that issue. Then I think if we look at those products which have a dual market which means those who have a significant middle income or even a higher income country market there I think the value of inter-country differential pricing and intra-country differential pricing and some combination of the two becomes one of our most important tools. The idea is very simple. We believe we can recoup our ND costs at the same time improve access but for some reason the simple theoretical idea does not translate into something which we can see being used on a wide scale in practice and as an academic or someone who works at the think tank I have had the opportunity of working with several companies who have been experimenting trying to do either intra-country or some combination of inter- and intra-country differential pricing and as a result have learned what their challenges are and I think often times in forums like this we tend to think about what can we do at the inter-firm level which means what can we do in the way a global institution works but I think often in this case the challenges may even be intra-firm intra-firm incentives and I'll get into the details of what exists within a firm that often is challenging. So if we look at inter-country differential pricing I think a large part of it depends upon if you decrease price points in certain middle income countries or low income countries the expectation is from a firm standpoint volumes will increase but that doesn't happen because the cost care of care and the bottlenecks that exist in the cost care of care are very many whether it's diagnosis, lack of treatment care provision options and so on. So then it becomes a question can a firm work with partners to resolve each of the bottlenecks in the cost care of care and whose job is it, to what extent is it a firm's job to what extent is it the job of the government of the country and to what extent is it the job of some global institutions and that's something which we've experimented with we've not come up with one way of doing it but I think that's an area where we've learned quite a lot more in the last decade than what we used to know in the early 2000s when many of these newer institutions were being created and new programs like the malaria program at Novartis were being created so I think we've come a long way in that then I think if you look at intra-country differential pricing and this is something I've explored since 2007 and 2008 I went and asked in some of you perhaps in this room the question as a company do you engage in intra-country differential pricing and a resounding answer I got from most companies I talked to was either no or very little and it sort of baffled me that the Treaty of Westphalia which was defining the concept of a nation state in 1856 perhaps was not the only way to segment to do pricing I mean we didn't have to necessarily say the pricing segment will be a nation state and for a nation state this is the price we could choose pricing for market segments as we thought appropriate so then the question was why can't we do it why can't we say this is the wealthy people in Kenya and these are the less wealthy people in Kenya and can we have separate price points and the reasons for well there'll be product diversion it'll flow across the channels and whatever price we give to the low income will start that product will start flowing and so yes that's the reason I got more and more interested in this issue because my training is in supply chain management and looking at distribution channels and we try to figure out what can be done in the distribution channel and how can we split some of the risks that fall entirely on the firm if it does intra-country differential pricing so imagine and I'm going to use Novartis as an example just because I've been a friend of Hans for a while now so I think the key thing is if all of the risk of a product that is meant to be sold to the more affordable segment moving into the high income falls on the firm and it is expected of the firm to make investments to reduce that diversion then I think the equation doesn't work out well from a sustainability standpoint if we say that the package that is going to the low income market is subsidized by the US president's malaria initiative or the global fund now that package coming into a wealthy pharmacy in Nairobi suddenly becomes a risk which is also for the large financier and that sharing means both parties now have to exert effort to make sure that diversion doesn't happen and often times a company has very little control in the country to prevent diversion but a government or a global institution may have better ability to control that so that's an area I think we can experiment with and can learn some from what the Novartis work has done the second part we often forget and this is a very operational thing is that the risk that falls on a company in such markets is larger than what it is in bigger markets and the reasons are very many but there are two that stand out one is risk about demand uncertainty because the pair is more decoupled the pair is always decoupled in a pharmaceutical health product market but in this case the pair is far more decoupled from the company and from the end consumer because we are paying through a global mechanism it becomes hard for a company to know what the demand will be to do planning and every time you have poor demand certainty that leads to increased prices because someone has to pay the cost of the millions of doses that have to be destroyed or expired and occasionally one time the company may say we'll write it off but eventually if this is a repeat occurrence this is a cost that a public pair or a government will have to pay so that's the demand uncertainty part the second is a credit risk element when we look at small country governments purchasing often times for a company taking on the credit risk of whether they'll pay or at least whether they'll pay on time and then once it's beyond 180 days or 360 days do you call it a written off account or do you still consider that as account receivables and how do you manage that so that's another area where we can do something because we have new forms of capital today I think new kinds of philanthropic capital have become available which do not come with the kinds of constraints that public capital used to have and we can very effectively use this new philanthropic capital to do risk underwriting which can then lead to a company being able to serve smaller markets much better then I think if you look at inter-country differential pricing one element that doesn't always work out is the current distributor for a company their incentive structures are here is your target or your quota for the country and if you achieve it you remain a distributor you achieve your bonus that's how they incentivize the sales force the challenge is most distributors especially in countries where the company does not have an affiliate office are people who've been the distributors for more than a decade and they have become complacent I'm being very candid here acknowledging that this is being live streamed most of them have become complacent because they serve the capital city and the 25 or 50 tertiary care establishments that exist in the capital city and they meet their quota at that price point by serving just those tertiary care facilities so if you not tell them let's drop the price point to one third and now for you to meet the same quota and get the same bonus nothing more you will have to go to 300 more secondary care facilities or district hospitals if I have been in business for 20 years I started it my son is now running it I would say no this is not going to work and the commercial team comes back and says no this is not going to work so as a result we haven't changed intra-from incentives on the distribution and commercial side for making tiered pricing work and that's why the volumes remain small so we say well we did tiered pricing but the volume never increased but some of it is cascade of care constraints but some of it is just the wrong incentives and then we come back and say because it is not increasing volumes that means competition is a better way to improve access than tiered pricing and then this debate becomes more interesting from an analytical standpoint because we can't answer the question and Suri is here and she can tell us more because she's looked at this when do we say that volume expansion through competition is a better lever for improving access versus tiered pricing and the biggest concern to your pricing is the volumes that happen through the lower steers remain small so that's one way of thinking about it the reason this is important is new products for all types of diseases including the ones that are targeted for low income countries all the ones which have dual markets are going to be much more complex to manufacture so we welcome the program that Gilead has started with voluntary licensing and I think it has the potential of doing lots of interesting things but at the same time some future products will be so complex to manufacture that we won't be able to say there are 15 voluntary licensees in India or China who can start manufacturing because even manufacturing capabilities are going to be very technically intensive and also the cost of manufacturing will have much more economies of scale so these are some things which are emerging I think the last thing I'm going to say is at the interface between global institutions and firms we can change the risk profile we can create new types of partnership arrangements and I think many of our global institutions Global Fund, GAVI, PEPFAR have already started doing that and I think we need to look at that and highlight that more thank you thank you so much Prashant that's a ton of great stuff to chew on there so I'm going to call in Chen when I was in government I spent a little time working on reforming the patent system most of what's interesting that I know about the patent system I learned from Terry Fisher but when I was sort of thinking about the patent system and the America Invence Act I started researching who are the people who are writing interesting things about the patent system and I came across the scholarship


The hippocampus plays an important role in spatial navigation as it helps us form mental maps of our environment and plan out routes to reach our desired destinations. In this study, researchers examined the brain activity of participants while they were performing a goal directed navigation task. They found that when planning for a route, the hippocampus was more likely to activate when two routes shared a common context and a goal. Additionally, when participants reached a decision point, the hippocampus showed increased activity which reflected the retrieval of relevant information from the previous context. This suggests that the hippocampus may be involved in integrating context and goal information into the formation of navigational plans. This article was authored by Jordan Kriviledekar, Alex Clark, Siong Min-Ae Park, and others.


This is stock number 11512Z. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used Dodge and Dodge Challenger and sports car headquarters. Today we are checking out this super clean 2015 Dodge Challenger RT Scat Pack. This vehicle has the 6.4 liter V8 Hemi motor, which pumps out 485 horsepower. This car has been fully-safetyed and inspected by our service shop. Has a fresh oil and filter change for brand new tires and is 100% ready to go. Red line pro coat or tri coat, I should say, is the color. We shoot all of our videos in 1080p, 60 frames per second. So if you have HD capabilities on your computer tablet or smartphone device, turn them on right now because it is definitely your best way to check out the quality and condition of the car before seeing it in person. And if you'd like to check out all the photos on this car in the upper right-hand part of your screen, there's a link to our website. Click that and check us out there. This one comes with the 20-inch painted alloy rims and it has brand new unor oiled Tiger Paw 245-45 ZR20 tires. You can still see the little wear knobs on them. We put those on in our safety inspection. The Brembo brakes with the slotted rotors. Front fender is in excellent condition. I didn't see any dents or dings on that. This one comes with the HID headlamps, the LED running lights and the projector lamp fog lamps. Front bumper and lower valance are in really nice shape. Didn't see any major dents, dings or cracks on that. And the hood is in excellent condition as well. Passenger side front fender. No dents or dings on there. Do you like the little Rumblebee logo there? Or Scat Pack logo? Passenger side rim. No scuffs or scrapes on that. Looks really good. And as you go down this side of the car, take note of how clean the body is, how reflective and mirror-like that paint is. We take these HD videos so if you are far away or even if you're close by, you just cannot make the trip down, but you're still interested in purchasing the car. You can see the car, hear the car, and have confidence in the vehicle that you're looking at before you even get here so that when you do get here, there's absolutely no surprises. And that's why we offer the Summit Auto Fast Pass option in the upper right-hand part of your screen, a link right to our website where you can apply for financing, get pre-approved, see a payment quote, even appraise a trade, all from the comfort of your own home. So when you get here, all you have to do is drive the car, love it, you'll be all set to go. Those back tires are brand new as well. And this back rim is in really nice condition too. As we come around to the back of the vehicle, your bumper is in great shape. You get the chrome-tipped dual-rear exhaust, the backup parking sensors, the LED tail lamps, and the deck lid spoiler and strife are in excellent condition. The back trunk area is very nice and clean. And this one comes with the tire inflator kit, and the battery is located back here as well. Those seats do fold down for extra storage, and you can see that the trunk jam is nice and clear, nice and clean. And that the shocks are doing a nice job holding that trunk up. Shuts nice and solidly. And as you go down the driver's side, just as clean as that passenger's side, you can see any dents or dings on the rear quarter. And for full disclosure, this back rim is in nice condition as well. You even get the SRT valve stem covers on there. Driver's side door looks really good. Comes with the heated mirrors with blind spot monitoring. Has the enter and go system.  Get the rumble be stitched into the backrest. There's no rips or tears on the seats. Very nice condition. The back seats are in excellent shape as well. You do get the latch child safety system back there. And floor mats. Factory floor mats in the front.  As we have inside the vehicle, we'll turn the ignition on so you can see the miles in the radio. You can see this one has 29,284 miles on it. Instrument cluster is very nice and clean. You do get a digital speedometer, compass, and outside temperature display. And instrument cluster is really nice. Nicely set up and good looking. Cruise controls on the right. Bluetooth and information center controls on the left. Audio controls on the back of the steering wheel. This one comes with the 8.4 3C radio, which gives you the factory navigation system. AM, FM, and Sirius XM radio capabilities. This is also where your backup camera shows up.  And then you can do all your climate controls here as well. Down here is your push button start. You get the super track pack button, which basically takes you to your performance pages with launch control. Then you also have the performance pages right here. And I'll show you those in just a second. But back to down here, you get dual climate controls, volume and tune controls, and fan controls. So here are your performance pages. You get timers, 0 to 60, 8th mile, quarter mile, brake distance. You have your different gauges, G-Force. Then you get a live reading from the engine there for horsepower and torque. Obviously the car is off right now, so not much to show. But that comes with the car. And you do get the six-speed manual transmission. The keyless entry with the enter and go system. Passengers side, floor mat and seat are in excellent condition, no rips or tears. This car smells very clean inside. I don't think it's ever been smoked in. Headliner is in great shape. Get map lights, home link buttons for your garage door security systems and lane systems. 911 and assist buttons in the rear view mirror. We will start it up and take a quick look under the hood. I'll let you hear it start up here. Sounds really good. I would personally like to thank you for checking out the video today. Hopefully from this HD video. A little bit in but tell just how clean this car is all the way around. Inside and out. Under the hood we have this 6.4 liter V8 heavy motor. 185 horsepower engine bay is extremely clean. It's very smooth. Once again this car has been fully safety and inspected by our service shop. It has a brush, oil and filter change. All the fluids have been checked and topped off. It has four brand new tires. And this car is 100%. Ready to go. See the HID headlamps right there. The LED running lights. I would highly recommend this car from a quality and condition standpoint. And to see more pictures of this car or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers, challengers, chargers, Mustangs, Camaros, Corvettes, GT500, zoom name it we got it go to our website right there at www.summitauto.com Full pictures and descriptions of every single vehicle from two locations all at summitauto.com. And if you'd like to check out more HD videos you can go to www.youtube.com www.summitauto.com Remember to like, subscribe and share on this video and all the videos that you see there. In fact, in a second you'll see a link to subscribe to our YouTube channel in the upper left. A link to more Dodge Challenger videos like this one in the upper right. A link to this vehicle on our website in the lower left. And a link to our latest YouTube video in the lower right. Click those, check us out and we're super excited to be offering this extremely clean 2015 Dodge Challenger SRT, I'm sorry, RT Scat Pack in Redline Tri-Coat Metallic. Thanks again for checking out the video.


Yo what up, welcome back to another episode that seems a little different for some reason. Well, I'm in the middle of an explosive colon cleanse right now, so I figured why not just do a film review. So let's take a moment to stop thinking about entropy and the inevitable heat death of the universe, to instead think about motion picture film, more specifically, Sobersaults 35. Motion picture film has been making a lot of waves in the film photography community lately with more and more shops able to process it popping up all around the globe or flat disc, depending on your IQ. Just one of the biggest to enter the game in recent memory is Sobersaults, which translates to Silver Salt in German. But before you get too excited about cocaine, Sobersault is actually a reference to the silver light sensitive halide crystals that coat a strip of film. Sobersaults has already kind of made a name for itself, offering photochemical services to major motion pictures in the European region. In fact, their German office took their entire motion picture workflow and made the process compatible for still photography. I had a chance to hop on a call with Thomas Bergman, who is a managing director over in Germany to clear up some things about the pipeline and verify that they weren't actually running a meth lab. This image that's on screen right now kind of looks like the TV show Breaking Bad. Have you ever watched that? This was, to be honest, the inspiration a little bit. This is what our lab looks like. Basically, we use this sensor machine. It's a motion picture scanner that scans 4K HDR. And this we use for our motion picture customers and for our open projects and for you guys. Bergman goes on to describe this custom one of a kind machine that they built to process all these roles of film. We had a little cooperation going on with a very old guy. He had a lab. He was running a lab for like 30 years. He did never buy anything. He just constructed everything himself. We collaborated on coming up with this processor. The quality is very high and we are very proud that it does not touch air at all. So chemistry stays fresh very long in there. I found it kind of interesting that in order to develop multiple roles of still photography in a machine that processes mainly motion picture film, they have to tape one end of the role to another to feed it through the system as one long piece of film, just like the human centipede. So what you're getting with Silversols is the exact motion picture process, but for still photography. What that means is if for some reason you really liked the last Jedi and wanted to steal their film look of the movie, this is your chance. You can now shoot the exact same motion picture stock that that cinematographer used in the scene where Luke Skywalker jerks off a space cow.  We finally had a sunny day here in LA, so we hit the streets. Just kidding. Every day is sunny here. It's paradise. When half the state isn't burning to the ground. I met up with Caleb and handed over one of the roles to be used in his Canon 1N. I handed over the 50D to be specific. I was sent four roles and frankly I have a hard enough time getting through one role, so definitely gonna need some backup. When it came to choosing a camera to use with cine film, I figured what's more cinematic than the X-Pan, or in this case the TX-1. And don't worry, not every video from now on is gonna feature the TX-1. I'm just in the honeymoon phase with this camera. We headed down to Echo Park Lake, because it was still too early in the day to shoot gas stations at night. One thing to note here is that SilverSales actually recommends shooting all of its film one stop overexposed. In fact all the cartridges that you get from them will have a DX code rating that is one stop overexposed. So 500T will read as 250, 50D will read as 25, etc etc. If you like sun flares that blow out your photo and make you embarrassed to call yourself a photographer, so you cut all ties, sell your cameras, move to another state and change your name, then boy oh boy is this the photo for you. Photo of Caleb in his power stance, always ready for battle. So what is the whole process like?  I had one role of every stock that they offer, which is Vision 3, 50D, 200T, 250D, and of course the infamous 500T. Once you've sent your film back they process it all in about a week's time, sometimes less, and they send you high-res scans as well as preview scans via Dropbox, but more on that in a bit. Additionally you can request that your film be returned to you for home scanning, storage, autoerotic film strip asphyxiation, etc. This photo is an interesting case study in photos that you took, but you're not quite sure why. I think the day shots ended up looking pretty nice, but I was a little more excited to see what the nighttime photos would look like. So Caleb and I headed out at night in search of greatness in the form of neon signs, a staple of night photography. I started off with some 500T. I suppose the camera should be on. I shot doubles of the scene and I'm not sure which one I like more. I think this shot is more to the point and simple, which is pleasant to look at, but this one has this badass streak, which reminds me I need to wash my underwear. Bro you did it. You did it bro!  I guess I could just shop it out, but would you think less of me if I did? Sometime around this point I got yelled at by a lady threatening to stab me. I think it's important to suffer for your art. Okay, so speaking of motion picture film, what about Cinestill? Did we just forget that exists? No, of course not, but it's different. What makes a cine film a cine film at the end of the day has a lot to do with the developing process. The secret is really in the sauce. Here's a crude and quick comparison between SilverSalls and Cinestill.  ECN 2 chemicals are hard to come by, in fact most photo labs won't even go near this stuff.  With the Remjet layer out of the way, it opens up the cine film to be easily developed in standard C41 chemicals, which just about all photo labs do process. However, there are a few problems that arise. Most notably these orange sh** stains around the highlights of the image. These are called halations, and if you think they look cool, you're not alone. If you think that they look distracting and ugly, you're also not alone. The Remjet layer that was on the film that Cinestill removed was there to crush any halations from appearing, or God forbid unionizing. The ECN 2 process as a whole renders a finer grained and flatter image compared to C41. A flatter image helps arrest any extra detail in the highlights and shadows, and is designed to be flat, so cinematographers and colorists have a bunch of latitude to play with if they want to design a look in post. Basically cinematographers 20 years ago, they were taking like 16 stops of dynamic range to bring as much as possible latitude home, and then decide about contrasts later. If you have trouble learning anything unless it's in meme form, think of it this way. So that's it. Basically it boils down to the process. Soversalls uses the entire pipeline that Kodak recommends for its Vision 3 motion picture stock, and Cinestill throws the rulebook out the window completely. I'm not saying one's better than the other because honestly there is no right answer. Straight up, it all depends on the look that you're going for with your work, and that's the simple truth of it. What you see here is called densitometry. This is happening every morning before we process. So basically Kodak sending test strips, we process them, and then we can compare our chemistry to the official Kodak stand that, for example, here we were pushing the film for one stop. Basically you see the complete truth about what's happening to the colors and to the contrast. Is that a digital camera? What? No? Me? This photo of the phone is the perfect example of good idea but bad execution on my part. The lighting and colors aren't working for me, but the composition is nice. I soon found myself in a bit of a sticky predicament. I needed to wrap up this roll of 200T, but it was daytime out. If you don't know, the T in 200T stands for tungsten, which essentially means that the film is balanced for artificial light. So if you shot tungsten film during the day, you might get kind of a blue and desaturated image. Fortunately, there's a way to unf**k this whole situation. You can actually purchase a tungsten to daylight filter. The one I have here is an 85B filter. Once you slap that bad boy on the lens, you can shoot tungsten film in daylight. It's magic. If only the 85B filter solved all my problems in life. Here's a quick comparison of a totally original never before seen shot, shot with and without a daylight filter. As you can hopefully tell, the colors are a bit more balanced in the daylight filter image. And the straight tungsten image is a lot bluer. And here's another shot with the 85B filter. Looks pretty normal, which is something my doctor has never uttered to me. One night, we had this pretty crazy rainstorm pass through LA and so I took advantage of it to go shoot this gas station. I really like this shot. It's a shot that I had been kind of planning for a while and I think Silversalls was the perfect stock to use. But later on, I dared to ask the question, what would happen if I don't shoot neon signs or gas stations with tungsten film? Is the world even ready for such a thing? So let's talk about scanning. Everyone's favorite topic. When your Silversalls film is done, it's processed and scanned. You get a Dropbox link. And for each role, you have three folders. Image preview, full quality and raw scans. Full quality and raw scans are JP2 files, which is an uncompressed JPEG format. I mean, I guess standard JPEG format was already at rock bottom. So I really had nowhere to go but up. These are the files that are meant to be edited by you in Photoshop or Microsoft Paint if you're really talented. I think currently Lightroom cannot import JP2 files. You also get an image preview folder that exists for a quick glance of your shots with a standard look applied so that you can really get an idea of how your image might look with some added contrast and saturation. But me, I'm not so easy. Well, I was in college, but not anymore. I wanted to see what these bad boys would look like run through my editing program of choice, Negative Lab Pro. Long story short, the image output from Negative Lab Pro is actually pretty damn similar to the preview files. But in my opinion, I think that the home scanning takes it that extra mile and just polishes it to perfection. Here are a couple of my home scans compared to the preview files that were delivered. As you can probably see, there's a little bit more latitude and more vibrant colors. This is kind of to be expected. According to Silversols, the preview files are really just that previews. They are really just meant to give you an idea of how your finals might look. With all that being said, if you prefer not to edit them at all and just wanna blast the images up on Instagram, Reddit, MySpace, whatever, then you can totally just use the preview files. So what'd you think of the shots? I think the colors are just too good to be true, especially the night photos. There's just something so crisp and clean about them. Dare I say it, synagazmic. I think this is my favorite shot. After all, neon signs are a lifestyle at this point. I can see Silversols' film being used for all kinds of work. It might be interesting to kinda play with juxtaposing it against something mundane or something we perceive as standard to life. That's right, I'm justifying taking more toilet photos. You can have every special project you like. So if you wanna push or pull or bleach bypass, you can have it without extra costs. I think it would be fair to talk about some of the cons with the whole process, aside from the fact that they're based out of Germany and might be friends with the bad guys from Die Hard. For starters, shipping is gonna be rough, especially if you're like me and you live in California and need to ship to Germany and back. However, if you live in Europe or the UK, it's probably a non-issue. Additionally, Silversols only offers 35 millimeter. As of right now, they do not currently offer 120. I had the chance to briefly inquire about this when we chatted over AOL Instant Messenger. We would love to do it and we hear this question like, like literally several times a day. The processing side of things is easy. The scanning part, it's the challenge. So with all that being said, I think Silversols has a very strong foundation and a healthy head start in the motion picture film market. As well, they seem very dedicated to improving the cine film workflow as well as their pipeline in the future. Me personally, I think that's definitely something worth supporting, especially if you go ape-s**t for motion picture film. Whether it's upgrading technical equipment or improving logistical shipping issues, I'm excited to see where their pipeline goes and what they do next. I was certainly more than happy with the results I got back and a few of my images are gonna go into the portfolio. If you want even more cinematic goodness, you can follow Silversols on Instagram or even here on YouTube at gods of grain, even though I'm internally conflicted because I guess technically they are a competing film photography channel. So I should be trying to destroy them.


So welcome, everyone, to Istio Day. This is very exciting. So my name is Arthur. This is Bourdon. We are both SREs at Pigment. For those of us who don't know you, we don't blame you. We're a young company. And Pigment is a French software company. And so we've been using Istio in production since the very beginning of Pigment, so four years ago. And this talk is not about explaining how Istio works, because we don't fully understand it, but more about how we use it at Pigment. So brief aside, I'm not going to pitch you Pigment, but what you need to know is that Pigment is a web application that stores user data. They can use our application to import their data, transform it, visualize it, and do that, you know, make business decisions based on that. So there are zero Pigment users in this room. Well, two, because we talk food a little bit. That's it. So the way this talk is going to go is we're going to start with why we actually set up a global request routing to achieve seamless data locality, and then how we did it, which is the interesting part. And then we'll conclude with some next steps that we can see in the near future. So why did we do this? Why do we care about data locality? Why do we care about where data is? And the fact is that we're all tech people here. We care about where our data is. And the fact is that most organizations are starting to care as well. There's legislation in place, like GDPR, CCPA, that actually enforces rules on data and how it is managed, depending on where it is geographically. And so companies we want to sell Pigment to, they are starting to care a lot about where their data is. And so we need to have a response to that. And so our response was, well, I mean, when we talked about with our users, potential users, we wanted to sell Pigment to, what we figured was there are three things that are important to them. The first one is that they want their data to be stored and processed in a specific region. We call this a location in our implementation. And basically, European users, they want their data to stay in the EU. American users, sometimes they're OK with the EU, but sometimes they want their data to be in the US, et cetera, et cetera. So they want to be able to choose. The second thing is that users want a single platform. Users don't want on our login page to have to choose EU, US, Canada, whatever. They don't want to do that. They just want to click Login and be logged in and for it to work. So it needs to be seamless somehow. The fact is, organizations care about where the data is, but users do not. Users just want to use the app. They don't care about what data center they're using. And finally, they care about their data. So we have to protect it. We are stewards of their data, and so security is important. But then on top of that, we had Pigment R&D. We added some requirements to that. So first of all, this multi-regional, this global infrastructure has to be reliable. But when I were SREs, reliability matters to us. And also, when we're extending this infrastructure, so we're going from a single region application to a multi-region application, we don't want this extension to actually require downtime. We don't want to break our application even temporarily to be like, OK, well, hold on. Pigment is down for two hours because we're migrating. We don't want to do that. Third, we want our infrastructure to be cloud agnostic. So today, we're running on Google Cloud, but we want to be able to extend elsewhere, mostly because we have some potential users who don't really like that they don't like to give us money that we then give to Google because they're also working in advertising or something like that. So we want to be able to move to or extend to other cloud providers later, which is why we use Kubernetes, which is why we use Istio. It's really nice to manage your own stack. And finally, we don't want to compromise our productivity as engineers because we're managing multiple regions. We don't want to deploy more slowly. We don't want to have more operational load. And these are the things that are important to us. And so I'm going to pass to Boudewan who's going to talk about how we did it. So at a very high level, Pigmont's infrastructure is a quite common pattern. So we're Austin on Kubernetes. We have a set of databases, a set of backend services, gateways managed by Istio. And that's pretty much it. And with that project, what we wanted to do is do the exact same infrastructure but in the US, separate set of services, separate set of databases. And so came the question of the user experience. So what we could have done and didn't want to do was to have each infrastructure behind a different host name. That's the quickest. But as Aatro mentioned, we wanted something similar for users, so we did not go that way. Instead, what we decided to do was to route users to the correct location at the gateway level, leveraging Istio. And so American users would use the same host name as the European users. And the gateway would redirect their request to the correct location. So pretty simple. And this setup work as is, so perfect. Small problem, however, small detail, is that for American users that want to access the US location, that would be an unneeded back and forth. So not a big issue with GODNS. They resolved to the closest location, and that's fine. And in all different scenarios, well, they will still get routed to the correct location. And so perfect, no problem here. So now comes the question, how do we do that with Istio? Exactly. So for that, we'll average virtual services. So our gateways will serve two host names, one public, used by users, and another one internal, used by gateways to route to each others. So what the gateway will do, it will first check the presence of the HTTP header or query parameter to determine if the request that it's processing is meant for the current location or another one. If it's meant for another location, then it will send that traffic to that gateway, to the gateway of the other location. And if the request is meant for this location, then other matching rules will be used, and it will be then delegated to another Istio virtual service that will handle the routing and all the details to route to the correct endpoint of our services. So overall, this looks great. It's simple. But there is a downside is that it's a lot of virtual services to maintain and update and keep tracks of. We have a lot of services, lots of environment, and this number is increasing every day. It's error prone and tedious, especially for developers. So to tackle that, we decided to generate the virtual services from a configuration file with listing the endpoints for each service. So we don't have to modify by hand hundreds of files anymore. It's much quicker and less error prone, and devs are much happier. So everything looks good, but is it enough? Not exactly. There are a few HKS we still have to address. The first one is the global user authentication with that pattern. Because really, since an articulated user can log in from anywhere, we have to be able to do this login and find a location from anywhere too. So to do that, we went for the simplest way. So we shared the database for authentication. It's hosted in Europe. It's a simple caching. There is a simple caching at the application layer for performances. But the user cannot log in from any location. The data of the company stays on different infrastructure, and it's just the only piece of data that is shared across location. And I will let Hatch you talk about the second HKS. Thanks. So now let's talk about requests from third parties, because this is where it gets exotic. So as Bono mentioned, if we have a request coming in from our front end, the front end has authenticated the user. And so it knows where that user's data is, and it can set a header that our virtual source is used to route correctly. The issue is with requests that don't come from us. So these are requests, for instance, import calls that come from our user systems, or WALF callbacks that come from whatever single sign-on provider they have, or webbooks. For instance, we have a Slack integration, so we get webbooks from Slack. And most of these third parties, they don't allow setting request headers. We can't configure them to say, well, for this rule, if it's this Slack channel, please set this header to production EU1, please. They're not going to do that. And also requiring this header would actually break API compatibility for our own users. Those that have already been using our import API, we don't want to send them an email being like, OK, you have one month to start adding this header, or your imports aren't going to break. We don't want to do that. So what we did is we used an envoy middleware. And so this is where Istio comes in, because none of what we've been talking about until now is very Istio-specific, and now we're getting into it. And so the middleware, basically, when a request comes in, the middleware runs. And its job is to determine the target location of that request. And it can do so by communicating with the back end to get information. And once it's determined the target location, it sets the header, and then our routing logic from before happens, and proxies to the correct gateway. So to inject a middleware in Istio, I use an envoy filter, custom resource. I'm not going to go into the details, but basically you tell it where in Envoy's filter chain, you want to inject the middleware, and then you just inline the code at the bottom. That's pretty much it. So what does this middleware look like? First things first, it's written in Lua, which is pretty high level language and surprisingly fast. We were really impressed by the performance here. And basically what our middleware, to write a middleware, what you need to do is you need to implement a handler. This is the envoy on request function. And what our handler does is determines if it actually needs to do anything, if it doesn't, it returns early. Then it communicates with the back end to determine the target location for the requests that it's processing. And then finally, once it has that target location, it sets the X pigment location header so that our virtual services can do their job. So to get the target location, our middleware doesn't really know. Like if it gets a request with an API key in it, it doesn't have access to our database of API keys. So how does it know the target location? The way we do it is we take all of the requests metadata and data. So headers, query string, body, and we send all that to the back end to a specific endpoint asking the back end, hey, where is this request supposed to go? And so we send this to a special endpoint in our back end that has global knowledge. So that knows about all API keys in pigment EU and pigment US that knows all about that. And the back end can look at these headers, parse them, look at the query string, parse the body, make database calls, and then return a target location. But if there are any people, sorry, is among you, you may have heard that I am sending the body to the back end, which means I'm buffering it. I'm reading the entire body from the caller, keeping it in memory, sending it to the back end, and then once I have a response from the back end, and I can actually forward that body to the correct location. And so I'm keeping this body in memory. And so if an attacker, if somebody sends me a body that's one terabyte big, my gateway is not going to like that. And so we actually need to put a cap on the size of the body we're willing to read. And this is where Envoy is really great, because you can just read the content length header to determine the size of the body. And if the caller lied about the size of the body in the header, Envoy will just kill the connection the instant the caller just sends too many bytes. This is amazing. So this is actually really easy to do, but you've got to think about it. And if the body's too big, we just don't send it to the back end, which is enough for our use case, because the only time we need the body is for Slack callbacks, and the body is like 200 bytes. So how do you test something like this? The fact is this middleware integrates heavily with Envoy. It integrates heavily with our virtual services logic. It integrates heavily with our back end. And so actually unit testing is pretty hard. So what we opted for was black box end to end testing. So what we have is a few agents, different places in the world, that send at regular intervals, they send requests to our system, these requests, to a specific endpoint in our back end, which is that end points code is basically just respond with the back end's location. And that way we can send a battery of requests and check, OK, where are these requests landing? Are they landing in Europe? Are they landing in the US? And we can make sure that they're landing in the correct place. So for instance, in this example, the top API key is a belongs to an EU organization. And so it should be routed to the EU. And the bottom API key belongs to US organization. So it should be routed to the US. And so we can continuously run this. And the idea is that if the middleware ever breaks in production or before production, we get an alert. And so we know. So basically, if we want to change the middleware, we deploy it to staging. We wait for 10 minutes. And if we didn't get a message on Slack, we're good. And so at this point, we have the basic logic with the virtual services. We've handled the edge cases of authentication and third-party requests. And so we've met our requirements at this point. Our user data is stored and processed in specific locations. We have separate databases. We have separate back end instances. And we have a single platform. There's single authentication. They just go to pigment.app and it works. And there's seamless routing. Our EU users, they didn't even know when we made the US platform go live. They just didn't need to know. It just worked. Some of them actually saw decreased latency. They were like, wait, things are faster now. And regarding security, well, we encrypt the data in transit when it's in transit between gateways. And that was important to us. But we also have regular pen tests and a bug bounty program. So now we have 200 people who know how it works. If you find a bug, please call us. There's money on the line if you want it. And regarding our internal requirements, well, the extended infrastructure is very reliable. We've had no issues so far. We were able to add the US infrastructure piece by piece. And so this actually required no downtime on the EU infrastructure. We both deployed the cluster and then the gateway and then configured DNS, et cetera. The extended infrastructure is cloud agnostic. We use no cloud provider specific functionality here. It's just Istio, pure Istio config. And deploying to multiple locations is seamless. And I'll let Boudouan go into more detail about this seamless list. Yes, so actually mentioned some non-technical requirements that we had to address. One was that it had to be really seamless and not impact the rest of pigment R&D. And it's the case. Firstly, for backend services, our backend services, most of them, are not aware of the concept of location. They do not need it to do their job. And also, if we want to add a new location, we don't need to do any cut changes. And there is no downtime, as Arthur mentioned. So pretty simple on that matter. Also for developers, so we did not want to decrease developer velocity. It's especially important in a growing startup. So we have CI-CD tests and they deploy to all locations in parallel. So developers, it did not add any complexity to the job. And also, we just made sure to have location tags to dashboard and alerts to make sure that developers, especially on calls, would have the necessary information for troubleshooting. And there is also SRAs to think about. After all, SRAs put the system in place. The cross-location routing can be bypassed easily for testing, thanks to the internal loss names. Thanks to the black-box testing that Arthur mentioned, were alerted when the setup breaks even partially. And we've had no major outage due to this system in production since the go live. So pretty exciting for us. And well, even if everything turned out great, we still learned some lessons and made some mistakes along the way. So a couple of them. First is that we managed to self-doss ourselves. So we pushed a faulty manual configuration, we did a network loop between our two gateways and they just crashed. Thankfully, it was in staging. And since it was due to a manual config error, now we generate this configuration and as long as the logic in the code is good, this should not happen again. And something else also, we used the virtual service delegation pattern where parent virtual service would delegate the rest of the processing to a delegate virtual service. And we find out that for our use case, it was perhaps not such a great fit. So it's a pattern that can be error-prone, so you have to keep that in mind when you use it because it's easy to have a mismatch between the parent and delegate virtual service. Let's say, for example, you're matching traffic on a certain prefix at the parent level and you make a mistake, a developer modified just one chart and the delegates match another slightly different prefix. Then traffic will get dropped, so you have to keep that in mind when you use that pattern. And something else also, it's there is only one level of nesting. You cannot delegate virtual service, cannot delegate to a third virtual service. And for our use case and the image we have of infrastructure, we would have liked to be able to really separate virtual service for location routing, for backend service routing, et cetera. It's not possible, so it's something that for our specific use case is, well, we'd have liked to be able to leverage it and we're thinking of going back to one big generated virtual service instead of a lot of them. So we're getting close to the end of this talk. We're happy to be able to share this experience with you, with peers, like all of you. But the question is now, now we're looking to the future, like this works, this has been in production for nine months now. We haven't had any major issues and we've kind of moved on to other stuff because the company keeps growing. But regarding this setup, like what is next, what can we see in the near future? Or what do we want to do in the near future? I think the first thing we want to do is that we want to replace the authentication database. Like as Boudouin said, currently it's hosted in the EU and the US authentication service uses that database directly. The issue here is one of reliability. If the EU region goes down, the EU S region doesn't work anymore. The opposite isn't true. Like if the US region goes down, the EU region keeps working. And we'd like to split these failure domains. And so we'd like to have a global, highly available database for authentication. We'd also like more tests on the middleware, not because we think it's buggy. For now it works, right? But actually because as we add more integrations from third parties into our system, we keep adding more endpoints to the middleware than showing the code but manages some endpoints slightly differently. And the thing is today the feedback loop is basically we'll deploy the change to staging, wait a bit, and if it works, you're fine. But if it doesn't work, like the feedback loop is pretty slow. And so we'd like to have some form of unit or integration testing like in our CI so that we can quickly check if something works or not. We'd also like to extend this setup to other locations on the same cloud provider, so a different country, or different cloud providers. As we said, we made the conscious choice of making this setup cloud agnostic and we'd like to put that to the test. So that would be pretty exciting. We're eager to do it. It's not in like an immediate future but we can see it coming in like the next couple of years. And finally we'd like more cross-location features in the pigment app itself. Today like there are a few global features. The main one is authentication. But there are other features in pigment that make sense to be global. And we're working in collaboration with our dear backend engineers to actually make this work. And the fact is our network setup isn't perfect. For instance, like in this setup, services can send each other like HTTP calls via the gateways, but currently they can't send GRPC calls. But the backend mostly communicates using GRPC. So this is an issue. And we need to keep working to improve pigment on this. So thank you for your attention. And if you wanna join us, we are hiring. Thank you. All righty. And we've got a few minutes for questions as well. So if anybody has questions, go ahead and raise your hand and I'll bring the mic over. Sorry, I crossed the room here. So it seems like you're kind of a duplicating. You can correct me if I'm wrong. What I understood like you're kind of a duplicating the whole infrastructure for us. And you are like redirecting the request just on the basis of the gateway. So do you like in the whole process, have you thought about like putting some microservices as a central because these things we do because we have a PII data or these kind of regulations. So have you thought of like binding a few microservices which has no relation with like storing the data and PII data and just processing it centrally and then just restricting the reason-based things to the PII data or the data where we are storing or processing on everything? That's a good question. We thought about it. I think is in our case, it's not really PII data, it's business data. And just so happens that are sometimes there's PII data but we don't know about it, right? Sometimes users put PII data in our system. So we kind of need to assume that everything is sensitive. Today most, like I'd say like more than half of the pigment app itself is about processing this data. Fundamentally, it's a data processing application. And so I don't think it would make sense for us to just extract like a third of our microservices and put them and consider like, okay, these services aren't sensitive and so they're separate. I think we kind of like having this sort of monolithic infrastructure. Now we have to, I guess. I mean, we considered it and I think it's just a matter of preference that we went this way. Is there a question over here? More questions? I was wondering if you could clarify with Istio for the gateway, what, where does it overlap or what degree are you dependent on Istio for what you're offering? And then when sort of solo pickup or what was really cool about solo that you opted to use that to extend what you're doing? Gateway side I'm at. Yeah, a couple of things. Well, the first thing is we don't, we mostly use Istio for the service mesh. We just happen to already have the gateways and invoice capabilities at our disposal when we start to do work on this project. And to answer your question about solo, we don't use solo. Any other questions? Otherwise, I have one, I have one quick one while I'm walking over, which is, so for the middle where you implemented that in Lua, did you look at Wasm or not or was there any kind of debate or decision between those two? There was a discussion. We opted for Lua initially because the middle where isn't that big. Like I only showed like the gist of it, but overall it's maybe 300 lines of Lua. So it's not a big thing. So we figured like a scripting language was fine, but we may consider it Wasm for a more complex use case later. Okay, thanks for sharing. If I understood it, you have two regions like the US and Europe and have you thought about scaling these up? I mean, imagine you have 20, 30 points of presence. For example, you have zones in Germany, France, UK, several in Asia, like I don't know. Have you thought about scaling this infrastructure? I mean, it's expensive to keep the full set of your applications in each zone, yeah? And now you have to create something, you know, to put some services in Germany, some services are deployed in France, some of them are in the UK, and you have to split the traffic to route it across these regions, across these zones. Have you thought about this? I mean, when you have not two regions, but a lot of them. We have thought about it. Like how does this scale basically? What we're mostly worried about is the operational load of actually operating all these clusters. From a financial, like a cost standpoint, it's not really an issue. The core of our cost is our databases, and the fact is if we deploy a cluster and there's nobody on it, then it doesn't cause very much relative to the others. Okay, thanks. Hey, hello. You mentioned having issues with delegated virtual services. Have you considered using the Gateway API? Kind of what's, if you know the pros and cons? We haven't for the simple reason. So we're using Istio for four years now, and so we already had the gateways managed through Istio. So we didn't really, when we started the project, wanted to take care of the migration. Something we may revisit someplace in the future, but as of now it works. But yeah, it's definitely something we see a lot of work being done there. I'll just add one thing. As Boudon said, we already had virtual services everywhere, and we only needed to add a little bit of functionality to them, so we didn't figure moving to the Gateway API was what we wanted to do. It seemed like a big thing for just this small feature, but we are definitely keeping an eye on it. It is probably something we'll do relatively soon.


In this chapter, we will give you very quick overview of USB-C. Possibilities and features introduced with this new type of connector are very wide and only some of them will be mentioned here. On the picture you are able to see signals inside USB cable with reversible connector. In total, it's 24 pin, all of these 4 are dedicated for V-bass and 4 for ground. Signals for both high speed, so the USB 2.0 specification and super speed, which is 3.x specification, are included and doubled in order to keep the reversibility of the connector. But don't be mistaken, USB specification is alongside with USB 2.0 or 3.x specification. So with USB type C cable, you can meet either the so-called full-featured cables, which contain all the signals including the super speed or the cables which are missing the super speed. So only high speed communication is possible with this cable or cables completely without any data communication, which are intended only for the power options and power delivery. Interested from the microcontroller point of view are the power options introduced with the type C. So now the default power option can be up to 15W, so it's 5V with 3A and additional power delivery protocol, which is using directional communication on so-called CC pins, can negotiate the power profiles up to 100W, so on 20V and 5A. With USB type C and power delivery protocol, also alternate modes can be used. So for example, Ethernet, DisplayPort for image transport or audio can be negotiated. The power delivery protocol can be used only if both connected sites are using USB C cables and supporting this protocol. And what is also new compared to the older USB specification is that with USB type C power roll and data roll are now split. So it's not true anymore that only host can be the provider of the power on the bus. Now it's independent and can be negotiated and switched on the go. If you want to use the advantage of a nice reversible connector or also improve the power capabilities of your current design or new design, it's very easy to adapt only using to resistor. And such configuration you can see on the picture and more details can be found in USB type C specification or also in ST application node AN4775. Now a bit closer to ST offer with USB type C and power delivery. The oldest offer demonstration board is PNUCLEAR USB 001. On this board is STM32F072 with analog front end. The analog front end is used only for the voltage level adaptation according to the specification of the USB C and power delivery. But all the tasks are done here by the STM32. So it's completely covering the stack, covering the communication and as quite a big part of the peripherals for the specific tasks for which the peripherals are not prepared is used here. The resources demanded on the STM32 site are quite big for handling the USB power delivery communication. So in the next level is PNUCLEAR USB 002 where USB type C port control ST USB 1602 is used. This port control is already covering the lower part of the stack and also is taking care about electrical protection of the USB connection. But still some peripherals and some handling and the stack itself need to be covered by the microcontroller. Again STM32072 is used. With the ST USB 1602 microcontroller need to use both SPI and I2C to control this part. Another solution is to use USB type C port manager which is marked as TCPM. The usage of TCPM make the solution very universal and easier because the port manager is covering completely the communication and only I2C for the controlling of the port manager is needed. Which makes this solution very easy and universal among also other families. What is offered as a firmware package is called XCube USB PD where you can find examples, stack and drivers for all three solutions mentioned before. So this is already free of charge available on ST.com. All the solution mentioned until now were using MCU so it allows more universality also adding additional functionality to the design itself. And thanks to MCU also dual role and alternate function is possible with this board. But if the application is going to use only the consumer part or should act only as a provider it could be easier, cheaper and faster for development to use stand-own solution without any microcontroller. And for this there are two possible way where to go. So it's either ST USB 47X0 for the provider only functionality or ST USB 45O for consumer functionality. Both of these chips have non-volatile memory so the EEPROM where you can set the parameters of the connection and then these chips are working stand-own without any microcontroller to create the demanded functionality. So the solution then can be easier but it's lacking the universality and flexibility.


This paper explores global UAV regulations, highlighting their importance and impact on research and development through a comparative analysis of national regulatory frameworks, revealing distinct variations in all compared variables, while market forces such as industry design standards and reliable information about UAVs are expected to shape future developments. This article was authored by Claudia Stalker, Rohan Bennett, Francesco Nax, and others.


Well, hello and welcome to understand men now. I'm your host Jonathan Astley of Jonathan Astley.com And I'm so excited to be shooting this short video for you today our topic high quality men are attracted to these seven Feminine values or qualities, okay All right really quickly if you're new to my channel, please do me a favor hit the subscribe button where it's ever It's at and do me a favor share this video with your friends if it resonates with You and if it doesn't please leave my channel. I'm just kidding. All right our topic those seven Feminine values high value high quality men are most attracted to Okay, for those who follow my work, you know, I'm not big keen on the whole terminology of masculine and feminine energy So let's just say man and woman, okay? Let's make it simpler because oftentimes women are confused that when they're they're a woman But they're in a certain energy. It's considered masculine as if it's a man, but it just happens to be Great qualities that you have just like men have great qualities and women have great qualities So we're gonna talk about great qualities that are really attractive to both sexes. Okay, so of those seven that we're really attracted to Quality number one your actions match your words your actions match your words It's so important that in the dating process that in the relationship process that we are consistent with our words We're consistent with our behavior if you're not familiar with the book the four agreements And I've got it somewhere here The four I should just go run and get that for you But the four agreements is so Important to learn for oneself because one of the first agreements that you make is to be impeccable with your word And there's nothing sexier whether a man or woman is if your actions match your words And I know ladies you're attracted to men that show up that way and we are attracted to women who show up that way as well And it's not that hard to do. It's learning to actually have integrity within yourself Because that's highly attractive. I don't really need to go into that one too much detail, but number two is That you take personal responsibility for your choices you operate from Victor consciousness I'm gonna do that Victor consciousness versus victim consciousness Victor consciousness means that you're empowered with your life that you take Responsibility for all your choices and while bad things can happen to people you don't operate From the place that you know, it's you know, somebody else did something to me because most likely You on some level put yourself in that situation. I know that can be misconstrued. So I'm talking about the general things that happen And I don't mean that you happen to be driving down the street one day in a car hits you Yes, you put yourself there But yes, that is an accident. Okay, but in this particular case, I'm talking about the choices you make in Relationship the choices you make in other words, you know that the man is bad for you But you keep going after me, you know, he's a bad boy, but you keep leaning into the relationship You know his actions don't match your words But you continually move into the relationship and then you wonder why it collapses And then you're pointing the finger at him and not taking ownership those three other fingers pointing back Taking ownership of your own part Incredibly attractive quality when a woman takes personal responsibility for her choices She acts like a victor and not a victim the third highly attractive feminine value that we high quality men are attracted to is that you know how to fight fair And what I mean to say is relationships are gonna have conflicts They're gonna have friction with one another and you know how to express your needs wants and desires in a way That's conversational and not confrontational You're gonna express your needs wants and desires desires in a conversational not confrontational way If you're not familiar with the book nonviolent communication by Marshall Rosenberg Check it out because this is all about learning how to Express your needs and how to fight fair and what I mean by fighting fair as you listen to your partner's Opinions and perspectives and you accept it as being true for him just like he should accept Your opinions and your feelings as being true for you because your feelings are true for oneself Just like his feelings are true for him and When we can accept another person's feelings and we acknowledge another person's feelings and perspective doesn't mean you agree with it But certainly when you accept and honor it That is a highly attractive Feminine value, you know, I'm doing this tongue-in-cheek because I think it's just a human value. Okay Next is empathy Empathy you have empathy for your partner's feelings You actually care about your partner's feelings and they care about your feelings Empathy isn't as much about you can feel their feelings because that's certainly great But you actually care about your partner's feelings and their feelings are important to you Whoa Their feelings are important to you and just like you want that high quality, you know Just like you're showing up as a high quality high value woman He has to show up as a high quality high value man Your feelings have to matter to him and his field and he sees your feelings as Important to him as well because that's a sign of emotional maturity the fifth sign is transparency In other words, you're in a relationship where you don't have to sit there and second guess a Man doesn't have to second guess how you feel about him. You're expressing your feelings.  It's not a guess. You're transparent now That's not to say you vomit your feelings.   You lean into the 50 yard line and that's part of transparency That's a very sexy high value feminine action. Okay When you show up at the 50 yard line, you're not crossing the 50 yard line But you're not leaning back on the 10 yard line waiting for him to get you Okay, because men aren't going to do it They might chase sex for a few minutes, but they're not going to get you if you're always back They're going to be on to the next person at least a high quality man isn't going to be playing that game That's for the book the rules. You can go read that book The sixth And this is an important one is respect Is respect I think it's so important that we treat each other with respect and Sadly ladies, I know you haven't been respected by men.   You've been hurt by other men. They haven't respected you And now you don't respect men going forward And I'm here to say is if you want an amazing relationship, then you have to start From a level of respect and then watch to see if his actions don't meet And I wish I could shake men by the head and say start treating women with more respect But ladies if you've been disrespected by a guy Don't show up in relationship already assuming the worst in men because if you start from a level of respect Start from a level of going I respect you And I'm gonna like in other words I'm you're innocent before you're proven guilty That's gonna pay so many dividends in the long run in your relationship Yeah, that's a big one. Okay And the seventh Number seven uh All right, this might be a Jonathan one. Okay, by the way, there's more than seven out there. There's probably a hundred I'm just coming up with the seven that I like but the following is a Jonathan one and for those who know me know that I'm a Leo And we leo's oftentimes if you're familiar with the five love languages Our love language is words of adoration. It's actually words of affirmation, but I like to say adoration And I'm gonna say the seventh one Is compliments is compliments You know and it's not just compliment, but it's validating your guy. It's letting the guy know that he's your hero You know We men like to be complimented for our looks, but we also like to be complimented for our efforts And appreciated for our efforts I can tell you so many men have told me over and over again that they've been in relationship with women that they Haven't felt appreciated for who they were And that's sad to me because I know so many men that make so much effort and yet they haven't been acknowledged for that effort So I I take appreciation and compliments together because I'm the leo in here But I like to be a complimented for my looks and I like to be complimented for my efforts Complimented for my efforts and I know I'm not alone. There are so many men that feel the same way in high quality men Certainly want to be appreciated and complimented for their efforts Ah Wow, we covered a lot All right, I know you probably have some questions about what I shared Please post your question below. I read all of them or do my best to read all of them. I try to respond to them I certainly like to engage in interacts. So if you have something to say, please post it And if you like the content, you go god, I'd like to have access to jonathan Check out the link below or regarding a scheduling a one-on-one call with me to see if coaching is right for you And check out my link for my vip group as well if you can't afford coaching All right, I'm going to sign off this video right now giving myself a big gigantic jonathan bear hug I'm actually giving it to you right now and I'm going to ask you to do the same and grab yourself and give yourself a hug right now Because we all need hugs Yeah All right, wishing you a super duper wonderful fantastic day. Thanks so much. Bye. Bye now