Edit history

Earlier versions of Resending a failed reply turns a non-pinging reply into a pinging one, newest first.

Current version | Edited by Rex
Changes
example mesasages in hq: https://web.fluxer.app/channels/1427764882469228556/1427764882469228559/1495038814330341486Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

Resending a failed reply turns a non-pinging reply into a pinging one

Summary

When I sent a message (as a non pinged reply) in hq and the slowmode prevented me from doing so, the message allowed me to resend the red text after the slowmode timer was over. This caused my non ping reply to suddenly be a pinged reply.

Steps to reproduce

  1. fail a message send as a non ping reply (in my case send a message before slowmode is over)
  2. resend the red message once possible
  3. watch how magically the non ping turns into a ping (as indicated by the @ infront of the name of the person being replied to)

Environment (optional)

PC, stable build 382 (5a24713), Firefox 149.0

Logs or screenshots (optional)

example mesasages in hq: https://web.fluxer.app/channels/1427764882469228556/1427764882469228559/1495038814330341486
Edited by Rex
Changes
Removed: resending a failed reply message ignores whether the reply was marked as non pingedAdded: Resending a failed reply turns a non-pinging reply into a pinging one### Summary
Show

Resending a failed reply turns a non-pinging reply into a pinging one

Summary

When I sent a message (as a non pinged reply) in hq and the slowmode prevented me from doing so, the message allowed me to resend the red text after the slowmode timer was over. This caused my non ping reply to suddenly be a pinged reply.

Steps to reproduce

  1. fail a message send as a non ping reply (in my case send a message before slowmode is over)
  2. resend the red message once possible
  3. watch how magically the non ping turns into a ping (as indicated by the @ infront of the name of the person being replied to)

Environment (optional)

PC, stable build 382 (5a24713), Firefox 149.0

Logs or screenshots (optional)

example mesasages in hq: https://web.fluxer.app/channels/1427764882469228556/1427764882469228559/1495038814330341486

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.
Original by Rex
Show

resending a failed reply message ignores whether the reply was marked as non pinged

Summary

When I sent a message (as a non pinged reply) in hq and the slowmode prevented me from doing so, the message allowed me to resend the red text after the slowmode timer was over. This caused my non ping reply to suddenly be a pinged reply.

Steps to reproduce

  1. fail a message send as a non ping reply (in my case send a message before slowmode is over)
  2. resend the red message once possible
  3. watch how magically the non ping turns into a ping (as indicated by the @ infront of the name of the person being replied to)

Environment (optional)

PC, stable build 382 (5a24713), Firefox 149.0

Logs or screenshots (optional)

example mesasages in hq: https://web.fluxer.app/channels/1427764882469228556/1427764882469228559/1495038814330341486

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.