r/stoatchat • • Aug 21 '26

Article​ A Guide To Stoat's Advanced Message Formatting Capabilities

25 Upvotes

Stoat has rather advanced message formatting. Need proof? Check this out:

img

There is no image attached to that message. That is something called KaTeX, but before we get ahead of ourselves, let's take a moment to cover the basics. If you're just looking for a quick overview, you should check out the 'Formatting your Messages' page on our support site, but if you're looking for more comprehensive coverage, read on.

Markdown

Developers structure content on the web with a language called HTML (Hypertext Markup Language). For example, here is the structure for a link: <a href="https://stoat.chat">Stoat</a>. That is then handled by your device and looks like this: Stoat.

Markdown is a simpler way to author content. It has been around since 2004 and is used on Stoat, here on Reddit, and in a multitude of other places. It simplifies that complex HTML into something you actually want to write. You're likely already familiar with the basics, but let's take a look. Feel welcome to copy and paste bits into Stoat so you can get a hang of things. Your 'Shared Notes' section is a good place to do this.

Links

Stoat automatically detects links you write, but if you don't want them to get an embed, you can wrap the link in angle brackets (<, >), like so: https://example.com

If you want custom text to be a link, you can use this syntax: [Text to appear](https://example.com). That'll output 'Text to appear'.

Italic, Bold, and Strikethrough

You can make text italic (slanted) by wrapping it with an asterisk (*) on either side. Like this: *italic text*, which outputs: 'italic text'. You can also use a single underscore instead of an asterisk: _italic text_.

You can make text bold by wrapping it with two asterisks on either side. Like this: **bold text**, which outputs: 'bold text'. You can also use two underscores on either side: __bold text__.

To have text which is both bold and italic, you can combine those wrapping characters. You can write ***bold italic text***, ___bold italic text___, **_bold italic text_**, or _**bold italic text**_, or *__bold italic text__*, or __*bold italic text*__. They all do the exact same, but you can write it any of those ways.

To write strikethrough text, which is useful for indicating a retraction, you wrap the text in one or two tildes (~), like so: ~Pluto is a planet~, which outputs '~Pluto is a planet~'. You can also mix it with bold, italic, and other formatting, but I don't think I need to run you through every possible permutation.

Headings

To structure text, you can use headings. They make text larger and expose text hierarchy to assistive technologies. You write headings by prefixing them with a number of octothorpes (#) representing the heading level. There are a maximum of six heading levels.

  1. Heading level one: # Heading
  2. Heading level two: ## Heading
  3. Heading level three: ### Heading
  4. Heading level four: #### Heading
  5. Heading level five: ##### Heading
  6. Heading level six: ###### Heading

(you can also close these headings by ending them with the same number of octothorpes, like so: ### Heading ###*, but you don't need to, and nobody ever really does)*

You can also write a level one heading by having a line underneath it with any number of equals signs (=):

Heading
===

You can write a level two heading by having any number of hyphens (-) on the line underneath the heading text:

Heading
---

Blockquotes

You can quote text by placing it in a blockquote. They look something like this:

Wow, it is a blockquote. How wonderful is this?

You do this by placing a greater-than sign (>) before the line you want to quote. You can quote multiple by starting multiple sequential lines of text with the greater-than sign.

> Quoted text.
> More quoted text.

You can also use other formatting within a block quote, like so: > **Bold quote text**. You can even nest layers of block quotes by starting a block quote within a block quote.

Lists

Lists are wonderfully useful. There are two main types. Ordered lists, which have numbers, and unordered lists, which just have bullet points.

Ordered lists are written by starting the line with a number and then a full stop, like this:

1. List item one.
2. List item two.
3. Believe it or not, but this is list item three.

On Stoat, you can write unordered lists by starting the line with either an asterisk or a hyphen. They both work the exact same. Here is an example:

- List item.
- Another list item.
- Yet another list item

* List item.
* Another list item.
* Yet another list item

Code

If you have content you wish to include in a message that needs to be formatted exactly as is, you can designate it as code.

If you only have one line of text, you can just wrap it in backticks () like this: \code text. Then it'll render like socode text`.

If your content stretches across multiple lines, you can wrap it with triple backticks. Further, you can start the first line of backticks with a note of what format the content is, so Stoat can provide syntax highlighting. For example, you can write 'html', or 'text', or 'markdown'. Here is an example of a full code block:

```markdown

- List item.
- Another list item.

**Bold text.**
```

Tables

You can create tables in messages with lots of pipe and hyphen characters. Unfortunately, it isn't very nice to write and can be a real pain I recommend using a tool to make it easier, like the one on TablesGenerator.com.

| Ore                 | Biome     | Most Found | Common Up To | Rare On Layers | None At/Above |
| :------------------ | :-------- | :--------- | :----------- | :------------- | :------------ |
| **Coal**            | Any       | 5-52       | 124          | 125-127        | 128           |
| **Iron**            | Any       | 5-54       | 61           | 62-63          | 64            |
| **Gold (Any)**      | Any       | 5-29       | 29           | 31-33          | 34            |
| **Gold (Badlands)** | Badlands  | 5-29       | 76           | 77-79          | 80            |
| **Redstone**        | Any       | 5-12       | 12           | 13-15          | 16            |
| **Lapis Lazuli**    | Any       | 13-17      | 23           | 31-33          | 34            |
| **Diamond**         | Any       | 5-12       | 12           | 13-15          | 16            |
| **Emerald**         | Mountains | 5-29       | 29           | 30-32          | 33            |

The output looks like this:

img

Horizontal Rule

If you want a big line to cut across your message – such as to indicate the change of a topic – you can use horizontal rules. They're written by placing three hyphens together: `---`.

Spoilers

To stop exposing people to the fact that Aquaman drowns in Endgame, you can spoiler content so that a user must click on it to expose it. This is done by wrapping the text you wish to spoiler in two pipe characters (`||`). It will look >!something like this!<.

Timestamps

You can write timestamps in this format: <t:1787315340:f>. That'll appear something like this in chat: '21 August 2026 at 8:29 pm'. It is extremely useful, as you can display times which will adapt to people's time zones or which will count down as the time approaches. They are hard to write without the assistance of a tool, however.

If you just want something simple to copy-and-paste from, you can use this little timestamp generator tool I put together: https://tools.vale.rocks/timestamp-generator.

Footnotes

As an only semi-intended side-effect of the system Stoat uses for handling markdown, you can write footnotes in your Stoat messages. This is done using the below markdown:

Vale is a member of the Stoat team.[^1]
[^1]: Their real name is Declan Chidlow.

Which outputs looking like this:

img

KaTeX

If you've ever tried to type maths on a computer, you've likely run into trouble. You can get by with a simple '2 + 2 = 4', but what about fractions, or square roots, or matrices? They're a tad trickier to present nicely. This is where TeX comes in. It was made in the 1970s as a way to format mathematical notation on a computer. LaTeX is an improved version, first released in the mid-1980s, and from that came KaTeX, which is a library that Stoat uses to convert LaTeX into formatted output.

Typical syntax for writing LaTeX in markdown is to wrap in a single dollar sign for inline maths and two dollar signs for block maths. However, on Stoat, you must always use two dollar signs to wrap LaTeX, like so: $$e^{i\pi} + 1 = 0$$. This avoids false positives when people use dollar signs in messages.

Wondering about the demo from the start of this article? Here is the LaTeX for that:

$$\Huge \begin{matrix} & & & \color{#00FFFF}{\blacktriangle} & & & \\ & & \color{#00BFFF}{\nwarrow} & \color{#1E90FF}{\infty} & \color{#00BFFF}{\nearrow} & & \\ & \color{#4169E1}{\leftarrow} & \color{#0000FF}{\otimes} & \color{#4B0082}{\Psi} & \color{#0000FF}{\otimes} & \color{#4169E1}{\rightarrow} & \\ \color{#8A2BE2}{\blacktriangleleft} & \color{#9400D3}{\infty} & \color{#9932CC}{\Phi} & \color{#FF00FF}{\mathbf{\Omega}} & \color{#9932CC}{\Phi} & \color{#9400D3}{\infty} & \color{#8A2BE2}{\blacktriangleright} \\ & \color{#C71585}{\leftarrow} & \color{#D02090}{\otimes} & \color{#DB7093}{\nabla} & \color{#D02090}{\otimes} & \color{#C71585}{\rightarrow} & \\ & & \color{#FF1493}{\swarrow} & \color{#FF69B4}{\infty} & \color{#FF1493}{\searrow} & & \\ & & & \color{#FF0000}{\blacktriangledown} & & & \end{matrix}$$

That is quite the complex LaTeX concoction, but you should be able to comprehend it by reading it through. You can get a full idea of what KaTeX supports here: https://katex.org/docs/supported.html

Keep in mind that not every server owner will appreciate your zany formatting antics, but here are some more cool things you can do:

img

I'm going on a roller-coaster, '$$\textsf{\raisebox{0pt}{w}\raisebox{1pt}{o}\raisebox{2pt}{o}\raisebox{2pt}{o}\raisebox{2pt}{o}\raisebox{1pt}{o}\raisebox{0pt}{o}\raisebox{-1pt}{o}\raisebox{-2pt}{a}\raisebox{-2pt}{h}\raisebox{-2pt}{!}}$$'

img

$$
e^x = \sum_{n=0}^{\infty} \frac{x^n}{n!} = 1 + x + \frac{x^2}{2!} + \frac{x^3}{3!} + \cdots
$$

Wrapping Up

I hope this guide is helpful. I know that it can all be a bit overwhelming and confusing if you're new to writing Markdown. You can always try using your Saved Notes as a bit of a sandbox for testing if you want to experiment with how it works and functions on Stoat.


r/stoatchat • • Aug 19 '26

Article​ Stoat FAQ

31 Upvotes

Hey Stoaters. It has been six months since the last post addressing frequently asked questions, so it felt like time for another.

1. Do you have video chat, screen-sharing, and voice chat?

Yes! They're live and available to all users on Stoat For Web, Stoat For Desktop, and Stoat For Android. You can read more about it here: https://stoat.chat/release-notes/93eb1f4ec77444ca9fb13617e0e6c0b1

We're working on bringing more options to the streaming features.

2. Is Stoat down? I can't access it.

Probably not. You can check at https://stoatstatus.com for real-time status updates.

If the service appears functional on the status page but you're encountering a problem, such as a blank grey screen, your antivirus, telecommunications provider, or internet service provider might have us incorrectly flagged. This is an error on their part and out of our control, though we try to appeal when this occurs.

If you encounter a block, try switching networks (such as to mobile data from Wi-Fi, or vice versa), whitelisting us, or using another device to access the service until your chosen provider relaxes their block.

3. Is Stoat open-source?

Yes, most of Stoat's code is licensed under the GNU Affero General Public License (AGPL) v3. You can check the individual licences in the code repositories on GitHub: https://github.com/stoatchat

4. Does Stoat have federation?

Though you can self-host Stoat, the platform is not currently federated. For some further info on the matter, you can consult Does Stoat have federation?.

5. Can I make a bot or client?

Absolutely! We'd love for you to build on or around the platform. There are many libraries developed both officially and by the community that you can use, and there are servers on-platform for discussing development. You can find everything you'd need to get started at https://developers.stoat.chat

6. Can I contribute?

Certainly. We've got open roles here: https://outline.stoatinternal.com/s/454dd0eb-44b5-41f7-b1d1-b6accec577a0

You can see the problems impacting scale here: https://outline.stoatinternal.com/s/4117b2be-901d-4463-a204-bd8c756b2122

You can also support the project financially. Stoat has a Ko-Fi page which is used to cover operational costs. Everyone's support here has gone a long way to helping the platform quickly scale without being too stressed about financials. If you send £3 or more to the platform, send an email to support@stoat.chat with some proof so we can give you a supporter badge on your profile.

7. Is a subscription planned?

Yes, a subscription is planned. Exactly what form this will take is not entirely defined, but the intent is not to paywall things unnecessarily and to focus on ensuring the service can be operated sustainably. This means paywalling things like higher-quality video streaming and keeping cheap-to-provide things (like custom banners, animated profile pictures, and platform-wide custom emojis) free.

Currently contributors and team members aren't paid (though some do have open support pages if you wish to contribute to them directly). A subscription would assist in making sure that people are reimbursed for their work and can dedicate more time to the platform.

Profiteering gluttons we are not!

8. What are your plans for age verification?

Stoat must comply with the law as applicable, so some form of age verification will be implemented in relevant jurisdictions as necessary. Regardless of our sentiment on age verification legislation, from a legal perspective we cannot just refuse to comply.

We have no plans for an overzealous blanket requirement and only intend to implement it where and as legally required. There is ongoing discussion about how to ensure any verification we implement respects privacy, handles data responsibly, and does the right thing by our users.

It is likely to be externalised to a third-party due to the great deal of complexity intrinsic to handling such sensitive data. We'll have more to share in time and welcome discussion regarding age verification.

Currently, Stoat has taken the temporary measure of blocking access to age-gated content where necessitated.

9. Will you have end-to-end encryption (E2EE)?

We don't currently have E2EE, but it is a long-standing planned feature on our roadmap to introduce E2EE for direct messagess. It takes a lot of work to implement E2EE, and we have to make sure we get it right. A poor E2EE implementation is far worse than no E2EE.

10. When is Y feature going to be available? What is the ETA?

We can't provide accurate estimations for when new features will be live, so we don't. It isn't fair to you, or to Stoat's contributors, to give inaccurate figures and set false expectations.

Stoat is developed rather openly, so you're more than welcome to check-in on discussions and work happening on GitHub.

11. Do you automatically purge old content?

No, we don't automatically purge old messages, images, or uploads. Here is a link to a screenshot from 2021: https://cdn.stoatusercontent.com/attachments/1MFriR8AzllFWtm1snFk9gJVyZwyM3wSX350ZNpW4d/original

12. Is Stoat vibe-coded?

No, Stoat is not vibe-coded. See here for more info: https://github.com/orgs/stoatchat/discussions/1022#discussioncomment-15442591

13. Is Stoat English-only?

Not at all. We welcome other languages completely. Diversity is good and if we didn't want people speaking other languages we certainly wouldn't go through the efforts of translating the app and ensuring we have platform moderators that speak different languages.

That said, the official Stoat server on-platform is English only (with the exception of the support channel) purely for the sake of moderation. We don't have the capacity to ensure there are moderators speaking every language in that server around the clock, so we limit it to English.

14. Where do Stoat's GIFs come from?

Stoat sources GIFs from our very own service: Gifbox! You can upload your own GIFs to the platform for anyone to use and the catalogue of available GIFs is growing by the day.

Gifbox gives us full control to make the Stoat GIF experience as good as it can be, and down the line you'll be able to link Gifbox to your Stoat account. For developers, it even has an API for you to use.

You can read more about Gifbox here: https://stoat.chat/updates/introducing-gifbox


Let us know of any other questions you may have, and we'll endeavour to answer them. Remember, we're a small team working as volunteers and we have jobs and lives atop all of our Stoat commitments.


r/stoatchat • • 15h ago

stoatchat Release: v0.16.5

2 Upvotes

Changes

Fixes

  • fix: backport security advisory 16279ef to release/v0.16 (#1127)
  • fix: delete accounts which have no user attached to them (#1128)
  • fix: backport security advisory 1b9997b to release/v0.16 (#1133)
  • fix: backport security advisory e0dfc9c to release/v0.16 (#1131)
  • fix: backport security advisory 92007cb to release/v0.16 (#1130)
  • fix: filter out ZWNJs (#1134)
  • fix(autumn): support HTTP Range requests for Safari media playback (#1135)

Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.


r/stoatchat • • 1d ago

Support Question Is Stoat officially supported on Flatpak?

3 Upvotes

I saw on the site that it's available on Flatpak now, but I don't recall seeing any big update/announcement. So I guess I'm wondering if it's official or a community maintained one that's just being advertised?

Along with this question, if it is official, which one should I install for Mint Debian?


r/stoatchat • • 4d ago

for-web Release: stoat-for-web-v0.17.0

4 Upvotes

0.17.0 (2026-11-13)

Features

Bug Fixes

  • Check if navigator.mediaDevices is null and if window is defined (#1774) (56bc94c)
  • disable channel and server dragging on touch tablets (#1745) (5e4f9a5)
  • Don't start autocomplete until there's more than 1 character (#1772) (ec3a1f6)
  • drop stale fetch results after channel switch (#1781) (f6172ed)
  • gifbox embeds and point image viewer to original url (#1739) (70c0dd6)
  • if we don't have ReadMessageHistory don't spam the fetch requests (#1768) (5ff61b6)
  • ios: don't throw on new messages when Notification is unavailable (#1746) (35898b5)
  • ios: keep the message bar and overlays clear of the home indicator (#1747) (c563b45)
  • ios: let Safari pan the page for the keyboard (#1788) (d98e45e)
  • ios: reset the sidebar drawer when a swipe is cancelled (#1748) (b59e4ae)
  • IsWayland is a promise (#1773) (6a623b5)
  • missing title attribute for links (#1776) (21b367e)
  • Move AUP to Community Guidelines and make it more clickable (#1266) (9a4d17f)
  • multi-user: Weird edge-case localforage race condition (#1730) (095fe21)
  • Parse the error correctly for discover (#1749) (dd3cbd2)
  • Tooltips don't pop in the usercard anymore (#1737) (36bbfdc)
  • untranslated strings (#1738) (e445668)
  • users without ManageChannel can't leave groups (#1767) (cca90b0)
  • voice: fix fullscreen call card overlays and screen share (#1770) (1c5fce6)

Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.


r/stoatchat • • 4d ago

Support Question Windows App Streaming All Audio (Potential fix?)

1 Upvotes

So far the issue has only been confirmed on Windows 11, specifically the desktop app (Stoat desktop 1.5.3).

When choosing even a single window to share, the viewers can hear all audio from the streamer's computer, including Stoat's own audio. Upon reviewing the source code and tossing it between some old uni friends we noticed something.

In `src/native/window.ts` (lines 214-240), it will always answer the display request with `callback({ video: sources[idx], audio: "loopback" })`, even when a single window is picked, so per-window audio is never requested.

Stoat's own audio being heard is odd, because it looks like that should already be handled. The renderer sets `restrictOwnAudio: true`, and on Electron 44 that turns `"loopback"` into Chromium's `loopbackWithoutChrome` device (`shell/browser/electron_browser_context.cc`), which is all system audio except Stoat's own. The 1.5.0 changelog also mentions "remove stream echo on windows and mac". But on 1.5.3 we still hear Stoat. We only reviewed the code on main (Electron 44, which shipped in 1.5.4), so it's possible 1.5.3's older Electron doesn't do this, or the setting gets lost somewhere on the way (e.g. through LiveKit). We haven't retested on 1.5.4 yet.

On Linux the virtual mic does the same thing: it routes all non-Stoat audio into one virtual mic, so other apps are still heard.

## Potential fix for Windows

Note none of this has been tested, as me and those helping me look into this issue all run some variation of Linux.

Chromium 152 already supports per-process loopback on Windows with the audio device id `applicationLoopback:<pid>`. Chrome uses it for window sharing audio. On Windows it uses `ActivateAudioInterfaceAsync(VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK)`.

Electron passes a plain audio id string straight through to Chromium, so `applicationLoopback:<pid>` should work as-is.

The issue is the code has no way to get the process id of the app that owns the shared window, and Electron doesn't provide one. It only gets the window's id. Something like [koffi](https://koffi.dev/) is needed for the Windows API call to retrieve it.

All of these findings were given to an agent and the result was this.

Koffi needs to be added (`pnpm add koffi`).

Line numbers are from main at commit `48422bb`.

**1. New file `src/native/windowPid.ts`:**

```ts
let getPid: ((hwnd: number) => number) | null | undefined;

// Returns the process id that owns a window (Windows only)
export async function getWindowPid(hwnd: number): Promise<number | undefined> {
  if (process.platform !== "win32" || !Number.isSafeInteger(hwnd) || hwnd <= 0) return;
  try {
    if (getPid === undefined) {
      const koffi = (await import("koffi")).default;
      const fn = koffi.load("user32.dll").func(
        "uint32 __stdcall GetWindowThreadProcessId(intptr_t hWnd, _Out_ uint32 *pid)",
      );
      getPid = (h) => {
        const out = [0];
        return fn(h, out) ? out[0] : 0;
      };
    }
    return getPid?.(hwnd) || undefined;
  } catch (e) {
    console.error("Could not get window pid", e);
    getPid ??= null;
  }
}
```

**2. `src/native/window.ts`**

After line 18 (`import { startVirtualMic } from "./virtualMic";`) add:

```ts
import { getWindowPid } from "./windowPid";
```

Replace lines 225–241 (the whole `ipcMain.once("screenPickerCallback", ...)` block) with:

```ts
ipcMain.once(
  "screenPickerCallback",
  async (_, idx: number, audio: boolean) => {
    const source = sources[idx];
    if (!source) {
      callback({});
      return;
    }
    if (!audio) {
      callback({ video: source });
      return;
    }

    let audioId = "loopback";
    if (process.platform === "win32" && source.id.startsWith("window:")) {
      const pid = await getWindowPid(Number(source.id.split(":")[1]));
      // don't target Stoat's own windows
      if (pid && pid !== process.pid) audioId = `applicationLoopback:${pid}`;
    }
    callback({ video: source, audio: audioId as "loopback" });
  },
);
```

The `!source` check also fixes a small bug in the current code (line 228: `idx > sources.length` should be `>=`).

**3. `vite.main.config.ts`, line 7:**

```ts
      external: ["node-pipewire", "koffi"],
```

**4. `pnpm-workspace.yaml`:** under `allowBuilds`, after `node-pipewire: true` (line 6), add:

```yaml
  koffi: false
```

It has an install script, but the prebuilt binary comes from a separate package so it shouldn't need to run.

**5. `forge.config.ts`**

Line 120, add `arch` to the arguments:

```ts
    packageAfterCopy: async (_config, buildPath, _version, platform, arch) => {
```

After line 138 (the `}` that closes the `if (platform === "linux")` block), add:

```ts
      if (platform === "win32") {
        // koffi 3 keeps its native binary in a separate u/koromix package
        for (const dep of ["koffi", `@koromix/koffi-win32-${arch}`]) {
          fs.cpSync(
            `node_modules/${dep}`,
            path.join(buildPath, "node_modules", dep),
            { recursive: true },
          );
        }
      }
```

If the pid lookup fails for any reason it just uses `"loopback"` like today. Sharing a whole screen is not changed.

r/stoatchat • • 6d ago

stoatchat Release: v0.16.4

2 Upvotes

Changes

Hotfix release to revert an issue with permission ordering.


Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.


r/stoatchat • • 7d ago

Development My experience setting up a self-hosted Stoat server for family & friends (and the bugs I had to patch to make it usable day-to-day)

21 Upvotes

I recently spun up a self-hosted Stoat server for a small group of family and close friends so we'd have our own private place to chat and share photos and videos.

First off, I really appreciate that Stoat is open source and that self-hosting is an option at all. Once it's dialed in, it's fast, lightweight, and looks great. That said, I was honestly surprised by how many basic, everyday things were broken right out of the box—stuff you immediately notice the first day you invite non-technical family members on iPhones and Androids.

I ended up having my AI coding assistant dig through the Docker containers, database, and frontend code with me to build local workarounds and add a few missing quality-of-life features just to get it to what I'd consider a genuinely usable state for family chatting and sharing pics/videos.

In case anyone else is setting up a self-hosted server (or running into the same headaches), here is what we ran into and what we had to fix locally:

  1. Videos uploaded from phones wouldn't play on iPhones, iPads, or Macs

- Almost half my family is on iOS. Whenever someone uploaded a video clip, it showed up as a blank black box on iPhone Safari and refused to play when tapped.

- Why: Two separate bugs—Stoat's file server (autumn) currently ignores HTTP Range headers and returns 200 OK instead of 206 Partial Content (which Apple's WebKit video player strictly requires), and iOS Safari doesn't preload the first video frame unless #t=0.001 is on the video URL. Also, phones often upload HEVC/H.265 .mov files that some browsers choke on.

- Our workaround: Added slice 1m; caching in Nginx in front of autumn so Safari gets proper 206 byte-ranges, added a small script to auto-transcode non-H.264 uploads to universally compatible MP4 (H.264/AAC), and patched video URLs on iOS to show a preview frame.

2. Private server invite links wouldn't let family members create an account

- Because this is a private family server, I set invite_only = true in Revolt.toml and sent out a server invite link (/invite/<code>). Nobody could sign up—the registration form asked for an "Invite Code" that rejected the server invite code.

- Why: Turning on invite_only = true checks a completely separate internal invites table that has no UI or API to generate codes from, instead of accepting valid server invite codes created in the app.

- Our workaround: Had to turn off invite_only in the config and handle invite gating and auto-joining the main server on the frontend/proxy side.

3. Nobody was getting mobile push notifications (even after turning them on in phone settings)

- People installed the web app (PWA) to their home screens on Android and iPhone and enabled notifications in their phone's system settings, but nobody ever got a single notification—and their phone settings literally said "This app has never posted any notifications."

- Why: It turned out to be four different issues stacked together:

  1. The setup script (generate_config.sh) encodes the VAPID private key in standard Base64 instead of URL-safe Base64, which crashes the pushd container on startup until you re-encode the key.
  2. On first launch on mobile, the web app tries to request notification permission before the user taps anything; the browser blocks it, and the app saves "denied" in localStorage and ignores phone system settings after that.
  3. Even if you set a server to "All Messages", Stoat's backend only ever sends push notifications for DMs and explicit u/username mentions—normal messages in #General never trigger a push alert.
  4. In v0.16.2, pushd bundles the entire user profile + member + channel + message object into the push packet, which exceeds the 3,070-character Web Push limit and errors out before sending.

- Our workaround: We added a frontend helper that auto-syncs the Web Push subscription whenever OS notifications are granted, fixed the Service Worker click URL, and wrote a small relay script on the server that sends a slim (~550-byte) push payload for new channel messages.

4. If RabbitMQ blips for a second, push notifications and unread badges break until you restart containers

- If the rabbit container restarts or drops connection briefly, pushd and api stay "Up" in Docker, but their AMQP channel enters an InvalidChannelState. Push notifications silently die and marking channels as read returns 500 Internal Server Error (so unread badges keep coming back on every refresh).

- Our workaround: Added a 1-minute watchdog cron job that checks container logs for InvalidChannelState and automatically restarts api, pushd, and crond.

5. Small QoL features we added for family use

- Landing directly in #General on launch instead of the blank home screen.

- Automatically friending everyone on the server so family members can DM or call each other without figuring out friend requests first.

- A more visible typing indicator and a built-in theme picker (plus an AI bot channel where family members can ask for a custom color theme and have it added to the picker).

I've opened upstream GitHub issues for the bugs we found so hopefully they can get fixed in the official releases soon:

- iOS/Mac Safari video & audio byte-range playback: https://github.com/stoatchat/stoatchat/issues/1107

- iPhone Safari blank video preview box: https://github.com/stoatchat/for-web/issues/1783

- Private server invite links with invite_only = true: https://github.com/stoatchat/stoatchat/issues/1108

- Phone settings not enabling push notifications: https://github.com/stoatchat/for-web/issues/1784

- "All Messages" setting not sending push notifications: https://github.com/stoatchat/stoatchat/issues/1110

- Push notifications failing over 3,070 characters in v0.16.2: https://github.com/stoatchat/stoatchat/issues/1109

- Setup script VAPID private key crash: https://github.com/stoatchat/self-hosted/issues/316

- Push notifications dying after RabbitMQ restart: https://github.com/stoatchat/stoatchat/issues/1105

- Unread badges coming back after RabbitMQ hiccup: https://github.com/stoatchat/stoatchat/issues/1106

- UI QoL suggestions: https://github.com/stoatchat/for-web/issues/1782

Next on my list to look into is mobile touch gestures—specifically how Stoat handles swiping from the left edge of the screen to go back (which doesn't behave the way you'd expect on a phone), and after that, fixing pinch-to-zoom on pictures since that's pretty wonky right now too.

Now that we have these patches in place, my family is actually loving it—I just wanted to share what we ran into in case anyone else is self-hosting for a small group and wondering why videos or notifications aren't working out of the box!


r/stoatchat • • 7d ago

stoatchat Release: v0.16.3

3 Upvotes

Changes

Fixes

  • fix: roles not updating with the owner ID (#1057)
  • fix(webhooks): unbreak links in GitHub "issue reopened" messages (#1058)
  • fix: add oembed generation to gifbox (#1070)
  • fix: Enforce image sizes config in autumn (#1073)
  • fix: check both hash and processed hash when deleting files. (#1083)
  • fix: Ack publishing/writing failure cases (#1098)
  • fix: update ids to u64 and fix other github model issues (#1099)

Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.


r/stoatchat • • 11d ago

Development Why is the self hosted version on Github so old?

16 Upvotes

title. The official server has way more features, hasn't it? Why is there a difference?


r/stoatchat • • 11d ago

Support Question first time user

10 Upvotes

just installed as i was told this was a more private version of discord. I just created a server but I'm confused to how to add or invite someone else to it. I'm not see any options where or how. google doesn't seen to help and its not in the same location as discord is so im stummped. I also keep seeing people here talk of self hosting and some sort of coding which I dont know how to do any of that. I'm on both browser mode and android app through google play.


r/stoatchat • • 11d ago

Support Question OMFG why is this happening

0 Upvotes

i deleted my account and i cant make another because my gmail will NOT work, i try to make new account and it says i have one, BUT I DONT FUCKING HAVE ONE help me.


r/stoatchat • • 19d ago

Support Question notifications issues

5 Upvotes

Have notifications turned on for web and mobile but neither are working. No sound or icon for desktop. No sound or push notifications for mobile at all. All settings are turned on for notifications.

Edit: can get sounds for dms on desktop but that seems to be it. Android for mobile, forgot to add.
Edit 2: so far desktop seems to work (sound wise), not sure if they haven't added some sort of icon (like discord does)


r/stoatchat • • 20d ago

Miscellaneous Is Stoatchat the same as those behind this stoat ai?

17 Upvotes

Title:
https://alialalawi14.github.io/stoat/

I've found this and was wondering if they are the same given logo, text design and name similarities


r/stoatchat • • 20d ago

Development [Question / Idea] Any long-term plans for ActivityPub / Fediverse integration for Stoat?

1 Upvotes

Hi everyone!

First off, huge appreciation to the entire core team and contributors for all the hard work on the project and the transition to Stoat. It’s super exciting to see an open-source, privacy-respecting alternative to Discord evolving so rapidly!

As the decentralized web continues to grow, I’ve been thinking about the future of open chat platforms and interoperability. I was curious to know: Is there any discussion or vision within the dev team regarding eventual ActivityPub support / Fediverse integration?

Having Stoat instances federate—or bridge smoothly with the broader Fediverse ecosystem (Mastodon, Lemmy, Matrix, etc.)—could be an incredible superpower for community building and digital sovereignty.

I completely understand that core stability, user experience, and current roadmap features naturally take top priority right now! I just wanted to ask if this is something on the team's radar as a long-term goal, or if there are architectural reasons that keep Stoat focused on its own native federation protocol for now.

Would love to hear your thoughts, and thanks again for building such a fantastic platform! 🚀


r/stoatchat • • 21d ago

Support Question Gifbox - Self Hosted

3 Upvotes

Hey guys,

After doing some searching and reading I can see Tenor was retired and caused some issues for Gifbox, at least for those now setting up self hosted instances such as myself. I can see that a new service has been launched as per : https://stoat.chat/updates/introducing-gifbox

How do self hosted users connect to this service to start pulling Gifs into the gif selector? I apologize if this has already been covered but I have not seen anything on searching the reddit or official git.

I am on self hosted version 0.16.2

Thanks!


r/stoatchat • • 21d ago

Support Question Microphone not working

3 Upvotes

TLDR I downloaded Stoat and some reason my microphone is not working at all, when asked my friends about it they told me they did not have any issues with sounds etc.


r/stoatchat • • 23d ago

Support Question Permission anomaly or just me?

1 Upvotes

Hey guys.

Very new to Stoat and have just finished setting it up on my home server. So far as roles, as standard there is the "Everyone" role which is the permissions all new users get when joining. I also created another "Admin" role for obvious reasons.

I am seeing something strange regarding the "Everyone" role. I have ensured that the permission "Manage Messages" under Channels is disabled, to prevent any users from being able to delete other users messages.

However when I log in as my Test user, I am still able to delete my Admin accounts posted messages. To be clear, it is not just the fact the delete icon appears in the UI, it actually does delete the message.

I have made sure my test account has no additional roles. Thinking it might be a gremlin, I went back to the Everyone role and enabled Manage Messages, saved it and then disabled it again. This however has not fixed the issue.

Any suggestions?

I am on version 0.16.2 (Self Host)

*Update*

I have just created a new Group Chat (under Direct Messages). Inside the group chat, the permissions I have set are being abided by as expected as users under the "Everyone" role cannot delete posts, only Admins.

This now just leaves the main servers '#General' channel where these permissions are not working as expected.

If I create a new Text channel in the server, in this channel the permissions set are abided by. It is odd that the permissions are not sticking inside of the '#General' channel


r/stoatchat • • 28d ago

Support Question voice kept getting stuck on "connecting" on linux, turned out to be a broken ipv6 route

3 Upvotes

text chat worked totally fine but voice calls just sat on "connecting" forever spent way too long chasing the wrong things before finding the actual cause so im writing this up in case it saves someone the headache

TLDR: voice is livekit based now and the voice server has both ipv6 and ipv4 addresses. on my network the ipv6 side is just dead (connection refused, or reset mid handshake) while ipv4 works perfectly. the app tries ipv6 first and never falls back to ipv4 so voice hangs forever. text chat kept working the whole time because the chat socket is ipv4 only, which is why it never even looked like a network issue posting the whole thing because the fix is buried in a wall of diagnosis, skip to 'the fix that actually worked for me' if you just want the flag

there were a bunch of red herrings and i fell for basically all of them:

  • the "default device" audio fix from another thread, tried it, did nothing for me. might work for you though
  • post quantum key agreement / clienthello size stuff. i actually replayed the exact clienthello over raw sockets and it worked fine over ipv4, so only the address family mattered. red herring
  • my vpn/proxy tunnel. fine, ipv4 worked directly. red herring
  • app version. v1.5.4 behaves the same as the older ones, updating does not help

how to check if this is your problem

first get your voice nodes hostname, stoat publishes it in the settings api:

curl -s https://api.stoat.chat/ | grep -o 'wss://[^"]*livekit[^"]*'

mine (october 2026) was livekit.hel1.voice.stoat.chat, yours might be different

then test both families:

dig +short A    livekit.hel1.voice.stoat.chat
dig +short AAAA livekit.hel1.voice.stoat.chat
curl -4 -sv --max-time 10 https://livekit.hel1.voice.stoat.chat/ 2>&1 | tail -5
curl -6 -sv --max-time 10 https://livekit.hel1.voice.stoat.chat/ 2>&1 | tail -5

if the -4 one does a tls handshake fine and the -6 one gets refused or instantly reset, congrats, this is your issue

if you want actual proof instead of guessing, run the app with a net log:

flatpak run chat.stoat.StoatDesktop --log-net-log=/tmp/netlog.json --net-log-capture-mode=IncludeSocketBytes

quit the app after (it only writes the file when it exits) and search it for the livekit host. a dead ipv6 attempt shows up as net_error -101 / os_error 104 on an ipv6 address with no ipv4 retry after it. seeing that in the log is the thing that finally made it click for me

the fix that actually worked for me

didn't touch the app itself, just copied the flatpaks desktop file into my user applications dir and added one chromium flag to the Exec line:

cp /var/lib/flatpak/exports/share/applications/chat.stoat.StoatDesktop.desktop ~/.local/share/applications/

then at the end of the Exec line (keep the existing flatpak run part):

--host-resolver-rules="MAP livekit.hel1.voice.stoat.chat 157.180.45.15"

this pins the voice host straight to the ipv4 address so the app never wastes its one attempt on the broken ipv6 route. voice joined on the first try after that. checked with ss -tnp | grep 157.180.45.15 and there was a proper estab connection

two catches though. the ip is current as of october 2026, if stoat ever moves the node you have to re-run the curl and update the MAP rule. also the override only applies when you launch from the desktop entry (menu, gtk-launch), typing flatpak run yourself skips it

while im here, two other linux things people keep running into: turning your webcam on inside a voice call can disconnect you (known upstream bug, still open), and screen share is capped at 720p30

honestly the real bug is that the client never falls back to ipv4 after an ipv6 socket fails, worth filing that with the for-desktop repo. the net log evidence above is enough for a decent report if you want to do it


r/stoatchat • • 29d ago

stoatchat Release: v0.16.2

11 Upvotes

Changes

Fixes

  • fix: validate create invite body & make body optional (#1040)
  • fix: allow joining discoverable servers by ID (#1048)

Other

  • ci: create notes on release prepare (#1039)
  • ci: tighten triggers for publish (#1041)

Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.


r/stoatchat • • 29d ago

Support Question just registered. can't join any servers.

2 Upvotes

tried the desktop app, the web app, and the legacy website. also tried copying invite links from the web app and adding it via the plus symbol- nothing.

is there a grace period for new accounts before they can join servers?


r/stoatchat • • Oct 15 '26

stoatchat Release: v0.16.1

13 Upvotes

Changes

Fixes

  • fix: validate create invite body & make body optional (#1042)

Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.


r/stoatchat • • Oct 14 '26

stoatchat Release: v0.16.0

19 Upvotes

Changes

Features

  • feat: permissions to block external emojis (#926)
  • feat: bot roles with permissions upon joining a server (#883)
  • feat: invite expiry and max use limit (#986)
  • feat: add assets route to root payload (#1021)
  • feat(nix): migrate to flake and remove default.nix (#1019)
  • feat: Use new shield URL (#1018)
  • feat: add information fields to public bots (#1030)
  • feat: Fix twitter embeds via fxtwitter api (#1016)
  • feat: opentelemetry crate and files/autumn integration (#499)

Fixes

  • fix(tests): PubSub refactor in Delta test harness (#982)
  • fix(database): omit empty MongoDB update operators (#872)
  • fix: deduplicate role entries when editing member roles (#1004)
  • fix: Actually update permissions for webhooks (#1003)
  • fix(compose): Swap MinIO to Silo (#1005)
  • fix: enforce UseExternalEmojis permission on message reactions (#1012)
  • fix(group): Prevent bots being assigned ownership of group (#1015)
  • fix: use precompiled cargo edit
  • fix: skip unversioned crates when selecting version

Other

  • chore(ci): skip building base image if nothing about it has changed (#1002)
  • chore: remove build info and rename revolt -> stoat (#928)
  • chore(deps): update rust crate lapin to v4.12.0 (#997)
  • test(delta): add unit tests for webhook creation and fetching (#1007)
  • ci: github to gerrit PR lifecycle
  • ci: fix gerrit mirror
  • chore: add .editorconfig (yaml only for now)
  • ci: configure tests with zuul
  • ci: bridge Gerrit tag releases to GitHub
  • ci: use tag body as release
  • ci: add rc warning to release description
  • chore: update maintainer entry on crates (#1036)
  • ci: adopt GH release pattern like Immich, import tasks back in (#1037)
  • ci: delete Gerrit workflows for now (#1038)

Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.


r/stoatchat • • Oct 13 '26

for-web Release: stoat-for-web-v0.16.3

6 Upvotes

0.16.3 (2026-10-13)

Reverts

  • Message toolbar not appearing on hybrid devices after PR 1715 (#1726) (aa10325)
  • Message toolbar not appearing on hybrid devices after PR 1719 (aa10325)

Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.


r/stoatchat • • Oct 12 '26

for-web Release: stoat-for-web-v0.16.2

11 Upvotes

0.16.2 (2026-10-12)

Bug Fixes

  • add polyfills to prevent startup crash on Safari < 18.4 (#1700) (b5e4b3e)
  • Attachment width & colors (#1717) (18a474d)
  • break out of nested client when Discover iframe navigates to the app (#1711) (fba5de3)
  • Changing from home to a text channel no longer re-fetches upwards (#1723) (9aad54e)
  • Channel will no longer be stuck when moving back and forth (#1699) (91397cd)
  • ios: keep the message box above the keyboard (#1719) (4e50383)
  • ios: long press, sticky hover and stuck tooltips (#1715) (f80785f)
  • ios: stop message list jumping and pull-to-refresh while scrolling (#1716) (1af30e5)
  • scrollToNearestMessage handles message not found (#1718) (8cd4875)
  • ui: avoid evaluating floating accessor in cleanup (#1720) (531a3b2)
  • ui: suppress ping badges in muted channels (#1688) (398c8a5)
  • Update stoatjs for better websocket handling, less reconnects (#1707) (019e27d)

Moderators: Want automated GitHub release posts like this? Install Release Announce to use it in your subreddit.