Life Advice Exchange

A server for asking strangers for perspective: a required question format, topic channels and a clear scope boundary.

  • 3 categories
  • 14 channels
  • 5 roles
  • Small
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

BEFORE YOU ASK

  • how-to-ask

    The situation, what you already considered, and the actual question.

  • what-this-is-not

    Strangers with opinions, not professionals. Where to go instead is listed.

ASK

  • work-and-career

    Jobs, colleagues, decisions about work.

  • friendships

    The ones that are difficult.

  • family

    Complicated by definition.

  • money-decisions

    Everyday practicalities. Not investing, and never advice on it.

  • living-situations

    Housing, moving, sharing.

  • big-decisions

    The ones that do not fit anywhere else.

LISTENING

  • just-listening

    Being heard, not advised. Solutions belong elsewhere.

  • what-happened

    Come back and say what you did. The most useful channel here.

  • general

    Everything else.

  • report-a-problem

    Opens a ticket.

  • Talk It Through
  • Open Room

Roles

  • OwnerAdministrator
  • ModeratorModerator
  • Member
  • Muted

Overview

Asking strangers for a view on something is genuinely useful, and it goes wrong in predictable ways this layout addresses. #how-to-ask is read-only and states the format every question follows: the situation in a few lines, what you have already considered, and the specific question you want answered — because a wall of context with no question produces a thread of people solving a different problem. #what-this-is-not is the companion and matters just as much: this is a room of strangers with opinions, not professionals, and it lists what belongs with a doctor, a lawyer, or a crisis service instead. Ask splits by area so a reply comes from someone who has been there: #work-and-career, #friendships, #family, #money-decisions kept to everyday practicalities rather than investing, #living-situations and #big-decisions for the ones that do not fit. #just-listening is the channel for someone who wants to be heard rather than advised, and its topic says so, which prevents the commonest failure in advice servers — an unwanted solution offered to someone who only wanted acknowledgement. #what-happened is where an asker returns weeks later to say what they did, and it is the most valuable channel here, because it is the only way anyone learns whether the advice was any good. Moderation is active and boundaries are enforced kindly.

When to use it

Advice threads in general servers fail because the question is buried in context, the reply comes from whoever is awake rather than whoever has relevant experience, and someone who wanted to be heard gets a list of solutions instead. This layout requires a stated question, splits by area of life, gives being-listened-to its own channel, and asks people to come back and say what actually happened.

What makes it different

  • A required format: the situation, what you already considered, and the actual question.
  • A stated scope boundary listing what belongs with a professional instead.
  • A channel for being listened to rather than advised, which prevents the commonest failure.
  • People return to say what they did, which is the only way anyone learns if advice worked.

Recommended Vetox setup

  • Welcomer

    Point Welcomer at #how-to-ask so a first question already has the shape that gets useful answers.

  • Auto-Mod

    Run Auto-Mod, since a server where people describe personal situations attracts people looking for vulnerable targets.

  • Tickets

    Point Tickets at #report-a-problem so someone uncomfortable with a reply can raise it privately.

  • Starboard

    Point Starboard at #what-happened so the follow-ups become the archive that teaches the server how to advise.

Questions

Why insist on a stated question?

Because without one, every reply answers whatever the reader thought the problem was, and the asker gets six solutions to five different situations. One line naming what you actually want — whether to do it, how to say it, whether you are being unreasonable — focuses the whole thread. It also forces the asker to work out what they are asking, which is often most of the value.

How is the just-listening channel enforced?

By the topic and by moderators, gently and consistently. Someone posting there is asking for acknowledgement, and a well-meant solution is experienced as being told their feelings were a problem to solve. Moderators redirect advice into a reply in the relevant topic channel rather than deleting it, which keeps the helper's contribution while protecting the asker's request.

What should the scope boundary actually say?

That the people here are strangers with opinions and no training, that medical, legal and mental-health crises need someone qualified, and where to find them. Written plainly and without drama, so a moderator can point at it without seeming dismissive. Servers that skip this eventually receive a question nobody there should be answering, and by then the norm is already set.

Common mistakes

  • Accepting questions with no stated question, so every reply answers a different problem.
  • Offering solutions to someone who wanted to be heard, which is the fastest way to lose a member.
  • Failing to state a scope boundary, in a server that will receive medical and legal questions.

Consider instead

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages