Edit history

Two issues; the first being that s/e/d replacements are 'ratelimited' by cooldown¹, and the second that s/e/d replacement does not respect trailing whitespace. --- ¹I actually reported this issue a while back and it was fixed then, but a few months ago it appears to have re-appeared. As I'm literally one of the three users that use s/e/d replace I wasn't too bothered to report, hence I am only reporting now when there is another issue.

(For onlookers who have never heard of s/e/d before, in Fluxer you are able to "send" a message s/{before}/{after} to replace text; i.e. if I send a message I love Discord then immediately afterward s/Discord/Fluxer, the message will now read as I love Fluxer). --- Bug number one: As a s/e/d replacement is 'activated' by "sending" the message (and intercepted client-side afaik), when message cooldown is enabled, for some reason the s/e/d message will not process until the cooldown completes. Note editing a message normally still works, and sending through the s/e/d message once the cooldown clears does not re-start the cooldown (both of which are the expected behaviour), and considering Hampus has resolved this before; this is a bug not feature. Tested on Desktop (Web).

Bug number two: If I have a message say abcdef, and I send through s/abc/123 (notice the space after the "3"), Fluxer trims the message before proessing the edit, resulting in 123def instead of the expected/correct result of 123 def. I actually thought I would call out Discord for doing this wrong too, but it seems that Discord actually handles this correctly for some odd reason. Tested on both Desktop (Web) and Mobile (GPlay).

Canary Web 2026.1102.30752, Linux (x86), Chrome 156.0.0.0, Locale en-US

P.S. selected ui tag as I didn't know what category from the options suited this bug report best; both of these are client-side issues.