Welcome learners, I am Dr. Smriti Sikhasothri of Krishna Kanto Handic State Open University. Today we are going to discuss on business research methodology which is a core course of MBA program and today I am going to discuss the first unit of the course that is Introduction to Research and this is the first video lecture of this unit. So in this video lecture we are going to discuss about the concept of business research like why we need to do research and this video lecture that you need one. This is divided into two parts, one is your meaning and concept of research in business and types of research design that is exploratory and conclusive research. So in this video lecture we are going to discuss this part two portion and in another video lecture I will be discussing a process of research and features of a good research study. So let us start first we should know why we need to do research. So research means searching for some information facts, research is one of the most important aspects of any field like in any management field we can say whether it is marketing, finance, HR, any field like we need to do new and new research to upgrade ourselves. So like there basically we can say like in research we do problem identification and problem solving. So business research is a systematic and objective identification then collection analysis, dissemination of information and use of information for the purpose of improving decision making related to the identification and solution of problem and opportunities in the field of management. Suppose for example a marketer wants to launch a new product in the market. So like before launching the product he or she needs to do research like what type of product customer prefers then what price will be suitable for the market all these things we need to like do the research and then based on our research finding we can launch a product. So business research involves the identification of the information then collection of data analysis of data then dissemination of information and use of information and we define or like we define the business research problem or opportunity and then determine what information is needed to investigate it. So here I am showing you the different process of business research like first is your identification of the need or the problem we say then collection of data. Data we can collect either through primary data collection that is going to the field and collecting the data or maybe from secondary sources like whatever literature is available from that we can collect data. Then we analyze those data and then from that analysis of the data we interpret that okay data like into some feasible solutions for our study and then we use this information in the field of business. So we will be discussing all these details in later part of our video lectures. So basically there are two types of research design one is your exploratory research and another one is your conclusive research. So first we will discuss what is exploratory research. The primary objective of exploratory research is to provide insight into the problem confronting the researcher. So exploratory research is used in case when we must define identify relevant courses of action or gain additional insight before an approach can be developed. The information needed is only loosely defined at this stage and the research process that is adopted is flexible and unstructured. So while doing exploratory research we generally do some kind of unstructured and flexible research. Suppose we are exploring something for the first time that is that kind of research is known as your exploratory research. For example it may consist of a personal interview with few industry experts then the sample selected to generate maximum insights is small and non-representative. So suppose we have collected the information from this personal interview and then based on that study we might go for a concrete systematic research. So the primary data are qualitative in nature and are analyzed accordingly. Given these characteristics of the research process the findings of exploratory research should be regarded as tentative because we are exploring something new and it is like your non-structured or maybe semi-structured. So exploratory research just provides us some sort of framework for the conclusive research. So now we will discuss conclusive research. The insights gained from exploratory research might be verified by conclusive research because the objective of conclusive research is to test specific hypothesis like whichever we formulate for our study and then examine specific relationships. This requires that the information needed is clearly specified. Conclusive research is typically more formal and structured compared to our exploratory research. It is based on large representative of samples and the data obtained are subjected to quantitative analysis. The findings from this research are considered to be conclusive in nature in that they are used as input into managerial decision making. So conclusive research designs may be either descriptive or causal. So here in case of conclusive research we can say that it is more structured and formal type of research. Based on like in conclusive research we already have got some tentative picture of the research and based on that we will set our hypothesis objective and based on that we will do conclusive study. Some conclusive study can be again are subdivided into two types. One is your descriptive research and another one is your causal research. Now first we will discuss what is descriptive research. The major objective of descriptive research is to describe something usually the characteristics of relevant groups such as consumers, salespeople, organization or market etcetera. Many of the business research studies involve descriptive research which makes use of service and observations as major method. So in descriptive research what we do we describe certain kind of relationship like whether there is correlation between suppose consumers and salespeople or suppose consumer buying behavior and sale of a mall any kind of relationship when we are going to study we generally use descriptive research and under this descriptive research we use different types of survey methods then observations and for that we administered some structured questionnaires which I will be discussing in our next video lecture in details. Then we will go to the causal research. So causal research is used to obtain evidence of cause and effect relationship. Assuming managers continually make decisions based on assumed causal relationship. These assumptions may not be justifiable and the validity of the causal relationship should be examined via formal research. Like descriptive research causal research requires a planned and structured design. While descriptive research can determine the degree of association or correlation between the variables. As I have already said suppose there are two or three more variables and we will check whether there is any kind of association or relationship between those variables that is the part of our descriptive research. But in case of causal research what we do like we examine the causal relationship whether like one variable is the cause for the another variable. Because the sales are increasing so we need to examine why sales are increasing whether advertising is one of the reason for increasing sales so that will be your causal study. So such an examination requires a causal design. So in this video lecture I have basically discussed about what is research then I have discussed different types of research design. That is our exploratory and conclusive research. And then again under conclusive research there are two types one is your descriptive research and another one is your causal research. And depending on the type of study we administered like our research design will be different. Hope you have understand this video lecture here I have given some further references you can also go through these books for your study thank you.


Yeah, again, so this session has been video streamed and recorded, so just everyone of you should be aware of that. It is about this upcoming law, the GDPR, which is the data protection law. I'm going to say more about this. And the question I want to answer together with you is how does MediaViki relate to GDPR on a technical basis? So what do users need to know that use MediaViki on their sites? What's missing? How do we intend to remedy these things? And what's our position where do we stand regarding the GDPR? I'm Marcus Glaser. I have a few hats on or hat. Currently I'm spokesperson of the NW State User Group, which is a group that cares for MediaViki installations out there in the white internet world. On my professional life, I run an enterprise that helps companies set up their MediaViki's and we publish a product called Blue Spice, which makes MediaViki Enterprise ready. So I also do have a professional interest in the outcome of what's happening here. Okay, so where do we stand? What's the GDPR? GDPR is short for General Data Protection Regulation, which is an EU law that will become effective on May 25th, 2018. There has been a transition period from the old country-based regulations to this EU-wide regulation. The transition period was for two years, so actually all that panic that happens now with regards to the GDPR could have been avoided if all the people affected by the law would have started working towards implementing it earlier, but that's probably the human nature, so we see a lot of activity in Europe now in businesses trying to implement the requirements of this law. Actually, the intention of this law is good and I fully support it. It is decided to have individuals to better control their personal data, the use of it, the processing of it, and be able to interfere if they feel like something happens with their personal data they don't want. As with many laws, the intention is good, sometimes the details are not so perfect. One of the flaws I guess we are seeing is that the words are very vague, so there is a lot of room for interpretation, and actually what is a good way to implement the actual arguments of the law is something eventually courts will have to decide. So there is no blueprint, no checklist, you can just follow and say, okay, if you do this and that, then you fully comply. It's about the intention of protecting the data and having them, but there is a lot of room for interpretation. As I know that not all of you are from the EU, you might be wondering if this law how it does affect you. So the law is designed in a way that any interaction with any citizen from the EU, if you have any interaction, then this law applies. So if you come from outside the EU, I had found a very interesting hack, which is the EU blocker. So you set up your website, you put up a EU blocker and any IP address from the EU would not be able to reach your website, which is a good idea, but then you have to see what happens if your EU citizen is in the US and tries to access your site, it still applies. So this law is rather creeping all across the web and you should be... In one page of Media Week, someone said, I'm not from the EU, I'm not affected. Another person answered, if you ever plan to set your foot on the EU and you don't want to get arrested or find, you better see that you comply to that law. I don't want to say if it's good or bad, that's just the current reading of this law. Yeah, I forgot to say I'm not a lawyer, so I don't know this law by heart. I'm almost in the same situation as most of you are, so I see this law, I have to deal with it and the question is how can we do this? So a few basic terms. The law is about protecting personal data and this is taken directly from the law, so the question is what is personal data? It means basically any information that can be related to an individual person, a natural person. So personal data is not if I can identify an organization, but because an organization is not a person by definition. Interestingly, it's also about the question directly or indirectly. So if, say for example, I put my name somewhere, then I can be directly identified. If I put my IP address somewhere, that is probably a case of indirect identification because it's possible to use the IP address, go to my provider and get to my name. So that also applies to pseudonyms and other things. And then it's also a question of data processing, so if for example you write about a person that is from Germany, it's probably not totally identifiable here in this room if you write about another person that is age 40 to 45. And then you somehow can bring those two data sets together, then you pretty much get me or maybe another person here, but you can pretty much identify us or me. So that is the combination of factors which should also be considered. The law applies to data processing. So that basically means any case when you handle C, modify, delete whatever data, that is processing. So it's a very wide term and when in doubt if it's processing or not, you better assume it is processing under this law. So as a rule of thumb, if you deal with any personal data, somehow you will be affected by this law. Okay, so this law is a huge number of articles and there's a lot of principles involved and a lot of rights. The things that are of interest here are the ones that affect the technology. That's what I think we should be talking about. So it's not about, I don't know, the disclaimer you need to put on your page or things like that. And we have six rights. So actually when you try to categorize, to organize what's happening here, for the sake of technology, it's not that easy. So when you skim through the web pages, they give you a lot of advice. I try to compile it a little bit, condense it, but again, I'm not guaranteeing completeness here. It's just the way I understand it. Okay, so what are the rights of the principles? There's one principle called transparency. So the user needs to know what's happening with their data and they need to be able to access that data. So that is here right to access and to be informed. There are a few requirements. For example, the user can ask an organization, what do you store about me? And the organization then has to give the user a list of the data they stored about this person. Okay, then you have the right to rectification. So if there is any false information somewhere stored, then the processing entity, that's the term, is obliged to correct this error and do so without fee. That's another thing for companies. So Facebook cannot just go there and say, I taught you $10 for every spelling mistake in your name. I have somewhere in my data. They have to do it for free. Then there is the right to be forgotten. So if you want to go away from a website, from an organization, you can require that organization to completely forget about you. That is something we will probably have to talk about in the context of Media Weekly. Then there's the right to data portability, which sounds somewhat strange in the first place. Basically, the data processor is required to provide a set of data in a form that can be imported or can be used elsewhere in a commonly known format to the user on request. So I can go to Facebook again. I can say give me all the data you have about me. Then I get this large file or whatever print out, and I can do whatever I want with this file. The question is, what's the purpose of this? In the context of Facebook, for example, I see some people doing their photo journals on Facebook. The lawmakers want to prevent a situation where Facebook says, okay, you can go away, we can erase all your data, but you can't take your personal photos with you. They're just locked in the system, so either you stay or you lose your data. So this prevention of locking is one of the main intentions behind data portability. They also think competition among similar platforms will increase there. I don't think we have a huge problem with data portability. There might be the question of how do we compile all the contributions of the user, but generally all the contributions a user makes to a media, the key is basically open. So I don't see a big deal here. Okay, so then there's the right to restrict or object processing of data. Which is basically, yeah, and you can withdraw your consent. So if I say it's okay for Wikipedia to process my data to store my username, at a certain point I can say, okay, it's no longer okay, and then the username has to be removed. And the last thing is users need to be notified about security breaches. So if there is a large hack and a lot of data gets stolen, then all the affected users have to be notified. I guess that makes sense in a way. We still have to see how this can be achieved using media. Okay, so I looked a little bit to other software I worked with and tried to see what they do. I found some position papers and I guess you can find lots more if you look on the internet. So for example OSM takes the articles of the GDP audiences. Okay, with regard to this article, this is how we stand. This is the current situation, this is what we want to do. A more lightweight approach came by Easy Red Mind. So where the OSM paper has some 24 pages, I think Easy Red Mind paper could be condensed on two pages or three. So the second approach is to write plugins to make it easier for auditors, for example, and to provide the necessary export features. So WordPress, for example, does have a GDPR plugin, Joomla does have a GDPR plugin. And it might be worth looking into what features they provide using these plugins to see what kind of things we might think are missing in Media Weekend. And then of course there's the approach of adopting the core software again. Easy Red Mind, which is software I use personally. Thus they added a few buttons to provide complete audit trails and things like that to ensure data integrity. Okay, so that's the general overview about GDPR so far as I can give it to you. I was thinking a little bit about what data is affected in Media Weekend. And of course, again, this is not a complete list. This is the beginning of the brainstorming, which I want to continue with you in the etherpad after I talked. So what kind of data do we have in Media Weekend? What kind of personal data? I think these here are pretty obvious. We collect username, real name, email address and language. We do so by consent, say for the username I think. So no one has to give their email address, but if they do, it's still storing personal data. And we still need to see how we can, for example, remove that. Also we store IP address of anonymous users. That is probably more of an issue in Open Weekends out on the internet. It's not so much an issue in the internal Weekends because they typically do have something like a login only policy. But still the software is capable of storing IP addresses and uses that. And that's probably one of the questions that will keep us busy how to deal with the IP addresses. Then we do have user actions, like the version history and action log. And while these are mostly about content user contributes, there are some kinds of personal data which are interesting. So for example, there's a timestamp and you can do profiling using a timestamp. So when a user is active, you can, for example, interfere their time zone or their working hours or their non-working hours or whether they edit in their working hours. You see there's a lot of stuff in there. So timestamps in the logs also if you have a profile of what kind of articles a user edits, you can maybe profile their user's interests. You can draw various conclusions from that, which is also this combination of things, combination of data and identification. And I think we can also deal with that quite easily, hopefully, but then we do have one thing in MediaVQ which is quite tricky. That is all kind of data that is in the content area. So starting with signatures which are part of the content, links to user pages, any contribution of a user where the name is mentioned or that can be personally attributed could potentially be a personal data. And yeah, we have to find a reasonable way to deal with that. So while it is quite easy to do a replace of signatures in the current version, it might not be so easy to remove the signature from all the previous versions. I mean it can somehow be done probably, but even if you find the perfect regex to remove a signature, there's always the risk of false positives and things like that. So that is one of the things where we need to see how we deal with it. Okay, so whether we stand, this is again the beginning of drafting a document. So the right to access and to be informed about the data, we do have a list of recent changes, we do have a list of future contributions, we do have the logs that can be filtered. So the user pretty much knows most of what is stored about the person. They can also do a full text search for their username and see where they are mentioned, at least in the current revision. So then we have the right to rectification in the data. The user can just change it as far as I know. There is no history of data in the user table. And in the most current version of an article, you can also correct the data. And I think one could safely argue that if it is fixed in the current version, that would somehow suffice, at least rectification. I'm not sure about erasure. So that's the right to be forgotten. I think we have to put some effort, some energy into that. Regarding the data portability, there is the export pages. And what I still think we should provide easier user interfaces for exporting the data for one person, theoretically the person is able to export the pages they contributed. So we don't have a lock-in situation. And I think with the page export, this should be okay. Again, not a lawyer. Right to strict or object data processing. I'm not really sure if that is a technical thing. It might just be that we need an opt-out page on media key saying, I no longer consent. For the right to restrict, it's okay.  I will have a legal action over this data. Please do not move that. So the solution is to just clone this data into another base and move the data on another instance of media key. Don't touch this data there. Okay. But I have to remove the data of the user and the future version. Just need to edit somewhere else so that it can be used in a legal process and not on the page. Sounds cool. And last thing, breach notification. There is no mass mailing feature in media wiki right now. But again, there's no requirement for a technical solution. But if you run a wiki with more than a few hundred users, then extracting all the email addresses and sending a mail one by one to those users might be a little bit hard. Maybe this could be a good point to provision media wiki with a kind of notify all users about something feature. People have also proposed that central notice might be adequate to meet that requirement. It's just a suggestion. Yeah. I would, like from the text, from how I read the text, I think it would be okay because it's a notification. The question is, does it require a push notification, for example? And that's something that's probably up to lawyers to decide in the end. But I mean, if we decide, I mean, I don't know, we are not a decisive body here, but if the media community decides to do a minimal approach, then I guess that a notification on this side could also be okay. Just one additional sort of thought we'll have stored about that there's a check-use at the website, and I thought it was more about the website projects or larger projects. But that's something that they don't, the regional public, and we generally don't want to disclose to them. So there's a bit of a conflict in what we want and how we can resolve that. So I take an easier approach here because I say this is about media wiki and not about the Wikipedia's. But I know there's a discussion about that, and that's probably a very tricky part. Even though people can only request data stored about themselves and not about others, but the question is, how can you do this in a safe manner? Yeah, so that's the end of me talking, and what I would like to do is I have basically copied all of this over to an etherpad, and I think we can go through it and see if we have any additions right now. If we can find some potential solutions. And then what I would love to see, like in a few weeks maybe, is a page on media wiki saying GDPR compliance and then we address just the article and say, this is how we comply or how we intend to comply. There is one thing that might be useful information. When I was talking to, I have to get my company ready to GDPR as well, and I talked to a lot of people knowledgeable of GDPR. Most of them say, if you are in danger of being fined or being subject to a lawsuit, and you can prove that you actually started a process of implementing the regulations, that helps a lot. So at least for organizations, it will be that they will not, on May 25th they will not start a scan and find everyone with 20 million euros. But they want to see that you are in the process of getting there. So that's also a thing where I think the GDPR compliance page should be on media wiki.org. Could you or someone else be able to do a summary on where the foundation is at with their installation and how they did you comply? Is that something that anyone knows? No, just wait a second. I just want to remind you that this is publicly recorded, so be careful about the internet. Okay, yep. Okay. Yeah, you wanted to ask a question? No? Okay. So in the presentation which is also linked in the fabricator task and in the etherpad, I put a few links up there, most notably of course the text of the law itself, so we can look up for reference. Okay, so check out this etherpad. As I am well prepared, I hope. I opened it already. So I guess the best thing we can do in this session is to try and do some kind of collection of where we are and what we can do. So unless there are more questions, sorry. Yes? Okay. So that's a copyright thing basically. Yeah, okay. I have to rely on people that know more about that than I do. It is, yes. You talked about then starts to get into what is copyrightable. Yeah. Which can vary a lot by jurisdiction, but in some places like if it's just facts about the user that may not be copyrightable. In a similar sense to like if you're writing a phone book in many jurisdictions, but not all the listed numbers in the phone book isn't copyrightable. But the presentation happens. I don't think it's your right. If you're going to talk with some other right though, then it's... If a user requires us to analyze all the data and read it to him, everything he has published is longer attached to his name. Oh, I was not thinking about the content they had created. Yeah, that's an issue. Yeah, there's the attribution issue, which is a whole other thing we haven't talked about. Yeah, but I... So just taking on common sense if a user requests his removal of his name from Wikipedia and at the same time request attribution, then the user is probably schizophrenic. No, that's because there may be... In France you cannot renounce attribution. It's part of copyright that you cannot renounce attribution. Okay, that might be a legal loophole for any media, published media, stuff. But again, that is up to lawyers to decide, I think. And I don't know about the situation in Germany, for example. Yeah, okay, so what else? Any more questions need for clarification? Okay, so let's assume... Let's continue this under the assumption that we will be required to remove personal data and don't draw this one card. So what kind of data do you think that list is complete? The data we are collecting, actually. So username, rename, email address, language, IP address as like personal, directly related personal data. Yeah, I see the extensions that is probably also a very vast range of things. So I was thinking about that extension problematic before I did this talk. I think we need to split it up basically and say, okay, this is MediaViki Core and then see what the situation for extensions is in the second step, because an extension can do almost anything. So I know we have social profile extension which stores like any data. We do have extensions that store in Wikipages so revised, we have extensions that don't store revised and more. Okay, yeah, Web Server Access Logs. That is also a good point. I think it's not on the scope of MediaViki like on this GDPR compliance page. It should be mentioned because people should not forget about it, but that just applies to any website in, yeah, okay. How about like special pages? Is there, except for logs and recent changes do you think there's other, there's the list of most active users, for example, that might be some kind of information, but if the user is, what happens when the user is deleted, can't delete a user? If the user is merged into this big blob of anonymous users, will this information persist somehow? Probably not, okay. Does that lack of users would persist until the next time they're scripted? I guess that's okay. So there are some time periods like 30 days that you can argue, that's in the law, you can argue reasonable times. Well, I mean, that's... There's above where the active users can access where it doesn't get updated ever for certain configurations, but that user special page does. But in, as we work in a heavily developing environment, we assume that no bug is forever. One thing is right now with images, for the current version of an image, it's impossible to delete what user uploaded that image, like it's possible to delete that, and generally, like if you're looking at a page, you have to add a view, like edit the page because you can't delete the top user that's something to consider in terms of this. You can't delete which user? Well, I guess if you're renaming the user, like the user of the most recent provision of a page, like you can't re-vision delete that. If you delete it, it will be rushed into the message anonymous user of this special environment. Yeah, I guess. Then there would be the anonymous user when it is updated. It'd be nicer though if, like, you know, it was instead of showing random anonymous super-merged users showed the users deleted, like what you get when you use the hide user feature in special block. Would you be renaming the user to anonymous and some other generation identified, which is possible to reconstruct the original user name? I don't know. To the still student anonymous. I think in some ways, what this really needs is the hide user feature with that button that says, like, make this permanent. So you hide the user, what you made? Like, you know how there's a hide user feature currently? Oh, no. It's disabled by default, but not really disabled. By default, no user group has permission to do it. But if you give it things, the hide user right, then on this block page there's an extra checkbox to hide this user in all pages. Hide is not an option. What we need is that plus an option to make it not just hidden, but actually gone. Yeah. But I think that feature could be used as a stepping stone right now to see the things we need to do. Okay. That's cool. Let's just put it. Yeah. Great. I love Etherpad because you don't have to do anything as a presenter. People in the audience will help you out. There was a question? Yeah. A lot of this seems to be based on the production we actually are able to verify the person who's requesting a change. Or is that actually something that we generally don't have a list you've got the log in and you've got some sort of authentication. You've got the person who's chosen to use the name manually to be named so it could be someone else's user name that may request how do we know if the person did actually have a different visual correct person. So... Yeah. Yeah. That's a whole new problem with IP addresses. I think that is a process question. So if you're on your media key and you allow pseudonymus or anonymous access and then as you say a person using a pseudonym comes and says please delete this user you have to make them it makes sense to make them prove that they actually hold off that pseudonym. That is not a technical question though. Can be a technical problem if you've never actually chosen to keep your confirmation to be able to verify it. If you actually refuse that then you are actually not in compliance. It's a difficult way to do that with login users with users who have an actual account is to make them log into their account and edit their user page or something like that. With IP anonymous users I have no idea. So... Yeah. I hope they have not lost their credentials and want to be deleted simultaneously. The problem can be I've changed my email provider and I can no longer access the email that it sends. How can I rescue my account if I'm logging in in order to be able to verify who I am. We often have people in this scenario that end up having created a new account that old account is definitely lost. If you verify it was there in the context of email address that's if they didn't set an email address and they can't rescue the account so how do you make sure that we can actually be able to be used to verify an account in order to be able to make them change? So I came across this discussion several times here and I think that is you have to conflicting interests here. So I don't think there is a blueprint solution for this. So for example in order to verify this person that the pseudonym is still the person you might just say we store the IP address as long as the pseudonym is there that again leads to collection of more data instead of less data and I don't there is a clause that says store the data as long or store the data as long as it's necessary to run the operations and services in the way you want to provide them where with one exception eternally is not an option here and again that is something that will only be solved in practice so I assume that in a few months there will be some trial cases and then there will be some rules of thumb for this also for the request for takedown of pseudonyms for example but let's put it that way from a common sense perspective if you're not able to prove an identity of a pseudonym it's probably not possible so by not being able to prove you have shown that there is no relation between that that's what I would argue there's a provision in the GDPO it comments on if it's reasonable to do it in fact it says shall take responsible steps including technical measures taking accountability available technology and the cost of implementation shall take reasonable steps and that's directly from it so there may be conditions where it's just not going to be possible to do it and that's actually mentioned in here yeah and we have this reasonable costs that's everywhere in this law so that's what I say the law is very vague and I think a good first step is to just address it and say okay it's not reasonable even for Wikipedia I would say if it takes a year to implement then it's probably not reasonable and we have to find other ways to get around it and the same thing applies for media so user deletion for example is not easy now because you just can't go to the database and delete the user but it's not a good idea but there is a user merge plugin so that is a remedy that's a workaround you can say okay we don't delete that user but we merge it into the anonymous pool user and then we have probably come around this right for erasure so we have suffice to requirement just talking about future implementation there has been a lot of discussion about who is database and whether or not they can just ignore all of this and they're going to be fine and it's probably a comparable case with large non-profit wikis because it's a public good they are a rich public good which is a big difference if you could be considered to have a good benefactor that could actually influence the changes of the quality that's necessary so just saying well we're starting to implement changes is probably not going to be enough at least that seems to be an indication from the law actually saying not to just question on database one you may get sufficient consideration if you're not compliant on day one that the whole thing is not acceptable so that's also a political case there's a bit more to it than just the who is database it's worth using as a a witness test of whether or not the compliance is going to be acceptable they're worried about saying you've got 12 months to comply with what they always say is you had two years to comply so but now we have a situation where we have to deal with it and I think starting a process is better than not starting a process sure so that's what I think okay so responses to require I move on to the responses because we were talking about right to issue anyways so again I think is like the most the hardest bit if we go to like a data portability then I think like exporting the pages could be a good thing and as I don't know what you think but it shouldn't be hard to write for example for media weekies outside of Wikipedia to write a export script that dumps the list of user contributions and then compiles it and says export with these pages so and according to the law I think you have 30 days to react to a request of getting all the data so that is good question good question I don't know that's the contribution and we do track it and we need to provide files or file names I have no idea no it says the data stored about a user should be provided in a commonly used format so I'm thinking Jason XML I'm a developer so you don't want to text does it say that you have to only give them information about their user or just a dump of these yeah I was thinking about that and yeah yeah so it's always the same you know I would explain I mean what about if somebody else on a different account writes something about the user links their tool page exactly we need to implement the content permanently on request if it contains personal information because right now there is no way to permanently delete an article it's going to remain in the the provision text is going to remain on the servers and the archive provision log is going to remain on the servers so I think it also applies to file uploads and that's the point where it gets really messy because you can't just retrospectively edit the history that contradicts the whole philosophy of a wiki and yeah so I think we need to have wiki users in general not only media but we need to have to get a position on that that is legal as well as feasible and I don't have a solution for that but I think we're getting to a point where it's only safe to delete all the content of the wiki because you never know what kind of trace is someone left somewhere or some person wrote about another person somewhere and you just can't figure that out I think on that part probably the onus is on the user to provide infringing URLs for example google has an rtbf form and it requires the user to provide a list of URLs which contains their personal information and these are to be deleted so probably it's the same judgment to automatically delete the user pages for example but then the onus would be on the user to provide for example this guy put my name on their user page I think that's a defensive position maybe but still I mean reverse editing history is not I don't think it's an acceptable option I know this is I mean we're not negotiating with gdpr but maybe yeah I think that is also kind of a gray area because it can't be easily retrieved you cannot search revision pages in a search for example so I think that would be like this would all become gray area but again I'm not a lawyer I don't I can't say this is like what it is the dump formats in general would actually be considered to be a commonly used format to rely on that for the previous gfdl licensed that was actually a requirement of that law about the license that it would be distributed in a commonly acceptable format and with the dumps and the test neither of which were really common for much of the time but considered to be enough because people could actually use to interrogate themselves and provide we actually do here not but being one extra bit that's the one more visible part yeah no so we wouldn't want to try and add extra stuff to the dumps but we could use dumps as a way to say all the information is actually there there are tools to interrogate it and identify which is yours so therefore it's not being hidden it's not being just the tools would not be the most commonly used tools tools that we could write and what did you say was the case where that was used to show the gpl gfdl so that was a requirement it's also gpl any of the new licenses required that you use or you provide that are necessary in order to compile or make it usable so if you don't provide those tools it is considered to be a breach of license and if any of you can just pull one into that truck here is the source code and they forget to input the main file that would be a breach of gpl okay so we are getting closely to the end of that session I want to before we continue discussing until it was out I want to ask you what do you think is a good way to proceed I assume that if I now would create a page tdpr compliance on media you can just dump this there then it would be taken down like 10 seconds afterwards because that is might have legal implications and what not so I kind of think we should continue working on that maybe in the etherpad until we have a version which we think we can safely present but that's just a suggestion if someone has a better idea so just looking from what is the middle installation that is actually compliant what options do you need to have turned off in order to be compliant so then you can actually publish one way, not the way that this is one way of having it set up that it is actually compliant for example you must have authentication of your addresses rule out all the dodges and then all that whole lot papers or if you want to have anonymous users contributing here is how you would go about being compliant so we added an initial paper on how it can be set up ignoring what people might have as their current set up and how they might transition this is something that in one set up will work and we can fairly safely say that this will be a set up that is not going to cause problems may not have many people who have been actually switched to that very quickly but at least it's been a study of how this is going to work sure that's a good approach but again if we start creating this article publicly on media it has a very high visibility because a lot of people will look for it so maybe it's just a good idea to do a GDPR page and then go to the discussion page and work on this or use the etherpad I don't know until we have a good feeling about it now we can also use good so I think as I said this is more the kickoff of a process than in the end for anyone who is interested please contribute to that page if you want you can leave your email address or whatever and I will put it somewhere publicly and erase it on request I think the etherpad is good for now and then once we feel like that is a good thing maybe it's a good idea to put your some way to contact you on the etherpad so we can do some kind of informal working group and assess when we think that page quality on media wiki.org ok thanks for your contribution and for all your discussion and see you for the next person to talk about thank you


Hi everybody, this is Dave Vellante. Welcome to this CUBE conversation where we welcome an ESG senior analyst, Bob LaLiberte. Bob, good to see you. Great to see you too. Thanks for having me. So, love it. I love to have the analyst session. Set it up. What's your scope? What's your area of expertise? Yeah, so my coverage area right now is networking in its entirety. So that spans everything from enterprise networking, wired, wireless, campus, data center, et cetera, all the way up through telco and cloud networking. So how do you look at the landscape? I mean one of the big things I think about a lot is how does the shift to cloud migration? How does that affect the existing network players? I mean you've got Cisco as the big whale and it's amazing to me. They still have whatever percent markets here. They have 60, 65% of the market. Are things, what's happening in the competitive landscape? How is cloud affecting that? Yeah, no, that's a great question. I think the interesting piece is so many times organizations think about the network as plumbing. But the reality is it's really important plumbing because as you talk about cloud and things get more distributed, well guess what connects those distributed locations? It's the network. And so organizations as they've moved to the cloud, you've seen a big shift with things like SD-WAN and so forth. How do I get more efficient connectivity up to that cloud? How do I not only enable better connectivity between my data centers in the cloud but now all my remote workers in the cloud? And so there's been a lot of big shifts going on that have driven the importance of having not only a network but secure networks. So like I said, cloud is one thing and you're moving your applications there but with the pandemic you saw the remote work. So think about the network administrators who were managing, hey, I've got to control network connections between my data centers, a couple clouds and maybe dozens, maybe a hundred remote branches. And now I'm connecting to 10,000 micro branches that I need to ensure that they can connect up to these applications and so forth. So hell of a lot more complex environment today than it used to be for these network teams. When we look at what we're seeing how the networking providers are responding, it's by driving comprehensive end-to-end solutions. So unifying wired wireless and WAN, driving efficiencies there. You're seeing even thousand eyes for Cisco and things like that because they know the internet's becoming more integral part of the corporate network. So being able to drive those types of things, being able to I think look at how to drive those operational efficiencies through AI and ML. So one of the big shifts we've seen in networking is the transition to cloud-based network management. And obviously that couple of things that helps with, first of all, the operations teams who are working remotely can more easily access it. But once all that data's up in the cloud, it creates a platform to be able to invest in AI, ML and be able to drive intelligent alerting and even automation. And that's really what's needed because as the environments get more distributed and complex, you need to have those operational efficiencies, that automation, that intelligence to help them. How has remote work and hybrid work affected sort of network spending priorities?  And I always have this theory, okay, when people come back to the office, and I know it's going to be a different world, but the HQ probably needs some love as well. So has that been a tailwind for the industry? Yeah, absolutely. That's what we're seeing now. I think when the pandemic first hit, everyone said, I've got to ramp up my VPNs. I've got to scale out my concentrators. I've got to add more firewalls in my data center. And then after a while, when they realized this was here to stay, they said, okay, we just created that hub and spoke network that we just got rid of with SD-WAN. So what are the better solutions we can implement? So now you're seeing them, not only implement better networking solutions for the remote workers, but reimagining what the campus looks like. Because it's not going to be ever 100% full or maybe it will, but for how many times a year will it be 100% full? So you've got to go from 80% cubes and 20% conference and collaboration areas to 80% collaboration areas and 20% cubes. So we're seeing a lot of transition taking place in the campus environment as organizations are deploying newer technologies like Wi-Fi 6E that have greater bandwidth to allow for those collaboration apps to run in those collaboration areas instead of just having the single wired conference room for video, right? Everyone's got to be able to run their voice and video collaboration app. So how do you look at the landscape now? I mean, again, we can't talk about networking without talking about Cisco. They've up there, I saw you and Zia's talking about Cisco's quarter and other networking topics. You know, they're up, their long-term guidance is for 6% growth for a company that size, that's really outstanding. I mean, Cisco's really has always been an execution machine, of course. It's a new era now under Chuck. But so you got that, but you know, there's more than ankle biters. If you look at Aristos doing pretty well, there's guys like Extreme, there's others that are out there, but nobody seemed to be able to unseat Cisco. What's happening in the landscape? Well, yeah, I mean, that's a great question.  And you have to also keep in mind that with Cisco, it's not just about the technology, but the fact from a, if you think about it from a cultural standpoint, these are workers who have been trained on Cisco since some of them, since high school, right? The educational component that Cisco has done has groomed generations of network technologists. So when they come into the market, right, they're fully familiar and used to Cisco. Plus they make a really good product and they've got products that cover everything, right? They cover the whole gambit. So they're still able to maintain their share, they're able to grow, right? They're able to move. They've made a shift last year, they announced in last spring that they were going to focus more on end to end.  But the other competitors are also having good years, right? And I think also the rising tide floats all boats. And so because of this distributed nature, the importance of the network, everyone is doing that. Plus obviously this has to be said the supply chain issues where people are ordering ahead as well. But organizations, you look at ERISTA, they've gone from just being a data center company to expanding all the way down to the campus edge, wireless, right? They're creating an end to end environment. Extreme did the same thing, right? They went out and made a lot of acquisitions. They pulled them all together, integrated. They're all moving to this cloud based, right? End to end network management. ERISTA has been on a tear, bringing in a lot of, not only innovative technology, but innovative technologists. So if you look at some of the organizations they bought, you call it a Route 128, it's 128 technologies. Okay, so sorry folks, I live in Massachusetts. It's always been Route 128. You remember when, don't you? But yeah, 128 technologies, MIST was their big, MIST was kind of like their VMware, right? VMware to EMC was, MIST was to Juniper. And so we call it the mystification of Juniper, where every organization, every company they bring in, they're rolling under that and MIST is the AI engine. So they're bringing in the 128 technologies into that. They've got their own stuff under that, their wired switches. So they've got this unified wired and wireless and WAN assurance now that they have. So they've been gaining a lot of traction with that. And again, for the things we were talking about, because it's far more distributed and complex, you need to have, it's not like people are getting replaced. It's not like, hey, we're leveraging this automation. So that we can get rid of network teams. It's because it's getting so much more complex, just to have the same number of people manage that more complex environment, we need those intelligent solutions. So I want to ask you about networking and multi-cloud. And so it's kind of tongue in cheek because we coined this term super cloud. And so what we meant by that, so here's the premise, and I wonder if you could give us your perspective. So multi-cloud, I've said many times is, I think largely a symptom of multi-vendor. I run in this, I run in AWS or Azure, I've done the work to understand their primitives and or Google, whatever it is, but it's not like an abstraction layer that's floating above all those, but now you're starting to see that. In fact, it reinvent in November, the ecosystem, it seemed like was, everybody was focused on developing what we call the super clouds. And again, it's tongue in cheek, this abstraction layer, it hides the underlying complexity of the primitives and the APIs adds incremental value on top of that. So there's a company ProSimo, which Steve Herrod is invested in and others, Praveen Akiraju, you know, from Viptella. Aviatrix is another company that's sort of, Steve Mulaney has come on theCUBE and talked about what they're doing. Like, yeah, that's super cloud. So it seems like it's something new and different than just multi-cloud, which is kind of connecting in to different clouds. It's that value on top. What do you think about that? And what does that mean for networking? Yeah, no, that's a really good point because we are starting to see the inception of organizations going beyond having multiple cloud providers and looking at starting to deploy applications across multiple clouds. It's still really early. The vast majority of organizations are still, I use this application for this cloud and this application for that cloud, but that's the next frontier. So that's what they're trying to solve is, how do I create this basically cloud fabric and make it as simple as possible? And again, all the things we've been talking about, how do I, instead of you having to learn Amazon, Google, right, Azure networking technology, learn mine. I'll take care of it. I'll abstract all that complexity from you and make it so much simpler to be able to connect to these, interconnect and connect to them in a seamless fashion. And so that's what they're really trying to do, is they're, right, and the hard part is it takes really sophisticated solutions to remove that high level of complexity and make it simple for an organization to do that. So yeah, absolutely. If I had more time, I'd make it shorter as somebody writes a lot. Exactly. So, okay, and I think you're right. I think it is future. It's definitely not here today, but the other thing is it ties into digital transformation. You know, we used to, again, throw that buzzword around, but companies, not just tech company, I mean, everybody's becoming like a tech company, but organizations, financial services companies, healthcare, they're building their own clouds on top of the hyperscalers who spend $100 billion a year on CapEx. And that seems to be a trend that I think is going to take legs over this next decade is, just like in the previous decade, everybody was thinking, okay, we're going to sassify our business, software's eating the world, and now it's software and cloud services are the way in which I'm going to create customer experiences. Correct. Yeah, it's why should I go out and make an investment in technology when the technology's already there and I can rent it for when I need it, scale it as I need it and do all of that. So I agree with that. I think that's something that we're seeing. And you know, the interesting part though is that when we look at our data points, I, you know, probably less than 40% of the applications and workloads are in the cloud today. Right, so there's still a role that the corporate data center plays. We are seeing over time, they expect that to progress and transition, but I think there's still always going to be maybe a quarter of the workloads and applications may never leave, right? Depending on how they're built, et cetera. So there's always going to be that distributed environment where you've got workloads in the private data centers, workloads in multiple public clouds, and also that the big thing too is don't forget about the edge, right? We're seeing a lot more edge activity take place as organizations recognize as they deploy more IoT devices and want to get real-time business insights, they've got to deploy the compute there. Well, and that's something that I wanted to ask you about, but going back to what you just said, which is I agree with you. So that suggests to me, Bob, that we're just kind of with cloud just entering the steep part of the S curve.  Maybe they probably won't get there this year, but they will next year, but we're entering that steep growth phase. It really could be, I mean, it's incredible, but I wanted to ask you about the edge because you're right, we've got to move compute to the edge. ARM is going to dominate, I would think, the edge. They already are with our smartphones. How do you see the cloud guys participating in the edge? Whether it was Andy Jassy or now Adam Salipsky or anybody at Amazon, they have the dogma of in the fullness of time, all workloads are going to be in the cloud. So they either have to change their definition of cloud or they're wrong. So what's your thought on that? Yeah, I think it really starts coming down to what's your definition of edge. And so much like when the cloud technologies first came about and you had all the shadow IT, everyone running off and everyone thought, oh, this is all great. Until you realize you had to operationalize it and you had to pull the brakes, stop doing that, we're going to make sure IT operations. Call the CIO? Yeah, exactly, exactly. Finding out where stuff was by going through accounting and seeing credit card charges. For the edge, what we've seen, I think, is maybe organizations really saying, I've got to deploy my servers in my own site right at that edge in order to get the lowest possible latency. And so what I think we're starting to see is organizations looking at that and saying, okay, well, I'm in a metro and I've got 25 locations in a metro and I've deployed technology to every single one of those sites. Do I need it there or can I put it in an Equinix facility that's less than five milliseconds from all 25 sites? So I think there's starting to be this pragmatic approach of looking at, let's look at the edge, let's take a look at what type of latencies, what is our definition of real time, right? When do we actually need the data and so forth? What kind of connectivity do we have? And then from there, figure out how we go about connecting it. And so for companies like AWS and Google and Azure, a lot of them, there's the local zones and things like that, they're deploying them in those colos because they don't have data centers in every metro but they can leverage an Equinix, they can leverage someone else's hardware that's there to deploy their software stack within that location. So I think that's something that we're starting to see more and more of is the edge and obviously the association with the telcos as well. They've got a great footprint if you want to get close to the edge with their colos, right, their home offices and things like that and whatnot. So their ability to move the compute closer to the edge, the base stations of the antennas and things like that are certainly significant and that's why you're seeing the wavelengths and things like that, programs like that. So I was going to close but there's some really interesting topics you just brought up. So call it, what are we going to call it? Near edge, far edge or deep edge. So and you mentioned real time. So for those Equinix data centers, I don't need, you know, true real time, right? But for Tesla, I need real time. I need real time inference at the edge, probably using a bunch of ARM cores and I can't go back to any cloud. So how do you look at that? I mean, both, I would think big markets, do you have a sense as though is one bigger than the other or are they both just enormous or we don't even know yet? Yeah, I'm not sure that we know yet. I think certainly, you know, it's riding the tail of the IoT. So the more sensors, the more things that are deployed, the more that that data, businesses realize they can leverage that data to make real time business insights to drive either better experiences or if you're in retail, right? So location based services and real time offer management. It doesn't do any good to offer a coupon for something that you've, that's 40 yards behind you, right? That's past, like you said with the cars, there's, I've seen some studies recently they say, well, based on the latency, if the, if the command is to stop and it's, you're at one millisecond, it stops within four inches. If you are at 50 milliseconds, it stops 10 feet later, right? That's a big difference. You know, and I don't know if those numbers are right, but you get the idea about the impact, what the real time impact is. Margin for error is not huge. Exactly. So, so that's where organizations, I think first and foremost need to take a pragmatic approach to determine what is real time for us? What's our definition of it? And then that can lead them to where do I need to place this compute technology? And then that goes to how do I then connect to it? So for the Teslas and so forth, obviously you're going to want 5G connections if possible, right? Ultra low latency and not just any 5G, right? The, the good stuff, the, the millimeter bandwidth stuff that's the ultra low latency. All right, so let's wrap. So, so what's going on in your research world? Obviously the big, big acquisition tech target, they seem to be investing in ESG guys are really, really growing and hiring. That's awesome. Any research that you're working on? Yeah, there's a couple of, a couple of projects we have going on right now. We're, we're wrapping up a four part distributed cloud research series. So we did it on distributed cloud infrastructure, applications, observability. And now this last one is on the edge coincidentally. So we're working on that. We've got some new network modernization research that we've published. And we're going to be looking from a networking perspective, looking at end to end network modernization, which will be coming out soon. Awesome. Bob, thanks so much for coming on theCUBE. I really would love to have you back and chat about some of those things. Observability, hot space, God, I wish we had more time. All right, thanks again. Absolutely, appreciate it, thanks. And thank you for watching this CUBE Conversation. This is Dave Vellante and we'll see you next time.


Welcome to the Jalassette News. Take the top stories in cryptocurrencies and Jalassets. Yeah, break them down to bite-sized pieces. Today, we're not just going to talk about cryptocurrencies and Jalassets, but we're going to actually take a look at the news news, what is going on in the world. And if you live in America or if you live really anywhere, this has probably been one of the hottest subjects that is out there and is one of those things that is really causing a lot of controversy, which is Donald Trump has been permanently banned from Twitter. Now, if you have stumbled across this channel and you're into politics, just know that this is not a political channel. We try to stay away from that. I think there's two things that you can do to alienate people pretty quickly. That is one is to talk about religion and the other one is to talk about politics. So we try to keep away from those two subjects, but this one really plays into the cryptocurrency and digital asset aspect about what you can do for censorship if you want to even go that route and how things are actually progressing as far as social media platforms from centralized to decentralized. And I'll explain that in a bit. So again, I don't have an opinion on this one way or the other because I do not have a dog in the fight here. I'm not going to get in the middle of this because that is just a recipe for disaster on this channel, but it is something to note. And that is that if you are here and you are concerned about censorship, and let's just say that you are not Donald Trump, okay? Let's say you are the Dalai Lama. And for some reason, you have a website or an app. And for some reason, Google or the powers that be say, you know what, we don't like your message for whatever reason. And they just banned the Dalai Lama for whatever reason. Or maybe you have a business and you sell something wacky.  And we're just going to take it away from you. And that can be justified through a whole spectrum of things. Now, there's different laws and regulations. But and who knows what will happen in the future as far as these different propositions that are going to be brought up in the US Congress. But for right now, this is this is what we have, we have centralized aspects. And that's what pretty much runs everything. So if you're outside of the decentralized or cryptocurrency last set world, this may sound a little bit unfamiliar for you. But for those of you who follow the channel, this is not nothing new. But it is something to bring to light, and just to talk about real quick. And if you wanted to actually build an app or build a website to bring the people that you have as followers or members or whatever else, there was a good tweet by Nick Carter, I don't know Nick Carter, I don't know his affiliation, but he's got a good point here. He says, you want to build an app? Well, it's simple. First, create your own payment processor, DNS, hosting provider, DDoS protection, bank, internet infrastructure, App Store, mobile hardware and government, and then build the app. Because anywhere along the way, those will trip you up. And they can just say, you know what, we don't like this, this, this aspect, we're going to, we're going to break you down. And we're not going to allow you to have access. And that is just the truth. So if you are like me, maybe you don't really like that whole aspect. And maybe you think to yourself, maybe there's a better way. Well, there is. And it's called decentralization or distributed ledger technologies, DLT. So in a centralized aspect, let me blow this up so you can see an essentialized aspect, when you have like your DNS or your servers, they're an essentialized location. So let's say you have like a GoDaddy or Amazon web service or Google, it is an essentialized location. And those centralized players, they can pretty much control everything that happens in there. And that is a problem. So with distributed ledger technology or decentralized, whichever way you want to want to look at it, it's not you don't have just one point of failure, you have multiple nodes all throughout the state, the country and the globe. For example, Bitcoin runs on distributed ledger technology, and they have over 10,000 nodes.  So that is one of those things. So what do you do when you have this issue come up? You're like, you know what, I would really like to have a website, or I'd really like to start a social media platform, or I'd really like to do something online, but I'm afraid of this censorship. Well, it's pretty simple. I'm just going to show you real quick. There is a website called Unstoppable Domains. And I have a couple of domains on there, and a lot of subscribers also do. And what it does is it allows you to purchase NFTs, non-fundable tokens, or the decentralized aspects of a domain. So like for me, I have Dan teaches crypto, Dan teaches dot crypto. And that is my domain. There's a, you can use a dot crypto or a dot zill. So instead of like a dot com, a dot org, a dot gov, you can use dot crypto or dot zill. And what's great about this is that the domain is stored in your wallet, just like it says right here, just like a cryptocurrency. So if you wanted to purchase that domain, what is great about that is that you carry that around your wallet. And it's not, it's not sitting on some DNS server. It's not sitting at GoDaddy. It's not sitting at Google. It's sitting in your own decentralized wallet in your own personal possession. So how does that work? It's kind of difficult to really think about, but we'll go to that in a second. But you can point your domain to content on a decentralized storage network. Great. Blockchain domains plus these decentralized storage equals a website only you can put up and take down. Now also on top of that, if you're into this type of thing, like probably a lot of people here who subscribe to this channel, you can replace cryptocurrency addresses with a human readable name. So instead of, in cryptocurrency, we have these long, super long addresses.  So imagine saying that, hey, send me some Bitcoin and send it to 0x527357, they're like, I don't know what you're talking about. But if you can say, hey, just send me some Bitcoin to danteachers.crypto. Oh, okay, I can do that. It's pretty simple. So there's that aspect. So here's some questions on the website, which I think will help clue these types of things up. First of all, does unstoppable domain provide you with a wallet? Because that's we're going to keep your actual domain, right? Yes, but only for holding your blockchain domains in order to send you send and receive cryptocurrency user domain, you will use wallets that have integrated our software able to use your own self custody wallet to hold domains. So pretty simple there, right? How will I be able to view a blockchain website? Because you have to remember if it's on, like I said, like any kind of regular server like Google, I mean, they can be seen pretty easily. And this is where the technology is there, but it's not really there yet. However, things are moving at a rapid pace. Again, if you're new to this space, I mean, one's last time you heard about Ethereum or Bitcoin, like why didn't we know about that stuff? But now all of a sudden, it's everywhere. And that's just how technology does. It kind of lurks in the background until, you know, it just gets into the masses. And before you know it, it's it's everywhere. It's a part of your life. And I think this is one of those things that's going to be a part of everybody's life, decentralized apps, decentralized exchanges, decentralized websites, and everything else in between. So how will I be able to view a blockchain website? Now you need to use a mirroring service, a browser extension, or a browser that supports blockchain domains. And then if you scroll up, there's a link and there is their unstoppable domains, which you can get a app, which is downloadable, which you can use for Chrome and Firefox, and then you can view decentralized websites. So so there is that. And it's a very simple thing. So if you ever want to like start things up and like, well, I want this, or, and this is how I see it right now, there's a lot of problems with centralization.  So if you think about it like this, well, where are things going? Well, I think things are going, there's so many dot com websites. And they're expensive, if you wanted to purchase. But guess what, in the early 90s, you could pick them up for practically nothing, hold them on for years. And then all of a sudden people like, Hey, I want that website. So for me, like, I think to myself, well, who wouldn't want a websites like me, I was in the medical industry, who wouldn't want a website called like stem cell therapy dot crypto, or platelet rich plasma dot crypto, or orthopedic surgeon, the best orthopedic surgeon dot crypto or whatever else, I think it would be a big boom, especially later on. And that's just one of those things that I see that could potentially happen. So even if you want to build something right now, you have that ability right now with these different extensions. So last couple of questions was, will I be able to search for and find blockchain domain websites on Google or other search engines? Well, major search engines do not currently index blockchain domain websites. For now, you'll be able to search for them at unstoppable domains on partner applications that integrate our search bar or on blockchain apps that index blockchain domain websites. So again, to get into this space right now, I think this is like the golden era time to really get in. I personally got in in 2017, a lot of people on this website are on this channel. No, I got in around 2017. And then I've just been what's called dollar cost averaging for years. I think 2021 is going to be a very big year for mass adoption. So again, I think this would be the time to really get into things such as this, not just, you know, like a first generation blockchain like Bitcoin or a second generation blockchain like Ethereum, but maybe you're looking at something a little bit more robust than that, leading off into the future. And then let's see who else. Oh, are blockchain domains part of ICANN, traditional DNS and ICANN is where you can find different information about your websites that are out there. And then they say no, blockchain domains are what's called alternate routes. They are not part of the current DNS. And then actually, sorry, will there be some sort of who is record who is is where you can actually look up like, you know, if I had a website, Dan teaches crypto.com, you can look it up and say, well, who owns that? Well, it's Rob from Digital Asset News. But here for decentralized apps, decentralized websites, not by default, sharing who is information is an opt-in, something that you can choose to do if you want. Otherwise, your identity will probably know. And then trade marks like that. So that is really it in a nutshell. This is Unstoppable Domains. There is a link in the description. You can use that. It goes right to the exact websites. You don't get scammed or go to some other place. But you're welcome to use that or just go to Unstoppable Domains. And that's it. But that will be in the description below. And that is all I want to talk about today. So again, not a political channel, but I just want to talk about where technology is going and how to get ahead of the curve to help you out. All right. So thanks for watching. I really appreciate it. If you like these types of videos, there's going to be two months going to pop up on your left and right. Not sure I'll let YouTube do their magic. And that is all. So again, thanks. And I'll see you on the next one.


Hi, I'm George cow and I'm here with one of my clients Nathan lively. So for today's short video I thought that I would ask ask him to share some tips Nathan is among other talents He is a podcast expert. He has his own podcast that has had over a hundred and forty thousand downloads, which is which is a lot a lot a lot and he's interviewed dozens of people on this podcast some of the some of the best experts from his industry and Anyway, he knows how to create a podcast knows how to help people create it knows how to help people market it So Nathan maybe share with us a couple of tips on what what you cut some common questions answer a couple of common questions, maybe Sure, so let's see one of the most common things that I see people do is ask for podcast reviews on their podcast and While that is valiant and important I found that that never actually works the only way that I've gotten people to give me reviews on iTunes for my podcast has to ask them personally and While that might sound time-consuming at the beginning It could be the difference between, you know one podcast review and 16 or 20 podcast reviews Which is a big credibility indicator where people go to your podcast and they say let me see if this is worth my time Oh wait, there's no reviews, right, so When someone emails you or someone messages you and says I heard your podcast I like it a lot. Thanks so much for your work and you say to them. Hey, would you mind leaving a review? this is a perfect time and it's worked for me a bunch of times and I only learned that because somebody else asked me for a review and I emailed them and said thanks for your hard work in the Podcast and they said could you leave me a review and I said bingo? That's how you get reviews. So personal one-on-one requests is Really the only way that I've gotten podcast reviews So that's what I would recommend to people and if I could add to that What how do you ask for the review? Because so for example like if you leave it really open-ended it could work But would it be better to say to make it easy? Here's a quick format if you want to use this kind of script, you know answer these two questions What what one thing did you like most about the podcast and what what kind of person do you think would benefit most? Something like that. What do you think? I just asked people I say could you write me a quick? I saw me try to make it sound easy a quick podcast review You could just copy and paste what you just told me in the previous email great So I try to make it really easy and a lot of times people do that because the email They sent me was Harry like the podcast I found that it's valuable it helps me build the skills that I need for my job and I say perfect Why don't you just copy and paste that into a review? Awesome. Yeah, one more quick tip What was the other thing I suggested that we were gonna talk about you were gonna mention the I'm forgetting now. Actually, there's so many. There's there's so many. Okay. Tell you seasons seasons. Okay, okay So I want people to start thinking more about their podcasts in terms of seasons just like a television show and This the main reason is that I don't want you to start a podcast and think I need to do this every week for the rest of My life and then it's this huge thing weighing down on you George is a good example of that he started his podcast doing it twice a week for six months And then he slowly was warned out and I quit for a while. Yeah, totally And then basically after six months of a break I restarted it and so you could say that I was a second season absolutely Yeah, so making an editorial calendar or at least some plan where you say hey my first six episodes Here's what they're gonna be about or at least here's the dates They're gonna come out so that you stop you have a stopping point where you take a break And you say this is the end of the first season. Let me see what results I got from this Let me see what I can improve next time Let me see what feedback I can get from my audience and then people say you have to be consistent. You have to be consistent You should but people totally fine with you saying hey, this is the end of the first season I'll be back in a month. Yeah, exactly or two months or whatever Hey, if you want to find out or you want me to let you know when I'll be back Or I'm gonna email everyone on my mailing list the day before and I'm gonna let them know I'm gonna give them a sneak preview of everything I mean it just opens up a lot more possibilities And I just see people getting kind of weighed down by the fact that they have to keep doing the same show every day Or every week right so their lives awesome awesome tip Okay, so Nathan if people want to learn more about you how to work with you. Where should they go? They should go to podcast marketing biz that's dot bi z because the dot-com was taken And so podcast marketing dot bi z Yeah podcast marketing that biz and if you go there and sign up for my mailing list I have a free list of all of the tools I use for my podcast production So people are always asking me What's the software you use for recording editing mixing distributing the show So I give away a PDF with a list of all the tools that I use when you sign up for my mailing list awesome Thanks, Nathan for sharing and until the next video everyone be well