Seminar: Livestreaming meets HCI

Livestreaming digital games on platforms such as, YouTube or is popular today and has become a topic for research as well. In this blockseminar we explore selected HCI aspects on these platforms that might inform novel experiences in such livestreams.

The (mandatory to attend!) kick-off meeting for this seminar is on February the 27th, 11am, in room Reuse (DFKI Main Building -2.17). In this room, all presentations will be held. On March the 6th we will meet at 9am in seminar room 014 (SR 014) in building E1 3. This room will also be available during the block-phase of the seminar for group work.

We have 24 seats in this seminar, which will (in theory) be given on a first-come-first-serve basis; every registration after this limit will be on a waiting list. On the kick-off (after presenting what you need to do in this seminar) we will report who is (in theory) in the seminar and who is on the waiting list (and on what position). But you only receive your spot, if you pass the “getting-starting challenge” (see below); if you fail you cannot participate in the seminar and students who were on the waiting list but pass this challenge can take your seat.

The seminar is structured into 4 phases (see “Your tasks”). In every phase, you work together as a group of 2-5 people. The language of the seminar is English.


Kickoff Slides

Your tasks

Phase 1: Ideation
In this phase, your group will derive an idea each to improve a streamer’s audience overview, to provide possibilities for the audience to influence the streamer’s decisions as well as to combine games with a purpose and livestreaming to games that entertain the audience. More details about these topics can be found here. Each of your ideas will be presented in the Ideation talk (15 minutes + 10 minutes discussion).

Phase 2: Related Work & Study planning
After selecting the most promising of the three ideas, your group will look for scientific work, tools and other channels that are relevant for your topic. Moreover, your group needs to plan how to evaluate your implemented concept later (what are the research questions, how you methodologically try to answer them, …). Related work and your study concept is presented in Talk A (20 minutes: ~10 minutes to present related work + ~10 minutes for the user study + 10 minutes discussion).

Phase 3: Implementation
Until March the 24th, you will define 3 milestones for your prototype and send us a PDF containing the dates of these milestones and what you want to have reached until then. The final milestone will be the May the 23th. Here, all groups will meet (presumably 9am) again and you will present your prototype in Talk B (15 minutes). You will meet with your supervisors at least twice (after each milestone and before the third).

Phase 4: Study
With your prototype and your study concept of Phase 2 you conduct the user study. You will meet again with the supervisors before study start, to check for final changes and after you have obtained the first (or all) results.

The seminar ends on June the 30th, 9am with Talk C (20 minutes + 10 minutes questions). Here, you will give a short recap over your prototype and the study methodology (not more than 5 minutes), but will focus on the results and lessons learned.


The ideation and related work phase count 20% each towards the grade. The implementation and study phase 30% each. Phase 1 and 2 will be covered in the block in March.

Important dates

Please find the schedule here.

Getting started challenge

Test phase results

    • D7FKvV--705
    • GJSuBQ--697
    • RGhL99--658
    • DgxGZ2--680
    • kTC5rH--727
    • HmvLxp--668
    • NBC5ak--675
    • y6nxV4--690
    • n6pXXU--694
    • C3fQ9f--663
    • PL8vnR--715
    • BFmtPe--676
    • wXPzth--714
    • 7kqUG3--669
    • 7R4ytf--683
    • fUa6J8--698
    • qBJLWs--677
    • NexPw4--674
    • 85JeBF--679
    • vxtwsc--672
    • D9FKxV--677
    • GKSuBn--691
    • ZGhL98--680
    • EgxG32--688
    • kTC553--699
    • fUa7J9--622
    • qBJLXx--718
    • NexXw5--691



    To be able to attend the seminar, you need to pass our "getting started challenge". On March the 2nd we will launch a script which will periodically write into our own twitch AND beam channel (links will be provided at the kickoff). Your task is to count how often the channel owner (and only the channel owner!) mentions your ID (which will be also provided in the kickoff meeting). The only messages you should analyze for your ID are messages that start with !LivestreamingMeetsHCI. Pay attention that there might be other messages from other users or messages from the channel owner which do not follow the format (see below).

    A random number (at least 1) of IDs are mentioned behind this string. If multiple IDs are provided, they are separated by a semicolon and no ID will appear twice per message. Messages you should consider follow the following format:

    !LivestreamingMeetsHCI IDs
    (sent by the Channel owner; where IDs are of the format ID1;ID2;ID3;...)

    Every of these messages might be written into the Twitch chat OR the Beam chat OR both chats. In the case that the same line is written into both chats, you should count your ID (if available in this message) twice; otherwise it counts only once (if available).  Your task is to create a tool using the Beam and Twitch API, that is able to read chat messages and analyze the messages for your IDs automatically. Our script will run between 10am-1pm and 3pm-4pm. Between 10am-1pm you can test your tool. Between 3pm-4pm you should carry out the task as described and send us an e-mail until the same day, 11:59pm ( containing your ID and the amount of times your ID was mentioned. As you need this knowledge/the tool for your project in the seminar, this is fundamentally important for the tool you will create later on – which is why you need to submit the correct amount, otherwise you cannot participate in this seminar.


    • We provided the details of this task already. In theory you could already start to implement the tool, but also the time between kickoff and March the 2nd should be sufficient to implement it.
    • There are several libraries and documentations how to access the Twitch/Beam chat, so this task should be easy to do in the languages you like.
    • Your scripts should start 15 minutes before the start and should run for another 15 minutes after the end, to ensure that you do not miss any related messages, due to timing issues.

    • For Twitch: Please pay attention that direct IRC access (if you do not want to use external Twitch libs) might add \001ACTION CHATMESSAGE\001. (or with \0001) to our CHATMESSAGE.

    • For Beam: In your tests, pay attention that there might be differences in accessing your own channel and another channel.

    • The chat will be cleared periodically. So copy & paste will not help you.





    Please send your questions, submissions or other inquiries to