AllBugsFeaturesChangelogBountiesSearchNew post
Sign in with Fluxer
Bugs

Cannot forward messages with large attachments when you don't have Plutonium

(#4153) Bug Open: In progress Priority: P1 api messaging
by Jackuczys

Reproduction steps

This needs to be tested from an account that doesn't have Plutonium.
  1. Join https://fluxer.gg/fluxer-hq.
  2. Go to this message with large attachment: https://web.fluxer.app/channels/1427764882469228556/1427764882469228559/1561351554982739968
  3. Try forwarding the message to another channel
  4. See the issue:
pasted-image-1.png

Expected behaviour

I expected to be able to forward a message with large attachment when I don't have the ability to send large attachments myself. This is how forwarding works on Discord.

Actual behaviour

I was unable to forward a message with a large attachment, here's a popup I got on the desktop client: pasted-image-1.png Same occurs when trying to do this through API directly: 
400 Bad Request (error code: FILE_SIZE_TOO_LARGE): File size is too large. Maximum file size is 26214400.

Build information

N/A, API issue

Platform

macOS, Windows, Linux, Web, Android, iOS, API

  1. Hampus changed the status from Confirmed to In progress

4 comments

Sign in with Fluxer to comment and vote.
Comment by Fullest
FullestReviewer 1 vote
Status changed from Needs triage to Confirmed
CR: Canary Desktop 2026.1018.133614, Web 2026.1018.133614, Linux 7.2.10-200.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US
Permalink
Comment by Hampus
HampusStaff 1 vote 2 replies
Official response
While this is working as intended (matches the behaviour on Discord, for example), I recently introduced a new mechanism for avoiding cloning of forwarded attachments for the announcement channels feature. As such, I could make it so that attachments that are deleted from the source message that are too big for your file upload quota also break downstream, but still allows you to forward it. As such, it is not a faithful snapshot, but it arguably matches user expectations better.
Permalink
Comment by Jackuczys
Jackuczys OP1 vote 1 reply
I've tested this on Discord (as mentioned in the issue description) and Fluxer does not match Discord's behavior.
Permalink
Comment by Hampus
HampusStaff 1 vote
I overlooked that – at the time I implemented this feature, it matched Discord. They might've realised they could implement it this way with a non-snapshot recently too. Or they let you take a full snapshot without paying for it now anyway, though that wouldn't be something I would like to do at this time for as long as we do not have content-addressed storage in place. I can look into implementing content-addressed storage for this thing only initially, perhaps.
Permalink