Slack Etiquette

Last updated: December 2, 2025

Purpose of the LiveKit Community

The LiveKit community exists to help people learn, build, and collaborate around real-time audio, video, and data systems using LiveKit.
Our goals are to create a respectful, productive, and inclusive space for technical discussion, problem-solving, and sharing.

Community Values

Be respectful

  • Assume good intent.

  • Disagree constructively.

  • No harassment, personal attacks, insults, or demeaning language.

Be inclusive

  • Welcome developers of all experience levels.

  • Be aware of time-zones and cultural differences.

  • Avoid gatekeeping or dismissive responses.

Be considerate

  • Keep conversations focused and relevant.

  • Don’t dominate discussions; allow others space to contribute.

No discrimination

Harassment or discrimination based on race, gender, sexual orientation, age, nationality, disability, or any similar characteristic has zero tolerance.

No spam or self-promotion

Note: This does not apply to channels specifically designed for promotion, e.g. #jobs or #show-and-tell

Unsolicited advertising, recruitment outreach, or unrelated promotion is not permitted.

How to Ask for Help Effectively

When seeking debugging assistance or support:

  1. Provide a concise description upfront.  Your initial message should include:

    1. What you’re trying to do

    2. What went wrong

    3. What you expected to happen

  2. Share logs and technical detail in the thread 🧵

  3. Use triple backticks (```) for code or log blocks.

  4. Text logs are far more helpful than screenshots.

  5. Include relevant context.  Examples include:

    1. SDK version, LiveKit version, Agents version (if applicable)

    2. Platform (web, iOS, Android, server)

    3. Self-hosted vs LiveKit Cloud

    4. Any steps you already tried

Do not include sensitive or private data

Staff & Community Boundaries

Mentioning LiveKit staff and community members

  • Mentioning any user, such as a LiveKit staff member, in your initial message will not get you help any faster. Doing so will make others reluctant to answer, slowing the process.  

    • The exception to this rule is if you are already working with somebody within an existing thread.

  • Community moderators or staff members may escalate to subject-matter experts internally when needed.

Contacting LiveKit staff and community members directly

  • In general, we do not respond to unsolicited DMs.  Always start conversations publicly, in a channel.

  • DMs are good for deep debugging sessions, and the responder to move the conversation to DM or a call if confidential information needs to be shared.

  • Unless solicited, DO NOT contact LiveKit staff or other community members directly outside of Slack to receive support.  This includes contact on LinkedIn, WhatsApp, or Telegram. Extreme cases, such as messaging multiple staff directly through social media with the same question, will result in your removal from the community.

Response-time expectations

  • The Slack community is not a paid support channel; responses are best-effort.

  • Community members, not just staff, can and do provide support.  

  • For urgent or guaranteed-response issues, use your official support channel (email or support plan).

Email Support

  • Email support is available to members on our Ship plan and higher.  If you have previously discussed the issue over community Slack, please include that information in your initial email.

Slack Etiquette & Technical Posting Guidelines

Threading and Message Organization

  • Do not post multiple Slack messages on the same topic in the main slack thread back to back. Instead, use a single message or add more details in a Slack thread. This way a conversation does not get fragmented and is easier to follow.

  • Make sure "Also send to channel" is not checked when adding messages in a thread.

  • If you are having the "exact" same issue as someone else it is good to share your results in the same thread so we can all debug the same issue together.

  • That said, please do not share unrelated issues in someone else's Slack thread about a specific topic.

Sharing Code and Logs

  • When sharing code snippets, please post your code in your message's thread in order to keep the main channel readable.

    • Encasing the code in triple backticks (```like this```) will format it, making it easier to read.

  • We love logs, but it is most helpful to have a concise description of your concern in the main message then put the details like logs and detailed debug information in the Slack thread.

    • Logs are most helpful if you share a text file or the text directly. Screenshots of the log are less helpful.

    • More context from the log is better than less context.

Safety, Privacy & Security

Protect sensitive information

Do not post:

  • API keys

  • Secrets

  • Console tokens

  • Private URLs

  • Customer-specific data

  • Full proprietary codebases

Community moderators may delete messages for your protection, but any responsibility for leaked sensitive information resides with the original poster.

Respect confidentiality

Do not share private conversations or internal details from employers or clients.

No illegal content

Any illegal activity or content will be removed and will result in removal from the community.

Positive Participation

Help keep the community healthy:

  • If you solved a problem, share the solution.

  • Help others when you can — that’s what makes the community strong.

  • Celebrate launches, demos, and learning.

  • Keep discussions constructive and on-topic.

Moderation & Enforcement

To keep the environment safe and productive:

  • LiveKit staff and community moderators will remove content that violates these guidelines.

  • Repeated violations will result in removal from the Slack workspace.

  • If you see concerning behavior, quietly contact a LiveKit staff member.

  • We aim for fairness, transparency, and community well-being in all moderation decisions.