[Self-hosted] System DMs show "Fluxer" on web instead of the configured instance name

(#900) Bug Closed: Fixed dms self-hosting

Reproduction steps

  1. Use a self-hosted instance with a custom instance name.
  2. Send a system DM to a user.
  3. Open the system DM on mobile.
  4. Observe that the configured instance name is used.
  5. Open the same system DM in the Web client.
  6. Observe that the conversation is shown as coming from "Fluxer".
  7. Observe that the informational notice in the same conversation still uses the configured instance name.

Observed behaviour

System DMs on a self-hosted instance use different branding depending on the client. On mobile, the system DM is branded correctly using the configured self-hosted instance name. On Web, however, the same system DM is presented as coming from "Fluxer". The Web client currently shows "Fluxer" in several places, including:
  • The DM list
  • The message sender name
  • The system profile (Fluxer#0000)
  • The DM introduction text (for example, "Say hi to Fluxer. Your DM starts here.")
At the same time, the informational notice at the bottom of the same conversation correctly uses the configured instance name. This results in inconsistent branding within the same system DM view. Expected behavior: The Web client should use the configured self-hosted instance branding for system DMs, matching the behavior on mobile. The configured instance name should be used consistently throughout the system DM interface, and the generic "Fluxer" identity should not be exposed to users as the visible sender or conversation identity. Actual behavior: Mobile correctly uses the configured self-hosted instance name. Web instead displays the generic "Fluxer" system identity in several parts of the system DM interface, while other parts of the same view already use the configured instance name correctly. Possibly related This may be related to #865 , which also concerns inconsistent self-hosted branding between different client surfaces. This report affects a different area — system DMs — so it is being reported separately.

Build information

Stable Web 2026.1003.2520, Linux (x64), Firefox 157.0, Locale en-US

Platform

Web, Self-hosting

Evidence

  1. penguin changed the status from Awaiting confirmation to Fixed
  1. The pull request fluxer#3355 mentions this post Merged
  2. The pull request fluxer#3355 was merged Merged

10 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote 3 replies
Status changed from Needs triage to Awaiting confirmation
System DMs on self-hosted instances now show your instance's product name and icon instead of Fluxer.
Comment by Alek B | TekkNodes
Alek B | TekkNodes 1 vote 1 reply
Still shows Fluxer.
Comment by Hampus
HampusStaff 1 vote
It will still show Fluxer if you are using the desktop client which has not yet received the update. It should work on an updated integrated web client of your instance. Please provide your build info!
Comment by Alek B | TekkNodes
Canary Web 2026.1010.150331, Linux (x64), Firefox 157.0, Locale en-US Sent fresh account alt a DM test from the Admin, still getting Fluxer
Comment by dander
dander 1 vote Fixed for me
Fixed for me Canary Web 2026.1010.183920, Linux (x64), Firefox 157.0, Locale en-US
Comment by Alek B | TekkNodes
Alek B | TekkNodes 1 vote edited Fixed for me
Canary Desktop 2026.1009.45608, Web 2026.1010.212806, Linux 7.2.9-1-cachyos (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US and web Canary Web 2026.1010.212805, Linux (x64), Firefox 157.0, Locale en-US
Comment by penguin
penguin OP1 vote Fixed for me
Confirmed fixed on my self-hosted instance! System DMs now correctly display my custom instance name and avatar instead of the default Fluxer branding. Even previously sent system messages are displayed with the correct branding now. Everything looks great. Thank you so much for the fix! ❤️