Gيف y gherebyn, dyf yn ystafell wrth y gweithio fy ng Different yw'r sefydliadau, mae'r Rhywun 15-min yn olyg i'ch gyd, dyf yn f 의�. I'n rhan o'r sleidio o'r ff draws i gael i gael o'r busg oedd ffordd i ddweud o'r 20 ysgrif引ol? Ond yw'r Amgueddur yw'r hanfyddo drw'r eich dysgu rydych chi'n ysgrif ei fod yn cyfrifiad wahanol. Pau o'r sleidio wedi'i gwaith yn gweithio i'n meddwl yw'r hyn flynyddoedd, The challenge. Gloucestershire has been using their student record system for management of assessment for about the last five or six years. Students were submitting files on that. Any other assessment basically was done manually. About two and a half years ago, when I arrived at university, they had a list from staff of about 100 developments that they wanted done to the CMA system. And I took one look at this and said, well, Moodle will do about 80 or 90 of those out of the box. So why aren't we using Moodle for the front end of this? And then just using student records for the end of it. So this is what I arrived at. Basically they were using Moodle for learning and teaching. We had all these extra facilities, not all of them being used, but quizzes were group assignments. And file submissions were going direct into student records, but all of the administrative stuff like dates and suspected breach was all being done by student records. So the solution was we would integrate the two and we'd make Moodle do everything as the front end to save staff and students going into multiple systems. And the student record system would be used for the records. It's the admin tool, so use it for the admin, but use Moodle as the front end for the learning, the teaching and the assessments. The question there was how do we integrate the two together. And the first step for that was to recognise the bits that we already were and where the sources of the data were coming from. So courses and modules were coming from student records. So were the enrolments on to those, validated course details, things like that. We're all coming from student records already. Whereas the assignment brief, the due dates, quizzes, the date the students actually submit, the core data for those would eventually come from Moodle because that's where the student was submitting it to. So the asterix are the ones we were already passing to Moodle anyway to create courses and modules to put the staff and students on them. And the validated course details has a different colour start because that was in development. We had a parallel development to put module guides online and automate them at the same time. So the techie bit, we have a data warehouse sitting in the middle. We use MySQL for Moodle, Microsoft SQL for the student records. We have a data warehouse sitting in the middle of it that's also used for reporting. So we had schedule tasks. And that was our easiest way to create database writing and Moodle APIs to do everything we wanted to do. An assessment setting, schedule task where we decided these were summative assessments. We wanted a specific set of settings so we'd go with those. Assessment dates were to be passed from Moodle back into. And we did it by creating a link code. That link code represented the module, the semester and the academic year and which assessment it was, number one, number two. And that could be pasted into any assessable activity. Assignments, quizzes, forums, blogs, anything that could be assessed can have that ID number put in. And then we rolled it out. Pilot first. We started off with some staff just using Moodle because they were familiar with it from other institutions or from their formative assignments and you transfer the grades manually. And then rolling it out to a small group and then on to everybody else. And some of my colleagues, one of whom is sat somewhere in the back, I think Maggie, were responsible for doing a whole load of compulsory staff training to bring the staff up to speed with all of this. It did raise a few issues. Starting with a pre-pilot where we didn't have any of these integrations in place. It was just getting people used to using Moodle assignments. And then handling offline activities. We started by just saying, well, get rid of all of the submission types. But then Coventry and Catalyst developed their barcode scanner. So we tested that and we've had that in use since about October. Overall very positive. The main benefit being that they're not being a requirement of hopping between the learning environment and the student records to do your assessments. So it all came down to one front end. But we did have a few other fairly major issues that are still going on. I know I've just been up to Roger's talk for what they did at Solent and they had some of the similar ones. The data we get from Central Records, not the best. Practice doesn't always match policy. Dates are supposed to be in there before the beginning of a semester. Practice does not always match policy. So the integrations were written based on the policy and then got adapted to try and match as many different variations of the practice as we can. Or to be honest, I've told staff that's not policy so you can't have it. We're still addressing some of those issues. The accurate data and the policy one. That practice is ingrained. People have been doing it for four or five years. Getting them to change is not easy. There we go. I've caught up with myself. There should be another slide there, I think. There we go. So what we're then doing, one of the bits of practice was some of our staff seem to have difficulty copying and pasting a link code. So they want a button to click that will insert the link code and things like that. We actually released the feedback to students. Feedback and grace to students and to student records automatically after 20 working days. So that's something we need to tweak a little bit.  Anybody who's interested in using Moodle and Mahara, the Mahoodle for this year is being held at Gloucestershire. So if you want to register for it and come along and talk about anything to do with Moodle or Mahara, register on that site. Thank you. I'm here till Wednesday if anybody wants to ask me anything that takes more than six minutes. Any questions? Thank you very much. Thank you so much.


On September 25, scores of migrants courageously crossed the Rio Grande on foot in their pursuit of reaching the United States. Footage from Eagle Pass, Texas showed migrants, some of them traveling with children, walking through the violent river currents carrying their belongings. Some U.S. border patrol boats were also on scene. Thousands of migrants have crossed into the United States in recent days, from California to Texas, with many more still arriving by bus and cargo trains to Mexican border towns on the heels of record migration flows further south, the dramatic increase along the border, notably in San Diego, California, and the Texan cities of El Paso and Eagle Pass marks a turning point after numbers had plummeted in recent months and could create fresh political challenges for U.S. President Joe Biden heading into election season.


Starring Richard Widmar in the Return of the Lodger, presented by the DuPont Company, makers of better things for better living through chemistry. Good evening, and welcome to Cavalcade. This is Bill Hamilton. The Return of the Lodger, a story of Jacob Rees starring Richard Widmar, a rainy night in the year 1896. You're sure it's this police station, Rees? Are the scores of police stations in New York? It's this one. I couldn't forget it. And you still insist I see it at the Sun Godly Hour of 2 a.m.? It's insane. Are you shivering with cold? No, not with cold. I'm shivering with memory. I was here before, 20 years ago. Wet like this. Cold like this. Dismal like this. All right. Too dismal for me. Let's go in, Rees. Malavi. Oh, yes, Sergeant. Lay down them cards. Two more tramps, seating lodging. All right. Through the door, Bums. Find a plank, nobody's sleeping on it, flop. Hey, just a minute. There's something funny going on. You. You're not a bum. That's right, Sergeant. My name is Jacob Rees. I'm a newspaper man. Oh, I've heard about you. You make trouble. Well, not in my station house. How'd you go, Sergeant? Come on, Reformer, out. Take your hands off him.   We might go so far as to say that you're my boy. I'm the new police commissioner of the city of New York. Holy mother. Now take your hands off, Mr. Rees. Yes, sir. Sergeant? Yes, sir. This station house is a pigsty. Clean it up. I will, sir. Right away, sir. All right, Rees. Come on, let's see those homeless lodgers of yours. The sound of sleepiness. The sound of homeless men. The unwanted of New York. This is the refuge of the city, the offscourings. And yet they are mother's sons. And this is their lodging for the night. Their bed is hard. And I'll tell you that there's no comfort upon them, no blanket, no sheet. They sleep upon the wood of coffins. Hungry and cheerless they lay down to sleep. And cheerless and hungry will they rise. Rees. How do you know these things in the darkness? I know these things because twenty years ago, upon another winter's night, when the February rain drove down the river, I was a stranger and friendless in the city.  How long I stared, I don't know. Then out of the rain there came a voice. Who's that on the pier? Speak up, I'm the watchman. Who's there? I carry a club. I'm doing nothing, watchman. Then show your face to the lantern. Who are you? I'm just sitting here. Sitting? In the rain? Yes, watchman. Where's your home? I have none. I'm sitting in the rain. What are you up to? I'm staring at the water. The water's cold. And it runs deep. I've seen the bodies the harbor brings up. Have you, watchman? I have. But I will not argue with you. You're grown, you do what you must do. Yes, watchman. The rain is more cruel than winter snow. Two o'clock and the weather's fall. The clock can fall and there's no hope left. Twenty years ago I was hungry. I was lonely. I was given over to my own weariness. My clothes were wet shrouds. And the black water of the harbor was lodging for the night. For that night and for all nights. Deep and forever and final. And then, sir, there on that pier I found a living creature even more miserable than I. Well, hello, pup. What are you doing out in the cold rain, huh? You cold, pup? Yeah, I'm cold too.  Put him under your coat. Is that you, watchman? If you put him under your coat, he'll receive warmth from you. And you'll receive warmth from him. Put him under your coat. Why should you care whether we're warm or not? Because of the pain of all living things. What's your name? Jacob Reese. Where were you born, Jacob Reese? Denmark. And why did you come to America, Jacob Reese? Because they said America was a promise. Well, isn't it? I haven't seen it. Dead don't see the promise. Only the living. Put the dog under your coat and go away from the dark water. There's a place I know where you can stretch out on a canvas hammock for seven cents. You got seven cents? No. Would you take seven cents from an old man? I've lived this week on scraps and charity no more. Then go to the police lodging house. It costs nothing. There's a station house on Church Street. And so, Commissioner, twenty years ago, on a night like this night, enter this same place where the sleepers lay on wooden planks. I came with a living creature in my arms. I came out of the rain in the night to this same station house and to this same room. And it seems to me that the voice of the police, Sergeant, here tonight is the same voice I heard twenty years ago. What do you want? Lodging? Through that door. Thank you, Sergeant. Just a minute. Did you hear something? No, sir. I heard something. What's that bulging? What's inside your coat? Open your coat. I should lay my fists on you for that. Take it outside and be quick about it. But it's cold outside. The city keeps police lodging by human bums. Take the dark bum outside. Something to eat? Uh-uh.  I've got nothing. Got tobacco? No, no tobacco.  Liars and fleas. Hey, what are you pulling away from? Your fleas. What's wrong? What is wrong with the fleas? Can't you give some of your hospitality to God's homeless creatures? The police took me in. I took the fleas in. That's right. Thatch. Thatch.  Let me sleep. Thatch, I don't like a cranky man. There's sun and flowers and free lunch in the saloon, so what could be peepish, Dutch?  Granted. And a filthy station house. No argument, Dutch.  This part of it? And a rotten, filthy, hateful country. You shouldn't say a thing like that, Dutch. Why did you hit the tramp? It pleased me so. It was wrong of you to hit him. Nobody asked you. And it was wrong of you to say what you said. Nobody tells Dutch he's wrong. Nobody. I'm telling you. You talk too much. You talk too much. The tramp talks too much. I don't like such people. What's your name? Who are you to ask? Better answer it, young fella. Why? Because it is more healthy. In this rotten place I am in charge. Me.  What for? Because I have something to give you. Oh. Well, my name is Jacob Reese. Then here's for you. Jacob Reese. Come with me. That's enough. Dutch, who started it this time? Not me, officer. This man restarted it. Him and his friend, the tramp. No. That's all I want to know. Look out, Reese. That's one last piece. There'll be no fighting in this large in-house. I emphasize the point. I'll take the skin of the back of the next one of you so start anything. I go back to sleep. You are listening to Richard Widmark as Jacob Reese in The Return of the Lodger, tonight's radio play on the Cavalcade of America, presented by the DuPont Company, makers of better things for better living through chemistry. Twenty years ago, commissioner, in this same room, my jaw swollen, my back raw from the whip, surrounded by tramps and thugs and black-ards and young boys whom I could hear whimpering in the darkness. It was a monstrous place then, as it's a monstrous place still. For the old, it was a school of crime. And for the young boys, a nursery of vice. Yes? Ah, thanks. Oh, sir. Why did he whip us and not Dutch? Because Dutch is in with them? Them? The vicering that runs these lodging houses. How do you know that? Ah, I've been around, Reese. There are young boys in this room, country boys who came to the city for a job. Broke, they came here. And men like Dutch recruit them for the mobsters. Reese, why did you try to defend me? I'm nothing but a tramp. I don't know why. Perhaps, yes, Reese. Perhaps because you are a tramp and should be bitter. And yet you spoke up for your country. I'll tell you, Reese. Me, I'm no good, bone-lazy. But there ain't anything a man can't do in this country if he has the heart and the will. Tonight I... I wanted to kill myself. I? The usual. No job, lonely. Nothing left in the world except this gold locket. Your sweetheart? Yes. Where is she? Denmark, where I come from. Homsick? For her. I could be happy here. You could be. Anyone could be. I don't know. Anyone could be. Look, Reese, a rotten place. There are things wrong here, things like this. The slum tenements, slum people, the vicering. But there isn't one single wrong thing that can't be put right. That's why America's good or wrong gets put right. I, uh... I'd like to know your name. One name's as good as another. Jones will do for tonight. Thank you, Jones. What for? For talking to me. Talk is nothing. You know, Reese, there are doers and talkers. That's why I'm a tramp. I've talked all my life. Will you do? I don't know. I'll try. You try hard. I don't know. I hope so. Listen, Reese. Go and look at a stone cutter. He hammers at the rock a hundred times. Yes. Nothing happens, not even a crack. But the next time, the hundred and first time, the rock splits in two. Yes, I know what you mean, Jones. Reese, it isn't the hundred and first blow that splits the rock. It's every blow that went before. All of them together. How long do you lock it and go to sleep? There's a time in every man's life an hour, a moment, an instant. When his soul is as soft as wax. And in that instant, a man may receive the stamp that fashions his life. That moment, Mr. Commissioner, was my instant. I lay there an outcast. But in that moment, I knew that my life was shaped. Not to be my brother's keeper. To be my brother's brother. To erase the slum that diminishes his humanity. To make a space amid the tenements for a tree to grow for him. For a park. For green ground where his children might play. For clean houses, new houses. For an end to filth in the conditions which generate filth. I knew then. A tramp told me. I placed my hand upon a little locket of gold and I fell asleep. Reese! Who are you? What's wrong? Your locket. What? It's all him. Take it from your neck. Dutch. Dutch, wake up. Dutch, you're only pretending to be asleep. Dutch, I want my locket back. Give me up your bum and let another bum sleep. I want my locket. I want my locket. Give it to me. Give me my locket back, Dutch. Give it to me. Give it to me. So you're making trouble again. Dutch stole my gold locket. Gold? Yes. Yours? Yes. And you got it? My sweetheart and Denmark. Well, don't you believe me? No. There ain't any lockets. There is you stolen, you yourself. I did not.  You demand? What do you know about this, Dutch? That's a lie from beginning to end. Here's the truth. I can vouch for the truth of what Reese says. A tramp vouchers for a thief. Stop the laughing. Stop it. One more sound, I'll throw every last one of you in the cooler. Come on, Reese. What are you going to do? Come on, Reese. You'll see what I'm going to do. Oh, you're pulling me. I came here with a dog. Now I'm throwing you back to the dogs. Now I don't ever want you to show your face in this station house again. And I make sure you don't forget here's a swift kick to remind you.  Commissioner, he'd waited for me in the rain. I was his only friend. And when he saw his friend attacked, he defended. Bite me, will you?  Not forgotten. And the memory of it brought me back tonight. Sound of the sleepers. Listen to that sound, Commissioner. Twenty years ago and now, the same sound. I have the memory of that sound to thank. The memory of a little dog and a tramp and an evil man. Those memories, Commissioner, have been with me always. The tramp was right. There's no wrong in America that cannot be made right if men have heart for what must be done. Commissioner, I made you come on this night at this hour because there's danger in this room. Typhus, ambitiousness and crime. Reese, I'm grateful to you. Sergeant, I'll ask you now for a lantern. Yes, Commissioner. Yes, Sergeant, right away, sir. Sergeant, aren't these men given a bath before they lodge here? No, sir. Won't you give them a cup of tea or a slice of bread or even a drink of water? No, sir. And aren't blankets provided to cover them? No, sir. Raise it high, Malevi. Only what you see, Mr. Commissioner. Sergeant, the name of God, what are those children doing here? Sleeping on the boards with the others, sir. Why aren't the boys, the children, separated from the tramps and the thieves? Those are not my orders, sir. Those are your orders, Sergeant. Now. Yes, sir. Reese? Yes? I'm grateful to you. What for, Commissioner? For bringing a rotten situation to my attention. Yes, it is a rotten situation. And I know that you'll make it into a decent situation. That's a good deal of faith to put on a new police commissioner. Not when the name of the police commissioner is Theodore Roosevelt. You see, I have faith in you, sir. The land is large, Mr. Roosevelt. And perhaps this incident is small. And yet, small things are also symbols. The small symbols and the large symbols. The wrongs that are put right, the abuses that are corrected. The slums that will go down, the houses that will go up. The cities that will be cleansed. The never-ending struggle by our generation and each generation that follows. For now and for the future. To build a free land. A good land. Thanks to Richard Widmark and our Cavalcade players for tonight's drama about Jacob Reese, of whom Theodore Roosevelt said, if I was asked to name a fellow man who came near us to being the ideal American citizen, I would name Jacob Reese. Tonight's Cavalcade play, the return of the lodger, starring Richard Widmark, was written by Morton Wishingrad. Theodore Roosevelt was played by Ian Martin. Arthur Cole was the tramp and Edgar Staley the watchman. The music for the DuPont Cavalcade is composed by Arden Cornwell, conducted by Donald Borees. This is Ted Pearson speaking. Next week, the Cavalcade will present the distinguished American actor, Walter Hamden, together with the radio and television child star, Ivan Curry. Our play, Footlights on the Frontier, is a heartwarming story about a little boy who grew up to become one of the greatest stars of the American theater, Joseph Jefferson. Be sure to join us. Cavalcade of America is directed by John Zollard. Comes to you each week from the stage of the Longacre Theater on Broadway in New York and is presented by the DuPont Company of Wilmington, Delaware. Richard Widmark appeared by arrangement with 20th Century Fox, producers of House of Strangers. This is NBC, the national broadcasting company.


Okay, good afternoon everyone, my name is Gaurav and today I'm here to talk about Share Chat and Modge and there's a ticker here which says I have 15 minutes to tell you about a platform which reaches about half the Indians who are online, right? So instead of running through the entire laundry list, there are only four things that I want you to take away from this. Nothing more, nothing less. If you can walk away from this session over the next 15 minutes and remember four things that I want to tell, I think I've achieved my goal for the day. But I'll make it more interactive, hopefully more fun. And I'll ask you some of the questions, some of the very basic ones, right? What percentage of India today do you think has access to internet? You can just shout out the answer. What percentage of India today has access to the internet? I heard 56, okay? Somebody from the back? They're here, 80? 75, okay. What else, sir? Do you have a guess? And I loved it when you said, Why aren't we only talking about MNC? So today, or the next 15 minutes, 14 now, I will only talk about an Indian company built proudly by Indians for India. About 50% of India today has access to internet through, primarily through their mobile phones. That puts the number at about 700 million everyday. But the important question I want to ask is, why do you think this Indian of today is buying a smartphone with his or her hard earned money? Of course the phone cost has gone down, the data costs have become nearly negligible. But what is the reason, the number one reason you think that an Indian of today in a tier three city of today is wants access to internet? Any guesses there? Sorry? Can you say that loud please? Entertainment, by the way that was not planted, she doesn't work for me. The answer is entertainment, entertainment, entertainment. Today's India is buying smartphone is consuming internet because he or she wants to be entertained. They want to be by the way entertained in the language of their choice. I may be living in Bangalore, I may be comfortable talking in English and Hindi, but when I sit back and relax on my way back home in a cab, I want to consume content in Kannada which is my mother tongue. And that is what the behavior of today's India's internet is. And that's what we are here to talk about. This by the way blends beautifully with the massive rise of short form videos we are seeing in the country today. This is not only an India phenomenon, you would have heard of a company called Tiktok that is making waves across the globe, giving CPS nights to possibly the big giants of the US because people just can't get enough of short form video. India is no different. I can promise you there are some of you right now who are bored of this presentation and are looking at a short form video on your WhatsApp or on your Instagram reel or on your YouTube shots. And that is the advent and the sort of blast of short form video consumption that is happening in India today. It is not the future, it is the present while the future links even more brighter when we talk about short form video. But coming back, only four things I want you to take away from this. Number one, what is share chat and merge? Who in short hands, how many of you right now have share chat or merge app on their phone? No one right? Zero. I was expecting two hands there, they are part of my team but it looks like they have uninstalled as well. Okay, then my question is who are these 325 billion people who we say are part of share chat and launch and who are consuming more than 35 minutes of our content every day and they open their app about eight times a day to consume the content to engage with their friends to follow the influencer they so love. Why isn't any one of those 325 million people in this room? Isn't it a bit surprising? And that is where I think this quote that I find very dear is that anecdotes are always allowed in the statistics, right? Possibly none of us sitting in this room right now is not a target audience for share chat and merge because we consume content on one of those American social media companies because we like consuming content about high-end fashion stuff or about vacations but trust me, there are millions of Indians out there who are consuming or who have the deep desire to consume the content they like in their own language. We may find it cringe but let me ask you, is our job as marketer not to communicate a grand story to our consumers or is it only about creating that emotional add about climate change which helps us win those cans of water? I think it is the former and that is the number one thing I want you to take away with. Share chat and merge today reach more than 32 crore people in India. We are the third largest digital ecosystem in India today. We are by the way growing massively. Share chat was founded about eight years back by three IIT Kanpur graduates who thought there is a desperate need for something very Indian, something very vernacular because people of India are no longer satisfied with what American social media companies are offering them. Mohaj is our short-form video player. Ever since the Tiktok band, we have by far the largest short-form video company in the country today. We have more than 20 million users coming to our app every day and that puts us right at the very top. Of course, the heart and soul of every short-form video player is a world-class recommendation system and there is no tech presentation today without using the word artificial intelligence. So let me use it. AI powered REXIS which ensures that the next video that is shown to the user engages them at another level. So this is the number one thing I want you to take away from today. This is how our user base looks like. Share chat as an app is very tier two and tier three strong. As you can see, more than 90% or 85% of our users are coming from that. Mohaj on the contrary is very herbal, very Gen Z and millennial and that is I think one of the myths that I want to clear out or bust today. A lot of times I hear people use these two words share chat and moj interchangeably. These are two different apps. These are two different ecosystems reaching out to different set of audiences. Now what does it mean for you as marketeers today? Is that if you do common buying across these, you can see how you have access to people across age groups and across all the tiers of the day. Okay, so everyone with me, the second thing I want you to take away. Can I request everyone to take out their smartphones on their WhatsApp search for share chat. On WhatsApp, please do a search for share chat. And what I'm assuming or guessing is that there will be a lot of messages that you would be seeing because some of your family group, some of your dear friends, some of your college, Landa group or your one to one messages would have had some forwards from share chat. Let me give you some statistics around it. We joke internally that if share chat was to shut down for a day, it would lead to a significant reduction in traffic on WhatsApp India. That's how big we are. We are possibly the biggest content aggregator for WhatsApp today. And that's why I asked all of you to search for it. For the first time now, and we have now opened it up, this product offering outside our beta phase. But today we are now offering all these shares for monetization. Here's what I mean. Today about 10 million people come to share chat every day, consume content which may range from a good morning messages to a shiree to a husband wife joke or whatever they like. And the content which they like most, they actually do a one click share on their WhatsApp groups. And that is why I was confident that when you search for share chat on your WhatsApp, you will find some of the other content. Now imagine this is happening by, this is being done by 10 million people about two to three times every day. And that's the power of share chat content. Now imagine if all those good morning messages that are going or all those shirees or all those jokes that are going out there from share chat to WhatsApp, you could have your brand slap at the bottom of it either in form of a GIF or a banner or a six second pre-roll video. This becomes the world's only way to advertise on WhatsApp. And that is what the second thing I want you to take away from this presentation is we are now offering WhatsApp branded shares as a way to reach, to make your brand reach millions of Indians in possibly the most efficient way. Here's what it looks like. These are real examples. The first one is Zomato. Every time there was a festive share that was done from share chat to WhatsApp, there was a Zomato banner down at the bottom. The second one is how it would look like on the actual WhatsApp screen, which includes a click to action to a ITC store. And this is by the way a mock-up. This is a creative ideation that we were doing with the ITC team. So imagine reaching 30, 40, 50 million Indians on a single day running this campaign for 15 days at a stretch and imagine the amount of brand lift, brand message, recall or the actual click to action you could get from the WhatsApp branded shares. So this is the second thing I want you to take away from this. Third one. Like I said, Internet of today is no longer urban. It is no longer male-dominated. It is no longer English and Hindi. In fact, any data that you refer to will tell you that a bulk of the India's Internet users, and I say bulk, I mean majority, I mean more than 50%, actually are consuming content in their own language and that's where regional influencer ecosystem is very, very strong. And we at ShareChad and Moj are very proud to have worked with these influencers over the past eight years and have good relationships with more than 700,000 such influencers today. Now imagine leveraging those influencers as a one-stop shop for your next marketing campaign. This means you don't have to engage with any other influencer agency quote-unquote. You do not have to engage with a creative agency quote-unquote who would work on a creative ideation. We have invested in teams and processes at ShareChad wherein we work with you right from creative ideation, which hashtag challenge should work well, which jingle works well to selecting the influencers to giving you the choice to choose from that list of influencers and going all the way to ensuring that that campaign delivers 100 million, 200 million or 500 million views. So that is the third thing I want you to take away. When you think of ShareChad and Moj, think about how strong and important regional influencer marketing is and we are at the forefront of it. These are some of the examples. To reiterate the point, think about your next user, think about their behavior, think about where they spend time. How do they like to consume the media of today? Are they any longer interested in a 15-minute YouTube video with a pre-roll ads or do they want to engage with a 30-second short video of the influencer who speaks their language and then think how you can leverage that influencer for your brand? The last thing that I want you to remember, India Internet is going through a native language revolution. There is no other way to put it. Like I said, it is not the future, it is the present. Any data that you refer to will tell you that vernacular has taken over India's Internet. We again are at the forefront of it. Let me show you some numbers. This is our top five languages by user base. Hindi, Tamil, Telugu, Kannada, Marathi are our top five consuming languages. But if I were to show you the entire data, you would realize that I would have audience even in Gujarati, even in Bhojpuri, even in Urdu. And that's how powerful this native language revolution is. I just pulled a screenshot of some of the states and the list, of course, is long. Cannot be fit on one slide. But what it essentially means is that next time you are thinking of reaching out to your audience or doing a media mind, remember, we are not a subset of the large American companies that are out there. We are very proud to say that there are incremental users that are only available on our platforms. There are some of the numbers for some of the states that have put it out there. But it is not that you as a marketeer should think that if I'm buying on these platforms, I anyways have access. Because trust me, contrary to our intuitive belief, some people do not like those platforms and they only like to be on the platform where they are able to connect with people, real people, who speak their language. So this is the last one. That's all the board says. My time is up. But me and my team are available for any further questions. I consciously did not go into the details of this. The only four things I would like to repeat for you to remember. In March today, we reached 32.5 crore people on a monthly basis. These are engaged users coming to our app and spending upwards of 30 minutes every day. There is a native language revolution happening in the country today. We have incremental users that you will not find on any other platform. Short-form videos have taken over the world and India has no exception. For any short-form video, regional influencers are the bread and butter. We have strong ties in relationships with 700,000 of those. And lastly, the next time you receive a WhatsApp forward, do notice the top left-hand corner. I can promise you more often than not, it will have the shared chat lag. Thank you very much.


I guess many of you are using PGP here. If you do, raise your hand, good hackers. So if you want an introduction to someone new that you know someone else has a key to, you usually have to do the little dance, ask for a key. Do you have a key to that in that person? Because that's, well, let's admit it, pulling keys off key servers is boring, but that's the way you usually do it. What if I told you there is a better way? What if your friends and friends of friends can attest that a certain key actually belongs to someone in a more nicer way than just attaching signatures to PGP keys? Our next speaker will introduce you to ClaimChains, a system aiming to solve this problem. Please give a warm round of applause to doctoral researcher, Marius Kutakias. Hello, good hackers. So Hades has given a great description of what we would be talking about. It's called ClaimChains. It's a modern key distribution mechanism, protocol, and implementation that we've done in collaboration with Bogdan Kulinich and Carmela Troncozo from EPFL, and George Zanezes from University College London. I'm Marius Kutias again from University College London. So in a few words, ClaimChain is a decentralized public key infrastructure that supports privacy-friendly social verification. And if you've read the description of our talk, you know that we will be mentioning a lot the word blockchain. So it is a hype, of course. Blockchains have been used in many applications. But they actually provide some very good properties that might be useful for public infrastructures. For example, they provide high integrity for the data that we store. Past data become number proof. It's very difficult to modify them without overwriting the history. And we can also be sure of the authenticity of the data because of all these cryptographic signing and hashing going on. And by definition, blockchains are decentralized. So they can provide good availability. You can go to any Bitcoin full node, for example, and verify your transactions. They are sensitive resistant. If you want to bring Bitcoin down, you have to go and bring every full node down. And they've solved the problem of global consensus through this lottery mechanism of proof of work. The more resources you distribute, you contribute to the systems, then the more ballots you get in the lottery, more tickets you get. Oop. So the first generation of blockchain-based public infrastructures are based on such proof of work blockchains, for example, namecoin and blockstack. They have replaced the kind of use the Bitcoin token, the cryptocurrency tokens, for identities. Therefore, you can buy identities, you can sell them to others, et cetera. And they belong to you. So this is a more powerful abstraction for identities compared to PGP keys, as we use them today. And they also provide you with a global namespace. If you have this identity in namecoin, it is you. Everybody will recognize you as the owner of that identity. On the other side, they provide no mechanism for social validation. If somebody claims to be, for example, Alice in that system, how can we know out of all the people who claim to be Alice that this person is actually Alice? There is no kind of trust mechanism. All transactions are public, and this has some privacy implications. For example, you might be able through the transactions to infer that some identities are linked to each other. There are some inherent fees that users have to pay for buying coins and for all the transaction fees. And of course, it's very resource expensive with the proof of work. There is a 10-minute latency for every block to be a specific number of transactions that can be included, and so on. Then came the next generation of public infrastructures and blockchains with key base and the conics that can be deployed by email providers, for example, IZMB and Gmail. So what they did, they replaced the transactions block with a Merkle prefix tree. I'm going to describe in a bit what this is. And what they achieve is accountability for the providers with regards to the keys they publish about their users. So imagine, for example, that Gmail is using conics. You could go and retrieve the public key material for a Gmail user from the conic server, and you also get some proof that this is the same key that everybody's getting at that specific time. So you also have easy discovery, because you know, for example, that Alice at Gmail belongs to the Gmail provider, and you go directly there. And it's very efficient because it's only Google that maintains and constructs the structures, and they can provide you with very efficient proof in a few kilobytes that actually this is the right data that you get. On the other side, they do not prevent evocation. They just make it detectable at a later state, which might be already too late. And to an extent, they are centralizing the public key infrastructure, which opens them to attacks, for example, because they are a single point of failure. If the Gmail conic server is down, then you won't be able to get the PGP key material for the Gmail users, and also puts the providers in this privileged position to perform surveillance with regard to who is trying to communicate revealing the social graph that the users would like to hide, et cetera. So the Merkle binary prefix tree that I mentioned before is a Merkle binary tree, as you see. But the difference is that in order to sort the leaf nodes when we are inserting them, we are using a very randomly random function. Instead of a hash, we use this very randomly random function. It is a function that produces a unique output given a private key. So imagine that I have a private key that is compatible with this very fine random function. I can produce an output that looks random to everybody. You cannot guess it. But if I give you the public key, you can verify that this is the unique output. And this, as a result, when applied to Merkle trees, assures us that everybody who will search for a specific label will end up to the same leaf node in the Merkle tree. Therefore, achieving non-equivocation. I cannot, if two people come to Conics' Gmail provider and ask for Alice's Gmail, because of these properties, they will both get the same leaf node. Now, claim chains. How are we using the Merkle binary prefix trees? And what are we doing different compared to key-basin Conics, for example? What we do different is we push for decentralization by having the users host the claim chain by themselves. So we have a claim chain for each user, or for each of their devices, or for each of their identities that they don't want to connect. For example, you have Alice who has her own chain, Bob has his own chain. And Guy Fox, who could be anyone in the internet, even Alice, has a different chain. There is no consensus. There is no global consensus. Blocks are repeated as needed. You just generate the structure, sign it with a signing key, and that's it. Everybody can verify that there is a sequence. This sequence is valid. Imagine now that at some point, there is a fork in a chain, because two valid blocks originate from a given block, then this can be interpreted as a compromise, because somebody has got my signing key and published something different, or it could be that I've tried to evocate to one of the readers. And finally, we've also added a fine-grained access control mechanism based on capabilities that allows the claim chain owners to select who can read a specific claim. And through the non-equivocation of the Merkel prefix trees, we assure that all readers get the same content. Yet we need a way to propagate this information, because how do we know of updates of our friends? How do we find out how does the key distribution works? We have introduced this mechanism of cross-hassing, where we include a vouch, a stamp, of the latest state of the claim chains of our friends. So you see here, for example, that Alice includes an attestment for Bob's latest block and Guy Fogg's latest block, and Bob also includes a statement, but at a previous point that he was aware of. It might be stale a bit, but that's how consensus and propagation works in these systems. So we have propagation of key updates in cliques of users, in groups of users. This is how gossiping works in the real world and between real humans anyway. We don't just append cryptographic signs on keys of other users, but we also vouch for the latest state of their view of the world. And we can use this cross-hassing mechanism for introducing friends, for social validation on a web of trust, while at the same time preserving the privacy of the social graph of the claim chain owners. Another view of the claim chain properties, so claim chains are high integrity authenticated data stores, high integrity because of the block chains and the Merkel prefix tree authenticated because of all the signing going on, that can support generic claims. So we've decided to use this for a public infrastructure. You can use the claim chain structure for building access control delegation or command and control for your botnets or whatever you might come up with. At the same time, we assure privacy of the claims that are published, even though everything goes public. It would not reveal any information about the content of the claims or about the readers of the claims. And we do that via capability mechanism that we're going to describe in a bit. Privacy sometimes can mean a key vocation. I could present, I could encrypt different things to different readers. We, again, prevent that. All the readers get the same view. The crosshousing mechanism enables the propagation and vouching of the latest state of linked claim chains. I've mentioned that the evocation attempts and compromises produce non-reputable cryptographic evidence, the claim chain forks, and non-reputable cryptographic evidence. It means that we can take them. They are self-sustained evidence that we can share with the world that we've observed two blocks originating from a specific block in time. Therefore, something is wrong with that claim chain. Now, with regard to deployment, and we've done lots of work in evaluating how a claim chain can scale and how effective it is with regards to key propagation, et cetera, and what are the bandwidth requirements, how long does it take to compute the structs, et cetera. You can find all this information at claimchains.github.io page, where we have our paper. Claim chains is very flexible in terms of deployment. It can work in the federated scenario, like in Conics, or it can work with high availability online data stores when we just go on and upload all of our blocks. Or it can even work in gossiping ad hoc scenario when we just append. Do you want to? How do you say this word? When you just include the proofs in the emails that you want, when you attach the evidence that you want in the emails you send with your friends, and we can do that in a very efficient way by including only the claims that we want to include for that reader, plus some evidence that these claims are actually part of the claim chain and the proof of inclusion in the mercenary, et cetera. Now the internals of claim chain, we still have some time for that. The block structure has some claim chain protocol information, like the version, of course, a timestamp, the block sequence index, some nones that we use for achieving an leakability between the claims and the capabilities across different blocks. Claim chain metadata, all the connected identities may they be other claim chains, or a Twitter handle, or an email that the user wants to connect into this claim chain, and some public keys that are needed for the operation of claim chain. We need the public key for signing new blocks, the public key for the verifiable random function that we use for the Merkle prefix tree, and the difficult element key that we use for the capabilities technique. But then, the core element of the block is the block map, where we store all the claims and the capabilities in the form of a Merkle prefix tree. Of course, pointers to previous blocks, that's how we connect the blocks into the block chain. Now if we consider all of the fields on the left as the payload of the block, we sign it and we attach the signature. This is a self-sustained piece of information that we can attach to an email, or we can store in an online data store that we do not trust. And still be sure that no one can tamper that information. If we want to add a claim, for example, we are analysis Merkle prefix tree, and we want to add a crosshash for Bob. First, we need to define the label that we will be using for Bob from now on. It's going to be Bob at riseup.net. And let's imagine that the claim is the latest head. So first, we're going to compute the claim key with a verifiable random function using Alice's private key. And then we're going to put inside Bob at riseup.net plus the nonce, so that we can achieve only capabilities I've mentioned before. Then we can calculate the index of the leaf node. How are we going to store that leaf node in the tree? Simply by taking the claim key and hashing it with the string lookup. And we're going to generate a symmetric encryption key. Again, by taking the claim key k from step one and appending encryption and then hashing it all together. So we encrypt the claim content with the symmetric encryption key that we got in step number three. And we also include the VRF proof that other people can go and get to be sure that the claim key that we've computed in step number one is actually the correct and the only one. So that's how we get the leaf node that corresponds to the cross has for Bob's claim chain. We store that in the tree. Next scenario. We want to add the capability for Guy Fox to read Bob's cross has into Alice's claim chain. First step, we use the Diffie-Hellman to establish a third secret s between Alice and Guy Fox. So we use that third secret into a has, again, along with nonce and with lookup to generate the capability lookup key. That will be the index of the lookup key of the capability claim that we're going to store it in the tree. Nonce is here in order to achieve an leakability and to hide the patterns of how capabilities are added and revoked. We're going to derive a symmetric encryption key as we did before. And we're going to encrypt the claim key from the blue leaf node that we've added before with that symmetric encryption key from step three so that Guy Fox can decrypt it in the future. So we generate that leaf node and we store it in the tree. Now, if Guy Fox wants to retrieve that wants to find out the latest update for Bob in Alice's tree, he's going to do the reverse process. He's going to establish a Diffie-Hellman third secret s between Alice and Guy Fox and get the capability lookup key and the symmetric key in the same way that Alice computed it. And he's going to go to Alice's claim tree, metal prefix tree, and retrieve the corresponding leaf node. He's going to decrypt it with the symmetric key k from step number three. And he will be able to get the claim key for Bob's claim. So far, if you remember, the claim key for Bob's claim includes the VRF, the hash of a VRF. So he's going to retrieve Bob's claim from Alice's metal prefix tree and decrypt it using, yeah, again, he can compute the VRF key because of step number four. And are we done? Not really. He needs to use the VRF proof that is embedded into the decrypted claim in order to verify that actually the VRF proof that he gets is the only one that Alice could have produced with her VRF private key. I know it's, yeah, we went through that very fast. But again, all this information is in the paper. And you can take a look at it. Or please come find me after we're done. I have more slides that explain how proof of inclusion work, how proof of absence work, et cetera. Yeah, one thing I should have mentioned is that in step number four, if Guy Fox tries to retrieve a capability block and cannot find it, it means that Alice has not given to Guy Fox the capability to read the claim about Bob. Or at that point, Guy Fox cannot know whether a capability for Bob exists at all. Now, we've submitted this talk for the CCC resilience track. And we understand that this is academic work, to an extent. But we do care about resilience. And we would like to share some of why we decided to do that. First of all, we started with a field research to understand user needs. This was done by some researchers in Paris. Later on, projects that care about resilience need to be open to collaborations with communities that are already working on these problems. And we've done that, for example, with another organization in Germany. And we're in close collaboration with Autocrypt with that. And we've used techniques from that they are actually, again, very, very well used. OK, sorry. So in academia, there isn't this techniques going on now in applied research that is pushing for formally verifying the properties and the code that you are producing. And for claim change specific, we have formally defined all the security and privacy properties using cryptographic games. So we know, for example, that we provide non-equivocation under what terms and that we can provide unlicability across blocks again because of this and this and this cryptographic game that we can combine together. And we also have a formally verifying implementation of our cryptographic components in F-star. So you can go on and find the microprefix tree and the VRF function in our GitHub repositories. When it comes to resilience, we need to know of how our systems can scale. And therefore, we've used simulations with real-world data from the Endron data set. This is a leaked email directory from a company called Aeron. So it's usually used in the academia for when we need to simulate real-world communication patterns. And we've used this for calculating the efficiency of the cross-hassing protocol in propagating the latest state of other people's key material. When it comes to interoperability and plans for gradual deployment, as we've mentioned, claim chains is very flexible on how you're going to deploy it. We've chosen to be, and we know, for example, we haven't done much yet, but we know that when it comes to actually starting to implement it to give this to users, we need to be compatible with all existing email encryption applications. So for example, we want to be compatible with the GNU-PG agent. Again, something that is very important. I don't think we've done great work here, but usability of email encryption. How do you perform key management in a way that users can understand and not do mistakes? What happens when you need to revoke a key or there's a key compromise? How do you communicate with the user and how we can act upon that? Yeah, there is a great debate that is going on on that. And unfortunately, we cannot say that we've solved this at all. We focused on coming up with the structures and the properties and simulating how claim chains can scale and work effectively. Hopefully, though, we've been able to do all of the above because we are a multidisciplinary team in X-Leap. We've got sociologists. We've got philosophers, cryptographers. And it's great to have European projects that are focused on privacy and secure communications. And they can actually use the knowledge of all parties for that. And I think this is also pushing for open innovation. All of our material reports and source code is open to the public. And everybody can go and take the claim chain structure and use it for other types of applications. So this is how we can extend claim chains. Now, so we have a bit of time for questions. Thank you very much for your time. OK, we have four microphones here in the hall. Please line up next to them. Thank you again very much, Mariusz. We do have a question from the internet. Signal Angel, please. Yes. As far as I understand, to use this system, you both have to do the signing dance just as with GPG, but also to ask your friends to give you read access to parts of their social graph. Isn't that even harder to use and scale than GPG? Your understanding is correct. We still need to do these crazy dance thing and ceremonies and key signing parties. If you want to be sure about that the other person, that you have the right claim chain for the other person, but we believe that through this mechanism of introductions, it might actually, let's see how it works. So this is part of the simulations. And as you can see on the left, we simulate the completely centralized scenario where we just attach introductions in emails. And we see that it kind of works without having to, if you trust the person who is introducing you to the other participants in the conversation, then we say that we can have a good status of emails going out encrypted with the right keys. Microphone number one, please. I'm interested in the expressiveness of your capability-based access model. Do you support things like groups? Do you support revocation of credentials? Do you support sort of delegating, right access, things like that? You can do all that. This is a very, yeah. What we do, for example, we say that you can use Sekpal semantics, and then you can do whatever you like. Press hold revocations, and all that. You can build this on top of our struct, but we haven't done it now. Microphone number two, please. Use SHA-256 for both lookup and encryption key generation. How difficult would it be to change it, provided it's broken one day? Ha. Given that we have a claim chain protocol version somewhere at the top of the block structure, that's how you would probably change it. But no, it won't be easy. Thank you. Microphone number three, please. Hi, thank you. Great talk. I want to ask about the crypto bit and key derivation process. Why are you using SHA hash function to derive keys, not some key derivation function, like HKDF or PBKDF? I think it's for simplicity reasons. But yeah, I don't have an answer on that. Probably what you're suggesting is better. And would you like to discuss about it later on? Of course. Thank you very much. We have time for one more quick question from the internet before we have to close. Yes. How is privacy of the social graph, the cross hashing, ensured again? I'm not sure I fully understand that. The privacy of the social graph, how do we protect that? The privacy of the social graph, the cross hashing, how is this ensured? OK. So if you take a look at the when we add a claim, the actual content of the claim that we put in our Merkle prefix trees is encrypted. And it does not leak any information about the label or the content of that claim. And because of the capability mechanism of allowing only a specific number of readers to read a specific cross has, I think that's how we achieve the privacy of the social graph. Thank you to everyone. Sadly, we ran out of time. But Marios will be here for a little while longer, so you can catch up with him over a chunk or a beer. And well, thank you again, Marios.


Breast cancer continues to be the most common cancer diagnosed in females in the United States. In 2023, for example, we expect approximately 300,000 new invasive breast cancer diagnoses in the U.S. It is not a disease exclusive to females. I think that is a common myth. In fact, about 3,000 of those cases, around 1%, will be diagnosed in men. However, certainly it is females who are at most risk, and we estimate that approximately 13% of females, or 1 in 8, will be diagnosed with breast cancer at some point in their life. There was certainly a large increase in breast cancer diagnoses in the 1980s that kind of corresponded to when we really started integrating population mammogram screening. And then it was pretty steady. And in the mid-2000s, actually we're seeing another uptrend in rates. And we think this may be related to excess body weight, particularly among post-menopausal women, potentially changes in reproductive trends, such as later child births. And in general, we're seeing an increase of approximately a half percent per year. And certainly better understanding how certain lifestyle and or environmental risks are contributing to this is very important and certainly an active area of research. So the two most important risk factors for breast cancer are being born female and getting older. In fact, 50% of breast cancers are diagnosed in patients that have no other identifiable risk factor except for that. However, we do know that certain things will increase your risk. These include family history of breast cancer, a known pathogenic genetic mutation, a personal history of breast biopsies that demonstrate atypical lesions, such as atypical ductal hyperplasia or lobular personum in situ, having dense breasts and certain hormone factors, essentially your lifetime exposure to estrogen, as well as some modifiable factors like lifestyle factors like excess weight and not getting enough exercise. Well, when you think about how family history modifies risks, for example, one affected first-degree relative can increase a personal risk by about two-fold, whereas two first-degree family members on the same side will increase an individual's risk by about four-fold. So it's the number of relatives on the same side of the family and how close they are to you, i.e. first-degree, second-degree, etc., that really clarifies the risk associated with that family history. Genetic mutations are problems with genes or your DNA that is passed down from parents.  The genetic mutations explain really a minority of breast cancer cases in that we find a mutation in less than 10% of patients who are diagnosed with breast cancer. However, it's important to detect them because patients who have these mutations can have substantially elevated lifetime risk of breast cancer and other cancers. The two most common genes associated with breast cancer are BRCA1 and BRCA2, and families with these mutations have up to a 70-80% lifetime risk of getting breast cancer. Other genes that may contribute to breast cancer risk in our less-penetrating group CalV2, ATM, and some mutations in CHEC2 and several others. The lifetime risk in these patients ranges between 20-50% depending on their family history and where the mutation is along the gene. But the key in uncovering these is that there's specific elevated screening recommendations in this population. And sometimes we even consider prophylactic surgery in these patients to really significantly reduce that risk. So oftentimes a family history will tip a primary care physician on to offering it for a patient. So anyone that has a kind of pattern of cancers in a family will certainly identify individuals who should get tested. But really anyone can get tested and a large panel of genes is around $200 or $300 out of pocket if your insurance company doesn't cover it. Everything that we've talked about with the family history, the genetic mutation, being a female, these are things you can't modify. The things we can modify are our weight, and this is particularly in postmenopausal women. So prior to menopause, your ovaries are making the substantial amount of estrogen in your body.   So for postmenopausal women, weight loss is very important in decreasing your risk of breast cancer. Also alcohol in excess of more than two to three drinks per week or one beverage per day. And then exercise. Exercise is the most significant lifestyle factor that can decrease your risk of getting a cancer. This is in many cancers that we see this, including GI cancers, colorectal cancer, and certainly breast cancer. And we've also found that exercise will decrease your risk of a recurrence if you've had one of these cancers. We recommend you get at least 30 to 40 minutes of exercise a day, most days of the week.


Whether you are managing crops, trees, or native plants for wildlife, there are herbicides that can help you achieve your management objectives. Grass-selective herbicides such as coethydom and sephoxydom can be used for controlling grasses and broadleaf food plots, as well as promoting broadleaf forbs in early successional areas. Herbicides such as 2,4-D, atrazine, and dicamba will target broadleaf plants and they may be used in food plots planted with species such as millet and sorghum. Blyphosate is one of the most commonly known broad-spectrum herbicides that can be used to control a wide variety of plants. There are several trade names for each of these chemicals and each one may have different levels of concentration. Always be sure to read the label, follow instructions carefully, add suggested surfactants, and then spray at the recommended rates.