Skip to content
Maiks.yt

Website and stream

Participation should come with a clear destination.

Chat, profile recognition, website actions, commands, and future TTS should not all behave the same way. People should know when an interaction stays private, reaches the streamer, or may appear publicly on stream.

Participation paths

Several ways in, one understandable experience.

Guests should still be able to join ordinary provider chat. An account becomes useful when someone wants identity, recognition, visibility choices, or website-specific actions.

  1. 01
    Connected foundation

    Provider chat

    Twitch, YouTube, and Discord chat can reach the private streamer tools. A message is not automatically placed on the OBS overlay.

  2. 02
    Planned

    Website activity

    Approved account, project, schedule, profile, and community activity may later trigger a restrained stream notification.

  3. 03
    Planned

    Stream commands

    Short commands can return useful context, links, or stream information in the originating chat without becoming overlay noise.

  4. 04
    Later

    Limited website TTS

    A future free message may be available once per stream, with review, safety, cooldown, and playback controls. It is not active now.

Visibility and safety

Not every event belongs on screen.

Stream visibility is a separate decision from whether an event exists. The system should receive useful activity while still respecting privacy, moderation, and the pace of the live show.

  • 01Private can stay private

    Security, privacy, account, and provider-token events belong in private tools and never need an on-stream announcement.

  • 02Appearance stays optional

    Website signup, public name, and profile-image recognition should respect the account's stream-visibility preference.

  • 03Frequency has limits

    Cooldowns, once-per-stream rules, and duplicate suppression keep free interactions from becoming spam.

  • 04Some moments need review

    Text, images, audio, and unusual events may wait for approval before reaching viewers or playing through OBS.

Your choice

Joining the community should add control, not pressure.

Watching and ordinary chat should not require a Maiks.yt account. Signing in can later connect identities, remember preferences, enable eligible website actions, and let someone choose whether public profile activity may be recognized on stream.

Community rules still apply regardless of where an interaction starts. Moderation can keep a person or message out of stream presentation even when the originating provider continues to carry it.

Read the community rules →Manage account visibility →Browse stream context →