{
  "id": 1,
  "guid": "6b36f107-b08d-5bc9-8c3e-80b7638e2d91",
  "logo": "",
  "date": "2021-04-03T21:10:00+02:00",
  "start": "21:10",
  "duration": "00:45",
  "room": "Piscopia",
  "slug": "divoc-reboot-to-respawn-2021-1-emoji-domains-and-how-wonderfully-broken-they-are",
  "url": "https://pretalx.c3voc.de/divoc-reboot-to-respawn-2021/talk/3MXRDE/",
  "title": "Emoji domains and how wonderfully broken they are",
  "subtitle": "",
  "track": "Technology",
  "type": "Talk/Performance (30 minutes plus Q&A)",
  "language": "en",
  "abstract": "Did you know that you can get a domain that contains an emoji?  \r\nWell, technically speaking you can't because domains only allow a very limited character set.  \r\n \r\nHowever, there is a workaround to that called Punycode.  \r\nYou can encode non-supported characters to punycode and allow people to visit your site by entering those characters in their URL bar -the browser will take care of encoding them.\r\n\r\nSounds good, doesn't it?  \r\nWell, unicode is more complex than one would think; especially the parts around emoji are.  \r\nThat means encoding those characters isn't easy and a lot goes wrong.\r\n\r\nI want to showcase some ways in that emoji/ punycode domains are broken, how you can have fun with them and why you should actually just avoid them for anything you want to use productively.",
  "description": "Fragenpad: https://di.c3voc.de/pad/r2r:talk:3MXRDE",
  "recording_license": "",
  "do_not_record": false,
  "persons": [
    {
      "id": 15,
      "code": "DMUDXQ",
      "public_name": "DysphoricUnicorn",
      "biography": "I'm a full stack developer with a morbid curiosity about brokenness in the technology we use every day.\r\n\r\nWhen I'm not tinkering with that kind of stuff, I try to make the web more accessible by building accessible web sites and telling others how to do that.",
      "answers": []
    }
  ],
  "links": [],
  "attachments": [],
  "answers": [],
  "origin": null
}