Welcome everybody at day four at SHA 2017. Our next speaker is Vesna, and she will give a lecture on Ethics in Technology. Enjoy your talk. Hi everyone, I'm very happy to be at SHA 2017 because at this occasion I'm celebrating 20 years anniversary that I am attending Dutch hacker camps. So it's not too far away from the first place, which was at HIP 97 in Almere Bouter, so here I am back again in the polder. Why this talk about Ethics in Technology? Well, I've been very happy to be part of the modern science advancement and the engineering and the beauty that was the internet for 25 years. I've been a techno-optimist and I believed that the science and engineering and the internet are going to make the world a better place. And that corresponds with this white space in the Yin and Yang symbol. So it's the symbolism for the positive energy, for the expansion, for the growth, for all the good things. And then about five years ago I actually turned to the dark side and started being techno-pessimist.  And that's really scary and then I was thinking what can I do about it? And then I started exploring this grey area which is ethics, the values, the reasons why we do things, the reasons why we believe that something is good or bad. And that's somehow connected with my passions, things that I care about in daily life, but it's also connected with my work. So luckily I can combine these things because I work for IPaNCC and I'm a community builder there. And so I came from this engineering background and went towards the outreach, giving lectures. And what I'm not is an expert in philosophy of ethics. So it's just something that I'm passionate about and this is where the hacking comes into the picture. So I'm kind of hacking the psychology of ethics in our own way. A little bit about logistics. This talk looks like it's actually consisting of three parts but it's actually three talks crammed into one talk slot. So I'll be talking very quickly. I'll be skipping a lot of slides and I might not even finish by the end of the hour. So I actually booked another hour for the discussion in the Cha village next door. So if there is no time for the questions after this, we can move there afterwards. And since I'm celebrating, there will be probes. These are the references that I will be using throughout the slides so please read them because I cannot cram all of that in one hour. So let's start. The science and technology and then ethics. So what is ethics? Well, Wikipedia definition is here. So it's a philosophical study of looking into our values. So some people call it morality, some people call it ethics and then there is like a lot to study about that. And the people from the beginnings of the western philosophy have been studying this a lot. So as hackers, we sometimes tend to think that only the engineering is science so only natural science is a science. This is also science and we need to put some effort into incorporating all the learnings that have happened over the centuries to start with but also over the millennia since we were humans into thinking how do these values apply to this very, very modern technological field very narrow field that we are dealing with here at the hackers conference. So here is the handy pie chart that splits all the sciences into different disciplines which is great for going very deep into ethics of each one of these disciplines but the problem with that is that it also actually creates this silo mentality where you cannot easily get the interdisciplinarity between the philosophy and engineering. And that's what this talk is trying to merge and this is what I'm trying to actually invite you to incorporate in your practices trying to be interdisciplinary between things that are maybe not exactly your area of expertise. So since the classical sciences started developing well recently there were a lot of moral dilemmas for example with the development of nuclear energy and the threat of the nuclear destruction of the whole earth. In the medical sciences we had had to come up with oath of Hippocritus which then has to be applied on dealing with people and also on the medical research so there is a lot of ethical questions there and then similarly with the development of the chemistry we had to look into the ethical consequences of using these chemical products that are beneficial for certain tasks but actually destroying the rest of the life or biosphere and leading to extinctions of certain species. So the silent spring from Rachel Carson was started in the 60s this movement in the environmental sciences and ethics. So this is only there to kind of give you the background reading if you download the slides because I will take this as a given. Technical is political. As well as the programming is political, languages are political, artifacts have politics the translations are political, crypto is political, coding is political, personal is political everything is political but that's not my talk so I'll just move on. So again, in the more recent and a bit more focused on this crowd history we had a lot of ethical dilemmas with using computer science for the things that were maybe not intended to like counting the victims of the Holocaust or what is the artificial intelligence going to do when we embed our ethical biases, unconscious biases into programming artificial intelligence then we had of course cryptography then we have the privacy in the networking and all these things that of course covered by other people in the talk so I'll skip this and come to the internet and the free software and hacking so the problem with realizing how powerful the ethics and values that we have in building the internet is so many so I will just point to some of them when the internet was developed it was developed by geeks and academics and engineers and military and it wasn't meant to take such a large role that it has in the society today so the initial people who actually developed the internet because it didn't just appear it was actually developed by people those people had certain ethical values and they have built it into the foundations of the internet and now we have to deal with the consequences of that so we discussed all kinds of things there like biases, discrimination, sexism, whatever and the other important thing there is that a lot of these people used to feel like being on the margins of the society or they're just engineers or they're just geeks or they're just hackers and even themselves they were feeling discriminated against and now we who were these geeks and nerds and engineers and hackers we are not anymore on the margins of the society we are building this core network, this internet which is used for everything it's used for health, it's used for banking and for transport and for the social media and it's a lot of responsibility for ourselves to bear but we have to take that responsibility the similar thing with free software so it was a really nice idea the ethics of free software are beautiful and these quotes come from a book of a friend of mine which I want to promote so here's the link and then after the free software or Libre software came the open source and already there in such a small part of our small community there is already the ethical values that are clashing with each other and they are unexamined because we as engineers as hackers we don't really want to think about that and we're not even trained to think about that but we need to learn it because since recently everybody needs a hacker and we also have hackers ethics so this is a mandatory slide so talking about ethics and technology and the hackers conference we have to have hackers ethic as it is listed here but in one of these references that I already showed there is a link to a talk by Allison who actually questioned all of this so we will come back to this and see how can we question even such a great thing as hackers ethics the similar things about crypto so there was this guy who after Snowden said wait a minute what is the crypto community doing what is the brain cycles of all these brilliant people what are they used for and how can we put them to better use so if you are from the crypto community this is a checklist of the questions that you can ask yourself and try to live up to your own personal ethics by examining it and making conscious decisions about what is your work being used for another example critical engineering another great reference another great website when we talk about ethics so now we come to some even more applied ethics and that is going towards the work function that I do and that is about internet measurements so there there is a group of people who came up together like really made an interdisciplinary team and started from the theory of the applied ethics and this is the most difficult slide for me because like I read so many times their paper and it's really hard for me to deal with this so there are all kinds of types of ethics so consequentialism so the things are good if they are put to good use utilitarianism so if we may make a program or an app that is actually going to be used for some good things then the rest doesn't matter how it was developed what can it be abused for none of that matters because some of the uses that it was made for were good so that's utilitarianism then there is like consequences of the acts and consequences of the rules like yeah we meant it to be used this way and if it would have been used only that way it would have had good consequences but the people who choose to use it for something else then they have to stop behaving in an unethical way and that is one way of looking at the ethics in this consequentialism way then there is the ontology which now I don't exactly know what it is so I'll just skip it and then the virtue ethics like if you're a good person then the things that you develop will end up being good things so you just make sure that you're a good person and it doesn't matter if you work for bad company because you're a good person and so that's how some people explain their ethical position but I'm a good person it cannot be that my products are going to be used for bad things then there is principalism so that's already becoming a bit more practical like okay so how if we want to make sure that our products or our measurements are being used in an ethical way which rules do we have to follow which principles do we have to embed in our measurement to make it as ethical as possible so these are the rules you need to respect autonomy of the participants in that measurement you need to have their beneficence in mind you should try not to hurt anyone and then it should be fair and just so already if you embed only these principles it's already better than just thinking oh nothing can go wrong because I'm doing it for the good reason and finally the best would be to combine a lot of these because it cannot be prescribed like one set of rules for any internet measurement or any software project so you need to look into the pluralism of causes pluralism of ethical principles and try to combine them so again from that paper if you're interested only in internet measurements and you take anything back home this is the summary so they are saying that the internet is not anymore just a technical network it's actually a socio-technical system and we have to consider it as such the power imbalances that exist in building the internet, controlling the internet and the users of the internet also have to be taken into consideration and when involving these users into internet measurements a lot of effort has to be put into obtaining their informed consent and that's hard for many many reasons because people will just click I agree you can write anything in there it's very difficult to so that's one reason the other one is it's very difficult to simplify the explanation of what is it that you're actually doing and what the consequences can be for them to make the meaningful informed consent and so on so there are all kinds of challenges but this is the effort that has to be put in the measurements and then any other technological development before you even start then again, weighting all the risks and benefits before you start the next thing is if you're just using somebody's else's data or it's all there in public anyway it's easily accessible but it was maybe not meant to be used that way so you have to still go through all these checks and ask yourself doesn't matter if it was easily accessible and you didn't put it in there are you using it in the ethical way and not agreeing with somebody else who is doing unethical measurements so there were conferences which actually refused some papers which were based on the unethical measurement principles because they would put the users in danger and the conference organizers didn't want to accept such a paper although the findings were quite interesting but the methods to which those results were obtained were not actually ethical and another flowchart from that paper this is how you actually go around designing such a thing now that's all very theoretical and now we move to the actual practical thing so I will give a very short introduction about what is RIPE NCC, what is RIPE ATLAS and then how did we implement all these ethical principles in RIPE ATLAS but before that how many of you already know what RIPE NCC is? A half, how many of you know what RIPE ATLAS is? It's probably the same group Okay, so very very short introduction RIPE NCC stands for RISO IPE European pardon my French European IP networks and then RIPE NCC Network Coordination Centre now a lot of people say all the time RIPE for short when they mean RIPE NCC but it's two completely different things RIPE is a community of operators in Europe and all these other mustard coloured areas which came together in 1989 to develop principles for governing IP resources and by that also other aspects of developing internet in Europe and those areas and so they get together on these kinds of conferences called or not on the camping grounds and they talk to each other and come up with these common rules like how to deal with the internet and the similar thing happens in other regions now all these five organisations that are listed there not IANA but the other four regional internet registries are like RIPE NCC so there is a community which is RIPE and then there is a company, RIPE NCC that gives out IP addresses to keep it simple these are the IPv6 addresses that we give out so we get a large block from IANA so it's very hierarchical IANA Internet Assign Numbers Authority gives addresses to regional internet registry they give them to local internet registry which is normally an ISP or a hosting provider sometimes a bank, sometimes whatever some other organisation wants to be independent and then they, in case of internet providers they use them for their end user network and so these blocks are distributed that way it used to be the same process for the IPv4 but we ran out of IPv4 so we are now mostly talking about IPv6 and that's the end of the introduction about RIPE NCC now that was the core job of the NCC and what else we do is developing this global distributed internet measurement platform called RIPE Atlas we do that because all those members of the RIPE NCC because it's an association of members they all pay yearly fee to the RIPE NCC and since NCC is not for profit organisation we can't really spend all that money and so we invested into other projects such as this distributed measurement project because we are this central organisation that is trusted by its members then they trust us to collect the data generated by these measurement devices so the device itself, current version is a modified TP-Link router so it's not a router anymore we have installed OpenWRT on it and you plug it into your internet connection in the office or at home and you plug it into electricity and it starts doing ping, trace route and DNS look up to root name servers so DNS infrastructure, critical internet infrastructure so there is about 10,000 of these things hosted by volunteers, people like you and all of these devices generate these very baseline measurements like very low protocol stack measurements and we collect the data and then release the data back to the community we also create some visualisations of it a lot of tools and so on so it's a great measurement network also operated by the community but actually the infrastructure is operated by RIPE NCC and there are a lot of features that I will not talk about and then there are other measurement platforms that we both cooperate with and can be compared with so in 2014 somebody actually looked into all these measurement platforms how can they be used for looking into the interference so detecting if somebody is messing up with a network somewhere globally either for the censorship, mostly for the censorship or just to shut down the whole internet so the two use cases in this paper that were described were the shutting down internet in Turkey or rather redirecting the DNS servers in Turkey and what was the other one it will come to me later so there are other measurement networks and for this talk it is most important for me to see how the ethical principles applied for the rest of them and how they applied for the RIPE Atlas so that is also described in this paper if you want more details so when we were developing RIPE Atlas which was like six years ago maybe six, seven years ago we made some conscious decisions that made this network useful for certain things and actually completely unusable for other types of measurements although people asked us although there is a need for such a thing we decided not to go there and that was for the ethical reasons so what we do is only active measurements so we only generate pings and trace routes and DNS lookups we don't listen to the existing traffic so on one hand this is good because we protect the users from themselves like we don't listen to their traffic but on the other hand we cannot measure the bandwidth speed because not directly, not of your connection then we also decided to have all the tools open source and in some cases also free software API calls are also open and the data is completely available and open we published methodology on what is it that we measure so that other researchers can actually compare results with our analysis results and we limit the set of measurements so that we don't put the users in danger so a lot of people want to measure the web traffic because for the newer generation of internet users the web is the internet we just don't do that we don't actually do HTTP measurements because that would put in danger people in the countries where there is a blockage of the web content and so if you are trying to fetch a forbidden web page then you can get in trouble now something that I maybe didn't make clear is let me go back to this picture so the thing is when you install this thing in your house in let's say Holland the probe itself is not really useful to you it is useful for other people who want to measure how is the internet performance towards certain server in another part of the globe performing from Holland and you get access to all the probes around the globe hosted by other people so basically the building up principle was that of trust so I put this thing in my network I have to trust both RIPE NCC but also I have to trust 10,000 users around the globe that are going to do ping from my probe to a server in Brazil to a server in Saudi Arabia to a server in Africa to a server wherever and so if they do a ping it's less problematic than if they try to fetch a web page from my home IP address in a country where if that web page like is Pirate Bay in Holland well then I might get in trouble but if I ping Pirate Bay okay that's a bit less problematic so this is one of the reasons why we have kept the set of measurements to very limited set and here is the mandatory photo of a cat and this is somebody's probe in somebody's house so we don't want to put that person nor this cat in any danger by doing the measurements which are really geeky and really useful for all of us who want to know how internet performs but it can put the real people and the real cats in real life problems so that was many years ago when we were designing concept of a network what are we going to do and since then well since I was a community builder people kept asking me like wait a minute but why is no where is your source code and I was like oh yeah we are working on it so in 2013 we actually published the source code so now you can examine what it does then in 2014 we thought okay this is we would like to propose that all the measurements that are performed should be made public and then some of the users from the community said no we actually see the value of keeping some of my measurements not public at least not at the same like at real time so we kind of asked the users and they insisted so we decided to allow some of them to be non-public the difference is between the values of openness so having open data like you are paying for it and you should have all the open data and the other value is privacy or even in this case it wasn't even privacy but it was more like troubleshooting value so if my if I'm using right path was to troubleshoot some problems in my network I don't want that measurement to immediately become publicly visible to everybody else but of course it is published anyway in the aggregated data so the value of openness is still satisfied and some people who value privacy they also got their say then in 2015 we actually did implement HTTP measurements but they are not available for random websites so the user cannot actually schedule them but we do them towards some servers that we operate which are called right pathless anchors and in 2016 we hired one of the security companies to do a third party security audit to make sure that there aren't actually any exploits that we didn't think of or any security problems which lead to ethical consequences and so we published the results of that security audit and then this year we went to the rights con in Brussels which was actually quite an eye-opener for me there were a lot of people a lot of advocates of defending human rights using the internet tools and one of those internet tools is internet measurements and so how can we use the internet measurement networks to at least publicize the human rights violations in certain countries where internet shutdown is somewhat considered a human right violation if it is done for certain purposes of oppression and so the people who were there they made this survey and they compared a lot of existing measurement tools according to certain criteria and then they also examined the right pathless and they found out that indeed it does ensure large-scale access so a lot of measurements are possible however and again I said like we don't measure web traffic and then it does satisfy some of the requirements so they have their own checklist and the right pathless actually fits with some of their requirements but then again not with all of them so we also are very friendly with the hackers and so when we started distributing these probes to hackerspaces then they of course opened them and hacked them and examined them they were like oh really that's what you say it does well let me check so they did they checked it and then they reported it luckily first back to us so we have this responsible disclosure procedure available to the to everyone and so if you report it to us we will try to fix it first and then publish it anyway and then thank you for making us aware of this security flaw and there is more probes at hackerspaces and at hacker camps and there will be a talk tomorrow about the measurements between hackerspaces that that are done with the right pathless probes it's called Hackerspaces Jedi we also do hackathons they're a lot of fun we support academics to come to the right community and we also have this publishing platform called RIPE Labs I'm going very quickly through the slides because there's many slides left so at the end of this talk about the right pathless and the right NCC this is my invitation to you to join and to take part in one way or the other so if you are a coder or designer or developer or researcher you can join our hackathons the next one is in November in Copenhagen the topic is IPv6 it's our sixth hackathon then we have a lot of meetings where you can come and meet your colleagues from these communities and have their experiences with them you can join the right pathless community by hosting a probe so after this talk we can go to Cha and you can get one of these probes or you can just use the data so again to make it even more clear the data from these probes is not available only to the probe hosts it is available both hosts and to anybody so it's genuinely open you do need to have an account to download the data there are APIs, you can download things there is a web interface but the data is open so we are also interested in cooperation with other organizations that are interested in using our data how can we make it easily accessible what do you find in the data that you also like to learn from and once you do that then we are going to publish it also on labs.ribe.net and we also publish our software it's on github, especially from the hackathons please use it and improve it and give it back to the community so these are the contact details where you can find me oh I'll take some water so now the next part of my talk starts how do we go beyond the hackers ethics so how do we question the assumptions that we have about the hackers ethics beings about openness about meritocracy about sharing about tolerance about improving the world well one of the assumptions is how does the hacker look like and so it's kind of gray on gray but mostly if you do a search for the image of a hacker and you go to images it's a guy in a hoodie and then if you can see his face it's mostly a white guy in a hoodie and so there is this woman who made a website where you can actually choose all these characteristics and make other images of the hacker just to familiarize yourself with the fact that the hackers actually come in all kinds of shapes and forms and t-shirts and dresses hairs colors drink also other things and not only club mate so this is one of the assumptions about the hackers community that if an outsider comes to this community they will be pretty much reassured about the typical view of the hackers are so this is one of the other separate goals that I have in life is to change this situation and increase diversities of the hackers communities and then I want to plug in the paper of the Allison parish or her presentation which is called programming is forgetting so she described in that presentation that whenever we create a view of a reality we have to discard most of the input that we have in order to create a certain view and the way in which we choose what we keep to create our picture of reality is our ethics is our values is actually embodying our ethics and our values and then she goes on to kind of dissect the hackers ethics and then instead of coming up with a new set of hacker ethics she comes up with questions how can we question the classical hackers ethics and here are some of them so access to computers should be unlimited and total to whom who gets to use the computers who gets to make the computers who is actually making all the equipment that we are all using who is being left out how is the software that you are making hindering or helping the access to the computers that should be free the same for the data all information should be free well to whom who is using it and so on so there is a lot of questions there and in the original quote it also says that hackers should be judged by their hacking and not by any other criteria and the gender was not even there so it also says that the hackers can be from a different background different educational background without degrees without technical background of a different age of a different race in a different position in life mothers can also be hackers mothers are hackers so these are all the questions that we have to ask ourselves every time even if we are hackers and we think we are the good guys or we are the good girls more questions from the paper of the ethics in the network system research which you can access on this website these are all kinds of questions you have to ask yourself before you start measuring things on the internet and then this is to say do not be just utilitarian like if is this app a good thing because it actually achieves a useful purpose how does it do that okay that's a good question but it's just possible questions why did there even come an idea that this app should be in place who is going to use it who is going to be helped by that who is going to be harmed by that so question everything and then question even more things so what other kinds of internet can we imagine one of the possible types of internet is a feminist internet so several years ago a group of people came together and they came up with the principles for the feminist internet so it's at least a good reading material because we are not going to undo the current internet but embedding these values within yourself or even realizing that they exist is a good starting point one of my favorites is changing the way we communicate and that can be done using principles of nonviolent communication or empathic listening empathic leadership and being open to recognize your feelings and realizing that there is space in the open source of development for humans for our emotions for our needs and that is also very much connected with our values and with our ethics so the so called NVC the nonviolent communication by Marshal Rosenberg is in my opinion very suitable for the programmers types because it's quite algorithmical it gives you steps and there are loops where you can get back for a while but then you return with the variable that gets another value into your algorithm and then you proceed from there so give it a try if you're curious about learning another way to communicate and then going to step beyond that is even more empathic build up of the internet and I recommend this book called To Our Friends by the Invisible Committee they are an anarchist collective that few years ago gave a talk at the CCC Congress and so they are talking about redefining what freedom means and moving away from feelings of individual freedom to the freedom of forming collectives and the freedom to create connections with others and even further there is anarchism there is green anarchy there is Buddhism and the principles of Burning Man and principles of permaculture and the ethics of polyamory so these are the things that we can bring into the hackers community to make our community more resilient better and helpful for the rest of the world not only for ourselves how much time? okay so to go beyond techno-optimism I have to dive deeper into techno-pessimism first and to point out something that you all know about mobile phones being surveillance devices and this was actually predicted in the 1982 in the paper do artifacts have politics and so at that time he thought that oh if you ask people to wear a surveillance device they are not going to do it but if you just market it differently if you say oh it's a cool technological innovation then they will go for it well he said it better so everybody would propose that as a political statement people would revolt but since it wasn't political it was made apolitical to have a mobile phone and to examine what do the mobile phones can be used for people actually accepted the surveillance that comes with the cool gadget so the other problems that exist with the current technological level of development are the energy use the violence that has to be used for extracting the resources from nature the violence that has to be used against the people who make those devices and pollution of the environment so these are all the things that are also part of building the internet and then there is even more political statement about the hierarchy and the capitalistic way of how the internet is built and then there is a digital divide so while for some people we get these blue cool data center spaces where all of our data is stored and processed for other people we get pollution and again the violence and the extraction of their homes but there is hope the squirrels are fighting back so this is actually what happened on home four years ago there was a lot of damage to the infrastructure from rodents and for most of the people who actually maintained the network that was a problem but for me that was actually a good thing like yeah now we have to also count on them is this internet actually a good thing for the squirrels why are we only talking about us and humans in the other areas of the world how about the squirrels and we have to count on them in more ways than one because actually they are winning the cyber war the squirrels are apparently the number one cause of most of the internet disruptions at least the US and a lot of power outages too well that actually doesn't end well for them but still we have to count on squirrels and a little bit more succinct way which can be fit on a t-shirt is with great power comes great responsibility we as hackers, as engineers as technical community we now have great powers and we have to take the ethical principles in mind to know how to exercise this great power with the great responsibility and even beyond the internet there are other technologies which some people think lead to the technological singularity some other people ask us to consider the nature of the exponential function so the exponential growth is by definition unsustainable think about it Ursula Legvin on the other hand invites us again to consider a society which would not be focused on the growth and on the endless growth and endless progress but it would be concerned with preservation of the size and the wealth that we already have by going towards the modest standard of living by conserving natural resources by lowering our fertility rate and by changing our politics to go towards consent and trying to fit in our environment and to try to live without destroying the others, without destroying the environment and without destroying ourselves in that process so that can be summarized in these two pictures instead of having the hierarchy of a pyramid or a circle of life or as I like to say there is an Internet of Trees there was an Internet of Trees before we came up with this current Internet of Machines there is Internet of Mycelia and if we would consider the trees and the oxygen as important as Wi-Fi maybe we would at some point still have some oxygen or as this other joke says or maybe it's not that bad and what if we actually do all these changes to cut down consumption to preserve everything and it actually wasn't necessary and we created a better world well, it's worth it so my final words are in these small letters from a nuclear research scientist from his Nobel Prize acceptance speech where he calls his fellow scientists to take responsibility because science became very powerful in influencing lives of all the humans on the world and these scientists were called to take responsibility for the whole of humanity and I'm saying the same way as the scientists are responsible for it the engineers need to take responsibility and hackers need to take responsibility for the humanity we also need to take responsibility for the rest of the life on this planet which for me is symbolized by squirrels thank you great there is 10 minutes left so I would like to have a discussion or questions or anybody who wants to add something but didn't have time to be on the stage or to do a lightning talk 10 minutes so do it on the mic or ask me questions thanks so much for that great talk that was really good and wide and deep and very positive as well so it's also super if you go back to the slide of the pyramid of of internet network no internet networks and capitalism and what it says upper left corner is that you should decentralize and break up with your ISP to build networks well for that you need autonomous systems and isn't that exactly a thing that RIPE has loads of so how do you think RIPE could be part of that work okay politically correct answer to that question is RIPE is a community that is based on itself through the bottom up process so the distribution of autonomous system numbers is based on the policies that are created by the community currently that policy says if you want autonomous system number you ask RIPE NCC and we give you one based on a certain criteria if there is a need to change that policy and to make it easier to get an autonomous system number to make that distribution decentralized or some other proposal it is current policy development process for somebody to come up with a proposal send it to the mailing list it's going to be discussed other people are going to give their input and the final policy is going to be implemented by the RIPE NCC if something that RIPE NCC can decide for example if the policy is we want RIPE NCC to get out of the picture completely then maybe that has to go to the next level which is IANA ICANN which governs how are the internet resources given to the regional registries and if even that is not the right level there is the ITF level which decides about how is the networking done and where are these resources going and in which way so these are three possible steps the easiest one for this crowd is the RIPE policy development process the next one is IANA ICANN and then of course in parallel there is also ITF but you knew all that so I somehow suspect that that's not what you wanted to hear but we can have the discussion later does this answer your question thanks so does anybody have another question for Vanya Basna if not I'll be in the chat then thank you hello thank you for providing this indeed wide and deep framework I'm really intrigued by the metaphors you're using in the last part on say miscellaneous fungi network and the forests and the squirrels as sort of ethical hinge points to remind ourselves of the important questions to ask I was wondering how you balance that in say your official part the politically correct part of the work you do which you can embody some of these values and also there's a more radical potential perhaps there to think of a decentralized network that's perhaps beyond the official roles and titles we take so I was wondering the squirrel on your T-shirt it's in the talk it's there it's accompanying us everywhere as the ethical question is it good for the squirrels if not does this become the ethical grounding for your position do I understand that correctly yes that's a good way to explain it and the other way to say is that I'm not there yet so I keep also reminding myself all the time and questioning is this what I'm doing necessary is it enough what else could I do and one part of the strategy is to make this shared with other people to make it easier for myself to make the step away from the position where I am now towards some other position which I don't know even what that would be but maybe together we can come up with a path forward or path sideways where would that lead for myself it is very hard to think outside of the box because I am in the box so this is one small attempt to give an alternative way of looking at technologies, at values and to spend half of my talk on one topic and the other half and behind the last slide there is yet another talk which I'm not even going to show but if you download the slides you can see where else can that go and then one more thing I was in the many references you gave you were quite concrete about suggesting nonviolent communication as one of the openings to change I was wondering since we have a bit of time could you be able to give a concrete example of what that would mean for the people here at SHA so for the people at SHA the first step would be to educate themselves of what the nonviolent communication is so read the book go to the course watch videos and start implementing a different way of talking to yourself and to others which mostly means people in your team people in your organization and that is going to radically change the way how we deal with everyone but it's a very short time I cannot explain why is nonviolent communication so wonderful it's just very different it's very weird thank you last question hi thanks for mentioning empathy and things like that I think it's very much missing isn't part of the problem of the hacker ethic that it's almost fundamentally against things like mass media and social media and doing analytics and things like this and nowadays it seems that you need that stuff in order to get a word out so you sort of almost need to take the evil pill a little bit do you know what I mean I know what you mean and I would still question that question in a sense that if it is fundamentally against the hacker ethics to use social media as they are currently then who was the person who were the people who actually developed them in the first place so I don't think it is fundamentally against it was just unquestioned and it was actually implemented in the current social media the way how the hackers ethics is because it does give access to computers and to data to us it's just that these hackers are not Facebook and NSA so I don't think there is there is a mismatch there and how can we stop doing that well we need to question our hackers ethics and say if I'm fundamentally against this why would I use it there are other ways to get in touch with people that you need to do things together without taking the evil pill I'm not the one to speak I'm on Twitter, I'm guilty as everybody else here is or maybe more than most of you so we need to come with the solutions together I agree team collaborating is super important so our time is unfortunately up so if you want to talk to Vesna a little bit more you have to follow her to the Shah village give her a warm applause Vesna for your talk


Small and medium-sized or modular reactors are among the most innovative emerging technologies in nuclear power. SMRs, as they are called, are more flexible than larger reactors and have the potential to replace fossil fuel energy sources in a number of applications. National experts met at the IAEA's SMR Regulators Forum to share their experiences in developing regulations for this new technology. Small modular reactor technology and designs have been developing rapidly over the last five to ten years. There are currently in excess of 50 designs available worldwide and these have been developed across a number of member states. Commercial SMR operations are expected to begin in the coming years. Their designs include new and enhanced safety features. This is really the only forum for the regulators to have that conversation about how are we going to determine if these designs are safe enough for our different countries. To assist regulators worldwide, the forum plans to publish documents describing member state experience on the key safety issues for SMRs including design and licensing as well as manufacturing, commissioning and operations. From Vienna, Austria, this is Alejandra Silva reporting for the IAEA.


The NRC State Liaison Officer Program is a program where we maintain effective communications in coordination with local, state and Native American governments. We work to keep them informed on issues and topics of interest to them. We also work to establish good relationships where if they have any questions we work to answer those and in general keep them informed on activities and issues that might impact them. Each governor points a State Liaison Officer. That State Liaison Officer acts as the primary point of contact between that state and the Nuclear Regulatory Commission. That individual can reside in, for example, the Department of Health, Mercy Management or another area. What's important with that individual is that they have the understanding of the state government. The regional State Liaison Officers are located in each of the NRC's four regional locations in Philadelphia, Atlanta, Dallas and Chicago. And our job is to interact with state liaison officers as well as other officials from state government, tribal nations and from local government agencies as well as other federal agencies that have a role in responsibility in protecting public health and safety, the environment and the work. Most of our communications are one-on-one conversations with representatives from the state, federal and local agencies. They can be conversations on the phone, in person or by email. Our activities involve setting up meetings for government representatives to meet with our staff. We also coordinate government participation in public meetings. One of the ones I want to highlight though is the observation of inspections. I established cooperation with offering inspections for state personnel and we have in Region 3 a Pre-I and In-Community, allow them to come in and view or observe inspections in the field. And when people experience that observation of our inspections, they understand our procedures, they understand what we're looking at, they are part of the communications and questions that we have as a regulator and it really allows them to take that experience away and kind of be our advocate later on. I routinely work with state, local, tribal and other federal agencies that are all involved in the emergency response process in doing emergency response planning and participate in routine exercises and drills for those agencies to be sure that we are ready to respond in the event of an emergency. Our job is to provide them with the NRC's independent evaluation and insight into plant conditions so that they can make good informed protective action decisions. Two of the agency's most important goals are openness and transparency and the state liaison officers directly contribute to those goals by ensuring that the federal, state and local government partners that we interact with stay informed about our activities involving nuclear power plants and fuel facilities in their jurisdictions. The program also allows them to have an opportunity to provide input and their thoughts and feedback on issues of interest to them so that we can factor their input into our regulatory decision making. It can be summed up in the ideal that it's a shared mission to protect the health and safety of the public and the environment.


So hello. My name is Sebastian. I live in Bogota. That's the capital of Columbia in South America. You can find me at Sevastoga in Twitter and GitHub. I work for a startup called Ride. We are reinventing the way people commute to work, so you should definitely check us out. Today we're going to talk about microservices.  There's a bunch of them out there. They're really good. You should check them out if you haven't. Today I want to talk about why I think sometimes microservices are a bad idea, and not sometimes, like a lot of the times. So let's start by defining what microservices are. So microservices are like a particular way of designing software, basically. By designing software, we are creating, like, a lot of small applications that can be independently deployed. So a lot of people have discussed, like, is a microservice is just a service-oriented architecture, and it kind of is.  It's just like with a set of, it's just a piece of it with a set of really well-defined rules. And you could say that microservices are a service-oriented architecture. What, like, scrum is too agile, basically. And microservices are not just, like, a new thing that hipster developers like to talk about. There's probably people that have been doing microservices for 10 years. It's just like a name that was given to the subset of rules in the service-oriented architecture, like cloud or definition. So there has been a lot of controversy to how big a microservice should be. So the problem with that is that microservices have a failure by design. And that failure, it's in its name. It includes the size of the service in its name. And it's kind of confusing because, like, micro says that they should be really small. And the size here is not the most important thing. It's just part of what microservices are. But they could have probably been given a better name. So a lot of people like to say that microservices, I mean, that a service can be considered a microservice depending on how much line of code it has. That's, I don't know, that can be confusing. It changes a lot depending on the language you're using probably. Some people say that you can consider a service a microservice based on the size of the team that's building that microservice. For example, in Amazon they have, like, the two-pizza rule. And that makes sense, but I don't really like those approaches. There's another type of approach, which are, like, really arbitrary defined rules. For example, Chad Fowler likes to say that microservices have to be this big.  So if it's bigger, if the code you wrote is bigger than that, it's not a microservice. That's kind of arbitrary. I don't know. I don't really like that definition. So to present the definition, I think that we should all, like, have in mind when talking about microservices, also talk a little bit about cognitive psychology. So there's a concept in cognitive psychology called cognitive load, which refers to the amount of information a person is trying to process at any given time. And there's another concept I want to introduce that's called cognitive limit, which refers to the maximum number of chunks of information a person can process in working memory at any given time. So these are really related. So basically, I think that you can say that a service is a microservice if the cognitive load that microservice represents is lower than the cognitive limit. So let's talk a little bit more about the cognitive limit. So basically, the cognitive limit refers to how much information you can hold in your head at a given point in time. So if you're able to completely wrap your mind around a service, totally understand what it's doing without the need to look into code or documentation, you could call that service a microservice. But you have to keep something in mind. And it's that when talking about a group of people, cognitive limit tends to decrease as the team grows. So basically, the bigger the team, the lower the cognitive limit is. This is a totally made-up graph, so don't look for numbers or X and Y limits. But it's basically, I think, really explains what I'm trying to say. So before we go into more details about microservice-related stuff, I want to tell you a personal story. So that personal story will give us a little bit of context. So the story is about the first job I had. And that job was at Babel Stadium. My job consisted on selling hot dogs on game days, and it turned out I was good at it. So my manager asked me to also sell phone fingers. So it went okay. But when my manager asked me to make some public announcements, I mean between innings, it sounded a little crazy. But okay, I now had to also do that somehow. Weirdly enough, I was able to do all of that. So my manager asked me to moan the law before each game. So I was basically doing that also too before each game. Surprisingly, my manager lost an employee. So he asked me to help him accommodate people on their seats after moaning the law and what people was like getting into the stadium for the game. By the way, I'm sorry I couldn't find like a better image of a ticket in the Internet and I had to use one that's like for one direction. So because things weren't bad enough already, one direction showed up for the game and I had to accommodate them. That was definitely my last day of the job. I had to quit. Okay, that's the story. I don't know, but probably by this point you already realize that this is not a true story. I'm just trying to make a point here. So in that order of thoughts, I want to ask questions to everyone. Please raise your hand. If you have a system that's probably going over your team cognitive load and you want to break it up, break it down into other systems. Okay, cool. Thanks. So this is not uncommon and this happens a lot. We're going into this situation when we have a monolithic application. So the HH talked about this earlier today. And I kind of disagree with his concept of what a monolithic application is. So let's look at it a little bit. Let's look at it basically. So I think that like a single-rails application, like having a system basically that's a single-rails application doesn't make that system or doesn't make that application a monolithic application. So what makes a single-rails application a monolithic application is basically poor object-oriented design. So let's like separate those concepts. Given the fact that your system is only composed but one Rails app doesn't make that Rails app a monolithic. A single-rails app can be like well-designed and well-built. And there's actually like a talk that was given recently, I think on moving your nails, but Akira Matsuda, where he gave a really, I mean, which was really interesting and he talked about how Cookpad, which I think is a Japanese company, what's probably the world-largest Rails application. He gives, on the talk, he gives like really good insight of how he achieved it and like the amount of traffic they can handle with one Rails application that's like running on, I don't, I might be lying, but I think it's like 300 servers. So if you have an application, so although like I think they probably like do too much to keep their system being like a single-rails application and I don't know if I will go to that extent, you could do it. And if that's the way you like to roll, that's fine. And that doesn't mean that your application is a monolith. So you can call the integrated systems you want. That's fine. You can give it the name you want to them. But let's be honest, a monolith doesn't look like this. What's that? A monolith really looks like this. That makes more sense. That's how a monolith looks. That's how you feel when you're working with a monolithic application. When you're working with a monolithic application, you probably, you normally like can't reuse a part of your system without basically like reusing the whole system. Or you can like easily change the flow without having to do shotgun surgery, which is really bad. So now like, that we know like the difference between what's really a monolithic application and what's not, when should you go for microservices? I don't know. Let's think a little bit about it. It's an interesting topic. So should you go for a monolith?  That your single rails app is no longer a well-defined app, but it's like monolith? Well, I would say no. This is a fallacy that a lot of people believe in.  That's all you get. So the fact that you have a monolithic application doesn't mean that you have to go for microservices. I found this on Twitter, which is something I really like, and basically says that if you can't correctly design a single application, you won't be able to like design a microservice, or assist in that space based on a microservice architecture. And I totally agree with that. You first need to be able to nail a single rails application before thinking about even going for microservices. So when should you really like use microservices? I mean, it's clear why not to, but so when should you do it? So one good reason to go into that direction is when you have a part of your system that needs to be escalated differently from the rest of the system. So this has happened to us on RIDE where we started with a kind of like a brain application that was coordinating a lot of things, and we realized that some parts of that system needed to have a better performance. So we had to deal with the decision of do we want to scale the whole like brain application, which is wonderful for microservices? Or can we like just extract this and escalate it differently because that's a specific need for this? So this is a really good reason to go towards microservices. Another one, it's when a part of your system needs to be easily replaceable. So what happens when you have monoliths and what has happened, like in a lot of really big companies that have been producing software for a lot of years is that some systems are like 20 years old or 10 years old, are built on languages that probably no one in the team at a given time knows how to write code in, and it's running on a server that hasn't been touched for a lot of years, and no one wants to change because they're really scared about breaking stuff. So when you have stuff, I mean, when you have like your business logic basically spread in different small microservices, this is really difficult for this to happen because if you have a microservice that it's failing, it's not scaling as it should, it has a bug or whatever, and it's not technology on a server that no one in the team understands, you can easily replace it. Just building in whatever language you want, in whatever you think is best, and replace it. And you don't have to replace it right away. You can do it gradually and testing and every step that the new service will really be able to replace the old one. And this is really cool. This is great because you don't need to do a big rewrite. You don't have to throw the 20-year-old service to the garbage and start from scratch and probably create all the bugs that were already fixed on a huge application. Okay, so let's talk about another reason, like when you should think about going for microservices. And this is when you want to be able to deploy some parts of your system more often than others. And this is really common. Like when we have a big Rails app, you notice that there's some tools that actually allow you to check this. And you notice that there are some parts that have a greater churn. That you're changing all the time, probably because business logic is changing a lot, probably because it's harder to understand. So there are a lot of bugs on the specific part. It can be also because, I don't know, there's a lot of reasons. But sometimes you have to change parts of your system more often than others.  And this costs a lot. And also, the bigger the app, the more you're afraid to deploy it to production. So you tend to accumulate more changes for each deploy. And then when you accumulate a lot of changes for each deploy, there's a lot of more possibilities of a deployment to go bad than when you just deploy constantly smaller changes. So when this happens to you, it's also a good idea to think about microservices. Okay. So another reason why you should look at microservices is when you don't want to use the same technology stack for every part of your system, you have to be aware that this can be taken to an extreme. So there's a blog post out there by some cloud, I think, where they explain that when they moved to a microservice architecture, they allowed anyone to write a new microservice and any language they wanted to. And this ended up being a huge problem for them because there were microservices on basically any living language out there, any language that was still under development. Everyone wanted to learn a new language, so they basically created a new microservice on that language, which can be really cool, but can be also really hard to handle. So, for example, at Ride, what we do is when we need to create a new service, whoever is going to work on it or whoever is going to be responsible for it, basically creates like a proposal and says, okay, I'm going to create new microservices. This is like a contract, it's responsibilities, and I want to use this stack stack to build it. And then we open it for proposals, sorry for comments. So we do an RFC, a request for comments. Basically, everyone in the engineering team has a period of time when they can give feedback on that proposal. And that feedback is on design, too. It has to do with the business value that each microservice adds to the whole problem we're solving, but it's also around the technology stack we're going to use because the whole team is going to be responsible for maintaining that new microservice that's going to be created. So we probably want it to be bringing something that makes sense for the problem we're fixing, but also something that we want to maintain, something that we think makes sense and that it's not like a new crazy language, something someone just wants to learn and experiment with. So that's called technology heterogeneity. I know that word's confusing to me. So last but not least, the most important thing is that the team that's working on building your system has to be ready to support this type of architecture. And it's key. I mean, this is really important and it's what a lot of people moving towards microservices miss. The skill set of your team has to be ready to support what moving to microservices means, which we'll talk about a little bit further during this talk. And also, the team has to be big enough to be able to work on different services on a distributed, basically on a distributed system. And sometimes people overload a really small team with this type of architecture and that's when they start to see a lot of problems with it. So you have to be really aware of this. So how do you know if your team is ready to go towards some microservice architecture? There's basically three things that are key. The first thing is that you have to be able to easily provision new servers whenever you need to. The second one is that you need to be able to set up basic monitoring for every new microservice you create and the existing ones. And also, you need to be able to respond to failures that are monitoring the use set up decks. And last, as you mentioned, is that you need to be able to rapidly deploy new applications. So if you have a new microservice that you need to get into production, the team should be able to get it into production in a few minutes, not a few hours, not a few days, not a few weeks. So that's really important. If your team is not there yet, you're probably better off not going towards microservice architecture. So now that we, let's say that your team is ready to handle all of this, which is great. You could say, okay, I'm ready. Let's go for microservices. I really love the idea of it. I think we give it a really long time and discuss about it. So let's do it. But you have to consider the downsides of it. And they're not trivial. So let's get to, let's see what like the most common downsides of microservices are. So first of it is that DevOps intensive. So as I mentioned before, teams need to be good DevOps, need to be ready to support a lot of services running all the time. And this can kind of be mitigated by using a platform service, which will probably do a lot of the work for you. And that's good. If that's the way you say to go, I think that's fine. Another downside of, I mean, more than the downside, that's like something you need to be aware of. But let's talk about this. So you will have log files for every service that's running. And this can make really, I mean this can make debugging really complicated and hard. So you need to have a centralized logs for your whole system so that you can like watch what's going on there. And also something that's really important is that you probably want to have unique identifiers for every request that's going throughout your system so that if something goes wrong, you can easily trace it and figure out when word thinks are going wrong and how to fix them. This is really important, believe me. So another downside of microservices is that you have to be prepared for failure. So I know, I mean this is not, this is something that you shouldn't only worry about when you have microservices. Like you should also be prepared for failure when you have like a single app, if it's Rails or not, it doesn't matter. But the thing is that when you have microservices, this is harder to manage. You need to have a lot of more stuff into consideration to be prepared for failure. So let's look at what are the most common failures when you are dealing with a microservice architecture. So the first one is network practices. So this is something that will inevitably, you, I mean, sorry, this is something that you will inevitably have to deal with when working with distributed systems even if they're not microservices. So this is really important because there's no such thing as a network that doesn't fail or services that never goes down. We all know that sometimes, like, sometimes these things fail. So we need to be prepared for it. So for example, let's say we have a system that looks like this. And let's say that communication between node or service A and B goes down.  So node A has to decide between basically two options. Node A can respond to the client telling them, like, hey, there's, like, something wrong going on. I can't really process your request right now. Or node A can also say, okay, I'm going to deal with this. I'm going to respond to you something. And then I will internally deal with the consequences that having null communication to node T will bring to the system. So this is something that's not trivial and something that you need to plan ahead of. Okay. So the thing is that this is not the only problem. You can also have services that are sometimes unavailable. So even if you have the perfect network that never goes down, services will eventually be unavailable. So there's a formula for this. It says that basically, like, the probability of a failure occurring on your system is equal to one minus the probability of a node or service not failing forward to how many of those are. This is, like, wow. I don't know. It's complicated. When I first saw this, it was really, like, hard to get my head around. So let's just see an example. Let's say you have a bunch of microservices, all of them have an uptime of 99.9%, which is great. But you have 40 microservices. This means that your system, applying this formula we just saw, yeah, this one. The system will have an availability of 96.1%, which in other words means that you will have around 4%. I mean, like, most of the time you have a probability of a 4% of something going wrong in your system. And this is only considering, like, that if a node fails or a service fails, only that service will fail. But depending on how you design your system, if a node fails, a lot of other related fails can fail, too. So this can get really bad. You need to be prepared to handle this type of failures. So let's look at another one. That inconsistencies. So when the network is partitioned or a service is unavailable, they will most probably, this will most probably cause data to be inconsistent. And this requires planning. You need to know how you're going to deal with this so that data is eventually consistent. Or if you don't care about consistency, like maybe even, like, how to deal with this, how to deal with data not being consistent in your system. And this is not trivial because it can really, it can really make your system, like, not work as it should. Okay? And, like, these two problems we just talked about are basically part of something that's called the CAP theorem or CAP theorem, which talks about, like, dealing with this type of failures in distributed systems and really explains, like, not only how they can affect your system but also probably how you can deal with them depending on your business requirements. That's the most important thing. So basically, CAP stands for consistency, availability, and partition tolerance. And when you have distributed systems such as a microservice architecture, you have to deal with partition tolerance because your system is partitioned. It's not something you can choose off. But you have to balance how to be available and also, like, have consistency with data at the same time. So this is really important if you're thinking about microservices. If you haven't heard about the CAP theorem before, you should really read about. I really recommend it to you. It's really interesting. But this is a topic big enough to do another talk about it. So let's talk a little bit about, like, what to do, like, when you want to build microservices. Let's say your team is ready. You can deal with all the downsides of it. You're ready for it. So how to start? So first of all, when you're trying to break a big application into small services, use the bounded context pattern, which basically deals with large models by giving them the ability to have specific behavior based on their context or the context they're on. So like in this image, you see that we have the customer model and the product model in two different contexts. One of them is, like, the sales context and the support context. Depending on the context, each of these models is, they will probably have a different behavior and you'll probably want to have access to different data that's related to it. Check it out. It's really useful. So also, something you really need to do that I found is really useful, it's having a specification for each microservice and being able to run that specification as an executable test.  So one way you can handle this and make it easier to work with is by having specs that you can run as an executable contract. So that when you test each microservice, you can test it again, that executable contract and make sure that when everything's running together, when everything's deployed, it will work fine together. And you won't, like, only realize you have bugs until you go to production, which is really bad.  This is something you really need to do that will save you a lot of headaches. So you should also be aware that you should go for a synchronous communication over synchronous communication whenever you can. This will make you make it easier to deal with any type of failure, the type of failures we just saw the cap theory and talk about. And another thing that I found really useful and that we've learned in Bride is that you should use schema-based formats over schema-less ones. So there's, so, like, to give you a little bit of context, for example, like, a schema-less format is JSON. And a schema-based format can be protocol buffers or Captain Proto or, I don't know, there's probably a bunch of them outside, out there. So the good thing about this is that schema-based formats allows you to extend data that you pass between systems as you need to as your system grows and changes.  And this is something that's really important and we'll talk about something called the golden rule of microservices in a few minutes. So what should you do? Just start. Create a new microservice when you need it. Be aware that the perfect is the enemy of the good. So you don't need to have the perfect design before going to microservices. Just start and you'll be afraid to reiterate on your solution. So what shouldn't you do now that we know how to do it? So it's really important that you don't share databases between microservices. Sharing databases is like calling another object private methods. That's really bad. Something you don't want to do is solely ranking encapsulation. So don't do this. There's a lot of ways around this. And if you're doing it, it's probably because you don't want to think hard enough how to fix the problem. And if you see yourself in a situation when you temporarily, hopefully, have to deal with this, just make one microservice in charge of writing to the database and the rest of them just reading from it. But still, you'll have a lot of coupling because if the schema changes, all of these microservices that start reading from it will have to change too. When you share a database, you'll feel like this. You'll feel like you're moving on dangerous grounds. So something we saw before today is to avoid being biased by Conway's law. And this is basically... This law was coined by something that Marvin Conway coined at a point, say, in 1968. He said that organizations produce systems whose design is a copy of the structure of the organization. So you should be really aware of this and not try to just replicate the way your organization works into how your system works, because that's probably going to... that's probably going to have you creating microservices you shouldn't or designing them the way you shouldn't. Most importantly, don't break... I've mentioned it before, don't break the golden rule of microservices. And this basically says that you need to be able to deploy any service anytime without changing any other service. And this is not trivial to achieve. Because if you fail to achieve this, you're losing most of microservices' benefits. If you find yourself in a position where you are doing lockstep deployment, when you have to deploy more than one service at a time so that the system doesn't break, it doesn't really make sense to have microservices. It doesn't really make sense to have things that you should be able to deploy independently, change as much as you want without the rest of the system knowing. So be aware of that. If you find yourself in this situation, you have to fix it real quick or maybe think about going back to a single big application. So to rub everything I've been saying up, I would like to bring two quotes by Michael Feathers. And the first one says that he strongly believes that there's a lot of complexity conservation software, which means that, for example, in microservices, we need to be aware that when we go towards that direction, we're pushing complexity into the interaction of our services. And we need to be prepared to deal with that. So my recommendation is go for microservices if they allow you to better manage the complexity of the system that you are building. That's all I've got for today. Thanks a lot.


Ευχαριστώ για να σας δοκιμαστείτε. Είναι Vicky εδώ και σήμερα θα σας δοκιμαστείτε 8 δεύτερες καρδιά χρησιμοποίησης χρησιμοποίησης από την τελευταία εργασία μου από τα τελευταία μου. Για την πρώτη καρδιά θα χρησιμοποιώ αυτή η αδερφότητα, η οποία είναι called Space Explorer και θα σκοτήσω αυτό το μικρό μου, ο οποίος σκοτήσει τα τρεις καρδιάς. Τώρα θα σκοτήσω τρεις πλανέτσες. Και θα σκοτήσω όλα τα φωτιά μου με τα αλκοχόλια μου. Of course, at this stage you can use your favourite colouring medium. After colouring everything, I'm going to use the matching dynamic set and cut out images.  For my heart base I decided to use a black heart base, a black licorice card stock by my favourite things.  Το πιο πιο δύσκολο θα χρησιμοποιήσεις. Και εγώ really like how random they look and how you get teeny tiny splashes and a little bigger ones. Now that my sky is ready, my space is ready, I have cut out this stitched rounded rectangle and I am going for a shaker card. The truth is that you don't have to do this step, you can just stick all the images on top of the space that you have already created and you get done with it. But I wanted to take it a step further, so I am going to create a window out of this frame.  I am using my Nuvo Glupin at the back of the planets and sticking them on my space. I am also going to add some diamond dust at the center of that space just to add a little bit of something to move inside my window. And then I am going to stick the frame on top. Another idea is to cut out little stars and stick them inside the window so they look like falling stars at the sky. Now I am going to stick my little astronaut at one corner of my frame. And the outside of my card is pretty much finished, I am just trying to decide how he is going to go there. And on the inside I am going to stamp the sentiment. So for the sentiment I am going to use one of the sentiments from the same stamp set which is all about birthdays. I am going to stamp it with VersaMarking and then white emboss it. So I am preparing my cardstock first with my embossing tool which removes static electricity. I am going to stamp the sentiment, apply my white embossing powder and the one I am using is by Nuvo by the way. And then I am going to use my heat gun and melt the powder. And that says Mission Control will have a birthday. Now to finish it off on the outside I am going to add some glitter on the stars. And my first card is ready. For my second card I am using the Fancy Flowers stamp set. So I am going to pick up some flowers and some leaves, I am going to stamp them. And I am going to stamp them with Archival ink which does not smudge or smear when you use watercolor. I am going to stamp everything on watercolor paper on the smooth side. And then I am going to use my new Nuvo Aqua Flow pens to color everything. So to color the first flower I am going to mix two different watercolor pens, the red and the pink. Now if you want to see a more detailed video on how I am doing this technique with my Aqua Flow pens you can check the video that I have posted last week. The Aqua Flow pens are by Tonic Studios. They are already available in Europe and they will be available in the US really soon. And as always you will find a full list of all the supplies that I am using today down below in the description area as well as on my blog. So check that out.  And I end up having those beautiful flowers in a watercolor look. I love how bright and bold they are. Now just because I had on my table that black licorice cardstock that I used for my previous card I decided to stick those flowers on top of that just because this is going to help them pop even more. So I have cut out this rounded rectangle frame and I have placed it temporarily on top of my card base and I am going to stamp the sentiment. Now for the sentiment I am going with one from the Boss Babe stamp set that says design a life you love. I am going to stamp it with VersaMarking and then apply white embossing powder and heat set it. This way I have a bright white sentiment on top of my black cardstock. And by placing temporarily that white frame on top of my card base I made sure that everything is nicely aligned and centered. Now my sentiment is ready and it's time to assemble my card. I have already glued down the frame and now I am going to stick down the flowers and I am using some foam scores at the back to add a little bit of dimension. I am going to decide where everything is going to go and then I am also going to stick the leaves underneath the flowers. If you love coloring I think that this is a great set for you because they have nice white open areas to color with your favorite medium. So I have stuck down all my flowers and my leaves. My design is pretty much finished. I am just doing some finishing touches with my white gel pen. And of course this is totally optional. I just like to add some highlights sometimes. And for some finishing touches I am using my white crystal drops by Nouveau to add some dots.  And of course you can add a sequence instead or animal dots but I really like the look and feel and the dimension that my Nouveau drops add on my cards. So this is the finished card. And on the inside you can stick a white paper to write your sentiment or you can write with your white gel pen. And let's move on to the third card for today. And this is the perfect friend, some set by my favorite things. I have chosen to stamp the card with the flowers on her body. One of the cages, a little birdie and a couple of hearts. And I am going to use my alcohol markers to color everything. Now in these types of videos when I am creating 10 or 8 cards I never stop for you to see how I color everything otherwise it's going to take hours. So I am just going to move it forward where I have already colored everything and I have used the dyes to cut out all the images. The red cardstock that I am working on is by my favorite things. It's the red hot cardstock and I have cut it a rectangle which is slightly smaller than a standard card. So I am going to stick everything there. For the cage I am going to cut out a white and red baker's wine. I am going to place it at the back, secure it at the back with a foam square.  Now the truth is that this is quite small and it's not going to show too much at the end. Once I stick the sentiment but it's still there and it adds a little bit of texture. If that panel was bigger you would be able to see more of that wine. So anyway I have secured that there. I am going to stick the little birdie on my cage and now I am going to stick the little hearts. I wanted to have a big bold sentiment for my card so just because this is a red card I decided to do the sentiment white on top of black. So I am stamping the sentiment from the same stamp set that says you are the perfect friend. I am stamping it with my VersaMarking and then I am going to apply my white embossing powder. So this is my card base. It's again made out of red hot cardstock by my favorite things and since I want to add something interesting at the background I decided to stamp this floral background by my favorite things. This is from the previous release. I have stamped it with VersaMarking. I am going for a tone on tone look here and I am going to emboss it with clear embossing powder. So I am going to heat set it with my heat gun and I will end up with a background with lots of detail but at the same time it's very subtle. So I am going to stick my panel on top of my card base and you can see how it looks. Now for the sentiment I am going to cut out a fishtail on one end and I am going to stick that on top of my panel by using some foam tape at the back.  For my next card I am using images from the Farm Friends stamp set which is just adorable and I am going to stamp some of them in white cardstock color them with my alcohol markers and then die cut them with the matching dies. So I used a couple of trees, the wagon with three guys inside, a little birdie and now I am going to do all the coloring and it doesn't take a lot of time to color all those images but just because they are so tiny I didn't do a lot of shading. So it was quite quick.  My card base is by my favorite things, snow cone, color cardstock and I am also going to use this green which is the sour apple green by my favorite things again. I have cut out some slopes and I am going to stick one on top of the other. This way I am going to create my little scene.  I am trying to decide where everything is going to go before I commit with the glue and now I am going to use my tape runner and stick everything down. I have also cut out a few clouds, I am not going to use all of them but they come from a die that was released in the previous month and it was called Cloud9 I believe. You will find links to everything I use down below the description area. Now I am also going to stick that little birdie and I like how he is following everyone and I will continue assembling my card by sticking down the trees and the clouds. I have cut out a banner but those dies that were released in a previous month I have used them so much and I think that they are one of my go-to banners for stamping and adding my sentiments on my cards. So now I have stamped a sentiment from the same stamp set from the Farm Friends stamp set that says it's all more fun when we are together. A quick and easy design that you will see I am going to repeat for the last card. And this is not actually a card but a tag but I have cut out the wine tag twice and I am using the wine glasses from the Wine Service Dynamics set. I am going to decide where everything is going to go, secure them on top I am going to place one tag on top of the other and make sure that I round them through my CISIX machine at the same time. So those wine glasses cut out through both layers. That's why I am running it more than once just to make sure that everything is cut out all the way. I am going to pop out all those wine glasses and for this wine tag I am going for a very sophisticated let's say for a very clean and simple look just because I want this to work for any occasion. This is a great way to decorate a bottle of wine that you give us a hostess gift or for a birthday or for any occasion really. So I am placing some tape at the back of my tag and I am going to cover up those glasses with acetate So from the front they are going to look as if it's glass nice and shiny and transparent just like glass and I am going to do the exact same thing on one side of the other tag so I will end up with two tags that have acetate at the back and now of course I need to add red wine inside my glasses so I have cut out a strip of red paper which I am going to stick at the back I am going to cut off the excess and now I am going to sandwich one tag on top of the other so both ways are good ways so there is no front and back on this tag just because this is going to be a gift I just want it to be perfect I am going to make sure that I add enough glue all over the inside of my tag and then very carefully I am going to line the map making sure that I match perfectly and all I have to do now is to stamp the sentiment and this comes from the uncorked stamp set clean and simple and I really love it So here is a photo on how it looks on top of a bottle For this card I am working with the FrenchFourEVER stamp set which is full of teddy bears and I have chosen to stamp one that has his hands open as if he wants to hug you I have stamped my teddy bear on craft paper and I am doing the coloring with my Prismacolor pay sales and I am switching from one medium to another like I am doing watercoloring or alcohol markers and now Prismacolor just because I get bored to use the same coloring medium again and again and I like to give some love to my supplies So anyway I am going to color my teddy bear and of course you can use your favorite coloring method and I am planning to stick this teddy bear on top of this white panel but just because this is very plain I decided to add a little bit of color and I am using pink for my background just because pink and brown are a great combination together Now in the beginning I thought I would stick this panel and the teddy bear on top of this chocolate cardstock but then I changed my mind later on and you will see that I will change the card base So I am going to stick the teddy bear using one of those wobbles These are springs that help your teddy bear move and as if he wants to give you a hug I think this is really adorable I have cut out a banner This is cotton candy cardstock by my favorite things and I am going to white emboss the sentiment that comes from the same stamp set The sentiment says I can't wait to give you a squeeze and I think it matches perfectly the little teddy bear with that wobble that moves up and down Now I am going to hit set my sentiment and of course for my card base I decided to use the exact same cardstock that I used for the sentiment So everything is cotton candy now I am going to add some foam tape at the back of the sentiment and then stick that banner just below my teddy bear Very simple design but really adorable I have also punched out a tiny little heart which I am going to stick on top of my teddy bear and again the heart is the same pink cotton candy as the rest of my cardstock Now to finish it off I am going to use some glitter on top of my little heart and I am going to use my black nuvo drops on his eyes and his nose Now for this card I am going to stamp the sentiment first So I am using one that comes from the lots of hugs stamp set and it says sending hugs across the miles I have stamped it at the very bottom of my panel with black ink and then on top I am going to die cut the word hugs So I am going to place it nice and straight I am going to secure it temporarily and then run it through my Cezix machine and I end up with this beautiful panel for my card Now this is called sketched blooms and it is a layering flower set but there is a line that combines the flowers that go together So it is really easy to recognize which goes with which one So I am going to stamp some of them coming out of my hugs die cut and I am going to stamp the stamps and some of the flowers You can pretty much use many colors and create a colorful garden I decided to go with just one color for my flowers and I am going to play with my my favorite things ink cubes and all those stamps and flowers and meet you back once this is ready Now I have finished all my stamping and I am going to add some details and I am going to use my white gel pen to add some white details on the center of my flower the big flower there as well as the little yellow ones So I am giving them a white center and I am also going to add some dots These are the same yellow dots as I did the flowers I am going to do some highlighting with my white gel pen Just some finishing touches These are not something that you have to do I just like to do it and sometimes I cannot leave a card alone I always have to add more details Now for my card base I am going to use this Russell Berry cardstock by my favorite things that matches perfectly my flowers and I am going to make a note on where that die cut falls and this is where I am going to cover up the back with my tape this adhesive tape and I am going to make sure that I cover up all the backing I am going to check again and now I am going to peel off that adhesive and apply some glitter This is glitter by Nouveau and I am going to show you how you can do it mess free You see I haven't touched the glitter at all at this point I am going to place that backing on top and burnish with my bone folder the glitter to make sure that it sticks nicely on top of my adhesive and now I am going to place that back inside that jar I hope you can see how shiny it looks and just because I have that glitter there I decided to add some on top of my flower so I used my Nouveau pen there glue pen and it sticks on my flowers only where that glue pen touched and this is what I do for a mess free and glitter free table so there is no glitter anywhere now I am going to add some foam tape at the back and stick it on top of my card base and I hope you can see how shiny it looks For the last card I am going to stamp the little girl from the Pure Innocence Happy Together stamp set I am also going to stamp the sentiment from the same stamp set that says we make a great team and what I love about my favorite things stamp sets that come up every month is that you can combine them together so I am going to combine the little cow from the farm friends stamp set as well as that little tree and I am pretty much going to recreate a card that I created earlier where all those farm friends were in the valley outside in that little scene so again I used the same cardstock for the background I have cut out those hill sides and then again I am sticking them one at the back of the other so now I can stick the little girl on the front I am adding some foam tape at the back and just because I don't want her to be alone there I am going to give her some friends so I am adding a tree at the back and I am going to add the cow and of course I am going to add some clouds at the sky so mixing and matching many images from different stamp sets can give you the ability to create many different scenes and this goes perfectly well with the one that I created previously so you can pretty much make a whole set of those cards I am going to stick that panel on top of my card base and my card is finished and now let's take a quick look on all the 8 cards that I have created using the February release by my favorite things CREATE 8 is going to come back next month where I will be featuring the March release by my favorite things and take a look at what great set those two cards make together so these were the cards for today I hope you had fun and got inspired and if you did don't forget to leave my comment as well as give me thumbs up on my youtube channel and if you need more inspiration there are 2 more videos where I am creating 8 cards featuring the December and generally release by my favorite things thank you all for watching


He came and tried to get credit from the authorities. His sonness he cried but killed 12 young boys in a photo of his own son. He raised a kuinf pig with freight timer in universe. He said in a phone that his boy is old. ڈاطر difficulties, ڈاطر dumplings and hurricanes. ڈاطر fights, ڈ Acts of brothers and sisters. ڈاطر fights, ڈ crashesount, ژلyss 來 and plunder the cap. ڈاطر comeipadelous morning for this long, ڈatt coma, ڈattr stuff, ڈattr pick could either wave my life sa give me the magnificentLooks. ڈат 모습, ڈетр prer towards buttoufresand, ڈاط runEEP do neither attack my wife nor talk back. ڈاطto berries, ڈ MASTER BIRDA. ڈА topic sahips is very high. Caimpo deeply dulak, ڈα jumps on it needed incident. Caimpo dig and gets crazy. గా రడిటికమనాకాఆ side మ Jup achine in various countries where you every need to do fitness pure touch after introducing those kinds of exercise .  Floydardi  ಂರ Energie  launched in Inverness ostat  Noble Parwar глаз éraa దాచిక蘭త ధిన Scientists said that Tak وئาก Glück ڐ 그래  twee  कि नगी पुज री Ng πия दा उवर सार कसी च्वल लोत,  अव Java ना � Dot ना ब्दामा थे पुषा कर दे ल मुझाब। भस जकिि तिप, सक्चव प्ारों एक शमाजग ऴूसकनun군 अगटी Stay koi bhau racra hastaab chillik anga रो pilot countdown Ji