Summary
When a "Message Link" is copied and pasted into a browser, the application fails to resolve the URL and triggers a 404 error, even though the URL structure in the address bar appears correct.
Impact: This is a significant functional bug that breaks the core navigation and sharing experience. Users are unable to reference or share specific messages externally, leading to a loss of context and poor user retention.
Realistic Scenario: A user shares a direct link to an important announcement or a specific message with a friend. When the friend clicks the link, they are met with a 404 error page instead of the intended content, making the "Copy Message Link" feature useless.
Steps to reproduce
Step 1: Open Fluxer on the web client using Google Chrome.
Step 2: Right-click any message in a DM or Server and select "Copy Message Link".
Step 3: Paste this link into a new browser tab or an Incognito window.
Observed Behavior: The browser shows a 404 error page (as seen in the attached screenshot).
Expected Behavior: The platform should resolve the path (e.g., /channels/@me/...) and display the specific message.
Environment (optional)
stable build 277 (e0b277d), 2026-04-10 20:35:44 UTC, Chrome 146.0.0.0, Windows NT 10.0 (x64)
Logs or screenshots (optional)
Root Cause Analysis:
The issue is specifically caused by the missing
web. prefix in the generated URL.
- Current (Broken) Output:
https://fluxer.app/channels/1427764882469228556/1427764882469228559/1492307747926921254
- Correct (Working) URL:
https://web.fluxer.app/channels/1427764882469228556/1427764882469228559/1492307747926921254
The function generates the link without the web. subdomain. If the prefix is manually corrected, the routing works perfectly. The fix should involve updating the string generator in the "Copy Message Link" function to include the correct subdomain.
Proof: I have attached screenshots showing the exact 404 error page while the message URL is still present in the address bar. I have also tested this in Incognito mode and cleared my cache/cookies to ensure this is not a local client-side issue.
image
image
image
1 comment
Comment by ternera