Edit history

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.

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

image image

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.

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

image image

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 #2930 , 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.

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

image image