[image](https://feedback.fluxer.com/p/742#f-732)Removed: -### ChecksRemoved: -Removed: -- ☑ I searched existing issues.Removed: -- ☑ I wrote this report in my own words, except for direct translation if needed.Removed: -
Show
Naming a channel after a user ID makes it render as that user's name instead of the real name
Summary
The new issue for #425 since it got closed due to v2.
Naming a channel a user ID like "1473229884793090118" will log in the audit log, but the client thinks that it should resolve this ID to a user. The same happens with roles and potentially other things.
This happens because the client will check if something "looks like" a snowflake and if it does, try to resolve it, without taking the context of the field into consideration.
Steps to reproduce
Create a channel (name it whatever you want). You can also use an existing channel.
Copy your user ID.
Make the channel name be the user ID.
Look at the audit log. It is logged as described above.
Environment
Canary Desktop 2026.602.31138, Web 2026.605.11941, Linux 7.1.2-arch3-1 (x64), Electron 41.2.2, Chrome 146.0.7680.188, Node 24.14.1, Locale en-US
Also has the same behavior on stable:
stable build 508 (3250c73), 2026-06-06 21:26:08 UTC, Chrome 148.0.0.0, Linux (x86)
### SummaryRemoved: -The new issue for [#716](https://feedback.fluxer.com/p/425) since it got closed due to v2.Added: +The new issue for [#425](https://feedback.fluxer.com/p/425) since it got closed due to v2.Naming a channel a user ID like "1473229884793090118" will log in the audit log, but the client thinks that it should resolve this ID to a user. The same happens with roles and potentially other things.
Show
Naming a channel after a user ID makes it render as that user's name instead of the real name
Summary
The new issue for #425 since it got closed due to v2.
Naming a channel a user ID like "1473229884793090118" will log in the audit log, but the client thinks that it should resolve this ID to a user. The same happens with roles and potentially other things.
This happens because the client will check if something "looks like" a snowflake and if it does, try to resolve it, without taking the context of the field into consideration.
Steps to reproduce
Create a channel (name it whatever you want). You can also use an existing channel.
Copy your user ID.
Make the channel name be the user ID.
Look at the audit log. It is logged as described above.
Environment
Canary Desktop 2026.602.31138, Web 2026.605.11941, Linux 7.1.2-arch3-1 (x64), Electron 41.2.2, Chrome 146.0.7680.188, Node 24.14.1, Locale en-US
Also has the same behavior on stable:
stable build 508 (3250c73), 2026-06-06 21:26:08 UTC, Chrome 148.0.0.0, Linux (x86)
☑ I wrote this report in my own words, except for direct translation if needed.
Original by Rex
Show
Naming a channel after a user ID makes it render as that user's name instead of the real name
Summary
The new issue for #716 since it got closed due to v2.
Naming a channel a user ID like "1473229884793090118" will log in the audit log, but the client thinks that it should resolve this ID to a user. The same happens with roles and potentially other things.
This happens because the client will check if something "looks like" a snowflake and if it does, try to resolve it, without taking the context of the field into consideration.
Steps to reproduce
Create a channel (name it whatever you want). You can also use an existing channel.
Copy your user ID.
Make the channel name be the user ID.
Look at the audit log. It is logged as described above.
Environment
Canary Desktop 2026.602.31138, Web 2026.605.11941, Linux 7.1.2-arch3-1 (x64), Electron 41.2.2, Chrome 146.0.7680.188, Node 24.14.1, Locale en-US
Also has the same behavior on stable:
stable build 508 (3250c73), 2026-06-06 21:26:08 UTC, Chrome 148.0.0.0, Linux (x86)