 Hello, everyone. Thank you for joining us today for the session. I would first like to start by introducing our panel. Edard, he works as a products and research manager at the user group Wikimonimento Brazil. He has been associated with Wikilabs Monuments for the past three years. More recently, he has been working on a mobile application for Wikilabs Monuments that will make finding and uploading photographs for the competition more accessible. Jeffrey has been a volunteer with Wikimedia Uganda since 2014 and has organized Wikilabs Monuments in Uganda since 2017. He has also been associated with other Wikilabs competitions, such as Wikilabs Earth, Wikilabs Africa. Kimo works with Wikimedia Finland and has worked with Wikilists on categorization, maps, and so on. He has also organized Wikilabs Monuments in Finland in the previous years. Mikola, our last panelist, he is a member of Wikilabs Monuments Ukraine, organizing team since 2012 and is the vice chair of board of Wikimedia Uganda. We also have SEAL from our Wikilabs Monuments international team helping us with the questions in the chat. So in case you have any questions, please feel free to add it to the etherpad or the feed loop chat. We will get to it at the end of the discussion. And coming back to me, I am Misha Murli. I am based in Delhi, India. And I've been working as the DEI researcher for Wikilabs Monuments since 2021 and will be moderating today's session on understanding diversity, equity, and inclusivity in Wikilabs Monuments and federated campaigns at large. As part of this process, I have spoken to many Wikilabs Monuments national organizers and other Wikimedia affiliated Wikimedians about the experience of organizing this digital photo competition in their countries. These conversations made me realize diversity, equity, and inclusivity is an ever evolving process. What might be applicable to one country may not be so for another. So our approach to understanding and finding solutions to such issues have to be specific to the region or country in question. So today we have our panelists sharing their experience of hosting Wikilabs Monuments in their respective countries and if you are new to Wikilabs Monuments or would like to know more about it, we have our Wikicommence page. And you could also refer to our previous Wikimedia session that included a discussion for new organizers. So let's begin. So my first question to our panel would be their experience with representation of local monuments and communities in the competition. So according to you, how important are local contexts in understanding heritage and how do you ensure maximum participation from local communities? Hedda, would you like to go first? OK. I think it's important to take into consideration that Wikilabs Monuments is a competition, a contest born in the global north and that implicates in a set of assumptions. For example, the easier access to photograph equipment or a more stable internet connection, for example. Discussions around what constitutes a monument and how can we improve the impact of the competition results, for example, by highlighting monuments that don't make the cut of beauty in the main prize but denounce the abandonment of the state or institution responsible for those monuments are also relevant to taking into consideration when you are dealing with local contexts. Thank you. Jeffrey, would you like to go next? Yeah, thank you. So yeah, I think Wikilabs Monuments really is all about sharing our cultural heritage. And I think cultural heritage is really kind of local at the local level. Like what is a cultural heritage site in Uganda may not look like a monument to someone who lives in another country. I think we have to really contextualize it at country level first. So what we have done in Uganda, we have worked with the Uganda National Museum who helped us to come up with a list of cultural heritage sites and monuments in the country. But this also has to be kind of communicated with the participants that these are really monuments and cultural heritage sites but also the jury who judge the photos at the local level because without understanding that they may not, yeah, they may discard the photos thinking it's not a cultural heritage site but when it is really very meaningful to people who live in that particular location and are using this as a monument. But also I think representation in terms of local communities also have to make sure that more countries participate in wiki lives monuments. When you look at the map that is on wiki lives monuments there is very few countries participating in wiki lives monuments in Africa. So how can we get that more countries to participate? We need to reach out to new people and encourage them to organize wiki lives and monuments in their country. So the more countries, the better. So yeah, we need more participation to increase representation for local communities. Thank you, Jeffrey. Kimo, would you like to come next? Yeah, I think that in terms of accessibility the most biggest barriers are technical ones. It is kind of the first barrier which blocks people to participate in. How they can technically find the monuments but they sold photograph and whole tape for Google and like that. But then there is kind of things like inclusivity which is in local heritage context that what can be included as a monument in the competition but local heritage groups think what are important. And in that context we have been trying to select some groups each year and find what they think is interesting and what cultural organizations, formal cultural organizations like museums in that area and create interesting lists and hope and help that those local groups will spread the word and find new people to participate. But this is kind of that we select only a small geographic area in Finland each year because in that kind of work we can scale to whole Finland. So we create one area per year and in next year we move to the next area and next local groups. Thank you, Mikolav, please go ahead. Yes, so on Mikolav's monuments, Ukraine side, we had a challenge of starting with monument lists because when we started the contest in 2012, our government monument lists were of pretty bad quality and the monuments were not very well detailed anywhere online. So we had first to start an effort by getting this monument list from local authorities and we were very conscious that we were not equally successful everywhere in the country. Some regions had much better details than the others, so depending on where participants live, some of them might have 5,000 monuments and the region others might have just 100 monuments. Not that there are less monuments, but that we don't know. Another dimension for us was what is on this list and what is not because of the history, because of historical reasons, typically from communist times. We noticed that we have too many communist monuments, most of them were being demolished or rethought like Kalenin converted into Darth Vader statue during the decommunization campaign. So it might be, it was interesting for us to document the monument as it existed, as it was demolished and what happens next. And we had also kinds of heritage that was not on the government list, probably deliberately, probably by a mission. And we teamed up with partners, for example, on Jewish heritage or for the monuments that risk destruction. And we worked with these partners to add additional items so that we know that these sites are important to people. We know that they were omitted from the government list. And sometimes after Vards, they found their place on official lists and it's pretty good achievements that we managed to raise awareness. Thank you. So what we get to know is, you know, what is a monument for one person if in one country may not look the same in another country? And that is something that needs to be kept in consideration along with the fact that sometimes national or official lists are not adequate or not readily available for us while hosting this competition in our regions. So that also needs a lot of work from our part to get official lists and get them, meet them accessible. But what is one major issue that most people face is the technical end that, you know, even with the resources available, the technology may not be as accessible as we would like. So that brings me to my next question that, you know, given that Vicky Lam's monuments is a purely digital photo competition, how important is technological, what are the kind of technological issues that you face in implementing the competition in your country or region? And what kinds of initiatives have you taken in this area? Can I start? Yeah, please, Adam. Okay. From a global self-context perspective, technological accessibility and inclusivity relate to actions. We as local organizers need to adapt the context, the context to our local contexts. So this means that we have to consider and we have been doing this in Brazil since 2019 that we have to consider how they navigate through the lists via mobile devices, for example, or which devices are they using to take the pictures? Do they have a stable connection to send the photos once they have taken the photos? How high is the learning curve of the participation in the contest? So we have feedback from participants that say that it's impossible to navigate through the tables, the table lists on Wikipedia. So how we've been doing, trying to resolve this problem is to build solutions for the lists. For example, we are using a mobile and desktop map application to try to improve the user experience of the photographers participating. It's available through Forge, on beta, still, I'll put the link in the interpreter. And that is something that we feel that needs to be addressed, the user experience. And that's it. Thank you. Jeffrey, would you like to go next? Yes, thank you. So yeah, I think it's really very important to consider this gap of technology because, yeah, for the last moments and other photographic competitions really depend on whether someone has access to a nice camera or has access to a smartphone that can take really good, quieted pictures when you see the photos that, for example, win the international competition, they're really high quality photos and they can only win if you have like a nice camera but also have like that taking your capacity to take a good photo. And I think the good thing with the Wikilabs Monuments is also like it is kind of decentralized or federated. Like we have like a local Uganda competition where we know at the end of it all we have winners from Uganda and we are going to judge them depending on the quality of photos that we have that are coming in from. But the fact is that not everyone has access to a camera, that one remains the fact. So what we have done in Uganda to kind of reduce the gap is we have a device, a camera for the user group and normally we throw this out to participants. So one person can use it like for three days. So by the time the competition end the camera has moved hands like maybe to six people. So someone has just to share a list of monuments that they want to capture and when they want to capture them and then we brought out the device and someone goes to capture. And we try to prioritize sites that have never been captured before because we have been doing this since 2017 but also there are some places we have entrenched. And the other thing we are doing is also to go for photo hands. And when people are going in a group still they can share one device. One person takes one site, another takes another. So sharing devices and lastly also supporting people with internet data and also transport. So someone needs transport to go. Some of these monuments or sites are located in remote places. So we use also support from the foundation and we give support for the transport and also internet to upload pictures. And in that way are kind of reducing that kind of barrier to participation. Thank you. Kimu, would you like to go next? Yeah. I think that at first we tried to use the Wikipedia table list for showing what should be photographed but it was pretty fast that we were built. They were just too complex or hard to use for general users. And after that we have been mostly used maps which user can browse and see what are metals and mostly we are using custom Wikipedia tool for that. And generally it is very important that we sort of globally very well-working tools for the competition, support, finding what user needs to photograph and also what they need to fill information when they are saving photos. That is another thing. If we want the IDs and coordinates and everything like that then it will be automatically billed. Thank you. Mikolo, do you have something to share? Yeah. I think we have quite like, we have no real big problems with access to the internet for example at least before the war started we did not have it. So we know that participants can have their photos on a device that has internet connection but we know that some of them are not very used to upload forms like we have on comments. So they might get lost in accurately describing these pictures or just not knowing how to attribute them correctly and so on. So what we have done is we added upload buttons to monument lists which regenerates as a monument description so that we know that at least if person clicks on this button the picture will be correctly described and in the right category and so on. We also added a feature which a few people used that if you're uploading pictures of a lot of monuments I mean hundreds that we can help them with the bot to automatically add descriptions to these images if they add identifiers to file names in this case the person just needs to sort these images on their computer and the bot will take care of putting them into right categories and adding them correct descriptions. We still have some barriers to for example people are asking to have some sort of to-do list or maps that they can choose what pictures to see what monuments need pictures and create like lists for themselves by aggregating lists from multiple areas that's not something we still have but well those are things that would be good to add probably it's international level as well. Thank you. So listening to these experiences obviously there are roadblocks that each of us face in different ways right. So how is it that you get your participants motivated each year, year after year to send in entries and participate in the competition? I'd like to go first on this. So that's very key like to get participants engaged every year to continue participating and what we have done in Uganda is to hold events so we normally have events and this helps to help people learn more about the competition and why they should participate. It has been a challenge in the past two years because of the COVID situation and events had to happen online so the engagement really is not the same as an in-person event but that really helps. Of course the other thing that helps are the prizes so we normally have prizes for the winners and this also helps to not encourage participation but I can also say that still the numbers are low. When you compare like the participants in Uganda for example with participants in other countries for example last year in Uganda we had 15 participants who submitted 334 photos and when you compare that to a country like Italy who had 675 participants submitting 11,000 photos there is like a huge good difference so yeah we can get a few people getting involved every year and continuing participation but we also need more people to mobilize as many people as possible to participate which is still a kind of a challenge. Thank you Jeffrey. Mekola would you like to go next? Yes, so for us the biggest challenge is a bit different that we have many participants and many pictures we typically get around 30,000 images per year and this means that many participants feel I don't have a lot of chances to win if we just award prizes for the best 10 pictures the chances are slim so we tried to encourage participation by adding more awards people can win we added awards by regions so that you also get a smaller prize for the best picture of your region and we also added prizes for the number of monuments pictured and this evolved in time with the prize by the number of new monuments pictured so the goal is to say to people well maybe you don't have spectacular monuments in your area but you also have some important a bit less beautiful but also historically important monuments and we also want you to encourage picture maybe not very spectacular historical buildings around you it's not like the best castle of Ukraine but that's something that we want to have on Wikimedia and this encourages also people in different geographic areas to participate that we are not joining us before. Eda, would you like to go next? Yes, so we have been doing something similar I think it's the same thing in Brazil as well we have been promoting since the 2019 different prizes for participants of course we have the main category that is the best images that go to the international phase but we have also since 2019 the best contributors or the people that contribute to illustrate the most number of monuments and we also from 2021 since last year we had a state of Brazil in context of another set of activities we also established category for those for a state of Brazil to give prizes for that region but one thing that we struggled a lot is with outreach and communication that was something in 2019 we assumed the competition in Brazil that we attributed to the lack of participation and then covid hit and we had fewer people going to the streets and photographing but year by year we have been adding things to improve the user experience to try to tackle this participation problem but if you look at the numbers photograph contests on wiki are all of them we love earth, we love zafrica we love monuments, we scientific all of them rely on newcomers so you have a high percentage of people participating in the contests become a wiki medium in the moment of the contest context of the contest we need to read these numbers tackle why are the retention rate so low globally I think it's 9% for all the users 3 for newcomers in Brazil we have 3 for all the participants and 1% retention rate for newcomers in Brazil that is something that we are trying to tackle by improving the user experience thank you, Kimu do you have anything to add to it? yeah some ideas comments about newcomers what I have been filled about all the time is that the wiki loss monuments and these are mainly outreach campaigns outside of the current wiki community so I haven't really seen a problem that my growth of the users have been newcomers because it is kind of have been our focus another thing about the technical we have been doing different photographic campaigns in wiki which are focusing to photograph a statue or photograph of some buildings or something like that and we have had tools for that and we have been developing wiki suit me for that and another photography app which is for photographing historical photo again it shows that what photographs have been taken displays on the phone they are now rewriting it so that it will work also with the EOS phones and one idea what we are trying to do is that how well it will be working also in the competition like Vigilos Monumes but it is kind of focusing for those people who are already doing targeted photographing in wiki thank you for those inputs one last question came from one of our international organizers from SEAL so she asked that how important do you think gender is as a factor for a photo competition such as Vigilos Monumes and what does it bring to the table this is open to everyone do you have any ideas or comments about it that you would like to share maybe I can start again and I think gender is always perspective that we have to look into in every aspect of our competitions or activities and gender in this case relates to access to the resources that photographs have for example our internet connection showing research that women have less access to internet than men and that includes economic resources as well we all know that and that plays a role in defining the profile of photographer and photographs that we have on the competition but gender is something that is difficult to measure in Vigilos Monumes because we only have access to the username of the photographers and people tend to not answer surveys so we don't have this number at hand at any time so it's difficult to measure the impact of gender in the competition I think since we are coming up on time we just have 5 minutes left I think we could have one more speaker share their inputs and then we could move to the audience questions would that be okay? yeah it's okay would someone want to go ahead and answer the question go ahead I also think your gender is a very important factor if we are to bring diversity and inclusion within competitions like Vicky Loves Monuments and when for example you look at the example I gave last year in Uganda we had 15 participants but only 2 of those were women and if we are to really get more women involved as we reach out as we organize events that's where we have to kind of make sure that we have equal representation in terms of gender so if we are giving out for example support in terms of internet data and we have a budget for 20 people at least make sure 10 of those that support goes to women and 10 goes to men so that there is if we are organizing an event also make sure that there is representation on who is coming to the event and also things like supporting people like with internet data so one of the things that I think is equally important is also to get organizers for events and for competitions like women so are women I think women are more likely to participate if you know the organizers people are leading the event also women I want to give a shout out to my friend Tepe Le from Zimbabwe who started the Wikilabs monuments in Zimbabwe last year and she's organizing it again this year and I think because she's a woman more women are more likely to participate in the event so yeah we need more gender representation if we are to achieve diversity equity and inclusion within Wikilabs monuments Thank you I think we could move to the questions on the ether pack first question is for you Jeffrey they ask do you organize transport for groups so people can join to visit remote monuments so the challenge with monuments in Uganda is that they are really scattered so they are not like in one place so if you have a group and it's visiting one monument and these monuments are like you know five hours apart then there's a lot of time lost there so for Wikilabs monuments what we have done really is to send one person per region to go and capture monuments but when we when the monuments are concentrated like in one place then they will do group photo walks so for example in the capital Kampala here there are monuments which are also the concentration of monuments and there we have organized the group activities and that's where we we support people in a group to go and capture monuments but also makes it more fun when people can go out as a group it gets the competition more exciting because people get to interact as they contribute to Wikilabs monuments so we have done that where we can but also for sites and monuments which are very remote then we just send one person to our particular place thank you and we did something similar in Ukraine via VK expeditions for example where we focused on visiting a few areas there which are badly pictured on comments not only in terms of Wikilabs monuments but in general which have very few pictures we organize individual or small group trips to these regions to cover as many sites as possible and it's also very helpful if you have local authorities who help us or local historians thank you I think our next question is to Adair about the retention rate do you mean retention on Wikilabs monuments or newcomers participating in Wikilabs monuments in the following edition yeah by retention rate I think I put on the the hydropede as well and define as participating in the Wikilabs monuments competition in another year so if people participated last year this year if they participate again so we will have retention rate based on the number of people from last year or the years before participating again so that's our definition thank you so much I think we are on time thank you I think we are cut off but thank you everyone for joining us for the session it was great I think we are off air now are we yeah alright everyone thank you so much I appreciate your time before getting started I just want to let you know that I got a call to this a three days prior before this event and the result I have a sore throat to make apologize if it makes you uncomfortable also apologize for the bad lighting in my room because the reason is because I have cold I also quarantine myself in my bedroom and unfortunately there isn't any good lighting so I use this that my desk lamp but even that is I think it's working and it will go well within this session okay without further ado let's get started okay the title of this session is wikis stories a new way to share a knowledge before I begin let me introduce myself my name is Bona Fensura and I'm a product ambassador for the Indonesian community working on behalf of wikimedia foundation basically my role is to connect between wikimedia communities especially my case I'm handling the Indonesian community and wikimedia foundation also my case is in Uganda and the last thing I'm actively informing the communities updates for a certain project the wikimedia foundation team are working on for my case it's wikis stories okay just a little information so this is slide I'm using for presenting wikis stories this is presentation I'm using for presenting the wikis stories for the Indonesian communities and I'm not modifying it too much because I said before I am getting cold and I don't have time to fix too much but don't worry I made this presentation using Indonesian and English and I will explain everything using English so don't worry about that okay let me go to the next slide so what's the background of creating wikis stories over the years the internet has experienced a shift in the way content is presented and consumed also the preference for the content format has still to 91% of the population choosing visual and interactive content to a traditional text based format which has caused approximately 1% of the people both young and old had to identify as a visual learner within wikimedia project photos, audios and videos improve readers experience with wikipedia and other freaking knowledge projects furthermore the 2030 movement strategy discussions emphasize big equitable distribution of knowledge selling opportunities across wikimedia communities across the globe which inspired the exploration of wikis stories so what is wikis stories wikis stories is a story creation and consumption tool in wikimedia project for editors and readers who want to engage with visual and reliable knowledge in a quick way using mobile devices in other words wikis stories are tools to create a summary of knowledge using stories mode like instagram stories but this is the important thing the big difference here is unlike instagram stories where you can include basically everything you want wikis stories need information wikis stories need information from wikipedia articles and pictures or illustration from wikimedia comments so absolutely you cannot add information outside wikimedia projects to make sure the information shared on wikis stories can be traced back to wikipedia articles or in this case also the image or illustration from wikimedia comments so basically it all traced back to the wikimedia projects this is I just maybe know like many people from the community I met already we are concerned that wikis stories will make wikipedia more instagramized and it will take off it's main goal to provide instaclopedic information to all people yes that is understandable because the reason like maybe like the wikipedia will change to the visual thing and forgetting about the text the reference thing basically it's not those people who are concerned will make big change in wikipedia don't worry because wikis stories is just a little yeah just a little additional feature on the wikipedia articles and it will only show on mobile view let's emphasize my work my work on mobile view not so basically not on desktop view besides this feature can be activated if you have an account first and the second you must activate it by yourself on the beta menu so it will so if you don't have an account or if you have an account and choose not to activate it wikis stories will not show on your view at all so it's limited to the mobile view and the contributors who have account and activate manually via beta menu so it's not just like implemented easily like if you choose view on wikipedia you will immediately show the wikis stories will not like that you must activate it manually ok further some wikis stories is not available in Indonesian wiki only in Indonesian language wikipedia so far until now in the coming days wikimedia foundation in Khartim is collaborating with wikimedia Indonesia to run a campaign more like workshop and contest where the tools introduced to the newcomers and contributors in different wikimedia Indonesian communities and they will use it to add visual content at the same time the Inuka team learns from their experiences to better observe and evaluate the utilization of the capabilities of the tool for improvement and further enhancements ok as I mentioned earlier wikis stories are only available on mobile view and it means you don't need any software to download it to your phone you just open your web browser equipped within your mobile phone and you can go get ready to create the wikis stories oops sorry ok why did we make wikis stories the reason we make wikis stories already written on first make all people interested in accessing wikipedia also other wikimedia projects second giving a chance to all people to be a wikimedia project contributor wikis stories and the last thing creating quick byte content for easy access and visually appealing besides that I just want to add the objective of wikis stories is to support contributors to curate and engage with knowledge on wikimedia project in an experience that is image or visual lab this new form of content contribution will take into account the constraint editor in emerging digital communities when contributing content and make it easier or more welcoming to contribute to knowledge successfully through mobile phones the objective we would like to accomplish through wikis stories are first an increase in visual content will lead to increase contributor and reader engagement with encyclopedic content in emerging digital communities and the second understand users can create, curate, contribute and engage with knowledge through visually driven experience the goal with wikis stories is to provide suitable content for my alternative for subjects are not well served by long text or require events level of prior knowledge the wikis stories tool will first allow users to engage with wikimedia content both as consumer and creators in a way that meets contemporary internet experiences second be visually appealing easy to contribute and meet reader needs with visual knowledge and be shareable third provide a way to quick contribution and consumption of visual knowledge from an information source that is reliable and the last thing reach a larger and more diverse audience both in contributors and in readers so alright finally we arrived at the exciting part because at this part I will show you how wikis stories work and activated if you have an account on wikimedia project but I just said before that this on wikis stories is only available in wikimedia so I will demonstrate it on Indonesian wikipedia if you want to follow along my process if you want to try and find yourself while I'm explaining the process you can do it too I will explain it slowly as possible so you can follow my step creating of wikis stories please give me a moment to change the screen to show my browser one moment yes okay yes you can see okay apologies for apologies for the technical the first thing I want to show I want to show you how do wikis stories process for wikimedia using the but because it's not possible and it's not sure how to do this presentation so I will explain the process using this slide for me okay because the first thing before you using wikis stories you will obviously log into your account and activate it on wikis stories using the beta option yeah you can go to the beta and activating the wikis stories and save it after activating it you can create your wikis stories so the first thing is let's say if you want to create an article about for instance so did you see the did you see the plus button on the article for creating the story you can add the plus button after you click the plus button you will face a many pictures about writing and for your information this picture is taken from the wikimedia commons okay you can choose the many as you want but for this instance minimum is two pictures and in the next movie stand so next okay after after choosing the pictures for the for pictures you can choose the big first page on here you can add the create a text create the story text button on the white background available below and choose some text by dragging the information click add to wikisaurus next after choosing you can add it will show what you choose before and add some text about this the window next okay after we getting add text you can if you feel like I think the text is too long and I want to make sure right it's easier for the people to consume information don't worry you can edit the text too to make sure everything is on your own after you adding the edit the story and add the all of text to the stories the last thing the last step are add the title so it's very important to get the people know about what is the story wikisaurus and there you go there is a new wiki stories added next to the last button also if other contributors are adding there are ones too there will be another another wiki stories as well even you have created your wiki stories it doesn't mean you can it doesn't mean you can cannot edit it at all absolutely obviously you can edit the wiki stories after you creating it by click the wiki stories you create on the same page for instance on the same page and you can see um just after you choose the wiki stories you can click the the vertical three dots after that you can click edit and change the text or everything maybe you think it's not right or maybe just I think it's it will easier to edit the wiki stories as well because the last thing are basically this is like because I cannot see unfortunately because I cannot show my browser to show the process of creating wiki stories it's really really hard to understand what the wiki stories process is because you cannot see it on real time but I hope my explanation is it will help you to understand the wiki stories process so before basically before ending this session I will if you want to you can fill the feedback form about wiki stories because this form will help us to understand what the community needs and make sure the this tool will will help the wiki media and all wiki media projects to make to make it known to all the people and will help them to understand the knowledge as well so I will take at some moment maybe 30 seconds you can visit the website and fill in your thoughts what do you think what is once in your mind about wiki stories it will help us all finally this is the end of the session and I want to make an apologies for the technical problem because it cannot show my screen share to show you how the wiki stories created so maybe you want to know more about the wiki stories for your information you can visit the wiki stories page on the wiki on the link provided and the blog post on div also provided also you can contact me personally if you have any question about or anything about wiki stories you can you can contact me with the top page or email available on this slide okay yeah this is and this is the end of the session thank you so much for the session and I appreciate it so much again I want to just for the technical problem hopefully this is not like have don't know see you and have fun on the last day of wiki page bye thank you still working on the eq wo eq wo my name is Stella and I am the senior manager of the trust in safety policy team over here at the wiki foundation and currently located in san francisco and my pronouns are she or the UCOC as well as work on the emergency at workflow within the foundation. And I'm very happy to be joined by quite a few panelists on my end. I'm going to go ahead and pass the mic over to Dr. Monica Horton and all of the other panelists to give their intro, but let's just go in the order of the panelists that are there. Well, hello, I'm Dr. Monica Horton. I am the policy manager for freedom of expression at the open rights group here in the UK. I have some 15 years experience of researching in the field of content online policy. And I have worked with the Council of Europe on freedom of expression and human rights online. I'm currently based in London and my focus is on the online safety bill, which is a new law being currently put through the Westminster Parliament. And it is with the intention of tackling harmful content online. Awesome. Passing the mic on to Dr. Hussain. Could you give a quick intro to yourself as well before we get started? My name is Nada Hussain. My name is Dean Recorded. I'm a medical doctor and I have been a Wikimedian for the last 12 years. On Wikipedia, I usually write articles related to healthcare. And during the COVID-19 pandemic, I wrote several articles related to COVID-19, particularly related to the misinformation content of COVID-19. In 2020, I also launched the vaccine safety project where I was involved in mapping and bridging the knowledge gaps related to vaccines and vaccine safety. Outside of Wikimedia, I'm a medical doctor and a radiologist working in Sweden and I'm originally from India. Thank you. Awesome, awesome. Tina, would you like to give a quick intro to yourself? Sure. So hi, everyone. Thank you so much for joining us today. My name is Tina Bhutoyu and I am a lawyer here at the Wikimedia Foundation. Most of my work focuses on harmful content. Recently, I've also been working on the UK online safety bill and I also work on producing the biannual transparency report. And then so sorry, everyone, who is viewing the slides, we are missing one panelist, Praveen. Could you please give a quick intro to yourself as well? Yep. Hi, everyone. I'm Praveen Das. I'm a senior partnerships manager for South Asia region. And I'm based in Lucknow. Most of my partnership focus is currently in this region and the family I'm used to making help. Hence, I'll be talking about something today as well. Thank you so much. All right. Just want to take a brief pause. So let attendees know, you guys can submit questions at any time during this session. And we will be trying to get to as many questions as we can. I have the ether pad open in another tab. So I will be looking at that throughout the presentation. But with that, let's advance to the next slide. All right, let's talk legal definitions of harmful content and access to information. I'd love to hear from Dr. Horton just about your experience legally with harmful content and what types of definitions you would say fall under that scope. You're muted. Just as a quick FYI. I can hear you, please go ahead. Okay, thanks. Yeah. So yeah, thank you very much, Salah, for that introduction. Although you might think it is easy to define harmful content, it is actually quite difficult to define it in a way that is legally watertight. And in the UK, I think we are struggling with this a bit. We have a proposed new law, which is called the online safety bill. And it introduces a concept of harm in relation to online content. And it asks online platforms and other internet services to remove or take down or restrict that content. So it's quite important how we define it. But when you ask what it means, the first thing you actually get is a long list. And the list may include things like eating disorders, anorexia, suicide, online abuse. The harmful content is actually divided into two categories. But these are legal categories. So in one context, you're talking about illegal content. So content that is against the law, content that reflects a criminal offense. And illegal content is defined by criminal defences in UK law. And there are some 28 criminal offenses altogether that the law specifies. These 28 offenses include harassment and stalking, financial fraud, terrorism, child sexual abuse, and assisting suicide, and also assisting illegal immigration. So you can see quite a wide variety of things, not a lot of definition though. The other content type of harmful content is often referred to as legal but harmful content. This is content which is not covered under criminal law, but is nevertheless considered harmful and where the government considers it desirable that the online platforms remove this content or restrict it or restrict the user's accounts in some way. So in this context, you get eating disorders, online abuse, anorexia, and what is defined as legal suicide. But nowhere do we actually see what this content looks like in a Facebook post or a Twitter post or Instagram post. There are no guidelines on how the platforms should actually identify this content. So the law should tell the platforms what exactly they are supposed to be taken down, but it doesn't. And similarly, the users need to know what it is they can and cannot say, but in fact, they don't know that. There's not a lot more definition than what I've given you here. For example, if you look at the illegal content for assisting suicide, you get told that it is Section 2 of the 1961 Suicide Act, which is about assisting or encouraging suicide. And that's it. But what does that post look like? What's supposed to be taken down? What is it that you're allowed to say? We still don't really know. One of the big problems that comes up is when you're talking about linked content because as you know, users on social media generally like to link to content. They might link to Wikipedia and say, here's something that you ought to know in this post. But the question really is, how are these links treated? So for example, if they are taking down the content put up by the actual platform, or are they taking that content down, put up by a user of that platform? And therefore, what does that mean? What you tend to find is that when the platforms decide to take something down, they don't just take it down in one place, they take it down everywhere they can possibly find it using AI to identify it. And this raises real concerns for the sites who are being linked to a lot. So any sites that rely on links for people to find them, which might be Wikipedia or it might be your source material in Wikipedia. How do those websites and source sites know that their content is being removed or demoted or restricted in some way? And what can we do about it? At the moment, the law actually says very little about that. Interesting. I want to follow up on a point that you just made, just because you're bringing up a lot of examples in which the definition isn't very clear or slightly amorphous. Based on your experience working on this, how do legal definitions align or conflict with the right to freedom of expression globally? Just given it is a bit ambiguous. In this case, it is deeply problematic because I will take the right to freedom of expression under the European Convention on Human Rights, which is the one I'm most familiar with. And on the European Convention, you have a two-way right. So you have a right to express yourself, but you also have a right to access information on one hand. And also, under Article 10-2 of the Convention, Article 10 is the right to freedom of expression. Article 10 has a second paragraph, Article 2, which talks about how states should go about respecting content if they are going to do so. And it is actually very clear. It says, the law must be clear and precise as to what it is you are restricting. The law should define clearly. And in courts, that's sometimes actually defined as precise URL. So when you get this very broad stuff, like you get a criminal offense, where we don't know what it actually looks like in terms of content, that becomes problematic because how is the platform supposed to know? What is that offense? And I have an example from another area, which is terrorism content, where a reviewer of terrorism here in the UK said, look, you've got somebody giving a training in rifle shooting online. Now, that could be somebody training someone with a view to them undertaking a terrorist activity, but also it could be something completely innocent. It could be just a rifle, a sports club, but there's rifle shooting and it's legal and it's okay. So how does the platform know supposed to define between those two things? So that is where we end up with the problem. The law wants it to be clear and precise. Sorry, the human rights law wants it to be clear and precise. This law, the online safety bill, is very, very far from being clear and precise. Interesting. I'd love to hear your thoughts on this, Yuna. I mean, based on these definitions, how does it conflict with emerging research on what is harmful to readers? Yeah, so it's tricky because in the online safety bill, harm includes both physical and psychological harm that amounting to at least serious distress. But we know from emerging research that culturally harm is what qualifies as harm across cultures and languages, as well as lived experiences is different and how people in different countries and across cultures rate the severity of harm of certain content, it also differs. So for example, in the US, we know perinirixia content is problematic as based on the, and we've seen how Instagram misuse their algorithms from the Francis Hogan revelations, but Americans perceive perinirixia content as less severe than other types of content. That's where it gets complicated. But in other countries, I think in Southeast Asia, suicide-related content is higher on severity than in the US. So one of the issues with online safety legislation globally is that regulators with a particular bias and perspective are charged with enforcing these laws and may have blind spots with respect to the types of harms recognized and experienced by folks around the world. Interesting. I want to drill a bit more into that. I mean, what principles does the foundation take into consideration related to harmful content? So what we have is at the foundation is, as you all know, the foundation is based in the US. So US law always applies and we'll take into account the laws of California and Florida since we were based, we're headquartered in California. Oh, sorry, Tina. If we could slow down a bit and it looks like we've gotten a comment in chat just too, that it's a bit fast at the moment. Oh, absolutely. Thank you so much, Natasha. So the way we evaluate harmful content or whether an international law applies to us as the Wikimedia Foundation, since we are a US-based organization, is applying three factors. One, we evaluate the law issue and see if it applies to the specific case and whether geographic jurisdiction also applies. Next, we evaluate whether the case presents a risk to the foundation or the movement and these risks include, but are not limited to risks to editor safety, risks of project blocking or similar technical disruption and also monetary risks. And then finally, and perhaps most importantly, we conduct a human rights analysis. So we evaluate whether a law conflicts with existing human rights norms in accordance with our human rights policy. Interesting. How effective are community moderation processes? Just brief pause. Natasha, am I going too fast for you as well? Would you like for me to slow down? No, it's not you. It's Tina, because what she says is very interesting to me as a Wikipedia editor to know how the foundation evaluates harmful content. And she starts slowly, but then it goes very, very quickly. And I'm not used to American accent. I'm used to the English accent. So I have problems understanding Americans when they speak. If it goes too quickly, sorry. I'm really sorry to pass to you. And probably there are other people from other country who would not be as bold as me and daring to say it goes too fast. Well, thank you so much for that feedback, everyone. This is why it's important that we have feedback from community members from around the world because sometimes we're not aware of what we do. Just automatically, my apologies for, no, no worries. I really appreciate that. And it actually highlights why we need to have an ongoing conversation about harmful content is sometimes we edit or we do things in ways that make sense to us without realizing that others around the world may experience maybe the way we speak or what we say differently. So I'm actually really glad that you brought this up, Natasha. Yeah, so the main point of how we evaluate harmful content is one, we evaluate the law. We always, everything is done on a case-by-case basis. So we look at a complaint and then we examine the law itself, often with the help of outside counsel, local expert outside counsel. And we see if the law applies, but also if we're subject to a country's jurisdiction. Next, we also just look at what risks. Do we have folks on the ground? Do we have assets? What risks does a complaint or an issue bring to us? Present to the foundation. And then third, we're always committed to human rights. And that's why we conduct a human rights analysis. And if we identify that that law conflicts with human rights, then we will take that into account whether we comply or not. Again, each case is evaluated on, we make these evaluations on a case-by-case basis. So it's hard to predict when we will take content down. But I think the most important part is to realize that we have, that we do take into account human rights. And when we're looking at online safety legislation, that is something that our public policy and global advocacy team very much work with regulators and legislators to address. All right, we've gotten a question in from the chat. Could you please drill down or explain a bit more about human rights analysis? Yes. So our human rights policy came out last year in 2021. And there are, so Article 19 of the International Convention on Covenant on Civil and Political Rights says individuals have the right to access information and to share an important information. We also recognize the right to privacy, which is recognized, which is essential to the right to, which is part of the right to freedom of expression. So if you see our transparency report, thank you so much Rebecca for sharing the link to our policy, that's where we go in more depth. We take into account how community members and how the foundation's human rights will be affected when evaluating whether to comply with the law. And when it comes to privacy, we collect very little data, but in some countries where there's heavy surveillance, we do our best to protect the rights of our users over there. Thank you so much Tina. Just noting to all of the attendees, I am keeping a track of the questions that are being asked on Etherpad. We will be going over those at the end of the session. And if we do not have the time to rate your question, we will try to answer it asynchronously. Praveen, next slide please. All right, with this, I'd like to drill down deeper into Wikimedia projects as a global resource for mental health information. Dr. Hussain, I'd love for you to get started on this, just based on your personal and professional experiences, how would you describe mental health and suicide and how they're perceived in different countries? Yeah, from my experience, I could definitely say that how suicide is perceived depends on your background, your culture, and where you come from. We have some previous research showing that when it comes to gender, in countries where there is so much patriarchal influence, women are more likely to try to end their life and think about suicide ideation. And how you perceive suicide also depends on which culture you come from. There are cultures where you are stigmatized overtly. You are just stigmatized just for ideating related to suicide. And there are also some subcultures where suicide is glorified. When your suicide is for a greater good, perhaps for spreading the ideology or ending your own life as a part of a holy war and so forth. And there are certain religions where it's absolutely forbidden to take your own life. And in some cultures or in the people with lower socioeconomic status, we know that social and economic challenges often lead them to think about ending their own life. So how do you perceive suicide is a multi-faceted and a very complex issue. And I think it has very different you, depending upon where you come from and what do you, your background, there is a lot of difference in the way you perceive it. When it comes to Wikimedia, you have just one article. You have like one article about one aspect of suicide. Say if you take the article about suicide on English Wikipedia, you probably are likely to write in a way that is suitable for the Western audience. And I would like for the article to be more diverse when it comes to like addressing the challenges of people from all backgrounds and cultures. I want to drill down on something you mentioned about stigmatization, just in one of the first points you brought up. So research has stated specifically the WHO or the World Health Organization has stated that raising or addressing stigma and raising awareness is important to preventing suicide. They've also stated that improving community and online environments can help improve child and adolescent mental health. Do you have any thoughts about that? Definitely. I think there is so much that Wikipedia can do. I think the whole Wikimedia movement can do in terms of like raising awareness related to suicide. We are the largest health related, we are the largest encyclopedia in the world. And we also have the largest health related encyclopedia content. So I think, and we are also one of the most visited healthcare related information on the internet. So this gives us some responsibility when it comes to providing content to our readers because anything that we write out there, it could be like shared and amplified in different ways. So we have to be very careful about what we are presenting in terms of like, in terms of what articles we show to our readers. So I would like for more expert involvement in this area so that Wikimedia content is more and more reliable and updated. I would like for the knowledge gaps on Wikipedia to be fixed so that when people look for information and they don't see it on Wikipedia, I don't want them to go further and go into other websites that provide the misinformation. I would also like for Wikipedia articles not to be overtly academic. We are, as Wikimedians, we are very interested in writing everything in a very academic way. But when it comes to suicide, I think we also have to think about in a person, writing in a person-centered way so that we take into account of the emotional challenge that is also gone through by people who have attempted to take their own life. We also want our articles to be written in a holistic way, not to focus overtly on a person's, how a person tried to end their own life or focus overtly on the graphic content of how a certain person ended their life and so forth. So when we write an article about, say, by a person who ended their life, we have to be very careful about how we describe it in a person-centered way so that the readers can, it's possible for the readers to understand the fact but not overtly to focus it in a way that helps, a way that promotes them to actually take their own life as well. So these are some of the thoughts that I have about this. Thank you so much for providing your thoughts. I mean, just going into a bit more detail, I want to give Praveen a moment to speak. Praveen, if you'd like to weigh in, what role do you think Wikimedia projects more broadly have to address stigma and raise awareness about mental health and suicide? Okay, I think when it comes to Wikipedia, as Dr. Hussain mentioned, it is one of the most frequently visited resources for health information on the internet and it's a global source of seeking mental health information. But then again, when it comes to suicide and self-harm, these are very complex issues, which is caused by mixed factors. So as part of the project and as part of responsible community, I think we should be more sympathetic and also be very cautious while writing anything related to suicide and suicide prevention and build more repositories of mental health on Wikimedia projects in general, be it Wikimedia Commons or Wikipedia, textual and image repositories are going to help build more resources for seeking help for those people who wanted to come to suicide. Thank you so much. What do you think are the challenges in doing this or implementing this? I think there are a wide variety of challenge when it comes to mental health. These are very sensitive topics and we may need more editors from the background to understand mental health very well. Or we can organize some workshops to encourage participation to learn more about mental health so that the communities themselves can write really well Also other challenges are in general, so lack of research in third world countries. So when it comes to develop countries there would be more initiatives towards mental health but when it comes to not so developed countries there are not very much active non-profits for government taking action towards self-harm. So content specific to those countries are missing and why would we need those information? Because the reason of self-harm in different countries are different. We need to understand those reasons and then identify the resources which is needed to convey and for that a detailed research is required. Hence, the bigger challenge is do the lack of individuals, lack of experts in writing the content and the second one currently is lack of resources too. Thank you so much. I'm seeing that there's quite a few questions bubbling up in the chat and I saw that there was one regarding guidelines. Tina, would you like to weigh in here? You are muted. Hi, could you repeat the question? Which way do we have several? I'm looking at the question from Natasha from 409 a.m. my time. Would there be guidelines somewhere on how to write about suicide? And just keep a note to everyone on the etherpad and also on the channel. I am documenting all the notes. We are trying to prioritize what intersects. Yes, so we actually do have notes and guidelines on how to write about suicide and we will share those too with folks who are interested. Our emails are on the, so my email is on the page, the event page, I'll drop it here. But yeah, just send me an email and I will send the guidelines to folks who want them. All right, thank you, Tina. Before we move into the next slide, I wanna give a moment for you to chat about the SPIF Foundation Paint Your Blues campaign and the impact on raising awareness about mental health and suicide in India and around the world. Sure. So, you know, Paint Your Blues was a campaign started by Suicide Prevention India Foundation. It's an India-based one perfect working, you know, in terms of building more awareness related to mental health and encouraging people to seek help. One of the issues which we have seen is people don't seek help when it comes to mental health. There's a big stigma around that. And especially after COVID-19, the issue of stress, anxiety is high in the society. So we identified this as one of the opportunities where we could work with an organization who are, you know, freely active on-ground in creating content and identifying, you know, the gap in general. So, you know, as a result, we thought, you know, it could be a campaign where we could, you know, gather images. We can generate images through different artists by working with them in general. And we know that a single image can convey 1,000 words and has a power to increase awareness for people to action and change opinions. So when it comes to mental health imageries or even the content, both are, you know, both lacks in Wikipedia and Wikivolt in general. Images have a large influence on attitude formation and perception of views, but most images promote negative stereotypes. What is currently circulating, you know, on internet, reinforced stigma and discouraging mental health conversation and hinder self, you know, self-seeking. So Art for Good was a campaign, you know, that it started in December, 2021 with an ambitious aim to build the world largest repository of mental health imagery. These, basically, we've built these imageries with the help of artists. There were more than 50 artists across India who participated and have created more than 100 imageries. The imageries, the art which is currently shown, you know, in this presentation, is the outcome from Art for Good campaign. And basically, these were created so that this can be free to download, distribute images, will seek, you know, to leverage the popularity of memes, cartoons, illustration, infographics, and also the enduring powers of photos to support text-based narrative which is there in Wikipedia. And it is highly encouraged, you know, in India to the media industry to use these arts and not use the graphic, you know, picture to show mental health or mental health. Thank you so much, Raveen. Before moving to the next slide, I would like to ask the question that was bubbled up on the chat. What about establishing a free psychological line for all Wikimedians like Wikimedia France does? This helped a lot during lockdown, especially for underrepresented minorities. Tina, would you like to weigh in? Sure. So it's kind of tricky because we have readers around the world. So when we try to help our community, we try to help our global community. I know, Stella, maybe you can speak to the trust and safety resources and peer support work that's happening around the world. I'm not personally familiar with the Wikimedia France example, but we're definitely interested to hear more. So again, I'm happy to drop my email for someone who would like to chat more about this. All right. Natasha, would you like to weigh in with a few words about Wikimedia France before I give some details into our emergency workflow? Yes. So because there was quite a lot of problems for underrepresented communities, and that was a lot of LGBT persons on the Francophone Wikipedia, Wikimedia France established a psychological support, first as a test for four months, I think, with a psychologist who knew about LGBT questions in general. That was pretty much used. And now it has established a 24-hour round-the-clock service where any person contributing to the Francophone community or member Wikimedia France can call, take an appointment and get psychological support. So I'm not speaking about readers. I'm not speaking about readership there, but people who contribute. And if we want a better representation of minorities and underrepresented communities throughout the world, we have to bear in mind that these people are often the subject of microaggressions, which might not be labeled as cyber harassment or harassment and might fall beneath the red line, but can be very, very bearing in the long run, which is why having a service addressing these issues is really helpful, I think. I can weigh in a bit about how we currently provide resources for people who are going through mental health crises or just episodes in general. Right now, trust and safety maintains a 24-hour emergency app protocol in which writers, contributors or Wikipedians are encouraged to write in if they observe behavior that could become evidence of real-time harm or physical harm offline, as well as just threats in general. A lot of what we receive in that workflow does have to do with suicide or self-harm. So we receive an email in which we believe a user is in real and present danger or maybe self-harming. We will work to interpret what the harm is and then based on research, send it to the appropriate law enforcement agency within their region. I'm glad to hear the community is working on this. We also know that some languages of Wikipedia have added suicide hotlines and that is really great to hear. With that said, let's move into the next slide, Praveen. All right, let's talk about health misinformation on Wikimedia projects. I'd love to start off with Dr. Horton and your experience working on health misinformation as well as disinformation and the differences. Just first off, as I mentioned just now, the words misinformation and disinformation are used interchangeably. Could you briefly explain to our audience what the difference between those two things are? Yes, thank you very much, Stella. Yes, I mean, if we're talking about misinformation, you're talking about deliberately false information or perhaps you're even talking about something, it could be seen as something that has made an error. Who doesn't understand what they said is actually wrong, unintentionally said something wrong. If you're talking about disinformation, it's a much more deliberate thing and it's also a little bit more sinister. Disinformation does not have to be necessarily false, but it seeks to divide and confuse. It seeks to basically insert into a sentence or a series of what may be rational information, it will insert something that is deliberately there to confuse, which may be false or it may seem to be a wrong direction. Certainly that's how I would differentiate between the two. I don't know if that was what you were expecting. No, that was great. Based on my limited experience with misinformation and disinformation, it tracks the experience that I have. The other thing that I've heard is that it's used to deliberately elicit a strong emotion or a call to action for information that might be intentionally or unintentionally false. So it could be that you're sharing it and you don't intentionally mean for it to be fake, but it could also be you're sharing it because you intentionally know that the information is not rooted in reality. Just going deeper into that, what are some effective ways to address this problem, either misinformation or disinformation? Okay, if I can state a little bit more about the disinformation. If we're talking about somebody who is deliberately trying to, as you say, either elicit a reaction but in the way that you've described or somebody who is deliberately trying to slip in and untrue to get somebody confused, to get someone to believe something that may be actually false, but they want them to believe that it's true. And the point being that when people are confused or when they are divided, which is the other thing disinformation does, disinformation is part of what we call culture wars. So it's trying to find an enemy out there, maybe a fake enemy, but somebody that people can see as an enemy and therefore take on a viewpoint that they wouldn't otherwise take. And when people are confused and divided, they start to doubt the information that they get. So even when the truth is then staring in the face, they start to doubt it, they don't believe it and they may act accordingly. And this is certainly an experience that we've had here in the UK and I will just briefly talk about COVID here, where we have seen this become in the context of political organization. So we have seen the same accounts who will tweet or post COVID disinformation, who will also be posting on political issues here in the UK. They tend to be pro-Brexit accounts here and they also have been linked to climate change denial accounts. So what we have noted is that there's some kind of organized disinformation here around, in this case around COVID and health. And this is potentially different from what you sometimes hear when you hear that people have posted about taking, drinking bleach, for example, will cure COVID, which is clearly false. This is not what I'm really talking about here. I am talking about a deliberate attempt to kind of subvert people's thoughts. And it looks like it could be coming from an organized direction. I just want to sort of highlight that. I think the way to address it, one of the best most effective ways to address it is to challenge it and to call it out and to repeat the truth. And that is quite difficult because it doesn't always appear in a straightforward way. It appears randomly in people's timelines. So how do you do that by maybe responding to those posts when you see them and challenging them and calling out what they're saying and calling out the falsehoods and the lies and the distortions in that information? And informing people with the truth is the other way to do it. In terms of a policy response, it's very tricky because you then get back into the situation of, well, how does the law decide where it's going to deal with this stuff? If you're dealing with the content, the law would have to actually deal with the organized side of it, I think. That's a personal view rather than the actual content as it appears online. Okay, I would love to hear a bit about the intersection of this from Dr. Hussain. Given your training as a physician and neuroscientist, could you describe your work on COVID-19 misinformation and how the community came together to address it given the scientific community knew so little about it initially? I'd love to hear about that from your perspective, specific ones. So COVID-19, it was a healthcare emergency and it was a new disease and the scientific community knew too little about it. There were no textbooks, there were no past guidelines that we could use to tackle the pandemic. So the situation was kind of a chaos when people see that their loved ones have the disease and they don't have enough information about it even from the institutions, the World Health Organization, the CDC and different governments tried to put out as much information as possible but then there was so much unknown about the pandemic. So this created a kind of panic among people and people wanted to just try to get whatever information they could about the pandemic and the first thing what regular people with internet access do is to go to the internet and check what this is about. And then sooner or later they would land upon Wikipedia because we are one of the largest providers of healthcare information on the internet. And on Wikipedia they could just see the status of the current status of how scientific information evolves around COVID-19 which I think was a great resource because at that time, because due to the panic that's happening all over the world people were really in need of information. And we had a bunch of really very good experts plus a lot of other editors and experienced Wikimedians coming together and writing articles and updating articles related to the COVID-19 pandemic. And at points we had very high view when we looked at the view statistics of certain COVID-19 articles it was like a record number of views that these articles related to COVID-19 got not just in English but also in several regional languages. We do have like more than 200 languages we do have articles related to COVID-19 and these articles are still being developed by our editors. And I think that it was it just really showed how powerful our communities when it comes to like coming together and building something very quickly by using content from all over the world in multiple languages. And this is something which even large institutions cannot like accomplish to do it's only something that a crowdsourced enterprise like Wikipedia can do and I'm really proud of the work that the whole community has done when it comes to COVID-19. And when it comes to my own work I mostly focused on the knowledge gaps related to COVID-19. So the larger articles related to COVID-19 they were taken care of but when you talk about different socioeconomic aspects of COVID-19 such as mental health in COVID-19 you did not have a specific article for that. Then I just went in and created that article and worked on it giving a country related specifics on how mental health is being affected in India related to COVID-19 for example. So dividing it in terms of how it happens in different countries. I also wrote about stigma related to COVID-19. So I wrote all these satellite articles which were not given so much attention at that moment because it was the main COVID-19 related articles that were being edited by very many number of people. When it came to misinformation I have a story to share. I one day I was just looking through the newspaper and I saw that there was an Indian family which ate a poisonous fruit thinking that it would prevent them from getting COVID-19 and they got this information from social media. So I knew that there was a lot of misinformation circulating because at that time I was practicing as a doctor in a primary care setup and I would see a lot of patients and all of them would have their own ideas of how COVID-19 is transmitting and thus like eating garlic help prevent COVID-19 or so they had people had a lot of assumptions on how COVID-19 is spreading and the treatment methods that are used for that. So then I understood that misinformation is a real thing and we need to do something related to that and that was how I went into writing misinformation related articles about COVID-19 and now we do have some really good content related to misinformation but I think that what we have is only a tip of the iceberg because there is only so much that we can find related to misinformation that is surfacing on the internet but there is much more that is being shared privately on social media and right now we only have misinformation related articles in a bunch of languages. We do really need more of those articles in many different languages that Wikipedia has and similarly this was also the case with the vaccination information when government started rolling out COVID-19 vaccines and started giving vaccinating people. People were just so confused as to whether to take the vaccine or not or whether they should like take the booster doses or which commercial product they have to use that there were different companies offering different kinds of vaccines. So then at that time on Wikipedia, it was very important to make sure that the vaccine related articles are updated and also to map the existing knowledge gaps related to vaccines and vaccine safety and show the current scientific information related to safety of vaccines and efficacy of vaccines. So this was also something that I worked with and coming back to your question about how my background helped in this venture. Yeah, I was, I'm trained as a medical doctor and I have a PhD in neuroscience. So, and I also had a lot of experience writing similar Wikipedia articles before. So when all this experience came together, it was, it felt very natural for me to go ahead and create all these articles so that, so as to help people educate more about the pandemic as well as COVID, as well as the vaccines at that time. But on other days, I usually write about whatever that interests me. I have also worked related to the gender gap and improving the content of biographies and female persons on Wikipedia. But when an emergency came, I just wrote what was, I just hopped in and did what was needed at that time. And I think this is very, this is what most Wikimediants do. When they think that there is something that's happening, there's a knowledge gap that needs to be fixed. They just come in and they coordinate with each other. They create Wiki projects and they work together and build something awesome that people cannot individually do by themselves. And I think I really want to show, I'm really proud of the power of collaboration that we have in the Wikimedia movement. All right, one last question before we move to the next topic. You touched on this quite a bit in your answer previously, just about proactively creating content where it didn't exist in order to battle the misinformation and disinfo that was prevalent across the entire web during the onset of the pandemic. But I wanted to just drill in a bit more there. As a Wikipedia, how would you describe misinformation on projects with respect to health information and other important issues such as the gender gap? So taking a step back from COVID and thinking about other topics, what is your take on that? We do have disinformation and misinformation on Wikimedia. I think when it comes to like main articles related to say COVID-19 or stroke or Alzheimer's disease, there are a lot of people editing, there are a lot of people watching that article. So it's less likely that misinformation content comes in and sticks in there. But when it comes to articles that are not so popular, not so read by a lot of people, there can be misinformation which is there. And this could probably stick on because not many experts are reading that article very often and not many editors are updating that article. And the disinformation that we see on Wikipedia could be a propaganda. There are people who want to show that say vaccines are costing autism and they want to push their propaganda and they're using Wikipedia to like use unreliable references and try and insert that in vaccine related articles to show that vaccines are potentially harmful. And there is misinformation where people give undue weight to actual facts. So some vaccines contain traces of aluminum and people would give undue weight to that fact just to show that probably vaccines are not that safe and so forth. And there are also some people who are just playfully editing, they're just playful and they just want to edit and delete parts of articles. They just want to put in their own names. They want to vandalize content. So there is this kind of misinformation also happening. And on the other hand there are also like very innocent people who really want to give information to the world but on the other hand they are having false information in their arsenal. So they really do believe that vaccines are lethal and they want to sincerely spread that information to the rest of the world and they use Wikipedia for that. So regardless of the intention whether it's if it's misinformation on Wikipedia then we have this, we are being peer reviewed every day on Wikipedia. There are people who are reading it and anybody can edit Wikipedia and if you see that there is misinformation out there you could actually go in and challenge that information on the top page or you could remove that information right away. So we do have really very good policies on Wikipedia to tackle misinformation but when it comes to articles that are not given so much eyeballs, the in articles which are not read that often there could be misinformation that is creeping in and I think this is where many volunteer editors have to focus. We could watch list some of the articles so that if any new changes happen on vaccine related or COVID-19 related articles so that we could revert that changes made by that particular editor. We could also track the behavior of editors who have been regularly vandalizing articles. We could use technology to find out which of the editors which of the edits done by a certain editor is harmful and which of the edits are good. We could have like groups in communities where we discuss about misinformation policies and how we effectively tackle the misinformation problem and we could also have repositories of reliable sources where we could cross check and see that look this is a reliable resource and this is not. So there is so much work that should be done on Wikipedia in order to tackle the misinformation pandemic but when you compare Wikipedia with the rest of the rest of the internet say social media we are far ahead and we have since we started in 2001 we have been facing the misinformation problem and the rest of the world identified this problem much later and we were tackling this information like as early as in 2001 when the World Trade Center collapse happened and the rest of the world was actually following the Wikipedia's example of like finding reliable sources and tackling vandalism. So we have done a good job but I think we have to continue keep evolving and use technology and our volunteer workforce to better tackle more misinformation. Thank you so much for your thoughts. Very appreciated and very good to hear that it looks like we've been on the forefront of tackling misinformation for quite a long time. Let's advance to the next slide. I'd love to hear about best practices about writing health information versus Wikimedia policies. Praveen would love to hear from you first. Could you tell us about the role internet resources like what the media projects have in preventing individuals from dying by suicide? Sure. Am I audible? Yes, I can hear you. Perfect. So yeah, I just wanted to hold one hand. So sorry, it seems like we're having a bit of audio issues Praveen. I'm unfortunately unable to hear you. I'm going to give it a brief pause. We all know the internet is quite a beast to tackle especially in these online spaces. Praveen, we will come back to you. I'd like to pivot over to Dr. Hussein to talk about techniques or lessons to address COVID-19 and gender misinformation and how that applies to the overall picture of mental health information on the Wikimedia projects. Could you give some thoughts there? I think there is a lot that we can do on Wikipedia in terms of writing in a person-centered way, in a way that is not overtly to academic, in a way that resonates with the reader. I have some experience in doing this from my work related to gender gap. So we had the first step in here is to identify, how identify the writing style that we are adopting to write suicide related articles. So when it came to gender gap, there was a lot of research that showed how we differently portray men and women, how we usually give undue weight to women when it comes to their marriage and their family. But when it comes to men, we mostly write about their career and their as humans. When it comes to women, we usually tended to write more about, to generalize stuff. And when we wrote about men, we usually gave more weightage to, we did not assume things about them and we just gave them the benefit of doubt. So there were so many differences in the way we wrote articles, which was evident in the research that came afterwards. And in the light of this research, we created guidelines about how to write about women. And now I think after like 10 to 15 years of doing this kind of work, it just feels plain wrong to write differently about women. So it has been inculcated into our culture and we are more aware of how not to discriminate when we write articles, even though that came unconsciously earlier on. So now we are consciously trying to not write differently about women. I think the same approach can be done when it comes to writing about suicide related articles. There are many, very many organizations that provide guidelines about how to write about suicide in a person centered way. And we could incorporate all these guidelines into our Wikimedia when we write about suicide related content on Wikimedia. Then when we write about biographies, it would be important to focus more about the person. Say if we are writing about a person who ended their life, we should not give undue weight to that particular incident and we should more focus on the person. And we should also not give, we should also not sensationalize suicide related content but just give plain descriptions about what has happened. We should not provide overtly graphic descriptions of how some person ended their life. We should just say the plain truth and in very simple words. And I think we should also remember that Wikimedia is not there to be a memorial site just to provide, just to show that this person died of suicide but we have to more focus about their accomplishments on what else they have done in their life and so forth. So there is a lot that we can do in terms of creating guidelines to write on content related to suicide. And right now we already have a lot of policies in place. We have the policy of putting only verifiable content on Wikimedia so we can avoid taking all these articles from these news channels which sensationalize suicide. We could, so if only we only use verifiable content on Wikimedia, I think a lot of the problem is solved in that way just that the verifiable sources are usually very particular about using person-centered language. And so the policies that we already have on Wikimedia are really very good. We just have to build on those policies to create guidelines to write about suicide on Wikimedia. And I think we need more interest from the volunteer community to participate in creating these guidelines. We already have draft and a framework of all these guidelines from the Wikimedia Foundation but we need more participation from the volunteer side to build up this. When it came to gender gap, the field that I worked before there was a lot of volunteer participation in the end and there is still a lot of editor thorns, a lot of discussion, still research that is happening in this area. And I want the same to happen when it comes to suicide and mental health related content as well. Thank you so much. Before we move to the next topic, Tina, would you like to weigh in on the question that was originally for Praveen? Could you tell us about the role internet resources like Wikimedia projects have in preventing individuals from dying by suicide? Yes, so as Dr. Hussain mentioned, the Wikipedia is one of the most visited health information sites online and research shows that it's important that content moderation policies, I'm gonna speak a little bit more broadly now, should be developed with local perspectives and in local terms because people have different understandings of harm based on their lived experience. So the wonderful thing about Wikipedia is that, and Wikimedia projects generally is that they're available in 300 languages. We have people from around the world with different lived experiences, editing, challenging, different points of view and really making sure that articles are supported by reliable sources. So I think as research changes, having a community that's committed to accuracy and neutrality and sharing what they experience as harm is critical to addressing mental health around the world. In light of COVID-19, there's been a renewed interest in mental health. There've been more research. And now is really an opportunity where the community can do what it does best, follow the sources and challenge whatever notions of harm legislators or platforms and possibly even researchers themselves. Again, we don't have as much, as Praveen was mentioning earlier, we don't have as much research from the global South. So challenging some of those notions. Thank you so much, Tina. Let's advance over to the next slide. All right, I'd like to open the floor for all the panelists. What do you think is the role of the projects with respect to mental health information? Let's start with you, Dr. Horton. Unfortunately, we're having audio. Okay, I can hear you now. Perfect. No, sorry, sorry. Yeah, okay. The role, sorry, the role of the projects with regard to mental health information. And it sounds, I mean, but you certainly do have a very important role in bringing, I was going to say, bringing clarity. It sounds a bit like legalistic jargon, but I think just listening to Dr. Hussain just now and the way that you use, for example, verifiable sources with the amount of detail that you go into here, because I think it's about the way that you can challenge that the disinformation and the misinformation around up there is about by providing the truth and by providing accurate information that people can also find. And so I think that may well be the most important role. Thank you so much, Dr. Horton. Dr. Hussain, what about you? Any final thoughts? I would just amplify three points that I took, that I have been saying in the previous conversations. First, we need more research for mapping knowledge gaps related to mental health. We do have a lot of articles, they are scattered everywhere and we need to specifically map what defects we have in each of these articles and try to fix them. Secondly, we need solid guidelines related to suicide-related content and mental health-related content as well. We do have very good policies in place, but we don't really have guidelines about how to approach mental health and suicide-related articles. So with the participation of the volunteers, we need to provide some solid guidelines just as we have done in terms of our gender gap-related projects. We really need a community to take over this issue and create some guidelines for editors to think about when they write about mental health and suicide-related content. Thirdly, we need more volunteer participation in this area, including expert participation. Our volunteers, most of them, they might not be experts in mental health, but they are very interested in that area and they write articles. And we also have a small group of experts who also contribute to these articles. We need more expert participation so that the other articles are more structured and they are more understandable to a general audience and they are presented with a diverse, enriched content. We also need volunteers in different languages to write articles related to mental health in our 300-plus languages. I have been in editing in Malayalam language Wikipedia, which is my mother tongue, and there is too little content related to mental health in Malayalam language. So we need editors in all different languages to amplify the content related to mental health as well as to provide expert advice and expert input into all these articles so that they remain verifiable and up-to-date. Thank you so much. Praveen and Tina, could you also give your thoughts? Sure, I think in this world where internet usage is growing exponentially and people are seeking health information online, I think there's a great rule for the community to come forward and build a mental health repository, not just in English, but as Dr. Hussain said in all regional languages. And I think that these communities have an opportunity to increase access to knowledge on mental health and suicide prevention as a key impact subject. Thank you so much. Tina, how about you? Okay, so writing about mental health responsibly is a complex task. So we're not gonna solve this issue in this panel, but regulators and governments around the world are trying to be direct police harmful content. And some of this content includes important health information. Unfortunately, they're taking the same approach that larger tech companies have taken is apply a policy often based in the US to communities around the world instead of taking the perspective of communities into account. So my takeaway from this is that Wikipedia is keep doing what you're doing, stay curious, follow the sources, challenge what governments around the world say, but also be mindful of emerging research that identifies some content as being indeed harmful and explore the tensions between censorship and best practices. And be sure to be mindful of how what we write about, what we write on Wikipedia may affect those that you may not have thought would have been affected. All right, before we use the last five minutes to open up for questions, Praveen, I would like to give you the floor to talk about your work with art for good. Thank you, Salaam. So as I mentioned before, art for good was a campaign inviting all the artists in India to come forward and create art around mental health, which can detox and destigmatize the behavior of not seeking help. And in collaboration with Suicide Prevention India Foundation, we reached out to the artist communities in India, there are more than 50 artists who participated, who understand mental health from a background of psychology to someone who has seen loss in the family or who was going through the mental health state themselves, have participated in this context and this campaign to build image repository which is available on comments for all. So that was all and moreover with this initiative. I think it is one of the examples which we wanted to do, which we wanted to set with the communities where we work with different partners who are engaging in and out on mental health and suicide prevention specific topic and they have got great expertise in these areas. And somehow at this collaboration, we are able to build our information repositories with the help of collaborations, with the help of collaboration between two different communities and organization. I think we can build more information around mental health and suicide prevention on Vicky projects in general, which will be useful for people. Thank you so much Praveen. All right, five minutes remaining and we have a couple of questions on the docket for our presenters. The first one is going to be when a Wikimedian is accused of adding illegally harmful content by a government, how does the foundation communicate that to the editor? If the information added is illegal in the US but illegal in the editor's jurisdiction, what requirements, if any, bind the foundation and the editor? Tina, would you like to take this one? Sure. So as we discussed with respect to the applicable law determination, it varies a lot and we evaluate these cases on a case-by-case basis but always taking into account human rights. So that's something that is very important to us. But we do try to support communities as much as we can. We try to work with the volunteer communities and communicate to the extent allowed by law and taking into account the safety and of the community as well as the risks to the foundation. Thank you so much. Next question, as these tend to revolve around the legal aspect of this work, I will be allowing for Tina to take the first stab but if any of the other panelists want to weigh in, that's absolutely okay. The next one is the meaning and trade-offs in human rights law will often depend upon case law and may only be determined through legislation. Does Wikimedia interpret case law in making such judgments, clearly a time-consuming activity? And what will Wikimedia do when the case law is unclear and may only be clarifiable through court proceedings? And I've attached it in the chat as well. Well, we do the analysis to the best we can but we often work with local expert counsel to evaluate each case. And if we decide to take a case, we also hire outside counsel who has that expertise. Perfect, thank you so much, Tina. Are there any other questions that people want to bubble up in the chat as I go through the ether pad? Let me find one last question here. And this one I'd like to open to any panelists who would like to take it. To my mind, the interests of mental health practitioners and those who may be treated by them are not necessarily aligned. An example is that interventions taken to reduce the immediate risk of suicide in the short-term may increase long-term risks while providing a practitioner with a sense of having tried to do something. Literature directly targeting services, use service users may hide information in mislead users. How can the value of expert knowledge be traded off with implicit bias and distrust that a focus on suicide prevention could create? Potentially pushing readers to forms that are less regulated and having less regard for the truth. This will be our last question before we all say goodbye today. Would anyone like to weigh in? I will just say that this is where Wikipedia has an important role is to help folks who don't have the mental health expertise ask the right questions, know when their practitioners may be biased. I would like to ask Dr. Hussain to answer the question. This is a very difficult question to answer. I don't really have a concrete answer for this question. For example, on Wikipedia, Wikipedia is not exactly a forum. We just mirror the information that is presented on different reliable sources and we just show it on our platform. So it's not actually a forum where you can ask questions about your mental health and get answers from an expert and so forth. It's the interesting question that's there. And I recently looked into the article about suicide methods on English Wikipedia and I saw that there are 7,500 people, approximately 7,500 people, per day reading that article. And I'm pretty sure that some of them who are reading articles are ideating about suicide and they probably would take their own life. A small minority of them would probably take their own life in the future. So we do provide the kind of content on our websites and from a Wikimedia perspective, I think that we cannot censor the information. People who are ideating about taking their own life will try and find out a way to do that. Even though Wikimedia doesn't provide that kind of information. So we'd have to balance our... Dr. Hussain, so sorry. I just wanted to gently tag that we are at time. I would love for you to provide your written thoughts as well as we follow up with everyone in Metta. Thank you everyone for taking the time to attend today's session. Again, really appreciate our panelists and we will be looking to answer any questions that we missed asynchronously. Thank you again everyone for attending today's session. Tina provided her email in the chat as well. So if you want to get in touch with her or any of our other panelists through her, please feel free to send her an email. Thank you everyone. We can consider this session adjourned. If you attended the hackathon, this is your chance to present what you worked on. If you didn't attend the hackathon, welcome. We hope you learn more about what the technical community has been working on all weekend and about general technical community projects. So how this showcase will work, we've posted the etherpad link into the chat. Anyone is welcome to present what they've worked on this weekend. It's been a very informal way to show off what we've all been up to all around the world. So what will happen is in just a couple of minutes, Melinda and I will open up the floor and anyone can go on and present what they've worked on and people can share questions. And it'll be a great chance to, again, share what you've been working on and learn more about the technical community's projects. Again, anything is welcome. You can share a project. You could share something that's in progress, translations you might have done, bug fixes. We'd love to hear about it. Sorry to interrupt first. I don't think it's live-framing yet. Let me just check the YouTube link and it's not on there. It should work right now. There we go. Now works. Yeah, there's a short delay sometimes. It looks like it was just a little longer than normal. Okay. We'll welcome everyone. Again, our apologies for the technical difficulties, but we're live now. Everything's being recorded. And it looks like lots more people have joined us. So welcome everyone. So again, if you haven't already, do make sure to put your projects in the ether pad and we'll be going through them very shortly. Now we just want to share another thing. We would love to collect feedback from you about your experience at this year's hackathon. We know there are many newcomers. We know there are several people who have, this is their second hackathon. We also know there's a lot of people who have been around for upwards of 10 plus hackathons. Has anyone been to more than 10 hackathons? You could say something in the chat. No. I think there were a couple in the opening ceremony. So there's some very experienced people here, but we'd love your feedback. So seven, well, that's a lot. Brian says maybe. With articles in a particular language, we basically just remove the second article and we count over this. So in this two examples, I get 157,000 articles in English and 127,000 in both. So then French must be missing this minus this, which is what like about 30,000. Okay. So then what I did is I made a table in Google Sheets and I just manually did this query for a few different languages. And yeah, this is like what I filled out. So it's like, oh, oh, hello. Oh, I am playing something from Albuwakimania session in the background. Sorry, I just got distracted. Yeah, I left a lot of stuff in the background like to let it play. Sorry. So yeah, I've got this table. What I wanted to do was to publish it anonymously. I'm not really familiar with how to do that. So I just searched it on like, I don't know how to do that for Google Sheets. So there's like this link, which I think is anonymous. And then I have like this copy as well. And I'm like happy to upload that as well. And I publish the presentation as well, the spreadsheet. And like I can go in this. It's just the same thing here as well. And I just put a few filters on to sort of render this a bit differently. Like what I can see straight away is that the most you're missing is from the Chinese to English, just from what I did, but I only did it for a few. So just to summarize, that full table's 171 Wikipedia is covering quite a few more languages because there's some, because I'm not exactly sure how that works. Doing more than one at a time does make a time out. So the two options I thought was, I don't know how to do a data based on. So I thought I might do that. And maybe if there's a way to use a different API to do these queries, and I can put it all into a CSV that I can just paste into the spreadsheet or something. And also there's this information on language group data on meta. So like Germanic, Roman Slavic. I don't know how this is used in Wikidata, but I think it would also be interesting to filter by that as well. And yeah, so I'm hoping maybe in the next few weeks I'll be able to work out a way to fill this out more and get it on. So it's useful to see which language Wikis might stand out. Maybe it's like Chinese versus English is very sparse, but Chinese versus French, like Chinese has a lot of articles the French does. I don't know how it works. Yeah, that's my presentation. Thanks. Thank you. This was wonderful. Really, really informative. Darcy, we actually have to move on to... Oh, sorry, sorry. I probably took too much time. No, you were wonderful. That was super informative. And I am really excited personally to go learn more. I'm so glad you shared your information in the etherpad. But because we have more and more people joining, which is wonderful, I think we're going to need to start cutting presentations at five minutes. So do ask Darcy questions in the chat and let's move on to the next presentation just to make sure everyone gets a chance. And remember, try and keep it under five minutes. So I think next is Connor about RubyGem for the new Wikibase Rust API. Yep. Can you see my screen? And I guess hear me. Yep, looks great. Cool. So let me set the timer. So my project was continuing to work on a RubyGem that I've been working on on the side for the last while. Essentially, it's for the Rust API that's being built for Wikibase. And it's about just being able to pull data from Wikidata with this Rust API using a simple RubyGem. So I have this demo item on the BetaWikidata site. It has a bunch of miscellaneous stuff on it. I have a couple small demo scripts. So essentially demo one is just it creates a Wikidata client. And then I've got a bunch of hard coded the item ID and then a couple properties. And then it dumps the contents of the Wikidata item just into a big JSON blob. So it has all of the properties or all the statements on the item rendered as JSON. And this is from the way that the gem sees the data. So it can handle times. It can handle links to other Wikidata items. It can handle strings and globe coordinates and no value and unknown value statements and external IDs. So I have a couple things I can show. So you can essentially just do client.item and then ID demo item one. And then you can pull data from that like the information about their date of birth. So it has the property and then they're born on January 1st, 2000. And then there's a reference for it, which has just a reference URL and then a retrieve that timestamp. So you can pull data like that from any item on Wikidata and it handles all of the parsing of the JSON that you get back from the REST API. And then let's see. And you can get labels. You can get aliases. So like item label language EN, it'll give you the value for the label in that language. You can get it for all languages, but this one only has English. You can get all the aliases, the descriptions and site links and all that stuff. And then demo two is about actually writing the writing data to the item. So essentially it's just create the client and then add a statement and you input the item ID and the property ID and then you can create the monolingual text. So in this case it's just, it would be like a title or title of a book or whatever you want. And then you can also do edit summaries. So let's see. The second item. So I have this second item. It has no statements and then I think that script's finished. So after I ran that demo script, it now has this edit on it. And then I can do the same thing with deleting the statement. So in demo three, you create the client and then it just grabs the item and then the statements on that item for this property and then the ID of that statement and then we can just delete the statement and you can pass comments which are edit summaries and tags for the edit and then if we reload this again, it's not deleted. You can see in the history, it's got the data bridge tag and the edit summary. Yeah, let's see. And I have seven seconds left. So I think that's good. Awesome. Thank you for presenting, Connor. That was great to see. We're going to move on to Francesco with who painted this. Hi. Can you hear me? Yes, we can. Let's see if I can share my screen as well which is usually more tricky. Window. There we go. So I'm Francesco. I live in Milan, Italy. I've also recently joined the Wikimedia Foundation and the cloud services team. So I got to do the chance of this hackathon to learn a bit more about a lot of things that I will be working on in the coming months. And one of that is Wikidata. I didn't actually have any specific idea for the hackathon. So I got the idea from Lydia who wrote this guest-artist game idea. I discovered there are lots of other Wikidata games that you can find from this Fabricator task and in many other places, I guess. And this was the idea of adding a new one where you could guess the artist of a painting by just seeing the painting revealed gradually. I didn't have the time to complete the full kind of idea where the painting appears gradually. It just appears all at once at the moment but this was just a prototype I managed to create very quickly in one day. I should also mention that there were other people who helped with the idea like with how it should work and also with the implementation of the Wikidata query, including Darcy who presented before and other people who helped in the Telegram channel and in the IRC chat. So this is what I managed into code and this is basically a painting which is downloaded from Wikidata. I actually narrowed down the query. You can find a source on GitHub. I narrowed down the query to only select paintings from the impressionist movement, both for making the query faster but also to get some paintings that were vaguely possible to recognize because otherwise if you took all the paintings from Wikidata, most of them are from very obscure artists that nobody probably would be able to guess. This is something that could be improved or modified. Then you have five choices of a possible artist and I also find these from Wikidata and then you can click on one and say, okay, it wasn't right. Second one, not right. Let's try this one. Okay, this was the right one and then you see also the name of the painting and I want to add the link to Commons or to Wikidata or to Wikipedia for this painting. I haven't done it yet and then if you want, you can play again and a new painting will be loaded. There's a bug. As you can see, sometimes it gets like two artists, like two paintings by the same artist and so the same artist name gets displayed. This shouldn't happen. If you know how to fix it, tell me or open up an issue in the GitHub project or just write me in the chat or in the fabricator task which is here and will be also linked on the chat. Thank you. Cool. Thank you, Francesco. This is so great. I really love it. I feel like I wouldn't be able to guess the paintings but maybe I should use this to learn more about art. I got the first one, Pissarro. I love it. Okay, next steps. We're just trying to move through so that everyone as much time as possible. Convert spreadsheet functions to source code. Yeah. Hello. I will share my screen. I hope it works. How can I do this? Can you see my screen? Francesco, I think you're still sharing your screen. Sorry. There you go. Can you see my screen now? I can. Yes, I can now. Good. I have written a program or it's still in Brognes. Not yet ready. That can convert a spreadsheet functioned into the source code equivalent to start the same and for that I'm using programming language. And I have here now a program and when I execute that program and I have here frame. Sorry, I afford I could see your screen but actually we can't. So you can't see my screen. We can. I think you're sharing the wrong tab. Yeah, we can see a screen. So it's only one tab. And I will stop sharing a look. I'll do it again if I then can choose the right. So now I hope I now have now I think I have chosen the right thing. Do you have more than one screen? No. Can you see now? Yeah, good. So here I have written a program that could convert a spreadsheet function to source code and you can see now the spreadsheet function and then program to then do the same. So for that I have the programming language R. So here I have executed the program and I have printed here the frame. It looks before, before that is calculated. Now if I calculate it and then show you again, then you will see that here it is. It calculated here the same thing as it has done in the spreadsheet. This is a small program. I'm still working on it and it's not yet ready. It does not really support many functions, but I will add more support for more functions. I hope that this will be useful for wiki functions and then through that then people can convert to wiki functions through using spreadsheets in this spreadsheet. Definitions can be then converted into other programming language. So this is the idea of this whole thing. Awesome. Thank you for presenting. So let's move on again. And I lost my list. Where's my list? Okay, here. Next up is Scribe from Andrew. So let me share screen really quickly. There we go. Okay, so many of you, everybody is seeing the emulator, correct? Can I get a confirmation? Yes, okay, perfect. Thank you so much. So for those of you who don't know what Scribe is, it's keyboards for second language learners. So we're seeing a German keyboard right here, but actually what this is for is for a German second language learner. Scribe is also available for many other languages and this is fully based on wiki dated information that's coming in as far as lexemes. We're bringing in verb conjugations and noun genders and all kinds of other interesting information to help language learners. Basically, let me just give a quick demo of things that this keyboard can do. It can translate. So you can come in here and hit translate and then you can put in say the German word for book and enter it in here and then we get the German word for book right there. Other things that it can do, we can get the plural of a noun or we can also conjugate a verb by putting in say the German word for go, which is gayen and we come in here and then we can see this is the present tense for the German verb to go. Past tense, perfect tense and you basically just kind of go through and then you hit the verb that you need and then it all works to get you the verb conjugation that you need. Specifically what it is that we've been working on for this hackathon has been a very, very major issue that we've been working on for a while that has been a needed thing is basically adding autocomplete and auto-suggest to this, which is basically fully based off of WikiData. So Rob is also in here. Do you want to check and see if you can talk right now for the last two minutes or so? And there is no... the Android version is in progress. So Rob, are you able to talk or not? Just let me know in the chat. Can you hear me? Yeah, we can hear you. I'll do the emulator and you can talk about what it is you did. Yeah. So basically the main task I was working on was getting the correct words into the autocomplete. So the UI changes that you can see are mostly done by Andrew, but I wrote the function that brought the words into the correct buttons so for that we had to create an array of the nouns that we have. We currently stick to nouns just to keep it simple for the hackathon and WikiData gives us the complete list of nouns along with a few other properties with it. So we had to extract the keys so that we just got the nouns and then we create an array but that was acting as a bottleneck because every time you enter a letter you have to get the array and then sort it again to get the alphabetical autocomplete. So for that we basically just created the array once and sorted it outside and the next part is like when you click on a button the word needs to be inserted, right? So over there we need to take care of three cases which is like when you click on the button otherwise or if you type out the complete word yourself and then hit space and also while deleting. So the space bar was pretty simple you just have to reset all the variables when the word is complete. For like when you choose a button from the autocomplete you need to clear out the text so that it just doesn't add onto the last of the string that is already in the text bar and for during deleting you also need to store somewhere the previous string that was present so that it can go back to the previous state. So that's all I've worked on so I'll just hand it over to Anteva now. Thank you everyone. Yeah, so I'll just from here we just wanted to show this little update this is not going to be available on the App Store anytime probably we're going to work on this and finish up some bugs in the next week or something like that and then get this out to the users and post some links to the project into the chat so that if people are interested you can check it out. We would love to get some support on this as I said we're working on the Android version eventually a desktop GUI there really is a lot to be done and it would be great to have some people support. Thanks so much. Thank you Andrew. Again another cool project that's great to see. So next up we have maintenance script to restore revisions from old SQL dumps from please stands. Okay, so I mean I know this is this sort of thing that is like probably boring to a lot of you I mean with the hackathons like usually people do things like adding new features to apps and new tools like we've seen so far but sometimes you know there are just you know issues that just sit around and have not been fixed, have not been cleaned up and one of those issues is that a number of years ago the Wikipedia's and the Wiktionaries and you know sites like those the Wikimedia sites they didn't use like a number of years ago because the browser support just wasn't there but at some point they did a conversion and unfortunately for some smaller Wikis like in particular Spanish Wiktionary there was there was actually a reported problem that the database conversion made it to where revisions were corrupted and inaccessible and apparently I mean I just happen to see like this comment on this on this years old report from on fabricator that and they'll pop up on IRC with a new comment and I looked at it and realized that the same issue with Spanish Wiktionary which was fixed by restoring revisions from backup also probably happened to a Dutch Wiktionary as well in the bug report I put the links to the various mailing lists posts and things to support that and interesting I noticed because it was one of these things that because like the if any of you saw lego KTM you know recent talk at Hope he mentioned about verbose pasting I mean I think this might have been one of those things so on to my script if I can share my screen let's see entire entire screen share I okay so so if you see here on my screen you see on the actual Dutch Wiktionary you see there is a revision here of an old page that shows the edit summary and it's just completely blank that means that the text of the revision actually was lost and I've set up a test set up you know loading an old old database dumps I got from the internet archive way back machine and I've done a conversion to the latest media wiki that I've done the conversion in such a way as it would have the same issue that we're seeing on the live sites say for example click on here you see the same thing with the page is blank but if you go let's say go to a newer one go to a newer one is blank as well go to a newer one go to a newer one and this one because it was the latest one at the time of that database dump because the way the old media wiki worked it shows up so what I'm going to do is I'm going to run my script first I need to reload the oh use test in our dictionary when you reload the database dump and then I'm going to run my script and I've already you know ran the slow part already ahead of time so I'm just running the the other part of it and this is just a quick hack you know it's nowhere near ready to be merged or used on production yet but see all let's see all all all let's see see now the page it shows up the the and well not that one I mean the the script I mean it obviously needs some work right now it only it only reloads like revision say revisions from like one part of the old database dumps that I had but as I said I mean it's everyone I am Ibelda from the company product team and here with me today is Alon the freed our senior product manager and our product ambassadors for Arabic for French and Anthony for Swahili we have different language support available for live interpretations and our slides will be available in Arabic French and Swahili text today we will share what kind of work is being undertaken by the foundation product team and how communities can benefit from these new campaign projects and we hope for you to learn more about the newly developed feature of the event center which is the event registration system and we also hope to gather feedback from you and how to further improve the registration tool so it can be potentially incorporated into our later releases next slide just a brief background the campaign product team is a software and product development team focused on tools for campaign organizers our main goal is to build and improve the features in the campaign's ecosystem for experienced organizers we want to simplify their work flows and provide more powerful tools and for new organizers we want to make it easier to become effective and long-term organizers we hope that we will see more campaign organizers campaign participants campaign events and campaign contributions with higher retention rates for participants next a very vital part of our team is our product ambassadors they help us conduct multilingual outreach as we wanted to focus both on language and region organizers around the movement speak a diverse range of languages and some do not speak English campaign events are also in a range of languages some organizers have open felt overlooked by WMF especially the non-English speakers so it is our team's goals together with the product ambassadors to share our vision widely gather and receive feedback from organizers in these local communities and also to recruit testers for our first project and create a community of organizers who we can collaborate with over time our vision in general is to build a robust long-term support for Wikimedia campaign events to make this possible we plan to build the event center this platform will focus on improving and simplifying workflows related to top pain points in organizing and event participation this platform will have an organizer side and a participant side the organizer side will provide the tools and resources that organizers need to create and manage impactful event campaigns the participant side will provide the guidance and support that any participants will need to meaningfully engage in any Wikimedia campaigns overall this platform will be a modular which means the features can be separated and recombined based on a special needs of a wiki or community also extensible which means that features can be added over time by our team other teams or any volunteer developers and for our first priority to improve the organizing experience we work on the on wiki registration for event the event registration tool and for organizer we hope that this new feature the campaign organizers will same time they will no longer need to develop any alternative registration solutions and they will be able to collect better data on campaign participants their needs and respecting their participants privacy also on the participant side campaign participants will be able to join campaigns with minimal effort and their first point of contact in the campaign will be fun and inspiring we hope that participation for events around the movement will be easy even if you're just a new editor so I will give the floor to Alana for the demonstration my name is Alana I'm the product manager for the campaigns team before I get started I'll give a little more background also as you can see these slides came from a previous office hours that we had and they include the languages that we have product ambassadors on our team represented so you'll see that they're in English, French, Arabic and Swahili we also have some of the ambassadors in the chat giving a little more context in other languages as well so what I'm going to do now is I'm going to give a demo of what we've built so far so feel free to join along with me if you would like and try out some of these yourself so I'm going to be alternating between these slides and doing a live demo but one thing I should share is this what I'm demoing today is what we call v0 so we call it v0 because it's very new there's a lot of things we still want to do to improve it there's also some of these improvements are features others are smaller things like bug fixes and things like that but the reason why we built this early version called v0 is we wanted to get feedback early on so we know it's working for people what isn't and we can incorporate that in our next version which we're calling v1 and we'll talk more about v1 at the end of the presentation but I'll first demo what we have today so as a starting point v0 is on beta wiki or the beta cluster it's not on any live wikis yet that's because again we want to get feedback we want to learn more before we think about deploying to any live wikis so as a first step if you want to go along with me you would go to this URL and I'll show how it works right here so if you already have an account on the beta cluster that's great otherwise you can go ahead and create one I'll share the URL in our chat for anyone who wants to join along with me so if you're creating an account and again you need to create an account because you're a normal wikimedia account let's say for wikipedia or any other live projects wouldn't necessarily work in this case so I'm just going to create a test account and then I'll create a password right now so again feel free to join me and now the account has been created so the steps I just went through again where you go to beta wiki you create a test account so once you've done that and also by the way I should mention if anyone's following along with me and they want me to slow down because they need to complete a step first feel free to let me know in the chat I see don't know how to use the link, can't copy neither maybe perhaps someone who's an ambassador or who's a part of our team can provide a bit more context in the chat about how people in the call can create an account on the beta cluster so once you have created an account I'll show the next step now so we want to create an event page so what is an event page? Event pages have existed for a long time this isn't a new concept right so what's different here is you want to create an event page in the event namespace so any wiki that would have the campaign events extension so in this case beta cluster wiki has the campaign events extension able would have the event namespace now the reason why it's useful to create the event in the event namespace is we then know that this is an event page that's separate from say an article page or a user page it gives us that specific identification so the way you do that is you type in event colon and the name of your event in the search bar so just like how you create any other wiki page you can search for the page see that's a red link and then click on it in order to be able to make it an event page so I'll demo this right now and again feel free to join me so let's say and I live in Brooklyn so let's say I want to do an edit-a-thon of Brooklyn you'll call it Brooklyn edit-a-thon I click this red link here and now I'm going to create an event page just like I would any other event page so in real life of course if this wasn't a demo there would probably be a lot of time and effort that I put into making my event page look correct but because this is just a demo I want to do a really quick event page should I write something like please join this edit-a-thon that focuses on the history oops of Brooklyn New York okay so now I can publish the page and this is what brings us to the next step so I see one question in the chat how do I edit the event's name so basically you create the name of your event so it's in the event namespace so you do event colon but after the colon it is any name that you want of course if there's a name that's already been used on the wiki just like any other page you wouldn't want to use that again so for example let's say you want your name your event name to be called women's history edit-a-thon 2022 it'll be event colon women's history edit-a-thon 2022 okay so now we've gone through the steps of add content to the event page and publish the event page so the next thing I want to talk about is enabling registration so when you're on the event page enable registration which I'll show right now the reason why I can enable registration the event page is I'm the organizer I created the event so in order to enable registration and enable registration means that there's going to be this header that allows people who are prospective participants to join the event so I could do that in two ways way one which I'll show right now is a pop up that you click on the event page and you'll see a pop up it says enable registration you can dismiss the pop up if you don't want to but if you dismiss it there's a second way which I will also show so now let's go back to the event page so I can either click here where it says enable registration and it brings me to a form or if I dismissed it I always have this option here enable registration which will bring me to the same place so now let's talk about the next step which is adding oops adding basic information about the event so the next step is to fill out the form with event information when complete click enable registration and then it's recommended to review your changes just to make sure that everything looks alright so I should also explain that this part where you add information about the event since it's a v0 it's very basic information but we know in the future that organizers will probably like to have a more complex or sophisticated way to talk about their event so we'll be thinking about ways to improve this experience in the future as well but for v0 this is what we have so let's say so ready has a name of my event and that's because of course I went from the event page directly to the form we have I want the event to be on September 1st and let's say I want it to end on September 6th and let's say I wanted to go from 14 or 2pm you'll probably see the Z here so this is another, this is an example of something you want to fix in the next version so right now for v0 because we wanted to build a very basic first version you can just create events in UTC which are currently represented as Z and media wiki but our goal is to fix this in the future so the organizer can pick their time zone that they want for the event it doesn't have to be UTC and Z would not be represented and still it would show UTC but for now this is what we have you can choose if it's an online event, an in-person event or hybrid online and in-person I'll choose this so you can see both options so meeting URL this would be something like if there's a zoom or google hangout meeting this is where you can specify it you can have the country this is also something we want to improve in the future with how you add the address but for v0 this is how it works so maybe I'll say it's at 500 Jimmy Road and then here I can do the group chat so this could be something like if there's a telegram or whatsapp or any other sort of you know off wiki chat this is where you can specify it and both the meeting URL and the group chat invite would be something that is viewed to people once they register as participants before that they can't see it so then you click enable registration okay so now registration is enabled participants can now register on the event page so I saw one message say my voice is muted I hope people can hear me okay if other people cannot hear me please let us know in the chat so I can fix that so basically you see the top here it says online an in-person event it lets us know the date and time so far nobody has registered for the event yet if I click more details it can also show the location since I'm the organizer I see the link for the video call now what I'm going to do is I'm going to go the other side and show how someone can join an event as a participant now if you're following along if you want to join an event as a participant there's a few ways you can do that you can of course join my event and I'll share the URL but you can also search for many other events by going to special all pages and then after that I'll share the pages that are in the event namespace so there's many events you can also search by going like this but the idea is you basically want to search for an event that you did not create any registration for so you can be a participant so what I'm going to do now is I'm going to share a different window where I am a different user I'm going to share this cool what I'll do actually instead since I think I chose the wrong one I'll just choose what I'll do is I'll choose an event that I just did not create myself and see if one of them has registration enabled so for this one right here I can register for the event and now I'm listed as a participant so Tommy456 that is me now I can also choose to leave the event by clicking on the trash can right here and then I have no longer a member of the event someone else joined very cool but if I ever want to join again let me demo how the join link doesn't show if I'm not registered so when I click more details I need to register it says here to view the event link right now when I register again I can see that the link is right here okay so to go over the steps again for anyone who's following along to join as a participant you can search for events by either clicking event colon and the search bar and a lot of events will come up you can also go to special all pages which gives you access to all the events if you look into namespace in your search then you want to go to the event page and click register for events which will automatically register you then the next step which I also demoed is canceling registration as a participant so to do that you click on the trash can and then you're unregistered if you want to register again it's as simple as clicking register for a bet so I just demoed how a participant remove themselves now I'm going to show how an organizer would remove a participant so sometimes organizers want to remove participants maybe it's a trust and safety issue so for example maybe someone who joined event is someone that the organizer knows has caused issues in the past and they think it's not a wise decision for trust and safety reasons for this person to attend maybe the person is having trouble removing themselves and they ask the organizer to do it for them whatever the reason maybe we wanted to give the organizers that power to make that decision so the way you do that as an organizer is there's instead of register for event there's a button that says manage event so you click on the button that says manage event then you'll see a view of the participants who registered for your event you can select one you can select some you can select all and from there you choose to remove them so I'll demo that right now so let's see if anyone has joined my Brooklyn event if not then I'll have so many people have amazing so whoever I remove it is nothing against you personally it is just for the demo so I click manage event and I'll remove a melda so to do that I can click her name I could click all but I don't want to do that I just want to remove one so to do that I click here and I remove and the participant is now removed from the event so another thing you can do as an organizer is edit the registration information so for example maybe I added some incorrect information into the registration question what if the participant still shows up that's always a risk potentially so I think that would be an interesting discussion for us to talk about afterward because I think there's a lot of ways to think about that so please hold that question and let's see if we have time so to edit the registration information I'll show there's two main ways to get to edit but one way from here so is I go to edit another way is I have a my events list see these dots you can click here and also go to edit event so the my events would be a list of all the events you have organized so here let's say it's not 500 Jimmy Road I made a mistake it's 550 Jimmy Road so I can just make the change and then I click edit registration now I can go back to the event page and I see it is now 550 Jimmy Road question so only the participants see the list no for v0 we have it very basic in that organizers and participants and just the general public of anyone who's on wiki pages can see the list of people who joined and that's inspired by a lot of on wiki registration now where you can see who joined events but we also do know that some organizers are interested in confidential registration so that means that someone registers for an event and only the organizers see them for that that's something we're planning to look into for later release but it's not something that's currently available in this version so that's edit now let's go to open and close registration so when you create or when you enable registration on event page it's automatically open but perhaps you want to close an event registration so maybe there's a certain number of people you want to register reach the capacity whatever it may be when you close registration that means new people can't register so the people who register in the past the registration is preserved but new people can't come and join if you close about registration you can open it again but it's your it's your choice but you want to do really so I'll show now how to close and so you can go to my events or edit and then if you go through my events you click the three dots and you'll see it's the closed event you'll see open registration and if it's an open event you'll see closed registration you can also do it through edit so I'll show both versions so let's go back to the manage event so we saw here these dots you can choose here to close an event or open similarly if you go to edit event status is open you can change it to closed if it's closed that means that the registration header at the top that says register will no longer appear to so feel free to also go back to my event page and if you haven't registered already you'll see you no longer can so now delete registration so delete registration is very simple for v0 so I'm not going to complete the deletion process because right now we only have the ability to delete registration but we haven't built in the ability yet to restore it and I don't want to delete this because I've been using this to teach you all how the product works so I think it's more useful to keep it up but I'll show how you go about it do it so delete registration you're going to have the three dots and you click delete event and that will go ahead and delete it so if I wanted to I click delete event I'm going to cancel I'm not going to confirm this but if I truly wanted to delete I would click delete so those are the basics of v0 and how it works we are also though very aware of the fact that v0 is just the beginning there's a lot more we want to build for event registration and there's a lot more we want to build for events in general the on registration so Melda now is going to talk about some of our future plans and then we'll open it up to questions and thank you all right thank you Alana so what's next from our team coming in October on Metawiki organizers can message their participants via email or their talk pages also integration with programs and events dashboard and support for multiple organizers for one event also coming in in January also on metawiki registration for some events for example events that has two locations events that has in-person gathering or virtual participation also confidential registration where in participants participation of volunteers can only be seen by organizers not by everyone who joined event and also optional questions that an organizer can ask participants for example organizers can send questions to their participants during their registration also for our next steps first we will love if you can test the event registration feature on Betawiki share your feedback on our channels you may use our talk pages on Metawiki or the feedback form that we are going to share in the chat you can also subscribe to our newsletter to receive updates on our projects and any announcement on testing and version improvements also you may join our telegram group which is a community of Wikimedia organizers so now we are going to answer your questions I'm here do I see your hand up or is that just it looks like your hand up yes I see my hand up hi excellent presentation thank you you mentioned at some point that it's possible to see a list of events on special old pages which makes sense because these are just pages is it also possible to see all the available events something like a calendar great question so this is actually a future project plan for us so after we do the event registration project we want to do what we are just calling now the event page creation project so right now for some organizers they already have workflows in place for how to create event pages and feel rather comfortable with it for others it's a lot of work and a lot of maintenance so we would like to just how you saw with that form of information for registration you can think about it as sort of an extension of that you add more information that is you know I think useful for you to share for participants and then it can generate an event page without you having to do stuff with like wiki text or templates or whatever yourself so what we imagine the future is when you are creating the event page or if you are not using the event creation tool there can be other ways to do it but there is a way to specify if you want your event page to end up on so you don't have to say manually create some sort of calendar yourself there will be some sort of infrastructure that we create the future around that calendar that's in the future so we don't know a lot of details yet but what we imagine and we hope is that it will make it easier for people to find out about what's going on at any time and they can even apply search filters for things like topic area or location so they can find events that really excite them I think Natasha is tracing her hand yeah maybe you answered the question already but I have trouble understanding when it's people speak very very fast so would it be linked to the event dashboard eventually or not another great question so this is actually our plan for the next release so we have another release that we're planning for roughly in October we don't know the exact date because we just started this phase of the project and of course with software development there's always unknown so it's often hard to say at early stages but we're planning for roughly October and for this release we want to have integration with the programs and events dashboard and we're actually working directly with Sage Ross from Wiki Education to make this possible so what we want is that if you as an organizer have created a dashboard instance and you also are using your registration tool if anyone registers for your event as a participant or user name can be automatically pushed to that dashboard event so you wouldn't need to manually add user names yourself or have the participants during the event add the names so in short yes it's in our plans in the next few months great thank you you're welcome techno you can raise your question ask your questions on the chat would you like to ask your question if not maybe we can go to Gilbert to see his hands up as well thank you Rana just to say thank you for having think about this system because it is very easy because previously we have been answering two questions of a participant asking please check if I have been registered and when we are organizing things we have to check for messages and the answer and the check and sometimes it was difficult to check how to see if someone have registered but for now it is easy just for a click you see if you are registered and if for the second time you register you click and you are informed that you are already participant you can register for the second time just to say thank you thank you for having think about this system great well thank you so much for sharing that it's really appreciated and that also reminds me what you said we heard from other organizers when we were doing research before this project began which is that some organizers that use some tools especially the tools where someone registers but it is a private list that is not publicly shared people don't remember sometimes that they have registered so they will contact the organizers and then the organizers have extra work of essentially letting them know or not if they have registered already so this takes away some of that burden hopefully so it is great to hear from you that you feel like it would very great thank you one question from John okay so the diff calendar yeah the diff calendar so overall with all our tools I don't think we are aiming to replace anything we understand that Wikimedia is a super complex ecosystem that has a lot of decentralized ways managing things and determining what is best for different communities and different needs so that is not our goal to replace the diff calendar our goal is though to work really closely with organizers that currently feel like a lot of the existing workflows aren't working for them and find solutions that can give them meaningful improvements so they feel like they can lead more impactful campaigns and so that they can do more of the work of actually organizing rather than dealing with technical hurdles so when we do have the calendar project in the future we will also look into how we can complement whatever we do with what exists rather than trying to replace anything and so I guess too if any of you have any thoughts or feedback what would be the most useful way to provide some sort of calendar support feel free even if we are not on that stage yet of doing the work ourselves because we will launch the project feel free to share it because the earlier we get feedback the earlier we can start thinking through some of these complexities I think we have one very good question on Etherpad will a future version include a functionality where you can have the event details sent to your email or added to your calendar yeah it's a great question so maybe yeah so another thing coming in October we made this slide very shortened but there's more features actually that we're planning in the new release and another one is confirmation email so right now it's very simple you register as a participant and that's it you don't really get a confirmation email but we know this is really important so for the next release what we're looking into now is after the participant registers if they have an email address associated with their account and they don't have anything in preferences where they said they don't want to be emailed so they allow email then we will have an automatic email sent to the participant the organizer doesn't have to do anything and will have all that information event details sent to the participant so they can easily access it at any time through their email I also see a question in the chat do you also plan to add a feature for newbies to create a wiki account through the registration tool so yeah so right now let's say you want to join an event and you aren't logged in or you don't have an account yet the way it works is you can still see the register for event button it's not that the call to registration is only for logged in users but in order to complete registration we have you log in right now it takes you to the login or sign up page and then after you do that it will bring you back to the event page so you can easily sign up but one thing we could consider in the future is ways we can improve that intermediary step when someone is either logging in or signing up to make it just more user friendly so let's say I want to sign up for the Brooklyn edit-a-thon maybe there can be some sort of text that says in order to complete your process of joining the Brooklyn edit-a-thon you know please create a wiki account and maybe there's even some sort of image or graphic that's like the logo for the event so the user can really recognize okay I need to complete the process we haven't done that yet but please feel free to also share any suggestions for how you think we could make the initial account creation process more encouraging for newbies because a high priority for us is we don't want people to essentially drop out because they have to log in or sign up. We want them to complete the process so anything you think can make that more possible or encourage people to do those last steps we really want to hear it. Another question, when is the expected time to start using the event planner? For that I think it's the event calendar unfortunately it's too early for us to say so if I gave a date it would probably be wrong so I think what's better is to join our channels for various modes of communication so when we do have a better timeline we can share that with you. So ways you can stay informed about our teamwork is you can join our subscription list we send messages they're usually bulk we try to send a few things all at once about things that the team has going on every now and then via mass message so be on your user talk page about team updates you can also watch our team page on Meadowickey and if you do that I think the best way to stay informed about the work we're doing I should also mention we have a telegram group that's multi-lingual that's for organizers it's not only a place for people to come together who are organizers who want to share resources but it's also a place where we'll be sharing product updates as well and you can directly talk to us as well as our product ambassadors who are available for French, Arabic or Swahili as well as of course English for any questions you may have someone asked for sharing links in the etherpad it's like I saw Melda nodding so I guess that's coming up let's see if there's anything else we already shared the links in here but it also subscribers please and I saw that accurate well back I loved the new innovation about the registration tools thank you so much Natasha a very interesting tool for UA organizing editathons and so everyone who's sharing feedback we would love to hear from more from you essentially the feedback form so I'll show you how the feedback form works as well we want to know what's working what's not working because this is really the beginning it's not the end so if there's things you don't like we want to know so we can find ways to improve it so this link right here which you can also see in the slides and I'll share again the chat the feedback form you pick your language and then there's questions that you can answer some of the questions are things like what do you like what do you not like would you use this and here's the link again and I will register for your oh so Natasha the link you sent is in your event page this is it's kind of more like you could think about as your folder or organizer of your events instead of saying special my events it would have the name of your event so if you send the link of your event page I will register for your event as a participant okay so why doesn't it show another thing you can do that's what I wanted to you can also go if you forgot the name you can go under user contributions and you should be able to find your event page the event is said again that's the name of the I just posted the name of the event yeah thank you thank you so much this is the name of the event okay you're now two participants great so now I can remove one of them thank you no problem someone asked how can I get the tool for everyone in testing in the beta cluster but in the future we want of course for this to be a live wiki not just on the beta cluster so we're aiming to release it on meta wiki first there are a few reasons why but one of the main ones is it's really great for event organizing there's already a lot of event pages on meta wiki it's a multilingual wiki so that could be a great place for you to be using in the next few months if you would like to be one of the v1 testers you can also let us know now in the chat you can contact us later you can reach out to us on telegram and we can give you more updates on v1 and how that will work thank you ever so much I'm going to use that for sure that's great to hear another comment I love that we think about events at all because today they're either manual wiki text or off wiki but it'll be great if we were collaborating on one tool I think WMDE is investing in diff well this is really great to know this is also really aligned with our vision is that there's some stuff that currently exists for edits on wiki but of course that really is more geared to people who feel really comfortable creating and managing events on wiki or people who are especially interested in targeting participants who are experienced themselves but we're seeing that there's a lot of organizing activity that's already going on off wiki either due to maybe the organizer feeling more comfortable in those spaces or them feeling like participants can't easily onboard to on wiki flows and processes so our hope is if we simplify these experiences then more people can do the organizing and their event work on wiki which is better of course for the movement as a whole and as for again the calendar part that's something that we can totally explore and work out together in the future so it's good to hear about how WMDE is thinking about it as well and we've also been talking with WMDE in our current work so with event registration even we've already been talking with WMDE so we'll continue that collaboration with also the new tools we build we only have a few minutes left we have four minutes left so people of any last questions please share them if not I guess we can wrap things up so thank you so much for joining our session we really see this again as the beginning of us creating and improving a lot of tools so we strongly encourage you to join us in this process join our subscription list join our telegram group share feedback in the google form or on the talk page reach out to any of us in the team we would love to hear from you and thank you so much for coming to our session alright so goodbye thanks everyone hello everyone I'm very happy to have you here welcome to the last session before the closing ceremony of wikimania 2022 I'm super excited to be here super happy to have you all here even though I have no idea who you are because I don't see anything thanks to the virtual event we want to talk about wiki functions I will give a very short introductions into wiki functions before I let my team talk about it I have a few fantastic speakers who will talk about different aspects of wiki functions and then we'll go to a Q&A session at the end what is wiki functions wiki functions will be a new project of the wikimedia movement the first one in almost a decade to start we it's a wiki for functions and functions can do things like calculate things add information to existing data and so on so to give examples of functions given a date of birth you can calculate the age of a person or given population an area you can calculate the density of the place and so on and all these things can then also be used in the wikimedia and kept up to date for example based on data and wiki data so we can draw the population directly from wiki data make a calculation on it and display that in the wikimedia this way we can keep more information more data up to date and share it also across the different language editions of wikimedia so you can call those functions you will be able to call those functions instead of the wikimedia or the other wikimedia projects you will be able to call these functions in other modalities like just the wiki functions directly itself our plan is to keep working on it we just launched our better version we're not there yet to really kick off and launch wiki functions we'll do it when we're ready I hope this will happen in the future but I don't want to commit on a date but just make sure that we are getting a better point where we are satisfied with the products that you can launch we will start launch with small product just as we did with wiki data a decade ago so it won't have all the functionalities yet but rather we will grow it over the amount of 7 years to add more functionalities and to allow for more possibilities of wiki functions the mineral project won't be integrated into wikimedia yet and all of this but it will show you the first direction of where we are going to go one of the main goals of wiki functions is to also provide functions that generate natural language text that natural language text is then meant to be a foundation a baseline of knowledge that will be available in all the different languages of wikipedia so that we can write an article in abstract rotation abstracting from a natural language translating it into natural languages full of functions and wiki functions and make it available in the 300 or more languages that wikipedia supports so this is the rough idea this is the goal I'm very happy now to let the team members speak on certain aspects of wiki functions and see you after that for Q&A if you can roll the video please, thank you Hi everyone, I'm James Forrester I'm the lead engineer for abstract wikipedia team working on wiki functions I've been a staff member for 10 years and a volunteer for 20 years on wikimedia projects and I've been working on abstract wikipedia since we started in 2020 so the overview of the technology is that we've kind of split the code into two parts, there is the bit that you interact with directly that displays your functions your test cases, your implementations and your discussions about whether this is Hi everyone, I'm James Forrester I'm the lead engineer for abstract wikipedia team working on wiki functions I've been a staff member for 10 years and a volunteer for 20 years on wikimedia projects and I've been working on abstract wikipedia since we started in 2020 so an overview of the technology is that we've kind of split the code into two parts, there is the bit that you interact with directly that displays your functions, your test cases, your implementations and your discussions about whether this is a good idea, your community forum all that stuff all of that is in media wiki all of that is hopefully as familiar as possible with it being a totally new form of content for community members to be working on and then on the back end we have services that actually take your code and run it based on requests so the front end is a media wiki extension wiki lambda which was the first kind of code name for the project before wiki functions was community picked as the project name the wiki lambda code is media wiki extension so the content is stored as side media wiki, you can view, edit, interact with the content, you know, look at diffs write abuse filters all that on media wiki in the normal way the actual front end is written in Vue.js which gives you a very rich experience for doing complicated things like creating a new input of a particular type that is live created every time you input a content and setting a label for it in 12 different languages of the 500 or 2000 that we potentially support then on the back end we have two services, one of them the function orchestrator which is kind of user facing potentially and it's where you can request hey, I'd like the function to use this piece of data from I'm James Forrester, I'm the lead engineer for abstract wiki community I've been runs through that to that wall to have some serializes and deserializes in certain cases depending on your content type and then palms that all the way back up stack, that way you're not running user written code on the same service that have access to the databases and things like that so there's kind of separation of concerns but that's kind of our general stack I'm Yisemin, I'm a designer on the abstract team currently working on wiki functions and today I would like to share with you a small update on how we're approaching design wiki functions and for the purpose of this update we're going to look at some of the objects that are currently available on wiki functions and how the display and how the visualization of this object is going to change following a new design language so for example we're going to look at this mushroom object and for wiki functions objects they usually have a custom way to be visualized but it can happen that certain objects don't have like a custom component to be visualized so they're going to fold back to a default component so everything that you see here in this dash line is a default component sorry so they're going to fold back to a default component so everything that you see here in this dash line is a default component because in this case this object doesn't have sorry I'm trying to screen share again now instead of like but it doesn't allow me to have some component to be used for its own display and so we can see that this object mushroom object has type has an identity has different keys we call them attributes or properties like it has family, it has a species it has a genus and also the creator of this object decided also to add a list of common names and then here on the right we see another object which is this mushroom type of mushroom called the mista sub scupta and here you can see that the creator used the previously defined object to visualize or to define what is the family, what are the species and what's the genus and what are some common names and I apologize for what you see here it's currently but we're working on it but imagine that you can see a list of common names and so the way we are approaching this is the following so what we're trying to do is to reduce the amount of information and content available when you land on an object page to its essence and basically display just an overview of the information and then let editors go deeper only if they want to so the concept that we're trying to leverage is the progressive disclosure of information through interaction so basically every action of an editor is going to disclose information at their own request and here for example you can see our object and so at a glance you can see the type, the identity the validator and you can see that it also has like four items or properties here you see this Kalpovista mushroom using the previously defined object and you can immediately see at a glance what's the family, the species the genus, some of these common names and here on the right you can see another object that might use another type in this case is a type common and it's using and it's defining the title and the author in this case and so to go a little bit deeper on what we mean with progressive disclosure on information so it's basically this what you see here is a potential flow for navigating this information so let's say you go to this mushroom object page and you touch or you click if you're on mouse input or trumpet input device these row keys it would open and it will display what are the keys that are currently available in this object and then if you would touch or click on a specific key again you would go a little deeper and you could navigate what's the belly type, what's the kitty what's the genus and as you can see there's also the language icon and that's because you could access potentially available translations for the specific keys and in the scenario where the key is not available in the same language as the language you have set you're going to see a whole language based on your own preferences or navigation history with a dedicated language tag signaling that is a full-back language so this is how we're approaching design and how we are thinking about organizing information with your functions I would love to hear your feedbacks on your thought and thank you very much for your attention Hi, my name is I'm a staff software engineer in the AFSA Wikipedia team my colleague James already gave me a nice introduction on the architecture of the functions but I wanted to go a little bit in depth into the persistence and the content model I want to do this because it's ultimately what allows the functions to be a wiki and to collaborate, edit create objects but it also is what adds very big vulnerability ultimately the functions are user contributed code that will be run in our service so that makes it very important now I'm sure you're familiar with the type default content model of Wikipedia which is for wiki text in the case of the functions the content model is for the object so media wiki offers great tools and abstractions to handle this kind of difference we do this just as a very very brief technical overview by setting the configuration to say which is the class that is going to be handling this content and this class is in charge of creating object content but it's also in charge of making transformations from one way to the other so for example when we're reading stuff from the database and we're sending a browser to modify that content in order to make it readable to the user and create the UI but also when we send data from the content or from the APIs to save it in the libraries we'll do validations and transformations to make sure that this data is secure so what is called content object from the point of view of the function model is what we call persistent object set to now as an object content is just the JSON file but this is really heavily structured and this is an example of it persistent object it just adds a layer wrapper around the virtual object that we're saving so that we can save metadata this metadata is for example an internal identifier or a page name this identifier is extremely important to keep unedited so this needs to be remained completely locked and secured once it is created I would say that this is our current state right now when saving as an object the ID cannot be changed it's completely forbidden and also there's a set of additional validity checks like for example it should be a valid JSON or it should be a valid zero but there is a bunch of other things that need to be checked while saving for example this other third piece of metadata which is multilingual identifiers labels and aliases this is free to anyone to edit to add new labels and new languages but the actual content is a 2k2 which is what contains the or the function or the type this should be protected in certain aspects some pieces of it should not be edited and some pieces of it are open for edit now to illustrate what we're going to be working on in the next month I wanted to create this really easy example for Hackerize this is a function that transforms as an Wikipedia into a hacker language word it's very simple now when I do an edit what I'm sending to the backend is this full JSON file with a number of changes all of these changes will be done using a UI so that the user doesn't have to come from this kind of z object language but what the backend is receiving is this JSON file and the backend needs to understand what's going on changes are happening and whether those changes are allowed or not so as I said before changing the object ID is completely forbidden this is fine and if I add a new label to the function this is completely allowed and anyone is welcome to add labels and aliases to this function now there's four other edits going on on the content block what happens with them there's changes like for example changing the argument key that should also be completely forbidden so if I change the way that an argument is internally referenced every function call that is calling this function will be broken so this is something that needs to be detected and completely forbidden but then there's other changes like adding a new label to the arguments instead of like only having one English label will have two that is open to every user to contribute there's other changes for example like adding a function tester or adding a function application allowed but they're only allowed to privilege users, users that know which testers and which implementations are safe and are okay after reviewing so all this intricate understanding of the object that is being represented finding which changes are allowed and finding which changes require certain types of privileges is something that we are going to be working in the next four months I'm very excited about it I hope you are too and keep reading our newsletter because I'm sure we'll be talking a lot about this thanks a lot and I'm going to talk a little bit about wiki functions and how it makes use of a tool called codex so hopefully you've seen some of the videos from my colleagues to talk a little bit about what wiki functions is and how it works but for the purposes of this it is basically the UI or the front end that allows you to interact with functions in the wiki world so codex is a toolkit for building user interfaces within the wiki design system I'm reading this from the screenshot for the documentation and so it basically contains both the design pieces of this is how things should generally look and feel this is how interactivity should generally work but also relevant for developing the front end it has an actual view of three components and so you can see on the left-hand side where this red box is a list of some of the components that codex provides for us and so I like to think of this as things that I might see on any web page that's not super relevant to the functionality of that specific web page like a button, a checkbox, an icon things like that and so what's really nice about using this library from a developer's perspective it means that we don't need to write and maintain the code for something that's going to look nearly identical to that of another wikimedia extension or something like that and it also means from the wikimedia perspective that all of the different wikimedia products will look and feel very similar so even if you're new to wiki functions you don't really know a ton about it but there's a lot of interactions and visuals that are familiar to anyone who has used something like wikimedia for example so this is an example from wiki functions so what we're looking at here on the left side is a screenshot from the function page so I'm viewing a function that's called echo and what I'm viewing on the right side is a developer tool which is a view extension to the current browser and so the part that I kind of highlighted in red is a codex component called tabs tab container and then the about is grown tab and the details is another tab and so just to kind of reiterate what I said earlier what's nice about this is I can grab that component from codex and then I actually only have to worry about the parts below which are very specific to wiki functions whereas the way tabs work is not necessarily kind of what makes wiki functions special and so that part I can sort of abstract away from my application and so what I'm looking at on the right hand side is sort of like an under the covers here's how that actually breaks down into individual view components for anyone who's familiar with view so what I have here the cdx stands for codex so you can see I have this function viewer that's my component that I'm serving and then that holds in the cdx tabs component cdx button component and then the individual tab to the codex component hey I want these tabs to be called about in details and I just want you to route me when they click about I want them to route me here and when they click details I want you to route me here and codex sort of out of the box will say okay this is the line that we have this is the color that it changes to be all of that cool stuff and so this is just even one layer more under the covers a little bit about what the actual code base looks like this is part of the wikifructions code base which is available online and so this piece here on the left hand side is html and so on the right hand side in this little box you can see how you might actually use codex in an application you set it up as a dependency and then you do something like require quote at wikimedia slash codex dot name of the component you want so we just looked at tabs and so I have tabs which is like I want to have a place where lots of tabs can be and then the individual tab and so then once I've done this I can go back to the left hand side and I can use it like I would any other html component it has particular props that are relevant to it like the names of the tabs and stuff like that all of which is available on the documentation page but for my purposes it works just like any kind of out of the box html component so that's a little look at how wikifructions is leveraging some of the cool stuff that the foundation has to kind of offer and hopefully you enjoy Hi my name is Corey Massaro I'm part of the abstract wikipedia team I'm here because I'm interested in language and like probably all of us the democratization knowledge I'd like to present a little bit on a topic that's come up a few times with respect to abstract wikipedia and that's basically a set of questions around belonging, diversity, equity and inclusion these questions generally take the form of how do we make sure that when abstract wikipedia is launched and we're generating articles and a whole bunch of languages the perspective that's being represented is as diverse and inclusive and equitable as a set of languages we support and there are real challenges to that these are known challenges and we've discussed before right now we don't have answers if I said we did have answers we should be worried because that would be a reflection of the same problematic dynamic we're trying to resolve here but hopefully we're asking good questions I recently had the opportunity to do an international arts residency and while I was there I got to speak with people from a number of different linguistic backgrounds many of them spoke all of them spoke at least one hegemonic language but many spoke languages that we would consider under-resourced within the wikipedia project so this was a lot of ideas how can we use abstract wikipedia in the future it also let me with questions to ask and pointed me toward where different aspects of inclusion intersect so ultimately I'm hopeful that we can cultivate partnerships and conversations around these questions within a broader set of communities so one thing that came up was about the neutrality of facts when I asked people what they would like to share on something on a platform like abstract wikipedia people would say things that generally related to where they came from places where they lived and this is a little bit challenging because a place where you've lived has a particular tree or bird that is not threatened for example because of a war or the place itself has been inalterably terraformed because of war you're automatically getting into a political territory and so it's difficult to get knowledge democratization right because we want to think that knowledge can be neutral and it can be objective but often that's not the case but really these conversations excited me it means there's a lot to learn about the world and I wouldn't have learned any of this interesting stuff often sad stuff and interesting stuff without talking to people whose experiences are vastly different from my own so this makes me really excited about abstract wikipedia it means what can abstract wikipedia do it can expand access to historically under resource languages that's what we often say it's going to do but it can also amplify the voices of those languages speakers selfishly I want to read and hear more of these kinds of stories I want to have my own perspective complicated and I can maybe do that if I have a system like abstract wikipedia that lets me read in one of my languages stories and perspectives on knowledge that come from people who do not speak in my languages so I felt that was interesting another thing that came up was a set of questions I had around how people interact with technology so a lot of the ways people responded to this were pretty expected you know it's easier or harder to use software in one language or another if you speak a hegemonic language obviously the internet opens up greatly but then I also had some conversations that ended up being about literacy and this is really fascinating because I talked to people who were clearly fluent in literate in multiple languages multiple hegemonic languages usually but they also had a language they spoke at home or among friends and didn't read that language in particular and that people who spoke grumanji a Kurdish dialect and you know they'd say things like yeah when we're talking with our friends you know that's all fine and we exchange text messages we send like voice messages we don't send text we even looked at some online corpora of poetry and it was really hard to read it but like if somebody sat there and sounded it out everybody else could hear it so that was a really interesting thing to witness so when I think about how abstract Wikipedia has generally been conceived as a text based project I'm reminded always that there's you know there's time to restart a video for some reason last made me hopeful even though it kind of raises the bar on maybe what we should hope to be able to do with abstract Wikipedia that's my piece I hope you found it interesting and that we can talk about this I'm sure there'll be some contact information shared somehow after this so please reach out a Google Earth fellow for abstract Wikipedia working in the natural language generation works in the previous video my colleague Corey raised an important question how do we foster an equitable and diverse abstract Wikipedia a partial answer lies in the following we should foster an inclusive and diverse contributor base for abstract Wikipedia especially among contributors from low resource language communities this means in particular that we should cater for occasional contributors or contributors who lack programming skills of formal linguistic knowledge of course at the same time we also want to encourage contributors who want to get more involved for those who have more technical or linguistic skills what does this mean in the context of NLG that is natural language generation this means that the creation of basic natural language renderers key component of abstract Wikipedia should be as easy as possible not requiring a lengthy training while at the same time handling complex linguistic phenomena should be made possible for advanced contributors this can be achieved by modeling renderers using templates templates have been used for a long while within this field of energy in the simplest form templates can be sort of as text interspersed with placeholder or slots let's look at an example in Wikipedia we can find some information about Marie Curie such as her date and placeholders the location and contributor could write a simple template to render this date that such as the following person was born on date of course in place of course when we fill the placeholders with the content from Wikipedia that we get a sentence such as Marie Curie was born on the 7th of November 1867 in Warsaw at this point you may want to tell me come on this doesn't even work correctly for English as even the position may change in front of certain placeness as the example here shows in other languages which regularly exhibit phenomena such as verbal agreement or case assignment such an approach might not even work for the simplest cases and indeed you are right for this reason we enhance the template language syntax with a dependency grammar annotations dependency grammar is a linguistic formalism used to describe a sentence which can model phenomena such as agreement or case assignment our idea is that advanced contributors will be able to correct or enhance simplistic templates with the right annotations in order to get grammatical output just as seasoned micropedians may correct or enhance contribution of occasional community in the example here you can see that the French template is augmented with subject and mode labels to correct the renderer to enforce subject verbal agreement this permits render in the sentence Marie Curie and Ne the setting of home with the correct feminine form of the participle Ne if you are interested in more details you are welcome to read and discuss our proposal on metawiki stay tuned as well for the upcoming episode we eat the newsletter which will discuss this proposal thank you I am a very fellow working with the abstract Wikipedia team on the wiki functions project I will be presenting the work we are doing on the semantics of wiki functions first of all what is semantics in programming language theory semantics describes how programs should be executed in a particular language one way to do that is to describe the relationship between the input and output of a program for example we can convert temperatures in celsius to temperatures in Fahrenheit using this function take the temperature in celsius multiply it by 9 divide by 5 and add 32 here is how the evaluation could look like for the temperature of the human body here I highlight in each step the part of the program that the evaluation is focusing on first we replace the function by its definition and substitute the input value of 37 which gives the second line then we multiply by 37 sorry we multiply 37 by 9 over 5 which gives 66.6 and finally we add 32 which reduces the result 98.6 we have to be careful in the order in which we do the operations everyone knows it will be wrong to add 32 before multiplying by 9 over 5 that would give an incorrect result this is exactly what semantics is about by defining precisely evaluation rules for the language we can describe how programs should be evaluated in a correct and unambiguous way semantics is not limited to evaluation order it also describes how variables should be handled and substituted which terms are considered valid and which ones should produce errors and more as you may imagine in wiki functions this can get quite complex not only can we define functions in a native language like javascript or python but we can also define them by composition using other functions as building blocks and each of those other functions can themselves be defined then anyway in javascript in python or by composition and even built-ins we need to carefully orchestrate the evaluation of all these functions in order to get the correct result by being rigorous in our definition of the function model and its semantics we can give a precise meaning to all of this by the clear definition to which we can refer to here is a preview of the evaluation rules we are working on written in mathematical notation this work is still in progress but it has already allowed us to find and correct ambiguities in our model and bugs in our implementation thanks for your attention and we look forward to your questions hello all again the video is also available in comments and can be viewed there before the translation yet sorry for the technical issues that happened at the beginning of the video in the middle of it so we have no time for Q&A we still have 6 or 7 minutes available I see a few questions already there one was where can I get the weak functions back and is that once we launch we will make sure that we set up the usual merchandising machine and we will have all the usual functions so the team got an early version of this and I am very happy to have it here thanks to the community for the logo it is really growing on us second question maybe have a large language model similar to lambda and others there is one thing where we are very different in large language models so in wiki functions we use functions to generate natural language text which means we are using basically rule based systems that say if you see this do this and so on created all by the human developers and the data in wiki data for like so graphical entries we are not using a large language model in the background which is machine learned and which is doing this automatically the main reason for that is that those language models are not as editable one main feature of a wiki media project is that the contributors when they see a mistake the right edit button fix it mistake and see it being fixed this is something we don't know how to do with large automatic language models yet this is why we are using this currently quite out of fashion approach of a rule based natural language generation system and we are building on decades of knowledge in this area in order to make this happen but this means we will not we will not be providing a language model like this it also means it's not really something that the wiki media foundation would be best poised to do because the text that we have available it's either wikipedia and those are not really large enough for the kind of large language models that are currently out there where they usually take the whole web and other sources in order to build them be created by google or deep mind or facebook or apple they are always building on a much larger corpus than just wikipedia so all of this doesn't really put us in the place where we could provide our language model for our own there are open organizations working on these kinds of things and we support and there are ideas of how to use language models even within web security pdf for example to choose between two equally well looking alternatives and similar things or to check whether text makes sense and so on but it's not on our main route for the beginning those things will probably be added later as we go on next question I've just found out that labels of object properties like set 10024 mushroom can be translated however I try to do the same if set 4 type or set 2 persistent object their properties are not translatable using the normal edit interface are the cortex properties going to be translatable too so yes they will be translatable they will not be entirely editable but it should be possible to add translations to them they are still working on the rights model and on the right so this is not implemented yet and this is why you can't do it yet on the better properly but eventually yes it will be possible to add and edit labels on the core models but you won't be able to change the core model unless you have the right rights which will be quite locked down because a change to the core model can cause a lot of issues so how is your time plan holding up still launching this year originally no time plan was to launch last year so it's not holding up great no but things are different than we were planning originally so I really hope that I don't know to make any promises I really hope that the launch will go forward in a not too far future that we will see in the next few months the launch better that we started last week gives you a view where we are and you will be able to see how we progress to a place that we consider launchable we will also have a continuous discussion with the community about what really needs to be in the launch but what doesn't have to be and within the team as well so I don't want and we never made really a promise about when we will launch we will get out there ready but particularly with the Google.org fellows and with the new people that are joining our team I'm confident that the state won't be slipping too much into the future so I'd rather have you something to use and play with sooner than later and I think this is a shared sentiment on the team so I'm pretty confident that you'll have something to play with sooner than later but again, I'm not making a promise about it later I'm checking in if a pet whether they have more questions coming in just because I already have too many screens so we're also at the end of the session actually just seeing so thanks everyone for being here we have monthly volunteer corner you can come with more questions you can also reach us on our mailing list and our telegram and IRC chats so please feel free to reach out with more questions and take a look at the video again without the technical difficulties I hope so thanks everyone for being here thanks for the organizers for giving us opportunity to talk and I'm very excited about how the next few months will look like thanks everyone