Merge pull request #1233 from asweigart/fix-make-html-errors

Removed rst text from talk descriptions to prevent errors during make…

Author: jonafato

djangocon-eu-2021/videos/djangocon-eu-2021-django-with-postgresql-superpowers-paolo-melchiorre.json

@@ -1,5 +1,5 @@
 {
-  "description": "Every time we\u2019re going to create a new project with **Django** we make assessments on its requirements to choose the best architecture, of which, the **database** is usually the core.\n\nDjango is a _database-agnostic_ web framework but natively supports only 4 **open source** databases: PostgreSQL, SQLite, MariaDB and MySQL.\n\n**PostgreSQL** has the _richest feature set_ of any supported database and some of these features are natively supported directly in Django via its contrib module.\n\nIn this talk we\u2019ll see how to use to our _advantage_ the features of PostgreSQL as a database in Django, its exclusive features present in its _contrib module_ and also other **superpowers** that can be exploited through the use of _third-party packages_.\n\n--- \n\nMore info and slides: **https://www.paulox.net/2021/06/03/djangocon-europe-2021/**",
+  "description": "Every time we\u2019re going to create a new project with **Django** we make assessments on its requirements to choose the best architecture, of which, the **database** is usually the core.\n\nDjango is a database-agnostic web framework but natively supports only 4 **open source** databases: PostgreSQL, SQLite, MariaDB and MySQL.\n\n**PostgreSQL** has the richest feature set of any supported database and some of these features are natively supported directly in Django via its contrib module.\n\nIn this talk we\u2019ll see how to use to our advantage the features of PostgreSQL as a database in Django, its exclusive features present in its contrib module and also other **superpowers** that can be exploited through the use of third-party packages.\n\nMore info and slides: **https://www.paulox.net/2021/06/03/djangocon-europe-2021/**",
   "duration": 1871,
   "language": "eng",
   "recorded": "2021-06-03",

djangocon-us-2023/videos/best-practices-for-making-a-wagtail-site-as-accessible-as-possible.json

@@ -1,22 +1,22 @@
 {
-    "description": "Over the past few years, the Wagtail CMS core team and accessibility subteam have made a [significant commitment to improving Wagtail's accessibility](https://wagtail.org/accessibility/) \u2013\u00a0of the CMS interface itself as well as the websites that it produces. This talk is focused on the latter, showing how you (a developer of a Wagtail-powered site) can set up your models, templates, and workflows in order to make it as easy as possible for your editors to create websites that are as accessible _as possible_. I say \"as possible\" because it's important to recognize that it's _not_ possible for a website to ever be considered 100% accessible, but by putting some care into what we do on the development side, we can prevent some of the most widespread accessibility issues that users may come across.\n\nTopics that will be covered include:\n- How to use Wagtail's [new built-in accessibility checker](https://wagtail.org/blog/introducing-wagtails-new-accessibility-checker/)\n- Custom validation to ensure that a page has a logical heading order\n- Ensuring alt text is used appropriately (Spoiler alert: every image doesn't need alt text!)\n- Usage of `aria-label` attributes to provide essential context to screen readers\n- Providing timely, contextual help to editors as they create their content",
-    "language": "eng",
-    "recorded": "2023-10-18",
-    "related_urls": [
-        {
-            "label": "Conference Website",
-            "url": "https://2023.djangocon.us"
-        }
-    ],
-    "speakers": [
-        "Scott Cranfill"
-    ],
-    "thumbnail_url": "https://i.ytimg.com/vi/qqQBbVIHkCA/maxresdefault.jpg",
-    "title": "Best Practices for Making a Wagtail Site as Accessible as Possible",
-    "videos": [
-        {
-            "type": "youtube",
-            "url": "https://youtu.be/qqQBbVIHkCA"
-        }
-    ]
+  "description": "Over the past few years, the Wagtail CMS core team and accessibility subteam have made a [significant commitment to improving Wagtail's accessibility](https://wagtail.org/accessibility/) \u2013\u00a0of the CMS interface itself as well as the websites that it produces. This talk is focused on the latter, showing how you (a developer of a Wagtail-powered site) can set up your models, templates, and workflows in order to make it as easy as possible for your editors to create websites that are as accessible as possible. I say \"as possible\" because it's important to recognize that it's not possible for a website to ever be considered 100% accessible, but by putting some care into what we do on the development side, we can prevent some of the most widespread accessibility issues that users may come across.\n\nTopics that will be covered include:\n- How to use Wagtail's [new built-in accessibility checker](https://wagtail.org/blog/introducing-wagtails-new-accessibility-checker/)\n- Custom validation to ensure that a page has a logical heading order\n- Ensuring alt text is used appropriately (Spoiler alert: every image doesn't need alt text!)\n- Usage of `aria-label` attributes to provide essential context to screen readers\n- Providing timely, contextual help to editors as they create their content",
+  "language": "eng",
+  "recorded": "2023-10-18",
+  "related_urls": [
+    {
+      "label": "Conference Website",
+      "url": "https://2023.djangocon.us"
+    }
+  ],
+  "speakers": [
+    "Scott Cranfill"
+  ],
+  "thumbnail_url": "https://i.ytimg.com/vi/qqQBbVIHkCA/maxresdefault.jpg",
+  "title": "Best Practices for Making a Wagtail Site as Accessible as Possible",
+  "videos": [
+    {
+      "type": "youtube",
+      "url": "https://youtu.be/qqQBbVIHkCA"
+    }
+  ]
 }

europython-2020/videos/mark-smith-everything-you-know-about-mongodb-is-wrong.json

@@ -1,6 +1,6 @@
 {
   "copyright_text": "This video is licensed under the CC BY-NC-SA 3.0 license: https://creativecommons.org/licenses/by-nc-sa/3.0/\nPlease see our speaker release agreement for details: https://ep2020.europython.eu/events/speaker-release-agreement/\n",
-  "description": "(Probably)\n\nMongoDB is webscale, right? It's a JSON database, it's eventually consistent, and you use map-reduce to query it. Oh, and it's insecure.\r\n\r\nLet me clear up some things: MongoDB is an ACID-compliant database with transactions, schemas & relationships. It includes a powerful aggregation query language; map-reduce has been deprecated for some time now. MongoDB doesn't speak or store JSON, and nowadays it comes with pretty good security defaults (we think).\r\n\r\nThere are many myths around about MongoDB - what it is, how it works, and what it does wrong. Like any database product, you need to know its capabilities and how to get the best out of it. On top of this, the product has changed _a lot_ over the years, but lots of information out there hasn't caught up.\r\n\r\nI'll cover 8 myths around MongoDB, explain how they're wrong, why the myth originated in the first place (some of them weren't originally myths).\r\n\r\n* What exactly _is_ MongoDB?\r\n* What is the current release of MongoDB?\r\n* MongoDB is _not_ a JSON database.\r\n* MongoDB _has_ transactions.\r\n* MongoDB allows relationships.\r\n* You should only consider sharding if you _must_.\r\n* MongoDB _is secure_.\r\n* MongoDB stores your data reliably.\r\n* MongoDB is a big product, with lots to learn.\r\n\r\nAlong the way, I'll explain some of MongoDB's best-kept secrets, and provide practical tips and tricks for using it. The audience will leave with a good idea of what MongoDB is, what it isn't, and how to best develop with it.",
+  "description": "(Probably)\n\nMongoDB is webscale, right? It's a JSON database, it's eventually consistent, and you use map-reduce to query it. Oh, and it's insecure.\r\n\r\nLet me clear up some things: MongoDB is an ACID-compliant database with transactions, schemas & relationships. It includes a powerful aggregation query language; map-reduce has been deprecated for some time now. MongoDB doesn't speak or store JSON, and nowadays it comes with pretty good security defaults (we think).\r\n\r\nThere are many myths around about MongoDB - what it is, how it works, and what it does wrong. Like any database product, you need to know its capabilities and how to get the best out of it. On top of this, the product has changed a lot over the years, but lots of information out there hasn't caught up.\r\n\r\nI'll cover 8 myths around MongoDB, explain how they're wrong, why the myth originated in the first place (some of them weren't originally myths).\r\n\r\n* What exactly is MongoDB?\r\n* What is the current release of MongoDB?\r\n* MongoDB is not a JSON database.\r\n* MongoDB has transactions.\r\n* MongoDB allows relationships.\r\n* You should only consider sharding if you must.\r\n* MongoDB is secure.\r\n* MongoDB stores your data reliably.\r\n* MongoDB is a big product, with lots to learn.\r\n\r\nAlong the way, I'll explain some of MongoDB's best-kept secrets, and provide practical tips and tricks for using it. The audience will leave with a good idea of what MongoDB is, what it isn't, and how to best develop with it.",
   "duration": 1501.0,
   "language": "eng",
   "recorded": "2020-07-23",

north-bay-python-2025/videos/the-tangled-web-we-weave-continuing-education-through-silly-projects.json

@@ -1,6 +1,6 @@
 {
   "copyright_text": "",
-  "description": "Joe Kaufeld\n\nhttps://pretalx.northbaypython.org/nbpy-2025/talk/VMJR8F\n\n### Where'd that yellow schoolbus come from?\n\nThere are many things we're told aren't worth building because experts have done them already. Cryptography? Let the experts handle it. Algorithms? Same. Web frameworks? Yep. As a professional web developer focusing on arcane uses of Django (and others) for arcane purposes, it occurred to me a little while ago that I didn\u2019t actually know how a web framework _worked_. How does routing route? How does middleware work? How do variables in URLs work without regex? (Spoiler: they don't.)\n\nSo... I wrote one.\n\n_The Tangled Web We Weave_ is a love letter to learning and to doing things they tell you aren't worth your time. Come and get some inspiration on learning the answers to questions you don't know either... even if some folks say it's silly.\n\n### What to expect\n\n - Tips on how to tackle giant problems\n - Three big takeaways learned while designing a WSGI web framework from the ground up\n - Support and encouragement\n\n### Who's this for?\n\nAnyone who's feeling like they need a push to learn something new, anyone who wants to know some weird facts about web frameworks, and anyone who wants to learn a little bit about the beautiful science of learning with Python.\n\nSun Apr 27 10:15:00 2025 at Reis River Ranch\n\nProduced by NDV: https://youtube.com/channel/UCQ7dFBzZGlBvtU2hCecsBBg?sub_confirmation=1",
+  "description": "Joe Kaufeld\n\nhttps://pretalx.northbaypython.org/nbpy-2025/talk/VMJR8F\n\n### Where'd that yellow schoolbus come from?\n\nThere are many things we're told aren't worth building because experts have done them already. Cryptography? Let the experts handle it. Algorithms? Same. Web frameworks? Yep. As a professional web developer focusing on arcane uses of Django (and others) for arcane purposes, it occurred to me a little while ago that I didn\u2019t actually know how a web framework worked. How does routing route? How does middleware work? How do variables in URLs work without regex? (Spoiler: they don't.)\n\nSo... I wrote one.\n\nThe Tangled Web We Weave is a love letter to learning and to doing things they tell you aren't worth your time. Come and get some inspiration on learning the answers to questions you don't know either... even if some folks say it's silly.\n\n### What to expect\n\n - Tips on how to tackle giant problems\n - Three big takeaways learned while designing a WSGI web framework from the ground up\n - Support and encouragement\n\n### Who's this for?\n\nAnyone who's feeling like they need a push to learn something new, anyone who wants to know some weird facts about web frameworks, and anyone who wants to learn a little bit about the beautiful science of learning with Python.\n\nSun Apr 27 10:15:00 2025 at Reis River Ranch\n\nProduced by NDV: https://youtube.com/channel/UCQ7dFBzZGlBvtU2hCecsBBg?sub%5Fconfirmation=1",
   "duration": 1465,
   "language": "eng",
   "recorded": "2025-04-27",

pycon-au-2020/videos/ensuring-black-voices-matter-why-your-voice-assistant-is-racist-and-what-we-can-do-about-it.json

@@ -1,6 +1,6 @@
 {
   "copyright_text": "CC-BY-NC-SA 4.0",
-  "description": "Kathy Reid\n\nhttps://2020.pycon.org.au/program/99XMUR\n\nBy 2025, there will be over 8 million voice assistants in the world. They are found on your mobile phone, in your home, in your car, and over time, will be embedded in many cyber-physical systems across the world. At the same time, there are over 7000 languages spoken in the world - \"living languages\".\r\n\r\nBut voice assistants support just a fraction of these languages. Moreover, accents and diversity _within_ a spoken language are not well handled by voice assistants. For example, African American voices are much less likely to be correctly recognised by the speech recognition algorithms used within voice assistants. And as we start to interact with systems using voice, we have a human desire to listen to voices we resonate with. Voices like us. For many people, there are no synthesised voices that reflect their heritage, language, and gender expression.\r\n\r\nThere are several techno-social reasons behind this state of affairs.\r\n\r\n* The intent of a commercial voice assistant is to make money. This drives technical development in certain ways, such as certain languages being seen as more lucrative than others, irrespective of the number of speakers of that language. For example, there is more voice assistant support for Icelandic, a language spoken by 314,000 people, than there is for Kiswahili, a language spoken by over 100,000,000 people in Eastern Africa. Why? Money. \r\n\r\n* The big tech companies behind voice assistants have typically poor gender and racial diversity in their talent pool. Diversity in developers leads to diversity in development.\r\n\r\n* The data used for training speech recognition and speech synthesis models often has racial and gender biases. These can stem from both selection bias, but also broader systemic issues of inequality, such as the use of voice assistant technology to gather data - and the affordability of both that technology and its pre-requisites, such as internet access.\r\n\r\n* Many languages are considered \"low resource languages\". This means they often don't have written transcriptions, which are needed to train machine learning models. Those creating transcriptions often face the \"transcription bottleneck\" - a workflow impediment that means the creation of resources consumes significant labour time.\r\n\r\nThere are many established and emerging open source tools - many in Python - and movements that _individually_ are addressing aspects of this broader techno-social system. **Together**, they can effect change so that _everyone, everywhere can be afforded the benefits of voice technology_.\n\nProduced by NDV: https://youtube.com/channel/UCQ7dFBzZGlBvtU2hCecsBBg?sub_confirmation=1\n\nPython, PyCon, PyConAU, PyConline\n\nSat Sep  5 14:05:00 2020 at Floperator",
+  "description": "Kathy Reid\n\nhttps://2020.pycon.org.au/program/99XMUR\n\nBy 2025, there will be over 8 million voice assistants in the world. They are found on your mobile phone, in your home, in your car, and over time, will be embedded in many cyber-physical systems across the world. At the same time, there are over 7000 languages spoken in the world - \"living languages\".\r\n\r\nBut voice assistants support just a fraction of these languages. Moreover, accents and diversity within a spoken language are not well handled by voice assistants. For example, African American voices are much less likely to be correctly recognised by the speech recognition algorithms used within voice assistants. And as we start to interact with systems using voice, we have a human desire to listen to voices we resonate with. Voices like us. For many people, there are no synthesised voices that reflect their heritage, language, and gender expression.\r\n\r\nThere are several techno-social reasons behind this state of affairs.\r\n\r\n* The intent of a commercial voice assistant is to make money. This drives technical development in certain ways, such as certain languages being seen as more lucrative than others, irrespective of the number of speakers of that language. For example, there is more voice assistant support for Icelandic, a language spoken by 314,000 people, than there is for Kiswahili, a language spoken by over 100,000,000 people in Eastern Africa. Why? Money. \r\n\r\n* The big tech companies behind voice assistants have typically poor gender and racial diversity in their talent pool. Diversity in developers leads to diversity in development.\r\n\r\n* The data used for training speech recognition and speech synthesis models often has racial and gender biases. These can stem from both selection bias, but also broader systemic issues of inequality, such as the use of voice assistant technology to gather data - and the affordability of both that technology and its pre-requisites, such as internet access.\r\n\r\n* Many languages are considered \"low resource languages\". This means they often don't have written transcriptions, which are needed to train machine learning models. Those creating transcriptions often face the \"transcription bottleneck\" - a workflow impediment that means the creation of resources consumes significant labour time.\r\n\r\nThere are many established and emerging open source tools - many in Python - and movements that individually are addressing aspects of this broader techno-social system. **Together**, they can effect change so that everyone, everywhere can be afforded the benefits of voice technology.\n\nProduced by NDV: https://youtube.com/channel/UCQ7dFBzZGlBvtU2hCecsBBg?sub%5Fconfirmation=1\n\nPython, PyCon, PyConAU, PyConline\n\nSat Sep  5 14:05:00 2020 at Floperator",
   "duration": 1611,
   "language": "eng",
   "recorded": "2020-09-05",
@@ -38,4 +38,4 @@
       "url": "https://www.youtube.com/watch?v=eYyfhWf_sRw"
     }
   ]
-}
+}

pycon-au-2020/videos/geospatial-data-and-analysis-is-exploding-head-gala-pyconline-au-2020.json

@@ -1,6 +1,6 @@
 {
   "copyright_text": "CC-BY-NC-SA 4.0",
-  "description": "Gala\n\nhttps://2020.pycon.org.au/program/QJTSEP\n\nHere is my top level summary:\n\r\n- its hard for everyone, you are not alone. \r\n- snacks:\r\n  - points, lines and polygons\r\n  - projections (_scream quietly into the void_)\r\n  - WKT\r\n  - file types\r\n  - \"simple\" calculations\r\n- pantry:\r\n  - libraries\r\n  - useful stuff on the internet\r\n  - quick wins\r\n  - other software\r\n  - debugging\r\n- dinner:\r\n  - interesting problems\r\n  - other fun things\n\nProduced by NDV: https://youtube.com/channel/UCQ7dFBzZGlBvtU2hCecsBBg?sub_confirmation=1\n\nPython, PyCon, PyConAU, PyConline\n\nFri Sep  4 09:50:00 2020 at Curlyboi",
+  "description": "Gala\n\nhttps://2020.pycon.org.au/program/QJTSEP\n\nHere is my top level summary:\n\r\n- its hard for everyone, you are not alone. \r\n- snacks:\r\n  - points, lines and polygons\r\n  - projections (scream quietly into the void)\r\n  - WKT\r\n  - file types\r\n  - \"simple\" calculations\r\n- pantry:\r\n  - libraries\r\n  - useful stuff on the internet\r\n  - quick wins\r\n  - other software\r\n  - debugging\r\n- dinner:\r\n  - interesting problems\r\n  - other fun things\n\nProduced by NDV: https://youtube.com/channel/UCQ7dFBzZGlBvtU2hCecsBBg?sub%5Fconfirmation=1\n\nPython, PyCon, PyConAU, PyConline\n\nFri Sep  4 09:50:00 2020 at Curlyboi",
   "duration": 1552,
   "language": "eng",
   "recorded": "2020-09-05",
@@ -38,4 +38,4 @@
       "url": "https://www.youtube.com/watch?v=WdmcUl8klnc"
     }
   ]
-}
+}