--- title: "A Moving Mascot for Open-Source Conference Talks" description: "Resolved · affects genjutsu.app · Nov 4, 2026" base_url: "https://genjutsuai.openstatus.dev" canonical: "https://genjutsuai.openstatus.dev/events/report/3775" --- # A Moving Mascot for Open-Source Conference Talks [Status](/.md) › [Events](/events.md) › A Moving Mascot for Open-Source Conference Talks Nov 4, 2026 · 24 hours ago · affects: genjutsu.app · 1 minute ## Updates ### + Resolved — Nov 4, 5:03 AM affects: genjutsu.app (degraded performance) Open-source maintainers give a lot of talks: lightning talks at meetups, longer sessions at community conferences, recorded presentations for online events. Many projects have a beloved mascot, yet it usually appears only as a static logo on the title slide. A few seconds of that mascot moving, waving at the audience, taking a bow at the end, or acting out a key concept, can make a talk memorable. Motion transfer lets a maintainer animate the mascot using nothing more than their own recorded gestures. ## How it works Motion transfer takes the movement from a source video and applies it to a character defined by reference images. You film yourself performing a gesture; the mascot performs the same gesture in the output. It does not invent motion, so what you record is what you get. For talks, that is ideal. You can rehearse a gesture until it is clear and then hand it to the mascot. ## Moments in a talk that benefit from motion Choose a few deliberate moments rather than animating every slide: - **Opening.** The mascot waves as the title slide appears, setting a friendly tone. - **Concept illustration.** The mascot mimes "lifting" a heavy box to illustrate technical debt, or "juggling" to illustrate concurrency. - **Call to action.** The mascot points toward the repository address or contributor guide. - **Closing.** A bow or a cheerful thank-you gesture on the final slide. Three or four clips per talk are plenty. More becomes distracting. ## Licensing and community care Before animating a mascot, check its license and the project's trademark or branding guidelines. Many open-source mascots are released under permissive terms, but some have specific rules about modifications. If the mascot was designed by a community member, it is courteous to tell them how it will be used, and to credit them on the slide. ## Recording and references Source clips must be MP4 or MOV and between 4 and 30 seconds long. For slide clips, 4 to 8 seconds is the sweet spot. Record against a plain background, frame your full body or upper body depending on the gesture, and exaggerate slightly so the motion reads well at a distance. The mascot is defined by up to 20 reference images. Gather official artwork in several poses and angles. If the mascot is a non-human creature, choose gestures that suit its body; a character with short arms will look odd reaching high above its head. ## Resolution for projectors and recordings Output comes in 480p, 720p and 1080p at 3, 7 and 11 credits per second. Conference projectors and recorded streams generally benefit from 1080p, so render final versions there. A talk with four 6-second clips uses 24 seconds of output: 264 credits at 1080p. Draft at 480p first for 72 credits if you want to check gestures before committing. Credits come in one-time packs with no subscription, and they never expire. Maintainers who give a talk or two each year can buy a small pack and keep the balance for the next season. Failed renders are refunded automatically. ## Visibility and project announcements Videos made before an account's first purchase are public in the Community section. For most open-source projects that is not a problem, and may even be welcome. If you are preparing an unannounced release or a surprise reveal, purchase credits first to keep the clips private until the talk. ## Embedding clips in slides Most presentation tools accept MP4 files directly. A few tips: 1. Set clips to play automatically when the slide appears. 2. Mute them; you will be speaking. 3. Avoid looping unless the slide stays up for a long time. 4. Keep a fallback still image in case the venue's laptop struggles with video. ## Sharing the clips afterwards After the talk, the clips can live on in the project's community spaces: release announcements, contributor welcome messages and documentation landing pages. Store source clips alongside outputs in a shared folder so other maintainers can reuse the gestures with updated mascot art later. To try a first mascot animation before your next talk, visit [genjutsu.app](https://genjutsu.app). Open-source communities run on goodwill and personality. A mascot that greets the audience with a maintainer's own wave is a small, human touch in a talk full of technical detail. — Genjutsu AI --- _Powered by [openstatus.dev](https://openstatus.dev)_